How many CVEs have patched normalization?

1 published CVEs changed normalization in parse-community/parse-server, in 2 distinct patches totalling 17 changed lines, between 2026 and 2026.

What is the latest CVE that changed normalization?

CVE-2026-53724 (Parse Server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist), published 2026-06-12, changed lines 579 to 595 of src/Utils.js.

How does normalization compare to the rest of parse-community/parse-server?

parse-community/parse-server has 79 CVEs with a located fix in total; 1 of them changed normalization.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

parse-community/parse-server

Function

normalization

Name: normalization in parse-community/parse-server: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

src/Utils.js

Last patched June 12, 2026

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

17

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

normalization in parse-community/parse-server was changed by 1 published CVE fixes in 2026, in 2 distinct patches that added or removed 17 lines in total.

parse-community/parse-server has 79 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed normalization, newest first, with the lines each fix touched.

Parse Server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist
CVE-2026-53724 · lines 579–595 · +17 −0
Low · CVSS 2.1
EPSS 0.5%2026-06-12

Get an alert when the next CVE fix lands in parse-community/parse-server, with the patched functions.

Monitor parse-server CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1checkProhibitedKeywordssrc/Utils.js1 CVEs · 1 patches2023

Other hotspots in the repository

Functions in parse-community/parse-server changed by the most CVE fixes.

RestWrite5 CVEs · src/RestWrite.js then4 CVEs · src/RestQuery.js async3 CVEs · src/GraphQL/ParseGraphQLServer.js getStore3 CVEs · src/triggers.js verifyPublicKeyUrl3 CVEs · src/Adapters/Auth/gcenter.js fromEntries2 CVEs · src/RestWrite.js

All patched functions in parse-community/parse-server

Frequently asked questions

Common questions about CVE fixes to normalization.

How many CVEs have patched normalization?: 1 published CVEs changed normalization in parse-community/parse-server, in 2 distinct patches totalling 17 changed lines, between 2026 and 2026.
What is the latest CVE that changed normalization?: CVE-2026-53724 (Parse Server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist), published 2026-06-12, changed lines 579 to 595 of src/Utils.js.
How does normalization compare to the rest of parse-community/parse-server?: parse-community/parse-server has 79 CVEs with a located fix in total; 1 of them changed normalization.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track parse-community/parse-server CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing