{
  "module": "zero_day",
  "generated": 1794388071.1822546,
  "generated_iso": "2026-11-11T09:07:51.182258+00:00",
  "summary": {
    "Critical": 30,
    "High": 75,
    "Medium": 13,
    "Unknown": 1
  },
  "records": [
    {
      "name": "CVE-2024-43661",
      "published": "2025-01-09T08:15:29.450",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "The <redacted>.so library, which is used by <redacted>, is\nvulnerable to a buffer overflow in the code that handles the deletion\nof certificates. This buffer overflow can be triggered by providing a\nlong file path to the <redacted> action of the <redacted>.exe CGI binary or\nto the <redacted>.sh CGI script. This binary or script will write this\nfile path to <redacted>, which is then\nread by <redacted>.so\n\n\nThis issue affects Iocharger firmware for AC models before version 24120701.\n\nLikelihood: Moderate – An attacker will have to find this exploit by\neither obtaining the binaries involved in this vulnerability, or by trial\nand error. Furthermore, the attacker will need a (low privilege)\naccount to gain access to the <redacted>.exe CGI binary or <redacted>.sh\nscript to trigger the vulnerability, or convince a user with such access\nsend an HTTP request that triggers it.\n\n\nImpact: High – The <redacted> process, which we assume is\nresponsible for OCPP communication, will keep crashing after\nperforming the exploit. This happens because the buffer overflow\ncauses the process to segfault before\n<redacted> is removed. This means that,\neven though <redacted> is automatically restarted, it will crash\nagain as soon as it tries to parse the text file.\n\nCVSS clarification. The attack can be executed over any network connection the station is listening to and serves the web interface (AV:N), and there are no additional security measure sin place that need to be circumvented (AC:L), the attack does not rely on preconditions (AT:N). The attack does require authentication, but the level of authentication is irrelevant (PR:L), it does not require user interaction (UI:N). The attack leads to reducred availability of the device (VC:N/VI:N/VA:H). THere is not impact on subsequent systems. (SC:N/SI:N/SA:N). Alltough this device is an EV charger handing significant amounts of power, we do not forsee a safety impact. The attack can be automated (AU:Y). Because the DoS condition is written to disk persistantly, it cannot be recovered by the user (R:I)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43661",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43663",
      "published": "2025-01-09T08:15:29.810",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station",
        "gateway"
      ],
      "surfaces": [
        "EV Charging",
        "Gateway",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "There are many buffer overflow vulnerabilities present in several CGI binaries of the charging station.This issue affects Iocharger firmware for AC model chargers beforeversion 24120701.\n\nLikelihood: High – Given the prevalence of these buffer overflows, and the clear error message of the web server, an attacker is very likely to be able to find these vulnerabilities.\n\nImpact: Low – Usually, overflowing one of these buffers just causes a segmentation fault of the CGI binary, which causes the web server to return a 502 Bad Gateway error. However the webserver itself is not affected, and no DoS can be achieved. Abusing these buffer overflows in a meaningful way requires highly technical knowledge, especially since ASLR also seems to be enabled on the charging station. However, a skilled attacker might be able to use one of these buffer overflows to obtain remote code execution.\n\nCVSS clarification. The attack can be executed over any network connection the station is listening to and serves the web interface (AV:N), and there are no additional security measure sin place that need to be circumvented (AC:L), the attack does not rely on preconditions (AT:N). The attack does require authentication, but the level of authentication is irrelevant (PR:L), it does not require user interaction (UI:N). The attack has a small impact on the availability of the device (VC:N/VI:N/VA:L).  There is no impact on subsequent systems. (SC:N/SI:N/SA:N). While this device is an EV charger handing significant amounts of power, we do not expect  this vulnerability to have a safety impact. The attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43663",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-55705",
      "published": "2026-01-22T23:15:50.137",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "This vulnerability occurs when the system permits multiple simultaneous \nconnections to the backend using the same charging station ID. This can \nresult in unauthorized access, data inconsistency, or potential \nmanipulation of charging sessions. The lack of proper session management\n and expiration control allows attackers to exploit this weakness by \nreusing valid charging station IDs to establish multiple sessions \nconcurrently."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-55705",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-20781",
      "published": "2026-02-27T00:16:55.807",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling \nattackers to perform unauthorized station impersonation and manipulate \ndata sent to the backend. An unauthenticated attacker can connect to the\n OCPP WebSocket endpoint using a known or discovered charging station \nidentifier, then issue or receive OCPP commands as a legitimate charger.\n Given that no authentication is required, this can lead to privilege \nescalation, unauthorized control of charging infrastructure, and \ncorruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-20781",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-24731",
      "published": "2026-02-27T00:16:56.683",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling \nattackers to perform unauthorized station impersonation and manipulate \ndata sent to the backend. An unauthenticated attacker can connect to the\n OCPP WebSocket endpoint using a known or discovered charging station \nidentifier, then issue or receive OCPP commands as a legitimate charger.\n Given that no authentication is required, this can lead to privilege \nescalation, unauthorized control of charging infrastructure, and \ncorruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24731",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-25851",
      "published": "2026-02-27T00:16:57.550",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling \nattackers to perform unauthorized station impersonation and manipulate \ndata sent to the backend. An unauthenticated attacker can connect to the\n OCPP WebSocket endpoint using a known or discovered charging station \nidentifier, then issue or receive OCPP commands as a legitimate charger.\n Given that no authentication is required, this can lead to privilege \nescalation, unauthorized control of charging infrastructure, and \ncorruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25851",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-27767",
      "published": "2026-02-27T00:16:58.073",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling \nattackers to perform unauthorized station impersonation and manipulate \ndata sent to the backend. An unauthenticated attacker can connect to the\n OCPP WebSocket endpoint using a known or discovered charging station \nidentifier, then issue or receive OCPP commands as a legitimate charger.\n Given that no authentication is required, this can lead to privilege \nescalation, unauthorized control of charging infrastructure, and \ncorruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27767",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-27772",
      "published": "2026-02-27T00:16:58.250",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling \nattackers to perform unauthorized station impersonation and manipulate \ndata sent to the backend. An unauthenticated attacker can connect to the\n OCPP WebSocket endpoint using a known or discovered charging station \nidentifier, then issue or receive OCPP commands as a legitimate charger.\n Given that no authentication is required, this can lead to privilege \nescalation, unauthorized control of charging infrastructure, and \ncorruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27772",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-26290",
      "published": "2026-02-27T01:16:20.433",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely \nassociate sessions but allows multiple endpoints to connect using the \nsame session identifier. This implementation results in predictable \nsession identifiers and enables session hijacking or shadowing, where \nthe most recent connection displaces the legitimate charging station and\n receives backend commands intended for that station. This vulnerability\n may allow unauthorized users to authenticate as other users or enable a\n malicious actor to cause a denial-of-service condition by overwhelming \nthe backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26290",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-27028",
      "published": "2026-02-27T01:16:20.790",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling \nattackers to perform unauthorized station impersonation and manipulate \ndata sent to the backend. An unauthenticated attacker can connect to the\n OCPP WebSocket endpoint using a known or discovered charging station \nidentifier, then issue or receive OCPP commands as a legitimate charger.\n Given that no authentication is required, this can lead to privilege \nescalation, unauthorized control of charging infrastructure, and \ncorruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27028",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-27647",
      "published": "2026-02-27T01:16:20.967",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely \nassociate sessions but allows multiple endpoints to connect using the \nsame session identifier. This implementation results in predictable \nsession identifiers and enables session hijacking or shadowing, where \nthe most recent connection displaces the legitimate charging station and\n receives backend commands intended for that station. This vulnerability\n may allow unauthorized users to authenticate as other users or enable a\n malicious actor to cause a denial-of-service condition by overwhelming \nthe backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27647",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-22552",
      "published": "2026-03-06T00:16:10.347",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling attackers to perform unauthorized station impersonation and manipulate data sent to the backend. An unauthenticated attacker can connect to the OCPP WebSocket endpoint using a known or discovered charging station identifier, then issue or receive OCPP commands as a legitimate charger. Given that no authentication is required, this can lead to privilege escalation, unauthorized control of charging infrastructure, and corruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22552",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-26051",
      "published": "2026-03-06T15:16:09.973",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling attackers to perform unauthorized station impersonation and manipulate data sent to the backend. An unauthenticated attacker can connect to the OCPP WebSocket endpoint using a known or discovered charging station identifier, then issue or receive OCPP commands as a legitimate charger. Given that no authentication is required, this can lead to privilege escalation, unauthorized control of charging infrastructure, and corruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26051",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-26288",
      "published": "2026-03-06T16:16:10.723",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling attackers to perform unauthorized station impersonation and manipulate data sent to the backend. An unauthenticated attacker can connect to the OCPP WebSocket endpoint using a known or discovered charging station identifier, then issue or receive OCPP commands as a legitimate charger. Given that no authentication is required, this can lead to privilege escalation, unauthorized control of charging infrastructure, and corruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26288",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-25192",
      "published": "2026-03-20T23:16:42.780",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling attackers to perform unauthorized station impersonation and manipulate data sent to the backend. An unauthenticated attacker can connect to the OCPP WebSocket endpoint using a known or discovered charging station identifier, then issue or receive OCPP commands as a legitimate charger. Given that no authentication is required, this can lead to privilege escalation, unauthorized control of charging\ninfrastructure, and corruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25192",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-29796",
      "published": "2026-03-20T23:16:43.410",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "WebSocket endpoints lack proper authentication mechanisms, enabling attackers to perform unauthorized station impersonation and manipulate data sent to the backend. An unauthenticated attacker can connect to the OCPP WebSocket endpoint using a known or discovered charging station identifier, then issue or receive OCPP commands as a legitimate charger. Given that no authentication is required, this can lead to privilege escalation, unauthorized control of charging infrastructure, and corruption of charging network data reported to the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29796",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-20744",
      "published": "2026-07-10T23:16:47.683",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "The charging station websocket endpoint accepts connections without \nproper authentication, which could lead to privilege escalation."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-20744",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-8986",
      "published": "2026-07-21T22:19:11.023",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "diagnostics",
        "ocpp"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "Autel Maxi Charger Single firmware through V1.03.51 is vulnerable to OS command injection when processing OCPP GetDiagnostics requests. A malicious or compromised OCPP server can supply a crafted diagnostics URL that results in arbitrary command execution on the charging station."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-8986",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-44101",
      "published": "2026-07-30T07:16:58.357",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Due to missing authentication the CHARX OCPP Agent service allows an unauthenticated remote attacker to reconfigure the backend connection. This can lead to Denial-of-Service and confidential data being disclosed to the attacker."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44101",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-13214",
      "published": "2026-08-25T05:17:20.060",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The OCPP 1.6 client in subsys/net/lib/ocpp/ocpp_j.c contains a stack buffer overflow in parse_getconfig_msg(). When handling a GetConfiguration request from the central system, the handler copied the attacker-controlled JSON \"key\" string into the caller's fixed 50-byte stack buffer (skey[CISTR50], declared in subsys/net/lib/ocpp/ocpp.c) using an unbounded strcpy(). The parsed key value points directly into the receive buffer, so its length is bounded only by the message size (CONFIG_OCPP_RECV_BUFFER_SIZE, default 2048).\n\nThe GetConfiguration message is delivered over the WebSocket connection that the charge point opens to its configured central system. The reader thread ocpp_wsreader() reads the message into ui->recv_buf and dispatches it to parse_getconfig_msg() via the PDU function table. An attacker who controls the central system endpoint, or a man-in-the-middle on an unencrypted connection, can send a GetConfiguration request whose \"key\" field exceeds 50 bytes and overflow the reader thread's stack with attacker-chosen bytes.\n\nThe consequence is a remotely triggerable stack smash on the OCPP reader thread: at minimum a denial of service, and plausibly remote code execution depending on build-time hardening such as stack canaries and MPU configuration. The fix replaces the strcpy() with a bounded strncpy(key, payload.key[0], CISTR50 - 1) followed by explicit NUL termination, matching the bounded copies already used by the sibling handlers."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-13214",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-112354",
      "published": "2026-11-03T22:17:44.660",
      "score": "Critical",
      "cvss": 9.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "Etrel INCH AC charging station management web interface prior to firmware versions 7.1.2 and 8.0.1 contains a hard-coded default credentials vulnerability that allows remote attackers to gain full Administrator access by authenticating with the factory-default account. Attackers can log in over cleartext HTTP to obtain complete charger configuration, OCPP ChargePoint Identity, and CSMS WebSocket connection details, enabling unauthorized administrative control of the charging station."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112354",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-6029",
      "published": "2025-06-13T15:15:21.430",
      "score": "Critical",
      "cvss": 9.4,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "keyless entry",
      "keywords": [
        "keyless entry",
        "kia"
      ],
      "matched_terms": [
        "key fob",
        "keyless",
        "kia"
      ],
      "surfaces": [
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Use of fixed learning codes, one code to lock the car and the other code to unlock it, the Key Fob Transmitter in KIA-branded Aftermarket Generic Smart  Keyless Entry System, primarily distributed in Ecuador, which allows a replay attack.\n\nManufacture is unknown at the time of release.  CVE Record will be updated once this is clarified."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-6029",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-6030",
      "published": "2025-06-13T15:15:21.600",
      "score": "Critical",
      "cvss": 9.4,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "keyless entry",
      "keywords": [
        "keyless entry",
        "kia"
      ],
      "matched_terms": [
        "key fob",
        "keyless",
        "kia"
      ],
      "surfaces": [
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Use of fixed learning codes, one code to lock the car and the other code to unlock it, in the Key Fob Transmitter in Cyclone Matrix TRF Smart  Keyless Entry System, which allows a replay attack.\n\nResearch was completed on the 2024 KIA Soluto.  Attack confirmed on other KIA Models in Ecuador."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-6030",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43650",
      "published": "2025-01-09T08:15:27.417",
      "score": "Critical",
      "cvss": 9.3,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Iocharger firmware for AC models allows OS Command Injection as root\n\nThis issue affects  firmware versions before 24120701.\n\nLikelihood: Moderate – The <redacted> binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the <redacted> binary, or convince a user with such access to execute a crafted HTTP request.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete\nfiles and services.\n\nCVSS clarification: The attack can be executed over any network connection serving the web interface (AV:N). There are no additional measures that need to be circumvented (AC:L) or attack preconditions (AT:N). THe attack is privileged, but the level does not matter (PR:L) and does not require user interaction (UI:N). Attack leads to full system compromised (VC:H/VI:H/VA:H) and compromised devices can be used to \"pivot\" to other networks that should be unreachable (SC:L/SI:L/SA:H). Because this an EV charger using high power, there is a potential safety impact (S:P). The attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43650",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43651",
      "published": "2025-01-09T08:15:27.590",
      "score": "Critical",
      "cvss": 9.3,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root\nThis issue affects Iocharger firmware for AC models before version 241207101\n\nLikelihood: Moderate – The <redacted> binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the <redacted> binary, or convince a user with such access to execute a crafted HTTP request.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete files and services.\n\nCVSS clarification: Any network connection serving the web interface is vulnerable (AV:N) and there are no additional measures to circumvent (AC:L) nor does the attack require special conditions to be present (AT:N). The attack requires authentication, but the level does not matter (PR:L), nor is user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H) and a compromised device can be used to potentially \"pivot\" into a network that should nopt be reachable (SC:L/SI:L/SA:H). Because this is an EV charger handing significant power, there is a potential safety impact (S:P). THe attack can be autometed (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43651",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43655",
      "published": "2025-01-09T08:15:28.300",
      "score": "Critical",
      "cvss": 9.3,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root\n\nThis issue affects Iocharger firmware for AC model chargers before version 24120701.\n\nLikelihood: Moderate – The attacker will first need to find the name of the script, and needs a (low privilege) account to gain access to the script, or convince a user with such access to execute a request to it.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles and services.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43655",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-32058",
      "published": "2026-02-15T11:15:52.773",
      "score": "Critical",
      "cvss": 9.3,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus",
        "infotainment",
        "nissan"
      ],
      "matched_terms": [
        "bosch",
        "can bus",
        "ecu",
        "infotainment",
        "nissan"
      ],
      "surfaces": [
        "CAN Bus",
        "ECU",
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "The Infotainment ECU manufactured by Bosch uses a RH850 module for CAN communication. RH850 is connected to infotainment over the INC interface through a custom protocol. There is a vulnerability during processing requests of this protocol on the V850 side which allows an attacker with code execution on the infotainment main SoC to perform code execution on the RH850 module and subsequently send arbitrary CAN messages over the connected CAN bus.\n\n\n\nFirst identified on Nissan Leaf ZE1 manufactured in 2020."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32058",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-27815",
      "published": "2026-03-26T17:16:34.063",
      "score": "Critical",
      "cvss": 9.1,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "evse",
      "keywords": [
        "evse"
      ],
      "matched_terms": [
        "evse",
        "iso15118"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "EVerest is an EV charging software stack. Prior to versions to 2026.02.0, ISO15118_chargerImpl::handle_session_setup copies a variable-length payment_options list into a fixed-size array of length 2 without bounds checking. With schema validation disabled by default, oversized MQTT Cmd payloads can trigger out-of-bounds writes and corrupt adjacent EVSE state or crash the process. Version 2026.02.0 contains a patch."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27815",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-27816",
      "published": "2026-03-26T17:16:34.210",
      "score": "Critical",
      "cvss": 9.1,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "evse",
      "keywords": [
        "evse"
      ],
      "matched_terms": [
        "evse",
        "iso15118"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "EVerest is an EV charging software stack. Prior to versions to 2026.02.0, ISO15118_chargerImpl::handle_update_energy_transfer_modes copies a variable-length list into a fixed-size array of length 6 without bounds checking. With schema validation disabled by default, oversized MQTT Cmd payloads can trigger out-of-bounds writes and corrupt adjacent EVSE state or crash the process. Version 2026.02.0 contains a patch."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27816",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-69515",
      "published": "2026-04-07T20:16:22.950",
      "score": "Critical",
      "cvss": 9.1,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment"
      ],
      "matched_terms": [
        "infotainment"
      ],
      "surfaces": [
        "GNSS",
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "An issue in JXL 9 Inch Car Android Double Din Player Android v12.0 allows attackers to force the infotainment system into accepting falsified GPS signals as legitimate, resulting in the device reporting an incorrect or static location."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69515",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43648",
      "published": "2025-01-09T08:15:26.980",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Command injection in the <redacted> parameter of a <redacted>.exe request leads to remote code execution as the root user.\n\nThis issue affects Iocharger firmware for AC models before version 24120701.\n\nLikelihood: Moderate – This action is not a common place for command injection vulnerabilities to occur. Thus, an attacker will likely only be able to find this vulnerability by reverse-engineering the firmware or trying it on all <redacted> fields. The attacker will also need a (low privilege) account to gain access to the <redacted> binary, or convince a user with such access to execute a payload.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete files and services.\n\nCVSS clarification. The attack can be executed over any network connection the station is listening to and serves the web interface (AV:N), and there are no additional security measure sin place that need to be circumvented (AC:L), the attack does not rely on preconditions (AT:N). The attack does require authentication, but the level of authentication is irrelevant (PR:L), it does not require user interaction (UI:N). If is a full system compromise, potentially fully compromising confidentiality, integrity and availability of the devicer (VC:H/VI:H/VA:H).  A compromised charger can be used to \"pivot\" onto networks that should otherwise be closed, cause a low confidentiality and interity impact on subsequent systems. (SC:L/SI:L/SA:H). Because this device is an EV charger handing significant amounts of power, we suspect this vulnerability can have a safety impact (S:P). The attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43648",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43649",
      "published": "2025-01-09T08:15:27.233",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "Authenticated command injection in the filename of a <redacted>.exe request leads to remote code execution as the root user.\n\nThis issue affects Iocharger firmware for AC models before version 24120701.\n\nLikelihood: Moderate – This action is not a common place for command injection vulnerabilities to occur. Thus, an attacker will likely only be able to find this vulnerability by reverse-engineering the firmware or trying it on all <redacted> fields. The attacker will also need a (low privilege) account to gain access to the <redacted> binary, or convince a user with such access to execute a payload.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete files and services.\n\nCVSS clarification: This attack can be performed over any network conenction serving the web interfacr (AV:N), and there are not additional mitigating measures that need to be circumvented (AC:L) or other prerequisites (AT:N). The attack does require privileges, but the level does not matter (PR:L), there is no user interaction required (UI:N). The attack leeds to a full compromised of the charger (VC:H/VI:H/VA:H) and a compromised charger can be used to \"pivot\" to networks that should normally not be reachable (SC:L/SI:L/SA:H). Because this is an EV chargers with significant pwoer, there is a potential safety imp0act (S:P). THis attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43649",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43652",
      "published": "2025-01-09T08:15:27.757",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root\nThis issue affects Iocharger firmware for AC model chargers before version 24120701\n\nLikelihood: Moderate – The <redacted> binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the <redacted> binary, or convince a user with such access to execute a crafted HTTP request.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete\nfiles and services."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43652",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43653",
      "published": "2025-01-09T08:15:27.950",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability  allows OS Command Injection as root\nThis issue affects Iocharger firmware for AC model chargers before version 24120701.\n\nLikelihood: Moderate – The <redacted> binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the <redacted> binary, or convince a user with such access to execute a crafted HTTP request.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete\nfiles and services.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43653",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43654",
      "published": "2025-01-09T08:15:28.127",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Iocharger  firmware for AC models allows OS Command Injection as root\nThis issue affects all Iocharger AC EV charger models on a firmware version before 25010801.\n\nLikelihood: Moderate – The <redacted> binary does not seem to be used by the web interface, so it might be more difficult to find. It seems to be largely the same binary as used by the Iocharger Pedestal charging station, however. The attacker will also need a (low privilege) account to gain access to the <redacted> binary, or convince a user with such access to execute a crafted HTTP request.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and delete\nfiles and services.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43654",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43656",
      "published": "2025-01-09T08:15:28.487",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root\n\nThis issue affects Iocharger firmware for AC model chargers before version 24120701.\n\nLikelihood: Moderate – It might be difficult for an attacker to identify the file structure of the <redated> directory, and then modify the backup to add a new CGI script in the correct directory. Furthermore, the attacker will need an account to restore the settings backup, or convince a user with such access to upload a modified backup file.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles and services.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43656",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43657",
      "published": "2025-01-09T08:15:28.680",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability allows OS Command Injection as root\n\nThis issue affects Iocharger firmware for AC model chargers before version 24120701.\n\nLikelihood: High. However, the attacker will need a (low privilege) account to gain access to the action.exe CGI binary and upload the crafted firmware file, or convince a user with such access to upload it.\n\nImpact: Critical – The attacker has full control over the charging station as the root user, and can arbitrarily add, modify and deletefiles and services.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads to a full compromised (VC:H/VI:H/VA:H), and compromised devices can be used to pivot into networks that should potentially not be accessible (SC:L/SI:L/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43657",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-23971",
      "published": "2025-01-31T00:15:09.920",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of ChargePoint Home Flex charging stations. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the handling of OCPP messages. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-23971",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-25271",
      "published": "2025-07-08T07:15:25.270",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "An unauthenticated adjacent attacker is able to configure a new OCPP backend, due to insecure defaults for the configuration interface."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-25271",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-32059",
      "published": "2026-02-15T11:15:53.880",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment",
        "nissan"
      ],
      "matched_terms": [
        "alpine",
        "bosch",
        "ecu",
        "infotainment",
        "nissan"
      ],
      "surfaces": [
        "Bluetooth",
        "ECU",
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "The specific flaw exists within the Bluetooth stack developed by Alps Alpine of the Infotainment ECU manufactured by Bosch. The issue results from the lack of proper boundary validation of user-supplied data, which can result in a stack-based buffer overflow when receiving a specific packet on the established upper layer L2CAP channel. An attacker can leverage this vulnerability to obtain remote code execution on the Infotainment ECU with root privileges.\n\n\n\nFirst identified on Nissan Leaf ZE1 manufactured in 2020."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32059",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-32061",
      "published": "2026-02-15T11:15:54.170",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment",
        "nissan"
      ],
      "matched_terms": [
        "alpine",
        "bosch",
        "ecu",
        "infotainment",
        "nissan"
      ],
      "surfaces": [
        "Bluetooth",
        "ECU",
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "The specific flaw exists within the Bluetooth stack developed by Alps Alpine of the Infotainment ECU manufactured by Bosch. The issue results from the lack of proper boundary validation of user-supplied data, which can result in a stack-based buffer overflow when receiving a specific packet on the established upper layer L2CAP channel. An attacker can leverage this vulnerability to obtain remote code execution on the Infotainment ECU with root privileges.\n\n\n\nFirst identified on Nissan Leaf ZE1 manufactured in 2020."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32061",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-32062",
      "published": "2026-02-15T11:15:54.307",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment",
        "nissan"
      ],
      "matched_terms": [
        "alpine",
        "bosch",
        "ecu",
        "infotainment",
        "nissan"
      ],
      "surfaces": [
        "Bluetooth",
        "ECU",
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "The specific flaw exists within the Bluetooth stack developed by Alps Alpine of the Infotainment ECU manufactured by Bosch. The issue results from the lack of proper boundary validation of user-supplied data, which can result in a stack-based buffer overflow when receiving a specific packet on the established upper layer L2CAP channel. An attacker can leverage this vulnerability to obtain remote code execution on the Infotainment ECU with root privileges.\n\n\n\nFirst identified on Nissan Leaf ZE1 manufactured in 2020."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32062",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-72124",
      "published": "2026-08-15T06:21:29.720",
      "score": "High",
      "cvss": 8.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "isotp",
      "keywords": [
        "isotp"
      ],
      "matched_terms": [
        "isotp"
      ],
      "surfaces": [
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: isotp: serialize TX state transitions under so->rx_lock\n\nThe TX state machine (so->tx.state) is driven from three contexts:\nsendmsg() claiming and progressing a transfer, the RX path consuming\nFlow Control/echo frames, and two hrtimers timing out a stalled\ntransfer. Mixing a lock-free cmpxchg() claim in sendmsg() with\nhrtimer_cancel() calls made under so->rx_lock elsewhere left windows\nwhere a frame or timer callback could act on a state that had already\nmoved on, corrupting an unrelated transfer.\n\nso->rx_lock now covers the full lifecycle of a TX claim: sendmsg()\ntakes it to check so->tx.state is ISOTP_IDLE, switch it to\nISOTP_SENDING, bump so->tx_gen and drain the previous transfer's\ntimers - all as one critical section. isotp_rcv_fc()/isotp_rcv_cf()\nalready run under this lock via isotp_rcv(), and isotp_rcv_echo() now\ntakes it itself, so none of them can ever observe a transfer mid-claim.\nThis also means a transfer can no longer be handed to sendmsg()'s\ncleanup paths (signal or send error) while another thread is\nconcurrently claiming or finishing it, so those paths can cancel\ntimers and reset the state unconditionally.\n\nisotp_release() claims the socket the same way, so a racing sendmsg()\nsees a consistent ISOTP_SHUTDOWN and skips arming its timer or sending.\n\nOnly the hrtimer callbacks stay outside so->rx_lock, since they run\nunder so->rx_lock's cancellation elsewhere and taking it themselves\nwould deadlock. so->tx_gen lets them recognize whether the transfer\nthey timed out is still the one currently active, so they don't\nreport an error against a transfer that has since completed or been\nsuperseded."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72124",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-22099",
      "published": "2026-07-13T10:16:27.523",
      "score": "High",
      "cvss": 8.7,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Bluetooth",
        "EV Charging",
        "Identity",
        "OTA"
      ],
      "vulnerabilities": [
        {
          "text": "The charging station does not require authentication for Bluetooth commands to perform actions. The functionality exposed includes sensitive information leakage, triggering reboots, or pushing a firmware update URL."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22099",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-22105",
      "published": "2026-10-30T11:17:32.700",
      "score": "High",
      "cvss": 8.7,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "Delta UFC500 charging stations derive the default credentials of the Service account from character positions of the device serial number. An unauthenticated attacker with adjacent network access can reconstruct the resulting password, or exhaust the keyspace, and log in to read and change sensitive settings such as the OCPP backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22105",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-34251",
      "published": "2025-10-07T00:15:34.357",
      "score": "High",
      "cvss": 8.6,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "telematics",
      "keywords": [
        "telematics",
        "telematics control unit",
        "tesla"
      ],
      "matched_terms": [
        "tcu",
        "telematics control unit",
        "tesla"
      ],
      "surfaces": [
        "Identity",
        "Telematics"
      ],
      "vulnerabilities": [
        {
          "text": "Tesla Telematics Control Unit (TCU) firmware prior to v2025.14 contains an authentication bypass vulnerability. The TCU runs the Android Debug Bridge (adbd) as root and, despite a “lockdown” check that disables adb shell, still permits adb push/pull and adb forward. Because adbd is privileged and the device’s USB port is exposed externally, an attacker with physical access can write an arbitrary file to a writable location and then overwrite the kernel’s uevent_helper or /proc/sys/kernel/hotplug entries via ADB, causing the script to be executed with root privileges."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-34251",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-24912",
      "published": "2026-03-06T00:16:10.553",
      "score": "High",
      "cvss": 8.6,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers and enables session hijacking or shadowing, where the most recent connection displaces the legitimate charging station and receives backend commands intended for that station. This vulnerability may allow unauthorized users to authenticate as other users or enable\na malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24912",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-20748",
      "published": "2026-03-06T16:16:09.707",
      "score": "High",
      "cvss": 8.6,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers and enables session hijacking or shadowing, where the most recent connection displaces the legitimate charging station and receives backend commands intended for that station. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-20748",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-27764",
      "published": "2026-03-06T16:16:11.267",
      "score": "High",
      "cvss": 8.6,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers and enables session hijacking or shadowing, where the most recent connection displaces the legitimate charging station and receives backend commands intended for that station. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27764",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-22100",
      "published": "2026-07-13T10:16:27.670",
      "score": "High",
      "cvss": 8.6,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The OCPP DataTransfer message `ReserveLogin` is vulnerable to command injection. By manipulating the data value, arbitrary OS commands can be executed as root."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22100",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-44098",
      "published": "2026-07-30T07:16:57.950",
      "score": "High",
      "cvss": 8.6,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "This vulnerability allows an unauthenticated remote attacker with control over the OCPP backend via firewall-bypass to perform an OS command injection, resulting in the execution of arbitrary commands as the  limited user charx-oa. Charging could be interrupted."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44098",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-10848",
      "published": "2026-08-02T17:16:58.163",
      "score": "High",
      "cvss": 8.6,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The OCPP 1.6 client in subsys/net/lib/ocpp parsed inbound WAMP RPC frames in parse_rpc_msg() (subsys/net/lib/ocpp/ocpp_j.c) using a hand-rolled helper, extract_string_field(), that copied the message's uid and action fields with strncpy(out_buf, token + 1, outlen - 1) and then scanned the result with strchr(out_buf, '\"'). Because strncpy does not NUL-terminate the destination when the source is at least outlen - 1 (127) bytes long, the subsequent strchr reads past the 128-byte destination buffer into adjacent stack memory; if a \" byte is found beyond the buffer, a one-byte out-of-bounds NUL write also occurs. A related defect in extract_payload() runs strchr/strrchr over the receive buffer, which may not be NUL-terminated when a maximal-length frame fills it.\n\nThe parsed bytes come directly from the OCPP central-system server over a websocket: the reader thread fills recv_buf via websocket_recv_msg() and calls parse_rpc_msg() on each inbound DATA frame (subsys/net/lib/ocpp/ocpp.c). A malicious or compromised central server, or an on-path attacker (OCPP is commonly deployed over plain ws://), can send an RPC frame whose uid or action field is 127+ bytes with no closing quote, triggering the out-of-bounds access.\n\nThe primary impact is a remotely triggerable denial of service: the unbounded scan can fault on an unmapped page, and the stray NUL write can corrupt adjacent stack state. The over-read data is not reflected to the peer, so disclosure is limited. The feature is EXPERIMENTAL and must be explicitly enabled (CONFIG_OCPP). The fix replaces the manual parser with the bounds-respecting json_mixed_arr_parse() and copies the extracted uid with an explicitly NUL-terminated buffer, eliminating both over-reads."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-10848",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-97898",
      "published": "2026-09-25T10:17:08.907",
      "score": "High",
      "cvss": 8.4,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "keyless entry",
      "keywords": [
        "keyless entry"
      ],
      "matched_terms": [
        "keyless"
      ],
      "surfaces": [
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Insecure Direct Object Reference / missing object-level authorization in the Akia keyless entry cloud service. The unlock action is relying on a client-supplied room/door identifier that is not properly authorized server-side against the authenticated guest's booking. An authenticated guest could unlock rooms other than their own, resulting in unauthorized physical access to guest rooms at an affected property.\n\n\n\n\nAs of 19th September 2026 the service is no more vulnerable to this attack (feedback received by the reporter). \n\n\n\n\nThe attack is remote but the effect is local to an affected property."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97898",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-54413",
      "published": "2026-06-14T18:17:20.943",
      "score": "High",
      "cvss": 8.2,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "uds",
      "keywords": [
        "uds"
      ],
      "matched_terms": [
        "can bus",
        "doip",
        "ecus",
        "iso-tp",
        "obd-ii",
        "uds"
      ],
      "surfaces": [
        "CAN Bus",
        "DOIP",
        "ECU",
        "ISO-TP",
        "UDS Diagnostics"
      ],
      "vulnerabilities": [
        {
          "text": "driftregion iso14229 through 0.9.0 contains an integer underflow and downstream out-of-bounds read in the Handle_0x27_SecurityAccess function in iso14229.c that allows a remote unauthenticated attacker to crash a UDS server and potentially read memory past the receive buffer by sending a single-byte 0x27 SecurityAccess request that follows any earlier well-formed 0x27 message."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54413",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-9397",
      "published": "2026-05-24T21:16:32.767",
      "score": "High",
      "cvss": 8.1,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ota update",
      "keywords": [
        "charging station",
        "ota update"
      ],
      "matched_terms": [
        "charging station",
        "ota",
        "ota update"
      ],
      "surfaces": [
        "EV Charging",
        "OTA"
      ],
      "vulnerabilities": [
        {
          "text": "A weakness has been identified in Besen BS20 EV Charging Station up to 20260426. Affected by this issue is some unknown functionality of the component OTA Update Installation Handler. This manipulation causes improper authorization. The attack is possible to be carried out remotely. A high degree of complexity is needed for the attack. The exploitation is known to be difficult. The original disclosure mentions, that \"[t]hese vulnerabilities have been reported to Besen and we have received their acknowlegement that they are reviewing this as of April 2026.\""
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-9397",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-10653",
      "published": "2026-06-30T17:16:20.160",
      "score": "High",
      "cvss": 8.1,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "iso-tp",
      "keywords": [
        "iso-tp"
      ],
      "matched_terms": [
        "iso-tp"
      ],
      "surfaces": [
        "Bluetooth",
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "The Zephyr net_buf library (lib/net_buf/buf.c) manipulated both of its reference counts -- the per-header buf->ref and the per-data-block ref_count at the start of each variable/heap data allocation -- with plain non-atomic C operators (buf->ref++, if (--buf->ref > 0), if (--(*ref_count))).\n\nThe API is documented as self-synchronizing: callers may share one buffer across threads (e.g. via k_fifo) and each holder independently calls net_buf_unref() with no surrounding lock. Under true concurrency (SMP, or single-core preemption between the non-atomic load and store while another context unrefs the same buffer), two holders can both observe the same prior reference value and both conclude they are the last reference.\n\nFor heap/variable-data pools (mem_pool_data_unref/heap_data_unref, used by zbus message subscribers, the IP stack RX/TX buffers when CONFIG_NET_BUF_FIXED_DATA_SIZE=n, capture, wireguard, ISO-TP and usbip) this produces a double k_heap_free()/k_free() of the same block -- heap-metadata corruption and a use-after-free on the heap-hardening poison pattern.\n\nFor the per-header refcount the buffer is returned to the pool free LIFO twice for any pool type (including fixed-data pools used by Bluetooth and networking), corrupting the free list so a later allocation hands the same buffer to two owners.\n\nThe fix converts both refcounts to atomic_inc/atomic_dec (overlaying buf->ref in an atomic_t-sized union and changing the data-block refcount from uint8_t to atomic_t).\n\nImpact is gated on genuine concurrency and on an application architecture that shares one buffer among multiple independent unref'ers; the trigger is a refcount/timing race rather than packet content, so an external attacker has at most weak indirect influence over the race window. Affects all Zephyr releases through v4.4.0.\n\nThis fix is not being backported to v3.7-branch (LTS). The backport was attempted and closed unmerged (#111181): the v3.7 networking tree has diverged from main, and the new atomic word-packing -- together with the assertions it adds -- turns pre-existing v3.7-only reference-counting defects elsewhere in the stack into hard faults, so landing the change faithfully would mean pulling an open-ended set of additional v3.7-only fixes into an LTS branch. v3.7 remains affected. Applications on v3.7 that share one net_buf across threads should serialize their own net_buf_unref() calls rather than rely on the documented self-synchronizing behaviour. The fix is on main and has been backported to v4.3-branch (#110852) and v4.4-branch (#110853)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-10653",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-13308",
      "published": "2026-07-29T21:17:46.490",
      "score": "High",
      "cvss": 8.1,
      "cvss_version": "3.0",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Autel MaxiCharger AC Elite Home WebSockets Integer Underflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Autel MaxiCharger AC Elite Home EV chargers. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the handling of WebSocket messages related to the OCPP service. The issue results from the lack of proper validation of user-supplied data, which can result in an integer underflow before allocating a buffer. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-29113."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-13308",
      "fuzzing": []
    },
    {
      "name": "CVE-2023-28905",
      "published": "2025-06-28T16:15:22.410",
      "score": "High",
      "cvss": 8.0,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment",
        "skoda"
      ],
      "matched_terms": [
        "infotainment",
        "skoda"
      ],
      "surfaces": [
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "A heap buffer overflow in the image processing binary of the MIB3 infotainment unit allows an attacker to execute arbitrary code on it.\nThe vulnerability was originally discovered in Skoda Superb III car with MIB3 infotainment unit OEM part number 3V0035820. The list of affected MIB3 OEM part numbers is provided in the referenced resources."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-28905",
      "fuzzing": []
    },
    {
      "name": "CVE-2023-28909",
      "published": "2025-06-28T16:15:23.080",
      "score": "High",
      "cvss": 8.0,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment",
        "skoda"
      ],
      "matched_terms": [
        "infotainment",
        "skoda"
      ],
      "surfaces": [
        "Bluetooth",
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "A specific flaw exists within the Bluetooth stack of the MIB3 unit. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow when receiving fragmented HCI packets on a channel. An attacker can leverage this vulnerability to bypass the MTU check on a channel with enabled fragmentation. Consequently, this can lead to a buffer overflow in upper layer profiles, which can be used to obtain remote code execution.\nThe vulnerability was originally discovered in Skoda Superb III car with MIB3 infotainment unit OEM part number 3V0035820. The list of affected MIB3 OEM part numbers is provided in the referenced resources."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-28909",
      "fuzzing": []
    },
    {
      "name": "CVE-2023-28910",
      "published": "2025-06-28T16:15:23.253",
      "score": "High",
      "cvss": 8.0,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment",
        "skoda"
      ],
      "matched_terms": [
        "infotainment",
        "skoda"
      ],
      "surfaces": [
        "Bluetooth",
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "A specific flaw exists within the Bluetooth stack of the MIB3 infotainment system. The issue results from the disabled abortion flag eventually leading to bypassing assertion functions.\nThe vulnerability was originally discovered in Skoda Superb III car with MIB3 infotainment unit OEM part number 3V0035820. The list of affected MIB3 OEM part numbers is provided in the referenced resources."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-28910",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-8356",
      "published": "2024-11-22T22:15:18.980",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment",
        "visteon"
      ],
      "matched_terms": [
        "infotainment",
        "visteon"
      ],
      "surfaces": [
        "Infotainment",
        "OTA"
      ],
      "vulnerabilities": [
        {
          "text": "Visteon Infotainment VIP MCU Code Insufficient Validation of Data Authenticity Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Visteon Infotainment systems. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.\n\nThe specific flaw exists within the firmware update process of the VIP microcontroller. The process does not properly verify authenticity of the supplied firmware image before programming it into internal memory. An attacker can leverage this vulnerability to escalate privileges execute arbitrary code in the context of the VIP MCU. Was ZDI-CAN-23758."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-8356",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-8357",
      "published": "2024-11-22T22:15:19.107",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment",
        "visteon"
      ],
      "matched_terms": [
        "infotainment",
        "visteon"
      ],
      "surfaces": [
        "Identity",
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "Visteon Infotainment App SoC Missing Immutable Root of Trust in Hardware Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Visteon Infotainment systems. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.\n\nThe specific flaw exists within the configuration of the application system-on-chip (SoC). The issue results from the lack of properly configured hardware root of trust. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of the boot process. Was ZDI-CAN-23759."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-8357",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-13943",
      "published": "2025-04-30T20:15:20.520",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.0",
      "pending_analysis": false,
      "keyword": "tesla",
      "keywords": [
        "tesla"
      ],
      "matched_terms": [
        "tesla"
      ],
      "surfaces": [
        "General Automotive Surface"
      ],
      "vulnerabilities": [
        {
          "text": "Tesla Model S Iris Modem QCMAP_ConnectionManager Improper Input Validation Sandbox Escape Vulnerability. This vulnerability allows local attackers to escape the sandbox on affected affected Tesla Model S vehicles. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.\n\nThe specific flaw exists within the QCMAP_ConnectionManager component. An attacker can abuse the service to assign LAN addresses to the WWAN. An attacker can leverage this vulnerability to access network services that were only intended to be exposed to the internal LAN. Was ZDI-CAN-23199."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-13943",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-6031",
      "published": "2025-04-30T20:15:21.153",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.0",
      "pending_analysis": false,
      "keyword": "tesla",
      "keywords": [
        "tesla"
      ],
      "matched_terms": [
        "tesla"
      ],
      "surfaces": [
        "General Automotive Surface"
      ],
      "vulnerabilities": [
        {
          "text": "Tesla Model S oFono AT Command Heap-based Buffer Overflow Code Execution Vulnerability. This vulnerability allows local attackers to execute arbitrary code on affected Tesla Model S vehicles. An attacker must first obtain the ability to execute code on the target modem in order to exploit this vulnerability.\n \nThe specific flaw exists within the parsing of responses from AT commands. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-23198."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-6031",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-6032",
      "published": "2025-04-30T20:15:21.283",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.0",
      "pending_analysis": false,
      "keyword": "tesla",
      "keywords": [
        "tesla"
      ],
      "matched_terms": [
        "tesla"
      ],
      "surfaces": [
        "General Automotive Surface"
      ],
      "vulnerabilities": [
        {
          "text": "Tesla Model S Iris Modem ql_atfwd Command Injection Code Execution Vulnerability. This vulnerability allows local attackers to execute arbitrary code on affected Tesla Model S vehicles. An attacker must first obtain the ability to execute code on the target system in order to exploit this vulnerability.\n \nThe specific flaw exists within the ql_atfwd process. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code on the target modem in the context of root. Was ZDI-CAN-23201."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-6032",
      "fuzzing": []
    },
    {
      "name": "CVE-2023-28906",
      "published": "2025-06-28T16:15:22.573",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment",
        "skoda"
      ],
      "matched_terms": [
        "infotainment",
        "skoda"
      ],
      "surfaces": [
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "A command injection in the networking service of the MIB3 infotainment allows an attacker already presenting in the system to escalate privileges and obtain administrative access to the system.\nThe vulnerability was originally discovered in Skoda Superb III car with MIB3 infotainment unit OEM part number 3V0035820. The list of affected MIB3 OEM part numbers is provided in the referenced resources."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-28906",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-31474",
      "published": "2026-04-22T14:16:44.053",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "isotp",
      "keywords": [
        "isotp"
      ],
      "matched_terms": [
        "can frame",
        "isotp"
      ],
      "surfaces": [
        "CAN Bus",
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: isotp: fix tx.buf use-after-free in isotp_sendmsg()\n\nisotp_sendmsg() uses only cmpxchg() on so->tx.state to serialize access\nto so->tx.buf. isotp_release() waits for ISOTP_IDLE via\nwait_event_interruptible() and then calls kfree(so->tx.buf).\n\nIf a signal interrupts the wait_event_interruptible() inside close()\nwhile tx.state is ISOTP_SENDING, the loop exits early and release\nproceeds to force ISOTP_SHUTDOWN and continues to kfree(so->tx.buf)\nwhile sendmsg may still be reading so->tx.buf for the final CAN frame\nin isotp_fill_dataframe().\n\nThe so->tx.buf can be allocated once when the standard tx.buf length needs\nto be extended. Move the kfree() of this potentially extended tx.buf to\nsk_destruct time when either isotp_sendmsg() and isotp_release() are done."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-31474",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-68387",
      "published": "2026-08-10T13:20:31.950",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "isotp",
      "keywords": [
        "isotp"
      ],
      "matched_terms": [
        "isotp"
      ],
      "surfaces": [
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: raw: add locking for raw flags bitfield\n\nWith commit 890e5198a6e5 (\"can: raw: use bitfields to store flags in\nstruct raw_sock\") the formerly separate integer values have been integrated\ninto a single bitfield. This led to a read-modify-write operation when\nchanging a flag in raw_setsockopt() which now needs a locking to prevent\nconcurrent access.\n\nInstead of adding a lock/unlock hell in each of the flag manipulations this\npatch introduces a wrapper for a new raw_setsockopt_locked() function\nanalogue to the isotp_setsockopt[_locked]() approach in net/can/isotp.c\n\n[mkl: use Closes tag instead of Link]"
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68387",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-72113",
      "published": "2026-08-15T06:21:25.680",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "isotp",
      "keywords": [
        "isotp"
      ],
      "matched_terms": [
        "isotp"
      ],
      "surfaces": [
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: add missing device refcount for CAN filter removal\n\nsashiko-bot remarked a problem with a concurrent device unregistration\nin isotp.c which also is present in the bcm.c code. A former fix for raw.c\ncommit c275a176e4b6 (\"can: raw: add missing refcount for memory leak fix\")\nintroduced a netdevice_tracker which solves the issue for bcm.c too.\n\nbcm_release(), bcm_delete_rx_op() and bcm_notifier() relied on\ndev_get_by_index(ifindex) to re-find the device for an rx_op before\nunregistering its filter. If a concurrent NETDEV_UNREGISTER has already\nunlisted the device from the ifindex table, that lookup fails and\ncan_rx_unregister() is silently skipped, leaving a stale CAN filter\npointing at the soon-to-be-freed bcm_op/socket.\n\nHold a netdev_hold()/netdev_put() tracked reference on op->rx_reg_dev\nfrom the moment the rx filter is registered in bcm_rx_setup() until it\nis unregistered in bcm_rx_unreg(), and use that reference directly in\nbcm_release() and bcm_delete_rx_op() instead of re-looking the device\nup by ifindex."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72113",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-72125",
      "published": "2026-08-15T06:21:29.840",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "isotp",
      "keywords": [
        "isotp"
      ],
      "matched_terms": [
        "isotp"
      ],
      "surfaces": [
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER\n\nisotp_release() looked up the bound network device via dev_get_by_index()\nusing the stored ifindex. During device unregistration the device is\nunlisted from the ifindex hash before the NETDEV_UNREGISTER notifier\nchain runs, so a concurrent isotp_release() could find no device, skip\ncan_rx_unregister() entirely, and still proceed to free the socket.\nSince isotp_release() had already removed itself from the isotp\nnotifier list at that point, isotp_notify() would never get a chance to\nclean up either, leaving a stale CAN filter that keeps pointing at the\nfreed socket.\n\nFix this the same way raw.c already does: hold a tracked reference to\nthe bound net_device in the socket (so->dev/so->dev_tracker) from\nbind() onward instead of re-resolving it from the ifindex, and\nserialize bind()/release() with rtnl_lock() so that so->dev is always\nconsistent with what the NETDEV_UNREGISTER notifier sees. so->dev\nstays valid regardless of ifindex-hash unlisting, and is only ever\ncleared by whichever of isotp_release()/isotp_notify() gets there\nfirst, so the filter is always removed exactly once.\n\nisotp_bind() now rejects a (re)bind with -EAGAIN while so->[tx|rx].state\nisn't ISOTP_IDLE yet, so a timer left running by a prior\nNETDEV_UNREGISTER can't act on a newly bound so->ifindex. Both checks\nshare the same lock_sock() section, so there is no window in which a\nconcurrent isotp_notify() clearing so->bound could be missed."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72125",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-72126",
      "published": "2026-08-15T06:21:29.963",
      "score": "High",
      "cvss": 7.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "isotp",
      "keywords": [
        "isotp"
      ],
      "matched_terms": [
        "isotp"
      ],
      "surfaces": [
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: isotp: use unconditional synchronize_rcu() in isotp_release()\n\nisotp_notify() unregisters the (RCU) CAN filters via can_rx_unregister()\nand clears so->bound without waiting for a grace period. isotp_release()\nuses so->bound to decide whether it needs to call synchronize_rcu()\nbefore cancelling so->rxtimer, so when NETDEV_UNREGISTER runs first it\nskips that synchronize_rcu() and can cancel the timer while an\nin-flight isotp_rcv() is still executing and about to re-arm it via\nisotp_send_fc(), leading to a use-after-free timer callback on the\nfreed socket.\n\nsakisho-bot remarked a problem with rtnl_lock held in isotp_notify(),\ntherefore make isotp_release() always call synchronize_rcu() before\ncancelling the timers, regardless of so->bound. This still closes the\noriginal race (isotp_notify() clearing so->bound without waiting for\nin-flight isotp_rcv() callers before isotp_release() cancels the RX\ntimer) without adding any RCU wait to the netdevice notifier path."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72126",
      "fuzzing": []
    },
    {
      "name": "CVE-2023-34400",
      "published": "2025-02-13T22:15:10.847",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "mercedes-benz",
      "keywords": [
        "mercedes-benz"
      ],
      "matched_terms": [
        "mercedes-benz"
      ],
      "surfaces": [
        "General Automotive Surface"
      ],
      "vulnerabilities": [
        {
          "text": "Mercedes-Benz head-unit NTG6 contains functions to import or export profile settings over USB. In case of parsing file, service try to define header inside the file and convert it to null-terminated string. If character is missed, will return null pointer."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-34400",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-2082",
      "published": "2025-04-30T20:15:21.563",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.0",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus",
        "tesla"
      ],
      "matched_terms": [
        "can bus",
        "tesla",
        "tpms",
        "vcsec"
      ],
      "surfaces": [
        "CAN Bus",
        "Identity",
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Tesla Model 3 VCSEC Integer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected Tesla Model 3 vehicles. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the VCSEC module. By manipulating the certificate response sent from the Tire Pressure Monitoring System (TPMS), an attacker can trigger an integer overflow before writing to memory. An attacker can leverage this vulnerability to execute code in the context of the VCSEC module and send arbitrary messages to the vehicle CAN bus. Was ZDI-CAN-23800."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-2082",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-45584",
      "published": "2025-09-12T21:15:33.773",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "audi",
      "keywords": [
        "audi"
      ],
      "matched_terms": [
        "audi"
      ],
      "surfaces": [
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Incorrect access control in the web service of Audi UTR 2.0 Universal Traffic Recorder 2.0 allows attackers to download car information without authentication."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-45584",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-20791",
      "published": "2026-02-27T00:16:56.010",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Charging station authentication identifiers are publicly accessible via web-based mapping platforms."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-20791",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-20895",
      "published": "2026-02-27T00:16:56.350",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely \nassociate sessions but allows multiple endpoints to connect using the \nsame session identifier. This implementation results in predictable \nsession identifiers and enables session hijacking or shadowing, where \nthe most recent connection displaces the legitimate charging station and\n receives backend commands intended for that station. This vulnerability\n may allow unauthorized users to authenticate as other users or enable a\n malicious actor to cause a denial-of-service condition by overwhelming \nthe backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-20895",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-25711",
      "published": "2026-02-27T00:16:57.200",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely \nassociate sessions but allows multiple endpoints to connect using the \nsame session identifier. This implementation results in predictable \nsession identifiers and enables session hijacking or shadowing, where \nthe most recent connection displaces the legitimate charging station and\n receives backend commands intended for that station. This vulnerability\n may allow unauthorized users to authenticate as other users or enable a\n malicious actor to cause a denial-of-service condition by overwhelming \nthe backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25711",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-25778",
      "published": "2026-02-27T00:16:57.383",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely \nassociate sessions but allows multiple endpoints to connect using the \nsame session identifier. This implementation results in predictable \nsession identifiers and enables session hijacking or shadowing, where \nthe most recent connection displaces the legitimate charging station and\n receives backend commands intended for that station. This vulnerability\n may allow unauthorized users to authenticate as other users or enable a\n malicious actor to cause a denial-of-service condition by overwhelming \nthe backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25778",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-27652",
      "published": "2026-02-27T00:16:57.900",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely \nassociate sessions but allows multiple endpoints to connect using the \nsame session identifier. This implementation results in predictable \nsession identifiers and enables session hijacking or shadowing, where \nthe most recent connection displaces the legitimate charging station and\n receives backend commands intended for that station. This vulnerability\n may allow unauthorized users to authenticate as other users or enable a\n malicious actor to cause a denial-of-service condition by overwhelming \nthe backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27652",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-27828",
      "published": "2026-03-26T17:16:34.357",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "evse",
      "keywords": [
        "evse"
      ],
      "matched_terms": [
        "evse",
        "iso15118",
        "v2g"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "EVerest is an EV charging software stack. Prior to version 2026.02.0, ISO15118_chargerImpl::handle_session_setup uses v2g_ctx after it has been freed when ISO15118 initialization fails (e.g., no IPv6 link-local address). The EVSE process can be crashed remotely by an attacker with MQTT access who issues a session_setup command while v2g_ctx has been released. Version 2026.02.0 contains a patch."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27828",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-4156",
      "published": "2026-04-11T01:16:17.360",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.0",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "ChargePoint Home Flex OCPP getpreq Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of ChargePoint Home Flex EV chargers. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the handling of OCPP messages. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-26339."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-4156",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-4157",
      "published": "2026-04-11T01:16:17.487",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.0",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "ocpp"
      ],
      "matched_terms": [
        "ocpp"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "ChargePoint Home Flex revssh Service Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of ChargePoint Home Flex devices. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the handling of OCPP messages. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-26338."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-4157",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-37530",
      "published": "2026-05-01T17:16:22.603",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "uds",
      "keywords": [
        "automotive ecu",
        "uds"
      ],
      "matched_terms": [
        "diagnostic",
        "ecus",
        "uds"
      ],
      "surfaces": [
        "ECU",
        "UDS Diagnostics"
      ],
      "vulnerabilities": [
        {
          "text": "AGL agl-service-can-low-level thru 17.1.12 contains a stack buffer overflow in the uds-c library. The send_diagnostic_request function in uds.c allocates a 6-byte stack buffer (MAX_DIAGNOSTIC_PAYLOAD_SIZE=6) but copies up to 7 bytes (MAX_UDS_REQUEST_PAYLOAD_LENGTH=7) via memcpy at an offset of 1+pid_length (2-3 bytes), resulting in 1-4 bytes of controlled stack overflow. The payload_length field (uint8_t) has no bounds check against the destination buffer. On 32-bit ARM automotive ECUs without stack canaries, this can lead to return address overwrite and RCE."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-37530",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-42467",
      "published": "2026-05-01T17:16:25.027",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "j1939",
      "keywords": [
        "j1939"
      ],
      "matched_terms": [
        "can frame",
        "j1939"
      ],
      "surfaces": [
        "CAN Bus",
        "J1939"
      ],
      "vulnerabilities": [
        {
          "text": "An issue was discovered in Open-SAE-J1939 thru commit b6caf884df46435e539b1ecbf92b6c29b345bdfe (2025-11-30) in SAE_J1939_Read_Binary_Data_Transfer_DM16 causing a denial of service via crafted CAN frame on the J1939 bus."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42467",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-42485",
      "published": "2026-05-01T17:16:25.377",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "uds",
      "keywords": [
        "automotive ecu",
        "uds"
      ],
      "matched_terms": [
        "diagnostic",
        "ecus",
        "uds"
      ],
      "surfaces": [
        "ECU",
        "UDS Diagnostics"
      ],
      "vulnerabilities": [
        {
          "text": "AGL agl-service-can-low-level contains a stack buffer overflow in the uds-c library. The send_diagnostic_request function in uds.c allocates a 6-byte stack buffer (MAX_DIAGNOSTIC_PAYLOAD_SIZE=6) but copies up to 7 bytes (MAX_UDS_REQUEST_PAYLOAD_LENGTH=7) via memcpy at an offset of 1+pid_length (2-3 bytes), resulting in 1-4 bytes of controlled stack overflow. The payload_length field (uint8_t) has no bounds check against the destination buffer. On 32-bit ARM automotive ECUs without stack canaries, this can lead to return address overwrite and RCE."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42485",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-42952",
      "published": "2026-07-10T23:16:48.203",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Previously, there was no throttling on repeated authentication attempts \nto the charging station backend, which could allow an attacker to \nexecute a denial-of-service attack."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42952",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-44383",
      "published": "2026-07-10T23:16:48.343",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "ocpp",
      "keywords": [
        "charging station",
        "ocpp"
      ],
      "matched_terms": [
        "charging station",
        "ocpp"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "Multiple connections to the backend using the same charging station ID \nare allowed, which could allow an attacker to deploy multiple instances \nof malicious OCPP clients to overwhelm the backend."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44383",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-73523",
      "published": "2026-08-17T18:18:14.170",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus"
      ],
      "matched_terms": [
        "can bus",
        "can frames"
      ],
      "surfaces": [
        "CAN Bus"
      ],
      "vulnerabilities": [
        {
          "text": "COVESA Open1722 through 0.9.2 contains an integer truncation vulnerability in acf-can-listener.c that allows unauthenticated remote attackers to cause the CAN listener to transmit process stack memory onto the CAN bus by sending a rejected UDP datagram with a matching AVTP stream ID. The num_can_msgs variable declared as uint8_t truncates the -1 error return value from avtp_to_can() to 255, causing a write loop to iterate 255 times over a 15-slot stack array and leak approximately 18 KB of adjacent stack memory as roughly 240 CAN frames to any recipient on the CAN bus."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-73523",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-67560",
      "published": "2026-08-28T00:18:08.150",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus"
      ],
      "matched_terms": [
        "can bus",
        "ecu"
      ],
      "surfaces": [
        "CAN Bus",
        "ECU"
      ],
      "vulnerabilities": [
        {
          "text": "Bendix EC80 Brake ECU\n is vulnerable to a stack-based buffer overflow, which may allow an \nattacker to crash the ECU. A crafted payload can then be used to \nremotely execute arbitrary code or inject arbitrary CAN bus traffic. \nThis could cause the loss of the ABS function, steering assist, \nspeedometer, and shifting."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-67560",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-80707",
      "published": "2026-08-28T08:16:56.277",
      "score": "High",
      "cvss": 7.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "j1939",
      "keywords": [
        "j1939"
      ],
      "matched_terms": [
        "j1939"
      ],
      "surfaces": [
        "J1939"
      ],
      "vulnerabilities": [
        {
          "text": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: j1939: transport: j1939_session_fresh_new(): initialize receive buffer\n\nZero the allocated buffer in j1939_session_fresh_new() to ensure it\ncontains no residual data.\n\nWhile there is a potential performance impact if users allocate maximum\nsized ETP buffers, most real-world use cases are not noticeably affected\nsince the maximum known buffer size is typically around 65K.\n\n[mkl: add Message-ID]"
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80707",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-68133",
      "published": "2026-01-21T03:15:45.513",
      "score": "High",
      "cvss": 7.4,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "evse",
      "keywords": [
        "evse"
      ],
      "matched_terms": [
        "evse",
        "iso 15118"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "EVerest is an EV charging software stack. In versions 2025.9.0 and below, an attacker can exhaust the operating system's memory and cause the module to terminate by initiating an unlimited number of TCP connections that never proceed to ISO 15118-2 communication. This is possible because a new thread is started for each incoming plain TCP or TLS socket connection before any verification occurs, and the verification performed is too permissive. The EVerest processes and all its modules shut down, affecting all EVSE functionality. This issue is fixed in version 2025.10.0."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68133",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-68134",
      "published": "2026-01-21T19:16:04.510",
      "score": "High",
      "cvss": 7.4,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "evse",
      "keywords": [
        "evse"
      ],
      "matched_terms": [
        "evse"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "EVerest is an EV charging software stack. Prior to version 2025.10.0, the use of the `assert` function to handle errors frequently causes the module to crash. This is particularly critical because the manager shuts down all other modules and exits when any one of them terminates, leading to a denial of service. In a context where a manager handles multiple EVSE, this would also impact other users. Version 2025.10.0 fixes the issue."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68134",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-68141",
      "published": "2026-01-21T20:16:06.523",
      "score": "High",
      "cvss": 7.4,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "evse",
      "keywords": [
        "evse"
      ],
      "matched_terms": [
        "evse"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "EVerest is an EV charging software stack. Prior to version 2025.10.0, during the deserialization of a `DC_ChargeLoopRes` message that includes Receipt as well as TaxCosts, the vector `<DetailedTax>tax_costs` in the target `Receipt` structure is accessed out of bounds. This occurs in the method `template <> void convert(const struct iso20_dc_DetailedTaxType& in, datatypes::DetailedTax& out)` which leads to a null pointer dereference and causes the module to terminate. The EVerest processes and all its modules shut down, affecting all EVSE. Version 2025.10.0 fixes the issue."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68141",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-23929",
      "published": "2025-01-31T01:15:09.697",
      "score": "High",
      "cvss": 7.3,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "telematics",
      "keywords": [
        "telematics"
      ],
      "matched_terms": [
        "pioneer",
        "telematics"
      ],
      "surfaces": [
        "Identity",
        "Telematics"
      ],
      "vulnerabilities": [
        {
          "text": "This vulnerability allows network-adjacent attackers to create arbitrary files on affected installations of Pioneer DMH-WT7600NEX devices. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.\n\nThe specific flaw exists within the telematics functionality. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-23929",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-36842",
      "published": "2025-04-15T16:15:23.187",
      "score": "High",
      "cvss": 7.3,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment"
      ],
      "matched_terms": [
        "infotainment"
      ],
      "surfaces": [
        "Infotainment"
      ],
      "vulnerabilities": [
        {
          "text": "An issue in Oncord+ Android Infotainment Systems OS Android 12, Model Hardware TS17,Hardware part Number F57L_V3.2_20220301, and Build Number PlatformVER:K24-2023/05/09-v0.01 allows a remote attacker to execute arbitrary code via the ADB port component."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36842",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-70994",
      "published": "2026-04-23T15:36:26.687",
      "score": "High",
      "cvss": 7.3,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "keyless entry",
      "keywords": [
        "key fob",
        "keyless entry",
        "rolling code"
      ],
      "matched_terms": [
        "key fob",
        "keyless"
      ],
      "surfaces": [
        "Identity",
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Yadea T5 Electric Bicycles (models manufactured in/after 2024) have a weak authentication mechanism in their keyless entry system. The system utilizes the EV1527 fixed-code RF protocol without implementing rolling codes or cryptographic challenge-response mechanisms. This is vulnerable to signal forgery after a local attacker intercepts any legitimate key fob transmission, allowing for complete unauthorized vehicle operation via a replay attack."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-70994",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-56790",
      "published": "2026-06-25T19:16:45.637",
      "score": "High",
      "cvss": 7.3,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus"
      ],
      "matched_terms": [
        "can bus"
      ],
      "surfaces": [
        "CAN Bus"
      ],
      "vulnerabilities": [
        {
          "text": "CANBoat through 6.22, fixed in commit a5a22b7, contains an off-by-one global buffer overflow in the searchForPgn() function in analyzer/pgn.c that allows remote attackers to crash the application. Attackers can deliver a crafted NMEA-2000 message with an out-of-range PGN value over CAN bus or N2K-over-IP to trigger an out-of-bounds array access and denial of service."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56790",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-54479",
      "published": "2026-06-25T22:17:02.063",
      "score": "High",
      "cvss": 7.3,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54479",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-97212",
      "published": "2026-10-02T22:16:56.760",
      "score": "High",
      "cvss": 7.3,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "Backend",
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97212",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43658",
      "published": "2025-01-09T08:15:28.867",
      "score": "High",
      "cvss": 7.2,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "Patch traversal, External Control of File Name or Path vulnerability in  Iocharger Home allows deletion of arbitrary files\nThis issue affects Iocharger firmware for AC model before firmware version 25010801.\n\nLikelihood: High, but requires authentication\n\nImpact: Critical – The vulnerability can be used to delete any file on the charging station, severely impacting the integrity of the charging station. Furthermore, the vulnerability could be used to delete binaries required for the functioning of the charging station, severely impacting the availability of the charging station.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, but the level of authentication does not matter (PR:L), nor is any user interaction required (UI:N). The attack leads compromised of the integrity and availability of the device (VVC:N/VI:H/VA:H), with no effect on subsequent systems (SC:N/SI:N/SA:N). We do not forsee a safety impact (S:N). This attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43658",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-43659",
      "published": "2025-01-09T08:15:29.060",
      "score": "High",
      "cvss": 7.2,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "charging station",
      "keywords": [
        "charging station"
      ],
      "matched_terms": [
        "charging station"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "After gaining access to the firmware of a charging station, a file at <redacted> can be accessed to obtain default credentials that are the same across all Iocharger AC model EV chargers.\n\nThis issue affects Iocharger firmware for AC models before firmware version 25010801. \n\nThe issue is addressed by requiring a mandatory password change on first login, it is still recommended to change the password on older models.\n\nLikelihood: Moderate – The attacker will first have to abuse a code execution or file inclusion vulnerability (for example by using <redacted>.sh) to gain access to the <redacted>.json file, or obtain a firmware dump of the charging station or obtain the firmware via other channels.\n\nImpact: Critical – All chargers using Iocharger firmware for AC models started with the same initial password. For models with firmware version before 25010801 a password change was not mandatory. It is therefore very likely that this firmware password is still active on many chargers. These credentials could, once obtained, allow an attacker to log into many Iocharger charging station, and allow them to execute arbitrary commands via the System → Custom page.\n\nCVSS clarification: Any network interface serving the web ui is vulnerable (AV:N) and there are not additional security measures to circumvent (AC:L), nor does the attack require and existing preconditions (AT:N). The attack is authenticated, and requires high privileges (PR:H), there is no user interaction required (UI:N). The attack leads to a compromised of the confidentialy of the \"super user\" credentials of the device (VC:H/VI:N/VA:N), and can subsequently be used to full compromise and other devices (SC:H/SI:H/SA:H). Becuase this is an EV charger handing significant power, there is a potential safety impact (S:P). This attack can be automated (AU:Y)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43659",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-37532",
      "published": "2026-05-01T17:16:22.897",
      "score": "High",
      "cvss": 7.1,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "isotp",
      "keywords": [
        "isotp"
      ],
      "matched_terms": [
        "can frame",
        "isotp"
      ],
      "surfaces": [
        "CAN Bus",
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "AGL agl-service-can-low-level thru 17.1.12 contains a heap buffer over-read in the isotp-c library. In isotp_continue_receive (receive.c:87-89), the payload_length for a Single Frame is extracted from a 4-bit nibble in the CAN frame data, yielding values 0-15. However, a standard CAN frame is only 8 bytes, with payload starting at data[1] (7 bytes available). When payload_length exceeds the available data (e.g., nibble=15 but only 7 payload bytes exist), memcpy(message.payload, &data[1], payload_length) reads up to 8 bytes past the end of the data buffer."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-37532",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-37535",
      "published": "2026-05-01T17:16:23.210",
      "score": "High",
      "cvss": 7.1,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "iso-tp",
      "keywords": [
        "iso-tp"
      ],
      "matched_terms": [
        "can frame",
        "iso-tp",
        "isotp"
      ],
      "surfaces": [
        "CAN Bus",
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "openxc/isotp-c thru commit 5a5d19245f65189202719321facd49ce6f5d46ac (2021-08-09) contains an out-of-bounds read in the ISO-TP Single Frame receive handler, where the 4-bit payload length nibble is used directly as the memcpy size without validating it against the actual CAN data length. A malicious CAN frame with an oversized length nibble can cause memory reads beyond the buffer, allowing attackers to cause a denial of service, or gain sensitive information."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-37535",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-6030",
      "published": "2025-04-30T20:15:21.030",
      "score": "High",
      "cvss": 7.0,
      "cvss_version": "3.0",
      "pending_analysis": false,
      "keyword": "tesla",
      "keywords": [
        "tesla"
      ],
      "matched_terms": [
        "tesla"
      ],
      "surfaces": [
        "General Automotive Surface"
      ],
      "vulnerabilities": [
        {
          "text": "Tesla Model S oFono Unnecessary Privileges Sandbox Escape Vulnerability. This vulnerability allows local attackers to escape the sandbox on affected Tesla Model S vehicles. An attacker must first obtain the ability to execute code within the sandbox on the target system in order to exploit this vulnerability.\n \nThe specific flaw exists within the oFono process. The process allows an attacker to modify interfaces. An attacker can leverage this vulnerability to bypass the iptables network sandbox. Was ZDI-CAN-23200."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-6030",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-26074",
      "published": "2026-03-26T17:16:33.407",
      "score": "High",
      "cvss": 7.0,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "evse",
      "keywords": [
        "evse"
      ],
      "matched_terms": [
        "evse"
      ],
      "surfaces": [
        "EV Charging"
      ],
      "vulnerabilities": [
        {
          "text": "EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::map<std::queue>` corruption. The trigger is CSMS GetLog/UpdateFirmware request (network) with an EVSE fault event (physical). This results in TSAN reports concurrent access (data race) to `event_queue`. Version 2026.2.0 contains a patch."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26074",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-56448",
      "published": "2025-09-15T20:15:38.127",
      "score": "Medium",
      "cvss": 6.8,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "rolling code",
      "keywords": [
        "rolling code"
      ],
      "matched_terms": [
        "rolling code"
      ],
      "surfaces": [
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "The Positron PX360BT SW REV 8 car alarm system is vulnerable to a replay attack due to a failure in implementing rolling code security. The alarm system does not properly rotate or invalidate used codes, allowing repeated reuse of captured transmissions. This exposes users to significant security risks, including vehicle theft and loss of trust in the alarm's anti-cloning claims."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-56448",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-51073",
      "published": "2024-11-22T16:15:33.730",
      "score": "Medium",
      "cvss": 6.7,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus",
        "kia",
        "uds"
      ],
      "matched_terms": [
        "can bus",
        "diagnostic",
        "ecu",
        "kia",
        "uds",
        "unified diagnostic services"
      ],
      "surfaces": [
        "CAN Bus",
        "ECU",
        "UDS Diagnostics"
      ],
      "vulnerabilities": [
        {
          "text": "An issue in KIA Seltos vehicle instrument cluster with software and hardware v1.0 allows attackers to control or disrupt CAN communication between the instrument cluster and CAN bus. NOTE: this is disputed by the Supplier because the findings came from a potentially unrealistic test environment (an isolated ECU part that was not in a vehicle), and because the observed behavior follows the UDS (Unified Diagnostic Services) specification."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-51073",
      "fuzzing": []
    },
    {
      "name": "CVE-2024-51074",
      "published": "2024-11-22T16:15:33.860",
      "score": "Medium",
      "cvss": 6.7,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus",
        "kia",
        "uds"
      ],
      "matched_terms": [
        "can bus",
        "diagnostic",
        "ecu",
        "kia",
        "uds",
        "unified diagnostic services"
      ],
      "surfaces": [
        "CAN Bus",
        "ECU",
        "UDS Diagnostics"
      ],
      "vulnerabilities": [
        {
          "text": "Incorrect access control in KIA Seltos vehicle instrument cluster with software and hardware v1.0 allows attackers to arbitrarily change odometer readings in the vehicle by targeting the instrument cluster through the unsecured CAN network. NOTE: this is disputed by the supplier because the CAN bus is not externally exposed, and because the packets can only increase the odometer reading (which typically has no value to an adversary). Also, this is disputed by the Supplier because the findings came from a potentially unrealistic test environment (an isolated ECU part that was not in a vehicle), and because the observed behavior follows the UDS (Unified Diagnostic Services) specification."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-51074",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-49319",
      "published": "2026-06-25T15:16:37.980",
      "score": "Medium",
      "cvss": 6.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "keyless entry",
      "keywords": [
        "key fob",
        "keyless entry",
        "suzuki"
      ],
      "matched_terms": [
        "alpine",
        "key fob",
        "keyless",
        "rolling-code",
        "suzuki"
      ],
      "surfaces": [
        "Identity",
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Remote Keyless Entry System (RKES), using the 433 MHz key fob bearing FCC ID CWTR53R0 manufactured by ALPS ALPINE CO., LTD., is vulnerable to a roll-back attack against its rolling-code authentication. \n\n\n\nAn attacker within RF range who records two consecutive lock or unlock transmissions from a legitimate key fob can later replay the same pair of transmissions repeatedly. During testing, replaying the first captured transmission caused the RKES to enter a state in which replaying the second captured transmission resulted in a successful lock or unlock operation of the vehicle. Tested and confirmed on a 2024 Suzuki Swift (SWIFT ISG GLS AC 1.2 5P 4x2 TM)."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-49319",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-82357",
      "published": "2026-10-01T20:17:32.363",
      "score": "Medium",
      "cvss": 6.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus"
      ],
      "matched_terms": [
        "can bus"
      ],
      "surfaces": [
        "CAN Bus"
      ],
      "vulnerabilities": [
        {
          "text": "RT-Labs AB C-Open CANopen contains a NULL pointer dereference if the LSS protocol is used to configure the device. An object defined by the user application may not have all required subindexes for object 0x1018. An unauthenticated, remote attacker with access to the CAN bus, through a compromised node for instance, can initiate the LSS protocol on a device with a misconfigured identity object and potentially crash the device. Fixed in 1.1.1."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-82357",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-82358",
      "published": "2026-10-01T20:17:32.540",
      "score": "Medium",
      "cvss": 6.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus"
      ],
      "matched_terms": [
        "can bus"
      ],
      "surfaces": [
        "CAN Bus",
        "Identity"
      ],
      "vulnerabilities": [
        {
          "text": "RT-Labs AB C-Open CANopen contains a write protection bypass in the SDO (Service Data Object) server implementation 'src/co_sdo_server.c' that fails to properly validate write permissions when processing download-segment frames. An unauthenticated attacker on the CAN bus can initiate an SDO upload for a read-only Object Dictionary (OD) entry, which sets a data pointer to the read-only object, then send download-segment frames to write to that memory location. The download-segment handler does not verify that a download session is active, allowing any CANopen node to overwrite read-only OD entries using two SDO frames. Note that CANopen protocol operates over CAN bus and does not provide built-in authentication mechanisms. Fixed in 1.1.1."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-82358",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-2541",
      "published": "2026-02-15T11:15:55.223",
      "score": "Medium",
      "cvss": 6.4,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "rolling code",
      "keywords": [
        "rolling code"
      ],
      "matched_terms": [
        "rolling code"
      ],
      "surfaces": [
        "Identity",
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "The Micca KE700 system relies on a 6-bit portion of an identifier for authentication within rolling codes, providing only 64 possible combinations. This low entropy allows an attacker to perform a brute-force attack against one component of the rolling code. Successful exploitation simplify an attacker to predict the next valid rolling code, granting unauthorized access to the vehicle."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2541",
      "fuzzing": []
    },
    {
      "name": "CVE-2023-53523",
      "published": "2025-10-01T12:15:56.747",
      "score": "Medium",
      "cvss": 5.5,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus"
      ],
      "matched_terms": [
        "can bus",
        "can frames"
      ],
      "surfaces": [
        "CAN Bus"
      ],
      "vulnerabilities": [
        {
          "text": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: gs_usb: fix time stamp counter initialization\n\nIf the gs_usb device driver is unloaded (or unbound) before the\ninterface is shut down, the USB stack first calls the struct\nusb_driver::disconnect and then the struct net_device_ops::ndo_stop\ncallback.\n\nIn gs_usb_disconnect() all pending bulk URBs are killed, i.e. no more\nRX'ed CAN frames are send from the USB device to the host. Later in\ngs_can_close() a reset control message is send to each CAN channel to\nremove the controller from the CAN bus. In this race window the USB\ndevice can still receive CAN frames from the bus and internally queue\nthem to be send to the host.\n\nAt least in the current version of the candlelight firmware, the queue\nof received CAN frames is not emptied during the reset command. After\nloading (or binding) the gs_usb driver, new URBs are submitted during\nthe struct net_device_ops::ndo_open callback and the candlelight\nfirmware starts sending its already queued CAN frames to the host.\n\nHowever, this scenario was not considered when implementing the\nhardware timestamp function. The cycle counter/time counter\ninfrastructure is set up (gs_usb_timestamp_init()) after the USBs are\nsubmitted, resulting in a NULL pointer dereference if\ntimecounter_cyc2time() (via the call chain:\ngs_usb_receive_bulk_callback() -> gs_usb_set_timestamp() ->\ngs_usb_skb_set_timestamp()) is called too early.\n\nMove the gs_usb_timestamp_init() function before the URBs are\nsubmitted to fix this problem.\n\nFor a comprehensive solution, we need to consider gs_usb devices with\nmore than 1 channel. The cycle counter/time counter infrastructure is\nsetup per channel, but the RX URBs are per device. Once gs_can_open()\nof _a_ channel has been called, and URBs have been submitted, the\ngs_usb_receive_bulk_callback() can be called for _all_ available\nchannels, even for channels that are not running, yet. As cycle\ncounter/time counter has not set up, this will again lead to a NULL\npointer dereference.\n\nConvert the cycle counter/time counter from a \"per channel\" to a \"per\ndevice\" functionality. Also set it up, before submitting any URBs to\nthe device.\n\nFurther in gs_usb_receive_bulk_callback(), don't process any URBs for\nnot started CAN channels, only resubmit the URB."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53523",
      "fuzzing": []
    },
    {
      "name": "CVE-2025-6785",
      "published": "2025-09-04T15:15:48.720",
      "score": "Medium",
      "cvss": 4.7,
      "cvss_version": "4.0",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus"
      ],
      "matched_terms": [
        "can bus",
        "tesla"
      ],
      "surfaces": [
        "CAN Bus"
      ],
      "vulnerabilities": [
        {
          "text": "Securing externally available CAN wires can easily allow physical access to the CAN bus, allowing possible injection of specially formed CAN messages to control remote start functions of the vehicle.  Testing completed on Tesla Model 3 vehicles with software version v11.1 (2023.20.9 ee6de92ddac5). This issue affects Model 3: With software versions from 2023.Xx before 2023.44."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-6785",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-49324",
      "published": "2026-05-29T13:16:23.557",
      "score": "Medium",
      "cvss": 4.6,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "immobilizer",
      "keywords": [
        "immobilizer"
      ],
      "matched_terms": [
        "immobilizer",
        "in-vehicle",
        "indian motorcycle",
        "wcm"
      ],
      "surfaces": [
        "Identity",
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Uncontrolled resource consumption in the Wireless Control Module (WCM) of the Indian Motorcycle Scout Bobber + Tech 2025 model year allows an adjacent-network attacker with write access to the in-vehicle network to permanently immobilize the motorcycle. The WCM enforces a brute-force lockout on the immobilizer authentication algorithm, but the lockout counter is reachable by any unauthenticated message, has no session binding, and does not reset on power cycle. An attacker can deliberately trip the lockout with a small number of crafted frames, leaving the bike un-startable until dealer service. Specific thresholds have been withheld pending vendor remediation."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-49324",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-49316",
      "published": "2026-05-29T14:16:32.480",
      "score": "Medium",
      "cvss": 4.6,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "can bus",
      "keywords": [
        "can bus",
        "immobilizer"
      ],
      "matched_terms": [
        "can bus",
        "ecu",
        "ecus",
        "immobilizer",
        "in-vehicle",
        "indian motorcycle",
        "wcm"
      ],
      "surfaces": [
        "CAN Bus",
        "ECU",
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Expected behavior violation in the in-vehicle network of the Indian Motorcycle Scout Bobber + Tech 2025 model year allows an adjacent-network attacker to bypass the motorcycle's anti-theft shutdown by forcing the Wireless Control Module (WCM) into the CAN bus-off state. Using a well-known CAN error-frame injection technique against a periodic WCM transmission, the attacker drives the WCM CAN controller's transmit error counter past the bus-off threshold, after which the WCM stops transmitting all messages, including the shutdown command. Peer ECUs do not interpret WCM silence as a security event and continue normal operation, allowing the motorcycle to be operated despite the immobilizer never having been unlocked. Specific protocol details have been withheld pending vendor remediation."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-49316",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-49322",
      "published": "2026-05-29T08:16:19.060",
      "score": "Medium",
      "cvss": 4.3,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "infotainment",
      "keywords": [
        "infotainment"
      ],
      "matched_terms": [
        "in-vehicle",
        "indian motorcycle",
        "infotainment",
        "wcm"
      ],
      "surfaces": [
        "Identity",
        "Infotainment",
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Weak authentication in the Wireless Control Module (WCM) of the Indian Motorcycle Scout Bobber + Tech 2025 model year allows an adjacent-network attacker with read access to the in-vehicle network to recover the user-set unlock PIN by passively observing a single PIN authentication exchange. The Infotainment Digital Round display computes its response using a non-cryptographic operation rather than a cryptographic challenge-response, so the PIN is mathematically derivable from one captured exchange, defeating the motorcycle's primary user-authentication control. Specific protocol details have been withheld pending vendor remediation."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-49322",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-49323",
      "published": "2026-05-29T13:16:23.407",
      "score": "Medium",
      "cvss": 4.3,
      "cvss_version": "3.1",
      "pending_analysis": false,
      "keyword": "immobilizer",
      "keywords": [
        "immobilizer"
      ],
      "matched_terms": [
        "immobilizer",
        "in-vehicle",
        "indian motorcycle",
        "wcm"
      ],
      "surfaces": [
        "Identity",
        "Keyless / Hardware"
      ],
      "vulnerabilities": [
        {
          "text": "Weak authentication between the Wireless Control Module (WCM) and the Engine Control Module (ECM) of the Indian Motorcycle Scout Bobber + Tech 2025 model year allows an adjacent-network attacker with read access to the in-vehicle network to recover the per-vehicle ECM immobilizer secret by passively observing a single seed/key exchange. The WCM derives its response using a reversible, non-cryptographic operation rather than a cryptographic challenge-response, so the persistent immobilizer secret can be reconstructed from one captured exchange. With this secret the attacker can authenticate to the ECM independently of the WCM and start the engine, defeating the immobilizer. Specific protocol details have been withheld pending vendor remediation."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-49323",
      "fuzzing": []
    },
    {
      "name": "CVE-2026-80889",
      "published": "2026-09-04T18:17:56.910",
      "score": "Unknown",
      "cvss": null,
      "cvss_version": null,
      "pending_analysis": true,
      "keyword": "isotp",
      "keywords": [
        "isotp"
      ],
      "matched_terms": [
        "isotp"
      ],
      "surfaces": [
        "ISO-TP"
      ],
      "vulnerabilities": [
        {
          "text": "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: isotp: fix timer drain order, wakeup handling and tx_gen ordering\n\nThis patch is a follow-up to commit cf070fe33bfb (\"can: isotp: serialize\nTX state transitions under so->rx_lock\") which addresses following\nsashiko-bot findings:\n\n- isotp_sendmsg(): drain so->txfrtimer first so a stale callback can't\n  re-arm echotimer after the claim\n\n- isotp_release(): wake so->wait after forcing ISOTP_SHUTDOWN so a\n  sleeping sendmsg() claim isn't stranded\n\n- isotp_sendmsg(): have both wait_event_interruptible() calls in\n  isotp_sendmsg() also wake on ISOTP_SHUTDOWN and do not return claim to\n  IDLE to avoid corrupting a concurrent isotp_release() process.\n\n- isotp_sendmsg(): handle potential claim of a new transfer when\n  the wait_event_interruptible() call returns in CAN_ISOTP_WAIT_TX_DONE\n  mode. Don't touch timers and states of the new transfer if a new thread\n  incremented so->tx_gen before getting the lock at err_event_drop.\n\n- isotp_sendmsg(): handle a stuck can_send() and omit timer and state\n  changes if a new transfer was claimed. wait_tx_done() returns the error\n  recorded in so->tx_result[], tagged with the caller's own generation.\n\n- isotp_tx_timeout(): on a claimed timeout, record the ECOMM error for\n  the timed-out transfer's own generation in so->tx_result[]; sk->sk_err\n  is raised unconditionally, same as every other error path here.\n\n- isotp_tx_gen_done()/isotp_tx_timeout(): always read tx.state (acquire)\n  before tx_gen - the reverse order let a weakly ordered CPU pair a fresh\n  tx.state with a stale tx_gen/tx_result slot.\n\n- isotp_sendmsg(): wait_tx_done: drain sk_err via sock_error() once we\n  have read the result from so->tx_result[], so an already-reported error\n  doesn't stay latched for a later poll()/SO_ERROR.\n\nAlso align the remaining lock-free so->tx.state/rx.state/cfecho accesses\nand use skb->hash as unique loopback echo frame indicator."
        }
      ],
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80889",
      "fuzzing": []
    }
  ]
}