Vulnerability advisory

CVE-2026-77831

Algorithmic-complexity denial of service in AshPaperTrail full-diff list tracking

Published Updated OSV record ↗

Also known as EEF-CVE-2026-77831GHSA-7c66-59m8-723c

Severity
  • CVSS 4.0CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Affected versions

Repository

Affected commitsFixed by commit
GIT github.com/ash-project/ash_paper_trail ↗
449cd2a93416853066378fa61c715e89f80dc854 to before e781f5d8840b07d57db99f9a4728298837d7b3a8e781f5d8840b07d57db99f9a4728298837d7b3a8
e4f1a1527c84a1ba0ceffb271abcb72cb78fc92c to before e03925c19365697ceb099d2ceca9ee1f5ce8c8b8e03925c19365697ceb099d2ceca9ee1f5ce8c8b8
Also listed as affected (17)
  • v0.6.0
  • v0.5.7
  • v0.5.6
  • v0.5.5
  • v0.5.4
  • v0.5.3
  • v0.5.2
  • v0.5.1
  • v0.5.0
  • v0.3.0
  • v0.2.1
  • v0.2.0
  • v0.1.4
  • v0.1.3
  • v0.1.2
  • v0.1.2-rc.0
  • v0.1.1

Description

Inefficient Algorithmic Complexity vulnerability in ash-project ash_paper_trail allows a user who can submit a large array attribute to a paper-trailed create or update action to cause a denial of service through excessive CPU and memory use.

With full-diff change tracking, AshPaperTrail.ChangeBuilders.FullDiff.ListChange pairs each prior array element against the new list by rebuilding the remaining-elements accumulator with acc ++ [tuple] on every step, copying the growing list each time, so the pairing scales cubically in the array length. Nothing bounds the length and the value comes straight from action input, so one request carrying a large accepted {:array, _} attribute forces tens of seconds of CPU and multi-gigabyte allocations.

This issue affects ash_paper_trail: from 0.1.1 before 0.7.0.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools