<?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>Fri, 09 Oct 2026 09:20:39 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-322077</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-322077</link>
      <description>EUVD-2026-322077</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-322077</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44972</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44972</link>
      <description>&lt;p&gt;GuardDog is a CLI tool to identify malicious PyPI packages. From 2.6.0 to 2.9.0, GuardDog includes attacker-controlled filenames, file locations, messages, and code snippets in its default human-readable output without escaping terminal control characters. A malicious package can therefore inject ANSI or OSC escape sequences into analyst terminals or CI logs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GuardDog is a CLI tool to identify malicious PyPI packages. From 2.6.0 to 2.9.0, GuardDog includes attacker-controlled filenames, file locations, messages, and code snippets in its default human-readable output without escaping terminal control characters. A malicious package can therefore inject ANSI or OSC escape sequences into analyst terminals or CI logs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44972</guid>
    </item>
    <item>
      <title>GHSA-m5p4-gvpx-4mvr — GuardDog: Unsanitized human-readable scan output allows terminal escape injection from malicious package content</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m5p4-gvpx-4mvr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: guarddog&lt;/p&gt;
&lt;p&gt;# Summary
GuardDog includes attacker-controlled filenames, file locations, messages, and code snippets in its default human-readable output without escaping terminal control characters. A malicious package can therefore inject ANSI or OSC escape sequences into analyst terminals or CI logs.&lt;/p&gt;
&lt;p&gt;# Description
The finding formatter stores file paths and snippets from scanned content:&lt;/p&gt;
&lt;p&gt;```python
location = file_path + &amp;#34;:&amp;#34; + str(start_line)
finding = {
    &amp;#34;location&amp;#34;: location,
    &amp;#34;code&amp;#34;: code,
    &amp;#34;message&amp;#34;: result[&amp;#34;extra&amp;#34;][&amp;#34;message&amp;#34;],
}
```&lt;/p&gt;
&lt;p&gt;The human-readable reporter later prints these values directly:&lt;/p&gt;
&lt;p&gt;```python
&amp;#34;  * &amp;#34; + finding[&amp;#34;message&amp;#34;] + &amp;#34; at &amp;#34; + finding[&amp;#34;location&amp;#34;] + &amp;#34;\n    &amp;#34; + _format_code_line_for_output(finding[&amp;#34;code&amp;#34;])
```&lt;/p&gt;
&lt;p&gt;No escaping is applied for control characters such as `\x1b`. A malicious package can therefore ship a filename like:&lt;/p&gt;
&lt;p&gt;```text
evil\x1b[2J.py
```&lt;/p&gt;
&lt;p&gt;or matched source lines containing terminal escapes, which survive into the final CLI output.&lt;/p&gt;
&lt;p&gt;# Reproduction summary
1. Create a file whose name contains `\x1b[2J`.
2. Feed a semgrep-style result referencing that file into `Analyzer._format_semgrep_response()`.
3. Render the result with `HumanReadableReporter.print_scan_results()`.
4. The output string contains the raw escape bytes, which a terminal may interpret.&lt;/p&gt;
&lt;p&gt;# Key code paths
- `guarddog/analyzer/analyzer.py:377-392`
- `guarddog/reporters/human_readable.py:36-42`
- `guarddog/reporters/human_readable.py:84-91`&lt;/p&gt;
&lt;p&gt;# Practical impact
This can be used t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: guarddog&lt;/p&gt;
&lt;p&gt;# Summary
GuardDog includes attacker-controlled filenames, file locations, messages, and code snippets in its default human-readable output without escaping terminal control characters. A malicious package can therefore inject ANSI or OSC escape sequences into analyst terminals or CI logs.&lt;/p&gt;
&lt;p&gt;# Description
The finding formatter stores file paths and snippets from scanned content:&lt;/p&gt;
&lt;p&gt;```python
location = file_path + &amp;#34;:&amp;#34; + str(start_line)
finding = {
    &amp;#34;location&amp;#34;: location,
    &amp;#34;code&amp;#34;: code,
    &amp;#34;message&amp;#34;: result[&amp;#34;extra&amp;#34;][&amp;#34;message&amp;#34;],
}
```&lt;/p&gt;
&lt;p&gt;The human-readable reporter later prints these values directly:&lt;/p&gt;
&lt;p&gt;```python
&amp;#34;  * &amp;#34; + finding[&amp;#34;message&amp;#34;] + &amp;#34; at &amp;#34; + finding[&amp;#34;location&amp;#34;] + &amp;#34;\n    &amp;#34; + _format_code_line_for_output(finding[&amp;#34;code&amp;#34;])
```&lt;/p&gt;
&lt;p&gt;No escaping is applied for control characters such as `\x1b`. A malicious package can therefore ship a filename like:&lt;/p&gt;
&lt;p&gt;```text
evil\x1b[2J.py
```&lt;/p&gt;
&lt;p&gt;or matched source lines containing terminal escapes, which survive into the final CLI output.&lt;/p&gt;
&lt;p&gt;# Reproduction summary
1. Create a file whose name contains `\x1b[2J`.
2. Feed a semgrep-style result referencing that file into `Analyzer._format_semgrep_response()`.
3. Render the result with `HumanReadableReporter.print_scan_results()`.
4. The output string contains the raw escape bytes, which a terminal may interpret.&lt;/p&gt;
&lt;p&gt;# Key code paths
- `guarddog/analyzer/analyzer.py:377-392`
- `guarddog/reporters/human_readable.py:36-42`
- `guarddog/reporters/human_readable.py:84-91`&lt;/p&gt;
&lt;p&gt;# Practical impact
This can be used t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m5p4-gvpx-4mvr</guid>
    </item>
    <item>
      <title>PYSEC-2026-2506 — GuardDog: Unsanitized human-readable scan output allows terminal escape injection from malicious package content</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2506</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: guarddog&lt;/p&gt;
