CVE-2026-76073

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
8.8EG
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.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

Label Studio does not scope the annotation detail endpoint to the requesting user's organization. AnnotationAPI in label_studio/tasks/api.py declares queryset = Annotation.objects.all() and provides no get_queryset override, so the default lookup retrieves any annotation by primary key. The view's permission_required entries name annotations.view, annotations.change and annotations.delete, and label_studio/core/permissions.py registers every permission with rules.is_authenticated, so the check is satisfied by any logged-in account and no object-level organization test runs. The sibling task endpoint does constrain its queryset with project__organization set to the requester's active organization, which is the boundary this path omits. Annotation identifiers are sequential integers, so an authenticated user of one organization can enumerate identifiers to read, modify and delete annotations belonging to other organizations on the same instance. The same unscoped queryset appears on AnnotationConvertAPI in the same file.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.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 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.5%
EPSS %ILE
42nd
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

August 24, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Aug 24, 2026
No fix on record yet.
Web page

Label Studio through 1.23.0 Cross-Organization Annotation Access via Unscoped AnnotationAPI Queryset | Advisories | VulnCheck

https://www.vulncheck.com/advisories/label-studio-through-cross-organization-annotation-access-via-unscoped-annotationapi-queryset
Web page

label-studio/label_studio/tasks/api.py at 1.23.0 · HumanSignal/label-studio · GitHub

https://github.com/HumanSignal/label-studio/blob/1.23.0/label_studio/tasks/api.py
Web page

IDOR in /api/annotations/{id}/ allows cross-organization read, modify, and delete of annotation data · Issue #9796 · HumanSignal/label-studio · GitHub

https://github.com/HumanSignal/label-studio/issues/9796
Web page

GitHub - HumanSignal/label-studio: Label Studio is a multi-type data labeling and annotation tool with standardized output format · GitHub

https://github.com/HumanSignal/label-studio

Vendor Advisories for CVE-2026-76073(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 21× in last 7d / 102× 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 174 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 74 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-76073?
CVE-2026-76073 is a high-severity vulnerability; its CVE record was published on August 24, 2026. Label Studio does not scope the annotation detail endpoint to the requesting user's organization. AnnotationAPI in labelstudio/tasks/api.py declares queryset = Annotation.objects.all() and provides no getqueryset override, so the default lookup retrieves any annotation by primary key. The view's…
When was CVE-2026-76073 made public?
CVE-2026-76073 was made public on August 24, 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 24, 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-76073 actively exploited?
CVE-2026-76073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76073?
CVE-2026-76073 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76073?
No fix for CVE-2026-76073 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-76073 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76073?

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