CVE-2026-61448

LOWPre-NVD 2.12.1
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 2.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
2.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 2.1Exploit: None knownExposed 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 parse-community parse-server versions 9.0.0 up to but not including 9.10.0-alpha.2 and before 8.6.84 as affected, and parse-community parse-server versions 9.10.0-alpha.2 and 8.6.84 as unaffected. No release containing a fix is confirmed on record.

Parse Server is affected by a stored cross-site scripting (XSS) vulnerability in versions >= 9.0.0, < 9.10.0-alpha.2 and <= 8.6.83. When an uploaded file's extension is not recognized by the mime package, Parse Server preserves the client-supplied Content-Type. A malformed Content-Type that is not a valid type/subtype media type (e.g., 'image', 'image/', or 'image//svg+xml') bypasses the fileUpload.fileExtensions blocklist and is stored unchanged. On storage adapters that persist and serve the uploaded Content-Type (such as Amazon S3, Google Cloud Storage, or Azure Blob Storage), a browser cannot parse the malformed value and falls back to MIME-sniffing; a file whose body begins with HTML is rendered as HTML, executing embedded script in the application's origin against other users who open the file URL. The default GridFS storage adapter is not affected. Fixed in 9.10.0-alpha.2 and 8.6.84.

CVSS v3
2.1
EG Score
2.1LOWmedium confidence
EG Risk
10
EG Risk 10/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity21% × 45%
The EG Score, 2.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (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.

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

July 11, 2026

Last Modified

July 14, 2026

Vendor Advisories for CVE-2026-61448(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 11× in last 7d / 33× 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 98 of 131 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 33 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-61448?
CVE-2026-61448 is a low-severity vulnerability; its CVE record was published on July 11, 2026. Parse Server is affected by a stored cross-site scripting (XSS) vulnerability in versions >= 9.0.0, < 9.10.0-alpha.2 and <= 8.6.83. When an uploaded file's extension is not recognized by the mime package, Parse Server preserves the client-supplied Content-Type. A malformed Content-Type that is not…
When was CVE-2026-61448 made public?
CVE-2026-61448 was made public on June 25, 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 July 11, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-61448 actively exploited?
CVE-2026-61448 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61448?
CVE-2026-61448 has a CVSS base score of 2.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-61448?
No fix for CVE-2026-61448 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 parse-community parse-server versions 9.0.0 up to but not including 9.10.0-alpha.2 and before 8.6.84 as affected, and parse-community parse-server versions 9.10.0-alpha.2 and 8.6.84 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-61448 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-61448?

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