Avo: Direct attachment upload endpoint lacks upload authorization and bypasses field-level upload policy (CVE-2026-53769) | HOL Guard CVE

Medium · CVSS 6.5CVE-2026-53769GHSA-PQPW-CVM4-8MV9

Avo: Direct attachment upload endpoint lacks upload authorization and bypasses field-level upload policy

Answer in brief

CVE-2026-53769 records a Medium severity (CVSS 6.5) vulnerability in Avo: Direct attachment upload endpoint lacks upload authorization and bypasses field-level upload policy. The current sources do not mark it as known exploited. The current feed maps avo-hq/avo (generic), avo (rubygems), avo (rubygems). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 4, 2026Updated Sep 9, 2026Source checked Sep 17, 2026First seen by HOL Jul 10, 2026Material review Sep 9, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps avo-hq/avo (generic), avo (rubygems), avo (rubygems). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
avo-hq/avogeneric	>= 2.28.0, < 3.32.0	Not reported
avorubygems	>=2.28.0,<3.32.0	3.32.0
avorubygems	>=2.28.0 <3.32.0	3.32.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for avo-hq/avo, avo, avo.
Review the reported fix. Update avo to 3.32.0; avo to 3.32.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 10, 2026

Sources and claim methodology

Upstream source description

Avo is a framework to create admin panels for Ruby on Rails apps. From version 2.28.0 to before version 3.32.0, Avo's direct attachment upload endpoint lacks server-side upload authorization and bypasses the documented field-level upload policy methods such as upload_{FIELD_ID}?. An authenticated Avo user who can reach the Avo attachment upload endpoint can replace or add attachment content, including binary content, filename, and content-type metadata, on a resolved record even when both update? and upload_<field>? policies deny the operation. This primarily affects multi-role Avo Pro/Advanced-style deployments where non-administrator or restricted operator users can reach Avo and per-record or per-field operations are expected to be enforced by policies. This issue has been patched in version 3.32.0.

Quoted source text, attributed separately from HOL analysis.