Summary
Janssen Config API returns results without scope verification
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
The user can potentially fork and build the config api and patch it in their system following the commit here https://github.com/JanssenProject/jans/commit/92eea4d4637f1cae16ad2f07b2c16378ff3fc5f1
References
Are there any links users can visit to find out more?
https://github.com/JanssenProject/jans/issues/11575
https://github.com/JanssenProject/jans/commit/92eea4d4637f1cae16ad2f07b2c16378ff3fc5f1
Impact
What kind of vulnerability is it? Who is impacted?
The configAPI is an internal service and hence should never be exposed to the internet. With that said, this is a serious vulnerability that has a large internal surface attack area that exposes all sorts of information from the IDP including clients, users, scripts ..etc.
This affects all users of Janssen <1.8.0 and Gluu Flex <5.8.0
The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Has the problem been patched? What versions should users upgrade to?
All users are advised to upgrade immediately to 1.8.0 for Janssen users and 5.8.0 For Flex users.
Frequently Asked Questions
- What is CVE-2025-53003? CVE-2025-53003 is a high-severity improper privilege management vulnerability in io.jans:jans-config-api-server (maven), affecting versions < 1.8.0. It is fixed in 1.8.0. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
- Which versions of io.jans:jans-config-api-server are affected by CVE-2025-53003? io.jans:jans-config-api-server (maven) versions < 1.8.0 is affected.
- Is there a fix for CVE-2025-53003? Yes. CVE-2025-53003 is fixed in 1.8.0. Upgrade to this version or later.
- Is CVE-2025-53003 exploitable, and should I be worried? Whether CVE-2025-53003 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-53003 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-53003? Upgrade
io.jans:jans-config-api-serverto 1.8.0 or later.