CVE-2026-81675

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
9.3EG
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.4%CVSS: 9.3Exploit: 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).

The endpoint ‘/ws/apiprensa/getVideoUltimasSeccion’ contains an SQL injection vulnerability in the id_seccion parameter. The parameter is directly embedded in a complex SQL query that includes grouping and sorting operations. By injecting SQL syntax, an attacker can disrupt the query structure and cause database errors, exposing the internal logic of the queries. The complexity of the query increases the potential impact, as it could allow for broader manipulation of the content retrieval logic.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity93% × 45%
The EG Score, 9.3 of 10.
Exploitation0.4% × 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.4%
EPSS %ILE
35th
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 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

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

Multiple Vulnerabilities in TOOOLS' iSquad | INCIBE-CERT | INCIBE

https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-toools-isquad

Vendor Advisories for CVE-2026-81675(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 28× in last 7d / 184× 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 316 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 216 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81675?
CVE-2026-81675 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. The endpoint ‘/ws/apiprensa/getVideoUltimasSeccion’ contains an SQL injection vulnerability in the id_seccion parameter. The parameter is directly embedded in a complex SQL query that includes grouping and sorting operations. By injecting SQL syntax, an attacker can disrupt the query structure and…
When was CVE-2026-81675 made public?
CVE-2026-81675 was made public on August 27, 2026: that is the date its CVE record's CNA, Spanish National Cybersecurity Institute, S.A. (INCIBE), gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-81675 actively exploited?
CVE-2026-81675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81675?
CVE-2026-81675 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-81675?
A fix for CVE-2026-81675 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-81675 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81675?

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

Book a Demo →Browse All CVEs