CVE-2026-53769: CWE-862: Missing Authorization in avo-hq avo
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.
AI Analysis
Technical Summary
CVE-2026-53769 describes a missing authorization vulnerability (CWE-862) in the Avo framework for Ruby on Rails, specifically affecting the direct attachment upload endpoint. From version 2.28.0 to before 3.32.0, this endpoint does not enforce server-side upload authorization and bypasses documented field-level upload policy methods such as upload_{FIELD_ID}?. Authenticated users who can reach this endpoint can modify or add attachments, including binary content and metadata, on resolved records regardless of the update? and upload_<field>? policy restrictions. This primarily affects multi-role Avo Pro/Advanced deployments where non-administrator users should have restricted upload capabilities. The vulnerability was patched in version 3.32.0.
Potential Impact
The vulnerability allows authenticated users with access to the Avo attachment upload endpoint to bypass intended upload restrictions and replace or add attachment content on records even when policies deny such operations. This can lead to unauthorized modification of attachments, potentially impacting data integrity and trustworthiness of records in affected deployments. There is no indication of confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability has been officially fixed in Avo version 3.32.0. Users should upgrade to version 3.32.0 or later to remediate this issue. No additional mitigation is required once the update is applied.
CVE-2026-53769: CWE-862: Missing Authorization in avo-hq avo
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.
CVSS v3.1
Score 6.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53769 describes a missing authorization vulnerability (CWE-862) in the Avo framework for Ruby on Rails, specifically affecting the direct attachment upload endpoint. From version 2.28.0 to before 3.32.0, this endpoint does not enforce server-side upload authorization and bypasses documented field-level upload policy methods such as upload_{FIELD_ID}?. Authenticated users who can reach this endpoint can modify or add attachments, including binary content and metadata, on resolved records regardless of the update? and upload_<field>? policy restrictions. This primarily affects multi-role Avo Pro/Advanced deployments where non-administrator users should have restricted upload capabilities. The vulnerability was patched in version 3.32.0.
Potential Impact
The vulnerability allows authenticated users with access to the Avo attachment upload endpoint to bypass intended upload restrictions and replace or add attachment content on records even when policies deny such operations. This can lead to unauthorized modification of attachments, potentially impacting data integrity and trustworthiness of records in affected deployments. There is no indication of confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability has been officially fixed in Avo version 3.32.0. Users should upgrade to version 3.32.0 or later to remediate this issue. No additional mitigation is required once the update is applied.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-pqpw-cvm4-8mv9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53769"]
- Ecosystems
- ["RubyGems"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a50ba7668715ace435803d3
Added to database: 07/10/2026, 09:25:10 UTC
Last enriched: 09/07/2026, 11:05:19 UTC
Last updated: 09/14/2026, 22:12:12 UTC
Views: 145
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.