&lt;p&gt;# Summary
GuardDog includes attacker-controlled filenames, file locations, messages, and code snippets in its default human-readable output without escaping terminal control characters. A malicious package can therefore inject ANSI or OSC escape sequences into analyst terminals or CI logs.&lt;/p&gt;
&lt;p&gt;# Description
The finding formatter stores file paths and snippets from scanned content:&lt;/p&gt;
&lt;p&gt;```python
location = file_path + &amp;#34;:&amp;#34; + str(start_line)
finding = {
    &amp;#34;location&amp;#34;: location,
    &amp;#34;code&amp;#34;: code,
    &amp;#34;message&amp;#34;: result[&amp;#34;extra&amp;#34;][&amp;#34;message&amp;#34;],
}
```&lt;/p&gt;
&lt;p&gt;The human-readable reporter later prints these values directly:&lt;/p&gt;
&lt;p&gt;```python
&amp;#34;  * &amp;#34; + finding[&amp;#34;message&amp;#34;] + &amp;#34; at &amp;#34; + finding[&amp;#34;location&amp;#34;] + &amp;#34;\n    &amp;#34; + _format_code_line_for_output(finding[&amp;#34;code&amp;#34;])
```&lt;/p&gt;
&lt;p&gt;No escaping is applied for control characters such as `\x1b`. A malicious package can therefore ship a filename like:&lt;/p&gt;
&lt;p&gt;```text
evil\x1b[2J.py
```&lt;/p&gt;
&lt;p&gt;or matched source lines containing terminal escapes, which survive into the final CLI output.&lt;/p&gt;
&lt;p&gt;# Reproduction summary
1. Create a file whose name contains `\x1b[2J`.
2. Feed a semgrep-style result referencing that file into `Analyzer._format_semgrep_response()`.
3. Render the result with `HumanReadableReporter.print_scan_results()`.
4. The output string contains the raw escape bytes, which a terminal may interpret.&lt;/p&gt;
&lt;p&gt;# Key code paths
- `guarddog/analyzer/analyzer.py:377-392`
- `guarddog/reporters/human_readable.py:36-42`
- `guarddog/reporters/human_readable.py:84-91`&lt;/p&gt;
&lt;p&gt;# Practical impact
This can be used t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: guarddog&lt;/p&gt;
&lt;p&gt;# Summary
GuardDog includes attacker-controlled filenames, file locations, messages, and code snippets in its default human-readable output without escaping terminal control characters. A malicious package can therefore inject ANSI or OSC escape sequences into analyst terminals or CI logs.&lt;/p&gt;
&lt;p&gt;# Description
The finding formatter stores file paths and snippets from scanned content:&lt;/p&gt;
&lt;p&gt;```python
location = file_path + &amp;#34;:&amp;#34; + str(start_line)
finding = {
    &amp;#34;location&amp;#34;: location,
    &amp;#34;code&amp;#34;: code,
    &amp;#34;message&amp;#34;: result[&amp;#34;extra&amp;#34;][&amp;#34;message&amp;#34;],
}
```&lt;/p&gt;
&lt;p&gt;The human-readable reporter later prints these values directly:&lt;/p&gt;
&lt;p&gt;```python
&amp;#34;  * &amp;#34; + finding[&amp;#34;message&amp;#34;] + &amp;#34; at &amp;#34; + finding[&amp;#34;location&amp;#34;] + &amp;#34;\n    &amp;#34; + _format_code_line_for_output(finding[&amp;#34;code&amp;#34;])
```&lt;/p&gt;
&lt;p&gt;No escaping is applied for control characters such as `\x1b`. A malicious package can therefore ship a filename like:&lt;/p&gt;
&lt;p&gt;```text
evil\x1b[2J.py
```&lt;/p&gt;
&lt;p&gt;or matched source lines containing terminal escapes, which survive into the final CLI output.&lt;/p&gt;
&lt;p&gt;# Reproduction summary
1. Create a file whose name contains `\x1b[2J`.
2. Feed a semgrep-style result referencing that file into `Analyzer._format_semgrep_response()`.
3. Render the result with `HumanReadableReporter.print_scan_results()`.
4. The output string contains the raw escape bytes, which a terminal may interpret.&lt;/p&gt;
&lt;p&gt;# Key code paths
- `guarddog/analyzer/analyzer.py:377-392`
- `guarddog/reporters/human_readable.py:36-42`
- `guarddog/reporters/human_readable.py:84-91`&lt;/p&gt;
&lt;p&gt;# Practical impact
This can be used t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2506</guid>
    </item>
  </channel>
</rss>
