Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-61448Published 2026-07-11

CVE-2026-61448 — parse-community parse-server

low (derived)

As of 2026-07-11, CVE-2026-61448 is a Low-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in parse-community parse-server, CVSS v4.0 2.1, EPSS 0.2% (15.5th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-61448 as of 2026-07-11; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
2.1/10Low (derived)
EPSS
0.2%Higher than 15.5% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
1.7/10Threadlinqs triage score
Published
CVSS v4.0 2.1 (Low, derived from score) · EPSS 0.2% (higher than 15.5% of all scored CVEs) · Priority 1.7/10 · Published 2026-07-11

Last updated:

What is CVE-2026-61448?

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.

The record classifies CVE-2026-61448 under weakness class CWE-434. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 86 days ago.

Severity and exploitation probability

CVSS v4.0 base score
2.1 — Low (derived from score)
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 15.5% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
1.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-11

Is CVE-2026-61448 being exploited?

It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.

Affected products and versions

  • parse-community: parse-server

How to fix CVE-2026-61448

No vendor patch reference has been recorded for CVE-2026-61448 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-61448

No threat campaign in the Threadlinqs corpus currently references CVE-2026-61448, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Third-party advisory