CVE-2022-29693: Unicorn Engine v2.0.0-rc7 and below was discovered to contain a memory leak via the function uc_close at /my/u

Q: How do I fix CVE-2022-29693?

unicorn engine: upgrade to 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-29693 being exploited?

CVE-2022-29693 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-29693 affect?

CVE-2022-29693 affects unicorn engine. Severity is high (CVSS 7.5). 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.

Q: How urgent is CVE-2022-29693?

Priority 54/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2022-29693 is a high-severity flaw (CVSS 7.5) affecting unicorn engine. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.3% (top 31%)
CISA exploited list	No
Weakness	CWE-401
Published	2022-06-02
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: unicorn-engine

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-02 14:15 UTCPublished CVE record published
2026-06-17 04:40 UTCUpdated Record last modified

unicorn-engine unicorn engine UPGRADE

Affected: < 2.0.0 · 2.0.0 · 2.0.0 rc1 · 2.0.0 rc2 · 2.0.0 rc3 · 2.0.0 rc4 · 2.0.0 rc5 · 2.0.0 rc6

Fixed in: 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy unicorn-engine || rpm -q unicorn-engine || unicorn-engine --version

2. UPGRADE to 2.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade unicorn-engine

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade unicorn-engine

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-29693?

unicorn engine: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2022-29693 being exploited?

CVE-2022-29693 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-29693 affect?

CVE-2022-29693 affects unicorn engine. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2022-29693?

Priority 54/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-29695 HIGH 7.5 UPGRADE Unicorn Engine v2.0.0-rc7 contains memory leaks caused by an incomplete unicorn engine initialization.
CVE-2022-29694 HIGH 7.5 UPGRADE Unicorn Engine v2.0.0-rc7 and below was discovered to contain a NULL pointer dereference via qemu_ram_free.
CVE-2022-29692 HIGH 7.8 DOWNGRADE Unicorn Engine v1.0.3 was discovered to contain a use-after-free vulnerability via the hook function.
CVE-2021-44078 HIGH 8.1 UPGRADE An issue was discovered in split_region in uc.c in Unicorn Engine before 2.0.0-rc5
CVE-2021-36979 MEDIUM 5.5 DOWNGRADE MITIGATE Unicorn Engine 1.0.2 has an out-of-bounds write in tb_flush_armeb (called from cpu_arm_exec_armeb and tcg_cpu_

References

← Back to latest CVEs