# CVE-2025-48056: Hubble CLI vulnerable to character injection

> Attackers can inject control characters into Hubble CLI output to hide logs or disrupt the terminal, requiring Layer 7 visibility monitoring.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2025
- **Updated:** 20 May 2025
- **Also known as:** GHSA-274q-79q9-52j7, GO-2025-3700, MINI-5x3m-g792-qq36, MINI-877v-gq6h-42c6

## What is CVE-2025-48056?

CVE-2025-48056 is a medium-severity vulnerability in cilium hubble, published on 20 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hubble is a fully distributed networking and security observability platform for cloud native workloads. Prior to version 1.17.2, a network attacker could inject malicious control characters into Hubble CLI terminal output, potentially leading to loss of integrity and manipulation of the output. This could be leveraged to conceal log entries, rewrite output, or even make the terminal temporarily unusable. Exploitation of this attack would require the victim to be monitoring Kafka traffic using Layer 7 Protocol Visibility at the time of the attack. The issue is patched in Hubble CLI v1.17.2. Hubble CLI users who are unable to upgrade can direct their Hubble flows to a log file and inspect the output within a text editor.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

3 open source packages ship an affected version, including github.com/cilium/hubble.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/cilium/hubble` | Go | All versions | 1.17.2 |
| `github.com/cilium/hubble` | Go | All versions | 1.17.2 |
| `github.com/cilium/hubble` | Go | All versions | 1.17.2 |

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

Upgrade github.com/cilium/hubble to 1.17.2 or later.

## Is CVE-2025-48056 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48056 is a medium-severity vulnerability in cilium hubble, published on 20 May 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-48056 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cilium/hubble (Go): affected all versions; fixed in 1.17.2
- github.com/cilium/hubble (Go): affected all versions; fixed in 1.17.2
- github.com/cilium/hubble (Go): affected all versions; fixed in 1.17.2

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-48056/ (Markdown: https://insights.sbomify.com/CVE-2025-48056/index.md)
```

## Sources

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

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