CVE-2026-96330

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreHIGH confidence

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-09. A secondary CVSS source baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.3Exploit: None knownExposed services: Not assessed

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

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in tagDiv tagDiv Opt-In Builder td-subscription allows Blind SQL Injection.This issue affects tagDiv Opt-In Builder: from n/a through 1.7.6.

CVSS v3
9.3
EG Score
9.3CRITICALhigh confidence
EG Risk
46
EG Risk 46/100CISA SSVC

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
Severity93% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 9, 2026

Last Modified

October 9, 2026

Advisory Details (1)

Auto-updated Oct 9, 2026
No fix on record yet.

Vendor Advisories for CVE-2026-96330(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 17× in last 7d / 17× 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.

  1. 2026-10-11 08:35 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  2. 2026-10-11 04:16 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  3. 2026-10-10 23:58 UTCEG score recompute
  4. 2026-10-10 23:58 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  6. 2026-10-10 19:39 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  7. 2026-10-10 15:21 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  8. 2026-10-10 11:03 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  9. 2026-10-10 06:45 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  10. 2026-10-10 02:27 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  11. 2026-10-09 22:09 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  12. 2026-10-09 17:51 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  13. 2026-10-09 13:33 UTCEG score recompute
  14. 2026-10-09 13:33 UTCGHSA enrichmentGHSA-hqjj-cvjq-q9rv · GitHub severity CRITICAL · GitHub CVSS 9.3
  15. 2026-10-09 10:36 UTCEG score recompute
  16. 2026-10-09 10:12 UTCEG score recompute
  17. 2026-10-09 10:08 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-96330?
CVE-2026-96330 is a critical vulnerability published on October 9, 2026. Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in tagDiv tagDiv Opt-In Builder td-subscription allows Blind SQL Injection.This issue affects tagDiv Opt-In Builder: from n/a through 1.7.6.
When was the CVE record for CVE-2026-96330 published?
The CVE record for CVE-2026-96330 was published on October 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-96330 actively exploited?
CVE-2026-96330 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96330?
CVE-2026-96330 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96330?
No fix for CVE-2026-96330 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-96330 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-96330?

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