CVE-2026-63408Public exploitNetwork attack vector

API token exposure via query parameter

Published Aug 19, 2026 · Updated Aug 19, 2026

Information disclosure in Grav API Plugin before 1.0.0-rc.16 allows attackers to reuse exposed API tokens via URL query strings. JwtAuthenticator::extractBearerToken() accepts a JWT from the token query parameter on every /api/v1 route instead of confining bearer tokens to headers or narrowly scoped download handling, so full token-bearing URLs are recorded in server, proxy, and CDN logs, browser history, and Referer headers. Exploitation requires access to those recorded or forwarded URLs, but any recovered token carries the owner's API privileges and can reach both read and state-changing endpoints.

CVSS severity7.5
High
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Grav API Plugin before 1.0.0-rc.16 allows attackers to reuse exposed API tokens via URL query strings. JwtAuthenticator::extractBearerToken() accepts a JWT from the token query parameter on every /api/v1 route instead of confining bearer tokens to headers or narrowly scoped download handling, so full token-bearing URLs are recorded in server, proxy, and CDN logs, browser history, and Referer headers. Exploitation requires access to those recorded or forwarded URLs, but any recovered token carries the owner's API privileges and can reach both read and state-changing endpoints.

The record

CVE
CVE-2026-63408
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
Grav
Product
Grav API Plugin
Classifications
CWE-598, T1528
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.0.0-rc.16

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Grav · Grav API Pluginversion=< 1.0.0-rc.16

Published CVSS scores

7.5GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-598Use of HTTP Request With Sensitive Query String
T1528Steal Application Access Token

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo