<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cve-2026-12569 on CyberVeille</title>
    <link>https://cyberveille.ch/tags/cve-2026-12569/</link>
    <description>Recent content in Cve-2026-12569 on CyberVeille</description>
    <generator>Hugo -- 0.146.0</generator>
    <language>fr-fr</language>
    <copyright>Cyberveille CC BY-NC-SA 4.0</copyright>
    <lastBuildDate>Mon, 29 Jun 2026 13:56:36 +0000</lastBuildDate>
    <atom:link href="https://cyberveille.ch/tags/cve-2026-12569/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>🪲 Semaine 26 — CVE les plus discutées</title>
      <link>https://cyberveille.ch/posts/2026-06-28-cves-weekly/</link>
      <pubDate>Mon, 29 Jun 2026 13:56:36 +0000</pubDate>
      <guid>https://cyberveille.ch/posts/2026-06-28-cves-weekly/</guid>
      <description>&lt;p&gt;Cette page présente les vulnérabilités &lt;strong&gt;les plus discutées&lt;/strong&gt; sur les sources publiques
(Fediverse, Bluesky, GitHub, blogs) sur la période analysée.&lt;/p&gt;
&lt;p&gt;Période analysée : &lt;strong&gt;2026-06-21 → 2026-06-28&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Les données sont collectées via &lt;a href=&#34;https://www.vulnerability-lookup.org&#34;&gt;&lt;strong&gt;Vulnerability-Lookup (CIRCL)&lt;/strong&gt;&lt;/a&gt; et enrichies automatiquement
afin d’aider à la &lt;strong&gt;priorisation de la veille et de la remédiation&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;📌 &lt;strong&gt;Légende&lt;/strong&gt; :&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CVSS&lt;/strong&gt; : score officiel de sévérité technique.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;EPSS&lt;/strong&gt; : probabilité d’exploitation observée.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;VLAI&lt;/strong&gt; : estimation de sévérité basée sur une analyse IA du contenu de la vulnérabilité.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CISA KEV&lt;/strong&gt; : vulnérabilité activement exploitée selon la CISA.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;seen / exploited&lt;/strong&gt; : signaux observés dans les sources publiques.&lt;/li&gt;
&lt;/ul&gt;
&lt;style&gt;
.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 &gt; 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; }
}
&lt;/style&gt;
&lt;div class=&#34;card&#34; id=&#34;CVE-2026-20245&#34;&gt;
  &lt;h2&gt;&lt;a href=&#34;https://vulnerability.circl.lu/vuln/CVE-2026-20245&#34;&gt;CVE-2026-20245&lt;/a&gt;&lt;/h2&gt;
  &lt;div class=&#34;badge-wrap&#34;&gt;&lt;span style=&#34;display:inline-block;margin:0 .25rem .4rem 0;padding:.2rem .55rem;border-radius:.55rem;font-size:.85rem;line-height:1;color:white;background:#c2410c;&#34;&gt;&lt;strong&gt;CVSS:&lt;/strong&gt; 7.8&lt;/span&gt; &lt;span style=&#34;display:inline-block;margin:0 .25rem .4rem 0;padding:.2rem .55rem;border-radius:.55rem;font-size:.85rem;line-height:1;color:white;background:#2563eb;&#34;&gt;&lt;strong&gt;EPSS:&lt;/strong&gt; 9.92%&lt;/span&gt; &lt;span style=&#34;display:inline-block;margin:0 .25rem .4rem 0;padding:.2rem .55rem;border-radius:.55rem;font-size:.85rem;line-height:1;color:white;background:#c2410c;&#34;&gt;&lt;strong&gt;VLAI:&lt;/strong&gt; High (confidence: 0.9888)&lt;/span&gt; &lt;span style=&#34;display:inline-block;margin:0 .25rem .4rem 0;padding:.2rem .55rem;border-radius:.55rem;font-size:.85rem;line-height:1;color:white;background:#9f1239;&#34;&gt;CISA: KEV&lt;/span&gt;&lt;/div&gt;
  &lt;div class=&#34;kv&#34;&gt;
    &lt;div&gt;Produit&lt;/div&gt;&lt;div&gt;Cisco — Cisco Catalyst SD-WAN Controller&lt;/div&gt;
    &lt;div&gt;Publié&lt;/div&gt;&lt;div&gt;2026-06-04T22:33:00.748Z&lt;/div&gt;
  &lt;/div&gt;
  &lt;p&gt;A vulnerability in the CLI of Cisco Catalyst SD-WAN Controller, formerly SD-WAN vSmart, Cisco Catalyst SD-WAN Manager, formerly SD-WAN vManage, and Cisco Catalyst SD-WAN Validator, formerly SD-WAN vBond, could allow an authenticated, local attacker to execute arbitrary commands as root by supplying a crafted file to the affected system. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by uploading a crafted file to the affected system. A successful exploit could allow the attacker to perform command injection attacks on an affected system and elevate their privileges as the root user. To exploit this vulnerability, the attacker must have netadmin privileges on the affected system. This would require valid credentials or exploitation of or . Cisco is not aware of successful exploitation by other methods. Cisco has observed limited cases where the exploitation of this bug resulted in a configuration change pushed to edge devices. Cisco recommends that customers upgrade to the fixed software that is documented in the that was published on May 14, 2026, and verify the configuration of the edge devices.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
