{"api_version":"1","generated_at":"2026-09-05T03:54:51+00:00","cve":"CVE-2026-53769","urls":{"html":"https://cve.report/CVE-2026-53769","api":"https://cve.report/api/cve/CVE-2026-53769.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53769","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53769"},"summary":{"title":"Avo: Direct attachment upload endpoint lacks upload authorization and bypasses field-level upload policy","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.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-09-04 21:17:25","updated_at":"2026-09-04 21:17:25"},"problem_types":["CWE-862","CWE-863","CWE-862 CWE-862: Missing Authorization","CWE-863 CWE-863: Incorrect Authorization"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"6.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"6.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","data":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"}}],"references":[{"url":"https://github.com/avo-hq/avo/pull/4520","name":"https://github.com/avo-hq/avo/pull/4520","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/avo-hq/avo/security/advisories/GHSA-pqpw-cvm4-8mv9","name":"https://github.com/avo-hq/avo/security/advisories/GHSA-pqpw-cvm4-8mv9","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/avo-hq/avo/commit/de12070dbac0cb6a7e2bea357f9697f99e92554c","name":"https://github.com/avo-hq/avo/commit/de12070dbac0cb6a7e2bea357f9697f99e92554c","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/avo-hq/avo/releases/tag/v3.32.0","name":"https://github.com/avo-hq/avo/releases/tag/v3.32.0","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53769","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53769","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"avo-hq","product":"avo","version":"affected >= 2.28.0, < 3.32.0","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"product":"avo","vendor":"avo-hq","versions":[{"status":"affected","version":">= 2.28.0, < 3.32.0"}]}],"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-862","description":"CWE-862: Missing Authorization","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-863","description":"CWE-863: Incorrect Authorization","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-09-04T20:02:01.456Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/avo-hq/avo/security/advisories/GHSA-pqpw-cvm4-8mv9","tags":["x_refsource_CONFIRM"],"url":"https://github.com/avo-hq/avo/security/advisories/GHSA-pqpw-cvm4-8mv9"},{"name":"https://github.com/avo-hq/avo/pull/4520","tags":["x_refsource_MISC"],"url":"https://github.com/avo-hq/avo/pull/4520"},{"name":"https://github.com/avo-hq/avo/commit/de12070dbac0cb6a7e2bea357f9697f99e92554c","tags":["x_refsource_MISC"],"url":"https://github.com/avo-hq/avo/commit/de12070dbac0cb6a7e2bea357f9697f99e92554c"},{"name":"https://github.com/avo-hq/avo/releases/tag/v3.32.0","tags":["x_refsource_MISC"],"url":"https://github.com/avo-hq/avo/releases/tag/v3.32.0"}],"source":{"advisory":"GHSA-pqpw-cvm4-8mv9","discovery":"UNKNOWN"},"title":"Avo: Direct attachment upload endpoint lacks upload authorization and bypasses field-level upload policy"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-53769","datePublished":"2026-09-04T20:02:01.456Z","dateReserved":"2026-06-10T17:48:40.547Z","dateUpdated":"2026-09-04T20:02:01.456Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-04 21:17:25","lastModifiedDate":"2026-09-04 21:17:25","problem_types":["CWE-862","CWE-863","CWE-862 CWE-862: Missing Authorization","CWE-863 CWE-863: Incorrect Authorization"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"NONE"},"exploitabilityScore":2.8,"impactScore":3.6}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53769","Ordinal":"1","Title":"Avo: Direct attachment upload endpoint lacks upload authorizatio","CVE":"CVE-2026-53769","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53769","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"Avo: Direct attachment upload endpoint lacks upload authorizatio"}]}}}