Skip to content

🚨 [security] Update h3 1.15.5 → 1.15.9 (patch)#19832

Open
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/h3-1.15.9
Open

🚨 [security] Update h3 1.15.5 → 1.15.9 (patch)#19832
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/h3-1.15.9

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Mar 20, 2026


🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ h3 (1.15.5 → 1.15.9) · Repo · Changelog

Security Advisories 🚨

🚨 h3: Double Decoding in `serveStatic` Bypasses `resolveDotSegments` Path Traversal Protection via `%252e%252e`

More info than we can show here.

🚨 h3: SSE Event Injection via Unsanitized Carriage Return (`\r`) in EventStream Data and Comment Fields (Bypass of CVE Fix)

More info than we can show here.

🚨 h3 has a Server-Sent Events Injection via Unsanitized Newlines in Event Stream Fields

More info than we can show here.

🚨 h3 has a Path Traversal via Percent-Encoded Dot Segments in serveStatic Allows Arbitrary File Read

More info than we can show here.
Release Notes

1.15.9

More info than we can show here.

1.15.8

More info than we can show here.

1.15.6

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot requested a review from a team as a code owner March 20, 2026 22:05
@depfu depfu bot added the depfu label Mar 20, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 20, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 8632a743-4842-4b20-be1b-28fa5c093123

📥 Commits

Reviewing files that changed from the base of the PR and between 17d324f and d507eb7.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • packages/@tailwindcss-browser/package.json

Walkthrough

A development dependency in the Tailwind CSS browser package was updated. The h3 development dependency version in packages/@tailwindcss-browser/package.json was incremented from ^1.15.5 to ^1.15.9. This is a patch-level version bump within the same minor release. No other package configuration, dependencies, or exported functionality was modified by this change.

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: updating the h3 dependency from version 1.15.5 to 1.15.9 as a security patch.
Description check ✅ Passed The description is directly related to the changeset, explaining the h3 dependency update, the security vulnerabilities being fixed, and providing relevant details and resources.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

@depfu
Copy link
Contributor Author

depfu bot commented Mar 20, 2026

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants