ZeroDay Findings
Sign inSign up

Findings

RUSTSEC-2026-0367

Insecure Preservation of SUID/SGID Bits during ZIP Extraction Leading to Potential Privilege Escalation

Published Oct 9, 2026 · corrected/updated Oct 16, 2026 · evidence confidence medium

The crate preserves privileged Unix permission bits (SUID, SGID, and sticky bits) from ZIP during extraction, instead of masking them to safe permission bits. If a privileged process (for example, in an installer, CI/CD pipeline, or container build) extracts an attacker-controlled ZIP archive using or the stream extraction API, files can be created as setuid-root or setgid. This behavior allows the creation of SUID/SGID files during extraction, which can lead to local privilege escalation depending on the execution environment. For further details see: https://github.com/zip-rs/zip2/security/advisories/GHSA-vv5m-jxxh-4627

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

RUSTSEC-2026-0367 is a high public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: zip (0.0.0-0 → 9.0.0). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: CVSS 7.3. It is not currently listed in the CISA Known Exploited catalog. Sources contributing to this record: github, osv. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.

  • Patch and remediation

    No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 9, 2026 · GitHub Advisory Database

    Detected

    The crate preserves privileged Unix permission bits (SUID, SGID, and sticky bits) from ZIP during extraction, instead of masking them to safe permission bits. If a privileged process (for example, in an installer, CI/CD pipeline, or container build) extracts an attacker-controlled ZIP archive using or the stream extraction API, files can be created as setuid-root or setgid. This behavior allows th

  2. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    zip fixed in 9.0.0

  3. Oct 16, 2026 · GitHub Advisory Database

    Fix available

    zip fixed in 9.0.0

  4. Oct 16, 2026 · GitHub Advisory Database

    Updated

    The crate preserves privileged Unix permission bits (SUID, SGID, and sticky bits) from ZIP during extraction, instead of masking them to safe permission bits. If a privileged process (for example, in an installer, CI/CD pipeline, or container build) extracts an attacker-controlled ZIP archive using or the stream extraction API, files can be created as setuid-root or setgid. This behavior allows th

Affected

  • crates.io zip0.0.0-0 → 9.0.0

Sources

References