[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-OPENSUSE-SU-2026:20236-1":6},{"stargazers_count":4,"fetched_at":5},8,"2026-09-19T17:35:29.592Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":28,"duplicates":29,"related":30,"reserved_at":9,"published_at":38,"modified_at":39,"state":9,"summary":40,"references_raw":42,"kevs":102,"epss":9,"epss_history":103,"metrics":104,"affected":105},"OPENSUSE-SU-2026:20236-1","Security update for nodejs22\n\nThis update for nodejs22 fixes the following issues:\n\nUpdate to 22.22.0:\n\n- CVE-2025-55130: file system permissions bypass via crafted symlinks (bsc#1256569).\n- CVE-2025-55131: timeout-based race conditions allow for allocations that contain leftover data from previous operations and lead to exposure of in-process secrets (bsc#1256570).\n- CVE-2025-55132: a file's access and modification timestamps can be changed via `futimes()` even when the process has only read permissions (bsc#1256571).\n- CVE-2025-59465: malformed HTTP/2 HEADERS frame with invalid HPACK data can cause a crash due to an unhandled error (bsc#1256573).\n- CVE-2025-59466: uncatchable \"Maximum call stack size exceeded\" error when `async_hooks.createHook()` is enabled can lead to crash (bsc#1256574).\n- CVE-2026-21637: synchronous exceptions thrown during certain callbacks bypass the standard TLS error handling paths and can cause a denial of service (bsc#1256576).\n- CVE-2026-22036: undici: unbounded decompression chain in HTTP responses via Content-Encoding may lead to resource exhaustion (bsc#1256848).\n\nFor full changelog, please see https://nodejs.org/en/blog\n",null,[],[],[],[14,16,18,20,22,24,26],{"_key":15},"CVE-2025-55130",{"_key":17},"CVE-2025-55131",{"_key":19},"CVE-2025-55132",{"_key":21},"CVE-2025-59465",{"_key":23},"CVE-2025-59466",{"_key":25},"CVE-2026-21637",{"_key":27},"CVE-2026-22036",[],[],[31,32,33,34,35,36,37],{"_key":15},{"_key":17},{"_key":19},{"_key":21},{"_key":23},{"_key":25},{"_key":27},"2026-02-15T09:26:17Z","2026-03-23T04:54:48.462593Z",{"cisa_kev":41,"cisa_ransomware":41,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[43,49,53,57,61,65,69,73,78,82,86,90,94,98],{"url":44,"sources":45,"tags":47},"https://bugzilla.suse.com/1256569",[46],"osv_opensuse",[48],"REPORT",{"url":50,"sources":51,"tags":52},"https://bugzilla.suse.com/1256570",[46],[48],{"url":54,"sources":55,"tags":56},"https://bugzilla.suse.com/1256571",[46],[48],{"url":58,"sources":59,"tags":60},"https://bugzilla.suse.com/1256573",[46],[48],{"url":62,"sources":63,"tags":64},"https://bugzilla.suse.com/1256574",[46],[48],{"url":66,"sources":67,"tags":68},"https://bugzilla.suse.com/1256576",[46],[48],{"url":70,"sources":71,"tags":72},"https://bugzilla.suse.com/1256848",[46],[48],{"url":74,"sources":75,"tags":76},"https://www.suse.com/security/cve/CVE-2025-55130",[46],[77],"WEB",{"url":79,"sources":80,"tags":81},"https://www.suse.com/security/cve/CVE-2025-55131",[46],[77],{"url":83,"sources":84,"tags":85},"https://www.suse.com/security/cve/CVE-2025-55132",[46],[77],{"url":87,"sources":88,"tags":89},"https://www.suse.com/security/cve/CVE-2025-59465",[46],[77],{"url":91,"sources":92,"tags":93},"https://www.suse.com/security/cve/CVE-2025-59466",[46],[77],{"url":95,"sources":96,"tags":97},"https://www.suse.com/security/cve/CVE-2026-21637",[46],[77],{"url":99,"sources":100,"tags":101},"https://www.suse.com/security/cve/CVE-2026-22036",[46],[77],[],[],[],[106],{"ecosystem":107,"name":108,"vendor":109,"product":110,"cpe_part":9,"purl_type":111,"purl_namespace":109,"purl_name":110,"source":9,"versions":112},"openSUSE","nodejs22","opensuse","nodejs22&distro=openSUSE Leap 16.0","rpm",[113],{"version":114,"is_range":115,"range_type":116,"version_start":9,"version_start_type":9,"version_end":117,"version_end_type":118,"fixed_in":9},"lt22_22_0_160000_1_1",true,"ecosystem","22.22.0-160000.1.1","excluding"]