# CVE-2025-36274: IBM Aspera HTTP Gateway information disclosure

> Unauthenticated attackers can read sensitive information stored in clear text within easily obtainable files in IBM Aspera HTTP Gateway.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-56h4-7qj3-rf74

## What is CVE-2025-36274?

CVE-2025-36274 is a high-severity vulnerability in IBM Aspera HTTP Gateway, published on 26 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Aspera HTTP Gateway 2.0.0 through 2.3.1 stores sensitive information in clear text in easily obtainable files which can be read by an unauthenticated user.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2025-36274?

It affects 1 product.


Products: Ibm Aspera Http Gateway.

## How do I fix CVE-2025-36274?

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

## Is CVE-2025-36274 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-36274 and fix it if it is affected.

What it is: CVE-2025-36274 is a high-severity vulnerability in IBM Aspera HTTP Gateway, published on 26 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-36274 in the wild and no public exploit code.

Affected product: IBM Aspera HTTP Gateway. 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-2025-36274/ (Markdown: https://insights.sbomify.com/CVE-2025-36274/index.md)
```

## Sources

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

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