LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22251: wlc may leak API keys due to an insecure API key configuration

wlc is a Weblate command-line client using Weblate's REST API. Prior to 1.17.0, wlc supported providing unscoped API keys in the setting. This practice was discouraged for years, but the code was never removed. This might cause the API key to be leaked to different servers.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22251 affects wlc, Weblate’s command-line client. Versions before 1.17.0 allowed an old, discouraged configuration using unscoped API keys. In some use, that key might be sent or exposed to different servers. The main business risk is credential disclosure, not system takeover.

Executive priority

Treat as a targeted credential-exposure issue. Prioritize teams using Weblate automation or CI with wlc. Remediation should be straightforward: upgrade, remove legacy unscoped keys, and rotate potentially exposed credentials.

Technical view

wlc before 1.17.0 retained support for unscoped API keys in settings. The CVSS vector is local, high complexity, low privileges, user interaction required, changed scope, and high confidentiality impact. The issue is classified as CWE-200 information exposure and fixed by removing the insecure configuration path.

Likely exposure

Exposure is most likely on developer workstations, automation hosts, or CI systems running wlc below 1.17.0 with unscoped API keys configured. Organizations not using wlc, or using scoped tokens with current versions, are less likely affected.

Exploitation context

The provided sources do not show active exploitation, and this CVE is not marked KEV. Exploitation appears to require a specific local/user-driven configuration scenario. Successful abuse could expose a Weblate API key to an unintended server.

Researcher notes

Evidence is limited to the CVE record, GitHub advisory, pull request, and fixing commit. No cited source claims active exploitation. The key question for validation is whether vulnerable wlc versions were configured with unscoped API keys.

Mitigation direction

  • Upgrade wlc to version 1.17.0 or later.
  • Stop using unscoped API keys in wlc settings.
  • Review wlc configurations for legacy API key usage.
  • Rotate any API keys that may have been exposed.
  • Check the GitHub advisory for updated vendor guidance.

Validation and detection

  • Inventory systems and CI jobs using wlc.
  • Confirm installed wlc versions are 1.17.0 or later.
  • Review wlc settings for unscoped API keys.
  • Confirm API keys are scoped according to Weblate guidance.
  • Check logs for unexpected API key use if available.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22251 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N0.84Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-22251Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WeblateOrgwlc< 1.17.0Listed
Weakness

CWE details

CWE-200

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs