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

Insertion of Sensitive Information into Externally-Accessible File or Directory in Jenkins Credentials PluginGHSA-xm94-9jw8-p6hw

MEDIUMFix: jenkinsci/credentials-plugin@40d0b5c

GHSA-xm94-9jw8-p6hw is a medium-severity (CVSS 4.3) CWE-538 vulnerability in org.jenkins-ci.plugins:credentials. A fix is available for org.jenkins-ci.plugins:credentials — see the affected versions and patch details below.

Also known asCVE-2019-10320
Published
Updated
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 ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk
0.00%0.49%0.98%1.47%0.1%1.0%May 26Sep 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

1 pkg affected
☕org.jenkins-ci.plugins:credentials

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 Credentials Plugin 2.1.18 and earlier allowed users with permission to create or update credentials to confirm the existence of files on the Jenkins master with an attacker-specified path, and obtain the certificate content of files containing a PKCS#12 certificate.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkins-ci.plugins:credentialsall versions2.1.19org.jenkins-ci.plugins:credentials:2.1.19

Affected Products

1 product · 1 configurations
Application
credentialsjenkins
≤ 2.1.18
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:credentials, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jenkins-ci.plugins:credentials to 2.1.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xm94-9jw8-p6hw 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.

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-enterprise-service-catalog-1:3.11.117-1.git.1.376e432.el7RHBA-2019:1605
Red Hat OpenShift Container Platform 4.1jenkins-2-plugins-0:4.1.1561471763-1.el7RHSA-2019:1636

Frequently Asked Questions

Jenkins Credentials Plugin 2.1.18 and earlier allowed users with permission to create or update credentials to confirm the existence of files on the Jenkins master with an attacker-specified path, and obtain the certificate content of files containing a PKCS#12 certificate.
O3 Security · Impact-Aware SCA

Is GHSA-xm94-9jw8-p6hw in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Insertion of Sensitive Information into Externally-Accessibl…