Bug 2523526 - CVE-2026-73423 python-jupytext: Astro: Cross-site Request Forgery (CSRF) due to origin check bypass in `astro/hono` pipeline [fedora-all]
Summary: CVE-2026-73423 python-jupytext: Astro: Cross-site Request Forgery (CSRF) due ...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: python-jupytext
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Jerry James
QA Contact:
URL:
Whiteboard: {"flaws": ["18bd8d0e-eeb4-427c-82f4-f...
Depends On:
Blocks: CVE-2026-73423
TreeView+ depends on / blocked
 
Reported: 2026-08-25 15:05 UTC by Joel Chamberlain
Modified: 2026-08-25 15:05 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Joel Chamberlain 2026-08-25 15:05:57 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Astro is a web framework for content-driven websites. From 7.0.0 until 7.0.6, the composable astro/hono pipeline installs security.checkOrigin only through the middleware() primitive, while actions() and pages() can dispatch to user code independently. Mounting actions() before middleware(), as in the examples/advanced-routing example and Cloudflare Hono documentation, allows cross-origin form-encoded action requests to execute before the origin check, and using pages() without middleware() drops the check for on-demand endpoints and pages. The flaw enables blind write-only cross-site request forgery using the victim's cookies against ActionHandler.handle and PagesHandler.handleWithErrorFallback when manifest.checkOrigin is enabled; the attacker can trigger a state-mutating action or endpoint handler but cannot read the cross-origin response. The default non-composable astro() pipeline is not affected. This issue is fixed in version 7.0.6.


Note You need to log in before you can comment on or make changes to this bug.