Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

ntru-rs has unsound FFI: Wrong API usage causes write past allocated area

GHSA-fq33-vmhv-48xh

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io ntru

    Affected
    >= 0.4.3, <= 0.5.6
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

The following usage causes undefined behavior. When compiled with debug assertions, the code above will trigger a attempt to subtract with overflow panic before UB occurs. Other mistakes (e.g. using EncParams from a different key) may always trigger UB. Likely, older versions of this crate are also affected, but have not been tested.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-fq33-vmhv-48xh

Agent brief

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

# Patch Next advisory brief: GHSA-fq33-vmhv-48xh

Advisory: ntru-rs has unsound FFI: Wrong API usage causes write past allocated area
IDs: GHSA-fq33-vmhv-48xh
Record: https://patchnext.com/advisories/ghsa-fq33-vmhv-48xh (revision 1, source checked 26 Oct 2026, 15:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
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 ntru: affected >= 0.4.3, <= 0.5.6

## Suggested inspection (read-only)
- crates.io ntru: 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 ntru.
- 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-fq33-vmhv-48xh (GitHub-reviewed advisory GHSA-fq33-vmhv-48xh lists affected ranges: crates.io ntru >=0.4.3 <=0.5.6)

Commands are suggestions: review each one before running it.

Loading voting…