CVE-2026-77389 in pmo-platform
Summary
by MITRE • 11/20/2026
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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified within pmo-platform versions prior to 3.73 centers on improper handling of missing dependencies during the execution of shell-based security hooks. Specifically, the scripts core/hooks/block-fragile-refs.sh and core/hooks/block-gh-path-leak.sh rely on external awk primitives located in the core/hooks/lib/ directory. In scenarios involving partial installations, corrupted deployments, or environments where these specific library files are absent, the scripts fail to validate their prerequisites before proceeding with execution logic. This lack of defensive programming leads to a degradation in security monitoring capabilities rather than a complete system failure, as the hooks do not abort but instead alter their behavior based on available resources.
The operational impact differs between the two affected components due to their distinct design architectures. The block-gh-path-leak.sh script exhibits a critical flaw where it completely skips its entire path-leak detection routine when required primitives are missing. This results in a total blind spot for potential GitHub-related information leakage, allowing sensitive repository paths or internal structures to remain undetected during release processes. Conversely, the block-fragile-refs.sh script demonstrates partial resilience; while it fails to execute the positional-issue-reference detector due to the absence of specific awk functions, it continues to run its other associated detectors. This means that while some aspects of reference integrity checking are lost, a baseline level of monitoring persists for non-positional issues.
From a threat modeling perspective, this vulnerability is classified under CWE-754: Improper Check for Unusual or Exceptional Conditions, as the software fails to verify the presence of required components before executing security-critical logic. Furthermore, it aligns with ATT&CK technique T1083: File and Directory Discovery, specifically in the context of how an attacker might exploit a misconfigured environment to evade detection mechanisms that rely on external tooling. However, the severity is mitigated by the operational posture of these hooks. They function primarily as warning systems rather than enforcing controls such as pre-commit gates or mandatory policy enforcement engines. Consequently, while the vulnerability reduces visibility and increases the risk of undetected information leakage during release management workflows, it does not directly facilitate code execution, privilege escalation, or data exfiltration through active exploitation vectors.
The recommended mitigation is to upgrade pmo-platform to version 3.73 or later, where this dependency handling issue has been resolved. In interim scenarios where an immediate upgrade is not feasible, administrators should ensure that the core/hooks/lib/ directory contains all required awk primitives and verify their integrity before deployment. Additionally, implementing strict environment validation checks within CI/CD pipelines can help detect missing dependencies early in the release process, ensuring that security hooks operate with full functionality rather than degraded modes. Regular audits of hook configurations and dependency availability are essential to maintain consistent security posture across different development environments.