# CVE-2025-30354: Bruno ignores Safe-Mode in Asserts expressions

> Attackers can execute arbitrary code by tricking users into opening malicious API collections, bypassing the application's Safe Mode sandbox restrictions.

- **Severity:** High 8.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Apr 2025
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-hffg-7v8v-79j3

## What is CVE-2025-30354?

CVE-2025-30354 is a high-severity code injection vulnerability in usebruno bruno, published on 1 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Bruno is an open source IDE for exploring and testing APIs. A bug in the assertion runtime caused assert expressions to run in Developer Mode, even if Safe Mode was selected. The bug resulted in the sandbox settings to be ignored for the particular case where a single request is run/sent. This vulnerability's attack surface is limited strictly to scenarios where users import collections from untrusted or malicious sources. The exploit requires deliberate action from the user—specifically, downloading and opening an externally provided malicious Bruno collection. The vulnerability is fixed in 1.39.1.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

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

It affects 1 product.


Products: Usebruno Bruno.

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

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

## Is CVE-2025-30354 being exploited?

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

## Other vulnerabilities in usebruno bruno

- [CVE-2026-34841](https://insights.sbomify.com/CVE-2026-34841/): Axios npm Supply Chain Incident Impacting @usebruno/cli (critical 9.8)
- [CVE-2025-30210](https://insights.sbomify.com/CVE-2025-30210/): Bruno XSS On Environment Name (high 8.7)
- [CVE-2024-48463](https://insights.sbomify.com/CVE-2024-48463/): Open redirect in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30354 is a high-severity code injection vulnerability in usebruno bruno, published on 1 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-30354 in the wild and no public exploit code.

Affected product: usebruno bruno. 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-30354/ (Markdown: https://insights.sbomify.com/CVE-2025-30354/index.md)
```

## Sources

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

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