Skip to main content
No exploitation reportedFix available

CVE-2025-60542

No exploitation reported by the sources we read.

  • Published2025-10-29
  • Fixed in0.3.26
  • WeaknessCWE-89

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

SQL Injection vulnerability in TypeORM before 0.3.26 via crafted request to repository.save or repository.update due to the sqlstring call using stringifyObjects default to false.

Timeline

dates in UTC
  1. 2025-10-2916:15CVE publishedNVD

Versions per branch

OSV
typeorm
BranchAffectedFixed in
0.3< 0.3.260.3.26

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • @rootio/typeormRoot:npmall versions · fixed in 0.3.19-root.io.1
  • redisinsightChainguardall versions · fixed in 2.70.1-r3and 1 other package
  • typeormRoot:npmall versions · fixed in 0.3.19-aikido.1

Vendor advisories

  • CVE-2025-60542 Red Hat Product Security2 products fixed

    TypeORM: SQL Injection via crafted request to repository.save or repository.update

  • RHSA-2025:22861 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat Developer Hub 1.8.1 release.

  • RHSA-2025:22404 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat Developer Hub 1.7.3 release.

Full record on NVD

Fix

  1. Update typeorm to 0.3.26
  2. Vendor fix Red Hat Product Security RHSA-2025:22861 · 1 productFor more about Red Hat Developer Hub, see References links
  3. Workaround from the vendor Red Hat Product Security RHSA-2025:22861 · 3 productsRed Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Published
2025-10-29
Last Modified
2026-10-27
NVD status
Deferred
GitHub Advisory
GHSA-q2pj-6v73-8rgj

Frequently asked questions

What is CVE-2025-60542?

SQL Injection vulnerability in TypeORM before 0.3.26 via crafted request to repository.save or repository.update due to the sqlstring call using stringifyObjects default to false.

Is CVE-2025-60542 actively exploited?

Active exploitation of CVE-2025-60542 has not been confirmed. Its EPSS score was 0.3% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-60542?

CVE-2025-60542 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N.

Running typeorm? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record