<?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>Sun, 18 Oct 2026 20:44:24 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-263486</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-263486</link>
      <description>EUVD-2026-263486</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-263486</guid>
    </item>
    <item>
      <title>fkie_cve-2025-67750</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-67750</link>
      <description>&lt;p&gt;Lightning Flow Scanner provides a A CLI plugin, VS Code Extension and GitHub Action for analysis and optimization of Salesforce Flows. Versions 6.10.5 and below allow a maliciously crafted flow metadata file to cause arbitrary JavaScript execution during scanning. The APIVersion rule uses new Function() to evaluate expression strings, enabling an attacker to supply a malicious expression within rule configuration or crafted flow metadata. This could compromise developer machines, CI runners, or editor environments. This issue is fixed in version 6.10.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Lightning Flow Scanner provides a A CLI plugin, VS Code Extension and GitHub Action for analysis and optimization of Salesforce Flows. Versions 6.10.5 and below allow a maliciously crafted flow metadata file to cause arbitrary JavaScript execution during scanning. The APIVersion rule uses new Function() to evaluate expression strings, enabling an attacker to supply a malicious expression within rule configuration or crafted flow metadata. This could compromise developer machines, CI runners, or editor environments. This issue is fixed in version 6.10.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-67750</guid>
    </item>
    <item>
      <title>GHSA-55jh-84jv-8mx8 — Lightning Flow Scanner Vulnerable to Code Injection via Unsafe Use of `new Function()` in APIVersion Rule</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-55jh-84jv-8mx8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: lightning-flow-scanner&lt;/p&gt;
&lt;p&gt;### Impact
The APIVersion rule uses `new Function()` to evaluate expression strings. A malicious crafted flow metadata file can cause arbitrary JavaScript execution during scanning. An attacker could execute arbitrary JavaScript during a scan by supplying a malicious expression within rule configuration or crafted flow metadata. This could compromise developer machines, CI runners, or editor environments.&lt;/p&gt;
&lt;p&gt;### Patches
The patch removes all uses of `new Function()` and replaces them with a safer parser. It now validates operators (`&amp;gt;`, &amp;gt;=`, `&amp;lt;`, `&amp;lt;=`, `==`) and performs numeric comparisons without evaluating untrusted JavaScript.&lt;/p&gt;
&lt;p&gt;**version:** core-v6.10.6,
**version vsx:**: v2.4.4
**version app:**: v3.1.0&lt;/p&gt;
&lt;p&gt;### Work around&lt;/p&gt;
&lt;p&gt;```
// --- Handle APIVersion rule separately to avoid unsafe-eval in the core library ---
      const apiVersionConfig = ruleConfig.rules.APIVersion;
      if (apiVersionConfig) {
        delete ruleConfig.rules.APIVersion;
      }&lt;/p&gt;
&lt;p&gt;// Manually evaluate the APIVersion rule, if it was configured.
      if (apiVersionConfig) {
        const flowApiVer = this.currentFlow.apiVersion || this.currentFlow.xmlData?.apiVersion;
        const apiVersionRuleDef = allRules.find(r =&amp;gt; r.name === &amp;#34;APIVersion&amp;#34;);&lt;/p&gt;
&lt;p&gt;// Determine the required expression (e.g. &amp;#34;&amp;gt;=58&amp;#34;).
        let requiredExpr;
        if (apiVersionConfig.expression) {
          requiredExpr = apiVersionConfig.expression;
        } else if (apiVersionConfig.threshold != null) {
          requiredExpr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: lightning-flow-scanner&lt;/p&gt;
&lt;p&gt;### Impact
The APIVersion rule uses `new Function()` to evaluate expression strings. A malicious crafted flow metadata file can cause arbitrary JavaScript execution during scanning. An attacker could execute arbitrary JavaScript during a scan by supplying a malicious expression within rule configuration or crafted flow metadata. This could compromise developer machines, CI runners, or editor environments.&lt;/p&gt;
&lt;p&gt;### Patches
The patch removes all uses of `new Function()` and replaces them with a safer parser. It now validates operators (`&amp;gt;`, &amp;gt;=`, `&amp;lt;`, `&amp;lt;=`, `==`) and performs numeric comparisons without evaluating untrusted JavaScript.&lt;/p&gt;
&lt;p&gt;**version:** core-v6.10.6,
**version vsx:**: v2.4.4
**version app:**: v3.1.0&lt;/p&gt;
&lt;p&gt;### Work around&lt;/p&gt;
&lt;p&gt;```
// --- Handle APIVersion rule separately to avoid unsafe-eval in the core library ---
      const apiVersionConfig = ruleConfig.rules.APIVersion;
      if (apiVersionConfig) {
        delete ruleConfig.rules.APIVersion;
      }&lt;/p&gt;
&lt;p&gt;// Manually evaluate the APIVersion rule, if it was configured.
      if (apiVersionConfig) {
        const flowApiVer = this.currentFlow.apiVersion || this.currentFlow.xmlData?.apiVersion;
        const apiVersionRuleDef = allRules.find(r =&amp;gt; r.name === &amp;#34;APIVersion&amp;#34;);&lt;/p&gt;
&lt;p&gt;// Determine the required expression (e.g. &amp;#34;&amp;gt;=58&amp;#34;).
        let requiredExpr;
        if (apiVersionConfig.expression) {
          requiredExpr = apiVersionConfig.expression;
        } else if (apiVersionConfig.threshold != null) {
          requiredExpr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-55jh-84jv-8mx8</guid>
    </item>
  </channel>
</rss>
