NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Improper Restriction of XML External Entity Reference Jenkins Token Macro PluginGHSA-g6h2-4x64-c59x

HIGHFix: jenkinsci/token-macro-plugin@004319f

GHSA-g6h2-4x64-c59x is a high-severity (CVSS 7.5) XML External Entity (XXE) vulnerability in org.jenkins-ci.plugins:token-macro. A fix is available for org.jenkins-ci.plugins:token-macro — see the affected versions and patch details below.

Also known asCVE-2019-10337
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk-0.02%
Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk
0.00%0.87%1.74%2.60%0.2%2.0%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.jenkins-ci.plugins:token-macro

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An XML external entities (XXE) vulnerability in Jenkins Token Macro Plugin 2.7 and earlier allowed attackers able to control a the content of the input file for the "XML" macro to have Jenkins resolve external entities, resulting in the extraction of secrets from the Jenkins agent, server-side request forgery, or denial-of-service attacks.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkins-ci.plugins:token-macroall versions2.8org.jenkins-ci.plugins:token-macro:2.8

Affected Products

1 product · 1 configurations
Application
token macrojenkins
≤ 2.7
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:token-macro, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jenkins-ci.plugins:token-macro to 2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g6h2-4x64-c59x is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat OpenShift Container Platform 3.11atomic-openshift-0:3.11.129-1.git.0.bd4f2d5.el7RHSA-2019:1851
Red Hat OpenShift Container Platform 4.1jenkins-2-plugins-0:4.1.1561471763-1.el7RHSA-2019:1636

Frequently Asked Questions

An XML external entities (XXE) vulnerability in Jenkins Token Macro Plugin 2.7 and earlier allowed attackers able to control a the content of the input file for the "XML" macro to have Jenkins resolve external entities, resulting in the extraction of secrets from the Jenkins agent, server-side request forgery, or denial-of-service attacks.
O3 Security · Impact-Aware SCA

Is GHSA-g6h2-4x64-c59x in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Restriction of XML External Entity Reference…