Skip to content
Heist/ feed
Back to feed
Medium

Shamefile has an arbitrary file read via shamefile.yaml in shame next

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-47144
Confirmed fixed CVEs
Not specified
Updated in this feed
5 Nov 2026, 04:00 UTC · Revision 1

Source evidence

Shamefile has an arbitrary file read via shamefile.yaml in shame next

core-osv · Original source

Published 20 Jul 2026, 21:49 UTC

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.

osv:CVE-2026-47144
Complete source record
{
  "id": "96611cc22f20d83348efd27a2bc316846c95a6bda505803a78c8a966d6fa5300",
  "url": "https://osv.dev/vulnerability/CVE-2026-47144",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Shamefile has an arbitrary file read via shamefile.yaml in shame next",
    "summary": "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.",
    "evidence": "osv:CVE-2026-47144",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2026-47144",
      "aliases": [
        "CVE-2026-47144",
        "GHSA-x6p3-76f2-xxvh",
        "PYSEC-2026-3065"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/bkddfs/shamefile",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "9f4e5b06ab4651ed3e39c3bd90bcddfe649d8a29"
                },
                {
                  "fixed": "77b0aeea318503582818c708518c601fedc43557"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "0.1.7"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StringRangeExpression"
                  },
                  {
                    "range": [
                      {
                        "fixed": "77b0aeea318503582818c708518c601fedc43557"
                      }
                    ],
                    "source": "REFERENCES_COMMIT"
                  },
                  {
                    "range": [
                      {
                        "fixed": "9f4e5b06ab4651ed3e39c3bd90bcddfe649d8a29"
                      }
                    ],
                    "source": "REFERENCES_TAG",
                    "original_tag": "v0.1.7"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v0.1.6",
            "v0.1.5",
            "v0.1.4",
            "v0.1.3",
            "v0.1.2",
            "v0.1.1",
            "v0.1.0",
            "v0.1.0-rc.3",
            "v0.1.0-rc.2",
            "v0.1.0-rc.1"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-47144.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:42.128508020Z",
      "provider": "osv",
      "references": [
        "https://github.com/BKDDFS/shamefile/releases/tag/v0.1.7",
        "https://github.com/BKDDFS/shamefile/security/advisories/GHSA-x6p3-76f2-xxvh",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/47xxx/CVE-2026-47144.json",
        "https://github.com/pypa/advisory-database/tree/main/vulns/shamefile/PYSEC-2026-3065.yaml",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-47144",
        "https://github.com/BKDDFS/shamefile/commit/77b0aeea318503582818c708518c601fedc43557",
        "https://github.com/BKDDFS/shamefile/pull/80"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-22"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/47xxx/CVE-2026-47144.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-47144",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 510075,
  "published_at": "2026-07-20T21:49:09.058+00:00"
}