Highflame ramparts 0.8.1 through 0.8.10 Skill Bundle Scan Bypass via Nested .pyc
Affects ramparts 0.8.1 through 0.8.10 when a skill bundle has a .pyc file in a nested subdirectory, which the bundle scan does not enter. No fixed version is listed.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Highflame's ramparts tool, a security scanner for skill bundles, is affected by this flaw. Because it skips nested directories and compiled .pyc files, malicious code can be hidden inside a bundle and still run when the skill is executed, bypassing the scan.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Highflame ramparts 0.8.1 through 0.8.10 contains a security scan bypass vulnerability that allows attackers to hide malicious payloads because collect_bundle_siblings and walk_bundle_subdir skip nested directories and .pyc files. Attackers can distribute a skill bundle with an unchecked-hash .pyc under scripts/<subdir>/pycache/ that ramparts silently ignores, while CPython executes it when the skill runs.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- highflame-ai ramparts
From 0.8.1 · through 0.8.10
References 4
GitHub · highflame-ai/ramparts
Questions about CVE-2026-120202
What does this mean?
The bundle scanner does not descend into nested subdirectories, so a .pyc file there, such as in scripts/<subdir>/__pycache__/, is not inspected. The .pyc can contain arbitrary code, and the scan reports zero findings while that code runs when the skill is imported.Source: github.com
Am I affected, and how do I check?
Versions 0.8.1 through 0.8.10 of ramparts (highflame-ai) are in the affected range, and the bug was tested on v0.8.2. The setup is a skill bundle with a .pyc file in a nested subdirectory; check your installed version against that range and inspect your skill bundles for nested __pycache__ directories.Source: github.com
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be confirmed from them. Check the vendor's advisory for a fixed release and move to it once it is published.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The facts list no fix and no workaround. Until a fix is available, avoid bundling .pyc files in nested subdirectories of skill bundles, since that nested layout is the condition the scan misses.Source: github.com