dbcve.org
Alfresco Transform ServiceApplication · Hyland

CVE-2026-26337

HIGH · 8.2 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 4.3 / 5.3.0 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Hyland Alfresco Transformation Service allows unauthenticated attackers to achieve both arbitrary file read and server-side request forgery through the absolute path traversal.

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

Hyland Alfresco Transformation Service contains an absolute path traversal vulnerability that allows unauthenticated attackers to read arbitrary files on the server filesystem and perform server-side request forgery (SSRF) attacks. The vulnerability stems from insufficient validation of file path inputs, enabling attackers to specify absolute paths to access sensitive files or make arbitrary HTTP requests through the affected service.

MitigationImplement strict input validation and path sanitization to restrict file access to allowed directories and prevent path traversal sequences. Consider adding authentication requirements and network segmentation to limit the attack surface for this service.

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
Alfresco Transform ServiceApplication
Affected:< 4.3
Alfresco Transform CoreApplication
Affected:< 5.3.0= 5.3.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 checks

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

  1. Identify Hyland Alfresco Transform Service version
    Locate the installation directory and check the version file or use the product's version command. Common locations include the service configuration or logs. Compare the installed version number against the affected range of versions prior to 4.3.
    Affected if The installed version is lower than 4.3 (for example, 4.0, 4.1, 4.2)
  2. Identify Hyland Alfresco Transform Core version
    Locate the Transform Core component and check its version. This may be a separate module or service. Compare against the affected ranges of versions prior to 5.3.0 or equal to 5.3.0.
    Affected if The installed version is lower than 5.3.0 or exactly 5.3.0 (for example, 5.0, 5.1, 5.2, or 5.3.0)
  3. Confirm transformation service is network accessible
    Determine if the transformation service API endpoints are exposed to the network. Check firewall rules, service binding configuration, and network access controls. The vulnerability is exploitable by unauthenticated attackers if the service is reachable over the network.
    Affected if The transformation service is accessible from untrusted networks without authentication barriers
  4. Inspect transformation endpoint path parameters
    If accessible, examine the transformation service API endpoints that accept file or path parameters. Look for endpoints that process transformation requests where absolute file paths could be supplied as input.
    Affected if The service accepts path parameters in transformation requests without validation preventing absolute paths

A user is affected if their environment runs Hyland Alfresco Transform Service below version 4.3 or Transform Core below version 5.3.0 (or exactly 5.3.0) and the transformation service is network-accessible with endpoints that accept path parameters.

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.

dbcve · scoped
Upgrade available Upgrade to 4.3 / 5.3.0 or later
Fixed in 4.35.3.0
Interim mitigation

Implement strict input validation and path sanitization to restrict file access to allowed directories and prevent path traversal sequences. Consider adding authentication requirements and network segmentation to limit the attack surface for this service.

Recommended fix High confidence

Alfresco Transform Service >= 4.3; Alfresco Transform Core >= 5.3.1

  1. Identify the exact Alfresco Transform Service and Transform Core versions currently deployed
  2. For Alfresco Transform Service: upgrade to version 4.3 or later
  3. For Alfresco Transform Core: upgrade to version 5.3.1 or later
  4. Verify the upgrade in a non-production environment first
  5. Test that transformation workflows function correctly after upgrade
  6. Deploy the updated versions to production
Caveat Review release notes for any breaking changes between current version and target fixed version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Alfresco Transform Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26337 — 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-26337 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