Skip to content
IoT

CVE-2026-74238

8.7
High
EPSS 0.38%Aug 18, 2026

OOB UDP read in Velodyne decoder allows fabricated PointCloud2 data.

common questions

Is CVE-2026-74238 being exploited?

Not confirmed. CVE-2026-74238 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.38% probability of exploitation in the next 30 days.

How severe is CVE-2026-74238?

CVE-2026-74238 is rated High with a CVSS score of 8.7. 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-74238?

Not known from our data. No patch reference has been recorded for CVE-2026-74238, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-74238 affect?

CVE-2026-74238 affects TIER IV Nebula <=1.2.0, Velodyne UDP sensor port/driver, Autoware nodes consuming PointCloud2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74238?

Restrict UDP access to Velodyne ports, isolate sensors, and apply vendor patch when available.

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

executive summary
technical analysis
affected
TIER IV Nebula <=1.2.0Velodyne UDP sensor port/driverAutoware nodes consuming PointCloud2
impact

Unauthenticated UDP packet triggers heap OOB read, publishing fabricated PointCloud2 points—enables sensor spoofing and perception/safety manipulation.

action required

Immediate action required

affected versions
tier4 nebula
  • affected<= 1.2.0

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