fix(deps): update dependency typeorm to ^0.3.26 [security] - #26
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update dependency typeorm to ^0.3.26 [security]#26renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
October 31, 2025 22:27
2887857 to
37022f1
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
November 10, 2025 15:11
37022f1 to
02fa321
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
November 11, 2025 02:03
02fa321 to
573c41c
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
November 18, 2025 16:12
573c41c to
54be7e5
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
November 19, 2025 01:37
54be7e5 to
558ede7
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
December 3, 2025 17:46
558ede7 to
32ed9d1
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
December 3, 2025 20:59
32ed9d1 to
1742e01
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
December 30, 2025 14:42
1742e01 to
de53361
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
December 30, 2025 18:52
de53361 to
f17aca7
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
December 31, 2025 14:33
f17aca7 to
6101f9a
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
December 31, 2025 19:00
6101f9a to
415e26e
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
January 8, 2026 17:43
415e26e to
0365c35
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
January 8, 2026 23:09
0365c35 to
8c0f913
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
January 19, 2026 18:58
8c0f913 to
0235f3f
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
January 19, 2026 21:04
0235f3f to
b3af4cc
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
February 17, 2026 15:52
829c375 to
84a46d9
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
February 17, 2026 21:15
84a46d9 to
d192fd2
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
March 5, 2026 14:59
d192fd2 to
989c5d8
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
March 5, 2026 19:00
989c5d8 to
7de6a25
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
March 13, 2026 16:52
7de6a25 to
68e28ed
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
March 13, 2026 22:44
68e28ed to
eb31fa8
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
March 31, 2026 08:08
eb31fa8 to
793856e
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
March 31, 2026 13:09
793856e to
25af708
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
April 1, 2026 19:42
25af708 to
5916607
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
April 1, 2026 22:53
5916607 to
8c66144
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
April 8, 2026 20:41
8c66144 to
24a06a5
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
April 9, 2026 00:49
24a06a5 to
63eb20b
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
April 15, 2026 10:15
63eb20b to
0c09a70
Compare
renovate
Bot
force-pushed
the
renovate/npm-typeorm-vulnerability
branch
from
April 16, 2026 15:57
0c09a70 to
5dd5b00
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.2.32→^0.3.26Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
SQL injection in typeORM
CVE-2022-33171 / GHSA-fx4w-v43j-vc45
More information
Details
The findOne function in TypeORM before 0.3.0 can either be supplied with a string or a FindOneOptions object. When input to the function is a user-controlled parsed JSON object, supplying a crafted FindOneOptions instead of an id string leads to SQL injection. NOTE: the vendor's position is that the user's application is responsible for input validation.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
TypeORM vulnerable to SQL injection via crafted request to repository.save or repository.update
CVE-2025-60542 / GHSA-q2pj-6v73-8rgj
More information
Details
Summary
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.
Details
Vulnerable Code:
Intended Payload (non-malicious):
username=myusername&city=Riga&name=JavadOR
{username:\"myusername\",phone:12345,name:\"Javad\"}SQL query produced:
Malicious Payload:
username=myusername&city[name]=Riga&city[role]=adminOR
{username:\"myusername\",city:{name:\"Javad\",role:\"admin\"}}SQL query produced with Injected Column:
Above query is valid as
city=name=Javadis a boolean expression resulting incity= 1 (false). “role” column is injected and updated.Underlying issue was due to TypeORM using mysql2 without specifying a value for the stringifyObjects option. In both mysql and mysql2 this option defaults to false. This option is then passed into SQLString library as false. This results in sqlstring parsing objects in a strange way using objectToValues.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:L/SI:H/SA:L/E:PReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
typeorm/typeorm (typeorm)
v0.3.26Compare Source
Notes:
stringifyObjects: true, in order to avoid a potential security vulnerabilityin the mysql/mysql2 client libraries. You can revert to the old behavior by setting
connectionOptions.extra.stringifyObjects = false.@sap/hana-clientlibrary. The deprecatedhdb-poolis no longer necessary and can be removed. See https://typeorm.io/docs/drivers/sap/#data-source-options for the new pool options.
Bug Fixes
stringifyObjectsimplicitly (#11574) (d57fe3b)useIndexwhen cloning a QueryExpressionMap (or a QueryBuilder) (#10679) (66ee307), closes #10678 #10678Features
Performance Improvements
v0.3.25Compare Source
Bug Fixes
Features
v0.3.24Compare Source
Bug Fixes
Features
Performance Improvements
v0.3.23Compare Source
This release includes a technically breaking change (from this PR) in the behaviour of the
deleteandupdatemethods of the EntityManager and Repository APIs, when an empty object is supplied as the criteria:Empty criteria(s) are not allowed for the delete/update method.Why?
This behaviour was not documented and is considered dangerous as it can allow a badly-formed object (e.g. with an undefined id) to inadvertently delete or update the whole table.
When the intention actually was to delete or update all rows, such queries can be rewritten using the QueryBuilder API:
An alternative method for deleting all rows is to use:
Bug Fixes
aggregatemethod's generic type to its returned cursor (#10754) (56f1898)Features
Performance Improvements
v0.3.22Compare Source
Bug Fixes
Features
Reverts
v0.3.21Compare Source
Bug Fixes
reflect-metadatatopeerDependenciesand set version to"^0.1.14 || ^0.2.0"(#10779) (e7649d2)Performance Improvements
v0.3.20Compare Source
Bug Fixes
Features
Reverts
v0.3.19Compare Source
Bug Fixes
Cannot read properties of undefined (reading 'sync')caused after glob package upgradev0.3.18Compare Source
Bug Fixes
@VirtualColumn(#10432) (b53e410), closes #10431update: falsein persistence (#10250) (f8fa1fd), closes #10249date-fnsin favor ofDayJs(#10306) (cf7147f)Features
Performance Improvements
BREAKING CHANGES
See: https://github.com/mongodb/node-mongodb-native/blob/HEAD/etc/notes/CHANGES_6.0.0.md
| null,if all columns in your embed entity are nullable. Since database queries now return embedded property as
nullif all its column values are null.v0.3.17Compare Source
Bug Fixes
v0.3.16Compare Source
Bug Fixes
trustServerCertificateoption toSqlServerConnectionOptions(#9985) (0305805), closes #8093Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.