What’s Vulnerable › Vulnerabilities

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

• Severity: medium (CVSS 6.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-09-04 · updated 2026-09-30
• Weakness: CWE-862

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.

Affected products

• avo-hq avo: from 2.28.0, < 3.32.0

References

• https://github.com/avo-hq/avo/commit/de12070dbac0cb6a7e2bea357f9697f99e92554c
• https://github.com/avo-hq/avo/pull/4520
• https://github.com/avo-hq/avo/releases/tag/v3.32.0
• https://github.com/avo-hq/avo/security/advisories/GHSA-pqpw-cvm4-8mv9
• https://github.com/avo-hq/avo/security/advisories/GHSA-pqpw-cvm4-8mv9

Get alerted when CVE-2026-53769 or the next vulnerability affects your stack