Prompty: Arbitrary File Read via ${file:path} Reference Expansion
microsoft prompty
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| prompty PyPI |
|
|
| @prompty/core npm |
|
|
| prompty crates.io |
microsoft prompty
| Product | Affected | Fixed in |
|---|---|---|
| prompty PyPI |
|
|
| @prompty/core npm |
|
|
| prompty crates.io |
< 2.0.0-beta.2
|
| Prompty.Core NuGet |
|
|
Prompty is a markdown file format (.prompty) for LLM prompts. Prior to 2.0.0-beta.2, Prompty loaders expanded ${file:...} references in .prompty frontmatter without enforcing that resolved paths stayed within the prompt directory or allowed roots, allowing an attacker-controlled prompt file to read local files through absolute paths, .. traversal, or symlink escapes. This issue is fixed in versions 2.0.0-beta.2.
From the CVE record · GitHub_M
Prompty loaders did not restrict where ${file:...} references in .prompty frontmatter could resolve. When an application loads an attacker-controlled prompt file, the attacker can read local files using absolute paths, .. traversal, or symlink escapes. The input does not specify an authentication requirement or separate user interaction.
Check applications using PyPI prompty before 2.0.0b2, or npm @prompty/core, crates.io prompty, or NuGet Prompty.Core before 2.0.0-beta.2.