Skip to content
Noroxi
CVE-2020-15366· NVD / CVE Program· CNA mitre

An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2.

An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)

MediumCVSS 5.6 · v3.1—No exploit Fix available
Published
Jul 15, 2020
Updated
Jun 16, 2026
EPSS
2.3% · 83th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
22 / 40 · 5.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.3%

Affected systems

VendorProduct
ajv.jsajv

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • ajv.js ajv6.12.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8nodejs-nodemonbefore 2.0.3-1.module_el8.4.0+2521+c668cc9f2.0.3-1.module_el8.4.0+2521+c668cc9f
AlmaLinux:8nodejs-nodemonbefore 1.18.3-1.module_el8.3.0+2023+d2377ea31.18.3-1.module_el8.3.0+2023+d2377ea3
AlmaLinux:8nodejs-nodemonbefore 1.18.3-1.module_el8.3.0+2047+b07ac28e1.18.3-1.module_el8.3.0+2047+b07ac28e
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.4.0+2521+c668cc9f17-3.module_el8.4.0+2521+c668cc9f
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.4.0+2224+b07ac28e17-3.module_el8.4.0+2224+b07ac28e
AlmaLinux:8nodejs-packagingbefore 23-3.module_el8.5.0+254+b4526b1623-3.module_el8.5.0+254+b4526b16
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.3.0+2023+d2377ea317-3.module_el8.3.0+2023+d2377ea3
AlmaLinux:8nodejs-packagingbefore 23-3.module_el8.4.0+2522+3bd4276223-3.module_el8.4.0+2522+3bd42762
Debian:12node-ajvbefore 6.12.4-16.12.4-1
npmajvbefore 6.12.36.12.3
Red Hat:ansible_automation_platform:4.2::el7automation-hubbefore 0:4.2.2-1.el7pc0:4.2.2-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python-bleachbefore 0:3.3.0-1.el7pc0:3.3.0-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python-bleach-allowlistbefore 0:1.0.3-1.el7pc0:1.0.3-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python-galaxy-importerbefore 0:0.2.15-1.el7pc0:0.2.15-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python-galaxy-ngbefore 0:4.2.2-1.el7pc0:4.2.2-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python-pulp-ansiblebefore 1:0.5.6-1.el7pc1:0.5.6-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python3-bleachbefore 0:3.3.0-1.el7pc0:3.3.0-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python3-bleach-allowlistbefore 0:1.0.3-1.el7pc0:1.0.3-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python3-djangobefore 0:2.2.18-1.el7pc0:2.2.18-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python3-galaxy-importerbefore 0:0.2.15-1.el7pc0:0.2.15-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python3-galaxy-ngbefore 0:4.2.2-1.el7pc0:4.2.2-1.el7pc
Red Hat:ansible_automation_platform:4.2::el7python3-pulp-ansiblebefore 1:0.5.6-1.el7pc1:0.5.6-1.el7pc
Red Hat:ansible_automation_platform:4.2::el8automation-hubbefore 0:4.2.2-1.el8pc0:4.2.2-1.el8pc
Red Hat:ansible_automation_platform:4.2::el8python-bleachbefore 0:3.3.0-1.el8pc0:3.3.0-1.el8pc

+60

Other highest-scoring records for the same primary product.

  • CVE-2025-69873ajv (Another JSON Schema Validator) before 8.18.0 is vulnerable to Regular Expression Denial of Service (ReDoS) when the $data option is ena
    11Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:nodejs-nodemon1.18.3-1.module_el8.3.0+2023+d2377ea3 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging17-3.module_el8.4.0+2224+b07ac28e · AlmaLinux:8Package registry (OSV)
debian:node-ajv6.12.4-1 · Debian:12Package registry (OSV)
npm:ajv6.12.3Package registry (OSV)
red hat:nodejs1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-debuginfo1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-debugsource1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-devel1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-docs1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-full-i18n1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:nodejs-nodemon0:1.18.3-1.module+el8.1.0+3369+37ae6a45 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:rh-nodejs12-nodejs0:12.19.1-2.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-debuginfo0:12.19.1-2.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-devel0:12.19.1-2.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-docs0:12.19.1-2.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-npm0:6.14.8-12.19.1.2.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
rocky linux:nodejs-nodemon0:1.18.3-1.module+el8.3.0+101+f84c7154 · Rocky Linux:8Package registry (OSV)
rocky linux:nodejs-packaging0:17-3.module+el8.3.0+101+f84c7154 · Rocky Linux:8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

CVSS vector

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

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records