PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

New CVE Detected

CVE-2026-90774 – Path Traversal / Arbitrary File Write – rustypaste before 0.18.1

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

Summary

CVE-2026-90774 is a path traversal vulnerability (CWE-22) in rustypaste, a minimal self-hosted file upload/pastebin service written in Rust. Versions before 0.18.1 validate the destination path before applying an optional, attacker-supplied custom filename HTTP header, allowing the header value to bypass the directory-escape checks that are supposed to confine uploads to the configured storage directory. The flaw is remotely exploitable without authentication and carries a high severity rating.

Technical details

  • Root cause: rustypaste performs its "is this path inside the upload directory" validation on the initial/expected destination path, then separately applies the client-controlled filename header to rename/relocate the stored file. Because the header value is applied after the safety check, it is never itself validated against the base directory.
  • Trigger condition: An attacker sends a file upload request (e.g., via curl -F "[email protected]" -H "filename:../../override.txt") with a crafted filename header containing directory-traversal sequences (../).
  • Attack vector: Network — the vulnerability is exploitable via a standard, unauthenticated HTTP upload request to any rustypaste instance that has the filename-override feature enabled (as it is by default).
  • Impact: The crafted filename allows the resulting file to be written outside the intended upload directory, enabling arbitrary file write/overwrite on the host filesystem. Depending on deployment (e.g., web-root paths, cron directories, configuration files reachable by the process), this can lead to data corruption, service disruption, or further compromise such as planting web-accessible content or overwriting sensitive files.

Affected software

  • Product: rustypaste (vendor: orhun)
  • Affected versions: All versions prior to 0.18.1
  • Fixed version: 0.18.1 and later

Severity

  • CVSS v3.1 Base Score: 7.5 (High)
  • CVSS v3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
  • (A CVSS v4.0 score of 8.7, High, is also associated with this CVE: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N)

Mitigation and recommended actions

  • Immediate: Upgrade rustypaste to version 0.18.1 or later, which routes header-supplied filenames through the application’s safe path-joining logic to ensure the final path stays within the configured upload directory.
  • If unable to patch immediately:
    • Disable or restrict the custom filename override feature at the reverse proxy or application configuration layer if such a control is available in your deployment.
    • Restrict network access to the rustypaste upload endpoint (e.g., via IP allow-listing, VPN, or authentication at a reverse proxy) to reduce exposure to untrusted clients.
    • Run the rustypaste process with a dedicated, low-privilege OS account and minimal filesystem permissions so that any unauthorized write is contained to a non-sensitive location.
    • Monitor upload directories and adjacent paths for unexpected files or modifications as a compensating detective control until the upgrade is applied.

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