CVE-2026-82448

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-29. The CNA's CVSS baseline 9.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
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Shinobi before commit 5a76c74f contains a hardcoded connection key in the child node service that allows unauthenticated attackers to execute arbitrary database queries. Attackers reaching the child node port can present the hardcoded key during WebSocket handshake, then dispatch SQL queries through the onWebSocketDataFromChildNode handler to read and modify user records and camera configuration.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 29, 2026

Last Modified

September 24, 2026

Advisory Details (5)

Auto-updated Oct 8, 2026
Fix referenced — no release confirmed yet.
Web page

Shinobi before commit 5a76c74f Arbitrary Database Query Execution via Hardcoded Child Node Key | Advisories | VulnCheck

https://www.vulncheck.com/advisories/shinobi-before-commit-5a76c74f-arbitrary-database-query-execution-via-hardcoded-child-node-key
Web page

libs/childNode/utils.js · f04e685b8bd4c6190fcd62993131b86a76c2b806 · Shinobi Systems / Shinobi · GitLab

https://gitlab.com/Shinobi-Systems/Shinobi/-/blob/f04e685b8bd4c6190fcd62993131b86a76c2b806/libs/childNode/utils.js
Web page

Shinobi Systems / Shinobi · GitLab

https://gitlab.com/Shinobi-Systems/Shinobi
Web page

Fix #560 : Child Node Vulnerability fix (5a76c74f) · Commits · Shinobi Systems / Shinobi · GitLab

https://gitlab.com/Shinobi-Systems/Shinobi/-/commit/5a76c74f3977661ff3f9fd55a260db352c0b19c0
Web page

Mass Fixes from Work Items (Issues) (!554) · Merge requests · Shinobi Systems / Shinobi · GitLab

https://gitlab.com/Shinobi-Systems/Shinobi/-/merge_requests/554

Vendor Advisories for CVE-2026-82448(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 29× in last 7d / 198× 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 100 of 327 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. None are among the latest 100 rows. The 227 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82448?
CVE-2026-82448 is a critical-severity vulnerability; its CVE record was published on August 29, 2026. Shinobi before commit 5a76c74f contains a hardcoded connection key in the child node service that allows unauthenticated attackers to execute arbitrary database queries. Attackers reaching the child node port can present the hardcoded key during WebSocket handshake, then dispatch SQL queries…
When was CVE-2026-82448 made public?
CVE-2026-82448 was made public on July 5, 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 29, 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-82448 actively exploited?
CVE-2026-82448 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82448?
CVE-2026-82448 has a CVSS base score of 9.8 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-82448?
A fix for CVE-2026-82448 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-82448 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82448?

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

Book a Demo →Browse All CVEs