CVE-2022-29692: Unicorn Engine v1.0.3 was discovered to contain a use-after-free vulnerability via the hook function.

This month

HIGH 7.8DOWNGRADE

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

Unicorn Engine v1.0.3 was discovered to contain a use-after-free vulnerability via the hook function.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.8% (top 43%)
CISA exploited list	No
Weakness	CWE-416
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 DOWNGRADE

Affected: 1.0.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.3

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 1.0.3 (Debian / Ubuntu)

apt-cache madison unicorn-engine sudo apt install unicorn-engine=<VERSION_BEFORE_1.0.3> sudo apt-mark hold unicorn-engine

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list unicorn-engine sudo dnf downgrade unicorn-engine-<VERSION_BEFORE_1.0.3> sudo dnf versionlock add unicorn-engine

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-29692?

unicorn engine: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-29692 being exploited?

CVE-2022-29692 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-29692 affect?

CVE-2022-29692 affects unicorn engine. Severity is high (CVSS 7.8). Unicorn Engine v1.0.3 was discovered to contain a use-after-free vulnerability via the hook function.

How urgent is CVE-2022-29692?

Priority 46/100. High severity; Public exploit reference

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-29693 HIGH 7.5 UPGRADE Unicorn Engine v2.0.0-rc7 and below was discovered to contain a memory leak via the function uc_close at /my/u
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