CVE-2025-53742: Jenkins Applitools Eyes Plugin Exposes Unencrypted API Keys

Summary

09/07/2025
No i
Moderate
4.3

CVE-2025-53742: Jenkins Applitools Eyes Plugin vulnerability exposes unencrypted keys to certain authenticated users. Affects org.jenkins-ci.plugins:pplitools-eyes versions < 1.16.5. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Jenkins Applitools Eyes Plugin is an integration tool that allows Jenkins users to utilize Applitools' visual testing capabilities within their CI/CD pipelines. This plugin enables automated visual testing, helping developers ensure that their applications appear as intended across different browsers and devices. However, it has a critical vulnerability that affects the security of sensitive information stored within Jenkins job configurations.

Vulnerability Detail

Jenkins Applitools Eyes Plugin versions 1.16.5 and earlier store Applitools API keys in an unencrypted format within the job config.xml files on the Jenkins controller. This exposes sensitive API keys to users who have Item/Extended Read permission or direct access to the Jenkins controller file system. The vulnerability arises from inadequate encryption practices, allowing unauthorized access to sensitive credentials, which could lead to unauthorized use of the Applitools service and potential data breaches.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can restrict access to the Jenkins controller file system and limit Item/Extended Read permissions to trusted users only. This will help mitigate the risk of unauthorized access to the unencrypted API keys until the plugin is updated.

Conclusion

The Jenkins Applitools Eyes Plugin vulnerability (CVE-2025-53742) poses a significant risk by exposing unencrypted API keys. Users are strongly advised to update to the latest version of the plugin to secure their sensitive information. Implementing access restrictions can serve as a temporary measure until the update is applied.

See every vulnerability recorded for org.jenkins-ci.plugins:pplitools-eyes →

Share this vulnerability

FAQ

The vulnerability has a CVSS score of 4.3, indicating a moderate severity level.

Any Jenkins user utilizing the Applitools Eyes Plugin version 1.16.5 or earlier is at risk.

If exploited, unauthorized users could gain access to sensitive Applitools API keys, leading to unauthorized use of the service and potential data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If immediate updates are not feasible, restrict access to the Jenkins controller file system and limit permissions for users to reduce the risk of exposure.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback