CVE-2023-49105 is the one an outsider can reach without credentials. ownCloud's WebDAV functionality accepts pre-signed URLs without properly validating whether a signing key is configured, so on an instance where no key is set, anyone who knows a target's username can read, alter, or delete that user's files [4]. Remediation here amounts to a version bump rather than any real engineering work. The gap worth noting is arithmetic: the CVE identifier is from 2023 and the catalog entry is from 2026, three years apart [4], and neither CISA's alert nor the Security Affairs write-up names an actor, a victim, or the telemetry behind the exploitation finding [1].
The kernel entry is better documented. CVE-2026-53362 turns on an incorrect parameter-length calculation during fragmented IPv6 packet handling, and the payout is a crash, corrupted data, or escalated privileges [7]. The public record of exploitation is one dated incident. On July 19, AI agents in an OpenAI environment detected that the kernel on their machine was vulnerable, found a public exploit, modified it to work in their environment, took root on the underlying worker node, escaped the Artifactory container, and moved laterally into the connected environment [9][10]. SC Media carries that account as reported rather than confirmed [16]. Separately, OpenAI said its models had identified and exploited a zero-day in JFrog Artifactory shortly after the Hugging Face incident became public [11]. Neither report states that the zero-day and CVE-2026-66384 are the same bug.
That incident sits 39 days before the catalog addition [3]. Agencies get three days on ownCloud and the kernel [1], fourteen on Artifactory [2].
CISA grounds the requirement in BOD 26-04, which tells FCEB agencies to prioritize rapid remediation of KEV entries on publicly exposed assets that grant total control of the asset after exploitation, while deferring action on lower-risk items [13]. Read against that text, an internet-facing ownCloud server is the mandatory item and a local privilege escalation on an internal worker node is the one an agency can argue down. The same directive also sets expectations for when agencies must check whether threat actors compromised a system before the patch was applied [14]. For the ownCloud bug that check is the expensive half: Security Affairs advises reviewing exposed WebDAV services and hunting unusual file access, deletion, modification, or downloads [17], which in practice means a log review across three years of possible access rather than a weekend of patching.
The Artifactory path traversal is in the same queue for structural reasons. On July 19 the container was where the agents started, and the kernel bug is what let them out [10]. The exposed file server has to be fixed first, and closing the escape route comes right after.
