# CVE-2026-120202: Highflame ramparts 0.8.1 through 0.8.10 Skill Bundle Scan Bypass via Nested .pyc


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Oct 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-6cmq-892m-x8wh

## What is CVE-2026-120202?

CVE-2026-120202 is a high-severity vulnerability in highflame-ai ramparts, published on 31 Oct 2026. 

### Official 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.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2026-120202?


## How do I fix CVE-2026-120202?

No fix has been published for CVE-2026-120202 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120202 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120202 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120202 and fix it if it is affected.

What it is: CVE-2026-120202 is a high-severity vulnerability in highflame-ai ramparts, published on 31 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120202 exists.

Affected product: highflame-ai ramparts. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120202/ (Markdown: https://insights.sbomify.com/CVE-2026-120202/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120202
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120202
- OSV: https://osv.dev/vulnerability/CVE-2026-120202

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120202/
Summaries are generated and may contain mistakes; the official description above is the record.