CVE-2026-47144

See a problem?
Please try reporting it to the source first.

Source

https://cve.org/CVERecord?id=CVE-2026-47144

Import Source

https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-47144.json

JSON Data

https://api.osv.dev/v1/vulns/CVE-2026-47144

Aliases

Published

2026-07-20T21:49:09.058Z

Modified

2026-07-22T05:32:31.857953150Z

Severity

5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N CVSS Calculator

Summary

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

Details

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.

Database specific

{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/47xxx/CVE-2026-47144.json",
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
        "CWE-22"
    ]
}

References

Affected packages

Git / github.com/bkddfs/shamefile

Affected ranges

Type

GIT

Repo

https://github.com/bkddfs/shamefile

Events

Introduced

Fixed

77b0aeea318503582818c708518c601fedc43557

Fixed

9f4e5b06ab4651ed3e39c3bd90bcddfe649d8a29

Database specific

{
    "source": [
        "AFFECTED_FIELD",
        "REFERENCES"
    ],
    "extracted_events": [
        {
            "introduced": "0"
        },
        {
            "fixed": "0.1.7"
        }
    ]
}

Affected versions

v0.*

v0.1.0

v0.1.0-rc.1

v0.1.0-rc.2

v0.1.0-rc.3

v0.1.1

v0.1.2

v0.1.3

v0.1.4

v0.1.5

v0.1.6

Database specific

source

"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-47144.json"