CVE-2026-12686

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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

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

An authenticated user could manipulate a company ID parameter in a POST request to the backend to gain unauthorised access to other companies hosted within the same subdomain environment. The application does not adequately verify whether the requested company ID belongs to the authenticated user’s session, resulting in a cross-tenant authorisation bypass. If this vulnerability is successfully exploited, it allows unauthorised access to sensitive customer information, including billing data, and may enable the unauthorised modification of third-party data.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
42
EG Risk 42/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% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 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 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

July 6, 2026

Last Modified

July 6, 2026

Advisory Details (1)

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

Incorrect authorisation in Adiss’s Biloop | INCIBE-CERT | INCIBE

https://www.incibe.es/en/incibe-cert/notices/aviso/incorrect-authorisation-adisss-biloop

Vendor Advisories for CVE-2026-12686(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 10× in last 7d / 38× 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 371 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 271 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12686?
CVE-2026-12686 is a critical-severity vulnerability; its CVE record was published on July 6, 2026. An authenticated user could manipulate a company ID parameter in a POST request to the backend to gain unauthorised access to other companies hosted within the same subdomain environment. The application does not adequately verify whether the requested company ID belongs to the authenticated user’s…
When was CVE-2026-12686 made public?
CVE-2026-12686 was made public on July 6, 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 July 6, 2026. EchelonGraph's copy of the record carries a last-modified date of July 6, 2026; the record at its source may have been updated since.
Is CVE-2026-12686 actively exploited?
CVE-2026-12686 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12686?
CVE-2026-12686 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-12686?
No fix for CVE-2026-12686 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-12686 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-12686?

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

Book a Demo →Browse All CVEs