Hayroo path traversal in product image deletion
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
The hasan-py Hayroo image deletion function, Product.deleteImages, contains a path traversal flaw. An attacker can reach it remotely over the network with a low-privilege login and use it to manipulate file paths during image deletion.
Written by a model
Original description
A vulnerability was identified in hasan-py Hayroo up to fd0fbe763153f72bfaa04ed1e1e4a1bb6f7c61df. Affected by this issue is the function Product.deleteImages of the file server/controller/products.js of the component Image Deletion Handler. The manipulation leads to path traversal. The attack may be initiated remotely. The exploit is publicly available and might be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The identifier of the patch is 9714947bb43ec8559287aa3962b70a7be8c8d6b1. It is recommended to apply a patch to fix this issue.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133486 (hasan-py Hayroo Image Deletion products.js Product.deleteImages path traversal), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133486 (entry last updated 2026-11-20):
Affected:
- hasan-py Hayroo: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133486 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133486 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/hasan-py/Hayroo/pull/52
- https://github.com/hasan-py/Hayroo/commit/9714947bb43ec8559287aa3962b70a7be8c8d6b1
- https://vuldb.com/vuln/440904
- https://vuldb.com/vuln/440904/cti
- https://vuldb.com/cve/CVE-2026-133486
- https://vuldb.com/submit/1049321
- https://github.com/hasan-py/Hayroo/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133486
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133486"}.Affected versions
- hasan-py HayrooVersion range not reported
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 10
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133486 |
| Record | NVD · CVE-2026-133486 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · hasan-py/Hayroo · Issue #51 |
| Other links 7 | |
| Advisory | VulDB · Advisory #440904 |
| Advisory | VulDB · Threat intelligence #440904 |
| Advisory | VulDB · CVE-2026-133486 record |
| Advisory | VulDB · Submission #1049321 |
| Patch | GitHub · hasan-py/Hayroo · Pull request #52 |
| Patch | GitHub · hasan-py/Hayroo · Commit 9714947b |
| Repository | GitHub · hasan-py/Hayroo · Repository |
Related
- CVE-2026-133501Gladys Assistant Backup Restore gateway.downloadBackup.js path traversal
- CVE-2026-126054Path Traversal in Dataform, BigQuery Studio and Colab Enterprise allows Cross-Tenant File Read and Write
- CVE-2026-77355isomorphic-git: NTFS .git::$INDEX_ALLOCATION alias bypass writes into the active gitdir
- CVE-2026-77309AIT-GUI route chain allows unauthenticated Python execution in server process
- CVE-2026-134167devpi-web before 5.2.0 Unauthenticated Path Traversal via +doc Route
- CVE-2026-54065NukeViet CMS: Path Traversal to Arbitrary File Deletion in Edit Comment Function
No corrections so far. Something wrong on this page? Report an error.