BuildRiot
Sign in

SecuritySource: Fission-AI

Fission-AI removes vulnerable dependency in OpenSpec v1.14.3

OpenSpec v1.14.3 removes the unpatched braces dependency and strengthens instructions for artifact writes. The openspec status command also rejects generates patterns whose braces expand to more than 1,024 paths to prevent memory exhaustion.

By News DeskPublished here (UTC)2 min read
Fission-AI logo
Cover: BuildRiot

Fission-AI released OpenSpec v1.14.3 on October 17, 2026, removing a vulnerable dependency and strengthening instructions for checking artifact destinations before writes. Maintainers say installations no longer pull in the unpatched braces package, eliminating its associated audit finding through OpenSpec. Sources: Fission-AI

The GitHub-reviewed advisory identifies CVE-2026-93687 as a denial-of-service vulnerability affecting braces versions through 3.0.3, with no patched version listed. Deeply nested patterns can exhaust recursive processing and terminate Node.js with an uncaught RangeError. Sources: GitHub Advisory Database

The propose, ff, continue and explore workflows now instruct agents to select and check a concrete destination before writing or delegating artifact creation. Those instructions require refusing paths that escape the change directory, including through symlinks. According to MnzAI Labs, delegated writers must support the checked destination, and the resulting artifact must be verified there. MnzAI Labs cautions that these workflow instructions do not establish a filesystem sandbox. Sources: Fission-AI, MnzAI Labs

Separately, openspec status now rejects generates patterns whose braces expand to more than 1,024 paths, according to the release notes. That cap aims to prevent memory exhaustion from expansion volume. The braces advisory concerns nesting depth and stack exhaustion. Sources: Fission-AI, GitHub Advisory Database

What to do

  1. Upgrade to OpenSpec v1.14.3, then inspect the resolved dependency tree and rerun the relevant audit to verify braces removal in your installation.
  2. Review custom generates patterns and narrow any whose braces expand to more than 1,024 paths. Sources: Fission-AI

Why it matters

The update removes a vulnerable dependency and adds instructions intended to keep generated artifacts inside their change directory. MnzAI Labs cautions that these instructions do not establish a filesystem sandbox.

Attribution

Sources

  1. 1Fission-AIRelease v1.14.3 - Linked specs, safer globsSource published (UTC)
  2. 2MnzAI LabsOpenSpec 1.14.3: Artifact Writing RulesSource published (UTC)
  3. 3GitHub Advisory Databasebraces vulnerable to stack-exhaustion denial of service through deeply nested patternsSource published (UTC)

Read the original source for full details and context.

Report a problem

Links, dates or what you expected. Do not include passwords or private data.

More on Security

All Security stories

Review · AI

GitHub license compliance: dependency policies, package checks and enforcement

GitHub’s documentation describes a package-check API that checks dependency licenses against repository policy. Agent integration is one possible application. Open Source License Compliance is available for Enterprise Cloud, including data-resident deployments; repository enforcement requires Code Security. Setup requires the dependency graph and enterprise policy/ruleset management access, with policy configured under Policies > License compliance > Default policy. The Enterprise Open-Source License Manager role receives notifications to review exception requests. Package checks accept a purls array at /repos/OWNER/REPO/license-compliance/package-checks. The documentation examples use API version 2026-03-10. Fine-grained tokens need Repository license policy: read permission.

GitHub Docs