CVE-2026-53442: Vulnerability in Jenkins Project Jenkins
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.
AI Analysis
Technical Summary
CVE-2026-53442 affects Jenkins versions 2.567 and earlier, and LTS 2.555.2 and earlier. The vulnerability involves the failure to encrypt secrets submitted through POST requests to config.xml, resulting in these secrets being stored unencrypted in job configuration files on the Jenkins controller. Users with Item/Extended Read permission or access to the Jenkins controller file system can view these secrets. This is classified under CWE-311 (Missing Encryption of Sensitive Data). The CVSS v3.1 base score is 5.3 (medium severity), reflecting network attack vector, low complexity, no privileges required, no user interaction, and confidentiality impact only.
Potential Impact
Sensitive secrets submitted via config.xml POST requests are stored unencrypted on the Jenkins controller, exposing confidential information to users with Item/Extended Read permission or anyone with file system access to the Jenkins controller. This can lead to unauthorized disclosure of secrets, potentially compromising Jenkins jobs or credentials stored within.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict Item/Extended Read permissions to trusted users only and limit access to the Jenkins controller file system to prevent unauthorized viewing of unencrypted secrets.
CVE-2026-53442: Vulnerability in Jenkins Project Jenkins
Description
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.
CVSS v3.1
Score 5.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53442 affects Jenkins versions 2.567 and earlier, and LTS 2.555.2 and earlier. The vulnerability involves the failure to encrypt secrets submitted through POST requests to config.xml, resulting in these secrets being stored unencrypted in job configuration files on the Jenkins controller. Users with Item/Extended Read permission or access to the Jenkins controller file system can view these secrets. This is classified under CWE-311 (Missing Encryption of Sensitive Data). The CVSS v3.1 base score is 5.3 (medium severity), reflecting network attack vector, low complexity, no privileges required, no user interaction, and confidentiality impact only.
Potential Impact
Sensitive secrets submitted via config.xml POST requests are stored unencrypted on the Jenkins controller, exposing confidential information to users with Item/Extended Read permission or anyone with file system access to the Jenkins controller. This can lead to unauthorized disclosure of secrets, potentially compromising Jenkins jobs or credentials stored within.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict Item/Extended Read permissions to trusted users only and limit access to the Jenkins controller file system to prevent unauthorized viewing of unencrypted secrets.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- jenkins
- Date Reserved
- 2026-06-09T14:26:44.789Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2967b6c9170919df1fdd52
Added to database: 06/10/2026, 13:33:42 UTC
Last enriched: 06/10/2026, 17:22:19 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 123
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.