Skip to content

Commit 5b40f21

Browse files
committed
1 parent f1fbd2d commit 5b40f21

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

advisories/github-reviewed/2025/03/GHSA-f82v-jwr5-mffw/GHSA-f82v-jwr5-mffw.json

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-f82v-jwr5-mffw",
4-
"modified": "2025-10-13T15:32:07Z",
4+
"modified": "2025-10-13T15:32:09Z",
55
"published": "2025-03-21T15:20:12Z",
66
"aliases": [
77
"CVE-2025-29927"
@@ -10,8 +10,8 @@
1010
"details": "# Impact\nIt is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.\n\n# Patches\n* For Next.js 15.x, this issue is fixed in `15.2.3`\n* For Next.js 14.x, this issue is fixed in `14.2.25`\n* For Next.js 13.x, this issue is fixed in 13.5.9\n* For Next.js 12.x, this issue is fixed in 12.3.5\n* For Next.js 11.x, consult the below workaround.\n\n_Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability._\n\n# Workaround\nIf patching to a safe version is infeasible, we recommend that you prevent external user requests which contain the `x-middleware-subrequest` header from reaching your Next.js application.\n\n## Credits\n\n- Allam Rachid (zhero;)\n- Allam Yasser (inzo_)",
1111
"severity": [
1212
{
13-
"type": "CVSS_V3",
14-
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:P/AC:H/AT:P/PR:H/UI:A/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N"
1515
}
1616
],
1717
"affected": [
@@ -143,7 +143,7 @@
143143
"CWE-285",
144144
"CWE-863"
145145
],
146-
"severity": "CRITICAL",
146+
"severity": "LOW",
147147
"github_reviewed": true,
148148
"github_reviewed_at": "2025-03-21T15:20:12Z",
149149
"nvd_published_at": "2025-03-21T15:15:42Z"

0 commit comments

Comments
 (0)