Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV

CVE-2025-13472 BlazeMeterJenkinsPlugin

Fix: jenkinsci/blazemeter-plugin@9fe5ed7

CVE-2025-13472 is a CWE-862 vulnerability in com.blazemeter.plugins:BlazeMeterJenkinsPlugin. A fix is available for com.blazemeter.plugins:BlazeMeterJenkinsPlugin — see the affected versions and patch details below.

BlazeMeter Jenkins Plugin is Missing Authorization for Available Resources

Published
Dec 3, 2025
Updated
Dec 3, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-13472.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected
com.blazemeter.plugins:BlazeMeterJenkinsPlugin

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

A fix was made in BlazeMeter Jenkins Plugin version 4.27 to allow users only with certain permissions to see the list of available resources like credential IDs, bzm workspaces and bzm project Ids. Prior to this fix, anyone could see this list as a dropdown on the Jenkins UI.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.blazemeter.plugins:BlazeMeterJenkinsPluginall versions4.27com.blazemeter.plugins:BlazeMeterJenkinsPlugin:4.27

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update com.blazemeter.plugins:BlazeMeterJenkinsPlugin to 4.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-13472 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-13472 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-13472. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A fix was made in BlazeMeter Jenkins Plugin version 4.27 to allow users only with certain permissions to see the list of available resources like credential IDs, bzm workspaces and bzm project Ids. Prior to this fix, anyone could see this list as a dropdown on the Jenkins UI.
O3 Security · Impact-Aware SCA

Is CVE-2025-13472 in your dependencies?

O3 Security finds CVE-2025-13472 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2025-13472: BlazeMeterJenkinsPlugin | O3 Security