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

Jenkins Configuration as Code Plugin vulnerable to Exposure of Sensitive InformationGHSA-393r-r9mq-g9jv

MEDIUM

GHSA-393r-r9mq-g9jv is a medium-severity (CVSS 6.5) Information Exposure vulnerability in io.jenkins:configuration-as-code. A fix is available for io.jenkins:configuration-as-code — see the affected versions and patch details below.

Also known asCVE-2018-1000609
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 11, 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 CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk
0.00%0.50%0.99%1.49%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
☕io.jenkins:configuration-as-code

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 exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in ConfigurationAsCode.java that allows attackers with Overall/Read access to obtain the YAML export of the Jenkins configuration. Version 0.8-alpha contains a fix for this issue.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.jenkins:configuration-as-codeall versions0.8-alphaio.jenkins:configuration-as-code:0.8-alpha

Affected Products

1 product · 7 configurations
Application
configuration as codejenkins
7 versions
0.10.20.30.40.50.60.7

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:configuration-as-code, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.jenkins:configuration-as-code to 0.8-alpha or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-393r-r9mq-g9jv is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in ConfigurationAsCode.java that allows attackers with Overall/Read access to obtain the YAML export of the Jenkins configuration. Version 0.8-alpha contains a fix for this issue.
O3 Security · Impact-Aware SCA

Is GHSA-393r-r9mq-g9jv in your dependencies?

Find it across Maven, including transitive dependencies.

Jenkins Configuration as Code Plugin vulnerable to…