Skip to content
Web

CVE-2026-53983

9.2
Critical
EPSS 0.33%Patch availableAug 7, 2026

Unauthenticated SSRF in Ground Station allows server-side requests to attacker-controlled/internal targets.

common questions

Is CVE-2026-53983 being exploited?

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

How severe is CVE-2026-53983?

CVE-2026-53983 is rated Critical with a CVSS score of 9.2. 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-53983?

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

What does CVE-2026-53983 affect?

CVE-2026-53983 affects Ground Station < 0.6.0, Socket.IO server (port 7000), orbital-sync background task, tlesync/source_adapters.py. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-53983?

Block port 7000, restrict CORS/auth, validate URLs, and apply vendor patch when released

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

executive summary
technical analysis
affected
Ground Station < 0.6.0Socket.IO server (port 7000)orbital-sync background tasktlesync/source_adapters.py
impact

Unauthenticated SSRF via Socket.IO lets attackers force server to fetch attacker URLs, access cloud metadata and internal services, enabling credential theft and lateral movement.

action required

Immediate action required

affected versions
Efstratios Goudelis Ground Station
  • affected< 0.6.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