| CVE-2026-48352US | — | 0.93% (60th) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-48351US | — | 0.93% (60th) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-48439US | — | 0.90% (60th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48438US | — | 0.90% (60th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48295US | — | 0.83% (57th) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-48436US | — | 0.72% (54th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-47922US | — | 0.56% (47th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-34711US | — | 0.43% (37th) | — | ✗no fix | 2026-06-09 | ≤ @contentauth/c2pa-web@0.7.1 |
| CVE-2026-34713US | — | 0.41% (35th) | — | ✗no fix | 2026-06-09 | ≤ @contentauth/c2pa-web@0.7.1 |
| CVE-2026-34712US | — | 0.41% (35th) | — | ✗no fix | 2026-06-09 | ≤ @contentauth/c2pa-web@0.7.1 |
| CVE-2026-48444US | — | 0.30% (23rd) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48442US | — | 0.30% (23rd) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48290US | — | 0.29% (22nd) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-48446US | — | 0.29% (22nd) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48445US | — | 0.29% (21st) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48387US | — | 0.29% (21st) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48354US | — | 0.29% (21st) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-48312US | — | 0.28% (21st) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-71390US | — | 0.27% (19th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48302US | — | 0.27% (19th) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-48353US | — | 0.26% (18th) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-71389US | — | 0.26% (18th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48443US | — | 0.26% (18th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48435US | — | 0.26% (18th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48434US | — | 0.26% (18th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-48357US | — | 0.26% (18th) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-48298US | — | 0.26% (18th) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-48296US | — | 0.26% (18th) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-48287US | — | 0.22% (13th) | — | ✗no fix | 2026-07-14 | ≤ @contentauth/c2pa-web@0.9.0 |
| CVE-2026-34657US | — | 0.18% (7th) | — | ✗no fix | 2026-06-09 | ≤ @contentauth/c2pa-web@0.7.1 |
| CVE-2026-48437US | — | 0.15% (4th) | — | ✗no fix | 2026-08-11 | ≤ 0.12.1 |
| CVE-2026-47905US | — | 0.15% (4th) | — | ✗no fix | 2026-06-09 | ≤ @contentauth/c2pa-web@0.7.1 |
| CVE-2026-47904US | — | 0.15% (4th) | — | ✗no fix | 2026-06-09 | ≤ @contentauth/c2pa-web@0.7.1 |
| CVE-2026-47903US | — | 0.15% (4th) | — | ✗no fix | 2026-06-09 | ≤ @contentauth/c2pa-web@0.7.1 |
| CVE-2026-47902US | — | 0.15% (4th) | — | ✗no fix | 2026-06-09 | ≤ @contentauth/c2pa-web@0.7.1 |