dbcve.org
Alfresco Transform ServiceApplication · Hyland

CVE-2026-26339

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 4.2.3 / 5.2.4 or later.
See remediation →
100/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 remote code execution through the argument injection vulnerability, which exists in the document processing functionality.

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 argument injection vulnerability in its document processing functionality that allows unauthenticated attackers to inject malicious arguments, leading to remote code execution. The lack of input validation on document processing arguments enables attackers to execute arbitrary commands on the underlying system.

MitigationImplement strict input validation and parameterized command execution for all document processing operations, enforce authentication requirements, and restrict service permissions to minimize impact if exploited.

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.2.3
Alfresco Transform CoreApplication
Affected:< 5.2.4

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
High
Availability
High

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

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. Check Hyland Alfresco Transform Service version
    Locate and inspect the installed version of Hyland Alfresco Transform Service in the product documentation, installation directory, or version file. Compare it against the affected range.
    Affected if Version is below 4.2.3
  2. Check Hyland Alfresco Transform Core version
    Locate and inspect the installed version of Hyland Alfresco Transform Core in the product documentation, installation directory, or version file. Compare it against the affected range.
    Affected if Version is below 5.2.4
  3. Verify network exposure of the transformation service
    Determine if the Alfresco Transformation Service is listening on network interfaces accessible from untrusted networks. Check firewall rules, service binding configurations, and network ACLs.
    Affected if The transformation service is exposed to untrusted or unauthenticated network access
  4. Confirm authentication status on transformation service endpoints
    Inspect the authentication configuration for the transformation service to verify whether authentication is required and properly enforced for document processing operations.
    Affected if Authentication is disabled or not required for transformation service endpoints

A user is affected if either Transform Service is below 4.2.3 or Transform Core is below 5.2.4 AND the service is accessible to unauthenticated attackers without proper network or authentication controls.

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.2.3 / 5.2.4 or later
Fixed in 4.2.35.2.4
Interim mitigation

Implement strict input validation and parameterized command execution for all document processing operations, enforce authentication requirements, and restrict service permissions to minimize impact if exploited.

Recommended fix Moderate confidence

Alfresco Transform Service 4.2.3 / Alfresco Transform Core 5.2.4

  1. 1. Identify which Alfresco transform component is deployed: Alfresco Transform Service or Alfresco Transform Core
  2. 2. For Alfresco Transform Service: upgrade to version 4.2.3 or later
  3. 3. For Alfresco Transform Core: upgrade to version 5.2.4 or later
  4. 4. Review Hyland official release notes and documentation for upgrade prerequisites
  5. 5. Backup current installation and configuration before upgrading
  6. 6. Apply the upgrade following Hyland's standard upgrade procedures
  7. 7. Verify the transform service is functioning correctly after upgrade
Caveat Review release notes for any breaking changes between current version and target 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
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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