CVE-2026-1229
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 · uneditedThe CombinedMult function in the CIRCL ecc/p384 package (secp384r1 curve) produces an incorrect value for specific inputs. The issue is fixed by using complete addition formulas. ECDH and ECDSA signing relying on this curve are not affected. The bug was fixed in v1.6.3 https://github.com/cloudflare/circl/releases/tag/v1.6.3 .
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 confidenceThe CombinedMult function in CIRCL's ecc/p384 package (secp384r1 curve) produces incorrect output values for specific inputs due to incomplete addition formulas. This affects point multiplication operations on the secp384r1 curve, though ECDH and ECDSA signing operations are explicitly not impacted by this vulnerability.
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< 1.6.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 CIRCL library usageSearch your codebase for 'circl' imports or check your go.mod file for 'github.com/cloudflare/circl' dependencyAffected if The circl library is present as a dependency
-
Check CIRCL versionRun 'go list -m github.com/cloudflare/circl' or inspect the version listed in your go.sum fileAffected if The version is lower than v1.6.3 (e.g., v1.6.2, v1.6.1, v1.6.0, etc.)
-
Identify CombinedMult usageSearch your codebase for calls to 'CombinedMult' function, typically in the pattern 'circl/ecc/p384'. Example search: grep -r 'CombinedMult' --include='*.go'Affected if Code calls CombinedMult from the ecc/p384 package
-
Verify secp384r1 curve usageInspect the CombinedMult calls to confirm they use the secp384r1 curve (the p384 curve). Check the context or parameters passed to CombinedMultAffected if The CombinedMult function is used with secp384r1 (secp384r1) curve parameters
-
Check for point multiplication operationsReview code paths that invoke CombinedMult to determine if point multiplication operations are performedAffected if Point multiplication operations using CombinedMult are executed in your application
You are affected if your application uses the CIRCL library version lower than v1.6.3 and executes point multiplication operations via the CombinedMult function with the secp384r1 curve.
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 · scoped1.6.3
Update CIRCL library to v1.6.3 or later to obtain the corrected complete addition formulas. Given the critical CVSS score (9.8), prioritize this update in systems using the affected CombinedMult function for secp384r1 operations.
v1.6.3 (github.com/cloudflare/circl)
- Identify all codebases and dependencies that use the Circl library with version lower than 1.6.3
- Update the circl dependency in your go.mod or dependency management file to version 1.6.3 or later (e.g., go get github.com/cloudflare/[email protected])
- Run go mod tidy to clean up dependencies
- Rebuild the application to ensure the new library version is incorporated
- Redeploy the updated application to all affected environments
- Verify the fix by testing the CombinedMult function with the specific inputs that previously produced incorrect values
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1229 — 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-1229 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