Skip to main content
Menu
CVEs

falcon-rust signature soundness flaw in discrete-Gaussian sampler

CVE-2026-77382EUVD-2026-130395Published November 19, 2026, updated

5.9MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 0.2.0
Who is exposed
Not reported

Summary

The falcon-rust Rust implementation of the Falcon post-quantum signature scheme has a discrete-Gaussian sampler with too little numeric precision, which falls short of what Falcon requires. An attacker can reach the flaw remotely, without logging in or any user action, but it is a cryptographic-soundness defect and no practical key-recovery attack has been demonstrated.

Written by a model

Original description

falcon-rust is a Rust implementation of the Falcon post-quantum signature scheme. Prior to 0.2.0, the discrete-Gaussian sampler in src/samplerz.rs evaluates approx_exp, ber_exp, and sampler_z acceptance probabilities with FixedPoint64 values having only 32 fractional bits. The scaling in approx_exp quantizes its input and limits relative precision to about 2^-33, below Falcon's required bound, causing reference known-answer vectors to diverge and invalidating the proof assumption that secret-dependent signature and key distributions are negligibly close to the ideal discrete Gaussian. This is a cryptographic-soundness defect and no practical key-recovery attack has been demonstrated. This issue is fixed in version 0.2.0.

What to do

Upgrade to a fixed version: 0.2.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77382 (falcon-rust: Discrete-Gaussian sampler runs at 2^-33 precision, far below Falcon's requirement (reference KAT vectors no longer pass)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77382 (entry last updated 2026-11-19):
Affected:
- aszepieniec falcon-rust: fixed in 0.2.0
Fixed versions: 0.2.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77382 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77382 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/aszepieniec/falcon-rust/security/advisories/GHSA-25rm-9wvm-m38v
- https://github.com/aszepieniec/falcon-rust/commit/930d766256f9d67ec9b6d437557286cf47f042ca
- https://github.com/aszepieniec/falcon-rust/commit/bf2cf000e63a9803f7ab1a34f629a5a0e9c49cf6
- https://github.com/aszepieniec/falcon-rust/releases/tag/v0.2.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77382
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77382"}.

Affected versions

cve.now Index

38Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.9/10CVSS 5.9
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 43 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · aszepieniec/falcon-rust · Advisory GHSA-25rm-9wvm-m38v
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77382
RecordNVD · CVE-2026-77382
Other links 3
RepositoryGitHub · aszepieniec/falcon-rust · Commit 930d7662
RepositoryGitHub · aszepieniec/falcon-rust · Commit bf2cf000
RepositoryGitHub · aszepieniec/falcon-rust · Release v0.2.0

Questions about CVE-2026-77382

Is CVE-2026-77382 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-77382?

falcon-rust: before 0.2.0.

Source: cve.now feed data

How do I fix CVE-2026-77382?

Upgrade to a fixed version: 0.2.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.