CVE-2026-110769

HIGHPre-NVD 8.68.6
EchelonGraph scoreHIGH confidence

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

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-10-14. A secondary CVSS source baseline 8.6; 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 weekElevated
8.6EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists holaboss-ai holaOS versions up to and including 2026.822.1 as affected. No release containing a fix is confirmed on record.

holaOS through 2026.822.1 contains a missing authorization vulnerability in channel-gateway connectors that allows any messaging-platform user to submit agent tasks because the #isAllowed check accepts all senders when the default allowFrom list is empty. Attackers who can message the operator's Telegram, Slack, Discord, or other bot can have ChannelIngress.handle pass turns to the workspace agent, running configured tools on the operator's machine.

CVSS v3
8.6
EG Score
8.6HIGHhigh confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; 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 public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

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

October 14, 2026

Last Modified

October 15, 2026

Advisory Details (4)

Auto-updated Oct 14, 2026
No fix on record yet.
Web page

holaOS through 2026.822.1 Missing Authorization in Channel-Gateway Connectors | Advisories | VulnCheck

https://www.vulncheck.com/advisories/holaos-through-2026.822.1-missing-authorization-in-channel-gateway-connectors
Web page

GitHub - holaboss-ai/holaOS: Open-source agentic workspace enterprises can make their own. Connect the systems you already run — 100+ integrations, MCP, chat tools, apps, browser, local files — with shared memory. Any agent (Claude Code, Codex), any model, or BYOK. Set up in clicks, not months. Local-first: your data never leaves your machines. · GitHub

https://github.com/holaboss-ai/holaOS
Web page

holaOS/runtime/channel-gateway/src/connectors/telegram.ts at 4684714ee133794cdbb86630e42b7d93447fb2e2 · holaboss-ai/holaOS · GitHub

https://github.com/holaboss-ai/holaOS/blob/4684714ee133794cdbb86630e42b7d93447fb2e2/runtime/channel-gateway/src/connectors/telegram.ts#L488
Web page

holaOS channel-gateway: IM connectors authorize every sender by default, and allowlists match mutable usernames - HackMD

https://hackmd.io/@hieuPenguinnn/holaos-channel-gateway-allow-all-sender-default

Vendor Advisories for CVE-2026-110769(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 16× in last 7d / 19× 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-21 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-20 19:09 UTCEG score recompute
  3. 2026-10-20 19:09 UTCGHSA enrichmentGHSA-v8pm-qrjg-7q78 · GitHub severity HIGH · GitHub CVSS 8.6
  4. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-18 05:06 UTCEG score recompute
  8. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-10-15 15:26 UTCEG score recompute
  12. 2026-10-15 15:26 UTCGHSA enrichmentGHSA-v8pm-qrjg-7q78 · GitHub severity HIGH · GitHub CVSS 8.6
  13. 2026-10-15 15:07 UTCEG score recompute
  14. 2026-10-15 15:07 UTCGHSA enrichmentGHSA-v8pm-qrjg-7q78 · GitHub severity HIGH · GitHub CVSS 8.6
  15. 2026-10-15 14:40 UTCEG score recompute
  16. 2026-10-15 14:40 UTCGHSA enrichmentGHSA-v8pm-qrjg-7q78 · GitHub severity HIGH · GitHub CVSS 8.6
  17. 2026-10-14 19:33 UTCEG score recompute
  18. 2026-10-14 18:57 UTCEG score recomputeFirst assessed: 8.6 HIGH
  19. 2026-10-14 18:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-110769?
CVE-2026-110769 is a high-severity vulnerability; its CVE record was published on October 14, 2026. holaOS through 2026.822.1 contains a missing authorization vulnerability in channel-gateway connectors that allows any messaging-platform user to submit agent tasks because the #isAllowed check accepts all senders when the default allowFrom list is empty. Attackers who can message the operator's…
When was CVE-2026-110769 made public?
CVE-2026-110769 was made public on October 14, 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 October 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-110769 actively exploited?
CVE-2026-110769 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-110769?
CVE-2026-110769 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-110769?
No fix for CVE-2026-110769 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 CVE record's CNA (VulnCheck) lists holaboss-ai holaOS versions up to and including 2026.822.1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-110769 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-110769?

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