CVE-2026-123540OpenIdentityPlatform OpenAM improper output encoding
CVE-2026-123540 is a improper output encoding in OpenIdentityPlatform OpenAM, rated low (2.0 on CVSS 4.0).
Why this priority: Low severity, with no exploitation signal.
Published · Updated · NVD status: Awaiting Analysis
What it is
Output is not encoded for where it lands, so data can be read as markup or commands.
How it is reached
An attacker can exploit it over the network, with an administrator account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker act inside a signed-in user's browser session.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade OpenIdentityPlatform OpenAM to 16.1.4 or later.
- Until it is patched, review who holds accounts that can reach it.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
OpenAM before 16.1.4 contains an incomplete output encoding vulnerability that allows a SAML 1.x identity provider to alter attribute values by injecting unencoded content into the service provider auto-submitted form. Attackers controlling a trusted identity provider can craft assertion attribute names or values that reach the target application in modified form, undermining the integrity of received attributes.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Web front ends and single-page apps. The flaw sits between a user's browser and the web application.
- Admin consoles served to a browser. The flaw sits between a user's browser and the web application.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between a user's browser and the web application. An attacker who crosses it can act inside a signed-in user's browser session.
Questions to answer about your own systems
- Where does OpenIdentityPlatform OpenAM run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.