# CVE-2026-9506: Path Traversal Vulnerability in Bagisto

> Unauthenticated attackers can read arbitrary sensitive files on the server via path traversal in Bagisto's ImageCacheController.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-qhcg-rw5x-vg94

## What is CVE-2026-9506?

CVE-2026-9506 is a high-severity path traversal vulnerability in Webkul Bagisto, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability exists in Bagisto due to improper validation of user-supplied input in the ImageCacheController component. An unauthenticated remote attacker could exploit this vulnerability by sending crafted path traversal sequences through the filename parameter to access arbitrary files outside the intended directory on the targeted system.

Successful exploitation of this vulnerability could allow an attacker to read arbitrary sensitive files on the targeted system.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-9506?


## How do I fix CVE-2026-9506?

No fix has been published for CVE-2026-9506 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9506 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9506 exists.

Public exploit code:

- Bagisto <= 2.4.1 - Unauthenticated Arbitrary File Read (nuclei): http/cves/2026/CVE-2026-9506.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9506 and fix it if it is affected.

What it is: CVE-2026-9506 is a high-severity path traversal vulnerability in Webkul Bagisto, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9506 exists.

Affected product: Webkul Bagisto. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9506/ (Markdown: https://insights.sbomify.com/CVE-2026-9506/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9506
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9506
- OSV: https://osv.dev/vulnerability/CVE-2026-9506

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9506/
Summaries are generated and may contain mistakes; the official description above is the record.