# CVE-2026-114574: massCodeIO massCode Local HTTP Service index.ts information disclosure


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-336g-g7w5-w9wv

## What is CVE-2026-114574?

CVE-2026-114574 is a medium-severity vulnerability in massCodeIO massCode, published on 21 Oct 2026. 

### Official description

A security vulnerability has been detected in massCodeIO massCode 5.10. Affected is an unknown function of the file src/main/api/index.ts of the component Local HTTP Service. Such manipulation leads to information disclosure. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. The name of the patch is d25d8fa3f5a1e34285c8634f18729650c0c05cda. It is advisable to implement a patch to correct this issue.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-114574 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114574 is a medium-severity vulnerability in massCodeIO massCode, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114574 exists.

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

## Sources

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

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