py-lmdb Invalid write operation

published 2019-09-11 7 y ago modified 2026-06-17 4 mo ago also GHSA-9q62-r72g-pvv7 , PYSEC-2019-236 , EUVD-2019-0077

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

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.

Patch / fix

fixed in 1 distros 1

pypi lmdb 0.98

python-lmdb openSUSE Tumbleweed 2.1.1-1.1

opensuse advisories openSUSE-SU-2026:10430-1

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-2019-16224 updated 2026-01-08 cvss 7.6

python-lmdb: out-of-bounds write when setting a wrong value of field md_flag

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.81% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/TeamSeri0us/pocs/tree/master/lmdb/lmdb%20initialization%20vuln referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
pypi	lmdb	<=0.97 <0.98	0.98

Classification

Weakness

CWE-787 Out-of-bounds Write

References

github.com /TeamSeri0us/pocs/tree/master/lmdb/lmdb%20initialization%20vuln
web, exploit, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2019-16224
advisory
github.com /jnwatson/py-lmdb
package
github.com /pypa/advisory-database/tree/main/vulns/lmdb/PYSEC-2019-236.yaml
web
pypi.org /project/lmdb
web, package
github.com /advisories/GHSA-9q62-r72g-pvv7
advisory

Sources

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