Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-5918: Nablarch 5 (5, and 5u1 to 5u13) allows remote attackers to conduct XML External Entity (XXE) attacks via unspe

57
This month
CRITICAL 9.1REMOTEDOWNGRADE

CVE-2019-5918 is a critical-severity flaw (CVSS 9.1) affecting nablarch. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Nablarch 5 (5, and 5u1 to 5u13) allows remote attackers to conduct XML External Entity (XXE) attacks via unspecified vectors.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.9% (top 21%)
CISA exploited listNo
WeaknessCWE-611
Published2019-03-12
Last modified2026-06-17
Publisher (CNA): JPCERT/CC · Vendor: nablarch project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

nablarch project nablarch DOWNGRADE
Affected: 5 · 5u1 · 5u13
Fixed in: no fixed release known
Safe to downgrade to: a release before 5
1. Check installed version
apt-cache policy nablarch || rpm -q nablarch || nablarch --version
2. No fixed release: DOWNGRADE to a release before 5 (Debian / Ubuntu)
apt-cache madison nablarch sudo apt install nablarch=<VERSION_BEFORE_5> sudo apt-mark hold nablarch
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nablarch sudo dnf downgrade nablarch-<VERSION_BEFORE_5> sudo dnf versionlock add nablarch
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-5918?

nablarch: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-5918 being exploited?

CVE-2019-5918 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-5918 affect?

CVE-2019-5918 affects nablarch. Severity is critical (CVSS 9.1). Nablarch 5 (5, and 5u1 to 5u13) allows remote attackers to conduct XML External Entity (XXE) attacks via unspecified vectors.

How urgent is CVE-2019-5918?

Priority 57/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.