# CVE-2025-3791: symisc UnQLite unqlite.c jx9MemObjStore heap-based overflow

> A heap-based buffer overflow in UnQLite allows local attackers to execute arbitrary code or cause denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 18 Apr 2025
- **Updated:** 18 Apr 2025
- **Also known as:** GHSA-fg69-m383-f979

## What is CVE-2025-3791?

CVE-2025-3791 is a medium-severity memory corruption vulnerability in symisc UnQLite, published on 18 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in symisc UnQLite up to 957c377cb691a4f617db9aba5cc46d90425071e2. This vulnerability affects the function jx9MemObjStore of the file /data/src/benchmarks/unqlite/unqlite.c. The manipulation leads to heap-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2025-3791 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3791 is a medium-severity memory corruption vulnerability in symisc UnQLite, published on 18 Apr 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-3791 exists.

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

## Sources

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

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