<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-12T14:21:43.436935+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-47144</id>
    <title>CVE-2026-47144 — Shamefile has an arbitrary file read via shamefile.yaml in shame next</title>
    <updated>2026-10-12T14:21:43.643562+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> BKDDFS shamefile</p>
<p>Shamefile is a linter for undocumented linter warnings. Prior to version 0.1.7, a path traversal vulnerability in `shame next` allows an attacker-controlled `shamefile.yaml` to disclose contents of files outside the repository, one line at a time, to the terminal of a user who runs the command. See patch commit for technical details. The issue is fixed in 0.1.7. Upgrade to either 0.1.7 or later versions to incorporate the patch. As a workaround, do not run `shame next` against untrusted `shamefile.yaml`. Use `shame me --dry-run` for CI validation.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-47144"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-x6p3-76f2-xxvh</id>
    <title>GHSA-x6p3-76f2-xxvh — Shamefile has an arbitrary file read via shamefile.yaml in shame next</title>
    <updated>2026-10-12T14:21:43.643698+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: shamefile, npm: shamefile, crates.io: shamefile</p>
<p>### Impact</p>
<p>A path traversal vulnerability in `shame next` allows an attacker-controlled `shamefile.yaml` to disclose contents of files outside the repository, one line at a time, to the terminal of a user who runs the command. See patch commit for technical details.</p>
<p>### Patches</p>
<p>Fixed in 0.1.7. Upgrade to either 0.1.7 or later versions to incorporate the patch.</p>
<p>### Workarounds</p>
<p>Do not run `shame next` against untrusted `shamefile.yaml`. Use `shame me --dry-run` for CI validation.</p>
<p>### Resources</p>
<p>- Patch commit: https://github.com/BKDDFS/shamefile/commit/77b0aeea318503582818c708518c601fedc43557
- Pull request: https://github.com/BKDDFS/shamefile/pull/80
- Release: https://github.com/BKDDFS/shamefile/releases/tag/v0.1.7
- [CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')](https://cwe.mitre.org/data/definitions/22.html)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-x6p3-76f2-xxvh"/>
  </entry>
</feed>
