CVE-2026-24895
FrankenPHP affected by Path Confusion via Unicode casing in CGI path splitting allows execution of arbitrary files
FrankenPHP is a modern application server for PHP. Prior to 1.11.2, FrankenPHP’s CGI path splitting logic improperly handles Unicode characters during case conversion. The logic computes the split index (for finding .php) on a lowercased copy of the request path but applies that byte index to the original path. Because strings.ToLower() in Go can increase the byte length of certain UTF-8 characters (e.g., Ⱥ expands when lowercased), the computed index may not align with the correct position in the original string. This results in an incorrect SCRIPT_NAME and SCRIPT_FILENAME, potentially causing FrankenPHP to execute a file other than the one intended by the URI. This vulnerability is fixed in 1.11.2.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
8.9
FrankenPHP affected by Path Confusion via Unicode casing in CGI path splitting allows execution of arbitrary files
FrankenPHP is a modern application server for PHP. Prior to 1.11.2, FrankenPHP’s CGI path splitting logic improperly handles Unicode characters during case conversion. The logic computes the split index (for finding .php) on a lowercased copy of the request path but applies that byte index to the original path. Because strings.ToLower() in Go can increase the byte length of certain UTF-8 characters (e.g., Ⱥ expands when lowercased), the computed index may not align with the correct position in the original string. This results in an incorrect SCRIPT_NAME and SCRIPT_FILENAME, potentially causing FrankenPHP to execute a file other than the one intended by the URI. This vulnerability is fixed in 1.11.2.
- Record
CVE-2026-24895- CVSS 4.0
- 8.9 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P - Weakness
- CWE-180
- Updated
- 2026-11-02
EUVDEUVD-2026-6699
8.9
FrankenPHP is a modern application server for PHP. Prior to 1.11.2, FrankenPHP’s CGI path splitting logic improperly handles Unicode characters during case conversion. The logic computes the split index (for finding .php) on a lowercased copy of the request path but applies that byte index to the original path. Because strings.ToLower() in Go can increase the byte length of certain UTF-8 characters (e.g., Ⱥ expands when lowercased), the computed index may not align with the correct position in the original string. This results in an incorrect SCRIPT_NAME and SCRIPT_FILENAME, potentially causing FrankenPHP to execute a file other than the one intended by the URI. This vulnerability is fixed in 1.11.2.
- Record
EUVD-2026-6699- CVSS 4.0
- 8.9 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-g966-83w7-6w38
8.9
FrankenPHP's unicode case-folding length expansion causes incorrect split_path index (SCRIPT_NAME/PATH_INFO confusion) in FrankenPHP
Summary
FrankenPHP’s CGI path splitting logic improperly handles Unicode characters during case conversion. The logic computes the split index (for finding .php) on a lowercased copy of the request path but applies that byte index to the original path.
Because strings.ToLower() in Go can increase the byte length of certain UTF-8 characters (e.g., Ⱥ expands when lowercased), the computed index may not align with the correct position in the original string. This results in an incorrect SCRIPT_NAME and SCRIPT_FILENAME, potentially causing FrankenPHP to execute a file other than the one intended by the URI.
Details
The vulnerability resides in the splitPos() function and its usage within splitCgiPath(). The logic attempts to find the script extension (e.g., .php) in a case-insensitive manner by lowercasing the path:
lowerPath := strings.ToLower(path)
idx := strings.Index(lowerPath, strings.ToLower(split))
return idx + len(split)
The issue is that the returned idx represents a byte offset within lowerPath. However, splitCgiPath() uses this index to slice the original path:
fc.docURI = path[:splitPos]
fc.pathInfo = path[splitPos:]
fc.scriptName = strings.TrimSuffix(path, fc.pathInfo)
fc.scriptFilename = sanitizedPathJoin(fc.documentRoot, fc.scriptName)
This logic relies on the assumption that len(strings.ToLower(path)) == len(path). This assumption is false for certain Unicode characters. For example, the character Ⱥ (U+023A) requires 2 bytes in UTF-8 (0xC8 0xBA), but its lowercase equivalent ⱥ (U+2C65) requires 3 bytes (0xE2 0xB1 0xA5).
If the path contains such characters before the .php extension, the index calculated on lowerPath will be larger than the corresponding visual point in the original path. When applied to the original path, the split occurs at the wrong byte offset. This can cause the server to treat a larger portion of the path as the script name, effectively allowing an attacker to manipulate SCRIPT_FILENAME.
PoC
The following Go program demonstrates the discrepancy between the byte index in the lowercased string versus the original string.
- Save the following as
poc.go:
package main
import (
"fmt"
"strings"
)
func splitPos(path string, split string) int {
lowerPath := strings.ToLower(path)
idx := strings.Index(lowerPath, strings.ToLower(split))
if idx < 0 {
return -1
}
return idx + len(split)
}
func main() {
// U+023A: Ⱥ (UTF-8: C8 BA). Lowercase is ⱥ (UTF-8: E2 B1 A5), longer in bytes.
// We construct a path where the byte expansion shifts the index.
path := "/ȺȺȺȺshell.php.txt.php"
split := ".php"
pos := splitPos(path, split)
fmt.Printf("orig bytes=%d\n", len(path))
fmt.Printf("lower bytes=%d\n", len(strings.ToLower(path)))
fmt.Printf("splitPos=%d\n", pos)
// Current Unsafe Behavior:
fmt.Printf("orig[:pos] (Calculated Script)=%q\n", path[:pos])
fmt.Printf("orig[pos:] (Calculated PathInfo)=%q\n", path[pos:])
// Expected Safe Behavior:
want := strings.Index(path, split) + len(split)
fmt.Printf("expected splitPos=%d\n", want)
fmt.Printf("expected orig[:]=%q\n", path[:want])
}
- Run the PoC:
go run poc.go
- Output:
orig bytes=26
lower bytes=30
splitPos=22
orig[:pos]="/ȺȺȺȺshell.php.txt"
orig[pos:]=".php"
expected splitPos=18
expected orig[:]="/ȺȺȺȺshell.php"
In this example, FrankenPHP would identify /ȺȺȺȺshell.php.txt as the PHP script to execute, ignoring the fact that the actual file extension in the file system might be .txt.
Impact*
This is a Security Boundary Bypass and Path Confusion vulnerability.
In setups where users can upload files (e.g., avatars, text files) that are stored within the document root or a reachable path, an attacker can upload a file containing malicious PHP code with a safe extension (e.g.,…
- Record
GHSA-g966-83w7-6w38- CVSS 4.0
- 8.9 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - Weakness
- CWE-20, CWE-180
- Updated
- 2026-11-02
NVD
8.9
FrankenPHP is a modern application server for PHP. Prior to 1.11.2, FrankenPHP’s CGI path splitting logic improperly handles Unicode characters during case conversion. The logic computes the split index (for finding .php) on a lowercased copy of the request path but applies that byte index to the original path. Because strings.ToLower() in Go can increase the byte length of certain UTF-8 characters (e.g., Ⱥ expands when lowercased), the computed index may not align with the correct position in the original string. This results in an incorrect SCRIPT_NAME and SCRIPT_FILENAME, potentially causing FrankenPHP to execute a file other than the one intended by the URI. This vulnerability is fixed in 1.11.2.
- Record
CVE-2026-24895- CVSS 4.0
- 8.9 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-180
- Updated
- 2026-11-02
OSV
8.9
FrankenPHP affected by Path Confusion via Unicode casing in CGI path splitting allows execution of arbitrary files
FrankenPHP is a modern application server for PHP. Prior to 1.11.2, FrankenPHP’s CGI path splitting logic improperly handles Unicode characters during case conversion. The logic computes the split index (for finding .php) on a lowercased copy of the request path but applies that byte index to the original path. Because strings.ToLower() in Go can increase the byte length of certain UTF-8 characters (e.g., Ⱥ expands when lowercased), the computed index may not align with the correct position in the original string. This results in an incorrect SCRIPT_NAME and SCRIPT_FILENAME, potentially causing FrankenPHP to execute a file other than the one intended by the URI. This vulnerability is fixed in 1.11.2.
- Record
CVE-2026-24895- CVSS 4.0
- 8.9 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P - Weakness
- CWE-180
- Updated
- 2026-11-02
OSVGHSA-g966-83w7-6w38
8.9
FrankenPHP's unicode case-folding length expansion causes incorrect split_path index (SCRIPT_NAME/PATH_INFO confusion) in FrankenPHP
Summary
FrankenPHP’s CGI path splitting logic improperly handles Unicode characters during case conversion. The logic computes the split index (for finding .php) on a lowercased copy of the request path but applies that byte index to the original path.
Because strings.ToLower() in Go can increase the byte length of certain UTF-8 characters (e.g., Ⱥ expands when lowercased), the computed index may not align with the correct position in the original string. This results in an incorrect SCRIPT_NAME and SCRIPT_FILENAME, potentially causing FrankenPHP to execute a file other than the one intended by the URI.
Details
The vulnerability resides in the splitPos() function and its usage within splitCgiPath(). The logic attempts to find the script extension (e.g., .php) in a case-insensitive manner by lowercasing the path:
lowerPath := strings.ToLower(path)
idx := strings.Index(lowerPath, strings.ToLower(split))
return idx + len(split)
The issue is that the returned idx represents a byte offset within lowerPath. However, splitCgiPath() uses this index to slice the original path:
fc.docURI = path[:splitPos]
fc.pathInfo = path[splitPos:]
fc.scriptName = strings.TrimSuffix(path, fc.pathInfo)
fc.scriptFilename = sanitizedPathJoin(fc.documentRoot, fc.scriptName)
This logic relies on the assumption that len(strings.ToLower(path)) == len(path). This assumption is false for certain Unicode characters. For example, the character Ⱥ (U+023A) requires 2 bytes in UTF-8 (0xC8 0xBA), but its lowercase equivalent ⱥ (U+2C65) requires 3 bytes (0xE2 0xB1 0xA5).
If the path contains such characters before the .php extension, the index calculated on lowerPath will be larger than the corresponding visual point in the original path. When applied to the original path, the split occurs at the wrong byte offset. This can cause the server to treat a larger portion of the path as the script name, effectively allowing an attacker to manipulate SCRIPT_FILENAME.
PoC
The following Go program demonstrates the discrepancy between the byte index in the lowercased string versus the original string.
- Save the following as
poc.go:
package main
import (
"fmt"
"strings"
)
func splitPos(path string, split string) int {
lowerPath := strings.ToLower(path)
idx := strings.Index(lowerPath, strings.ToLower(split))
if idx < 0 {
return -1
}
return idx + len(split)
}
func main() {
// U+023A: Ⱥ (UTF-8: C8 BA). Lowercase is ⱥ (UTF-8: E2 B1 A5), longer in bytes.
// We construct a path where the byte expansion shifts the index.
path := "/ȺȺȺȺshell.php.txt.php"
split := ".php"
pos := splitPos(path, split)
fmt.Printf("orig bytes=%d\n", len(path))
fmt.Printf("lower bytes=%d\n", len(strings.ToLower(path)))
fmt.Printf("splitPos=%d\n", pos)
// Current Unsafe Behavior:
fmt.Printf("orig[:pos] (Calculated Script)=%q\n", path[:pos])
fmt.Printf("orig[pos:] (Calculated PathInfo)=%q\n", path[pos:])
// Expected Safe Behavior:
want := strings.Index(path, split) + len(split)
fmt.Printf("expected splitPos=%d\n", want)
fmt.Printf("expected orig[:]=%q\n", path[:want])
}
- Run the PoC:
go run poc.go
- Output:
orig bytes=26
lower bytes=30
splitPos=22
orig[:pos]="/ȺȺȺȺshell.php.txt"
orig[pos:]=".php"
expected splitPos=18
expected orig[:]="/ȺȺȺȺshell.php"
In this example, FrankenPHP would identify /ȺȺȺȺshell.php.txt as the PHP script to execute, ignoring the fact that the actual file extension in the file system might be .txt.
Impact*
This is a Security Boundary Bypass and Path Confusion vulnerability.
In setups where users can upload files (e.g., avatars, text files) that are stored within the document root or a reachable path, an attacker can upload a file containing malicious PHP code with a safe extension (e.g.,…
- Record
GHSA-g966-83w7-6w38- CVSS 4.0
- 8.9 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - Weakness
- CWE-180, CWE-20
- Updated
- 2026-11-02
OSVGO-2026-4486 No score
FrankenPHP's unicode case-folding length expansion causes incorrect split_path index (SCRIPT_NAME/PATH_INFO confusion) in FrankenPHP in github.com/dunglas/frankenphp
FrankenPHP's unicode case-folding length expansion causes incorrect split_path index (SCRIPT_NAME/PATH_INFO confusion) in FrankenPHP in github.com/dunglas/frankenphp
- Record
GO-2026-4486- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
- GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
- GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
- GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
- GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
- GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
- GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
- GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
- GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
- GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
- GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
- GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
- GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
- GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
- GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
- GO-2026-5933 GHSA-3g4q-2f67-2gvh
- GO-2026-5934 GHSA-59qp-cfj3-rp64
- GO-2026-5935 GHSA-7856-g3gv-9wq8
- GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
- GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
- GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
- GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
- GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
- GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
- GO-2026-5942 CVE-2026-46600
- GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
- GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
- GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
- GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
- GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
- GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
- GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
- GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
- GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
- GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
- GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
- GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
- GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
- GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
- GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
- GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
- GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
- GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
- GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
- GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
- GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
- GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
- GO-2026-5969 GHSA-g936-7jqj-mwv8
- GO-2026-5970 CVE-2026-56852
- GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
- GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
- GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
- GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
- GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
- GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
- GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
- GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
- GO-2026-5981 GHSA-mqxv-9rm6-w8qc
- GO-2026-5982 GHSA-pqg7-v6wh-3pfp
- GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
- GO-2026-5985 GHSA-7rx3-5wx3-5v76
- GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
- GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
- GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
- GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
- GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
- GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
- GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
- GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
- GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
- GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
- GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
- GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
- GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
- GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
- GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
- GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
- Record
openSUSE-SU-2026:21483-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0757-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
Update to version 0.0.20260226T182644 2026-02-26T18:26:44Z (jsc#PED-11136) Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-4259 CVE-2025-13767 GHSA-fmqf-pmcm-8cx9
- GO-2025-4260 CVE-2025-64641 GHSA-vww6-79rv-3j4x
- GO-2026-4282 CVE-2017-18873 GHSA-x6mw-hf2j-vqpc
- GO-2026-4305 CVE-2017-18903 GHSA-fcwg-45jh-5qhf
- GO-2026-4325 CVE-2025-14822 GHSA-9r42-rhw3-2222
- GO-2026-4326 CVE-2025-14435 GHSA-mx8m-v8qm-xwr8
- GO-2026-4332 CVE-2026-23644 GHSA-2657-3c98-63jq
- GO-2026-4348 CVE-2026-23991 GHSA-846p-jg2w-w324
- GO-2026-4349 CVE-2026-23992 GHSA-fphv-w9fq-2525
- GO-2026-4377 CVE-2026-24686 GHSA-jqc5-w2xx-5vq4
- GO-2026-4410 CVE-2026-25140 GHSA-f4w5-5xv9-85f6
- GO-2026-4502 CVE-2026-25766 GHSA-pgvm-wxw2-hrv9
- GO-2026-4534 CVE-2026-25899 GHSA-2mr3-m5q5-wgp6
- GO-2026-4535 CVE-2026-27585 GHSA-4xrr-hq4w-6vf4
- GO-2026-4536 CVE-2026-27590 GHSA-5r3v-vc8m-m96g
- GO-2026-4537 CVE-2026-27589 GHSA-879p-475x-rqh2
- GO-2026-4538 CVE-2026-27587 GHSA-g7pc-pc7g-h8jh
- GO-2026-4539 CVE-2026-27586 GHSA-hffm-g8v7-wrv7
- GO-2026-4540 CVE-2026-25891 GHSA-m3c2-496v-cw3v
- GO-2026-4541 CVE-2026-27588 GHSA-x76f-jf84-rqj8
- GO-2026-4543 CVE-2026-25882 GHSA-mrq8-rjmw-wpq3
- GO-2026-4559 CVE-2026-27141
Update to version 0.0.20260225T230704 2026-02-25T23:07:04Z.
- GO-2026-4358 CVE-2026-24137 GHSA-fcv2-xgw5-pqxf
- GO-2026-4361 GHSA-c32p-wcqj-j677
- GO-2026-4394 CVE-2026-24051 GHSA-9h8m-3fm2-qjrq
- GO-2026-4399 CVE-2026-25518 GHSA-gx3x-vq4p-mhhv
- GO-2026-4507 CVE-2026-26314 GHSA-2gjw-fg97-vg3r
- GO-2026-4508 CVE-2026-26313 GHSA-689v-6xwf-5jf3
- GO-2026-4509 CVE-2026-27017 GHSA-7m29-f4hw-g2vx
- GO-2026-4511 CVE-2026-26315 GHSA-m6j8-rg6r-7mv8
- GO-2026-4512 CVE-2026-26995 GHSA-rrxv-pmq9-x67r
- GO-2026-4531 CVE-2026-25591 GHSA-w6x6-9fp7-fqm4
- GO-2026-4532 CVE-2026-25802 GHSA-299v-8pq9-5gjq
- GO-2026-4533 CVE-2026-27571 GHSA-qrvq-68c2-7grw
- GO-2026-4542 CVE-2026-27598 GHSA-6v48-fcq6-ff23
- GO-2026-4545 CVE-2025-50180 GHSA-3c9r-837r-qqm4
- GO-2026-4546 CVE-2026-27611 GHSA-8vrh-3pm2-v4v6
- GO-2026-4547 CVE-2026-27626 GHSA-49gm-hh7w-wfvf
- GO-2026-4548 GHSA-2phg-qgmm-r638
Update to version 0.0.20260223T182315 2026-02-23T18:23:15Z.
- GO-2026-4392 CVE-2026-24845 GHSA-9m43-p3cx-w8j5
- GO-2026-4434 CVE-2023-43635 GHSA-4jvr-vj2c-8q37
- GO-2026-4435 CVE-2023-43636 GHSA-5h7v-g49c-h887
- GO-2026-4436 CVE-2023-43637 GHSA-g7vp-j25f-h34p
- GO-2026-4442 GHSA-x9p2-77v6-6vhf
- GO-2026-4444 CVE-2026-23989 GHSA-9j2f-3rj3-wgpg
- GO-2026-4445 CVE-2026-25760 GHSA-2286-hxv5-cmp2
- GO-2026-4446 CVE-2026-24851 GHSA-jq9f-gm9w-rwm9
- GO-2026-4447 GHSA-vf5j-r2hw-2hrw
- GO-2026-4448 CVE-2025-64111 GHSA-gg64-xxr9-qhjp
- GO-2026-4449 CVE-2025-64175 GHSA-p6x6-9mx6-26wj
- GO-2026-4450 CVE-2026-23632 GHSA-5qhx-gwfj-6jqr
- GO-2026-4451 CVE-2026-22592 GHSA-cr88-6mqm-4g57
- GO-2026-4452 CVE-2026-24135 GHSA-jp7c-wj6q-3qf2
- GO-2026-4453 CVE-2026-23633 GHSA-mrph-w4hh-gx3g
- GO-2026-4454 GHSA-26gq-grmh-6xm6
- GO-2026-4455 CVE-2025-70963 GHSA-9f8m-9547-2gqm
- GO-2026-4456 CVE-2025-13523 GHSA-ffx7-34p2-vm3w
- GO-2026-4457 CVE-2025-65852 GHSA-rjv5-9px2-fqw6
- GO-2026-4458 CVE-2026-25793 GHSA-69x3-g4r3-p962
- GO-2026-4459 CVE-2017-18907 GHSA-42x9-rr3c-gr59
- GO-2026-4460 CVE-2017-18918 GHSA-5ghq-28r7-qwfj
- GO-2026-4461 CVE-2026-25804 GHSA-86x4-wp9f-wrr9
- GO-2026-4462 CVE-2017-18915 GHSA-hxxj-8phw-74vw
- GO-2026-4463 CVE-2017-18917 GHSA-jxc4-w54c-qv5r
- GO-2026-4464 CVE-2017-18911 GHSA-m462-mqw4-2c8m
- GO-2026-4465 GHSA-vhvq-fv9f-wh4q
- GO-2026-4466 CVE-2026-25791 GHSA-wxrw-gvg8-fqjp
- GO-2026-4467 CVE-2017-18916 GHSA-x33g-375j-jhf7
- GO-2026-4471 CVE-2025-66630 GHSA-68rr-p4fp-j59v
- GO-2026-4473 CVE-2026-25934 GHSA-37cx-329c-33x3
- GO-2026-4474 CVE-2026-25890 GHSA-4mh3-h929-w968
- GO-2026-4475 CVE-2026-25889 GHSA-hxw8-4h9j-hq2r
- GO-2026-4476 CVE-2017-18908…
- Record
SUSE-SU-2026:0757-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/dunglas/frankenphpGo |
before 1.11.2 | 1.11.2 |
govulncheck-vulndbopenSUSE:Leap 15.6 From an advisory covering 104 CVEs |
before 0.0.20260226T182644-150000.1.149.1 | 0.0.20260226T182644-150000.1.149.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 1734 CVEs |
before 0.0.20260723T184607-160000.1.1 | 0.0.20260723T184607-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-24895 is a high vulnerability (CVSS 8.9) in Php Frankenphp, published February 12, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.65%, the 51st percentile. Fixed in github.com/dunglas/frankenphp 1.11.2.
References
github.com/php/frankenphp/security/advisories/GHSA-g966-83w7-6w38
github.com/php/frankenphp/commit/04fdc0c1e8fde94e2c1ad86217e962c88d27c53e
github.com/php/frankenphp/releases/tag/v1.11.2
nvd.nist.gov/vuln/detail/CVE-2026-24895
github.com/advisories/GHSA-g966-83w7-6w38
github.com/CVEProject/cvelistV5/tree/main/cves/2026/24xxx/CVE-2026-24895.json
Show 194 moreShow less
github.com/php/frankenphp
suse.com/support/update/announcement/2026/suse-su-20260757-1
suse.com/security/cve/CVE-2017-18873
suse.com/security/cve/CVE-2017-18903
suse.com/security/cve/CVE-2017-18906
suse.com/security/cve/CVE-2017-18907
suse.com/security/cve/CVE-2017-18908
suse.com/security/cve/CVE-2017-18909
suse.com/security/cve/CVE-2017-18911
suse.com/security/cve/CVE-2017-18912
suse.com/security/cve/CVE-2017-18915
suse.com/security/cve/CVE-2017-18916
suse.com/security/cve/CVE-2017-18917
suse.com/security/cve/CVE-2017-18918
suse.com/security/cve/CVE-2023-43635
suse.com/security/cve/CVE-2023-43636
suse.com/security/cve/CVE-2023-43637
suse.com/security/cve/CVE-2025-13523
suse.com/security/cve/CVE-2025-13767
suse.com/security/cve/CVE-2025-13821
suse.com/security/cve/CVE-2025-14350
suse.com/security/cve/CVE-2025-14435
suse.com/security/cve/CVE-2025-14573
suse.com/security/cve/CVE-2025-14822
suse.com/security/cve/CVE-2025-50180
suse.com/security/cve/CVE-2025-64111
suse.com/security/cve/CVE-2025-64175
suse.com/security/cve/CVE-2025-64641
suse.com/security/cve/CVE-2025-65852
suse.com/security/cve/CVE-2025-66630
suse.com/security/cve/CVE-2025-67860
suse.com/security/cve/CVE-2025-70963
suse.com/security/cve/CVE-2026-0997
suse.com/security/cve/CVE-2026-0998
suse.com/security/cve/CVE-2026-0999
suse.com/security/cve/CVE-2026-20796
suse.com/security/cve/CVE-2026-21434
suse.com/security/cve/CVE-2026-21435
suse.com/security/cve/CVE-2026-21438
suse.com/security/cve/CVE-2026-22592
suse.com/security/cve/CVE-2026-22892
suse.com/security/cve/CVE-2026-23632
suse.com/security/cve/CVE-2026-23633
suse.com/security/cve/CVE-2026-23644
suse.com/security/cve/CVE-2026-23989
suse.com/security/cve/CVE-2026-23991
suse.com/security/cve/CVE-2026-23992
suse.com/security/cve/CVE-2026-24051
suse.com/security/cve/CVE-2026-24122
suse.com/security/cve/CVE-2026-24135
suse.com/security/cve/CVE-2026-24137
suse.com/security/cve/CVE-2026-24686
suse.com/security/cve/CVE-2026-24834
suse.com/security/cve/CVE-2026-24845
suse.com/security/cve/CVE-2026-24851
suse.com/security/cve/CVE-2026-24894
suse.com/security/cve/CVE-2026-24895
suse.com/security/cve/CVE-2026-25120
suse.com/security/cve/CVE-2026-25140
suse.com/security/cve/CVE-2026-25229
suse.com/security/cve/CVE-2026-25232
suse.com/security/cve/CVE-2026-25242
suse.com/security/cve/CVE-2026-25518
suse.com/security/cve/CVE-2026-25591
suse.com/security/cve/CVE-2026-25760
suse.com/security/cve/CVE-2026-25766
suse.com/security/cve/CVE-2026-25791
suse.com/security/cve/CVE-2026-25793
suse.com/security/cve/CVE-2026-25802
suse.com/security/cve/CVE-2026-25804
suse.com/security/cve/CVE-2026-25882
suse.com/security/cve/CVE-2026-25889
suse.com/security/cve/CVE-2026-25890
suse.com/security/cve/CVE-2026-25891
suse.com/security/cve/CVE-2026-25899
suse.com/security/cve/CVE-2026-25934
suse.com/security/cve/CVE-2026-25935
suse.com/security/cve/CVE-2026-25949
suse.com/security/cve/CVE-2026-26014
suse.com/security/cve/CVE-2026-26055
suse.com/security/cve/CVE-2026-26056
suse.com/security/cve/CVE-2026-26187
suse.com/security/cve/CVE-2026-26190
suse.com/security/cve/CVE-2026-26201
suse.com/security/cve/CVE-2026-26205
suse.com/security/cve/CVE-2026-26313
suse.com/security/cve/CVE-2026-26314
suse.com/security/cve/CVE-2026-26315
suse.com/security/cve/CVE-2026-26957
suse.com/security/cve/CVE-2026-26958
suse.com/security/cve/CVE-2026-26963
suse.com/security/cve/CVE-2026-26995
suse.com/security/cve/CVE-2026-27017
suse.com/security/cve/CVE-2026-27111
suse.com/security/cve/CVE-2026-27112
suse.com/security/cve/CVE-2026-27141
suse.com/security/cve/CVE-2026-27571
suse.com/security/cve/CVE-2026-27585
suse.com/security/cve/CVE-2026-27586
suse.com/security/cve/CVE-2026-27587
suse.com/security/cve/CVE-2026-27588
suse.com/security/cve/CVE-2026-27589
suse.com/security/cve/CVE-2026-27590
suse.com/security/cve/CVE-2026-27598
suse.com/security/cve/CVE-2026-27611
suse.com/security/cve/CVE-2026-27626
suse.com/security/cve/CVE-2016-11063
suse.com/security/cve/CVE-2016-11066
suse.com/security/cve/CVE-2016-11067
suse.com/security/cve/CVE-2016-11068
suse.com/security/cve/CVE-2016-11069
suse.com/security/cve/CVE-2016-11070
suse.com/security/cve/CVE-2016-11071
suse.com/security/cve/CVE-2016-11072
suse.com/security/cve/CVE-2016-11073
suse.com/security/cve/CVE-2016-11074
suse.com/security/cve/CVE-2016-11075
suse.com/security/cve/CVE-2016-11076
suse.com/security/cve/CVE-2016-11077
suse.com/security/cve/CVE-2016-11078
suse.com/security/cve/CVE-2016-11079
suse.com/security/cve/CVE-2016-11080
suse.com/security/cve/CVE-2016-11081
suse.com/security/cve/CVE-2016-11082
suse.com/security/cve/CVE-2016-11083
suse.com/security/cve/CVE-2016-11084
suse.com/security/cve/CVE-2017-18870
suse.com/security/cve/CVE-2017-18871
suse.com/security/cve/CVE-2017-18872
suse.com/security/cve/CVE-2017-18874
suse.com/security/cve/CVE-2017-18875
suse.com/security/cve/CVE-2017-18876
suse.com/security/cve/CVE-2017-18877
suse.com/security/cve/CVE-2017-18878
suse.com/security/cve/CVE-2017-18879
suse.com/security/cve/CVE-2017-18883
suse.com/security/cve/CVE-2017-18884
suse.com/security/cve/CVE-2017-18885
suse.com/security/cve/CVE-2017-18886
suse.com/security/cve/CVE-2017-18887
suse.com/security/cve/CVE-2017-18888
suse.com/security/cve/CVE-2017-18889
suse.com/security/cve/CVE-2017-18890
suse.com/security/cve/CVE-2017-18891
suse.com/security/cve/CVE-2017-18892
suse.com/security/cve/CVE-2017-18893
suse.com/security/cve/CVE-2017-18894
suse.com/security/cve/CVE-2017-18895
suse.com/security/cve/CVE-2017-18896
suse.com/security/cve/CVE-2017-18897
suse.com/security/cve/CVE-2017-18898
suse.com/security/cve/CVE-2017-18900
suse.com/security/cve/CVE-2017-18901
suse.com/security/cve/CVE-2017-18902
suse.com/security/cve/CVE-2017-18904
suse.com/security/cve/CVE-2017-18905
suse.com/security/cve/CVE-2018-21258
suse.com/security/cve/CVE-2019-8400
suse.com/security/cve/CVE-2021-25320
suse.com/security/cve/CVE-2022-45786
suse.com/security/cve/CVE-2023-26154
suse.com/security/cve/CVE-2023-32199
suse.com/security/cve/CVE-2023-34620
suse.com/security/cve/CVE-2023-43630
suse.com/security/cve/CVE-2023-43631
suse.com/security/cve/CVE-2023-43632
suse.com/security/cve/CVE-2023-43633
suse.com/security/cve/CVE-2023-43634
suse.com/security/cve/CVE-2023-47108
suse.com/security/cve/CVE-2024-12886
suse.com/security/cve/CVE-2024-21635
suse.com/security/cve/CVE-2024-25621
suse.com/security/cve/CVE-2024-41260
suse.com/security/cve/CVE-2024-41265
suse.com/security/cve/CVE-2024-44905
suse.com/security/cve/CVE-2024-52284
suse.com/security/cve/CVE-2024-53412
suse.com/security/cve/CVE-2024-58259
suse.com/security/cve/CVE-2024-58260
suse.com/security/cve/CVE-2024-58267
suse.com/security/cve/CVE-2024-58269
suse.com/security/cve/CVE-2024-6717
suse.com/security/cve/CVE-2025-0426
suse.com/security/cve/CVE-2025-10543
suse.com/security/cve/CVE-2025-10545
suse.com/security/cve/CVE-2025-10630
suse.com/security/cve/CVE-2025-10678
suse.com/security/cve/CVE-2025-10954
suse.com/security/cve/CVE-2025-11374
suse.com/security/cve/CVE-2025-11375
suse.com/security/cve/CVE-2025-11393
suse.com/security/cve/CVE-2025-11579
suse.com/security/cve/CVE-2025-11621
suse.com/security/cve/CVE-2025-11776
Left out here: 1,542 references and the rest of 4 source descriptions. The JSON record has them.