# CVE-2026-10579: Picketlink-federation: auth bypass in picketlink saml unsolicited-response

> An unauthenticated attacker can forge SAML assertions to bypass authentication and access restricted data or operations in JBoss EAP.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-wcq4-9xxp-5px6

## What is CVE-2026-10579?

CVE-2026-10579 is a critical authentication bypass vulnerability in Red Hat JBoss Enterprise Application Platform 7, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in Picketlink Federation SAML; the unsolcited response handler would accept forged assertions with no verification or validation, permitting an unauthed attacker to authenticate as any principal in any role. This could lead to information disclosure, access to restricted operations, or other flaws.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

Apply the vendor's patch.

## Is CVE-2026-10579 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10579 is a critical authentication bypass vulnerability in Red Hat JBoss Enterprise Application Platform 7, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10579 in the wild and no public exploit code.

Affected product: Red Hat JBoss Enterprise Application Platform 7. 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-10579/ (Markdown: https://insights.sbomify.com/CVE-2026-10579/index.md)
```

## Sources

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

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