# CVE-2026-62386: Grav < 1.0.0-rc.16 Authentication Bypass via token URL Parameter

> Attackers can steal admin JWT tokens from logs or history due to URL exposure, enabling unauthorized API access and privilege escalation.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** 17 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-cx27-6j8x-h4h6

## What is CVE-2026-62386?

CVE-2026-62386 is a high-severity vulnerability in getgrav grav, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Grav API plugin (getgrav/grav-plugin-api) before 1.0.0-rc.16 accepts JWT access tokens through the ?token= URL query parameter on every API route (JwtAuthenticator::extractBearerToken fallback). Because tokens are embedded in URLs, they are logged verbatim in web server access logs, leaked via the Referer header, stored in browser history, and captured by upstream proxy and CDN logs, exposing valid admin access tokens. A leaked token grants unauthorized API access, including reading configuration and user data, creating admin accounts, modifying system settings, and deleting pages.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String)

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


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

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

## Is CVE-2026-62386 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62386 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62386 is a high-severity vulnerability in getgrav grav, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62386 exists.

Affected product: getgrav grav. 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-62386/ (Markdown: https://insights.sbomify.com/CVE-2026-62386/index.md)
```

## Sources

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

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