EUVD-2026-67267
GHSA-gmrc-gf77-xwpg
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Credentials are in public source (PR:N/AV:N); impact falls on the separate Langfuse telemetry system rather than PentestGPT itself, warranting S:C.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
6DescriptionCVE.org
A vulnerability in pentestgpt/core/langfuse.py in PentestGPT 1.0.0 allows remote attackers to disclose sensitive user telemetry data via hardcoded API credentials.
AnalysisAI
Hardcoded Langfuse API credentials embedded in PentestGPT 1.0.0's core telemetry module expose all user session telemetry to unauthorized third parties. Any actor who reads the public GitHub repository can extract the literal API key pair from pentestgpt/core/langfuse.py:114 and authenticate directly to the Langfuse observability backend, gaining read access to pentest session traces that may contain targets, findings, and full AI prompt-response histories. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The attacker requires only the ability to read the public PentestGPT GitHub repository, which imposes no authentication or network privilege requirement. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Despite the CVSS 7.5 score with AV:N/PR:N vector, real-world exploitation requires only the ability to read a public GitHub repository - effectively zero barrier. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | The immediate fix is to remove the hardcoded Langfuse API key pair from pentestgpt/core/langfuse.py and replace them with environment variable lookups (for example, LANGFUSE_PUBLIC_KEY and LANGFUSE_SECRET_KEY) or a secrets management solution. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Immediately audit all PentestGPT 1.0.0 deployments and revoke the hardcoded Langfuse API credentials from your Langfuse account to prevent unauthorized backend access. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Hardcoded Credentials
View allSame weakness CWE-798 – Use of Hard-coded Credentials
View allShare
External POC / Exploit Code
Leaving vuln.today