# CVE-2026-4010: ThakeeNathees pocketlang pkByteBufferAddString memory corruption

> Local attackers can trigger memory corruption in pocketlang via integer overflow in pkByteBufferAddString, potentially leading to code execution or crashes.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-5gjx-6c5v-frf5

## What is CVE-2026-4010?

CVE-2026-4010 is a medium-severity memory corruption vulnerability in ThakeeNathees pocketlang, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in ThakeeNathees pocketlang up to cc73ca61b113d48ee130d837a7a8b145e41de5ce. The affected element is the function pkByteBufferAddString. The manipulation of the argument length with the input 4294967290 results in memory corruption. The attack requires a local approach. The exploit has been made public and could be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-4010 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4010 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4010 is a medium-severity memory corruption vulnerability in ThakeeNathees pocketlang, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4010 exists.

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

## Sources

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

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