<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/a5913a0979c24d238f71d3673c8c98bc&quot; frameborder=&quot;0&quot; width=&quot;3794&quot; height=&quot;2845&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2845</height><width>3794</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2845</thumbnail_height><thumbnail_width>3794</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/a5913a0979c24d238f71d3673c8c98bc-51400947e0067230.gif</thumbnail_url><duration>215.581</duration><title>Deeper CVE Root Cause Tracking</title><description>This Loom explains how expanding evidence and CVE tracking can improve vulnerability remediation when CVEs are caused by embedded dependencies. It notes that a known CVE and root cause may appear inside other applications, such as SQLite embedded in software like Microsoft ToDos and NordVPN, or issues related to components like OpenSSL. The speaker says the approach identifies the affected containing applications, indicates whether patching can remediate the issue, and flags cases where no fix may exist. They also mention an upcoming option to remediate directly from a CVE into the affected applications, and the plan to expand this coverage in the coming weeks.</description></oembed>