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

CVE-2022-23107 — warnings-ng

HIGH

CVE-2022-23107 is a high-severity (CVSS 8.1) Path Traversal vulnerability in io.jenkins.plugins:warnings-ng. A fix is available for io.jenkins.plugins:warnings-ng — see the affected versions and patch details below.

Path Traversal in Jenkins Warnings Next Generation Plugin

Also known asGHSA-rvh4-g2rj-hr9c
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk
0.26%0.97%1.68%2.39%0.8%1.9%May 26Aug 26Nov 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

4 pkgs affected
☕io.jenkins.plugins:warnings-ng☕io.jenkins.plugins:warnings-ng☕io.jenkins.plugins:warnings-ng☕io.jenkins.plugins:warnings-ng

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

Jenkins Warnings Next Generation Plugin prior to 9.10.3, 9.7.1, 9.5.2, and 9.0.2 does not restrict the name of a file when configuring a custom ID.

This allows attackers with Item/Configure permission to write and read specific files with a hard-coded suffix on the Jenkins controller file system.

Jenkins Warnings Next Generation Plugin 9.10.3, 9.7.1, 9.5.2, and 9.0.2 checks for the presence of prohibited directory separator characters in the custom ID.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.jenkins.plugins:warnings-ng≥ 9.8.0&&< 9.10.39.10.3io.jenkins.plugins:warnings-ng:9.10.3
☕Mavenio.jenkins.plugins:warnings-ng≥ 9.6.0&&< 9.7.19.7.1io.jenkins.plugins:warnings-ng:9.7.1
☕Mavenio.jenkins.plugins:warnings-ng≥ 9.1.0&&< 9.5.29.5.2io.jenkins.plugins:warnings-ng:9.5.2
☕Mavenio.jenkins.plugins:warnings-ngall versions9.0.2io.jenkins.plugins:warnings-ng:9.0.2

Affected Products

1 product · 4 configurations
Application
warnings next generationjenkins
≥ 9.10.0 && ≤ 9.10.2
1 version
9.7.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update io.jenkins.plugins:warnings-ng to 9.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23107 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Jenkins Warnings Next Generation Plugin prior to 9.10.3, 9.7.1, 9.5.2, and 9.0.2 does not restrict the name of a file when configuring a custom ID. This allows attackers with Item/Configure permission to write and read specific files with a hard-coded suffix on the Jenkins controller file system. Jenkins Warnings Next Generation Plugin 9.10.3, 9.7.1, 9.5.2, and 9.0.2 checks for the presence of prohibited directory separator characters in the custom ID.
O3 Security · Impact-Aware SCA

Is CVE-2022-23107 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-23107: warnings-ng — Fixed in 9.10.3