NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
LOW severity

CVE-2025-1396 — org.wso2.carbon.identity.…

LOWFix: wso2/carbon-identity-framework@5d5d592

CVE-2025-1396 is a low-severity (CVSS 3.7) CWE-203 vulnerability in org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

WSO2's Input Validation Management Service contains Observable Discrepancy when Multi-Attribute Login is enabled

Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • 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-1396.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk
0.00%0.25%0.50%0.75%0.0%0.3%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt

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

A username enumeration vulnerability exists in multiple WSO2 products when Multi-Attribute Login is enabled. In this configuration, the system returns a distinct "User does not exist" error message to the login form, regardless of the validate_username setting. This behavior allows malicious actors to determine which usernames exist in the system based on observable discrepancies in the application's responses.

Exploitation of this vulnerability could aid in brute-force attacks, targeted phishing campaigns, or other social engineering techniques by confirming the validity of user identifiers within the system.

There is a fix available in version 7.8.491, however it has not been published to the Maven registry.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
☕Mavenorg.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgtall versionsNo fix

Affected Products

3 products · 6 configurations
Application
identity serverwso2
4 versions
5.10.05.11.06.0.06.1.0
Application
identity server as key managerwso2
1 version
5.10.0
Application
open banking iamwso2
1 version
2.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgt for CVE-2025-1396. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    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

A username enumeration vulnerability exists in multiple WSO2 products when Multi-Attribute Login is enabled. In this configuration, the system returns a distinct "User does not exist" error message to the login form, regardless of the validate_username setting. This behavior allows malicious actors to determine which usernames exist in the system based on observable discrepancies in the application's responses. Exploitation of this vulnerability could aid in brute-force attacks, targeted phishing campaigns, or other social engineering techniques by confirming the validity of user identifiers
O3 Security · Impact-Aware SCA

Is CVE-2025-1396 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2025-1396: org.wso2.carbon.identity.… (Low 3.7)