{"action":"Upgrade lmdb to 0.98 or later.","affected":[{"fixed":"0.98","introduced":"0"}],"component":"lmdb","cve_ids":["CVE-2019-16226"],"ecosystem":"PyPI","epss":0.01586,"exploited":false,"fixed_versions":["0.98"],"ghsa_id":"GHSA-r8g9-w4f3-9crm","id":"tcs_01M5KG959MX6A7TRQTNRJKJTN0","modified_at":"2026-06-10T17:02:01.584714334Z","published_at":"2019-09-11T15:15:00Z","references":["https://osv.dev/vulnerability/PYSEC-2019-238","https://github.com/TeamSeri0us/pocs/tree/master/lmdb/lmdb%20memory%20corruption%20vuln","https://pypi.org/project/lmdb","https://nvd.nist.gov/vuln/detail/CVE-2019-16226","https://github.com/advisories/GHSA-r8g9-w4f3-9crm"],"severity":{"label":"high","score":7.5},"sources":[{"source":"osv","source_id":"PYSEC-2019-238","url":"https://osv.dev/vulnerability/PYSEC-2019-238"},{"source":"nvd","source_id":"CVE-2019-16226","url":"https://nvd.nist.gov/vuln/detail/CVE-2019-16226"}],"summary":"An issue was discovered in py-lmdb 0.97. mdb_node_del does not validate a memmove in the case of an unexpected node->mn_hi, leading to an invalid write operation. NOTE: this outcome occurs when access"}