Called exploited 1009 days after disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing2.8y
- Last KEV listing1d
- Last sightingsame day
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Aug 27, 2026
- EUVDENISA, European Unionlisted Aug 27, 2026
- VulnCheck KEVcommercial researchlisted Aug 26, 2026
- CIRCLaggregator, mirrors the abovelisted Aug 27, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationeuvd.enisa.europa.eu/enisa/EUVD-2023-53114
- reported exploitationprevidian.com/CVE-2023-49105
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
- reported exploitationhunt.io/blog/chinese-speaking-operator-philippine-nuclear-na
4 public reports collected from VulnCheck and CIRCL, first on Aug 26, 2026. Each links to its original source. We have not verified them.
Description
ownCloud contains an improper authentication vulnerability that allows an attacker to access, modify, or delete any file without authentication if the username of a victim is known, and the victim has no signing-key configured.
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
