Approved changes feed: RSS · Atom
cpe:2.3:a:bkddfs:shamefile:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Bkddfs (4dbf6314-2ce6-53ae-9a41-59776ebd119e) |
|---|---|
| Product | Shamefile (7f2cbcba-dfda-5d5e-bc81-a732353d197a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-47144 |
vulnerable | 2026-07-29 00:54:59.843673 |
Shamefile has an arbitrary file read via shamefile.yaml in shame next
MEDIUM (5.5)
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.
Published: 2026-07-20T21:49:09.058Z
Updated: 2026-07-22T14:18:13.390Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.