Skip to content

fix(deps): require patched Symfony security dependencies - #12

Merged
brianvarskonst merged 1 commit into
mainfrom
fix/symfony-security-20261016
Oct 16, 2026
Merged

brianvarskonst merged 1 commit into
mainfrom
fix/symfony-security-20261016

Conversation

@brianvarskonst

@brianvarskonst brianvarskonst commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

Require HttpFoundation 8.1.9 and the patched Kernel 1.1.10 / Framework Bundle 1.0.7 releases, so fresh and lowest-version installations exclude the vulnerable ExpressionLanguage, YAML and HttpFoundation ranges. The WordPress integration fixture explicitly requires YAML 8.1.6 or newer. Prepare patch release 1.2.3.

The regression tests exercise Cache-Control parsing after long whitespace runs and retain support for spaces and tabs as header separators. The whitespace-separator regression is reproduced with HttpFoundation 8.1.8 and passes on 8.1.9.

Validation: full package QA passes with latest dependencies and with the critical runtime minima (ExpressionLanguage/HttpFoundation 8.1.9, YAML 8.1.6): 40 tests, 143 assertions in each run. Composer strict validation and audit including development packages pass. Composer's native Semver matcher rejects the previous unsafe dependency floors while accepting the patched versions. The WordPress fixture resolves and audits cleanly with latest and lowest dependencies; the real WordPress integration passes its 22 lazy-loop/block checks, 27 feature checks and template/admin/escaping checks with both runtime sets in a new disposable database, rebuilding its container cache for the minimum run.

Lowest runtime QA uses compatible current development tools. The completely oldest development stack has pre-existing PHPStan optional-ACF reflection failures and old Patchwork/Mockery PHP 8.5 incompatibilities; no source workaround or test suppression was introduced. PHPUnit 10 reports four existing deprecations, and WP-CLI reports its existing PHP 8.5 deprecations. The non-publishable WordPress fixture retains its intentional @dev source dependency, so Composer validation reports the existing unbound-version warning.

Upstream advisories: ExpressionLanguage CVE-2026-109449, YAML CVE-2026-109413, HttpFoundation CVE-2026-108082. No public ExpressionLanguage or YAML attack input is asserted by this dependency update.

@brianvarskonst brianvarskonst left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Independently reviewed 261bd76bcf318f9aa4b224d3117eb562ed088871 against current origin/main. No blocking findings in the four changed files.

The HttpFoundation 8.1.9 floor excludes the vulnerable versions and the whitespace-separator regression. Kernel 1.1.10 and Framework Bundle 1.0.7 carry safe ExpressionLanguage/YAML minima into lowest-version resolution; the integration fixture also declares YAML 8.1.6 directly. The functional header tests cover both the long-whitespace security case and the space/tab separator correction; the latter fails on the previous 8.1.8 implementation.

Highest package QA, strict validation, development-inclusive audit and real WordPress integration pass. All four hosted checks pass on this exact SHA. Lowest resolution and audits preserve the targeted security floors. The oldest analysis/mock tooling has separate PHP 8.5 incompatibilities; those are recorded and checked with current development tools while retaining runtime minima. No production logic or audit/test gate is changed.

@brianvarskonst
brianvarskonst merged commit 148c3d6 into main Oct 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant