# CVE-2026-25711: Chargemap chargemap.com Insufficient Session Expiration

> Attackers can hijack sessions or cause denial of service by exploiting predictable WebSocket session identifiers in the Chargemap backend.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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:** 26 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-qc92-5v9v-hh5w

## What is CVE-2026-25711?

CVE-2026-25711 is a medium-severity authentication bypass vulnerability in chargemap.com, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WebSocket backend uses charging station identifiers to uniquely 
associate sessions but allows multiple endpoints to connect using the 
same session identifier. This implementation results in predictable 
session identifiers and enables session hijacking or shadowing, where 
the most recent connection displaces the legitimate charging station and
 receives backend commands intended for that station. This vulnerability
 may allow unauthorized users to authenticate as other users or enable a
 malicious actor to cause a denial-of-service condition by overwhelming 
the backend with valid session requests.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

It affects 1 product.


Products: Chargemap Chargemap.com.

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

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

## Is CVE-2026-25711 being exploited?

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

## Other vulnerabilities in chargemap.com

- [CVE-2026-25851](https://insights.sbomify.com/CVE-2026-25851/): Chargemap chargemap.com Missing Authentication for Critical Function (critical 9.3)
- [CVE-2026-20792](https://insights.sbomify.com/CVE-2026-20792/): Chargemap chargemap.com Improper Restriction of Excessive Authentication Attempts (high 8.7)
- [CVE-2026-20791](https://insights.sbomify.com/CVE-2026-20791/): Chargemap chargemap.com Insufficiently Protected Credentials (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25711 is a medium-severity authentication bypass vulnerability in chargemap.com, published on 26 Feb 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-25711 in the wild and no public exploit code.

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

## Sources

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

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