# CVE-2026-25774: EV Energy ev.energy Insufficiently Protected Credentials

> Attackers can access charging station authentication identifiers via public web mapping platforms, exposing sensitive credentials.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/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:** 27 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-28pj-7rwg-vxrf

## What is CVE-2026-25774?

CVE-2026-25774 is a medium-severity vulnerability in ev.energy, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Charging station authentication identifiers are publicly accessible via web-based mapping platforms.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Ev.energy Ev.energy.

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

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

## Is CVE-2026-25774 being exploited?

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

## Other vulnerabilities in ev.energy

- [CVE-2026-27772](https://insights.sbomify.com/CVE-2026-27772/): EV Energy ev.energy Missing Authentication for Critical Function (critical 9.3)
- [CVE-2026-24445](https://insights.sbomify.com/CVE-2026-24445/): EV Energy ev.energy Improper Restriction of Excessive Authentication Attempts (high 8.7)
- [CVE-2026-26290](https://insights.sbomify.com/CVE-2026-26290/): EV Energy ev.energy Insufficient Session Expiration (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25774 is a medium-severity vulnerability in ev.energy, published on 27 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-25774 in the wild and no public exploit code.

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

## Sources

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

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