Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9

serde_yml crate is unsound and unmaintained

GHSA-hhw4-xg65-fp2x

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 serde_yml

    Affected
    <= 0.0.12
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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.

Using serdeyml::ser::Serializer.emitter can cause a segmentation fault, which is unsound. The GitHub project for serdeyml was archived after unsoundness issues were raised. If you rely on this crate, it is highly recommended switching to a maintained alternative. Recommended alternatives - serdenorway - Maintained fork of serdeyaml, using unsafe-libyaml-norway - serdeyamlng - Maintained fork of serdeyaml, using unmaintained unsafe-libyaml Incomplete pure Rust alternatives These implementation do not rely on C libyaml. - serdeyaml2 - yaml-peg

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

    Published from ghsa record GHSA-hhw4-xg65-fp2x

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-hhw4-xg65-fp2x

Advisory: serde_yml crate is unsound and unmaintained
IDs: GHSA-hhw4-xg65-fp2x
Record: https://patchnext.com/advisories/ghsa-hhw4-xg65-fp2x (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: Medium (CVSS 6.9)
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 serde_yml: affected <= 0.0.12

## Suggested inspection (read-only)
- crates.io serde_yml: 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 serde_yml.
- 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-hhw4-xg65-fp2x (GitHub-reviewed advisory GHSA-hhw4-xg65-fp2x lists affected ranges: crates.io serde_yml >=0 <=0.0.12)

Commands are suggestions: review each one before running it.

Loading voting…