Quick answers
- Is CVE-2026-75614 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75614 being exploited in the wild.
- How severe is CVE-2026-75614?
- High severity, with a CVSS score of 8.1, published 5 November 2026.
- Which products and versions are affected?
- ESA ASN1SCC prior to 4.7.0.1.
- Is there a fix for CVE-2026-75614?
- Yes: fixed in 4.7.0.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75614 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-75614?
- Check whether you run ESA ASN1SCC 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
- Fixed in: 4.7.0.1
Technical details
The BitStream_DecodeConstraintWholeNumber function in asn1crt_encoding.c fails to reject out-of-range integer values when the valid range is not a power of two. Generated decoders for variable-length structures (SEQUENCE OF, OCTET STRING, BIT STRING, and strings) use this unvalidated value as a loop or copy length, enabling a heap or stack buffer overflow. The vulnerability affects uPER and ACN format decoders and requires providing crafted untrusted data to the decoder.
Affected products
- ESA ASN1SCC prior to 4.7.0.1
Timeline
- 2026-11-05: disclosed