CVE-2026-6375
Unauthenticated PNR query in SpiceJet booking API exposes passenger names.
Is CVE-2026-6375 being exploited?
Not confirmed. CVE-2026-6375 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.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-6375?
CVE-2026-6375 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-6375?
Not known from our data. No patch reference has been recorded for CVE-2026-6375, 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-6375 affect?
CVE-2026-6375 affects SpiceJet booking API. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-6375?
Enforce auth checks on PNR endpoint and monitor access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated access enables PNR enumeration and passenger name disclosure.
Immediate action required