CVE-2026-53451
Unauthenticated path-traversal + unsafe YAML leads to code execution as service.
Is CVE-2026-53451 being exploited?
Not confirmed. CVE-2026-53451 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.73% probability of exploitation in the next 30 days.
How severe is CVE-2026-53451?
CVE-2026-53451 is rated Critical. 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-53451?
Yes. A fix has been recorded for CVE-2026-53451. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53451 affect?
CVE-2026-53451 affects Ground Station < 0.4.13, backend/server/snapshots.py, backend/common/logger.py. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53451?
Upgrade to Ground Station 0.4.13; block untrusted Socket.IO access and harden filesystem permissions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can write arbitrary files via path-traversal, set a malicious logging YAML, and trigger logging.config.dictConfig to execute code as the service user and cause crash loops.
Immediate action required
- affected< 0.4.13
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.