How severe is GHSA-fhrq-3gmx-p879?

No CVSS score has been assigned to GHSA-fhrq-3gmx-p879 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fhrq-3gmx-p879?

GHSA-fhrq-3gmx-p879 affects the following packages: org.openidentityplatform.openam:openam-federation-library (Maven). Ecosystems affected: Maven.

How do I fix GHSA-fhrq-3gmx-p879?

Update org.openidentityplatform.openam:openam-federation-library to 16.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fhrq-3gmx-p879 is resolved across your whole dependency graph.

How do I detect GHSA-fhrq-3gmx-p879 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.openidentityplatform.openam:openam-federation-library, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fhrq-3gmx-p879 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-fhrq-3gmx-p879?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fhrq-3gmx-p879 can be triaged on real exposure rather than presence alone.

Is GHSA-fhrq-3gmx-p879 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fhrq-3gmx-p879 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fhrq-3gmx-p879?

GHSA-fhrq-3gmx-p879 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fhrq-3gmx-p879?

GHSA-fhrq-3gmx-p879 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-fhrq-3gmx-p879 published, and has it been updated?

GHSA-fhrq-3gmx-p879 was published on June 22, 2026 and was last updated on June 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-fhrq-3gmx-p879 — openam-federation-library

GHSA-fhrq-3gmx-p879 is a Cross-site Scripting (XSS) vulnerability in org.openidentityplatform.openam:openam-federation-library. A fix is available for org.openidentityplatform.openam:openam-federation-library — see the affected versions and patch details below.

OpenAM SAML2 Cluster Cookie-Hash-Redirect Path has Pre-authentication Reflected XSS via `FSUtils.postToTarget`

Also known asCVE-2026-44793

Published

Jun 22, 2026

Updated

Jun 22, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 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 GHSA-fhrq-3gmx-p879.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕org.openidentityplatform.openam:openam-federation-library

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

Summary

Certain federation endpoints do not consistently apply output encoding when rendering user-supplied parameters into HTML responses. Under a non-default configuration used in some clustered deployments, this inconsistency can result in reflected XSS in the OpenAM origin without authentication.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.openidentityplatform.openam:openam-federation-library`	all versions	16.1.1`org.openidentityplatform.openam:openam-federation-library:16.1.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.openidentityplatform.openam:openam-federation-library, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.openidentityplatform.openam:openam-federation-library to 16.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fhrq-3gmx-p879 is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fhrq-3gmx-p879 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-fhrq-3gmx-p879. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Certain federation endpoints do not consistently apply output encoding when rendering user-supplied parameters into HTML responses. Under a non-default configuration used in some clustered deployments, this inconsistency can result in reflected XSS in the OpenAM origin without authentication.

O3 Security · Impact-Aware SCA

Is GHSA-fhrq-3gmx-p879 in your dependencies?

O3 Security finds GHSA-fhrq-3gmx-p879 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works