CVE-2025-44594
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedhalo v2.20.17 and before is vulnerable to server-side request forgery (SSRF) in /apis/uc.api.storage.halo.run/v1alpha1/attachments/-/upload-from-url.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an SSRF vulnerability in Halo's attachment upload feature. The endpoint /apis/uc.api.storage.halo.run/v1alpha1/attachments/-/upload-from-url accepts a user-provided URL and fetches content from it server-side without proper validation, allowing attackers to make the server request internal resources, cloud metadata services, or internal network endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.20.17CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Halo installation versionLocate the installed Halo version from the admin dashboard (typically in About or System Information section), startup logs, or the manifest/configuration files in the installation directory. Compare the version number against the affected range.Affected if The installed version is 2.20.17 or lower.
-
Confirm upload-from-url API endpoint is presentCheck the available API routes or documentation for the endpoint /apis/uc.api.storage.halo.run/v1alpha1/attachments/-/upload-from-url. This may be visible in API documentation, route configuration, or by inspecting network traffic when accessing the attachments section.Affected if The upload-from-url endpoint exists and is accessible in the API.
-
Determine if attachment upload feature is enabledReview Halo's configuration settings related to storage and attachments (typically found in the admin panel under Storage, Attachments, or System Configuration settings). Verify whether the upload-from-url functionality has been explicitly disabled or is available to users.Affected if The upload-from-url feature is enabled and accessible to users or attackers.
-
Assess network exposure of the vulnerable endpointCheck whether the API endpoint is exposed to untrusted users or the internet. Review authentication requirements and access control policies for the /apis/uc.api.storage.halo.run endpoint.Affected if The endpoint is accessible without strong authentication or from untrusted network contexts.
You are affected if your Halo version is 2.20.17 or lower AND the upload-from-url feature is enabled and accessible in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a Halo version after v2.20.17. If no patch is available, disable the upload-from-url feature or implement strict URL allowlisting (block internal IPs, cloud metadata endpoints) at the network level.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-44594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-44594 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data