# CVE-2026-6375: Authorization bypass through User-Controlled key in SpiceJet Online Booking System

> Unauthenticated attackers can enumerate predictable PNRs to access passenger names due to missing authorization checks on the booking API.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-x532-492q-g257

## What is CVE-2026-6375?

CVE-2026-6375 is a high-severity missing authorization vulnerability in SpiceJet Online Booking System, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in SpiceJet’s booking API allows unauthenticated users to query passenger name records (PNRs) without any access controls. Because PNR identifiers follow a predictable pattern, an attacker could systematically enumerate valid records and obtain associated passenger names. This flaw stems from missing authorization checks on an endpoint intended for authenticated profile access.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-6375?


## How do I fix CVE-2026-6375?

No fix has been published for CVE-2026-6375 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6375 being exploited?

There is no known exploitation of CVE-2026-6375 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6375 and fix it if it is affected.

What it is: CVE-2026-6375 is a high-severity missing authorization vulnerability in SpiceJet Online Booking System, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6375 in the wild and no public exploit code.

Affected product: SpiceJet Online Booking System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6375/ (Markdown: https://insights.sbomify.com/CVE-2026-6375/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6375
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6375
- OSV: https://osv.dev/vulnerability/CVE-2026-6375

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6375/
Summaries are generated and may contain mistakes; the official description above is the record.