Skip to main content
Menu
CVEs

pmo-platform security hook bypass via jq PATH lookup

Affects pmo-platform before 3.69.1 on macOS where jq comes only from Homebrew, so /usr/bin/jq is absent and the hooks cannot find it. CVSS scores it 7.3 (high). Fixed in 3.69.1.

CVE-2026-77350Published , updated

7.3HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.69.1
Who is exposed
Specific setups only

Summary

pmo-platform, a PMO and release-management platform for Claude Code, has security hooks that fail open on systems where jq is installed only in a Homebrew path, so checks on credential reads, network egress, filesystem boundaries, and MCP writes can be skipped. An attacker with local access, who needs no login but must get a user to take an action, can use these skipped checks to expose secrets or perform unauthorized tool actions by influencing a prompt, repository, or evaluation flow.

Written by a model

Original description

pmo-platform is a modular PMO and release-management platform for Claude Code. Prior to 3.69.1, core/hooks/block-credential-reads.sh, core/hooks/block-egress.sh, core/hooks/block-fs-boundary.sh, and core/hooks/block-mcp-writes.sh pin PATH to /usr/bin:/bin, hard-code jq as /usr/bin/jq, and return success when jq is unavailable there. On systems where jq exists only in a Homebrew path, including affected pre-Sequoia or Homebrew-only macOS installations, the hooks can skip credential-read, network-egress, filesystem-boundary, and MCP-write controls. Native deny rules independently protect some credential paths but do not backstop the egress or MCP controls. An attacker who can influence a prompt, repository, or evaluation flow can use the skipped checks to expose secrets or perform unauthorized tool actions. This issue is fixed in version 3.69.1.

Who should check

Teams running pmo-platform 3.69 or earlier with the Claude Code security hooks installed, especially macOS users who installed jq via Homebrew.

“This is a security feature bypass affecting all macOS users of pmo-platform v3.65 who followed the documented installation instructions.”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    On macOS, jq is installed only through Homebrew (/opt/homebrew/bin/jq or /usr/local/bin/jq), so /usr/bin/jq is absent. The hooks cannot find jq at their hard-coded path, so they exit 0 instead of blocking.
  2. Upgrade to a fixed version: 3.69.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77350 (pmo-platform: Security Hooks Fail Open Because Runtime PATH Excludes Documented jq Install Paths), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77350 (entry last updated 2026-11-20):
Affected:
- cody-hutson pmo-platform: fixed in 3.69.1
Fixed versions: 3.69.1.
Conditions (all must be true for the bug to be hit):
- On macOS, jq is installed only through Homebrew (/opt/homebrew/bin/jq or /usr/local/bin/jq), so /usr/bin/jq is absent. (source: https://github.com/cody-hutson/pmo-platform/security/advisories/GHSA-9cjm-v22x-4x33)
- The hooks cannot find jq at their hard-coded path, so they exit 0 instead of blocking. (source: https://github.com/cody-hutson/pmo-platform/security/advisories/GHSA-9cjm-v22x-4x33)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-77350 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77350 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/cody-hutson/pmo-platform/security/advisories/GHSA-9cjm-v22x-4x33
- https://github.com/cody-hutson/pmo-platform/commit/586b96850e4086a8a3471b7adcebbd571db18840
- https://github.com/cody-hutson/pmo-platform/releases/tag/v3.69.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77350
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77350"}.

Affected versions

cve.now Index

12Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.3/10CVSS 7.3
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · cody-hutson/pmo-platform · Advisory GHSA-9cjm-v22x-4x33
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77350
RecordNVD · CVE-2026-77350
Other links 2
RepositoryGitHub · cody-hutson/pmo-platform · Commit 586b9685
RepositoryGitHub · cody-hutson/pmo-platform · Release v3.69.1

Questions about CVE-2026-77350

Is CVE-2026-77350 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 does this mean?

The pmo-platform security hooks look for jq at a hard-coded path. When jq is not found there, the hooks print a warning and exit with code 0, so they skip their checks instead of blocking the operation.

Source: github.com

Which versions are affected by CVE-2026-77350?

pmo-platform: before 3.69.1.

Source: cve.now feed data

Am I affected, and how do I check?

Versions of pmo-platform before 3.69.1 on macOS, where jq was installed with Homebrew (brew install jq) and sits at /opt/homebrew/bin/jq or /usr/local/bin/jq rather than /usr/bin/jq. To check, compare the pmo-platform version against 3.69.1 and see whether /usr/bin/jq exists on the machine.

Source: github.com

How do I fix CVE-2026-77350?

Upgrade pmo-platform to 3.69.1, which is the listed fixed version. The sources give no vendor patch identifiers for this issue.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.