Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-h2cw-7qw9-56xr
No affected components available
Summary
When setting model permissions so that a group has read access to it, intending for other users to use it, those users also can read the model's system prompt.
However users may consider their system prompt confidential, so we consider this a security issue.
Compare https://genai.owasp.org/llmrisk/llm072025-system-prompt-leakage/ or prompt injections to get popular chatbots on the internet to reveal their prompt.
Details
We discovered that users can open the workspace model edit page /workspace/models/edit?id=notmymodel for models that do not appear in their workspace.
Saving is not possible, that permission check is correct.
On the API level:
/api/v1/models/model?id=notmymodel-> returns the model details, most importantly params.system- even though
/api/v1/models/listdoes NOT contain the model since it checks for write permission. /api/modelscontains the model correctly and does not reveal the system prompt.
It seems inconsistent that the REST API list does not contain an item, but if you know the id, you can access it anyway.
PoC
- create model
- give read permission to group with another user
- other user can access
/api/v1/models/model?id=notmymodel
Impact
System prommpt leakage
If this is intended behavior for the "read" permission, maybe there should be an additional "use" permission (which would be 99% of use cases of the read permission i believe).
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard