Skip to main content
Menu
CVEs

CVE

gosaml2 denial of service in encrypted SAML assertion decryption

CVE-2026-128073

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.12.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.12.0.

Published
Last modified
Reference
Last checked
25/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

gosaml2, a Go implementation of SAML 2.0, can be crashed by a specially crafted encrypted assertion that an attacker sends remotely, without logging in. The attacker needs only the service provider's public certificate, and the resulting panic can terminate the request or the whole service process.

Written by a model from the sources below. Verify against them.

Original 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.

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 0.12.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128073 (gosaml2: Unauthenticated panic decrypting an EncryptedAssertion with a short or empty CipherValue), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128073 (entry last updated 2026-11-17):
Affected:
- russellhaering gosaml2: fixed in 0.12.0
Fixed versions: 0.12.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128073 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128073 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/russellhaering/gosaml2/security/advisories/GHSA-5hj8-q7fv-qrj6
- https://github.com/russellhaering/gosaml2/pull/281
- https://github.com/russellhaering/gosaml2/commit/b2bd784b196b21f606faaa6a4eeae929bd75aa20
- https://github.com/russellhaering/gosaml2/releases/tag/v0.12.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128073
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128073"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • russellhaering gosaml2

    fixed in 0.12.0

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-128073

Is CVE-2026-128073 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-128073?

gosaml2: before 0.12.0.Source: cve.now feed data

How do I fix CVE-2026-128073?

Upgrade to a fixed version: 0.12.0.Source: cve.now feed data

More CVEs