GHSA-g2gw-q38m-vjfc: Lokka Remote Code Execution Vulnerability

HIGH
CWE-918
Published
Advisory Summary

GHSA-g2gw-q38m-vjfc is a HIGH remote code execution vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Lokka libraries in the npm ecosystem. The issue involves azure resource manager url path validation issue. Remediation is available by upgrading affected packages to version 2.1.2.

GHSA-g2gw-q38m-vjfc at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-g2gw-q38m-vjfc
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Lokka
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-g2gw-q38m-vjfc

To remediate this vulnerability, upgrade all affected Lokka dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@merill/lokka fixed: 2.1.2
npm install @merill/lokka@2.1.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @merill/lokka

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-g2gw-q38m-vjfc, inspect your project dependencies using npm:

npm ls @merill/lokka

Analyze the terminal output to locate any version of Lokka in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.1.2), your application is affected.

Note: The npm ls @merill/lokka command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Lokka, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Lokka versions prior to 2.1.2 constructed Azure Resource Manager request URLs using direct string concatenation with user-controlled path input. Specially crafted path values could alter URL authority parsing and cause Azure Resource Manager bearer tokens to be sent to an unintended host. Version 2.1.2 fixes the issue by validating Azure paths before token acquisition and constructing Azure Resource Manager URLs with the standard URL API while preserving the expected management.azure.com host. Reported by 정해창 <haechang__@naver.com>

GHSA-g2gw-q38m-vjfc Affected Lokka Versions

1 component(s)
Fixed Versions:
2.1.2
Product / Package Ecosystem Affected Versions Fixed Version
@merill/lokka
npm
< 2.1.2
2.1.2

References

Frequently Asked Questions

What is GHSA-g2gw-q38m-vjfc?
GHSA-g2gw-q38m-vjfc is a security vulnerability in Lokka involving Azure Resource Manager URL path validation issue under CWE-918: Server-Side Request Forgery (SSRF).
Which Lokka versions are affected?
Affected versions include releases prior to 2.1.2 across affected packages: @merill/lokka.
What version fixes GHSA-g2gw-q38m-vjfc?
Upgrading to 2.1.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @merill/lokka affected?
Yes, @merill/lokka is affected in releases prior to 2.1.2. Upgrade your dependency to 2.1.2 or later.
What CWE is associated with GHSA-g2gw-q38m-vjfc?
GHSA-g2gw-q38m-vjfc is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for GHSA-g2gw-q38m-vjfc?
Run the dependency tree command: 'npm ls @merill/lokka'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g2gw-q38m-vjfc",
  "modified" : "2026-06-19T22:10:39Z",
  "published" : "2026-06-19T22:10:39Z",
  "aliases" : [ ],
  "summary" : "Lokka: Azure Resource Manager URL path validation issue",
  "details" : "Lokka versions prior to 2.1.2 constructed Azure Resource Manager request URLs using direct string concatenation with user-controlled path input. Specially crafted path values could alter URL authority parsing and cause Azure Resource Manager bearer tokens to be sent to an unintended host. Version 2.1.2 fixes the issue by validating Azure paths before token acquisition and constructing Azure Resource Manager URLs with the standard URL API while preserving the expected management.azure.com host.\n\nReported by 정해창 <haechang__@naver.com>",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@merill/lokka"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.1.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/merill/lokka/security/advisories/GHSA-g2gw-q38m-vjfc"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/merill/lokka"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T22:10:39Z",
    "nvd_published_at" : null
  }
}