CVE-2025-44593: Halo prior to 2.20.13 allows bypassing file type detection and uploading malicious files such as .exe and .htm

Q: How do I fix CVE-2025-44593?

halo: upgrade to 2.20.13. Exact commands for each OS are on this page.

Q: Is CVE-2025-44593 being exploited?

CVE-2025-44593 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-44593 affect?

CVE-2025-44593 affects halo. Severity is medium (CVSS 6.1). Halo prior to 2.20.13 allows bypassing file type detection and uploading malicious files such as .exe and .html files. Specifically, .html files can trigger stored XSS vulnerabilities. This vulnerability is fixed in 2.20.13

Q: How urgent is CVE-2025-44593?

Priority 26/100. No elevated risk signals yet.

Routine

MEDIUM 6.1UPGRADE

CVE-2025-44593 is a medium-severity flaw (CVSS 6.1) affecting halo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Halo prior to 2.20.13 allows bypassing file type detection and uploading malicious files such as .exe and .html files. Specifically, .html files can trigger stored XSS vulnerabilities. This vulnerability is fixed in 2.20.13

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 83%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-09-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: halo

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-09-09 21:15 UTCPublished CVE record published
2026-06-17 09:25 UTCUpdated Record last modified

halo halo UPGRADE

Affected: < 2.20.13

Fixed in: 2.20.13

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy halo || rpm -q halo || halo --version

2. UPGRADE to 2.20.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade halo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade halo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-44593?

halo: upgrade to 2.20.13. Exact commands for each OS are on this page.

Is CVE-2025-44593 being exploited?

CVE-2025-44593 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-44593 affect?

CVE-2025-44593 affects halo. Severity is medium (CVSS 6.1). Halo prior to 2.20.13 allows bypassing file type detection and uploading malicious files such as .exe and .html files. Specifically, .html files can trigger stored XSS vulnerabilities. This vulnerability is fixed in 2.20.13

How urgent is CVE-2025-44593?

Priority 26/100. No elevated risk signals yet.

Related CVEs

CVE-2025-14117 MEDIUM 4.3 DOWNGRADE A vulnerability has been found in fit2cloud Halo 2.21.10
CVE-2025-15141 LOW 3.1 UPGRADE A vulnerability was determined in Halo up to 2.21.10
CVE-2025-70886 HIGH 7.5 UPGRADE An issue in halo v.2.22.4 and before allows a remote attacker to cause a denial of service via a crafted paylo
CVE-2025-44595 MEDIUM 6.1 UPGRADE Halo v2.20.17 and before is vulnerable to Cross Site Scripting (XSS) in /halo_host/archives/{name}.
CVE-2025-44594 CRITICAL 9.1 UPGRADE halo v2.20.17 and before is vulnerable to server-side request forgery (SSRF) in /apis/uc.api.storage.halo.run/

References

← Back to latest CVEs