CVE-2026-75833

MEDIUMPre-NVD 4.24.2
EchelonGraph scoreHIGH confidence

Score 4.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-18. a secondary CVSS source baseline 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
4.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Grav API plugin (getgrav/grav-plugin-api, bundled with Grav 2.0's admin-next/API stack) before version 1.0.14 contains an open redirect weakness in SsoController::sanitizeReturnTo(). The function rejects a literal '//' prefix but does not account for browsers normalizing backslashes to slashes in special (http/https) schemes, so a returnTo value such as '/\evil.com' passes the guard and is later resolved by the browser as the protocol-relative URL '//evil.com'. Following a legitimate OAuth login flow, an attacker-supplied returnTo parameter could redirect an authenticated victim to an attacker-controlled site for post-login phishing. Full browser-side exploitability depends on the admin-next SPA's client-side oauth-callback handler and was not independently verified by the reporter.

CVSS v3
4.2
EG Score
4.2(high)
EG Risk
35(Track*)
EG Risk 35/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity42% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Aug 18, 2026
Patch available. Sources: github.
generic

Grav API Plugin Open Redirect via Backslash Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/grav-api-plugin-open-redirect-via-backslash-bypass
github Patch Available

SsoController::sanitizeReturnTo() backslash bypass of the in-app-path-only open-redirect guard · Advisory · getgrav/grav · GitHub

https://github.com/getgrav/grav/security/advisories/GHSA-x72c-4jc4-8rh6

Vendor Advisories for CVE-2026-75833(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 20:39 UTCGHSA enrichment
  3. 2026-08-19 18:16 UTCEG score recompute
  4. 2026-08-19 18:16 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 14:47 UTCEG score recompute
  7. 2026-08-18 14:46 UTCGHSA enrichment
  8. 2026-08-18 14:06 UTCEG score recompute
  9. 2026-08-18 14:05 UTCGHSA enrichment
  10. 2026-08-18 12:34 UTCEG score recompute
  11. 2026-08-18 12:34 UTCGHSA enrichment
  12. 2026-08-18 11:29 UTCEG score recompute
  13. 2026-08-18 11:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75833?
CVE-2026-75833 is a medium vulnerability published on August 18, 2026. The Grav API plugin (getgrav/grav-plugin-api, bundled with Grav 2.0's admin-next/API stack) before version 1.0.14 contains an open redirect weakness in SsoController::sanitizeReturnTo(). The function rejects a literal '//' prefix but does not account for browsers normalizing backslashes to slashes…
When was CVE-2026-75833 disclosed?
CVE-2026-75833 was first published in the National Vulnerability Database on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75833 actively exploited?
CVE-2026-75833 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.5% of all scored CVEs.
What is the CVSS score of CVE-2026-75833?
CVE-2026-75833 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-75833?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75833, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-75833

Explore →

Is Your Infrastructure Affected by CVE-2026-75833?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.