CVE-2026-104875

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 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
Elevated

Also known asEUVD-2026-100469 (ENISA EUVD)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate 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.4%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

Ente provides end-to-end encrypted cloud services and security tools. Prior to server image 2026.07.09, the POST /emergency-contacts/approve-recovery endpoint authorized approval using a client-supplied userID and updated an emergency recovery session using only its client-supplied recovery-session UUID. An accepted emergency contact could submit the contact's own identifier, transition the victim's session from WAITING to READY, clear wait_till, retrieve recovery information, and continue account recovery before the owner-configured notice period expired. Exploitation of the approval bypass required the victim to have previously added and accepted the attacker as an emergency contact, and it did not create recovery rights for an arbitrary account. Separately, the same insufficiently scoped update pattern affected the reject and stop recovery transitions, allowing a user who knew another recovery-session UUID to potentially cancel a session to which the user was not a party. This issue is fixed in server image 2026.07.09.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

The score's inputs: 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

October 13, 2026

Last Modified

October 29, 2026

Advisory Details (5)

Auto-updated Oct 16, 2026
🔬 Proof of concept available. Fix named in the CVE record. Sources: github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Accepted emergency contact can bypass the recovery notice period · Advisory · ente/ente · GitHub

https://github.com/ente/ente/security/advisories/GHSA-2hxj-953x-c2vw
GitHub pull request

[server] Reuse emergency recovery status update path

Fix merged in ente/ente PR #11342 on 2026-07-09 — awaiting tagged release

https://github.com/ente/ente/pull/11342
GitHub pull request

[server] Additional check + test

Fix merged in ente/ente PR #11311 on 2026-07-08 — awaiting tagged release

https://github.com/ente/ente/pull/11311
GitHub commit

commit b3fa9f566466 (ente/ente)

Fix landed in ente/ente commit b3fa9f566466 — awaiting tagged release

https://github.com/ente/ente/commit/b3fa9f566466ac3660e276a67621130d684957e7
GitHub commit

commit 1fc4956f9027 (ente/ente)

Fix landed in ente/ente commit 1fc4956f9027 — awaiting tagged release

https://github.com/ente/ente/commit/1fc4956f90277076559c16dedbfad10cb4d1227b

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 29× 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-11-02 16:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  6. 2026-10-29 15:26 UTCEG score recompute
  7. 2026-10-29 14:53 UTCEG score recompute
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  12. 2026-10-25 14:55 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  14. 2026-10-24 00:38 UTCEG score recompute
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  21. 2026-10-18 05:09 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  23. 2026-10-16 20:08 UTCEG score recompute
  24. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 4 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-13 19:54 UTCEG score recompute
  3. 2026-10-13 19:19 UTCMITRE cvelistV5first tracked
  4. 2026-10-13 19:16 UTCEG score recomputeFirst assessed: 7.1 HIGH

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-104875?
CVE-2026-104875 is a high-severity vulnerability; its CVE record was published on October 13, 2026. Ente provides end-to-end encrypted cloud services and security tools. Prior to server image 2026.07.09, the POST /emergency-contacts/approve-recovery endpoint authorized approval using a client-supplied userID and updated an emergency recovery session using only its client-supplied recovery-session…
When was the CVE record for CVE-2026-104875 published?
The CVE record for CVE-2026-104875 was published on October 13, 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 29, 2026; the record at its source may have been updated since.
Is CVE-2026-104875 actively exploited?
CVE-2026-104875 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-104875?
CVE-2026-104875 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104875?
The CVE record for CVE-2026-104875 names the fix: "This issue is fixed in server image 2026.07.09."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-104875?

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

Book a Demo →Browse All CVEs