CVE-2026-39310

{
  "id": "CVE-2026-39310",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-39310",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2026-05-21T12:51:29.010426Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 8.6,
          "attackVector": "NETWORK",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "LOW",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "LOW"
        },
        "impactScore": 4.7,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "TriliumNext",
          "product": "Trilium",
          "versions": [
            {
              "status": "affected",
              "version": "< 0.102.2"
            }
          ]
        }
      ]
    }
  ],
  "published": "2026-05-20T20:16:39.213",
  "references": [
    {
      "url": "https://github.com/TriliumNext/Trilium/releases/tag/v0.102.2",
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/TriliumNext/Trilium/security/advisories/GHSA-jcvx-vc83-cppw",
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/TriliumNext/Trilium/security/advisories/GHSA-jcvx-vc83-cppw",
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
    }
  ],
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-284"
        },
        {
          "lang": "en",
          "value": "CWE-306"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Trilium Notes is a cross-platform, hierarchical note taking application focused on building large personal knowledge bases. In versions 0.102.1 and prior, the Clipper API in Trilium Desktop (v0.101.3) allows full authentication bypass when running in an Electron environment. When Trilium detects an Electron environment, it explicitly disables authentication middleware for the Clipper API, exposing endpoints such as /api/clipper/notes to the network with no password, API token, or CSRF protection. An attacker on a shared network (for example, a corporate LAN or public Wi-Fi) can scan for open high-range ports using a tool like nmap, since Trilium often binds to ports such as 37840. Once a candidate port is found, an unauthenticated request to the Clipper handshake endpoint, which also bypasses authentication, confirms a Trilium instance by returning the application name and protocol version. This facilitates unauthorized data access, phishing, and local system compromise. The issue has been fixed in version 0.102.2."
    },
    {
      "lang": "es",
      "value": "Trilium Notes es una aplicación de toma de notas jerárquica y multiplataforma centrada en la construcción de grandes bases de conocimiento personales. En las versiones 0.102.1 y anteriores, la API Clipper en Trilium Desktop (v0.101.3) permite una omisión completa de la autenticación cuando se ejecuta en un entorno Electron. Cuando Trilium detecta un entorno Electron, deshabilita explícitamente el middleware de autenticación para la API Clipper, exponiendo puntos finales como /api/clipper/notes a la red sin contraseña, token de API o protección CSRF. Un atacante en una red compartida (por ejemplo, una LAN corporativa o Wi-Fi pública) puede escanear en busca de puertos abiertos de alto rango utilizando una herramienta como nmap, ya que Trilium a menudo se enlaza a puertos como el 37840. Una vez que se encuentra un puerto candidato, una solicitud no autenticada al punto final de handshake de Clipper, que también omite la autenticación, confirma una instancia de Trilium al devolver el nombre de la aplicación y la versión del protocolo. Esto facilita el acceso no autorizado a datos, el phishing y el compromiso del sistema local. El problema ha sido solucionado en la versión 0.102.2."
    }
  ],
  "lastModified": "2026-07-23T12:10:00.110",
  "sourceIdentifier": "security-advisories@github.com"
}