VulnerabilityPublished 21 Jan 2026

CVE-2026-23955: everest-core · Creation of Immutable Text Using String Concatenation

Affects everest-coreSource CVE Database V5

Not known to be exploited · CVSS 4.2 Medium : upgrade to 2025.9.0 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.9.0

CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade everest-core and everest/everest-core to 2025.9.0.

Affected software

Product	Affected	Fixed in
EVeresteverest-core	Affected <2025.9.0	Fixed in 2025.9.0
GitHubeverest/everest-core`pkg:github/everest/everest-core`Other threats	Affected <2025.9.0	Fixed in 2025.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade all instances of EVerest everest-core to version 2025.9.0 or later to remediate this vulnerability. Until patching is complete, restrict operator access to the charging software to only trusted personnel and enforce strict privilege management to minimize the risk of malicious exploitation. Implement monitoring and logging of operator actions to detect anomalous behavior indicative of exploitation attempts. Conduct regular code reviews and security audits focusing on error handling and string operations to prevent similar issues. Additionally, apply memory protection mechanisms such as address space layout randomization (ASLR) and stack canaries to reduce the impact of memory disclosure vulnerabilities. Educate operators about the risks of interacting with suspicious error messages or prompts. Finally, ensure that incident response plans include procedures for handling potential memory disclosure incidents in EV infrastructure.

Description

CVE-2026-23955 is a medium severity vulnerability in the EVerest EV charging software stack (everest-core) prior to version 2025.9.0. The flaw arises from improper string concatenation of integer values to literal strings when throwing errors, causing pointer arithmetic instead of expected integer printing. This behavior can be exploited by a malicious operator with high privileges and requiring user interaction to read unintended memory regions, including heap and stack areas, potentially exposing sensitive information. The vulnerability does not affect integrity or availability but impacts confidentiality. No known exploits are currently reported in the wild. The issue is fixed in version 2025.9.0.

Impact

For European organizations operating EV charging infrastructure using affected versions of EVerest everest-core, this vulnerability could lead to unauthorized disclosure of sensitive memory contents. This may include cryptographic keys, authentication tokens, or other confidential operational data residing in heap or stack memory. Such information leakage could facilitate further attacks, including privilege escalation or unauthorized access to charging systems. Given the critical role of EV charging infrastructure in energy and transportation sectors, any compromise could disrupt services or erode trust. However, since exploitation requires high privileges and user interaction, the risk is somewhat mitigated but remains significant in insider threat scenarios or compromised operator accounts. The confidentiality breach could also have regulatory implications under GDPR if personal or operational data is exposed. Therefore, the impact on European organizations is primarily confidentiality loss with potential operational and compliance consequences.

References

github.com/EVerest/everest-core/security/advisories/GHSA-px57-jx97-hrff (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Jan 2026, 20:24 UTC

WeaknessesCWE-1046

Technical details

References

Community reviews

Related threats