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_? 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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-862",
"CWE-863"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53769.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "2.28.0"
},
{
"fixed": "3.32.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "de12070dbac0cb6a7e2bea357f9697f99e92554c"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v3.32.0",
"range": [
{
"fixed": "2aa06624ef6cf7bfd6657cf5b25a2afab29e189d"
}
],
"source": "REFERENCES_TAG"
}
]
}