CVE-2026-56783: Insufficiently Protected Credentials in parseablehq parseable
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.
AI Analysis
Technical Summary
CVE-2026-56783 affects parseable versions before 2.9.2. The vulnerability arises from the notification-target API endpoints returning sensitive information such as webhook tokens and basic-auth credentials in cleartext. This occurs due to the secret-masking feature being disabled via commented-out code. Authenticated users with the GetAlert action, even those with minimal privileges, can exploit this by making GET requests to /api/v1/targets or related endpoints to retrieve credentials and internal URLs for all configured notification targets. This represents a significant information disclosure risk.
Potential Impact
The vulnerability allows disclosure of sensitive authentication credentials and internal endpoint URLs to any authenticated user with the GetAlert permission, including low-privilege roles. This exposure can lead to unauthorized access to notification targets and potentially further compromise of the system or connected services. The CVSS 4.0 base score is 7.1, indicating a high severity impact due to network attack vector, low attack complexity, no user interaction, and high confidentiality impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects parseable versions prior to 2.9.2, upgrading to version 2.9.2 or later is recommended once a fix is officially released. Until then, restrict the GetAlert permission to trusted users only to limit exposure. Monitor vendor channels for an official fix or temporary mitigation instructions.
CVE-2026-56783: Insufficiently Protected Credentials in parseablehq parseable
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.
CVSS v4.0
Score 7.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-56783 affects parseable versions before 2.9.2. The vulnerability arises from the notification-target API endpoints returning sensitive information such as webhook tokens and basic-auth credentials in cleartext. This occurs due to the secret-masking feature being disabled via commented-out code. Authenticated users with the GetAlert action, even those with minimal privileges, can exploit this by making GET requests to /api/v1/targets or related endpoints to retrieve credentials and internal URLs for all configured notification targets. This represents a significant information disclosure risk.
Potential Impact
The vulnerability allows disclosure of sensitive authentication credentials and internal endpoint URLs to any authenticated user with the GetAlert permission, including low-privilege roles. This exposure can lead to unauthorized access to notification targets and potentially further compromise of the system or connected services. The CVSS 4.0 base score is 7.1, indicating a high severity impact due to network attack vector, low attack complexity, no user interaction, and high confidentiality impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects parseable versions prior to 2.9.2, upgrading to version 2.9.2 or later is recommended once a fix is officially released. Until then, restrict the GetAlert permission to trusted users only to limit exposure. Monitor vendor channels for an official fix or temporary mitigation instructions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-06-23T01:24:27.650Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a42b42727e9c7971940f82f
Added to database: 06/29/2026, 18:06:31 UTC
Last enriched: 07/15/2026, 10:17:33 UTC
Last updated: 08/13/2026, 00:41:13 UTC
Views: 58
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.