dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-5623

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability was identified in hcengineering Huly Platform 0.7.382. This affects an unknown part of the file server/front/src/index.ts of the component Import Endpoint. Such manipulation leads to server-side request forgery. The attack can be launched remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

Server-side request forgery (SSRF) vulnerability in hcengineering Huly Platform version 0.7.382 within the Import Endpoint component of the file server (server/front/src/index.ts). The vulnerability allows remote attackers to make the server perform arbitrary requests to internal or external resources by manipulating input to the import functionality.

MitigationImplement strict input validation and URL allowlisting for the import endpoint to prevent arbitrary URL fetching. Additionally, apply network segmentation and restrict outbound connections from the server to internal infrastructure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Huly Platform installation
    Check if Huly Platform is deployed in your environment by searching for running processes, containers, or services named 'huly' or by inspecting web server configurations for routes serving the Huly application.
    Affected if Huly Platform is installed and running in your environment
  2. Determine the installed version
    Check the version of Huly Platform by inspecting package.json, Docker image tags, or the application itself (often displayed in UI footer, /about page, or via API endpoint). Compare against version 0.7.382.
    Affected if The installed version is 0.7.382 exactly, or falls within a range including 0.7.382 where the vulnerability is present
  3. Verify the Import Endpoint is accessible
    Locate the import functionality endpoint in your Huly deployment. Check if routes handling file import (typically /import or similar paths in file server/front/src/index.ts) are exposed and accessible to users or attackers.
    Affected if The Import Endpoint is exposed and accessible without strict authentication or network restrictions
  4. Inspect import feature configuration
    Review the import feature configuration in your deployment to determine if input validation or URL allowlisting is applied. Check environment variables, config files, or API settings related to import functionality.
    Affected if No URL allowlisting or input validation is configured for the import endpoint, making arbitrary URL submissions possible
  5. Check network egress configuration
    Examine outbound network rules, firewall policies, or network segmentation applied to the server hosting Huly Platform. Determine if the server can make arbitrary HTTP requests to internal or external resources.
    Affected if The server has unrestricted outbound network access, allowing SSRF-triggered requests to internal services or metadata endpoints

You are affected if Huly Platform version 0.7.382 (or a vulnerable version) is running, the Import Endpoint is accessible, and no URL allowlisting or network restrictions are in place to block arbitrary requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and URL allowlisting for the import endpoint to prevent arbitrary URL fetching. Additionally, apply network segmentation and restrict outbound connections from the server to internal infrastructure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5623 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5623 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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