Skip to content
IoT

CVE-2026-12522

8.8
High
EPSS 0.22%Patch availableAug 21, 2026

Stack buffer overflow in HL7800 modem driver allows remote crash or code execution via rogue cellular network.

common questions

Is CVE-2026-12522 being exploited?

Not confirmed. CVE-2026-12522 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.

How severe is CVE-2026-12522?

CVE-2026-12522 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-12522?

Yes. A fix has been recorded for CVE-2026-12522. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-12522 affect?

CVE-2026-12522 affects HL7800 modem driver (drivers/modem/vendor_standalone/hl7800.c), Devices using HL7800 cellular modems or vendor implementations. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-12522?

Apply vendor/kernel firmware patch immediately; avoid untrusted cellular networks.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
HL7800 modem driver (drivers/modem/vendor_standalone/hl7800.c)Devices using HL7800 cellular modems or vendor implementations
impact

Remote stack overflow during +CGCONTRDP parsing can cause device crash and potentially remote code execution/privilege escalation without user interaction.

action required

Patch when possible

affected versions
zephyrproject zephyr
  • affected>= 2.4.0 and < 4.4.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free