CVE-2026-53769

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 9, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 4, 2026
Patch available. Sources: github_pr, github_commit, github_release, github.
GitHub release Patch Available

Release v3.32.0

Patch available: avo-hq/avo v3.32.0

https://github.com/avo-hq/avo/releases/tag/v3.32.0
GitHub commit Patch Available

commit de12070dbac0 (avo-hq/avo)

Patch available: avo-hq/avo v4.0.15 (contains commit de12070dbac0)

https://github.com/avo-hq/avo/commit/de12070dbac0cb6a7e2bea357f9697f99e92554c
GitHub pull request Patch Available

fix: attachment upload authorization in attachments controller

Patch available: avo-hq/avo v4.0.15 (PR #4520 merged 2026-06-02)

https://github.com/avo-hq/avo/pull/4520
GitHub advisoryMentions a patch (unverified)

Direct attachment upload endpoint lacks upload authorization and bypasses field-level upload policy · Advisory · avo-hq/avo · GitHub

https://github.com/avo-hq/avo/security/advisories/GHSA-pqpw-cvm4-8mv9

Vendor Advisories for CVE-2026-53769(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
avo2.28.0 ... 3.9.2 (281 versions)
  • 2.28.0 up to 3.32.0: fixed in 3.32.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-12 15:57 UTCEG score recompute
  4. 2026-10-11 19:40 UTCEG score recompute
  5. 2026-10-11 16:55 UTCEG score recompute
  6. 2026-10-11 14:18 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-09-30 20:04 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-09-28 10:26 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 25 more
  1. 2026-09-24 11:23 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-09-23 05:53 UTCEG score recompute
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-09-18 05:35 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  9. 2026-09-14 08:05 UTCEG score recompute
  10. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-09-13 08:18 UTCEG score recompute
  12. 2026-09-12 03:22 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-09-09 16:55 UTCEG score recompute
  16. 2026-09-09 16:04 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  20. 2026-09-05 22:30 UTCEG score recompute
  21. 2026-09-04 21:28 UTCEG score recompute
  22. 2026-07-30 12:13 UTCEG score recompute
  23. 2026-07-26 12:17 UTCEG score recompute
  24. 2026-07-23 03:19 UTCEG score recompute
  25. 2026-07-09 21:46 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-53769?
CVE-2026-53769 is a medium-severity vulnerability; its CVE record was published on July 9, 2026. 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{FIELDID}?. An authenticated Avo…
When was the CVE record for CVE-2026-53769 published?
The CVE record for CVE-2026-53769 was published on July 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-53769 actively exploited?
CVE-2026-53769 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53769?
CVE-2026-53769 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53769?
A fix for CVE-2026-53769 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53769 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53769

Explore →

Is Your Infrastructure Affected by CVE-2026-53769?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs