CVE-2026-33318

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

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

8.8EG
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.5%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Actual is a local-first personal finance tool. Prior to version 26.4.0, any authenticated user (including BASIC role) can escalate to ADMIN on servers migrated from password authentication to OpenID Connect. Three weaknesses combine: POST /account/change-password has no authorization check, allowing any session to overwrite the password hash; the inactive password auth row is never removed on migration; and the login endpoint accepts a client-supplied loginMethod that bypasses the server's active auth configuration. Together these allow an attacker to set a known password and authenticate as the anonymous admin account created during the multiuser migration. The three weaknesses form a single, sequential exploit chain — none produces privilege escalation on its own. Missing authorization on POST /change-password allows overwriting a password hash, but only matters if there is an orphaned row to target. Orphaned password row persisting after migration provides the target row, but is harmless without the ability to authenticate using it. Client-controlled loginMethod: "password" allows forcing password-based auth, but is useless without a known hash established by step 1. All three must be chained in sequence to achieve the impact. No single weakness independently results in privilege escalation. The single root cause is the missing authorization check on /change-password; the other two are preconditions that make it exploitable. Version 26.4.0 contains a fix.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
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.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% 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.

A fix is available. 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.

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

April 24, 2026

Last Modified

October 26, 2026

Advisory Details (2)

Auto-updated May 2, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Privilege Escalation via 'change-password' Endpoint on OpenID-Migrated Servers · Advisory · actualbudget/actual · GitHub

https://github.com/actualbudget/actual/security/advisories/GHSA-prp4-2f49-fcgp
Web page

Release 26.4.0 | Actual Budget

https://actualbudget.org/blog/release-26.4.0

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@actual-app/sync-server—
  • every version up to 26.4.0: fixed in 26.4.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× 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 96 of 213 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-33318?
CVE-2026-33318 is a high-severity vulnerability; its CVE record was published on April 24, 2026. Actual is a local-first personal finance tool. Prior to version 26.4.0, any authenticated user (including BASIC role) can escalate to ADMIN on servers migrated from password authentication to OpenID Connect. Three weaknesses combine: POST /account/change-password has no authorization check,…
When was the CVE record for CVE-2026-33318 published?
The CVE record for CVE-2026-33318 was published on April 24, 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 26, 2026; the record at its source may have been updated since.
Is CVE-2026-33318 actively exploited?
CVE-2026-33318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33318?
CVE-2026-33318 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-33318?
A fix for CVE-2026-33318 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33318

Explore →

Is Your Infrastructure Affected by CVE-2026-33318?

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

Book a Demo →Browse All CVEs