How severe is CVE-2019-1003011?

CVE-2019-1003011 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-1003011?

CVE-2019-1003011 affects the following packages: org.jenkins-ci.plugins:token-macro (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-1003011?

Update org.jenkins-ci.plugins:token-macro to 2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-1003011 is resolved across your whole dependency graph.

How do I detect CVE-2019-1003011 in my Maven dependencies?

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.

How do I mitigate CVE-2019-1003011 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2019-1003011 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-1003011 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-1003011?

CVE-2019-1003011 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 81th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-1003011?

CVE-2019-1003011 is classified as CWE-674 (CWE-674). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-1003011 published, and has it been updated?

CVE-2019-1003011 was published on February 6, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2019-1003011 — token-macro

HIGHFix: jenkinsci/token-macro-plugin@7016360

CVE-2019-1003011 is a high-severity (CVSS 8.1) CWE-674 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.

Jenkins Token Macro Plugin's recursive token expansion results in information disclosure and DoS

Also known asGHSA-23h9-m55m-c5jp

Published

Feb 6, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

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 information exposure and denial of service vulnerability exists in Jenkins Token Macro Plugin 2.5 and earlier in src/main/java/org/jenkinsci/plugins/tokenmacro/Parser.java, src/main/java/org/jenkinsci/plugins/tokenmacro/TokenMacro.java, src/main/java/org/jenkinsci/plugins/tokenmacro/impl/AbstractChangesSinceMacro.java, src/main/java/org/jenkinsci/plugins/tokenmacro/impl/ChangesSinceLastBuildMacro.java, src/main/java/org/jenkinsci/plugins/tokenmacro/impl/ProjectUrlMacro.java that allows attackers with the ability to control token macro input (such as SCM changelogs) to define recursive input that results in unexpected macro evaluation.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:token-macro`	all versions	2.6`org.jenkins-ci.plugins:token-macro:2.6`

Affected Products

2 products · 2 configurations

Application

token macrojenkins

≤ 2.5

range

Application

openshift container platformredhat

1 version

3.11

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update org.jenkins-ci.plugins:token-macro to 2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-1003011 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.11	`atomic-enterprise-service-catalog-1:3.11.82-1.git.1673.133961e.el7`	RHBA-2019:0326

Frequently Asked Questions

Jenkins Token Macro Plugin recursively applied token expansion. This could be used by users able to affect input to token expansion (such as change log messages), to inject additional tokens into the input, which would then be expanded, resulting in information disclosure (for example values of environment variables), or denial of service. Most tokens have been changed to no longer recursively apply token expansion.

O3 Security · Impact-Aware SCA

Is CVE-2019-1003011 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

CWE Classification

CWE-674CWE-674

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Feb 6, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-1003011

GHSA-23h9-m55m-c5jp

References

Advisoryaccess.redhat.com · RHBA 2019:0326 Advisoryaccess.redhat.com · RHBA 2019:0327 Advisoryjenkins.io · 2019 01 28 Advisorynvd.nist.gov · CVE 2019 1003011 Webgithub.com · 70163600031ea8d43833e6eea928f8fa2e44f96a

Related vulnerabilities

Also affects token-macro

This CVE is high severity, in line with the other 1 CVE affecting token-macro.

CVE-2019-10337

Same weakness: CWE-674

This CVE is high severity; 3 of 7 other CVEs with CWE-674 are rated as high or higher (top: high).

GHSA-2wrx-84qj-4pcgCVE-2026-119187CVE-2026-61847CVE-2026-116586CVE-2026-109413CVE-2026-114605CVE-2026-113650Browse all CWE-674

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026