CVE-2026-102808

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-29. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

PX4 Autopilot through 1.17.0 contains a NULL pointer dereference vulnerability in the sd_stress command where the -b byte count parameter is parsed without validation before being passed to malloc() and memset(). Attackers with shell access, including through MAVLink, can supply invalid byte count values to crash the flight controller.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
29
EG Risk 29/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

October 2, 2026

Advisory Details (5)

Auto-updated Sep 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

PX4 Autopilot through 1.17.0 NULL Pointer Dereference via sd_stress | Advisories | VulnCheck

https://www.vulncheck.com/advisories/px4-autopilot-through-1.17.0-null-pointer-dereference-via-sd-stress
generic

GitHub - PX4/PX4-Autopilot: PX4 Autopilot Software · GitHub

https://github.com/PX4/PX4-Autopilot
generic

PX4-Autopilot/src/systemcmds/sd_stress/sd_stress.cpp at d6f12ad1c4f70ad3230afd7d86e971421e02fef4 · PX4/PX4-Autopilot · GitHub

https://github.com/PX4/PX4-Autopilot/blob/d6f12ad1c4f70ad3230afd7d86e971421e02fef4/src/systemcmds/sd_stress/sd_stress.cpp#L186-L204
github_commit

commit c865dc9fde14 (PX4/PX4-Autopilot)

Fix landed in PX4/PX4-Autopilot commit c865dc9fde14 — awaiting tagged release

https://github.com/PX4/PX4-Autopilot/commit/c865dc9fde14d1391916775153aa271603c3c592
github_pr

fix(sd_stress): add size check when parse -b option to prevent system crash

Fix merged in PX4/PX4-Autopilot PR #28795 on 2026-09-28 — awaiting tagged release

https://github.com/PX4/PX4-Autopilot/pull/28795

Vendor Advisories for CVE-2026-102808(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 08:54 UTCEG score recompute
  2. 2026-10-04 08:54 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-03 11:06 UTCEG score recompute
  5. 2026-10-03 11:06 UTCGHSA enrichment
  6. 2026-10-02 13:18 UTCEG score recompute
  7. 2026-10-02 13:18 UTCGHSA enrichment
  8. 2026-10-02 12:22 UTCEG score recompute
  9. 2026-10-02 12:22 UTCGHSA enrichment
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 15:13 UTCGHSA enrichment
  12. 2026-09-30 17:26 UTCGHSA enrichment
  13. 2026-09-30 16:34 UTCEG score recompute
  14. 2026-09-30 16:34 UTCGHSA enrichment
  15. 2026-09-30 15:02 UTCEPSS rescore
  16. 2026-09-29 18:31 UTCEG score recompute
  17. 2026-09-29 17:29 UTCEG score recompute
  18. 2026-09-29 17:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102808?
CVE-2026-102808 is a medium vulnerability published on September 29, 2026. PX4 Autopilot through 1.17.0 contains a NULL pointer dereference vulnerability in the sd_stress command where the -b byte count parameter is parsed without validation before being passed to malloc() and memset(). Attackers with shell access, including through MAVLink, can supply invalid byte count…
When was CVE-2026-102808 disclosed?
CVE-2026-102808 was first published on September 29, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102808 actively exploited?
CVE-2026-102808 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102808?
CVE-2026-102808 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102808?
An upstream fix for CVE-2026-102808 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-102808 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-102808

Explore →

Is Your Infrastructure Affected by CVE-2026-102808?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs