[jonahgabriel]

Summary

Bumps mcp from 1.28.0 to 1.29.0 (satisfies >=1.28.1), fixing CVE-2026-59950 / SFTY-20260716-50488 — Improper Input Validation due to missing Host/related header validation in the MCP Python SDK (affected spec: <1.28.1).

mcp is a transitive dependency (pulled in via omnibase-infra and omninode-memory, both git-pinned) — omnimarket does not declare it directly. uv lock --upgrade-package mcp resolves cleanly to 1.29.0 with a single-package diff (no cascade to any other pin).

Provenance

Surfaced by #2084's (OMN-16001) security-scan.yml pull_request trigger — the first time PR content was ever scanned by this job (previously schedule/push-only). Confirmed pre-existing on dev, not introduced by any in-flight PR: dev tip's own uv.lock pins the same vulnerable mcp==1.28.0, and running the identical safety check command CI runs against dev's own lockfile reproduces the identical finding. Out of scope for #2084 by its own stated boundary (CI-gate-enforcement only) — this is the recommended standalone follow-up.

Verification

• uv lock --upgrade-package mcp → uv.lock diff is exactly the mcp package block (version, sdist URL/hash, wheel URL/hash) — no other package touched.
• uv sync → clean install, mcp==1.28.0 -> mcp==1.29.0.
• Both mcp-consuming packages import cleanly at the new pin: import omnibase_infra, import omnimemory (the omninode-memory package's actual import name).
• pre-commit run --files uv.lock → all applicable hooks green (Dependency health gate, Validator Requirements Fleet Gate, Pre-commit fail-loud meta-gate, etc.).
• Governed impacted-test selector (pre-push, OMN-13973) escalated to the FULL local suite (lockfile changes cannot be narrowed) — see push log for pass/fail counts.

Ticket

OMN-16112

dod_evidence: single-package uv.lock diff, clean uv sync, clean downstream imports, pre-commit all-green, full governed pre-push suite green.

Evidence-Ticket: OMN-16112

Evidence-Source: OCC#6589

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 02a5a1a0-bea7-42c6-b26a-ad210069a08b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Architectural Review — PASSED

Errors: 0
Warnings: 0

What this checks

Rule	Description
ARCH-TOPIC-001	No hardcoded Kafka topic strings in handler code
ARCH-DI-001	No event_bus=None bypass
ARCH-DI-002	No direct Handler instantiation outside workflow_runner/adapters
ARCH-DI-003	No reinvented DI containers
ARCH-TOPIC-002	contract.yaml topics follow `onex.{cmd

---

No architectural violations found.

Static architectural lint — no model inference (OMN-14176).

[onexbot-occ-writer]

OCC autobind did not mint a companion for this PR: no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required.

[github-actions]

✅ Hostile Reviewer — PASSED

Blocking findings (critical/error): 0
Total findings: 0
Models succeeded: qwen3-review,qwen3-review-b

---

Gate semantics

Verdict	Meaning	Blocks merge?
passed	>=2 models succeeded, no critical/error findings	No
blocked	CRITICAL or ERROR findings found	Yes
degraded	Fewer than 2 models succeeded (infra unavailable/timeout)	Yes (OMN-15110)

Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524)