Vulnerability in jenkins (CVE-2026-53442)
Summary
Vulnerability in jenkins (CVE-2026-53442). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.555.3, 2.568.0 or later.
Original description
The description as published by the source.
Jenkins 2.567 and earlier, LTS 2.555.2 and earlier does not encrypt secrets from POST config.xml submissions before storing them in job configurations unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Item/Extended Read permission, or access to the Jenkins controller file system.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53442 has been found in jenkins.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade jenkins to 2.555.3, 2.568.0 or later.
If unsure, ask your IT team or search "jenkins CVE-2026-53442" on the vendor's site.
CVE-2026-53442 (jenkins) — CWE-311 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.555.3, 2.568.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-311) exists in jenkins.
Check the vendor advisory for the affected versions of jenkins.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.555.3, 2.568.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jenkins' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jenkins' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
jenkinsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade jenkins to 2.555.3, 2.568.0ステージング環境で 2.555.3, 2.568.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory jenkins.io
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com