Repository navigation
fix: consume vendor-maintained legacy PHP security backports - #56
Closed
carlalexander wants to merge 2 commits into
Closed
carlalexander wants to merge 2 commits into
carlalexander wants to merge 2 commits into
Conversation
Apply pinned CVE-2026-109618 and CVE-2026-109619 source backports for PHP 7.2 through 8.1, including the pristine-source prerequisites. Add bounded image regressions and non-publishing PR verification. Refs YMIR-127. No release or layer catalog changes.
Replace Ymir-maintained patches with pinned PHP-team snapshots and complete Sury source packages prepared by dpkg-source. Preserve AL2023 execution and Lambda defaults without vendor source edits.\n\nVerify the separately fetched upstream PEAR bootstrap before installation and test native session defaults in final images.
carlalexander
deleted the
carlalexander/ymir-127-legacy-php-security-backports
branch
October 25, 2026 16:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vendor-source replacement — ready for Carl's review
Remediates CVE-2026-109618 / CVE-2026-109619 using complete vendor-maintained sources, not a Ymir patch set. Commit
d90b7fdreplaces the rejected206aa1barchitecture on the same branch.No merge, release/tag, image/layer publishing, platform catalog update, or production rollout is authorized.
Implementation
dpkg-sourcewith all 159/139 vendor patches, unchanged. Debian is build-only source preparation; compilation and final runtime remain AL2023.runtime/patches/entirely. No selected prerequisites, vendor C/header/script edits, fake tooling, or OS/ABI migration.phpizeuses its pathname fallback against native AL2023 helper files; future non-path Debian-tool dependencies require reevaluation, not stubs.Source identities, provenance limitations and compatibility details:
runtime/sources/README.md.Verification
runtime/test-image.sh, including modules, extension files, TLS, startup, size and all seven legacy regression groups (105–111MB).d90b7fd: 18-image matrix, PR quality/unit matrix, push quality/unit matrix. Every image built and verified; all publication steps were skipped. One isolated PHP 8.4 x86_64 rerun cleared a stale pending check after its original verification passed; no code changes. Historical green checks on206aa1bare not substituted.Compatibility and release boundary
Vendor mitigations immediately terminate PHP on OOM (exit 1, bypassing shutdown callbacks/destructors), disable session upload-progress tracking and change multipart handling. Do not add automatic application retries that could repeat side effects. These remain EOL versions; focused regressions are not comprehensive exploit/CVE coverage or a support guarantee.
No full amd64 image was built locally; both architectures and all supported PHP selectors are CI gates. Exported ZIP artifacts, live Lambda cold/warm invocations, release permissions/catalog parity and customer rollout require later, explicit authorization. Existing deployments are not patched retroactively; zip deployments need redeployment, and container deployments need base-image rebuild/redeployment, including pinned digests. Preserve recovery artifacts, but rollback to unpatched runtimes restores exposure.
Refs YMIR-127.