Go NtlmsspApplication · Microsoft
CVE-2026-32952
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedgo-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn go-ntlmssp versions prior to 0.1.1, a maliciously crafted NTLM challenge message can trigger a slice out of bounds panic in the NTLM parsing logic, causing a denial of service by crashing any Go process using ntlmssp.Negotiator as an HTTP transport.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Go NtlmsspApplication
< 0.1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify go-ntlmssp as a project dependencySearch your project for references to go-ntlmssp in go.mod, go.sum, vendor directory, or import statementsAffected if go-ntlmssp is listed as a dependency
-
Determine installed version of go-ntlmsspRun 'go list -m all' or inspect the version listed next to go-ntlmssp in go.modAffected if The version shown is less than 0.1.1 or no version is specified (indicating an unpatched release)
-
Find usage of ntlmssp.Negotiator as HTTP transportSearch source code files for 'ntlmssp.Negotiator' or '&ntlmssp.Negotiator{}' used with http.Transport's Proxy or TLSClientConfigAffected if The ntlmssp.Negotiator is instantiated and assigned to an HTTP transport
-
Confirm NTLM authentication is actively usedCheck if the application performs NTLM authentication by inspecting HTTP client configuration or runtime network traffic patternsAffected if The application uses NTLM authentication in its HTTP client setup
You are affected if go-ntlmssp version is below 0.1.1 AND ntlmssp.Negotiator is being used as an HTTP transport to handle NTLM authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.1.1
Upgrade go-ntlmssp to version 0.1.1 or later to patch the vulnerability; validate NTLM authentication functionality after the upgrade.
v0.1.1
- Identify the current version of go-ntlmssp in use by checking go.mod or running `go list -m all`
- Run `go get github.com/fullsailor/[email protected]` to upgrade to the fixed version
- Verify the upgrade was successful by running `go list -m github.com/fullsailor/go-ntlmssp`
- Run tests to ensure the upgrade does not break existing functionality
- Rebuild and redeploy the application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Go Ntlmssp
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32952 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data