CVE-2026-26338
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 · uneditedHyland Alfresco Transformation Service allows unauthenticated attackers to achieve server-side request forgery (SSRF) through 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 confidenceHyland Alfresco Transformation Service contains a critical SSRF vulnerability in its document processing functionality. Unauthenticated attackers can send crafted document processing requests to cause the service to make arbitrary HTTP requests to internal or external resources, potentially exposing sensitive services and enabling further attacks.
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< 4.3< 5.3.0= 5.3.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Hyland Alfresco Transform Service versionLocate the ATS installation directory and check the version file or use the product's built-in version command. Common locations include /opt/alfresco-transform-service or similar installation paths. Compare the installed version number against the affected range: versions < 4.3 are vulnerable.Affected if Installed version is lower than 4.3
-
Identify Hyland Alfresco Transform Core versionLocate the ATC installation and check its version information. This is typically found in the transform core service directory or via the service's version endpoint. Compare against affected range: versions < 5.3.0 or exactly 5.3.0 are vulnerable.Affected if Installed version is lower than 5.3.0 or equals 5.3.0
-
Verify transformation service endpoint exposureCheck the network configuration and service bindings for the Alfresco Transform Service. Determine if the transformation endpoints (typically endpoints handling document conversion requests) are accessible without authentication. Review configuration files like application.properties or transform-service.yml for security settings around endpoint access.Affected if Transformation endpoints are accessible to unauthenticated users or untrusted networks
-
Confirm document transformation functionality is enabledReview the Alfresco repository configuration to verify that the transformation service connector is actively configured and enabled. Check if content transformation for documents is operational by testing a simple conversion or reviewing the service status.Affected if The transformation service is enabled and processing document requests from users or systems
-
Inspect outbound HTTP request capabilityReview network configuration to determine if the transform service host can make outbound HTTP/HTTPS requests to arbitrary URLs. Check firewall rules, proxy settings, and network ACLs that govern the service's ability to initiate outbound connections.Affected if The transform service has unrestricted outbound network access without URL allowlist validation
Your environment is affected if either Hyland Alfresco Transform Service is version < 4.3 OR Transform Core is version < 5.3.0 or exactly 5.3.0, AND the transformation endpoints are exposed without authentication AND the service can make outbound HTTP requests.
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.
dbcve · scoped4.35.3.0
Restrict network access to the transformation service, implement strict URL validation and allowlist controls for document processing endpoints, and apply available vendor patches immediately.
Alfresco Transform Service >= 4.3; Alfresco Transform Core >= 5.3.1
- 1. Identify the currently installed version of Alfresco Transform Service and Alfresco Transform Core in your environment
- 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. After upgrading, verify the SSRF vulnerability is remediated by testing document processing functionality
- 5. Ensure the upgraded services are running correctly and document transformations work as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26338 — 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-2026-26338 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