Security readout for executives and security teams
Plain-English summary
EVerest everest-core before 2025.9.0 can expose unintended memory when certain error messages are built incorrectly. The issue requires a malicious operator with high privileges and user interaction, so broad internet-scale risk is not indicated. The main concern is confidentiality of memory from EV charging software environments.
Executive priority
Treat as a targeted confidentiality issue, not an emergency internet-wide incident. Patch during the next suitable maintenance window, sooner for sensitive or operator-facing charging environments. Restrict privileged operator access until remediation is confirmed.
Technical view
The bug is caused by concatenating integer values to string literals in error handling. In C/C++, this performs pointer arithmetic instead of formatting the integer, potentially reading unintended heap or stack memory. Affected versions are everest-core before 2025.9.0. CVSS is 4.2 with local access, low complexity, high privileges, user interaction required, and high confidentiality impact.
Likely exposure
Exposure is likely limited to deployments running EVerest everest-core earlier than 2025.9.0, especially EV charging systems where highly privileged operators can trigger affected error paths. The provided sources do not indicate remote unauthenticated exposure.
Exploitation context
The CVE describes possible memory disclosure by a malicious operator. CISA KEV status is false in the provided data, and no cited source states active exploitation. Exploitation appears constrained by local access, high privileges, and required user interaction.
Researcher notes
The advisory attributes the issue to string-literal and integer concatenation leading to pointer arithmetic in thrown errors. Evidence supports unintended heap and stack memory reads. Sources do not provide affected code locations, proof-of-concept details, or evidence of exploitation in the wild.
Mitigation direction
- Upgrade EVerest everest-core to version 2025.9.0 or later.
- Prioritize systems handling sensitive charging operations or operator-accessible workflows.
- If upgrade timing is uncertain, check the GitHub advisory for vendor guidance.
- Limit high-privilege operator access to trusted personnel until patched.
Validation and detection
- Inventory EVerest everest-core deployments and identify versions below 2025.9.0.
- Confirm whether EV charging systems include the affected everest-core component.
- Review vendor advisory details against local build and deployment records.
- After upgrade, verify deployed version reports 2025.9.0 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1046: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-23955 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N0.63.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.2MediumVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/EVerest/everest-core/security/advisories/GHSA-px57-jx97-hrffCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Creation of Immutable Text Using String Concatenation
Creation of Immutable Text Using String Concatenation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.