# CVE-2026-120503: EchoHS GeekezBrowser Public API status information disclosure


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/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:** 2 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-hvgv-gvfr-8qpm

## What is CVE-2026-120503?

CVE-2026-120503 is a medium-severity vulnerability in EchoHS GeekezBrowser, published on 2 Nov 2026. 

### Official description

A vulnerability was detected in EchoHS GeekezBrowser up to 1.7.2/1.8.0. This affects an unknown part of the file /api/status of the component Public API. The manipulation results in information disclosure. The attack requires a local approach. The exploit is now public and may be used. Upgrading to version 1.8.1 is able to mitigate this issue. The patch is identified as 9317a89aa0fd2715d9c2bd27bdbb52b5d228dd9e. Upgrading the affected component is recommended.

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

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


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

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

## Is CVE-2026-120503 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120503 is a medium-severity vulnerability in EchoHS GeekezBrowser, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120503 in the wild and no public exploit code.

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

## Sources

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

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