CVE-2025-27625: Medium severity Jenkins Jenkins vulnerability

Published Mar 5, 2025
·
Updated

In Jenkins 2.499 and earlier, LTS 2.492.1 and earlier, redirects starting with backslash (\) characters are considered safe, allowing attackers to perform phishing attacks by having users go to a Jenkins URL that will forward them to a different site, because browsers interpret these characters as part of scheme-relative redirects.

Other sources

Various features in Jenkins redirect users to partially user-controlled URLs inside Jenkins. To prevent open redirect vulnerabilities, Jenkins limits redirections to safe URLs (neither absolute nor scheme-relative/network-path reference).

In Jenkins 2.499 and earlier, LTS 2.492.1 and earlier, redirects starting with backslash (\) characters are considered safe.

This allows attackers to perform phishing attacks by having users go to a Jenkins URL that will forward them to a different site, because browsers interpret these characters as part of scheme-relative redirects.

Jenkins 2.500, LTS 2.492.2 considers redirects to URLs starting with backslash (\) characters to be unsafe, rejecting such redirects.

GitHub

Affected Software

6 affected componentsFixes available
Jenkins Jenkins<2.500
Jenkins Jenkins LTS<2.492.2
maven/org.jenkins-ci.main:jenkins-core>=2.493<2.500
2.500
maven/org.jenkins-ci.main:jenkins-core<2.492.2
2.492.2
Jenkins Jenkins<2.492.2
Jenkins Jenkins<2.500

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.jenkins-ci.main:jenkins-core to a version that resolves this vulnerability.

    Fixed in 2.500
  2. Upgrade

    Upgrade maven/org.jenkins-ci.main:jenkins-core to a version that resolves this vulnerability.

    Fixed in 2.492.2

Event History

Mar 5, 2025
CVE Published
via MITRE·10:33 PM
Data Sourced
via MITRE·10:33 PM
Description
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
Affected Software
Mar 6, 2025
Advisory Published
via GitHub·12:31 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-27625?

CVE-2025-27625 is considered a medium severity vulnerability due to its potential to facilitate phishing attacks.

2

How do I fix CVE-2025-27625?

To fix CVE-2025-27625, upgrade Jenkins to version 2.500 or later, or Jenkins LTS to version 2.492.2 or later.

3

What are the risks associated with CVE-2025-27625?

The risks associated with CVE-2025-27625 include the possibility of users being redirected to malicious sites without their knowledge.

4

Who is affected by CVE-2025-27625?

CVE-2025-27625 affects users of Jenkins 2.499 and earlier, as well as Jenkins LTS 2.492.1 and earlier.

5

What are the symptoms of exploitation for CVE-2025-27625?

Exploitation of CVE-2025-27625 may manifest as unexpected redirects to external sites when navigating within Jenkins.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203