CVE-2019-16224: An issue was discovered in py-lmdb 0.97

Q: How do I fix CVE-2019-16224?

py-lmdb: upgrade to newer than 0.97. Exact commands for each OS are on this page.

Q: Is CVE-2019-16224 being exploited?

CVE-2019-16224 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-2019-16224 affect?

CVE-2019-16224 affects py-lmdb. Severity is critical (CVSS 9.8). An issue was discovered in py-lmdb 0.97. For certain values of md_flags, mdb_node_add does not properly set up a memcpy destination, leading to an invalid write operation. NOTE: this outcome occurs when accessing a data.mdb file supplied by

Q: How urgent is CVE-2019-16224?

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

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2019-16224 is a critical-severity flaw (CVSS 9.8) affecting py-lmdb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in py-lmdb 0.97. For certain values of md_flags, mdb_node_add does not properly set up a memcpy destination, leading to an invalid write operation. NOTE: this outcome occurs when accessing a data.mdb file supplied by an attacker.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 21%)
CISA exploited list	No
Weakness	CWE-787
Published	2019-09-11
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: py-lmdb project

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

Am I affected?

Timeline

2019-09-11 15:15 UTCPublished CVE record published
2026-06-17 02:21 UTCUpdated Record last modified

py-lmdb project py-lmdb UPGRADE

Affected: <= 0.97

Fixed in: newer than 0.97

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy py-lmdb || rpm -q py-lmdb || py-lmdb --version

2. UPGRADE to newer than 0.97 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade py-lmdb

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade py-lmdb

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-2019-16224?

py-lmdb: upgrade to newer than 0.97. Exact commands for each OS are on this page.

Is CVE-2019-16224 being exploited?

CVE-2019-16224 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-2019-16224 affect?

CVE-2019-16224 affects py-lmdb. Severity is critical (CVSS 9.8). An issue was discovered in py-lmdb 0.97. For certain values of md_flags, mdb_node_add does not properly set up a memcpy destination, leading to an invalid write operation. NOTE: this outcome occurs when accessing a data.mdb file supplied by

How urgent is CVE-2019-16224?

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

Related CVEs

CVE-2019-16228 HIGH 7.5 UPGRADE An issue was discovered in py-lmdb 0.97
CVE-2019-16227 CRITICAL 9.8 UPGRADE An issue was discovered in py-lmdb 0.97
CVE-2019-16226 HIGH 7.5 UPGRADE An issue was discovered in py-lmdb 0.97
CVE-2019-16225 CRITICAL 9.8 UPGRADE An issue was discovered in py-lmdb 0.97

References

← Back to latest CVEs