# CVE-2023-44273: GO-2023-2096 - Signature malleability in github.com/consensys/gnark-crypto

Source: https://junglewise.ai/threats/cve-2023-44273-duplicate-advisory-consensys-gnark-crypto-allows-signature  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-10-30  
License: CC BY 4.0 with a link back

CVE-2023-44273 · Severity: low · CVSS 3.1 · Published 2025-10-30

Gnark-crypto doesn't range check input values during ECDSA and EdDSA deserialization in github.com/consensys/gnark-crypto

Technologies: [github.com/Consensys/gnark-crypto (Go)](https://junglewise.ai/threats/technologies/github-com-consensys-gnark-crypto). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2023-44273 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2023-44273 being exploited in the wild.

**How severe is CVE-2023-44273?** Low severity, with a CVSS score of 3.1, published 30 October 2025.

**Which products and versions are affected?** github.com/Consensys/gnark-crypto (Go) SEMVER:introduced=0,fixed=0.12.0.

**Is there a fix for CVE-2023-44273?** Yes. github.com/Consensys/gnark-crypto (Go): upgrade to 0.12.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2023-44273?** Check whether you run github.com/Consensys/gnark-crypto (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/Consensys/gnark-crypto (Go): upgrade to 0.12.0 or later

  ```sh
  go get github.com/Consensys/gnark-crypto@v0.12.0
  ```


## Affected products

- github.com/Consensys/gnark-crypto (Go) SEMVER:introduced=0,fixed=0.12.0

## Identifiers

- CVE-2023-44273
- GHSA-9xfq-8j3r-xp5g
- GHSA-fr8m-434r-g3xp
- GO-2023-2096
- GO-2025-4027

## Related threats

- [GO-2025-4087 - Unchecked memory allocation during vector deserialization in github.com/consensys/gnark-crypto](https://junglewise.ai/threats/go-2025-4087-unchecked-memory-allocation-during-vector-deserialization-980b0170)
- [gnark-crypto allows unchecked memory allocation during vector deserialization](https://junglewise.ai/threats/gnark-crypto-allows-unchecked-memory-allocation-during-vector-a494c11d)
- [GO-2023-2101 - Incorrect exponentiation results in github.com/consensys/gnark-crypto](https://junglewise.ai/threats/go-2023-2101-incorrect-exponentiation-results-in-github-com-consensys-439a60d2)
- [gnark-crypto's exponentiation in the pairing target group GT using GLV can give incorrect results](https://junglewise.ai/threats/gnark-crypto-s-exponentiation-in-the-pairing-target-group-gt-using-glv-6f1a4bb3)