CVE-2025-14117: A vulnerability has been found in fit2cloud Halo 2.21.10

Routine

MEDIUM 4.3DOWNGRADE

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

A vulnerability has been found in fit2cloud Halo 2.21.10. Impacted is an unknown function. The manipulation leads to cross-site request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 85%)
CISA exploited list	No
Weakness	CWE-352, CWE-862
Published	2025-12-06
Last modified	2026-10-15

Publisher (CNA): VulDB · Vendor: fit2cloud

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

Am I affected?

Timeline

2025-12-06 06:15 UTCPublished CVE record published
2026-10-15 20:10 UTCUpdated Record last modified

fit2cloud halo DOWNGRADE

Affected: 2.21.10

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.21.10

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 2.21.10 (Debian / Ubuntu)

apt-cache madison halo sudo apt install halo=<VERSION_BEFORE_2.21.10> sudo apt-mark hold halo

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list halo sudo dnf downgrade halo-<VERSION_BEFORE_2.21.10> sudo dnf versionlock add halo

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-14117?

halo: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-14117 being exploited?

CVE-2025-14117 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-14117 affect?

CVE-2025-14117 affects halo. Severity is medium (CVSS 4.3). A vulnerability has been found in fit2cloud Halo 2.21.10. Impacted is an unknown function. The manipulation leads to cross-site request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be u

How urgent is CVE-2025-14117?

Priority 24/100. Public exploit reference

Related CVEs

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/
CVE-2025-44593 MEDIUM 6.1 UPGRADE Halo prior to 2.20.13 allows bypassing file type detection and uploading malicious files such as .exe and .htm

References

← Back to latest CVEs