# CVE-2026-56783: Parseable < 2.9.2 - Cleartext Credential Exposure in Notification Target API

> Authenticated users can retrieve cleartext webhook tokens and credentials from notification targets due to missing secret masking.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-9cf6-6j4g-mw9r

## What is CVE-2026-56783?

CVE-2026-56783 is a high-severity vulnerability in parseablehq parseable, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Parseable before 2.9.2 contains an information disclosure vulnerability in the notification-target API endpoints that returns webhook tokens and basic-auth credentials in cleartext due to commented-out secret-masking functionality. Any authenticated user with the GetAlert action, including low-privilege reader roles, can recover credentials and internal endpoint URLs for all configured notification targets by querying GET /api/v1/targets or related endpoints.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-56783 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56783 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56783 is a high-severity vulnerability in parseablehq parseable, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56783 exists.

Affected product: parseablehq parseable. 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-56783/ (Markdown: https://insights.sbomify.com/CVE-2026-56783/index.md)
```

## Sources

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

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