---
id: GHSA-g2gw-q38m-vjfc
title: 'Lokka: Azure Resource Manager URL path validation issue'
summary: 'Lokka: Azure Resource Manager URL path validation issue'
severity: high
cwe:
  - CWE-918
vendor: merill
product: '@merill/lokka'
ecosystem: npm
affected:
  - '@merill/lokka < 2.1.2'
patched:
  - '@merill/lokka 2.1.2'
published: '2026-06-19'
updated: '2026-06-19'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-g2gw-q38m-vjfc'
references:
  - url: 'https://github.com/merill/lokka/security/advisories/GHSA-g2gw-q38m-vjfc'
  - url: 'https://github.com/advisories/GHSA-g2gw-q38m-vjfc'
tags:
  - ghsa
  - npm
ingestedAt: '2026-06-22T13:35:24.208Z'
---

## Overview

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>

## Affected packages

- `@merill/lokka < 2.1.2`

## Remediation

Upgrade to a patched release:

- `@merill/lokka 2.1.2`