Zanata 3.0.0 through 3.1.2 has RCE due to EL interpolation in logging

published 2019-12-03 6y ago modified 2026-06-16 4mo ago also EUVD-2013-4351

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits: 0; none known

Patch / fix

links 2

bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-4486 advisory
github.com/zanata/zanata-server/wiki/Security-advisories advisory

Is CVE-2013-4486 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.50% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

Zanata Zanata

Classification

Weakness

CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

bugzilla.redhat.com /show_bug.cgi?id=CVE-2013-4486
issue-tracking, patch, vendor-advisory
github.com /zanata/zanata-server/wiki/Security-advisories
patch, third-party-advisory
access.redhat.com /security/cve/cve-2013-4486
third-party-advisory, vendor-advisory

Sources

CVE List CVE-2013-4486
NVD CVE-2013-4486

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.