LiveActive security incident?Get immediate response
CVE Record

CVE-2021-21823: An information disclosure vulnerability exists in the Friend finder functionality of GmbH Komoot version 10...

An information disclosure vulnerability exists in the Friend finder functionality of GmbH Komoot version 10.26.9 up to 11.1.11. A specially crafted series of network requests can lead to the disclosure of sensitive information.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-21823 is a privacy issue in Komoot’s friend finder. An unauthenticated network attacker could make crafted requests that disclose sensitive information. The sources rate it medium, with confidentiality impact only. It matters most where employees use affected Komoot mobile versions with personal or business-linked profile data.

Executive priority

Handle as a privacy and data-exposure cleanup item, not an emergency infrastructure incident. Prioritize if affected Komoot use exists among executives, field teams, or managed-device users with sensitive identity or contact data.

Technical view

The issue is CWE-359 information disclosure in Komoot friend finder, affecting versions 10.26.9 through 11.1.11 as listed. CVSS 3.0 is 5.3: network reachable, low complexity, no privileges or user interaction, confidentiality low, no integrity or availability impact.

Likely exposure

Exposure is limited to organizations with users running the affected Komoot versions, especially on managed devices or accounts tied to identifiable staff data. The source bundle does not identify server-side exposure, enterprise products, or non-Komoot affected software.

Exploitation context

The provided CVE data says specially crafted network requests can trigger disclosure. CISA KEV is false in the bundle, and no cited source here states active exploitation. Treat exploit status as unconfirmed rather than active.

Researcher notes

Evidence is narrow: one CVE record and Talos reference. The source bundle does not provide exploit details, fixed versions, or observed exploitation. Validation should focus on version presence, data sensitivity, and vendor remediation status.

Mitigation direction

  • Inventory managed devices for affected Komoot versions listed in the CVE.
  • Review Komoot or Talos guidance for a fixed release; sources do not name one.
  • Prioritize updates or removal through MDM where affected versions are present.
  • Review policies for personal apps handling contact or friend-discovery data on corporate devices.

Validation and detection

  • Confirm whether Komoot is installed on managed devices or approved app catalogs.
  • Check installed versions against 10.26.9, 11.0.14, and 11.1.11.
  • Determine whether users linked corporate identities, contacts, or visible profile data.
  • Record that KEV is false and active exploitation is not evidenced in provided sources.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-359: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2021-21823 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.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
2Source 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.0MediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.3Medium
CVSS 3.0 vector shape for CVE-2021-21823Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
n/aKomootKomoot GmbH Komoot 10.26.9 , Komoot GmbH Komoot 11.0.14 ,Komoot GmbH Komoot 11.1.11Listed
Weakness

CWE details

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

CWE-359 · source CWE mapping

Exposure of Private Personal Information to an Unauthorized Actor

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