Skip to content

The YAML parser is the one the advisory is about - #26

Merged
fabeat merged 1 commit into
mainfrom
fix/yaml-advisory
Nov 5, 2026
Merged

fabeat merged 1 commit into
mainfrom
fix/yaml-advisory

Conversation

@fabeat

@fabeat fabeat commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

The lock holds symfony/yaml v8.1.9, and an advisory published today covers it:

Exponential and Quadratic Parse Times in the YAML Parser Let a Single Document
Hold a Process — GHSA-hwfg-qwvh-2wfx, PKSA-nktx-f1n1-b4yd

The affected versions are >=8.1.0,<8.1.11, so v8.1.11 is the one the advisory stops
at, and it is the newest version on the line the lock is on.

The second change in the lock is the directives package's path reference, which moves
from ffcda3d to 1044638 — the merge commit of the 0.3.1 release. The lock recorded
the release branch's commit; the pipeline checks out main, so the lock now says what
the pipeline installs.

The phpunit advisory is left alone. phpunit/phpunit v13.4.3 is covered by
CVE-2026-119193, which v13.4.4 fixes — but pest v5.3.3 conflicts with phpunit 13.4.4,
so the fix drags a test framework upgrade into a lock file. That advisory is from the
27th of October, it affects the development dependencies only, and it is not what this
change is about.

The site builds, the suite passes (126 tests), and every address on every page still
resolves.

@sonarqubecloud

sonarqubecloud Bot commented Nov 4, 2026

Copy link
Copy Markdown

@fabeat
fabeat merged commit 53af3dc into main Nov 5, 2026
3 checks passed
@fabeat
fabeat deleted the fix/yaml-advisory branch November 5, 2026 08:28
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