Quick Take
- What: CVE-2026-123965, a prompt injection flaw in Jet Admin Cloud Platform that exposed .env configuration files and credentials
- Who is affected: All versions of Jet Admin Cloud Platform; customers who stored credentials in platform .env files
- Severity: CISA scored it 9.9 (CVSS 3.1); GitHub Advisory Database lists 9.3 (CVSS 4.0)
- What to do: Rotate any credentials that were stored in Jet Admin .env configuration files
- Fix status: CISA reports a sandbox mitigation around October 29, 2026, but lists remediation as “No fix available
In plain English
Jet Admin is a cloud platform that helps companies build admin panels and internal tools. Researchers found that an attacker could trick the platform’s AI features into reading secret configuration files (called .env files) that contain passwords and other credentials. Anyone could do this with just a free account, no special access needed. Because Jet Admin is a hosted service, the company had to fix it on their servers.
What you should do: If you use Jet Admin and stored any passwords or API keys in those configuration files, you should change them now, because they might have been exposed. If you don’t use Jet Admin, you can ignore this.
What happened
CISA published advisory VA-26-317-01 on November 13, 2026 for CVE-2026-123965, a prompt injection vulnerability in Jet Admin Cloud Platform. The flaw was discovered by security researcher Mahmoud Elkhaligy. CISA records the issue as affecting all versions of the platform.
The vulnerability allowed a remote attacker with only a free account to expose sensitive .env configuration files and exfiltrate critical credentials. CISA classifies the weakness as CWE-200 (exposure of sensitive information to an unauthorized actor) and scored it 9.9 using CVSS version 3.1. The GitHub Advisory Database records a score of 9.3 using CVSS version 4.0 for the same flaw.
According to CISA’s scoring, the attack requires no privileges and no user interaction. The technical impact is marked as total in CISA’s SSVC entry, though no observed exploitation has been recorded.
How it works
The vulnerability is a prompt injection flaw. In this type of attack, attacker-supplied text reaches the platform’s AI features as instructions rather than as data. By crafting specific prompts, an attacker could manipulate the AI system to read and expose .env configuration files that should have remained protected.
Because Jet Admin Cloud Platform is a hosted service, customers cannot install version updates themselves. Any credential that was stored in a platform .env file represents a potential exposure that organizations must assess.
What you should do
Rotate any credentials that were stored in Jet Admin .env configuration files, since CISA states those files could be exposed and their contents taken. CISA’s advisory provides no additional customer-side steps beyond recording the vendor’s sandbox mitigation.
What it means
CISA reports that the issue was mitigated via a sandbox component around October 29, 2026. However, the advisory’s remediation entry reads No fix available,” and the advisory does not explain this discrepancy. CISA continues to list all versions as affected.
The gap between CISA’s 9.9 score and GitHub’s 9.3 score comes from the two different CVSS scoring systems (3.1 versus 4.0) rather than from disagreement about the severity of the flaw. CISA’s vector marks scope as changed, reflecting the potential for the vulnerability to affect resources beyond the vulnerable component itself.



