# CVE-2025-0733: Postman profapi.dll untrusted search path

> Local attackers can exploit an untrusted search path in Postman's profapi.dll to potentially execute arbitrary code.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2025
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-3gvp-wpmx-3ff3

## What is CVE-2025-0733?

CVE-2025-0733 is a low-severity path traversal vulnerability in Postman, published on 27 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in Postman up to 11.20 on Windows. This affects an unknown part in the library profapi.dll. The manipulation leads to untrusted search path. An attack has to be approached locally. The complexity of an attack is rather high. The exploitability is told to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2025-0733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0733 is a low-severity path traversal vulnerability in Postman, published on 27 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0733 in the wild and no public exploit code.

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

## Sources

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

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