CVE-2026-77831: Algorithmic-complexity denial of service in AshPaperTrail full-diff list tracking

Published Aug 30, 2026
·
Updated

Inefficient Algorithmic Complexity vulnerability in ash-project ashpapertrail 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 ashpapertrail: from 0.1.1 before 0.7.0.

Affected Software

1 affected component
ash-project ash_paper_trail>0.1.1<0.7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ash-project ash_paper_trail to a version that resolves this vulnerability.

    Fixed in 0.7.0

Event History

Aug 30, 2026
CVE Published
via MITRE·12:18 AM
Data Sourced
via MITRE·12:18 AM
DescriptionWeakness

Frequently Asked Questions

1

Which deployments are exposed to this denial of service?

Deployments using ash_paper_trail versions from 0.1.1 before 0.7.0 are affected when a paper-trailed create or update action accepts an array attribute and uses full-diff change tracking.

2

What access does an attacker need to trigger the issue?

An attacker needs the ability to submit a large array attribute to an affected paper-trailed create or update action. The oversized value is accepted directly from action input, and the array length is not bounded.

3

Is the default configuration affected?

The issue specifically requires full-diff change tracking. The available information does not establish whether full-diff tracking is enabled by default.

4

What is the impact of a successful request?

A single request with a sufficiently large accepted array can cause tens of seconds of CPU consumption and multi-gigabyte memory allocations, resulting in denial of service.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203