Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.3

How to Fix CVE-2026-25711: chargemap.com (Bundle Sibling)

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-25711 is a sibling vulnerability in the same vendor advisory as CVE-2026-20791. Apply the same patched build and you close both. The technical detail below is what differs.

⚡ At a glance
Severity7.3 (High)
Actively exploited?No public listing in CISA KEV
Affectedchargemap.com All versions
Fixed inSame patched build as CVE-2026-20791
Type (CWE)CWE-613

What's different about CVE-2026-25711?

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.

How to fix CVE-2026-25711

Apply the patched build per the primary write-up: How to Fix CVE-2026-20791. All commands, verification steps, and rollback notes for chargemap.com are listed there.

Frequently asked questions

Does the CVE-2026-20791 patch close CVE-2026-25711?

Yes. Both CVEs are addressed by the same vendor patch. Applying the patched build closes the full bundle.

Is CVE-2026-25711 listed in CISA KEV?

No public KEV listing at the time of this writing.

Where is the official advisory?

See https://chargemap.com/en-us/support

References


*Written by Sai Kiran Pandrala. Part of the chargemap.com bundle. Full procedure at how-to-fix-cve-2026-20791.*