# CVE-2026-116255: PGYER codefever URI Sanitizer doc.php _detail path traversal


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-6c57-xg7f-f8g9

## What is CVE-2026-116255?

CVE-2026-116255 is a medium-severity vulnerability in PGYER codefever, published on 26 Oct 2026. 

### Official description

A vulnerability has been found in PGYER codefever up to 0c35e60f006f9d558cc33a159baf110659351990. Affected is the function _detail of the file application/controllers/doc.php of the component URI Sanitizer. The manipulation of the argument uri_string leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed to the public and may 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 e4433eee96883a222403854e8ac38b3146774a07. Applying a patch is the recommended action to fix this issue.

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

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


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

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

## Is CVE-2026-116255 being exploited?

There is no known exploitation of CVE-2026-116255 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116255 is a medium-severity vulnerability in PGYER codefever, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116255 in the wild and no public exploit code.

Affected product: PGYER codefever. 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-116255/ (Markdown: https://insights.sbomify.com/CVE-2026-116255/index.md)
```

## Sources

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

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