# CVE-2026-9177: Server-Side Template Injection in SecureTransport's Apache Velocity mail templates

> An admin can inject Java code into mail templates to execute arbitrary code on the server, leading to full host compromise.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-gqhf-wf6p-pjv9

## What is CVE-2026-9177?

CVE-2026-9177 is a critical code injection vulnerability in Axway SecureTransport, published on 29 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A Server-Side Template Injection (SSTI) vulnerability was identified 
in the mail template functionality of the Axway SecureTransport product in version 5.5-20260326. This 
flaw 
allows an attacker with admin privileges to inject arbitrary Java code expressions, which are 
executed server-side when the template is rendered (i.e., during email 
sending). Successful exploitation of this flaw allows an attacker to 
execute 
arbitrary code on the server that results in full host compromise.

This issue affects all Axway SecureTransport versions prior 5.5-20260528 update.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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


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

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

## Is CVE-2026-9177 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9177 is a critical code injection vulnerability in Axway SecureTransport, published on 29 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9177 in the wild and no public exploit code.

Affected product: Axway SecureTransport. 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-9177/ (Markdown: https://insights.sbomify.com/CVE-2026-9177/index.md)
```

## Sources

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

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