CVE-2026-82262

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. The CNA's CVSS baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Logto through 1.42.0 contains a server-side request forgery vulnerability in the POST /api/hooks/:id/test endpoint that accepts arbitrary URLs without host validation. Tenant administrators with Management API tokens can make the server issue HTTP POST requests to internal URLs and retrieve response bodies from services on the private network.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

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 (value × EchelonGraph’s weight)
Severity68% × 45%
The EG Score, 6.8 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

September 24, 2026

Advisory Details (5)

Auto-updated Aug 28, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

Logto Server-Side Request Forgery via webhook test endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/logto-server-side-request-forgery-via-webhook-test-endpoint
GitHub commit

commit 16f4b2e732d5 (logto-io/logto)

Fix landed in logto-io/logto commit 16f4b2e732d5 — awaiting tagged release

https://github.com/logto-io/logto/commit/16f4b2e732d5114ac98646c9370ec6ab61d6ed26
Web page

logto/packages/core/src/libraries/hook/utils.ts at v1.42.0 · logto-io/logto · GitHub

https://github.com/logto-io/logto/blob/v1.42.0/packages/core/src/libraries/hook/utils.ts
Web page

GitHub - logto-io/logto: 🧑‍🚀 Authentication and authorization infrastructure for SaaS and AI apps, built on OIDC and OAuth 2.1 with multi-tenancy, SSO, and RBAC. · GitHub

https://github.com/logto-io/logto
Web page

SSRF via Webhook Endpoint and OIDC SSO Connector issuer URL · Issue #9465 · logto-io/logto · GitHub

https://github.com/logto-io/logto/issues/9465

Vendor Advisories for CVE-2026-82262(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 15× in last 7d / 78× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 125 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 27 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  3. 2026-10-12 14:55 UTCEG score recompute
  4. 2026-10-11 19:20 UTCEG score recompute
  5. 2026-10-11 16:36 UTCEG score recompute
  6. 2026-10-11 13:54 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  9. 2026-10-10 00:54 UTCEG score recompute
  10. 2026-10-10 00:53 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  13. 2026-10-08 09:13 UTCEG score recompute
  14. 2026-10-08 09:13 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  16. 2026-10-07 08:45 UTCEG score recompute
  17. 2026-10-07 08:45 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  19. 2026-10-06 08:10 UTCEG score recompute
  20. 2026-10-06 08:10 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  22. 2026-10-05 07:42 UTCEG score recompute
  23. 2026-10-05 07:42 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  24. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  25. 2026-10-04 07:13 UTCEG score recompute
Show 73 more
  1. 2026-10-04 07:13 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  2. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  3. 2026-10-03 06:45 UTCEG score recompute
  4. 2026-10-03 06:45 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  5. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  6. 2026-10-02 06:16 UTCEG score recompute
  7. 2026-10-02 06:16 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  8. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  9. 2026-10-01 04:18 UTCEG score recompute
  10. 2026-10-01 04:18 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  11. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  12. 2026-09-30 03:50 UTCEG score recompute
  13. 2026-09-30 03:50 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  14. 2026-09-28 21:09 UTCEG score recompute
  15. 2026-09-28 21:09 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  16. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  17. 2026-09-27 18:46 UTCEG score recompute
  18. 2026-09-27 18:46 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  20. 2026-09-26 18:17 UTCEG score recompute
  21. 2026-09-26 18:17 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  23. 2026-09-25 15:42 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  24. 2026-09-24 14:58 UTCEG score recompute
  25. 2026-09-24 14:58 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  26. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  27. 2026-09-24 06:42 UTCEG score recompute
  28. 2026-09-24 06:41 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  29. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  30. 2026-09-23 06:13 UTCEG score recompute
  31. 2026-09-23 06:13 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  32. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  33. 2026-09-22 05:44 UTCEG score recompute
  34. 2026-09-22 05:44 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  35. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  36. 2026-09-21 05:16 UTCEG score recompute
  37. 2026-09-21 05:16 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  38. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  39. 2026-09-20 04:45 UTCEG score recompute
  40. 2026-09-20 04:45 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  41. 2026-09-19 04:16 UTCEG score recompute
  42. 2026-09-19 04:16 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  43. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  44. 2026-09-18 03:48 UTCEG score recompute
  45. 2026-09-18 03:48 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  46. 2026-09-17 03:20 UTCEG score recompute
  47. 2026-09-17 03:20 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  48. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  49. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  50. 2026-09-16 02:50 UTCEG score recompute
  51. 2026-09-16 02:50 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  52. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  53. 2026-09-15 02:21 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  54. 2026-09-14 01:47 UTCEG score recompute
  55. 2026-09-14 01:47 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  56. 2026-09-13 01:19 UTCEG score recompute
  57. 2026-09-13 01:19 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  58. 2026-09-12 00:51 UTCEG score recompute
  59. 2026-09-12 00:51 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  60. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  61. 2026-09-11 00:22 UTCEG score recompute
  62. 2026-09-11 00:22 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  63. 2026-09-09 23:53 UTCEG score recompute
  64. 2026-09-09 23:53 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  65. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  66. 2026-09-08 20:52 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  67. 2026-09-07 22:55 UTCEG score recompute
  68. 2026-09-07 22:55 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  69. 2026-09-06 22:27 UTCEG score recompute
  70. 2026-09-06 22:27 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8
  71. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  72. 2026-09-05 21:59 UTCEG score recompute
  73. 2026-09-05 21:59 UTCGHSA enrichmentGHSA-2442-5g74-2q7v · GitHub severity HIGH · GitHub CVSS 6.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82262?
CVE-2026-82262 is a medium-severity vulnerability; its CVE record was published on August 28, 2026. Logto through 1.42.0 contains a server-side request forgery vulnerability in the POST /api/hooks/:id/test endpoint that accepts arbitrary URLs without host validation. Tenant administrators with Management API tokens can make the server issue HTTP POST requests to internal URLs and retrieve…
When was CVE-2026-82262 made public?
CVE-2026-82262 was made public on August 16, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 28, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-82262 actively exploited?
CVE-2026-82262 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82262?
CVE-2026-82262 has a CVSS base score of 6.8 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-82262?
An upstream fix for CVE-2026-82262 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-82262 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82262?

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

Book a Demo →Browse All CVEs