CryptoApplication · Golang
CVE-2026-46597
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 · uneditedAn incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs.
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 · moderate confidenceA type conversion error in the AES-GCM packet decoder allows attackers to send specially crafted packets that cause the server to panic. The vulnerability stems from an incorrectly placed cast from bytes to int, likely causing an integer overflow or out-of-bounds access when processing malformed input.
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
CryptoApplication
< 0.52.0CVSS 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 golang.org/x/crypto dependencySearch your codebase for imports of golang.org/x/crypto or check go.mod for 'golang.org/x/crypto' entriesAffected if The golang.org/x/crypto package is present in the project dependencies
-
Check installed crypto versionRun 'go list -m golang.org/x/crypto' or inspect go.mod to find the exact version numberAffected if The version is below 0.52.0 (e.g., 0.51.0, 0.50.0, etc.)
-
Verify AES-GCM usage for packet decodingSearch source code for usages of aesgcm.New, cipher.NewGCM, or similar AES-GCM initialization functions that process incoming packetsAffected if The application uses AES-GCM to decrypt or decode packets from network sources
-
Confirm untrusted input processingInspect code paths where AES-GCM decryption occurs on data from network connections, external APIs, or other untrusted sourcesAffected if AES-GCM packets from untrusted or remote sources are being processed
-
Check for runtime panic handlingReview application logs or error handling for panic occurrences related to 'crypto/aes' or 'crypto/gcm' during packet processingAffected if Runtime panics occur during AES-GCM packet decryption
The environment is affected if golang.org/x/crypto version is below 0.52.0 AND the application uses AES-GCM to process packets from untrusted network sources.
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.52.0
Update the AES-GCM packet decoder to use proper type conversion and bounds checking. Implement input validation before type casting to ensure values are within expected ranges.
v0.52.0
- Run `go get go.crypto@latest` or `go get [email protected]` to update the Crypto module to the fixed version
- Verify the upgrade was successful by running `go list -m all` to confirm the module version
- Run your project's test suite to ensure the upgrade does not introduce regressions
- Commit the changes to go.mod and go.sum
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Crypto
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46597 — 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-46597 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