# CVE-2026-26337: Hyland Alfresco Transformation Service Absolute Path Traversal Arbitrary File Read and SSRF


- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-3453-mrqq-23pm

## What is CVE-2026-26337?

CVE-2026-26337 is a high-severity vulnerability in Hyland Alfresco Community (Transform Core), published on 19 Feb 2026. 

### Official description

Hyland Alfresco Transformation Service allows unauthenticated attackers to achieve both arbitrary file read and server-side request forgery through the absolute path traversal.

Weakness: CWE-36 (Absolute Path Traversal)

## Which versions are affected by CVE-2026-26337?

It affects 2 products.


Products: Hyland Alfresco Transform Core, Hyland Alfresco Transform Service.

## How do I fix CVE-2026-26337?

No fix has been published for CVE-2026-26337 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-26337 being exploited?

There is no known exploitation of CVE-2026-26337 in the wild and no public exploit code.

## Other vulnerabilities in Hyland Alfresco Community (Transform Core)

- [CVE-2026-26339](https://insights.sbomify.com/CVE-2026-26339/): Hyland Alfresco Transformation Service Argument Injection RCE (critical 9.3)
- [CVE-2026-26338](https://insights.sbomify.com/CVE-2026-26338/): Hyland Alfresco Transformation Service SSRF (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26337 and fix it if it is affected.

What it is: CVE-2026-26337 is a high-severity vulnerability in Hyland Alfresco Community (Transform Core), published on 19 Feb 2026. 
Exploitation: There is no known exploitation of CVE-2026-26337 in the wild and no public exploit code.

Affected product: Hyland Alfresco Community (Transform Core). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26337/ (Markdown: https://insights.sbomify.com/CVE-2026-26337/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26337
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26337
- OSV: https://osv.dev/vulnerability/CVE-2026-26337

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26337/
Summaries are generated and may contain mistakes; the official description above is the record.