CVE-2025-31727: Medium severity jenkins vulnerability
Jenkins AsakusaSatellite Plugin 0.1.1 and earlier stores AsakusaSatellite API keys unencrypted in job config.xml files on the Jenkins controller as part of its configuration.
These API keys can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.
Additionally, the job configuration form does not mask these API keys, increasing the potential for attackers to observe and capture them.
As of publication of this advisory, there is no fix.
Other sources
Jenkins AsakusaSatellite Plugin 0.1.1 and earlier stores AsakusaSatellite API keys 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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-31727?
The severity of CVE-2025-31727 is classified as high due to the exposure of sensitive API keys.
How do I fix CVE-2025-31727?
To fix CVE-2025-31727, upgrade the Jenkins AsakusaSatellite Plugin to a version later than 0.1.1.
What kind of data is exposed in CVE-2025-31727?
CVE-2025-31727 exposes AsakusaSatellite API keys which are stored unencrypted in job config.xml files.
Who is affected by CVE-2025-31727?
Users with Item/Extended Read permission or access to the Jenkins controller file system are affected by CVE-2025-31727.
Is there a workaround for CVE-2025-31727?
There is no official workaround for CVE-2025-31727; upgrading to a secure version is recommended.