Heads up: this repo pins a PHP version affected by PHP2Shell (CVE-2026-109618 / CVE-2026-109619)
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Anfängerfreundlichkeit
- 35/100
Rechercherichtung
Start by inspecting the repository's Dockerfile and identify the PHP base image tag it uses. Check whether that version is affected by the advisories cited in the issue, then update to a patched release or document the vendor backport if the project must stay on an older version. Rebuild and verify the image uses the patched PHP version.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Hey, I ran a GitHub code search for Dockerfiles pinning an end-of-life PHP base image and your repo came up. You're getting this because of that.
What happened: On October 21 2026 the PHP project disclosed two critical unauthenticated remote-code-execution flaws in PHP core, together nicknamed "PHP2Shell" (CVE-2026-109618 and CVE-2026-109619, both CVSS 9.2). They affect every PHP build before 8.2.35, 8.3.36, 8.4.27 and 8.5.12. PHP 8.1 and older are end-of-life and get no official fix, only source backports for 7.4 / 8.0 / 8.1. The FBI and CISA have both urged operators to patch immediately or take affected systems offline.
Why this repo
Your repo has a Dockerfile building on a web-serving PHP image (php:…-apache or php:…-fpm) for a release below the patch line (7.2–8.1). Those tags get no official PHP fix, so the image serves web requests on a vulnerable PHP unless you upgrade or apply the backport. mod_php, the -apache image, is the configuration the advisory rates highest-risk.
Checklist
- Move the base image to a patched release:
php:8.2.35,php:8.3.36,php:8.4.27orphp:8.5.12(or newer). - If you must stay on 7.4 / 8.0 / 8.1, apply the PHP security team's source backport, or get a patched package from your distro / LTS vendor.
- Rebuild and redeploy. A rebuild alone does not help if the tag is still below the patch line.
- If you can't patch right away, the FBI and CISA both say to take the system offline until it's fixed.
- Watch your web servers: a PHP worker process unexpectedly launching a shell or downloading files is the thing to look for.
- If you find signs of compromise, isolate the box, preserve your web-server and PHP logs, and report it to your local FBI field office or https://www.ic3.gov.
If you can't update immediately
These reduce exposure to specific attack paths. They are not a fix; only an update is.
- Enforce
memory_limit=-1administratively (FPM pool or Apache config) so an application can't put a finite limit back. - Set
session.upload_progress.enabled=0and restart every worker. - On PHP 8.5, set
fatal_error_backtraces=0and restart every worker. - Keep
post_max_sizeconservative and bound multipart part / header counts at your proxy.
References
- FBI Cyber Division advisory
- PHP security advisory, 21 Oct 2026
- CVE-2026-109618, RCE via OOM corruption
- CVE-2026-109619, RCE via stale global state
- CISA alert
- CERT-EU advisory 2026-018
Disclaimer
This is informational only and not professional security advice. I ran a search and wanted affected maintainers to hear about it. If this is a false positive, a library, an example, a test fixture, an archived project, or an image that already carries a distro backport, sorry for the noise, feel free to close.
- Vorherrschende Sprache
- PHP
- Sterne
- 194
- Forks
- 104
- Ø Merge
- 20 Std. 28 Min.
- Gemergte PRs (30 T.)
- 3
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus nextcloud/nextcloud-docker-dev
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
nextcloud/nextcloud-docker-dev#483 · 1 Kommentar · 3 Reaktionen ·
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
nextcloud/nextcloud-docker-dev#480 · 1 Kommentar ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
enhancement
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 55/100
-
bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 55/100
Alle Issues in nextcloud/nextcloud-docker-dev
Ähnliche Issues
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 1 Tag
-
0. Needs triage bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
nextcloud/fulltextsearch#1061 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Resource]: Claude KitOffenresource-submission validation-passed
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
hesreallyhim/awesome-claude-code#3375 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
C-CDA export: allergy concern act code, policy activity translation and empty id/@extension fail conformanceEvtl. vergeben @doctorman hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100