https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 17 Oct 2026 19:33:30 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-343941 EUVD-2026-343941 https://cve.radiocsirt.org/vuln/euvd-2026-343941 https://cve.radiocsirt.org/vuln/fkie_cve-2026-66296 <p>Improper Neutralization of Input During Web Page Generation (XSS) vulnerability in lud oaskit allows reflected cross-site scripting via the default HTML error handler.</p> <p>Oaskit.ErrorHandler.Default.format_reason/4 and Oaskit.ErrorHandler.Default.reason_to_html/1 in lib/oaskit/error_handler/default.ex render request-validation failures as an HTML page whenever the request&#39;s Accept header contains html, interpolating request-controlled strings into that page without HTML escaping. The unescaped values are object keys taken from a request body or from an object or deepObject query parameter, which appear in the JSON Schema error&#39;s instance path when a schema rejects them (for example under additionalProperties: false), and the raw Content-Type header, reflected in unsupported-media-type errors when it fails to parse.</p> <p>Because browsers send Accept: text/html on ordinary top-level navigation, a crafted GET link is sufficient to trigger the error page; no form submission, custom Content-Type, or attacker-controlled script on the victim&#39;s side is required. A payload such as filter[&lt;/code&gt;&lt;/h2&gt;&lt;script&gt;alert(document.domain)&lt;/script&gt;]=x terminates the enclosing markup and the injected script executes in the origin of the application using oaskit, giving it access to that origin&#39;s cookies, session, and same-origin responses.</p> <p>Both HTML error rendering and the vulnerable handler are enabled by default: Oaskit.Plugs.ValidateRequest defaults :html_errors to true and :error_handler to Oask…</p> <p>Improper Neutralization of Input During Web Page Generation (XSS) vulnerability in lud oaskit allows reflected cross-site scripting via the default HTML error handler.</p> <p>Oaskit.ErrorHandler.Default.format_reason/4 and Oaskit.ErrorHandler.Default.reason_to_html/1 in lib/oaskit/error_handler/default.ex render request-validation failures as an HTML page whenever the request&#39;s Accept header contains html, interpolating request-controlled strings into that page without HTML escaping. The unescaped values are object keys taken from a request body or from an object or deepObject query parameter, which appear in the JSON Schema error&#39;s instance path when a schema rejects them (for example under additionalProperties: false), and the raw Content-Type header, reflected in unsupported-media-type errors when it fails to parse.</p> <p>Because browsers send Accept: text/html on ordinary top-level navigation, a crafted GET link is sufficient to trigger the error page; no form submission, custom Content-Type, or attacker-controlled script on the victim&#39;s side is required. A payload such as filter[&lt;/code&gt;&lt;/h2&gt;&lt;script&gt;alert(document.domain)&lt;/script&gt;]=x terminates the enclosing markup and the injected script executes in the origin of the application using oaskit, giving it access to that origin&#39;s cookies, session, and same-origin responses.</p> <p>Both HTML error rendering and the vulnerable handler are enabled by default: Oaskit.Plugs.ValidateRequest defaults :html_errors to true and :error_handler to Oask…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-66296 https://cve.radiocsirt.org/vuln/ghsa-5rgx-mcq5-r7wv <p>Improper Neutralization of Input During Web Page Generation (XSS) vulnerability in lud oaskit allows reflected cross-site scripting via the default HTML error handler.</p> <p>Oaskit.ErrorHandler.Default.format_reason/4 and Oaskit.ErrorHandler.Default.reason_to_html/1 in lib/oaskit/error_handler/default.ex render request-validation failures as an HTML page whenever the request&#39;s Accept header contains html, interpolating request-controlled strings into that page without HTML escaping. The unescaped values are object keys taken from a request body or from an object or deepObject query parameter, which appear in the JSON Schema error&#39;s instance path when a schema rejects them (for example under additionalProperties: false), and the raw Content-Type header, reflected in unsupported-media-type errors when it fails to parse.</p> <p>Because browsers send Accept: text/html on ordinary top-level navigation, a crafted GET link is sufficient to trigger the error page; no form submission, custom Content-Type, or attacker-controlled script on the victim&#39;s side is required. A payload such as filter[&lt;/code&gt;&lt;/h2&gt;&lt;script&gt;alert(document.domain)&lt;/script&gt;]=x terminates the enclosing markup and the injected script executes in the origin of the application using oaskit, giving it access to that origin&#39;s cookies, session, and same-origin responses.</p> <p>Both HTML error rendering and the vulnerable handler are enabled by default: Oaskit.Plugs.ValidateRequest defaults :html_errors to true and :error_handler to Oask…</p> <p>Improper Neutralization of Input During Web Page Generation (XSS) vulnerability in lud oaskit allows reflected cross-site scripting via the default HTML error handler.</p> <p>Oaskit.ErrorHandler.Default.format_reason/4 and Oaskit.ErrorHandler.Default.reason_to_html/1 in lib/oaskit/error_handler/default.ex render request-validation failures as an HTML page whenever the request&#39;s Accept header contains html, interpolating request-controlled strings into that page without HTML escaping. The unescaped values are object keys taken from a request body or from an object or deepObject query parameter, which appear in the JSON Schema error&#39;s instance path when a schema rejects them (for example under additionalProperties: false), and the raw Content-Type header, reflected in unsupported-media-type errors when it fails to parse.</p> <p>Because browsers send Accept: text/html on ordinary top-level navigation, a crafted GET link is sufficient to trigger the error page; no form submission, custom Content-Type, or attacker-controlled script on the victim&#39;s side is required. A payload such as filter[&lt;/code&gt;&lt;/h2&gt;&lt;script&gt;alert(document.domain)&lt;/script&gt;]=x terminates the enclosing markup and the injected script executes in the origin of the application using oaskit, giving it access to that origin&#39;s cookies, session, and same-origin responses.</p> <p>Both HTML error rendering and the vulnerable handler are enabled by default: Oaskit.Plugs.ValidateRequest defaults :html_errors to true and :error_handler to Oask…</p> https://cve.radiocsirt.org/vuln/ghsa-5rgx-mcq5-r7wv