<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>S21sec Cyber Solutions by Thales — recent CVEs</title>
    <link>https://vulnogram.org/</link>
    <atom:link href="https://vulnogram.org/rss/s21sec" rel="self" type="application/rss+xml"/>
    <description>Most recent CVEs assigned by S21sec Cyber Solutions by Thales (s21sec).</description>
    <image>
      <url>https://vulnogram.org/seaview/icons/s21sec.png</url>
      <title>S21sec Cyber Solutions by Thales — recent CVEs</title>
      <link>https://vulnogram.org/</link>
    </image>
    <lastBuildDate>Wed, 21 Oct 2026 07:00:07 GMT</lastBuildDate>
    <item>
      <title>CVE-2026-22539 · 5.3 MEDIUM — INFORMATION DISCLOSURE VIA CURL REQUESTS (OCPP)</title>
      <link>https://vulnogram.org/CVE-2026-22539</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-22539</guid>
      <description>As the service interaction is performed without authentication, an attacker with some knowledge of the protocol could obtain information about the charger via OCPP v1.6.</description>
      <category>Medium</category>
      <pubDate>Wed, 07 Jan 2026 17:12:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-22537 · 6.8 MEDIUM — INFORMATION DISCLOSURE WITHIN THE OPERATING SYSTEM</title>
      <link>https://vulnogram.org/CVE-2026-22537</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-22537</guid>
      <description>The lack of hardening of the system allows the user used to manage and maintain the charger to consult different files containing clear-text credentials or valuable information for an attacker.</description>
      <category>Medium</category>
      <pubDate>Wed, 07 Jan 2026 17:05:41 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-22536 · 8.6 HIGH — PRIVILEGE ESCALATION VIA SUDO COMMAND</title>
      <link>https://vulnogram.org/CVE-2026-22536</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-22536</guid>
      <description>The absence of permissions control for the user XXX allows the current configuration in the sudoers file to escalate privileges without any restrictions</description>
      <category>High</category>
      <pubDate>Wed, 07 Jan 2026 16:47:13 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-22535 · 8.9 HIGH — FRAIL SECURITY IN MQTT PROTOCOL ALLOWS AN ATTACKER MODIFY CRITICAL PARAMETERS</title>
      <link>https://vulnogram.org/CVE-2026-22535</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-22535</guid>
      <description>An attacker with the ability to interact through the network and with access credentials, could, thanks to the unsecured (unencrypted) MQTT communications protocol, write on the server topics of the board that controls the MQTT communications</description>
      <category>High</category>
      <pubDate>Wed, 07 Jan 2026 16:37:18 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-22544 · 8.7 HIGH 🌩️ — EXCHANGE OF CREDENTIALS IN CLEAR TEXT</title>
      <link>https://vulnogram.org/CVE-2026-22544</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-22544</guid>
      <description>An attacker with a network connection could detect credentials in clear text.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 07 Jan 2026 16:23:08 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-22543 · 6.9 MEDIUM — WEEK ENCODING FOR PASSWORDS</title>
      <link>https://vulnogram.org/CVE-2026-22543</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-22543</guid>
      <description>The credentials required to access the device&apos;s web server are sent in base64 within the HTTP headers. Since base64 is not considered a strong cipher, an attacker could intercept the web request handling the login and obtain the credentials</description>
      <category>Medium</category>
      <pubDate>Wed, 07 Jan 2026 16:10:57 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-22542 · 9.2 CRITICAL 🌩️ — DENIAL OF SERVICE FOR CONCURRENT CONNECTIONS ON TELNET</title>
      <link>https://vulnogram.org/CVE-2026-22542</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-22542</guid>
      <description>An attacker with access to the system&apos;s internal network can cause a denial of service on the system by making two concurrent connections through the Telnet service.</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 07 Jan 2026 15:24:04 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-22541 · 8.2 HIGH 🌩️ — DENIAL OF SERVICE VIA ICMP PACKETS</title>
      <link>https://vulnogram.org/CVE-2026-22541</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-22541</guid>
      <description>The massive sending of ICMP requests causes a denial of service on one of the boards from the EVCharger that allows control the EV interfaces. Since the board must be operating correctly for the charger to also function correctly.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 07 Jan 2026 15:12:42 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-22540 · 9.2 CRITICAL 🌩️ — DENIAL OF SERVICE VIA ARP PACKETS</title>
      <link>https://vulnogram.org/CVE-2026-22540</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-22540</guid>
      <description>The massive sending of ARP requests causes a denial of service on one board of the charger that allows control of the EV interfaces. Since the board must be operating correctly for the charger to also function correctly.</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Wed, 07 Jan 2026 14:16:32 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-64385 · 9.2 CRITICAL 🌩️ — INCORRECT SECURITY VALIDATION IN SENDING UDP FRAMES</title>
      <link>https://vulnogram.org/CVE-2025-64385</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-64385</guid>
      <description>The equipment initially can be configured using the manufacturer&apos;s application, by Wi-Fi, by the web server or with the manufacturer’s software. Using the manufacturer&apos;s software, the device can be configured via UDP. Analyzing this communication, it…</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 31 Oct 2025 14:23:06 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-64389 · 8.3 HIGH 🌩️ — EXCHANGE OF SENSITIVE INFORMATION IN CLEAR TEXT</title>
      <link>https://vulnogram.org/CVE-2025-64389</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-64389</guid>
      <description>The web server of the device performs exchanges of sensitive information in clear text through an insecure protocol.</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 31 Oct 2025 14:19:48 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-64388 · 9.2 CRITICAL 🌩️ — Denial of service through specific packets</title>
      <link>https://vulnogram.org/CVE-2025-64388</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-64388</guid>
      <description>Denial of service of the web server through specific requests to this protocol</description>
      <category>Critical</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 31 Oct 2025 14:17:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-64387 · 5.1 MEDIUM 🌩️ — CLICKJACKING</title>
      <link>https://vulnogram.org/CVE-2025-64387</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-64387</guid>
      <description>The web application is vulnerable to a so-called ‘clickjacking’ attack. In this type of attack, the vulnerable page is inserted into a page controlled by the attacker in order to deceive the victim. This deception can range from making the victim cli…</description>
      <category>Medium</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 31 Oct 2025 14:12:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-64386 · 7.7 HIGH 🌩️ — HIJACKING OF THE TOKEN AND GAINING ACCESS</title>
      <link>https://vulnogram.org/CVE-2025-64386</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-64386</guid>
      <description>The equipment grants a JWT token for each connection in the timeline, but during an active valid session, a hijacking of the token can be done. This will allow an attacker with the token modify parameters of security, access or even steal the session…</description>
      <category>High</category>
      <category>Network Exploitable</category>
      <pubDate>Fri, 31 Oct 2025 13:42:32 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2025-11155 · 6.8 MEDIUM — WEAK ENCODING FOR PASSWORD IN DEVICE SERVER CONFIGURATION</title>
      <link>https://vulnogram.org/CVE-2025-11155</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2025-11155</guid>
      <description>The credentials required to access the device&apos;s web server are sent in base64 within the HTTP headers. Since base64 is not considered a strong cipher, an attacker could intercept the web request handling the login and obtain the credentials.</description>
      <category>Medium</category>
      <pubDate>Mon, 29 Sep 2025 15:14:39 GMT</pubDate>
    </item>
  </channel>
</rss>
