SM2-PKE has Unchecked AffinePoint Decoding (unwrap) in decrypt()

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-22699: 0.44% estimated exploitation activity in the next 30 days; percentile 37.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A denial-of-service vulnerability exists in the SM2 PKE decryption path where an invalid elliptic-curve point (C1) is decoded and the resulting value is unwrapped without checking. Specifically, AffinePoint::fromencodedpoint(&encodedc1) may return a None/CtOption::None when the supplied coordinates are syntactically valid but do not lie on the SM2 curve. The calling code previously used .unwrap(), causing a panic when presented with such input. Affected Component / Versions - File: src/pke/decrypting.rs - Function: internal decrypt() (invoked by DecryptingKey::decrypt methods) - Affected releases: - sm2 0.14.0-rc.0 (https://crates.io/crates/sm2/0.14.0-rc.0) - sm2 0.14.0-pre.0 (https://crates.io/crates/sm2/0.14.0-pre.0) Details The library decodes the C1 field (an EC point) as an EncodedPoint and then converts it to an AffinePoint using AffinePoint::fromencodedpoint(&encodedc1). That conversion returns a CtOption<AffinePoint (or an Option equivalent) which will indicate…

Published by the source

9 Jan 2026, 22:35 UTC

Last modified by the source

11 Jan 2026, 14:56 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-78p6-6878-8mj6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-22699

Advisory: SM2-PKE has Unchecked AffinePoint Decoding (unwrap) in decrypt()
IDs: CVE-2026-22699, GHSA-78p6-6878-8mj6
Record: https://patchnext.com/advisories/cve-2026-22699 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io sm2: affected >= 0.14.0-pre.0, <= 0.14.0-rc.4

## Suggested inspection (read-only)
- crates.io sm2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sm2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-78p6-6878-8mj6 (GitHub-reviewed advisory GHSA-78p6-6878-8mj6 lists affected ranges: crates.io sm2 >=0.14.0-pre.0 <=0.14.0-rc.4)

Commands are suggestions: review each one before running it.