CVE-2026-53662

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (22nd 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-38551 (ENISA EUVD)Source: ENISA EUVD

9.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: 9.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.

immich is a high performance self-hosted photo and video management solution. From commit 4ffa26c9 until 4eb1003, a reflected cross-site scripting (XSS) vulnerability on the /auth/login page allows an attacker to fully compromise any authenticated user's account with a single link click. The continue query parameter is read from the URL and passed to SvelteKit's redirect() without any scheme or origin validation, allowing attacker-controlled JavaScript to execute inside Immich's origin. The payload then uses the victim's existing session to mint an all-permission API key on their account, leading to persistent account takeover. This vulnerability is fixed in commit 4eb1003.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.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.
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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.3%
EPSS %ILE
22nd
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 (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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: 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.

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

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.

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

June 23, 2026

Last Modified

October 25, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
No fix on record yet. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

One-click account takeover via XSS in login page continue redirect · Advisory · immich-app/immich · GitHub

https://github.com/immich-app/immich/security/advisories/GHSA-8244-8vpr-vp9c
GitHub commit

commit 4eb100327ea5 (immich-app/immich)

Fix landed in immich-app/immich commit 4eb100327ea5 — awaiting tagged release

https://github.com/immich-app/immich/commit/4eb100327ea5da2e90381b96809f1f1cc51cc7e3

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 49× 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 179 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 79 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53662?
CVE-2026-53662 is a critical-severity vulnerability; its CVE record was published on June 23, 2026. immich is a high performance self-hosted photo and video management solution. From commit 4ffa26c9 until 4eb1003, a reflected cross-site scripting (XSS) vulnerability on the /auth/login page allows an attacker to fully compromise any authenticated user's account with a single link click. The…
When was the CVE record for CVE-2026-53662 published?
The CVE record for CVE-2026-53662 was published on June 23, 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 25, 2026; the record at its source may have been updated since.
Is CVE-2026-53662 actively exploited?
CVE-2026-53662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53662?
CVE-2026-53662 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53662?
No fix for CVE-2026-53662 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53662?

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

Book a Demo →Browse All CVEs