<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 27 Oct 2026 20:48:04 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-22168</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-22168</link>
      <description>EUVD-2026-22168</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-22168</guid>
    </item>
    <item>
      <title>fkie_cve-2021-21316</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-21316</link>
      <description>&lt;p&gt;less-openui5 is an npm package which enables building OpenUI5 themes with Less.js. In less-openui5 before version 0.10., when processing theming resources (i.e. `*.less` files) with less-openui5 that originate from an untrusted source, those resources might contain JavaScript code which will be executed in the context of the build process. While this is a feature of the Less.js library it is an unexpected behavior in the context of OpenUI5 and SAPUI5 development. Especially in the context of UI5 Tooling which relies on less-openui5. An attacker might create a library or theme-library containing a custom control or theme, hiding malicious JavaScript code in one of the .less files. Refer to the referenced GHSA-3crj-w4f5-gwh4 for examples. Starting with Less.js version 3.0.0, the Inline JavaScript feature is disabled by default. less-openui5 however currently uses a fork of Less.js v1.6.3. Note that disabling the Inline JavaScript feature in Less.js versions 1.x, still evaluates code has additional double codes around it. We decided to remove the inline JavaScript evaluation feature completely from the code of our Less.js fork. This fix is available in less-openui5 version 0.10.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;less-openui5 is an npm package which enables building OpenUI5 themes with Less.js. In less-openui5 before version 0.10., when processing theming resources (i.e. `*.less` files) with less-openui5 that originate from an untrusted source, those resources might contain JavaScript code which will be executed in the context of the build process. While this is a feature of the Less.js library it is an unexpected behavior in the context of OpenUI5 and SAPUI5 development. Especially in the context of UI5 Tooling which relies on less-openui5. An attacker might create a library or theme-library containing a custom control or theme, hiding malicious JavaScript code in one of the .less files. Refer to the referenced GHSA-3crj-w4f5-gwh4 for examples. Starting with Less.js version 3.0.0, the Inline JavaScript feature is disabled by default. less-openui5 however currently uses a fork of Less.js v1.6.3. Note that disabling the Inline JavaScript feature in Less.js versions 1.x, still evaluates code has additional double codes around it. We decided to remove the inline JavaScript evaluation feature completely from the code of our Less.js fork. This fix is available in less-openui5 version 0.10.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-21316</guid>
    </item>
    <item>
      <title>GHSA-3crj-w4f5-gwh4 — Processing untrusted theming resources might execute arbitrary code (ACE)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3crj-w4f5-gwh4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: less-openui5&lt;/p&gt;
&lt;p&gt;### Impact
When processing theming resources (i.e. `*.less` files) with less-openui5 that originate from an untrusted source, those resources might contain JavaScript code which will be executed in the context of the build process.&lt;/p&gt;
&lt;p&gt;While this is a [feature](http://lesscss.org/usage/#less-options-enable-inline-javascript-deprecated-) of the [Less.js library](https://github.com/less/less.js), it is an unexpected behavior in the context of OpenUI5 and SAPUI5 development.&lt;/p&gt;
&lt;p&gt;Especially in the context of [UI5 Tooling](https://github.com/SAP/ui5-tooling), which relies on less-openui5, this poses a security threat:&lt;/p&gt;
&lt;p&gt;An attacker might create a [library](https://sap.github.io/ui5-tooling/pages/Builder/#library) or [theme-library](https://sap.github.io/ui5-tooling/pages/Builder/#theme-library) containing a custom control or theme, hiding malicious JavaScript code in one of the `.less` files.&lt;/p&gt;
&lt;p&gt;This is an example of inline JavaScript in a Less file:
```less
.rule {
	@var: `(function(){console.log(&amp;#39;Hello from JavaScript&amp;#39;); process.exit(1);})()`;
	color: @var;
}
```&lt;/p&gt;
&lt;p&gt;Starting with Less.js version 3.0.0, the Inline JavaScript feature is disabled by default. less-openui5 however currently uses [a fork](https://github.com/SAP/less-openui5/tree/master/lib/thirdparty/less) of Less.js v1.6.3.&lt;/p&gt;
&lt;p&gt;Note that disabling the Inline JavaScript feature in Less.js versions 1.x, still evaluates code has additional double codes around it:
```less
.rule {
	@var: &amp;#34;`(function(){console.log(&amp;#39;Hello from JavaScrip…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: less-openui5&lt;/p&gt;
&lt;p&gt;### Impact
When processing theming resources (i.e. `*.less` files) with less-openui5 that originate from an untrusted source, those resources might contain JavaScript code which will be executed in the context of the build process.&lt;/p&gt;
&lt;p&gt;While this is a [feature](http://lesscss.org/usage/#less-options-enable-inline-javascript-deprecated-) of the [Less.js library](https://github.com/less/less.js), it is an unexpected behavior in the context of OpenUI5 and SAPUI5 development.&lt;/p&gt;
&lt;p&gt;Especially in the context of [UI5 Tooling](https://github.com/SAP/ui5-tooling), which relies on less-openui5, this poses a security threat:&lt;/p&gt;
&lt;p&gt;An attacker might create a [library](https://sap.github.io/ui5-tooling/pages/Builder/#library) or [theme-library](https://sap.github.io/ui5-tooling/pages/Builder/#theme-library) containing a custom control or theme, hiding malicious JavaScript code in one of the `.less` files.&lt;/p&gt;
&lt;p&gt;This is an example of inline JavaScript in a Less file:
```less
.rule {
	@var: `(function(){console.log(&amp;#39;Hello from JavaScript&amp;#39;); process.exit(1);})()`;
	color: @var;
}
```&lt;/p&gt;
&lt;p&gt;Starting with Less.js version 3.0.0, the Inline JavaScript feature is disabled by default. less-openui5 however currently uses [a fork](https://github.com/SAP/less-openui5/tree/master/lib/thirdparty/less) of Less.js v1.6.3.&lt;/p&gt;
&lt;p&gt;Note that disabling the Inline JavaScript feature in Less.js versions 1.x, still evaluates code has additional double codes around it:
```less
.rule {
	@var: &amp;#34;`(function(){console.log(&amp;#39;Hello from JavaScrip…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3crj-w4f5-gwh4</guid>
    </item>
    <item>
      <title>gsd-2021-21316</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-21316</link>
      <description>gsd-2021-21316</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-21316</guid>
    </item>
  </channel>
</rss>
