# CVE-2026-123536: OpenAM before 16.1.4 SSRF via Federation Configuration Wizard Metadata URLs


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-49pf-qwcj-84qg, GHSA-rmw3-j353-w9f7

## What is CVE-2026-123536?

CVE-2026-123536 is a medium-severity vulnerability in OpenIdentityPlatform OpenAM, published on 8 Nov 2026. 

### Official description

OpenAM before 16.1.4 contains a server-side request forgery vulnerability that allows administrators, including delegated realm administrators, to make the server fetch arbitrary URLs through federation configuration wizard metadata URLs. Attackers can enter metadata or OpenID Connect discovery URLs pointing to internal hosts or cloud metadata endpoints to probe the internal network and read partial responses.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-123536?


## How do I fix CVE-2026-123536?

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

## Is CVE-2026-123536 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123536 and fix it if it is affected.

What it is: CVE-2026-123536 is a medium-severity vulnerability in OpenIdentityPlatform OpenAM, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123536 in the wild and no public exploit code.

Affected product: OpenIdentityPlatform 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-2026-123536/ (Markdown: https://insights.sbomify.com/CVE-2026-123536/index.md)
```

## Sources

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

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