Skip to content

fix(OMN-17184): close all 14 omnimemory Dependabot alerts (8 high) - #467

Merged
jonahgabriel merged 1 commit into
devfrom
jonah/omn-17184-omnimemory-dep-bumps
Aug 31, 2026
Merged

jonahgabriel merged 1 commit into
devfrom
jonah/omn-17184-omnimemory-dep-bumps

Conversation

@jonahgabriel

@jonahgabriel jonahgabriel commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Closes all 14 open Dependabot alerts on omnimemory (8 high / 4 medium / 2 low). Lockfile only — no source or pyproject.toml change; every bump sits inside constraints already declared.

Ticket: OMN-17184

Alerts Sev Package Was → Now CVE
#21, #23 high Mako 1.3.10 → 1.4.1 CVE-2026-41205, CVE-2026-44307
#48, #49, #50 high pyasn1 0.6.3 → 0.6.4 CVE-2026-59884/59885/59886
#25, #26 high urllib3 2.6.3 → 2.7.0 CVE-2026-44431, CVE-2026-44432
#3 high deepdiff 8.6.1 → 9.1.0 CVE-2026-33155
#47 high mcp 1.27.2 → 1.29.1 CVE-2026-59950
#5 medium requests 2.32.5 → 2.34.2 CVE-2026-25645
#28 medium tuf 6.0.0 → 7.0.0 GHSA-qp9x-wp8f-qgjj
#57 medium h2 4.3.0 → 4.4.1 CVE-2026-71554
#27 medium idna 3.11 → 3.19 CVE-2026-45409
#7 low Pygments 2.19.2 → 2.21.0 CVE-2026-4539

mcp was deliberately held inside 1.x

pyproject.toml declares mcp>=1.27.2,<3.0.0, so an unconstrained upgrade resolves to 2.1.1 and drags in httpx2, httpcore2, httpx2-jsfetch and mcp-types — a transport swap, not a security patch. Alert #47 only needs >= 1.28.1, so the bump was pinned <2 and lands on 1.29.1 with zero new packages.

Two majors are deliberate and both are transitive-only: deepdiff 8→9 matches the version omnibase_infra already runs on dev, and tuf 6→7 arrives through sigstore — nothing here imports either directly.

Verification

  • uv lock --check clean; uv sync --all-extras resolves
  • uv run pytest tests/unit — 1233 passed, 0 failed
  • Governed pre-push selector (OMN-13973) ran and passed. No PREPUSH_* override, no --no-verify.

Context

One of six PRs closing 141 open Dependabot alerts org-wide under OMN-17184. The ticket originally scoped only omnidash's 39; a live sweep of all 14 registry repos found 141 across six.

Evidence-Ticket: OMN-17184
Evidence-Source: OCC#7794

Lockfile-only remediation of every open Dependabot alert on omnimemory
(8 high / 4 medium / 2 low). No source or pyproject change — every bump
sits inside the constraints already declared in pyproject.toml.

- Mako      1.3.10 -> 1.4.1   CVE-2026-41205, CVE-2026-44307 (2x high)
- pyasn1    0.6.3  -> 0.6.4   CVE-2026-59884/59885/59886 (3x high)
- urllib3   2.6.3  -> 2.7.0   CVE-2026-44431, CVE-2026-44432 (2x high)
- deepdiff  8.6.1  -> 9.1.0   CVE-2026-33155 (high)
- mcp       1.27.2 -> 1.29.1  CVE-2026-59950 (high, direct)
- tuf       6.0.0  -> 7.0.0   GHSA-qp9x-wp8f-qgjj (medium)
- requests  2.32.5 -> 2.34.2  CVE-2026-25645 (medium)
- h2        4.3.0  -> 4.4.1   CVE-2026-71554 (medium)
- idna      3.11   -> 3.19    CVE-2026-45409 (medium)
- Pygments  2.19.2 -> 2.21.0  CVE-2026-4539 (low)

Two majors are deliberate and both are transitive-only:
- deepdiff 8 -> 9 matches the version omnibase_infra already runs on dev,
  and omnimemory has no direct deepdiff import.
- tuf 6 -> 7 is pulled through sigstore; nothing here imports tuf directly.

mcp was deliberately held INSIDE the 1.x line. pyproject declares
`mcp>=1.27.2,<3.0.0`, so an unconstrained upgrade resolves to 2.1.1 and
drags in httpx2, httpcore2, httpx2-jsfetch and mcp-types — a transport
swap, not a security patch. Alert #47 only needs >= 1.28.1, so the bump was
pinned to `<2` and lands on 1.29.1 with no new packages.

Verification: `uv lock --check` clean; `uv sync --all-extras` resolves;
tests/unit run in full — 1233 passed, 0 failed.

Ticket: OMN-17184
@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown

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: 55f7c593-8461-4282-b61c-a5f873648789

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.

@jonahgabriel
jonahgabriel merged commit a64e4a4 into dev Aug 31, 2026
45 of 46 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-17184-omnimemory-dep-bumps branch August 31, 2026 06:13
jonahgabriel pushed a commit to OmniNode-ai/onex_change_control that referenced this pull request Aug 31, 2026
…imemory#467 (#7794)

* evidence(OMN-17184): author OCC companion for OmniNode-ai/omnimemory#467

OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head b85725aba58e5fab6fe8687566a23b7fa7b2f23f.

* evidence(OMN-17184): self-bind OCC#7794 + rebind contract_sha256

---------

Co-authored-by: omnimarket-bot <bot@omninode.ai>
jonahgabriel added a commit that referenced this pull request Aug 31, 2026
…pattern fixes (#470)

omnimemory#466 (OMN-17236) fixed three PII detector pattern defects on a live
persistence path and merged to dev at 2026-08-30T17:50:52Z. The v0.18.0 tag and
PyPI publish had already happened at 14:06Z that day, so the fixes missed the
cut by under four hours and there has been no release since.

The consequence is live and reproducible in the .201 dev lane, whose containers
all report omninode-memory 0.18.0:

    docker exec omninode-runtime python -c "... PIIDetector().detect_pii(s) ..."
    visa     -> 'card ***-***-****111111 end'   types: ['phone']
    discover -> 'card ***-***-****111117 end'   types: ['phone']
    uuid     -> 'run 550e8400-e29b-41d4-a***-***-****40000 done'
    ssn-sp   -> 'ssn 123 45 6789 end'           types: []

The trailing six digits of a Visa or Discover card are still being written into
stored content, UUID-bearing storage requests are still refused, and a
space-separated SSN is still not detected at all.

This bump is the first of three links; the omnimarket repin (exact pin at
==0.18.0) and the dev-lane image rebuild follow on OMN-17390.

Release contents (v0.18.0..dev): #466 PII fixes + 170 behavioral tests,
#467 all 14 Dependabot alerts, #464 omnibase-infra 0.38.14, #468 sibling locks,
#469 CI guide doc fix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant