CVE-2025-47889: In Jenkins WSO2 Oauth Plugin 1.0 and earlier, authentication claims are accepted without validation by the "WS

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

wso2 oauth: upgrade to newer than 1.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-47889 being exploited?

CVE-2025-47889 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-47889 affect?

CVE-2025-47889 affects wso2 oauth. Severity is critical (CVSS 9.8). In Jenkins WSO2 Oauth Plugin 1.0 and earlier, authentication claims are accepted without validation by the "WSO2 Oauth" security realm, allowing unauthenticated attackers to log in to controllers using this security realm using any username

Q: How urgent is CVE-2025-47889?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2025-47889 is a critical-severity flaw (CVSS 9.8) affecting wso2 oauth. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In Jenkins WSO2 Oauth Plugin 1.0 and earlier, authentication claims are accepted without validation by the "WSO2 Oauth" security realm, allowing unauthenticated attackers to log in to controllers using this security realm using any username and any password, including usernames that do not exist.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 49%)
CISA exploited list	No
Weakness	CWE-287
Published	2025-05-14
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-05-14 21:15 UTCPublished CVE record published
2026-06-17 09:28 UTCUpdated Record last modified

jenkins wso2 oauth UPGRADE

Affected: <= 1.0

Fixed in: newer than 1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wso2-oauth || rpm -q wso2-oauth || wso2-oauth --version

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

sudo apt update && sudo apt install --only-upgrade wso2-oauth

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wso2-oauth

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-47889?

wso2 oauth: upgrade to newer than 1.0. Exact commands for each OS are on this page.

Is CVE-2025-47889 being exploited?

CVE-2025-47889 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-47889 affect?

CVE-2025-47889 affects wso2 oauth. Severity is critical (CVSS 9.8). In Jenkins WSO2 Oauth Plugin 1.0 and earlier, authentication claims are accepted without validation by the "WSO2 Oauth" security realm, allowing unauthenticated attackers to log in to controllers using this security realm using any username

How urgent is CVE-2025-47889?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Jenkins vulnerabilities

References

← Back to latest CVEs