# CVE-2025-50361: Memory corruption in n/a

> A buffer overflow in SmallBASIC allows attackers to cause crashes and potentially leak sensitive information.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2025
- **Updated:** 3 Dec 2025
- **Also known as:** GHSA-46q6-hv9q-wj69

## What is CVE-2025-50361?

CVE-2025-50361 is a medium-severity memory corruption vulnerability in n/a, published on 3 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer Overflow was found in SmallBASIC community SmallBASIC with SDL Before v12_28, and commit sha:298a1d495355959db36451e90a0ac74bcc5593fe in the function main.cpp, which can lead to potential information leakage and crash.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-50361?

It affects 1 product.


Products: Smallbasic Smallbasic.

## How do I fix CVE-2025-50361?

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

## Is CVE-2025-50361 being exploited?

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

Public exploit code:

- Report and PoC of Global Buffer Overflow on SmallBASIC before 02364eff880ba62afac67bcceebafade2b40d21f (github_poc): https://github.com/Ch1keen/CVE-2025-50361

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-50361 and fix it if it is affected.

What it is: CVE-2025-50361 is a medium-severity memory corruption vulnerability in n/a, published on 3 Dec 2025. 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-2025-50361 exists.

Affected product: n/a. 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-2025-50361/ (Markdown: https://insights.sbomify.com/CVE-2025-50361/index.md)
```

## Sources

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

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