Skip to content

ci: bump actions/checkout from 7.0.0 to 7.0.1 - #17

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/checkout-7.0.1
Open

ci: bump actions/checkout from 7.0.0 to 7.0.1#17
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/checkout-7.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 27, 2026

Copy link
Copy Markdown
Contributor

Bumps actions/checkout from 7.0.0 to 7.0.1.

Release notes

Sourced from actions/checkout's releases.

v7.0.1

What's Changed

Full Changelog: actions/checkout@v7...v7.0.1

Changelog

Sourced from actions/checkout's changelog.

Changelog

v7.0.1

v7.0.0

v6.0.3

v6.0.2

v6.0.1

v6.0.0

v5.0.1

v5.0.0

v4.3.1

v4.3.0

v4.2.2

v4.2.1

... (truncated)

Commits

@dependabot @github

dependabot Bot commented on behalf of github Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: ci, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/checkout-7.0.1 branch from cd542ab to 8d0e6a2 Compare July 31, 2026 14:47
Bumps [actions/checkout](https://github.com/actions/checkout) from 7.0.0 to 7.0.1.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@9c091bb...3d3c42e)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 7.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/checkout-7.0.1 branch from 8d0e6a2 to bb71f6f Compare July 31, 2026 19:57
ebrandi added a commit that referenced this pull request Jul 31, 2026
Nothing request-controlled reaches this today: the size preset is enum-checked twice, and
the background key can only be one of the manifest slugs seeded into SignatureBackground.
So as a reachable path traversal the alert is a false positive, and it would have been
defensible to dismiss it.

What was genuinely broken is the primitive. `sigbg_dir() / key / f"{preset}.png"` had no
confinement of any kind, so it depended entirely on every caller staying trustworthy. A
`key` of `..` walks out of the tree, and an absolute key escapes even more quietly —
pathlib DISCARDS the left operand when the right side is absolute, so `Path("/a") / "/etc"`
is `/etc`, which does not look like traversal when reading the line.

The path is now resolved and required to stay inside the asset tree, so the safety is local
to where the path is built instead of distributed across its callers. The file is only ever
read here and a miss returns None (the background is optional), so a strict rule costs
valid input nothing. Tests pin both escapes, and would fail if the confinement were removed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants