Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.8amended

yara-x: Unvalidated deserialization in safe Rules::deserialize allows memory corruption and UB

GHSA-2jx3-ff3v-j7jj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (yara-x 1.19.0), redeploy, then verify what is actually installed.

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 yara-x

    Affected
    <= 1.18.0
    Fixed in
    1.19.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
4.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

[!NOTE] This finding was identified during an agentic unsafe Rust code review performed by Gemini AI, followed by human review and verification. The Issue The crate exports a public safe API Rules::deserialize accepting any generic byte sequence B: AsRef<[u8]. It restores compiled rule structures directly from raw bytes using bincode::serde::decodefromslice. This decoded Rules struct contains internal lookup tables, including subpatterns: Vec<(PatternId, SubPattern), atoms: Vec<SubPatternAtom, and litpool: BStringPool. Subsequent safe operations assume these internal tables satisfy strict structural invariants: - Rules::getsubpattern executes unsafe { self.subpatterns.getunchecked(subpatternid.0 as usize) }. If untrusted serialized bytes contain an atom referencing an out-of-bounds SubPatternId, calling getsubpattern during scanning triggers an out-of-bounds memory read (Undefined Behavior).…

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

    Amended from ghsa record GHSA-2jx3-ff3v-j7jj

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-2jx3-ff3v-j7jj

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-2jx3-ff3v-j7jj

Advisory: yara-x: Unvalidated deserialization in safe `Rules::deserialize` allows memory corruption and UB
IDs: GHSA-2jx3-ff3v-j7jj
Record: https://patchnext.com/advisories/ghsa-2jx3-ff3v-j7jj (revision 3, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: yara-x 1.19.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io yara-x: affected <= 1.18.0; fixed in 1.19.0

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on yara-x.
- 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://osv.dev/vulnerability/GHSA-2jx3-ff3v-j7jj (OSV record GHSA-2jx3-ff3v-j7jj lists affected ranges: crates.io yara-x >=0 <1.19.0 (fixed))
- Verified: https://github.com/advisories/GHSA-2jx3-ff3v-j7jj (GitHub-reviewed advisory GHSA-2jx3-ff3v-j7jj lists affected ranges: crates.io yara-x >=0 <=1.18.0)

Commands are suggestions: review each one before running it.

Loading voting…