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

CVE-2022-23106 — configuration-as-code

MEDIUMFix: jenkinsci/configuration-as-code-plugin@4f42567

CVE-2022-23106 is a medium-severity (CVSS 5.3) CWE-203 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.

Observable Discrepancy and Observable Timing Discrepancy in Jenkins Configuration as Code Plugin

Also known asGHSA-fpj7-9xm6-8hgr
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk+0.04%
Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk
0.00%0.55%1.11%1.66%0.1%1.2%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

4 pkgs affected
☕io.jenkins:configuration-as-code☕io.jenkins:configuration-as-code☕io.jenkins:configuration-as-code☕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

Jenkins Configuration as Code Plugin prior to 1.55.1, 1.54.1, 1.53.1, and 1.47.1 does not use a constant-time comparison when checking whether two authentication tokens are equal.

This could potentially allow attackers to use statistical methods to obtain a valid authentication token.

Configuration as Code Plugin 1.55.1, 1.54.1, 1.53.1, and 1.47.1 now uses a constant-time comparison when validating authentication tokens.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.jenkins:configuration-as-code≥ 1.55&&< 1.55.11.55.1io.jenkins:configuration-as-code:1.55.1
☕Mavenio.jenkins:configuration-as-code≥ 1.54&&< 1.54.11.54.1io.jenkins:configuration-as-code:1.54.1
☕Mavenio.jenkins:configuration-as-code≥ 1.48&&< 1.53.11.53.1io.jenkins:configuration-as-code:1.53.1
☕Mavenio.jenkins:configuration-as-codeall versions1.47.1io.jenkins:configuration-as-code:1.47.1

Affected Products

1 product · 1 configurations
Application
configuration as codejenkins
≤ 1.55
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 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 1.55.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23106 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.

Frequently Asked Questions

Jenkins Configuration as Code Plugin prior to 1.55.1, 1.54.1, 1.53.1, and 1.47.1 does not use a constant-time comparison when checking whether two authentication tokens are equal. This could potentially allow attackers to use statistical methods to obtain a valid authentication token. Configuration as Code Plugin 1.55.1, 1.54.1, 1.53.1, and 1.47.1 now uses a constant-time comparison when validating authentication tokens.
O3 Security · Impact-Aware SCA

Is CVE-2022-23106 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-23106: configuration-as-code — Fixed in 1.55.1