Security Patch #565

Merged
moritz merged 2 commits from chore/deps-security-patches into main 2026-10-05 13:29:32 +02:00
Owner

Description of the implemented changes

The changes were:

  • Bugfixing
  • New Feature
  • Breaking Change
  • Refactoring

Patches the dependency security advisories that currently fail mix deps.audit on
every branch, so that unrelated pull requests are no longer blocked by them. One
advisory cannot be patched by a version bump and is deliberately suppressed, tracked
by #564.

What has been changed?

  • phoenix 1.8.8 → 1.8.9, patching GHSA-63mc-hw7g-86rr (Presence keys colliding with
    Object.prototype members) and GHSA-6983-jfq8-485w (unbounded channel joins per
    transport, DoS over few connections).
  • ash 3.29.3 → 3.34.1, patching CVE-2026-69659 / GHSA-j35q-v8h8-7mwq (unbounded
    keyset size, unsanitized managed-relationship lookup filters). Note that
    mix deps.audit does not report this one — our advisory database does not carry it
    yet; it was found in the Ash changelog.
  • config :ash, default_string_length_count: :codepoints — required by Ash 3.34,
    which refuses to compile without it. See Additional Notes.
  • GHSA-777c-2fxx-qr28 (ash_authentication, critical) added to
    .deps_audit_ignore, with rationale and a pointer to #564.

Only mix.lock, config/config.exs and .deps_audit_ignore are touched. The lock
diff is two entries — mix deps.unlock phoenix ash plus mix deps.get rather than
mix deps.update, which would have unlocked the whole transitive tree and moved 27
entries including req 0.6 → 0.7.

Definition of Done

Code Quality

  • No new technical depths
  • Linting passed
  • Documentation is added were needed

This PR knowingly adds one piece of technical debt: the .deps_audit_ignore entry for
GHSA-777c-2fxx-qr28. It is documented in place with severity, exposure assessment,
removal condition and the tracking issue.

Testing

  • Tests for new code are written
  • All tests pass
  • axe-core dev tools show no critical or major issues
## Description of the implemented changes The changes were: - [x] Bugfixing - [ ] New Feature - [ ] Breaking Change - [ ] Refactoring Patches the dependency security advisories that currently fail `mix deps.audit` on every branch, so that unrelated pull requests are no longer blocked by them. One advisory cannot be patched by a version bump and is deliberately suppressed, tracked by #564. ## What has been changed? - `phoenix` 1.8.8 → 1.8.9, patching GHSA-63mc-hw7g-86rr (Presence keys colliding with `Object.prototype` members) and GHSA-6983-jfq8-485w (unbounded channel joins per transport, DoS over few connections). - `ash` 3.29.3 → 3.34.1, patching CVE-2026-69659 / GHSA-j35q-v8h8-7mwq (unbounded keyset size, unsanitized managed-relationship lookup filters). Note that `mix deps.audit` does not report this one — our advisory database does not carry it yet; it was found in the Ash changelog. - `config :ash, default_string_length_count: :codepoints` — required by Ash 3.34, which refuses to compile without it. See Additional Notes. - `GHSA-777c-2fxx-qr28` (`ash_authentication`, critical) added to `.deps_audit_ignore`, with rationale and a pointer to #564. Only `mix.lock`, `config/config.exs` and `.deps_audit_ignore` are touched. The lock diff is two entries — `mix deps.unlock phoenix ash` plus `mix deps.get` rather than `mix deps.update`, which would have unlocked the whole transitive tree and moved 27 entries including `req` 0.6 → 0.7. ## Definition of Done ### Code Quality - [ ] No new technical depths - [x] Linting passed - [x] Documentation is added were needed This PR knowingly adds one piece of technical debt: the `.deps_audit_ignore` entry for `GHSA-777c-2fxx-qr28`. It is documented in place with severity, exposure assessment, removal condition and the tracking issue. ### Testing - [ ] Tests for new code are written - [x] All tests pass - [ ] axe-core dev tools show no critical or major issues
Ash 3.34 requires `default_string_length_count` to be set. Chose
`:codepoints` over `:mixed` so that `min_length`/`max_length` validate
identically in Elixir and in Postgres, and so `max_length` actually bounds
the size of a stored value — under `:mixed` a single grapheme can carry an
unbounded number of combining characters.
chore(deps): suppress ash_authentication advisory until oidc identities land
All checks were successful
continuous-integration/drone/push Build is passing
continuous-integration/drone/promote/production Build is passing
49ae7f483b
moritz changed title from WIP: to Security Patch 2026-10-05 13:29:26 +02:00
moritz merged commit 28c737d855 into main 2026-10-05 13:29:32 +02:00
moritz deleted branch chore/deps-security-patches 2026-10-05 13:29:32 +02:00
Sign in to join this conversation.
No description provided.