Possible prototype pollution in metadata record, when using meta decorator

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2023-30857: 0.48% estimated exploitation activity in the next 30 days; percentile 41.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Possible prototype pollution for the MetadataRecord, when merged with a base class' metadata object, in meta decorator from the @aedart/support package. The likelihood is questionable, given that a class' metadata can only be set or altered when the class is decorated via meta(). Furthermore, object(s) of sensitive nature would have to be stored as metadata, before this can become a vulnerability. Patches Has been patched in version 0.6.1.

Published by the source

1 May 2023, 14:01 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wwxh-74fx-33c6

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wwxh-74fx-33c6

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

# Patch Next advisory brief: CVE-2023-30857

Advisory: Possible prototype pollution in metadata record, when using meta decorator
IDs: CVE-2023-30857, GHSA-wwxh-74fx-33c6
Record: https://patchnext.com/advisories/cve-2023-30857 (revision 2, source checked 26 Oct 2026, 12:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @aedart/support 0.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @aedart/support: affected < 0.6.1; fixed in 0.6.1

## Suggested inspection (read-only)
- `npm ls @aedart/support --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 @aedart/support.
- 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://osv.dev/vulnerability/GHSA-wwxh-74fx-33c6 (OSV record GHSA-wwxh-74fx-33c6 lists affected ranges: npm @aedart/support >=0 <0.6.1 (fixed))
- Verified: https://github.com/advisories/GHSA-wwxh-74fx-33c6 (GitHub-reviewed advisory GHSA-wwxh-74fx-33c6 lists affected ranges: npm @aedart/support >=0 <0.6.1)

Commands are suggestions: review each one before running it.