# CVE-2026-97181: ezGlobal｜GPM LIGHT - Sensitive Data Exposure

> Unauthenticated attackers can access system logs in ezGlobal GPM LIGHT, exposing sensitive information.

- **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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-4266-g8jg-m68m

## What is CVE-2026-97181?

CVE-2026-97181 is a medium-severity vulnerability in ezGlobal GPM LIGHT, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GPM LIGHT developed by ezGlobal has a Sensitive Data Exposure vulnerability. Unauthenticated remote attackers can directly access system logs.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2026-97181 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97181 is a medium-severity vulnerability in ezGlobal GPM LIGHT, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97181 in the wild and no public exploit code.

Affected product: ezGlobal GPM LIGHT. 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-97181/ (Markdown: https://insights.sbomify.com/CVE-2026-97181/index.md)
```

## Sources

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

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