Repository navigation
Conversation
…6-109413 composer audit on a fresh resolve picks symfony/yaml 5.0.x-dev via overtrue/phplint 2.4.1, which still carries 4 known advisories incl. CVE-2026-109413 (unbounded recursion in the YAML inline lexer) and CVE-2026-45304 (exponential memory allocation via recursive aliasing). Root cause of the old pin: phplint 2.4.1 requires symfony/console ^3.2|^4.0|^5.0 while symfony/console >=5.4 conflicts psr/log >=3 and symfony/yaml >=5.3 conflicts console <5.3, wedging the resolver. phplint 3.x requires PHP >=5.5.9 so the php ^7.3|^8.0 constraint is unchanged. With 'overtrue/phplint: ^3.0' and an explicit 'symfony/yaml: ^5.4' floor in require-dev, a fresh resolve lands console v5.3.16 and yaml v5.4.54 and 'composer audit' is clean. phplint src/ passes (7/7 files).
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.
Summary
A fresh
composer resolveof this repo's dev dependencies picks symfony/yaml 5.0.x-dev (throughovertrue/phplint2.4.1), which still carries 4 known advisories, notably:These are dev-tooling-only (phplint transitively pulls yaml; runtime deps are unaffected), but the dev tree runs
symfony/yamlon untrusted YAML on contributor machines, so the audit should be clean there too.Root cause of the old pin
overtrue/phplint2.4.1 requiressymfony/console ^3.2|^4.0|^5.0, but:symfony/yaml >=5.4conflicts withsymfony/console <5.3symfony/console >=5.4conflicts withpsr/log >=3…which wedges the resolver on console v5.2 + yaml 5.0.x-dev. phplint 3.x requires only
php >=5.5.9, so the repo'sphp: ^7.3|^8.0constraint is unchanged.Changes
overtrue/phplint:^2.3→^3.0symfony/yaml: explicit^5.4floor added torequire-devVerification (local resolve on this branch)
composer whychain unwinds: console v5.3.16 + yaml v5.4.54,composer audit→ cleanphplint src/passes (7/7 files)phpunitfailures unaffected: 49 errors / 7 failures on both this branch and pristinemaster(pre-existing PHPUnit 9 on PHP 8.5 issue, not touched by this dev-dep change)