CVE-2022-1534: Buffer Over-read at parse_rawml.c:1416 in GitHub repository bfabiszewski/libmobi prior to 0.11

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

libmobi: upgrade to 0.11. Exact commands for each OS are on this page.

Q: Is CVE-2022-1534 being exploited?

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

CVE-2022-1534 affects libmobi. Severity is high (CVSS 7.1). Buffer Over-read at parse_rawml.c:1416 in GitHub repository bfabiszewski/libmobi prior to 0.11. The bug causes the program reads data past the end of the intented buffer. Typically, this can allow attackers to read sensitive information fro

Q: How urgent is CVE-2022-1534?

Priority 37/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

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

Buffer Over-read at parse_rawml.c:1416 in GitHub repository bfabiszewski/libmobi prior to 0.11. The bug causes the program reads data past the end of the intented buffer. Typically, this can allow attackers to read sensitive information from other memory locations or cause a crash.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Weakness	CWE-126, CWE-125
Published	2022-04-29
Last modified	2026-06-17

Publisher (CNA): huntr.dev · Vendor: libmobi project

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

Am I affected?

Timeline

2022-04-29 11:15 UTCPublished CVE record published
2026-06-17 04:22 UTCUpdated Record last modified

libmobi project libmobi UPGRADE

Affected: < 0.11

Fixed in: 0.11

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libmobi || rpm -q libmobi || libmobi --version

2. UPGRADE to 0.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libmobi

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libmobi

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

libmobi: upgrade to 0.11. Exact commands for each OS are on this page.

Is CVE-2022-1534 being exploited?

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

CVE-2022-1534 affects libmobi. Severity is high (CVSS 7.1). Buffer Over-read at parse_rawml.c:1416 in GitHub repository bfabiszewski/libmobi prior to 0.11. The bug causes the program reads data past the end of the intented buffer. Typically, this can allow attackers to read sensitive information fro

How urgent is CVE-2022-1534?

Priority 37/100. High severity; Public exploit reference

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2022-2279 MEDIUM 5.5 UPGRADE NULL Pointer Dereference in GitHub repository bfabiszewski/libmobi prior to 0.11.
CVE-2022-29788 MEDIUM 6.5 UPGRADE libmobi before v0.10 contains a NULL pointer dereference via the component mobi_buffer_getpointer
CVE-2022-1987 HIGH 8.1 UPGRADE Buffer Over-read in GitHub repository bfabiszewski/libmobi prior to 0.11.
CVE-2022-1908 HIGH 8.1 UPGRADE Buffer Over-read in GitHub repository bfabiszewski/libmobi prior to 0.11.
CVE-2022-1907 HIGH 8.1 UPGRADE Buffer Over-read in GitHub repository bfabiszewski/libmobi prior to 0.11.

References

← Back to latest CVEs