CVE-2025-29927 - GitHub Advisory Database
Impact It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. Patches For Next.js 15.x, this issue is fixed in 15.2.3 For Next.js 14.x, this issue is fixed in 14.2.25 For Next.js 13.x, this issue is fixed in 13.5.9 For Next.js 12.x, this issue is fixed in 12.3.5 For Next.js 11.x, consult the below workaround. Note: Next.js deplo
CVE-2025-30066 - GitHub Advisory Database
Summary A supply chain attack compromised the tj-actions/changed-files GitHub Action, impacting over 23,000 repositories. Attackers retroactively modified multiple version tags to reference a malicious commit, exposing CI/CD secrets in workflow logs. The vulnerability existed between March 14 and March 15, 2025, and has since been mitigated. This poses a significant risk of unauthorized access to
CVE-2025-22150 - GitHub Advisory Database
Impact Undici fetch() uses Math.random() to choose the boundary for a multipart/form-data request. It is known that the output of Math.random() can be predicted if several of its generated values are known. If there is a mechanism in an app that sends multipart requests to an attacker-controlled website, they can use this to leak the necessary values. Therefore, An attacker can tamper with the req
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
CVE-2024-51757 - GitHub Advisory Database
CVE-2024-45047 - GitHub Advisory Database
CVE-2023-45133 - GitHub Advisory Database
CVE-2023-45311 - GitHub Advisory Database
CVE-2023-26122 - GitHub Advisory Database
CVE-2023-29008 - GitHub Advisory Database
CVE-2023-28155 - GitHub Advisory Database
CVE-2022-46175 - GitHub Advisory Database
CVE-2022-0639 - GitHub Advisory Database
CVE-2022-0235 - GitHub Advisory Database