CVE-2026-63220Network attack vector

HTTPS enforcement bypass via untrusted proxy headers

Published Jul 31, 2026 · Updated Jul 31, 2026

Improper header trust in CodeIgniter 4 before 4.7.4 allows remote attackers to bypass HTTPS-dependent security logic via crafted HTTP headers. IncomingRequest::isSecure() accepts X-Forwarded-Proto and Front-End-Https values without first verifying that the request came from a configured trusted proxy, so plain HTTP is classified as secure. Reachability requires direct HTTP access to the backend or a proxy that preserves client-supplied forwarding headers; consequences depend on application logic that trusts the secure-state result.

CVSS severity4.8
Medium
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper header trust in CodeIgniter 4 before 4.7.4 allows remote attackers to bypass HTTPS-dependent security logic via crafted HTTP headers. IncomingRequest::isSecure() accepts X-Forwarded-Proto and Front-End-Https values without first verifying that the request came from a configured trusted proxy, so plain HTTP is classified as secure. Reachability requires direct HTTP access to the backend or a proxy that preserves client-supplied forwarding headers; consequences depend on application logic that trusts the secure-state result.

The record

CVE
CVE-2026-63220
Published
Jul 31, 2026
Updated
Jul 31, 2026
Vendor
CodeIgniter Foundation
Product
CodeIgniter 4
Classifications
CWE-348, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 31, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 31, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 4.7.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

CodeIgniter Foundation · CodeIgniter 4version=< 4.7.4

Published CVSS scores

4.8GitHubCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-348Use of Less Trusted Source
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo