# CVE-2026-22539: INFORMATION DISCLOSURE VIA CURL REQUESTS (OCPP)

> Unauthenticated attackers can obtain charger information via OCPP protocol requests due to missing authentication in service interactions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-5c9g-c5m4-vmrj

## What is CVE-2026-22539?

CVE-2026-22539 is a medium-severity vulnerability in EFACEC QC 60/90/120, published on 7 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

As the service interaction is performed without authentication, an attacker with some knowledge of the protocol could obtain information about the charger via OCPP v1.6.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2026-22539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22539 is a medium-severity vulnerability in EFACEC QC 60/90/120, published on 7 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22539 in the wild and no public exploit code.

Affected product: EFACEC QC 60/90/120. 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-22539/ (Markdown: https://insights.sbomify.com/CVE-2026-22539/index.md)
```

## Sources

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

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