Skip to main content
CVE-2025-53653VulnerabilityPublished Updated

Org.jenkins ci.plugins:aqua security scanner: Jenkins Aqua Security Scanner Plugin vulnerability exposes scanner

Affects org.jenkins-ci.plugins:aqua-security-scannerSource GCVE Database

0
Compare
Authoritative record:CVE-2025-53653· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 4 Nov 2026, 18:13 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.14.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.jenkins-ci.plugins:aqua-security-scannerAffected
  • <=3.2.8
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a patch is released, Jenkins administrators should restrict Item/Extended Read permissions to trusted users only and tightly control access to the Jenkins controller file system to prevent unauthorized token disclosure.

Description

Jenkins Aqua Security Scanner Plugin versions 3.2.8 and earlier store Aqua API scanner tokens unencrypted in job config.xml files on the Jenkins controller. These tokens can be accessed by users with Item/Extended Read permissions or by anyone with file system access to the Jenkins controller. This exposure risks unauthorized disclosure of sensitive tokens. No fix is currently available for this vulnerability.

References

Community reviews

Loading reviews…