AshPaperTrail EUVD-2026-68142

The target application must define one or more Ash resource attributes marked sensitive? true that are actively tracked by AshPaperTrail - meaning those attributes are not excluded via the ignore_attributes configuration list. The version resource must be accessible to the attacker, either via the application's network API (typical for Ash applications using Ash.JsonApi or AshGraphql) or via direct database access. The CVSS 4.0 AT:P (Attack Requirements: Present) captures these deployment-dependent conditions. Exploitation is NOT possible if no attributes are marked sensitive? on tracked resources, if all sensitive attributes are listed in ignore_attributes, or if the version resource's read action is restricted to trusted roles via Ash authorization policies. The vulnerability does not require elevated attacker privileges beyond whatever access is needed to invoke the version resource's default read action.

The provided CVSS 4.0 vector (AV:L/AC:L/AT:P/PR:N/UI:N, score 5.9) designates a local attack vector with a specific attack requirement (AT:P), meaning exploitation depends on the application actually defining sensitive? attributes on tracked Ash resources. However, AV:L may understate real-world network exposure: Ash resources are routinely published over HTTP via Ash.JsonApi or AshGraphql, making the version resource's default read action reachable over the network in many typical deployments - not solely from local system access. The confidentiality impact is high (VC:H) because any value held in a sensitive field - such as tokens, password hashes, or PII - is fully exposed without redaction. No EPSS data was provided, no KEV listing exists, and no POC is known, which together indicate no observed exploitation at time of analysis. Real-world priority is moderate: the flaw is only triggered when the application marks attributes as sensitive? and when the version resource is accessible to lower-trust actors, both of which are common in Ash applications built for audit or compliance purposes. The CVSS score of 5.9 is consistent with the configuration-dependent, confidentiality-only nature of the flaw.

An attacker with authorized read access to an Ash application's version resource - such as a low-privileged internal user, a compromised API client, or any actor permitted by the resource's default read action - queries the version resource over the application's HTTP API. The changes map in each version record contains plaintext values of fields the application intended to protect as sensitive?, such as API keys, password hashes, or personally identifiable information. The attacker iterates through historical version records to harvest every past value of those fields, recovering credentials or PII the application believed was redacted from all output. No public exploit code is known.