VulnerabilityPublished 27 Feb 2026

CVE-2026-3285: berry · Out-of-bounds Read

Affects berrySource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

4.8Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Local: The vulnerable system 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 through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
berry-langberry	Affected =1.0 =1.1.0	Fixed in–
GitHubberry-lang/berry`pkg:github/berry-lang/berry`Other threats	Affected =1.0 =1.1.0	Fixed in–

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

AI-suggested

To mitigate CVE-2026-3285, organizations should immediately apply the official patch identified by commit 7149c59a39ba44feca261b12f06089f265fec176 or upgrade to a berry-lang version beyond 1.1.0 that includes the fix. Since the vulnerability requires local access, it is critical to enforce strict access controls and limit user privileges to reduce the risk of unauthorized local exploitation. Employing application whitelisting and monitoring for unusual local activity can help detect exploitation attempts. Additionally, conduct code audits and testing on any custom integrations of berry-lang to identify potential misuse of the scan_string function or similar parsing routines. For embedded systems, ensure secure firmware update mechanisms are in place to deploy patches promptly. Network segmentation and endpoint protection can further reduce the attack surface by isolating vulnerable systems. Finally, maintain an inventory of all systems using berry-lang to prioritize patching and risk assessment.

Description

A vulnerability was determined in berry-lang berry up to 1.1.0. The affected element is the function scan_string of the file src/be_lexer.c. This manipulation causes out-of-bounds read. The attack requires local access. The exploit has been publicly disclosed and may be utilized. Patch name: 7149c59a39ba44feca261b12f06089f265fec176. Applying a patch is the recommended action to fix this issue.

Impact

The primary impact of CVE-2026-3285 is the potential unauthorized disclosure of sensitive information due to out-of-bounds memory reads. This can compromise confidentiality by exposing internal memory contents that may include sensitive data such as credentials, cryptographic material, or proprietary information. Since the vulnerability requires local access and low privileges, the risk is somewhat mitigated by the need for an attacker to have initial foothold on the system. However, in environments where berry-lang is embedded in critical systems or used in multi-tenant or shared environments, this vulnerability could facilitate lateral movement or privilege escalation by leaking information useful for further attacks. There is no direct impact on data integrity or system availability. The scope is limited to systems running vulnerable versions of berry-lang, which may be embedded in IoT devices, lightweight applications, or specialized software. Failure to patch could lead to increased risk of data breaches and compromise of system confidentiality in affected environments.

Summary

CVE-2026-3285 identifies a security vulnerability in the berry-lang interpreter, an embeddable scripting language designed for resource-constrained environments. The vulnerability exists in the scan_string function within the lexer component (src/be_lexer.c) and manifests as an out-of-bounds read condition. This occurs when the function improperly handles string scanning, allowing it to read memory beyond the allocated buffer. The flaw requires local access and low privileges, meaning an attacker must have some level of access to the system but does not require elevated permissions or user interaction to exploit. The out-of-bounds read can lead to unauthorized disclosure of memory contents, potentially exposing sensitive data such as cryptographic keys, passwords, or other confidential information residing in adjacent memory. The vulnerability affects berry-lang versions 1.0 and 1.1.0. The CVSS v4.0 base score is 4.8, reflecting a medium severity level due to the limited attack vector (local access) and the absence of integrity or availability impacts. A patch identified by commit 7149c59a39ba44feca261b12f06089f265fec176 has been released to fix this issue. While no known exploits have been observed in the wild, the public disclosure of the vulnerability increases the risk of exploitation attempts. Organizations embedding berry-lang in their products or using it for scripting should apply the patch promptly to prevent potential data leakage.

References

Community reviews

Loading reviews…