Jenkins does not encrypt secrets from POST config.xml submissions before storing them in job configurations

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps org.jenkins-ci.main:jenkins-core (maven), org.jenkins-ci.main:jenkins-core (maven), org.jenkins-ci.main:jenkins-core (maven), org.jenkins-ci.main:jenkins-core (maven). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for org.jenkins-ci.main:jenkins-core, org.jenkins-ci.main:jenkins-core, org.jenkins-ci.main:jenkins-core.
2. 2Review the reported fix. Update org.jenkins-ci.main:jenkins-core to 2.555.3; org.jenkins-ci.main:jenkins-core to 2.568; org.jenkins-ci.main:jenkins-core to 2.555.3; org.jenkins-ci.main:jenkins-core to 2.568 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Jun 10, 2026

   Evidence: source:ghsa:source_dates:source-dates:record

2. Source modified

   Sep 10, 2026

   Evidence: source:ghsa:source_dates:source-dates:record

3. First seen by HOL

   Aug 13, 2026

Sources and claim methodology

• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• NVD vulnerability recordnvd.nist.gov
• Source referencejenkins.io
• GitHub security advisorygithub.com