Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Automatic named constructor discovery in Valinor

GHSA-xhr8-mpwq-2rr2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (cuyz/valinor 0.7.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist cuyz/valinor

    Affected
    >= 0.5.0, < 0.7.0
    Fixed in
    0.7.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Design issue - automatic constructor discovery The issue arises when upgrading from cuyz/valinor:0.3.0 to a newer system on an existing application, which broke due to the wrong constructor being picked. Still, a bigger security concern is problematic, and it is akin to https://github.com/rails/rails/issues/5228. Example exploit Take following DTO example: There is nothing inherently unsafe about the above UserDTO, but when mixed with cuyz/valinor:^0.5.0 ( specifically https://github.com/CuyZ/Valinor/commit/718d3c1bc2ea7d28b4b1f6c062addcd1dde8660b ), it is an explosive mix: The above payload is represented in PHP form, but may as well be input JSON, HTML or x-form-urlencoded. Mitigation Version 0.7.0 contains a patch for this issue. Automatic named constructor resolution should be disabled - only explicitly mapped named constructors should be used/discovered.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xhr8-mpwq-2rr2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-xhr8-mpwq-2rr2

Advisory: Automatic named constructor discovery in Valinor
IDs: GHSA-xhr8-mpwq-2rr2
Record: https://patchnext.com/advisories/ghsa-xhr8-mpwq-2rr2 (revision 1, source checked 26 Oct 2026, 13:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: cuyz/valinor 0.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist cuyz/valinor: affected >= 0.5.0, < 0.7.0; fixed in 0.7.0

## Suggested inspection (read-only)
- Packagist cuyz/valinor: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on cuyz/valinor.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xhr8-mpwq-2rr2 (GitHub-reviewed advisory GHSA-xhr8-mpwq-2rr2 lists affected ranges: Packagist cuyz/valinor >=0.5.0 <0.7.0)

Commands are suggestions: review each one before running it.

Loading voting…