# CVE-2026-128073: gosaml2: Unauthenticated panic decrypting an EncryptedAssertion with a short or empty CipherValue


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-5hj8-q7fv-qrj6

## What is CVE-2026-128073?

CVE-2026-128073 is a high-severity vulnerability in russellhaering gosaml2, published on 17 Nov 2026. 

### Official description

gosaml2 is a Pure Go implementation of SAML 2.0. Prior to 0.12.0, ValidateEncodedResponse() calls decryptAssertions() on an EncryptedAssertion before signature or content validation completes, and EncryptedAssertion.DecryptBytes() in types/encrypted_assertion.go slices decoded ciphertext without first validating the required nonce or initialization-vector length. A CipherValue shorter than the 12-byte AES-GCM nonce causes a slice-bounds panic, and an empty AES-CBC CipherValue passes the modulo block-size check before causing a slice-bounds panic at the 16-byte initialization-vector split. An attacker needs only the service provider's public certificate to wrap a symmetric key, and no valid identity-provider signature or relationship is required. The unrecovered panic can terminate the request goroutine or the service process. This issue is fixed in version 0.12.0.

Weakness: CWE-248 (Uncaught Exception), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-128073 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128073 is a high-severity vulnerability in russellhaering gosaml2, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128073 in the wild and no public exploit code.

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

## Sources

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

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