Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-49991 – Multi-Tenant Isolation Bypass via Path Traversal – RustFS 1.0.0-beta.4

Be the first to know when new zero-days emerge:

Summary

CVE-2026-49991 is a high-severity path traversal vulnerability (CVSS 8.6) in RustFS, an open-source S3-compatible distributed object storage system built in Rust. The flaw resides in the Snowball auto-extract feature and allows an attacker with only PutObject permission on their own bucket to write arbitrary objects into other tenants’ buckets, completely breaking multi-tenant isolation. There is currently no patch available; organizations running internet-exposed RustFS instances should apply network-level mitigations immediately.

Technical details

  • Root cause: Three chained flaws enable the attack: (1) the normalize_extract_entry_key() function trims slashes but does not sanitize ../ sequences in tar archive entry paths; (2) IAM policy wildcard matching evaluates raw, uncleaned paths, causing a policy like attacker-bucket/* to incorrectly match traversal paths such as attacker-bucket/../victim-bucket/object; (3) filesystem path utilities resolve ../ sequences across bucket boundaries without enforcing bucket containment checks.
  • Trigger conditions: An attacker uploads a specially crafted tar archive containing entries with traversal paths (e.g., ../victim-bucket/evil.txt) and sets the X-Amz-Meta-Snowball-Auto-Extract HTTP header to trigger the auto-extract processing pipeline.
  • Attack vector: Network-accessible (AV:N), low attack complexity (AC:L), no user interaction required (UI:N). The CVSS vector carries a Scope:Changed (S:C) designation, reflecting that a successful exploit impacts resources beyond the attacker’s own bucket.
  • Impact: An attacker can inject or overwrite arbitrary objects in any other tenant’s bucket. This results in full multi-tenant isolation bypass, enabling data corruption, unauthorized data injection, and potential escalation (e.g., overwriting application configuration or script objects stored in victim buckets). Confidentiality impact is rated None; Integrity impact is High.

Affected software

  • RustFS version 1.0.0-beta.4

Severity

  • CVSS v3.1 Base Score: 8.6 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
  • CWE-22: Improper Limitation of a Pathname to a Restricted Directory (Path Traversal)
  • CWE-862: Missing Authorization

Mitigation and recommended actions

  • Patch: No patched version of RustFS is currently available. Monitor the official RustFS security advisories for a fix release.
  • Workarounds:
    • Restrict network access to RustFS endpoints to trusted internal networks only; do not expose RustFS S3 API ports directly to the internet.
    • Disable or block use of the Snowball auto-extract feature (X-Amz-Meta-Snowball-Auto-Extract header) at the reverse proxy or load balancer layer if multi-tenant deployments are in use.
    • Audit IAM policies to apply the principle of least privilege and monitor bucket access logs for unexpected cross-bucket write activity.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge