Unicorn Engine v2.0.0-rc7 and below was discovered to contain a memory leak via the function uc_close at /my/unicorn/uc.c.

published 2022-05-27 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-34019

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits: 0; none known

Patch / fix

fixed in 1 distros 1 links 1

unicorn-engine unicorn_engine 2.0.0

unicorn Alpine 3.24 2.0.1-r0

alpine advisories ALPINE-CVE-2022-29693

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

github.com/unicorn-engine/unicorn@469fc4c commit

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-29693 updated 2025-11-21

unicorn: memory leak via the function uc_close at /my/unicorn/uc.c

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/unicorn-engine/unicorn/issues/1586 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

CWE-401 Missing Release of Memory after Effective Lifetime

References

github.com /unicorn-engine/unicorn/commit/469fc4c35a0cfabdbefb158e22d145f4ee6f77b9
patch, third-party-advisory
github.com /unicorn-engine/unicorn/issues/1586
exploit, issue-tracking, third-party-advisory

Sources

CVE List CVE-2022-29693
NVD CVE-2022-29693

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary