CVE-2026-57449

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.3% (17th 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-87369 (ENISA EUVD) · GHSA-m62c-5q34-f3cf (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Actual is a local-first personal finance tool. Prior to 26.7.0, Actual Sync Server's CORS proxy is intended to let authenticated users fetch resources only from repositories listed in the official plugin allowlist. When ACTUAL_GITHUB_TOKEN is configured, the proxy automatically attaches the server's GitHub token to GitHub requests. The GitHub API allowlist check uses a raw startsWith() prefix test for /repos/{owner}/{repo} without requiring a path boundary after the repository name. If an allowlisted public plugin repository is https://github.com/acme/plugin, the proxy also accepts GitHub API URLs. Those URLs are outside the allowlisted repository but still pass because their API path starts with /repos/acme/plugin. The proxy then forwards the request with the server's ACTUAL_GITHUB_TOKEN, allowing any authenticated Actual user to read private GitHub resources reachable by that token. Version 26.7.0 fixes the issue.

CVSS
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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
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
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 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 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

September 25, 2026

Last Modified

September 28, 2026

Advisory Details (1)

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

CORS Proxy GitHub API Allowlist Prefix Bypass Leaks Private Repositories Through the Server GitHub Token · Advisory · actualbudget/actual · GitHub

https://github.com/actualbudget/actual/security/advisories/GHSA-m62c-5q34-f3cf

Vendor Advisories for CVE-2026-57449(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@actual-app/sync-server @ 26.7.0 (fixes <= 26.6.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-11-07 17:06 UTCEchelonGraph re-scored
  7. 2026-11-07 17:06 UTCGHSA enrichmentGHSA-m62c-5q34-f3cf · GitHub severity HIGH
  8. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-11-01 07:42 UTCGHSA enrichmentGHSA-m62c-5q34-f3cf · GitHub severity HIGH
  16. 2026-11-01 07:42 UTCEchelonGraph re-scored
  17. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-10-31 08:30 UTCEchelonGraph re-scored
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-10-25 14:17 UTCEchelonGraph re-scored
Show 55 more
  1. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-23 23:54 UTCEchelonGraph re-scored
  3. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-18 03:28 UTCEchelonGraph re-scored
  9. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-16 15:12 UTCEchelonGraph re-scored
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-12 15:54 UTCEchelonGraph re-scored
  17. 2026-10-11 19:37 UTCEchelonGraph re-scored
  18. 2026-10-11 16:52 UTCEchelonGraph re-scored
  19. 2026-10-11 14:15 UTCEchelonGraph re-scored
  20. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-11 06:09 UTCEchelonGraph re-scored
  22. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-09 20:29 UTCEchelonGraph re-scored
  24. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-08 22:01 UTCEchelonGraph re-scored
  26. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  27. 2026-10-08 10:46 UTCEchelonGraph re-scored
  28. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-10-07 00:56 UTCEchelonGraph re-scored
  30. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-10-06 02:29 UTCEchelonGraph re-scored
  32. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  33. 2026-10-05 03:47 UTCEchelonGraph re-scored
  34. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  35. 2026-10-03 18:07 UTCEchelonGraph re-scored
  36. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-10-02 19:32 UTCEchelonGraph re-scored
  38. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  39. 2026-10-01 21:06 UTCEchelonGraph re-scored
  40. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  41. 2026-09-30 22:39 UTCEchelonGraph re-scored
  42. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  43. 2026-09-30 00:11 UTCEchelonGraph re-scored
  44. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-09-29 01:39 UTCEchelonGraph re-scored
  46. 2026-09-28 14:26 UTCEchelonGraph re-scored
  47. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  48. 2026-09-28 13:27 UTCEchelonGraph re-scored
  49. 2026-09-27 20:22 UTCEchelonGraph re-scored
  50. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  51. 2026-09-26 21:52 UTCEchelonGraph re-scored
  52. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  53. 2026-09-25 23:22 UTCEchelonGraph re-scored
  54. 2026-09-25 22:28 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
  55. 2026-09-25 22:24 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-57449?
CVE-2026-57449 is a high-severity vulnerability; its CVE record was published on September 25, 2026. Actual is a local-first personal finance tool. Prior to 26.7.0, Actual Sync Server's CORS proxy is intended to let authenticated users fetch resources only from repositories listed in the official plugin allowlist. When ACTUAL_GITHUB_TOKEN is configured, the proxy automatically attaches the…
When was the CVE record for CVE-2026-57449 published?
The CVE record for CVE-2026-57449 was published on September 25, 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 September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-57449 actively exploited?
CVE-2026-57449 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57449?
CVE-2026-57449 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-57449?
A fix for CVE-2026-57449 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57449 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57449?

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

Book a Demo →Browse All CVEs