# CVE-2026-116046: eventcatalog sdk Custom Documentation Helpers custom-docs.ts rmCustomDoc path traversal


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-wcv6-jfg6-vfc5

## What is CVE-2026-116046?

CVE-2026-116046 is a medium-severity vulnerability in eventcatalog sdk, published on 25 Oct 2026. 

### Official description

A flaw has been found in eventcatalog sdk up to 2.29.0. This vulnerability affects the function getCustomDoc/writeCustomDoc/rmCustomDoc of the file packages/sdk/src/custom-docs.ts of the component Custom Documentation Helpers. This manipulation of the argument options.path causes path traversal. It is possible to launch the attack on the local host. Upgrading to version 2.30.0 is able to resolve this issue. Patch name: a4f072a03f440d58230092e88d8b4893f4c6d6ca. The affected component should be upgraded. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

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

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


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

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

## Is CVE-2026-116046 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116046 is a medium-severity vulnerability in eventcatalog sdk, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116046 in the wild and no public exploit code.

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

## Sources

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

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