# CVE-2026-115998: IDOR: User reads and modifies findings from other people's projects


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-5c44-fgrh-f6cp

## What is CVE-2026-115998?

CVE-2026-115998 is a medium-severity vulnerability in CervantesSec cervantes, published on 24 Oct 2026. 

### Official description

IDOR in Cervantes version v1.3-beta could allow an authenticated attacker ca access sensitive findings, proof-of-concept details, credentials, and client information from projects they do not belong to. Additionally, they can modify finding statuses and transfer findings to their own projects, compromising data confidentiality and integrity.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-115998 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115998 is a medium-severity vulnerability in CervantesSec cervantes, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115998 in the wild and no public exploit code.

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

## Sources

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

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