Orval generates type-safe JavaScript clients in TypeScript from OpenAPI v3 and Swagger v2 specifications. Prior to 8.21.0, an unescaped backtick in servers[0].url is emitted into request URL template literals generated when output.baseUrl.getBaseUrlFromSpecification is enabled without safe encoding. This permits attacker-controlled JavaScript to be evaluated when a generated request or URL-builder function is called, resulting in code execution in the developer, CI, test, or application environment. The affected code is packages/core/src/getters/route.ts function getFullRoute. This issue is fixed in version 8.21.0.
CVE-2026-72717 is a critical code injection vulnerability in orval-labs' orval tool that generates type-safe JavaScript clients from OpenAPI and Swagger specifications. Versions prior to 8.21.0 improperly handle ${...} expressions or backticks in schema defaults, allowing attacker-controlled JavaScript to be executed when the generated zod schema module is imported. This can lead to code execution in developer, CI, test, or application environments. The issue is fixed in version 8.21.0.
CVE-2026-71865 is a critical code injection vulnerability in orval-labs' orval tool that generates type-safe JavaScript clients from OpenAPI and Swagger specifications. Versions prior to 8.21.0 improperly handle double quotes in query parameter names, embedding them unsafely into generated zod validation schemas. This flaw allows attacker-controlled JavaScript to be executed when the generated schema module is imported, leading to code execution in developer, CI, test, or application environments. The issue is fixed in version 8.21.0.
CVE-2026-71869 is a critical code injection vulnerability in orval-labs' orval software prior to version 8.21.0. The issue arises from unsafe encoding of ${...} expressions or backticks in array item defaults during zod schema generation, allowing attacker-controlled JavaScript to be executed when the generated module is imported. This can lead to code execution in developer, CI, test, or application environments. The vulnerability is fixed in version 8.21.0.
CVE-2026-71864 is a critical code injection vulnerability in orval-labs orval prior to version 8.21.0. The issue arises because a double quote in a header parameter name is not safely encoded when generating the request-validation zod schema, allowing attacker-controlled JavaScript code to be executed when the generated module is imported. This can lead to code execution in developer, CI, test, or application environments. The vulnerability is fixed in version 8.21.0.
CVE-2026-71871 is a critical code injection vulnerability in orval-labs' orval tool that generates type-safe JavaScript clients from OpenAPI and Swagger specifications. Versions prior to 8.21.0 improperly handle default header parameter values containing ${...} expressions or backticks, embedding attacker-controlled JavaScript into generated zod schema modules. This leads to arbitrary code execution when the module is imported in developer, CI, test, or application environments. The issue is fixed in version 8.21.0.
CVE-2026-62681 is a critical code injection vulnerability in orval versions prior to 8.21.0. The issue arises because unescaped backticks in OpenAPI paths are directly embedded into JavaScript template literals used for generating request URLs in clients like axios, fetch, react-query, and SWR. This flaw allows attacker-controlled JavaScript code to be executed in environments where the generated code runs, such as developer machines, CI pipelines, test environments, or applications. The vulnerability is fixed in version 8.21.0.
Improper Encoding or Escaping of Output vulnerability in ninenines cowlib allows Link header directive smuggling via unescaped special characters in cow_link:link/1.
cow_link:do_link/1 in cowlib interpolates the target URI, rel value, and attribute keys directly into the serialized Link: header value without escaping or token-grammar validation. A > byte in target prematurely closes the URI slot, allowing an attacker to append additional link entries with attacker-chosen rel directives. A " or \ in rel escapes the quoted string and opens new parameters. Any byte — including whitespace, =, and " — in an attribute key is emitted verbatim. Because browsers act on Link: directives such as rel="preconnect", rel="preload", and rel="prerender", an attacker who can influence these fields in an application that round-trips parsed Link headers through cow_link:link/1 can force victim browsers to make out-of-band connections to attacker-controlled origins.
This issue affects cowlib: from 2.9.0 before 2.20.0.
HCL AION is affected by a vulnerability where certain input fields do not enforce sufficient server-side input validation. Unexpected or crafted input may be accepted by the application, potentially resulting in unintended behavior or security impact under certain conditions.
Shescape is a simple shell escape library for JavaScript. Prior to 2.1.14 and 3.0.1, getEscapeFunction in src/internal/unix/dash.js fails to escape ~ after : or = when applications use the escape or escapeAll APIs on Unix with shell set to dash, or with shell set to true when Dash is the default, and interpolate the result into an assignment prefixed to a command. An attacker who controls the input can supply a value such as :~ to disclose the home-directory path and may change the location on which the command operates. This issue is fixed in versions 2.1.14 and 3.0.1.
is affected by an Improper Encoding or Escaping of Output vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain limited unauthorized write access, causing a limited disruption to availability. Exploitation of this issue does not require user interaction.
SWC is a TypeScript / JavaScript compiler written in Rust. Prior to @swc/html 1.15.47-nightly-20260729.1 and swc_html_minifier 59.0.0, the minifyJson processing in crates/swc_html_minifier/src/lib.rs parsed and serialized attacker-controlled JSON in application/json and application/ld+json script elements without the escape_json_for_html_script behavior to re-escape less-than signs, allowing a closing script sequence to terminate the element early and execute script in the generated page's origin. This issue is fixed in @swc/html 1.15.47-nightly-20260729.1 and swc_html_minifier 59.0.0.
Affected versions of cti-transmute improperly handle conversion-table values passed through the search highlighting feature. The highlight() function previously returned the underlying text directly when no search query was supplied, or performed a regex replacement that inserted <mark> tags without first escaping the original content. Because the resulting value is used by an HTML-rendering sink, malicious markup contained in conversion data could be interpreted as HTML rather than displayed as text.
The fix introduces a shared highlightMatches() helper that first converts special characters such as <, >, &, and quotes into HTML entities. Only after escaping does the code insert the application-controlled <mark> element used for search highlighting.
Affected versions of cti-transmute render data obtained from a remote MISP instance into the event-browser interface using HTML interpolation. Because fields such as event IDs, event information, organization names, tags, tag colors, TLP labels, distribution labels, and error/flash text may be controlled by the remote MISP server, a malicious or compromised remote instance could return crafted values that inject HTML or script-capable content into the cti-transmute interface.
The patch explicitly notes that remote-derived values must not reach innerHTML, and replaces string-built rows and badges with DOM nodes populated through textContent. It also restricts remote-controlled tag colors to six-digit hexadecimal values, preventing malicious CSS values such as url(...).
GNU cpio is vulnerable to improper encoding or escaping of output in its archive member listing functionality. When listing archive members via cpio -it, member names are printed directly to output without quoting or escaping. An attacker can craft a cpio archive containing member names with embedded newline characters or ANSI escape sequences, causing forged listing entries or terminal control sequence injection when the listing is displayed.
This issue has been fixed in commit 2ff9600c9ef32e88759843cdbde74c8db5ae9b30
MathLive provides web components for math display and input. Prior to 0.110.0, MathLive fails to escape text-mode content in \text{} and \mbox{} commands in Box.toMarkup at src/core/box.ts, in xmlEscape, scanText, and text-mode output in src/formats/atom-to-math-ml.ts, and through convertLatexToMarkup, convertLatexToMathMl, <math-span>, <math-div>, and the default identity MathfieldElement.createHTML, allowing malicious input to run arbitrary JavaScript when rendered. This issue is fixed in version 0.110.0.
diff‑so‑fancy does not properly sanitize non‑SGR terminal control sequences before outputting diff data. The application only strips ANSI SGR sequences while allowing other control characters, including carriage return (\r) and escape sequences (e.g., OSC, CSI), to pass through unsanitized.
An attacker can embed malicious control sequences in filenames, diff metadata, or file content that are rendered directly in the terminal during diff viewing. This can lead to output manipulation, including filename spoofing, terminal screen clearing, and clipboard injection via supported escape sequences.
Successful exploitation may mislead users during code review, alter terminal state, or result in unintended command execution through clipboard hijacking.
This issue has been fixed in the commit 9c81294
Astro is a web framework for content-driven websites. In versions 3.10.0 through 7.0.3, when a transition:persist, transition:scope, or transition:persist-props directive is applied to a client-hydrated (client:*) component, Astro copied the directive value onto the rendered <astro-island> element without HTML-escaping it. If a developer reflects attacker-controlled input into one of these directives, an attacker can break out of the attribute and inject arbitrary HTML/JavaScript into the server-rendered output, resulting in reflected cross-site scripting (XSS). Exploitation requires the application developer to have written a non-idiomatic pattern — passing untrusted, request-derived input directly into a transition directive. Astro applications that do not route untrusted input into these directives are unaffected. This issue has been fixed in version 7.0.4.
Next.js versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10 have a vulnerability where server-side fetches with request bodies may return cached response bodies from different requests sharing the same URL but different bodies. This can lead to confidential data leakage in POST response bodies when the request body uses a non-UTF-8 charset. The issue is fixed in versions 15.5.21 and 16.2.11.
A reflected cross-site scripting (XSS) vulnerability (CWE-79) exists in Loytec LWEB-802 before version 5.0.8. This vulnerability allows an unauthenticated remote attacker to execute arbitrary JavaScript in a victim's browser by crafting a malicious link with specific parameters. The attack can lead to actions performed with the victim's privileges. The vulnerability has a high severity score of 8.7 (CVSS 4.0). No official patch or remediation guidance is currently provided by the vendor.