https://cyberveille.ch/tags/cve-2026-83548/ Recent content in Cve-2026-83548 on CyberVeille Hugo -- 0.146.0 fr-fr Cyberveille CC BY-NC-SA 4.0 Mon, 07 Sep 2026 19:10:52 +0000 https://cyberveille.ch/posts/2026-09-06-cves-weekly/ Mon, 07 Sep 2026 19:10:52 +0000 https://cyberveille.ch/posts/2026-09-06-cves-weekly/ <p>Cette page présente les vulnérabilités <strong>les plus discutées</strong> sur les sources publiques (Fediverse, Bluesky, GitHub, blogs) sur la période analysée.</p> <p>Période analysée : <strong>2026-08-30 → 2026-09-06</strong>.</p> <p>Les données sont collectées via <a href="https://www.vulnerability-lookup.org"><strong>Vulnerability-Lookup (CIRCL)</strong></a> et enrichies automatiquement afin d’aider à la <strong>priorisation de la veille et de la remédiation</strong>.</p> <p>📌 <strong>Légende</strong> :</p> <ul> <li><strong>CVSS</strong> : score officiel de sévérité technique.</li> <li><strong>EPSS</strong> : probabilité d’exploitation observée.</li> <li><strong>VLAI</strong> : estimation de sévérité basée sur une analyse IA du contenu de la vulnérabilité.</li> <li><strong>CISA KEV</strong> : vulnérabilité activement exploitée selon la CISA.</li> <li><strong>seen / exploited</strong> : signaux observés dans les sources publiques.</li> </ul> <style> .badge-wrap { margin:.25rem 0 .5rem 0 } .card { border:1px solid #e8eef5; border-radius:12px; padding:1rem 1.2rem; margin:1rem 0; box-shadow:0 1px 0 rgba(0,0,0,.03); background:#fff; } .card h2 { margin:.1rem 0 .35rem 0; font-size:1.25rem } .small { color:#6c757d; font-size:.95rem } .toot { margin:.5rem 0 .75rem 0 } .kv { display:grid; grid-template-columns: 10ch 1fr; gap:.25rem .75rem; margin:.5rem 0 } .kv div:nth-child(odd){ color:#6c757d } details > summary { cursor:pointer; margin:.25rem 0; font-weight:600 } .toot pre { max-height: 320px; overflow:auto; } /* petit confort pour markdown dans les fiches */ .frdesc p { margin:.25rem 0; } .frdesc ul, .frdesc ol { margin:.4rem 0 .4rem 1.1rem; } .frdesc li { margin:.15rem 0; } .frdesc code { padding:.1rem .25rem; border-radius:6px; } /* Dark mode soigné */ :root { color-scheme: light dark; } @media (prefers-color-scheme: dark) { body { background:#0b1220; color:#e6edf3; } .card { background:#0e1625; border-color:#263244; box-shadow:none; } .card h2 a { color:#c9d1d9; } .small { color:#aab6c3; } .kv div:nth-child(odd){ color:#9aa7b5 } a { color:#7ab7ff; } .toot pre { background:#0b1220; border:1px solid #263244; } } </style> <div class="card" id="CVE-2021-44228"> <h2><a href="https://vulnerability.circl.lu/vuln/CVE-2021-44228">CVE-2021-44228</a></h2> <div class="badge-wrap"><span style="display:inline-block;margin:0 .25rem .4rem 0;padding:.2rem .55rem;border-radius:.55rem;font-size:.85rem;line-height:1;color:white;background:#6c757d;"><strong>CVSS:</strong> N/A</span> <span style="display:inline-block;margin:0 .25rem .4rem 0;padding:.2rem .55rem;border-radius:.55rem;font-size:.85rem;line-height:1;color:white;background:#2563eb;"><strong>EPSS:</strong> 100.00%</span> <span style="display:inline-block;margin:0 .25rem .4rem 0;padding:.2rem .55rem;border-radius:.55rem;font-size:.85rem;line-height:1;color:white;background:#c2410c;"><strong>VLAI:</strong> High (confidence: 0.5546)</span> <span style="display:inline-block;margin:0 .25rem .4rem 0;padding:.2rem .55rem;border-radius:.55rem;font-size:.85rem;line-height:1;color:white;background:#9f1239;">CISA: KEV</span></div> <div class="kv"> <div>Produit</div><div>Apache Software Foundation — Apache Log4j2</div> <div>Publié</div><div>2021-12-10T00:00:00.000Z</div> </div> <p>Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.</p>