# CVE-2026-15580: PassPortal browser extension: vault token disclosure via unvalidated postMessage

> An attacker can steal vault tokens via unvalidated postMessage in the PassPortal browser extension, leading to authentication abuse.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-6637-gh22-j6hq

## What is CVE-2026-15580?

CVE-2026-15580 is a medium-severity vulnerability in N-able PassPortal, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

vault token disclosure via unvalidated postMessage vulnerability in N-able PassPortal allows Authentication Abuse.

This issue affects the PassPortal browser extension: before 3.49.6.

Weakness: CWE-1385 (Missing Origin Validation in WebSockets)

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


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

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

## Is CVE-2026-15580 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15580 is a medium-severity vulnerability in N-able PassPortal, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-15580 in the wild and no public exploit code.

Affected product: N-able PassPortal. 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-15580/ (Markdown: https://insights.sbomify.com/CVE-2026-15580/index.md)
```

## Sources

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

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