How severe is CVE-2025-49594?

No CVSS score has been assigned to CVE-2025-49594 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-49594?

CVE-2025-49594 affects the following packages: org.xwiki.contrib.oidc:oidc-authenticator (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-49594?

Update org.xwiki.contrib.oidc:oidc-authenticator to 2.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49594 is resolved across your whole dependency graph.

How do I detect CVE-2025-49594 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.contrib.oidc:oidc-authenticator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-49594 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-49594 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-49594 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-49594?

CVE-2025-49594 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-49594?

CVE-2025-49594 is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-49594 published, and has it been updated?

CVE-2025-49594 was published on October 6, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-49594 — oidc-authenticator

Fix: xwiki-contrib/oidc@d90d717

CVE-2025-49594 is a CWE-285 vulnerability in org.xwiki.contrib.oidc:oidc-authenticator. A fix is available for org.xwiki.contrib.oidc:oidc-authenticator — see the affected versions and patch details below.

XWiki OIDC Authenticator vulnerable to creation of token for any user with just `view` right

Also known asGHSA-f2hf-pfrj-vrm7

Published

Oct 6, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-49594.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.xwiki.contrib.oidc:oidc-authenticator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Anyone with VIEW access to a user profile can create a token for that user. If that XWiki instance is configured to allow token authentication, it allows authentication with any user (since users are very commonly viewable, at least to other registered users).

Patches

Version 2.18.2.

Workarounds

The only workaround is to disable token access.

References

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira XWiki.org
Email us at Security Mailing List

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.contrib.oidc:oidc-authenticator`	≥ 2.17.1&&< 2.18.2	2.18.2`org.xwiki.contrib.oidc:oidc-authenticator:2.18.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.contrib.oidc:oidc-authenticator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.contrib.oidc:oidc-authenticator to 2.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49594 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Anyone with VIEW access to a user profile can create a token for that user. If that XWiki instance is configured to allow token authentication, it allows authentication with any user (since users are very commonly viewable, at least to other registered users). ### Patches Version 2.18.2. ### Workarounds The only workaround is to disable token access. ### References * https://jira.xwiki.org/browse/OIDC-240 * https://github.com/xwiki-contrib/oidc/commit/d90d717172283aaa96bb5bb44e357f910ae64adb ### For more information If you have any questions or comments about this advisory:

O3 Security · Impact-Aware SCA

Is CVE-2025-49594 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works