Is CVE-2026-63220 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63220 being exploited in the wild.

How severe is CVE-2026-63220?

Medium severity, with a CVSS score of 4.8, published 31 July 2026.

Which products and versions are affected?

codeigniter4/framework (Packagist) < 4.7.4, ECOSYSTEM:introduced=0,fixed=4.7.4.

Is there a fix for CVE-2026-63220?

Yes. codeigniter4/framework (Packagist): upgrade to 4.7.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63220 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-63220?

Check whether you run codeigniter4/framework (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63220: CodeIgniter CodeIgniter4 header spoofing in IncomingRequest::isSecure

Q: Is there a fix for CVE-2026-63220?

Yes. codeigniter4/framework (Packagist): upgrade to 4.7.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-63220 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-63220?

Check whether you run codeigniter4/framework (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63220 · Severity: medium · CVSS 4.8 · Published 2026-07-31

CodeIgniter is a popular web application framework. A vulnerability in how it handles secure connection checks allows an attacker to trick the application into thinking an unencrypted (HTTP) request is actually encrypted (HTTPS). This could allow attackers to bypass security rules that require secure connections, potentially leading to unauthorized access or data exposure depending on how the application is configured.

Technologies: codeigniter4/framework (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-63220 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63220 being exploited in the wild.
How severe is CVE-2026-63220?: Medium severity, with a CVSS score of 4.8, published 31 July 2026.
Which products and versions are affected?: codeigniter4/framework (Packagist) < 4.7.4, ECOSYSTEM:introduced=0,fixed=4.7.4.
Is there a fix for CVE-2026-63220?: Yes. codeigniter4/framework (Packagist): upgrade to 4.7.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63220 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-63220?: Check whether you run codeigniter4/framework (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

codeigniter4/framework (Packagist): upgrade to 4.7.4 or later
```
composer require codeigniter4/framework:^4.7.4
```

Technical details

The IncomingRequest::isSecure() method in CodeIgniter4 incorrectly trusts 'X-Forwarded-Proto' and 'Front-End-Https' headers from any incoming request without verification. An attacker can spoof these headers to make the application believe a request is secure, bypassing logic in isSecure(), force_https(), or forceGlobalSecureRequests. This is particularly exploitable in environments where the backend is reachable via HTTP and a reverse proxy or load balancer fails to strip or overwrite client-supplied forwarding headers. The issue is classified as CWE-348 (Use of Less Trusted Source) and is fixed in version 4.7.4.

Affected products

CodeIgniter CodeIgniter4 < 4.7.4

Identifiers

CVE-2026-63220
GHSA-7wmf-pw8j-mc78

Timeline

2026-07-07: disclosed: Initial disclosure by paulbalandan
2026-07-31: advisory: NVD publication date
2026-08-07: advisory: GitHub Advisory published
2026-07-07: patched: Version 4.7.4 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.