CVE-2025-53653: Jenkins Aqua Security Scanner Plugin 3.2.8 and earlier stores Scanner Tokens for Aqua API unencrypted in job c

Q: How do I fix CVE-2025-53653?

aqua security scanner: upgrade to newer than 3.2.8. Exact commands for each OS are on this page.

Q: Is CVE-2025-53653 being exploited?

CVE-2025-53653 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-53653 affect?

CVE-2025-53653 affects aqua security scanner. Severity is medium (CVSS 4.3). Jenkins Aqua Security Scanner Plugin 3.2.8 and earlier stores Scanner Tokens for Aqua API 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 J

Q: How urgent is CVE-2025-53653?

Priority 19/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2025-53653 is a medium-severity flaw (CVSS 4.3) affecting aqua security scanner. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Jenkins Aqua Security Scanner Plugin 3.2.8 and earlier stores Scanner Tokens for Aqua API 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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 86%)
CISA exploited list	No
Weakness	CWE-311
Published	2025-07-09
Last modified	2026-06-17

Publisher (CNA): Jenkins Project · Vendor: jenkins

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-07-09 16:15 UTCPublished CVE record published
2026-06-17 09:38 UTCUpdated Record last modified

jenkins aqua security scanner UPGRADE

Affected: <= 3.2.8

Fixed in: newer than 3.2.8

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy aqua-security-scanner || rpm -q aqua-security-scanner || aqua-security-scanner --version

2. UPGRADE to newer than 3.2.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade aqua-security-scanner

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade aqua-security-scanner

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-53653?

aqua security scanner: upgrade to newer than 3.2.8. Exact commands for each OS are on this page.

Is CVE-2025-53653 being exploited?

CVE-2025-53653 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-53653 affect?

CVE-2025-53653 affects aqua security scanner. Severity is medium (CVSS 4.3). Jenkins Aqua Security Scanner Plugin 3.2.8 and earlier stores Scanner Tokens for Aqua API 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 J

How urgent is CVE-2025-53653?

Priority 19/100. No elevated risk signals yet.

Software pages

Jenkins vulnerabilities

References

← Back to latest CVEs