Org.jenkins ci.plugins:applitools eyes: Jenkins Applitools Eyes Plugin vulnerability exposes unencrypted keys to
Affects org.jenkins-ci.plugins:applitools-eyesSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 4 Nov 2026, 18:15 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Mavenorg.jenkins-ci.plugins:applitools-eyes | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should restrict access to Jenkins job configurations and the Jenkins controller file system to trusted personnel only. Review and limit Item/Extended Read permissions to minimize exposure. Monitor for any updates from the vendor regarding patches or mitigations.
Description
Jenkins Applitools Eyes Plugin versions 1.16.5 and earlier store Applitools API keys unencrypted in job config.xml files on the Jenkins controller. These keys can be accessed by users with Item/Extended Read permission or by anyone with access to the Jenkins controller file system. This exposure could lead to unauthorized disclosure of sensitive API keys.