Skip to main content
Menu
CVEs

pmo-platform security hook checks skipped when awk helper is missing

CVE-2026-77389Published , updated

2.0LowCNA
Exploited
No known exploitation
Fix
Fixed in 3.73
Who is exposed
Not reported

Summary

pmo-platform's warning-mode security hooks can skip their checks when a co-shipped awk helper file is missing, which can happen in a partial or corrupted deployment. A local attacker with low privileges can reach this, and the result is a skipped warning rather than a bypass of an enforcing control.

Written by a model

Original description

pmo-platform is a modular PMO and release-management platform for Claude Code. Prior to 3.73, core/hooks/block-fragile-refs.sh and core/hooks/block-gh-path-leak.sh source co-shipped awk primitives from core/hooks/lib/ and degrade when a required primitive is absent. In a partial or corrupted deployment, block-gh-path-leak.sh skips its entire path-leak check, while block-fragile-refs.sh skips only the positional-issue-reference detector and continues running its other detectors. Both hooks operate in a warning posture, so the impact is a skipped warning rather than bypass of an enforcing control, with no established exfiltration or code-execution primitive. This issue is fixed in version 3.73.

What to do

Upgrade to a fixed version: 3.73.

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-77389 (pmo-platform: Warn-mode security hooks fail open (skip their check) when a co-shipped awk primitive is absent), 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-77389 (entry last updated 2026-11-20):
Affected:
- cody-hutson pmo-platform: fixed in 3.73
Fixed versions: 3.73.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77389 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77389 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-g9g6-28c9-vrx5
- https://github.com/cody-hutson/pmo-platform/pull/3426
- https://github.com/cody-hutson/pmo-platform/commit/874f59abee96965a4561a032bb186d7d2377715f
- https://github.com/cody-hutson/pmo-platform/releases/tag/v3.73
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-77389
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-77389"}.

Affected versions

cve.now Index

2Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity2/10CVSS 2.0
  • No patch0/5No signal

What would change the score

  • Would score about 57 if added to CISA KEV
  • Would score about 52 if CISA's SSVC rates exploitation active
  • Would score about 24 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · cody-hutson/pmo-platform · Advisory GHSA-g9g6-28c9-vrx5
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77389
RecordNVD · CVE-2026-77389
Other links 3
RepositoryGitHub · cody-hutson/pmo-platform · Pull request #3426
RepositoryGitHub · cody-hutson/pmo-platform · Commit 874f59ab
RepositoryGitHub · cody-hutson/pmo-platform · Release v3.73

Questions about CVE-2026-77389

Is CVE-2026-77389 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

Which versions are affected by CVE-2026-77389?

pmo-platform: before 3.73.

Source: cve.now feed data

How do I fix CVE-2026-77389?

Upgrade to a fixed version: 3.73.

Source: cve.now feed data

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