# CVE-2025-8662: Other in OpenAM

> A tampered request can cause OpenAM to malfunction as a SAML Identity Provider, leading to service disruption.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-h8xh-grcg-wm4h

## What is CVE-2025-8662?

CVE-2025-8662 is a low-severity vulnerability in OpenAM, published on 2 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenAM (OpenAM Consortium Edition) contains a vulnerability that may cause it to malfunction as a SAML IdP due to a tampered request.This issue affects OpenAM: from 14.0.0 through 14.0.1.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-8662?

It affects 1 product.


Products: Openam Openam.

## How do I fix CVE-2025-8662?

No fix has been published for CVE-2025-8662 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8662 being exploited?

There is no known exploitation of CVE-2025-8662 in the wild and no public exploit code.

## Other vulnerabilities in OpenAM

- [CVE-2023-22320](https://insights.sbomify.com/CVE-2023-22320/): Path traversal in OpenAM Web Policy Agent (OpenAM Consortium Edition) (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8662 and fix it if it is affected.

What it is: CVE-2025-8662 is a low-severity vulnerability in OpenAM, published on 2 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8662 in the wild and no public exploit code.

Affected product: OpenAM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8662/ (Markdown: https://insights.sbomify.com/CVE-2025-8662/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8662
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8662
- OSV: https://osv.dev/vulnerability/CVE-2025-8662

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8662/
Summaries are generated and may contain mistakes; the official description above is the record.