{"total":17332,"items":[{"id":"CVE-2026-116099","cves":["CVE-2026-116099"],"title":"A flaw has been found in Fusion Creators Studio SCP Containment Breach Multiplayer up to 1.295","severity":"low","cvss":2.1,"vendors":["Fusion Creators Studio"],"products":["Fusion Creators Studio SCP Containment Breach Multiplayer"],"executive_summary":"A flaw has been reported in Fusion Creators Studio SCP Containment Breach Multiplayer, affecting versions up to 1.295. The advisory text describes a buffer overflow that could allow remote code execution, and it links to a public exploit repository. The advisory does not state a severity rating, and no vendor fix or recommendation is provided in the text.","technical_summary":"The advisory describes a buffer overflow vulnerability that allows arbitrary remote code execution. The stated preconditions are subscribing to a malicious addon on the workshop or connecting to a server that runs the RCE addon, and then playing the game. The affected version is stated as up to 1.295 in the title, and no fixed version is stated. No workaround, CVSS score, or vendor patch guidance is stated. Detection guidance is not stated, and the referenced repository includes a proof-of-concept exploit file named Exploit.gs.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/drbloop2000/SCP-CBM-RCE/tree/main"],"known_exploited":false,"published":"2026-10-26T00:17:14.613000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116099","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116098","cves":["CVE-2026-116098"],"title":"A vulnerability was detected in SteelRaven7 Ravenfield 25407073","severity":"medium","cvss":5.3,"vendors":["SteelRaven7"],"products":["SteelRaven7 Ravenfield"],"executive_summary":"The advisory reports a vulnerability in SteelRaven7 Ravenfield, but the text provided is a Steam Community web page and contains no description of the flaw itself. The severity and vendor recommendations are not stated.","technical_summary":"The advisory text only says a vulnerability was detected in SteelRaven7 Ravenfield 25407073, followed by boilerplate Steam Community page content. The vulnerability class, attack vector, and preconditions are not stated. Affected and fixed versions are not stated beyond the version string 25407073 shown in the title. No workaround, detection guidance, CVSS score, or evidence of exploitation is stated. Defenders should consult the NVD entry and the vendor for technical details.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://steamcommunity.com/app/636480/events/590690402783479125"],"known_exploited":false,"published":"2026-10-26T00:17:14.430000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116098","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116097","cves":["CVE-2026-116097"],"title":"A security vulnerability has been detected in CloudClassroom-PHP-Project","severity":"low","cvss":2.1,"vendors":["CloudClassroom-PHP-Project"],"products":["CloudClassroom-PHP-Project","CloudClassroom-PHP-Project addnewstudent.php"],"executive_summary":"A stored cross-site scripting flaw affects CloudClassroom-PHP-Project version 1.0 and prior, in the addnewstudent.php and studentdetails.php components. The advisory rates it Medium with a CVSS score of 6.1 and says the product is unpatched with no fix available yet. The advisory's recommended mitigations are output encoding, input validation, restricting access to the affected component, and reviewing sessions and credentials.","technical_summary":"The flaw is stored (persistent) cross-site scripting (CWE-79) in addnewstudent.php, where the fname, lname, faname, addrs and course fields are saved without sanitization and echoed back without HTML encoding, and the name is rendered unencoded in studentdetails.php. The advisory states that no authentication is needed to inject the data, that a victim admin or faculty user must view the record (user interaction required), and that the attack is remote over the network via POST. Affected versions are listed as 1.0 (and prior), and the fixed version is listed as None. The advisory gives workarounds: htmlspecialchars encoding with ENT_QUOTES, input validation, Content-Security-Policy, prepared statements, network ACLs and WAF rules, and session invalidation. It provides log search indicators for suspicious values such as script, onerror, onload and svg tags. It does not state a CVE identifier, an official vendor response, or any evidence of exploitation in the wild.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/vinniboy021-blip/Advisory/blob/main/addnewstudent-stored-xss.md"],"known_exploited":false,"published":"2026-10-26T00:17:14.260000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116097","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116096","cves":["CVE-2026-116096"],"title":"A weakness has been identified in ggml-org llama.cpp","severity":"low","cvss":1.9,"vendors":["ggml-org"],"products":["ggml-org llama.cpp"],"executive_summary":"The advisory describes a weakness in ggml-org llama.cpp, a C/C++ library for running large language models. The text provided is mostly repository content and does not describe the weakness, its severity, or a vendor fix, so these points are not stated.","technical_summary":"The advisory does not state the vulnerability class, attack vector, or preconditions. It does not list affected or fixed versions, workarounds, CVSS score, or exploitation status. The only identifiable reference is to the llama.cpp master branch repository page, which is not a version statement. Defenders should consult the NVD entry at the provided URL or the upstream project's security policy for the specific details.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/ggml-org/llama.cpp/"],"known_exploited":false,"published":"2026-10-25T23:17:41.897000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116096","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116095","cves":["CVE-2026-116095"],"title":"A vulnerability was identified in smg-project smg 1.7.0/1.8.0/1.9.0/1.10.0/1.10.1","severity":"medium","cvss":5.5,"vendors":["smg-project"],"products":["smg-project smg"],"executive_summary":"The advisory describes a flaw in smg-project smg versions 1.7.0 through 1.10.1 that appears to involve a crafted JPEG image causing excessive memory allocation. The advisory text is mostly a copied GitHub gist page and does not state a severity rating or a fixed version. No vendor recommendation is stated in the text provided.","technical_summary":"The advisory text is a copied gist page containing a proof-of-concept Python script that writes JPEG files declaring dimensions of 65500x65500 and 20000x20000, which the script says would require a large byte allocation in a decoder, and PNG control files. The vulnerability class is not explicitly stated, though the script comments suggest resource exhaustion through image dimension handling. The attack vector and preconditions are implied to be supplying a crafted image to the affected software, but this is not explicitly stated. Affected versions are listed as 1.7.0/1.8.0/1.9.0/1.10.0/1.10.1, and fixed versions, workarounds, CVSS score, and detection guidance are not stated.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://gist.github.com/Yunzez/24a1bf4c226fbc324ea8da1d202c6d9b"],"known_exploited":false,"published":"2026-10-25T23:17:41.220000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116095","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116094","cves":["CVE-2026-116094"],"title":"A vulnerability was determined in EyouCMS up to 1.8.3","severity":"medium","cvss":5.5,"vendors":["EyouCMS"],"products":["EyouCMS"],"executive_summary":"A vulnerability was reported in EyouCMS up to version 1.8.3, a content management system. The advisory describes a server-side request forgery flaw that can be triggered from the public site, but it does not state a severity rating.","technical_summary":"The advisory describes server-side request forgery caused by a missing SSRF check in the remote_file_to_local() function, which can be reached from the front end. It states the affected range as up to 1.8.3, but no fixed version is stated. Attack preconditions, CVSS score, and exploitation in the wild are not stated. No workaround is stated. No detection guidance is stated; the text mainly consists of repository file listings and references to a reproduction document and vulnerability report that are not included here.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/yy-t1/security-reports/tree/main/web/EyouCMS1.8.2/remote_file_to_local()%E7%BC%BA%E5%A4%B1%20SSRF%20%E6%A0%A1%E9%AA%8C%E5%AF%BC%E8%87%B4%E5%89%8D%E5%8F%B0%20SSRF"],"known_exploited":false,"published":"2026-10-25T22:16:29.253000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116094","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-115635","cves":["CVE-2026-115635"],"title":"Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to read another tenant's record through a skipped upsert.\n\nWhen Ash.bulk_create/4 or a single...","severity":"medium","cvss":6.0,"vendors":["ash-project"],"products":["ash-project ash_postgres"],"executive_summary":"A flaw in AshPostgres, a database library used with the Ash framework, can let one tenant read another tenant's record in a multi-tenant application. The advisory rates it MEDIUM with a CVSS 4.0 base score of 6.0. The advisory points to a fix in version 2.15.2 and the fix commit 8aa8122, and it does not state any workaround.","technical_summary":"This is an Incorrect Authorization flaw (CWE-863) in the ash_postgres data layer. When an upsert is skipped during Ash.bulk_create/4 or a single create with return_skipped_upsert?: true, the lookup of the existing row did not apply attribute multitenancy, so a user could receive another tenant's record that shares the same identity values. The advisory says the affected range is from 2.6.22 before 2.15.2 on Hex, and from commit af0903f up to commit 8aa8122 on GitHub. The CVSS vector is CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N, which requires low privileges and a resource that uses attribute multitenancy with return_skipped_upsert?: true. The advisory does not state any workaround or in-the-wild exploitation, and it gives no specific detection guidance beyond the affected routines.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://cna.erlef.org/cves/CVE-2026-115635.html"],"known_exploited":false,"published":"2026-10-25T20:16:32.293000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115635","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-115627","cves":["CVE-2026-115627"],"title":"Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant's join...","severity":"medium","cvss":6.0,"vendors":["ash-project"],"products":["ash-project ash_postgres"],"executive_summary":"A flaw in the ash_postgres library, used with the Elixir Ash framework, lets a user in one tenant see records that belong to other tenants' data when certain relationships are loaded. The advisory rates it MEDIUM with a CVSS 4.0 score of 6.0. The advisory states the affected range is from 0.38.0 before 2.15.2 on Hex, and the fix is in commit 8c25c94 on GitHub; it does not explicitly state an upgrade recommendation beyond that fix.","technical_summary":"This is an Incorrect Authorization flaw (CWE-863) where AshPostgres builds lateral join queries for many_to_many and through relationships without running the resource's read action, so attribute multitenancy is not applied to the join resource. The attack requires an authenticated user with low privileges (PR:L) and network access, and the preconditions are that the join resource uses :attribute multitenancy with rows from several tenants and that the relationship is loaded with a lateral join, such as with a limit, offset or sort. The advisory states the affected Hex versions as 0.38.0 up to but not including 2.15.2, and the GitHub affected range as commit 7115bec up to but not including 8c25c94. A workaround is not stated in the advisory. Detection guidance is not stated beyond the affected function names lateral_join_query/3, through_step_queries/4 and run_query_with_lateral_join/4 in lib/data_layer.ex.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://cna.erlef.org/cves/CVE-2026-115627.html"],"known_exploited":false,"published":"2026-10-25T20:16:32.110000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115627","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-114214","cves":["CVE-2026-114214"],"title":"Incorrect Authorization vulnerability in ash-project ash allows a client to read destination records unrelated to the source record through a through relationship.\n\nWhen a...","severity":"medium","cvss":6.0,"vendors":["ash-project"],"products":["ash-project ash"],"executive_summary":"A flaw in the Ash framework, an Elixir library from ash-project, lets a client read destination records that should only be reachable through a specific relationship. The advisory rates it MEDIUM with a CVSS 4.0 score of 6.0. The vendor's fix is in version 3.37.1, and the advisory says affected versions are 3.24.0 before 3.37.1.","technical_summary":"This is an Incorrect Authorization flaw (CWE-863) in the Ash read relationships code, specifically lateral_join?/4 in lib/ash/actions/read/relationships.ex. When a has_many through relationship is loaded for a single record with a limit of 1, or an unsorted has_one through relationship is loaded with a limit of 1, the query omits the filter linking destination records to the source, so the load returns unrelated records; paging with an offset can enumerate more of them. The attack vector is network with low complexity, and the CVSS vector requires low privileges and no user interaction, with high confidentiality impact. The advisory states the affected range as 3.24.0 up to but not including 3.37.1, with fix commit e374633, and says the vulnerable Git range is 24f41e2 to e374633. The advisory does not state a workaround or any detection guidance, and does not state whether the flaw has been exploited in the wild.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://cna.erlef.org/cves/CVE-2026-114214.html"],"known_exploited":false,"published":"2026-10-25T20:16:31.920000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-114214","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116063","cves":["CVE-2026-116063"],"title":"A weakness has been identified in DedeCMS up to 5.7.118","severity":"low","cvss":2.0,"vendors":["DedeCMS"],"products":["DedeCMS"],"executive_summary":"A remote code execution weakness has been reported in DedeCMS up to version 5.7.118, a content management system. The advisory rates it 7.2 under CVSS v3.1 base and 8.8 for the other listed score, and it lists a code injection flaw in the update guide script.","technical_summary":"The advisory describes a code injection flaw in dede/update_guide.php that can lead to remote code execution, mapped to CWE-94, CWE-96, and CWE-352. The table lists CVSS v3.1 scores of 7.2 / 8.8 without stating which score is the base score, and it does not state the attack vector, required privileges, or user interaction in plain terms. The advisory does not state a fixed version, a workaround, or any detection guidance. It also does not state whether exploitation has been observed in the wild.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/SDshadow/cve"],"known_exploited":false,"published":"2026-10-25T18:16:47.110000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116063","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116062","cves":["CVE-2026-116062"],"title":"A security flaw has been discovered in SourceCodester Performance Indicator System 1.0","severity":"medium","cvss":5.5,"vendors":["SourceCodester"],"products":["SourceCodester Performance Indicator System"],"executive_summary":"A SQL injection flaw has been reported in the Performance Indicator System 1.0 from SourceCodester, a PHP and MySQLi web application. The advisory says an attacker can exploit it without logging in to read, change, or delete database data. The advisory does not state a severity rating, a fixed version, or a vendor patch.","technical_summary":"The flaw is SQL injection in the 'contact' parameter of /opils/staff/save_profile.php, where user input is placed directly into SQL queries without validation. The advisory describes it as time-based blind and says no login or authorization is required. The affected version is listed as V1.0, and no fixed version is stated. No workaround is stated beyond the suggested repair of using prepared statements with parameter binding, strict input validation, least-privilege database accounts, and regular audits. The advisory gives no detection guidance, no CVSS score, and does not say whether exploitation in the wild has been observed.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/hubdk01/cve/issues/13"],"known_exploited":false,"published":"2026-10-25T18:16:46.950000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116062","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116061","cves":["CVE-2026-116061"],"title":"A vulnerability was identified in SourceCodester Performance Indicator System 1.0","severity":"medium","cvss":5.5,"vendors":["SourceCodester"],"products":["SourceCodester Performance Indicator System"],"executive_summary":"A SQL injection flaw has been reported in the Performance Indicator System 1.0 from SourceCodester, a PHP and MySQLi application. The advisory says an attacker needs no login to exploit it, which could expose or change database contents. The advisory does not state a vendor fix or official severity score, and it recommends using prepared statements, input validation, least-privilege database accounts, and regular security audits.","technical_summary":"The flaw is SQL injection in the 'contact' parameter of /opils/staff/edit_dealer.php, which the advisory says is passed directly into SQL queries without validation. The advisory describes it as time-based blind injection, reproduced with sqlmap, and says no login or authorization is required. The affected version is listed as V1.0; a fixed version is not stated. No workaround beyond the suggested code fixes (prepared statements, input validation, minimal database permissions) is given, and no CVSS score or detection guidance is stated. Exploitation in the wild is not stated.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/hubdk01/cve/issues/12"],"known_exploited":false,"published":"2026-10-25T18:16:46.790000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116061","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116060","cves":["CVE-2026-116060"],"title":"A vulnerability was determined in SourceCodester Performance Indicator System 1.0","severity":"medium","cvss":5.5,"vendors":["SourceCodester"],"products":["SourceCodester Performance Indicator System"],"executive_summary":"A SQL injection flaw has been reported in the Performance Indicator System 1.0 from SourceCodester, a PHP and MySQLi application. The advisory says an attacker who needs no login could read, change, or delete database data and potentially disrupt the service. The advisory does not state a severity score or a vendor fix, and it recommends prepared statements, input validation, and least-privilege database accounts.","technical_summary":"The flaw is a SQL injection in the 'contact' parameter of /opils/staff/adddealer.php, reached through a multipart/form-data POST request. The advisory states no login or authorization is required, and it describes a time-based blind variant that was confirmed with sqlmap. The affected version is listed as V1.0, and no fixed version is stated. No vendor patch, workaround beyond the suggested code fixes, CVSS score, or exploitation in the wild is stated. The suggested repair is to use prepared statements with parameter binding, validate and filter input, restrict database account privileges, and run regular security audits. The advisory gives no specific detection guidance such as log signatures.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/hubdk01/cve/issues/11"],"known_exploited":false,"published":"2026-10-25T17:17:02.123000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116060","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-115825","cves":["CVE-2026-115825"],"title":"HTTP::Server::PSGI versions before 1.0056 for Perl allow a single request to crash the server by declaring a large Content-Length.\n\nThe request body is read with sysread()...","severity":"unknown","cvss":null,"vendors":["HTTP::Server::PSGI"],"products":["HTTP::Server::PSGI"],"executive_summary":"HTTP::Server::PSGI for Perl, in versions before 1.0056, can be crashed by a single request that declares a very large Content-Length. The advisory describes this as a denial of service that makes the server run out of memory, and it says a fix caps body reads at 64 KiB. The advisory does not state a CVSS score or an explicit vendor recommendation beyond the fix in the patch.","technical_summary":"The flaw is a resource exhaustion (denial of service) issue in HTTP::Server::PSGI, where the whole remaining Content-Length is passed to sysread and Perl grows the buffer to that size before reading, causing an \"Out of memory!\" failure on Linux. The attack needs only a single crafted HTTP request declaring a large Content-Length; no authentication is mentioned in the advisory. Affected versions are stated as before 1.0056, and the fixed version is stated as 1.0056 by the vendor's description of the affected range. The fix reads the body in chunks of at most 64 KiB, and the added test checks that a huge Content-Length does not produce a sysread larger than MAX_REQUEST_SIZE. No workarounds, CVSS score, exploitation status, or detection guidance is stated in the advisory.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/plack/Plack/commit/11545871cadc5df1b744cebb429cfeb4ebc1069a.patch"],"known_exploited":false,"published":"2026-10-25T17:17:01.990000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115825","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-115824","cves":["CVE-2026-115824"],"title":"Starman versions before 0.4019 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies.\n\nThe chunked body decoder keeps each chunk in memory until...","severity":"unknown","cvss":null,"vendors":["Starman"],"products":["Starman"],"executive_summary":"Starman, a Perl web server, has a flaw that lets an attacker exhaust server memory by sending chunked request bodies that the server keeps buffering without limit. The advisory does not state a severity rating or CVSS score. The fix is included in version 0.4019, and the advisory indicates the patch is available in the repository.","technical_summary":"The advisory describes unbounded buffering of chunked request bodies in the chunk decoder, which can cause memory exhaustion, and the commit message also describes a quadratic-backtracking regex in chunk-size line parsing (CVE-2026-115822) that consumes CPU. The attack requires sending crafted chunked HTTP requests to a Starman server; the advisory does not state authentication or other preconditions. Affected versions are stated as those before 0.4019, and the fixed version is 0.4019. The fix replaces the regex with index() and an anchored parser, limits chunk-size lines to 4096 bytes, rejects sizes over 13 hex digits with 400 and closes the connection, and makes _prepare_env return an error status so bad bodies are not dispatched. No workarounds are stated, and no detection guidance or exploitation status is stated.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/miyagawa/Starman/commit/0f33f9b132b5e410d6cce722ff71988e22476acf.patch"],"known_exploited":false,"published":"2026-10-25T17:17:01.853000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115824","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-115823","cves":["CVE-2026-115823"],"title":"Starman versions before 0.4019 for Perl send response bodies for HEAD requests, desynchronizing responses on keep-alive connections.\n\nFor a HEAD request Starman omits chunked...","severity":"unknown","cvss":null,"vendors":["Starman"],"products":["Starman"],"executive_summary":"Starman, a Perl web server, sends response bodies for HEAD requests and for 1xx, 204 and 304 responses, which can cause response desynchronization on keep-alive connections. The advisory does not state a severity rating or an exploitation status, and the fix is in Starman versions 0.4019 and later.","technical_summary":"The flaw is a response desynchronization issue (HTTP response smuggling class) in Starman before 0.4019 for Perl, where bodies are written for HEAD, 1xx, 204 and 304 responses even though those responses must not carry a body. On keep-alive or pipelined connections, the extra bytes are read as the start of the next response, and a front end that pools upstream connections can be affected. The advisory does not state a CVSS score, attack preconditions beyond keep-alive or pipelined connections, or a workaround. The fix is in commit 91c47c529cd1e100f938486896ea9083ec3ec7bf, which skips body output for these responses and closes object bodies without reading them, and it adds a test file t/no_body_response.t. Detection guidance is not stated, and the advisory names no specific fixed release beyond the version threshold of 0.4019.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/miyagawa/Starman/commit/91c47c529cd1e100f938486896ea9083ec3ec7bf.patch"],"known_exploited":false,"published":"2026-10-25T17:17:01.743000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115823","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-115822","cves":["CVE-2026-115822"],"title":"Starman versions before 0.4019 for Perl allow CPU exhaustion via quadratic regex backtracking when parsing chunked request bodies.\n\nStarman decodes chunked request bodies...","severity":"unknown","cvss":null,"vendors":["Starman"],"products":["Starman"],"executive_summary":"The advisory says Starman, a Perl web server, is affected by a flaw that lets a remote sender exhaust CPU on the server by sending chunked request bodies with long runs of hex digits. The advisory does not give a severity rating or CVSS score. The vendor-side fix is a code change that rejects malformed or overly long chunk-size lines with a 400 error, and the advisory says versions before 0.4019 are affected.","technical_summary":"The flaw is a regular expression backtracking problem (quadratic complexity, a form of algorithmic CPU exhaustion) in parsing the chunk-size line of chunked request bodies, which the commit message says ran again over the whole buffer after every read. The attacker needs only to send an HTTP request with Transfer-Encoding: chunked; the advisory says 32 KiB of input cost about 1.7 seconds of worker CPU. The fix bounds chunk-size lines to 4096 bytes, parses them with an anchored linear-time pattern, rejects sizes with more than 13 significant hex digits, and returns 400 and closes the connection on malformed input. The advisory states affected versions as before 0.4019, but it does not state a fixed version number explicitly, and no workaround is stated. No detection guidance or evidence of exploitation in the wild is stated.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/miyagawa/Starman/commit/0f33f9b132b5e410d6cce722ff71988e22476acf.patch"],"known_exploited":false,"published":"2026-10-25T17:17:01.637000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115822","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-115817","cves":["CVE-2026-115817"],"title":"Starman versions before 0.4019 for Perl allow a stalled request body to hold a worker indefinitely, as read_timeout covers only the headers.\n\nContent-Length and chunked request...","severity":"unknown","cvss":null,"vendors":["Starman"],"products":["Starman"],"executive_summary":"Starman, a Perl web server, has a flaw where a client that sends a request body and then stalls can keep a server worker busy indefinitely, which can exhaust workers with only a few connections. The advisory describes the severity only in terms of workers being taken; a CVSS score is not stated. The fix adds a total time limit for reading request bodies, and the advisory's guidance is to update Starman to a release at or after 0.4019 (the fixed version is stated as 0.4019 in the advisory's wording of affected versions before 0.4019).","technical_summary":"The weakness is a resource exhaustion issue (missing timeout on request body reads): read_timeout applied only to request headers, so a Content-Length or chunked body could stall or trickle indefinitely. The attack requires only network access to the Starman listener and a few open connections to tie up workers, and no authentication is mentioned. Affected versions are stated as before 0.4019 and the fix adds a --body-timeout option (body_timeout, default 300 seconds, 0 disables) that responds with 408 Request Timeout and closes the connection. The advisory does not state a CVSS score, a CWE, exploitation in the wild, or detection guidance beyond the timeout behavior, and it recommends a reverse proxy that buffers request bodies as a mitigation. Workaround details beyond setting body_timeout are not otherwise stated.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/miyagawa/Starman/commit/89dffd3bdc9baa1cbe1b48a43615586ba2588558.patch"],"known_exploited":false,"published":"2026-10-25T17:17:00.940000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115817","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116058","cves":["CVE-2026-116058"],"title":"A vulnerability was found in Alfresco Activiti up to 7.21.0-rc.692","severity":"medium","cvss":5.3,"vendors":["Alfresco"],"products":["Alfresco Activiti"],"executive_summary":"A vulnerability has been reported in Alfresco Activiti, a workflow product, affecting versions up to 7.21.0-rc.692. The advisory says it can be exploited remotely to inject code, and the vendor did not respond when contacted about it. The advisory does not state a severity score or a fix.","technical_summary":"The flaw is described as code injection in the JuelScriptEngine.eval function of JuelScriptEngine.java, which is reached by performing a manipulation that the advisory does not specify. The attack can be initiated remotely. The advisory does not state any required privileges or user interaction, and it does not state a CVSS score. The advisory affects versions up to and including 7.21.0-rc.692, and no fixed version is stated. No workaround or detection guidance is stated. The vendor was contacted early but did not respond.","summary_by":"claude-haiku-5-5","summary_notes":[],"known_exploited":false,"published":"2026-10-25T16:16:50.350000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116058","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116057","cves":["CVE-2026-116057"],"title":"A vulnerability has been found in KodCloud KodExplorer up to 4.55","severity":"low","cvss":2.1,"vendors":["KodCloud"],"products":["KodCloud KodExplorer"],"executive_summary":"KodCloud KodExplorer, a web-based file manager, is affected by a vulnerability in versions up to 4.55. The advisory says the flaw can be exploited remotely and that exploit details are public, but it does not state a severity score. The advisory does not state any vendor-recommended fix, and the vendor did not respond to early disclosure.","technical_summary":"The flaw is an unrestricted upload issue in the Online Editor Save Endpoint, located in app/controller/editor.class.php, where manipulation of the path/filestr argument is reported. It can be attacked remotely, and the advisory says an exploit has been publicly disclosed and may be used. Affected versions are stated only as up to 4.55, and no fixed version is stated. No workaround, detection guidance, CVSS score, or authentication requirement is stated in the advisory.","summary_by":"claude-haiku-5-5","summary_notes":[],"known_exploited":false,"published":"2026-10-25T16:16:50.167000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116057","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116056","cves":["CVE-2026-116056"],"title":"A flaw has been found in KodCloud KodExplorer up to 4.56","severity":"medium","cvss":5.3,"vendors":["KodCloud"],"products":["KodCloud KodExplorer"],"executive_summary":"A flaw has been found in KodCloud KodExplorer, a file management product, up to version 4.56. The advisory describes it as a server-side request forgery issue that can be triggered remotely. The vendor did not respond when contacted about the disclosure, and no fix or vendor recommendation is stated.","technical_summary":"The flaw is server-side request forgery in the request_url_safe function of app/function/web.function.php, within the Remote Download component. An attacker can trigger it remotely by manipulating input to that function. The advisory states affected versions as up to 4.56 but does not state any fixed version. No workaround, exploitation status, CVSS score, or detection guidance is stated. The vendor was contacted early but did not respond.","summary_by":"claude-haiku-5-5","summary_notes":[],"known_exploited":false,"published":"2026-10-25T16:16:49.070000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116056","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116055","cves":["CVE-2026-116055"],"title":"A vulnerability was detected in SourceCodester Performance Indicator System 1.0","severity":"low","cvss":2.1,"vendors":["SourceCodester"],"products":["SourceCodester Performance Indicator System"],"executive_summary":"A SQL injection flaw was reported in the Performance Indicator System 1.0 from SourceCodester, a PHP and MySQLi web application. The advisory says an attacker needs no login to exploit it, which could expose or change database contents and disrupt the service. The advisory does not state a fixed version or a vendor patch, and it recommends code fixes such as prepared statements and input validation.","technical_summary":"The flaw is SQL injection in the 'id' parameter of /opils/admin/deleteproduct.php, where user input is placed directly into SQL queries without validation. The advisory states that no login or authorization is required, and it provides a POST request example. Boolean-based blind and time-based blind techniques were demonstrated with sqlmap. The affected version is listed as V1.0, and no fixed version is stated. No vendor workaround is stated beyond the suggested remediation of parameterized queries, input filtering, least-privilege database accounts, and security audits. No detection guidance or CVSS score is stated.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/hubdk01/cve/issues/5"],"known_exploited":false,"published":"2026-10-25T15:17:02.430000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116055","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116054","cves":["CVE-2026-116054"],"title":"A security vulnerability has been detected in SH3","severity":"low","cvss":1.2,"vendors":["SH3"],"products":["SH3 Módulo de Gestão/Módulo de Arrecadação"],"executive_summary":"A weakness has been reported in SH3, a product whose Gestão and Arrecadação management modules are affected. The advisory says the flaw is hard to exploit remotely, but a public exploit has been disclosed and may be used. The vendor's recommendation is to upgrade the affected component to version 2026.0.2.0.","technical_summary":"The flaw is classified as a password hash computed with insufficient computational effort, which weakens protection of stored credentials if an attacker obtains the hashes. The attack can be carried out remotely, but the advisory says it is highly complex and rated difficult to exploit. A public exploit has been disclosed. The advisory states that upgrading to version 2026.0.2.0 mitigates the issue; it does not state the vulnerable version range. No workaround, CVSS score, or detection guidance is stated in the advisory.","summary_by":"claude-haiku-5-5","summary_notes":[],"known_exploited":false,"published":"2026-10-25T15:17:01.307000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116054","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116211","cves":["CVE-2026-116211"],"title":"YesWiki 4.5.0 before 4.7.0 contains an SQL injection vulnerability in PageManager::save(), where the date_maj_fiche field of a Bazar entry-creation request is concatenated...","severity":"high","cvss":8.8,"vendors":["YesWiki"],"products":["yeswiki"],"executive_summary":"YesWiki versions from 4.5.0 before 4.7.0 contain an SQL injection flaw in the Bazar entry creation feature, where a date field from the request is inserted into a database query without escaping. The advisory rates it High with a CVSS score of 8.2 and says the fix is in version 4.7.0, so users should upgrade to 4.7.0 or later.","technical_summary":"The flaw is CWE-89 SQL injection in PageManager::save(), where the date_maj_fiche POST field is concatenated raw into an INSERT SET statement via the forcedDate parameter instead of being escaped like the other columns. The advisory describes a network attack with low complexity and no privileges required on the authenticated path, and says an unauthenticated path via action=saisir_fiche works on a default install, with confidentiality impact rated High. Affected versions are stated as >= 4.5.0, < 4.7.0 in the package data and <= 4.6.7 in the description, and the patched version is 4.7.0. The advisory suggests escaping $forcedDate at the sink or validating date_maj_fiche as a strict datetime, but does not state any other workaround. Detection guidance is not stated, and whether the flaw is exploited in the wild is not stated.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/YesWiki/yeswiki/security/advisories/GHSA-wjf7-hrf3-9gcx"],"known_exploited":false,"published":"2026-10-25T14:17:02.187000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116211","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}},{"id":"CVE-2026-116208","cves":["CVE-2026-116208"],"title":"YesWiki from 4.6.2 before 4.7.0 contains a missing authorization vulnerability in ActivityPubService::syncActorPosts that lets malicious ActivityPub servers manipulate other...","severity":"high","cvss":7.2,"vendors":["YesWiki"],"products":["yeswiki"],"executive_summary":"YesWiki, a wiki package used with ActivityPub federation, has a missing authorization flaw in its sync feature. A malicious federated server can cause a YesWiki administrator's routine sync to delete, overwrite, or create entries that belong to other federated actors. The advisory rates it High (8.1 CVSS) and states the fix status is not fixed, with the affected range given as versions 4.6.2 through 4.6.7; the advisory does not state a patched version for the sync path.","technical_summary":"The flaw is CWE-862 (missing authorization) in ActivityPubService::syncActorPosts, which processes Delete, Update, and Create activities from a remote outbox without the assertOwns() and sameHost() checks used by the inbox handler, and runs a host-scoped garbage-collection delete. Exploitation requires an administrator to trigger the sync action (a GET request with no CSRF token), and the attacker needs no privileges on the wiki; the CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H. The advisory lists the affected range as >= 4.6.2 and <= 4.6.7 in the body, while the metadata says '< 4.7.0' and the patched version is listed as 4.7.0, but it also says the fix status is 'not fixed' for the sync path. Workarounds are stated as avoiding sync with untrusted actors and adding a CSRF token to the sync action, which the advisory suggests but does not confirm as implemented. No detection guidance is stated, and no exploitation in the wild is stated.","summary_by":"claude-haiku-5-5","summary_notes":["Summarized from https://github.com/YesWiki/yeswiki/security/advisories/GHSA-cr64-h6xp-9g2j"],"known_exploited":false,"published":"2026-10-25T14:17:02.010000+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116208","source":{"name":"NVD","publisher":"NIST National Vulnerability Database"}}]}