Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2025-14177: Uninitialized heap memory disclosure in PHP getimagesize()

Published Dec 27, 2025 · Updated 23 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS6.3Medium · v4
EPSS0.50%44th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
PHP Group
IdentifiersCVE-2025-14177CWE-908

CVE-2025-14177 is an information-disclosure vulnerability in PHP getimagesize() affecting PHP 8.1 before 8.1.34, 8.2 before 8.2.30, 8.3 before 8.3.29, 8.4 before 8.4.16, and 8.5 before 8.5.1. When a JPEG APP segment is read across multiple chunks, php_read_stream_all_chunks() fails to advance the destination buffer pointer between reads. Subsequent chunks overwrite the beginning of the buffer, leaving trailing bytes uninitialized. These bytes can be returned to PHP code through the optional image-information array's APPn entries, potentially exposing sensitive process heap contents. Both filter-based and filterless stream-processing scenarios can trigger the flaw.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disclose residual data from the PHP process heap through returned JPEG APP metadata. Server confidentiality is affected if the application exposes that metadata to an attacker. The disclosed information depends on heap contents and application behavior. This vulnerability does not establish code execution, data modification, or denial of service.

Mitigation

If you can’t patch tonight, do this now.

Until patched, reduce exposure by preventing untrusted JPEGs from reaching the affected getimagesize() processing path and by avoiding disclosure of returned APPn metadata to untrusted clients. Disabling filter-based input alone is insufficient because ordinary streams can also trigger multi-chunk reads. These measures reduce exposure but do not correct the memory-handling defect.

Remediation

Patch, then assume compromise.

Upgrade to PHP 8.1.34, 8.2.30, 8.3.29, 8.4.16, or 8.5.1 or later in the corresponding branch, or install a vendor package containing the backported fix. The fix advances the destination buffer pointer after each read so that chunks are appended correctly. Distribution-specific fixed packages include Debian php8.2 8.2.30-1~deb12u1 and php8.4 8.4.16-1~deb13u1.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
PHP_8.1.x_ExploitThis repository is a standalone Bash-based exploit toolkit centered on PHP8.1.x_Exploit.sh, which orchestrates detection and exploitation of four PHP CVEs using modular helper scripts under modules/. The main script normalizes target URLs, fingerprints OS and PHP version via HTTP headers and a phpinfo.php probe, crawls homepage links/forms, enumerates likely CGI and upload endpoints, and then invokes per-CVE modules. The repository structure is simple: one main driver script, four CVE-specific Bash modules, one shared utils module, and a README. Primary exploit capability is CVE-2024-4577 against Windows PHP-CGI. The module tests two query-string injection variants, including a soft-hyphen bypass, by setting allow_url_include and auto_prepend_file=php://input and POSTing PHP code. On success it either demonstrates command execution with whoami or launches a PowerShell reverse shell to an operator-supplied IP/port. This is a real exploitation path providing RCE. A second remote capability targets CVE-2025-14177 by generating malformed JPEG files and POSTing them to discovered upload endpoints using multipart form field file. Detection looks for a marker string or long printable output in responses; exploitation repeats the upload 10 times and stores raw responses and extracted strings under a reports subdirectory, aiming to capture leaked heap data. The remaining two modules, CVE-2025-14180 and CVE-2025-14178, are effectively local/RCE-follow-on checks and crash payloads rather than pure remote exploits. Both use php -r locally when PHP CLI is present; the exploit functions POST PHP snippets to a target URL if remote code execution is already available. CVE-2025-14180 attempts to trigger a PDO PostgreSQL null dereference using DSN pgsql:host=localhost;dbname=postgres with emulated prepares enabled. CVE-2025-14178 attempts an array_merge integer overflow by allocating extremely large arrays. Both are described as potentially crashing or destabilizing the PHP process. Overall, this is an operational multi-CVE web exploitation script, not just a detector. It supports single-target and batch modes, optional GNU parallel execution, report logging, and automatic exploitation unless scan-only is specified. Fingerprintable targets include common CGI paths, common upload paths, phpinfo.php probing, php://input injection, localhost PostgreSQL access, and attacker-defined reverse-shell callback endpoints.gl1tch0x1 · Disclosed Apr 29, 2026 · bash · markdown · web · network · localOperationalCVE-2025-14177Repository contains a single Python exploit generator (CVE-2025-14177.py) and a README. The Python script is a standalone proof-of-concept/operational exploit helper for CVE-2025-14177, a PHP getimagesize() heap memory disclosure issue caused by php_read_stream_all_chunks() overwriting buffer offsets during multi-chunk reads. Its main capability is generating a malicious JPEG with an oversized APP1 segment sized to exceed the 8KB chunk boundary, thereby modeling the vulnerable condition where later chunks overwrite earlier data and the returned APP1 metadata may contain uninitialized heap bytes. The script supports multiple modes (demo, gen, test, analyze, flow), writes artifacts into ./exploit_output/, simulates heap spray/leak behavior, analyzes leaked bytes for recognizable patterns, and emits JSON reports/test cases plus generated PHP helper code. No live exploitation against a hardcoded remote target is present; instead, the repository focuses on payload generation, simulation, and deployment guidance. Fingerprintable observables are mostly local artifact paths and PHP stream-wrapper strings, plus README examples of likely target-side endpoints such as php://filter resource paths, upload handling via $_FILES, and a sample /preview.php?url=attacker.com/malicious.jpg remote-fetch scenario.34zY · Disclosed May 18, 2026 · python · markdown · file · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PHP GroupPhpapplication
FAQ

Frequently asked questions

Is CVE-2025-14177 exploited in the wild?
As of Oct 25, 2026, Mallory has no reports of CVE-2025-14177 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-14177?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-14177, the earliest disclosed Apr 29, 2026.
Is there a patch for CVE-2025-14177?
Upgrade to PHP 8.1.34, 8.2.30, 8.3.29, 8.4.16, or 8.5.1 or later in the corresponding branch, or install a vendor package containing the backported fix. The fix advances the destination buffer pointer after each read so that chunks are appended correctly.
What products are affected by CVE-2025-14177?
PHP Group Php.
How severe is CVE-2025-14177?
CVE-2025-14177 has a CVSS v4 score of 6.3 (Medium) and an EPSS score of 0.50% (44th percentile) as of Oct 25, 2026.
Activity feed

Recent activity

25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity14Community discussion across Reddit, Mastodon, and other social sources.