{
  "@id": "urn:uuid:d76404be-9193-4c87-80d2-aaff62449e41",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-10-16T19:26:00.107044+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.micrometer/micrometer-registry-stackdriver@1.12.12-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.micrometer/micrometer-registry-stackdriver@1.12.12-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-16T19:26:00.107044+00:00",
      "status_notes": "Vulnerability CVE-2026-40983 does not affect version 1.12.12-tuxcare.1 of io.micrometer:micrometer-registry-stackdriver. Micrometer v1.12.12 is NOT affected by CVE-2026-40983. The vulnerability requires PEER_NAME and PEER_PORT to be used in low-cardinality metric dimensions for gRPC server observations, causing unbounded metric creation when clients connect from different IPs/ports. In version 1.12.12, the PEER_NAME and PEER_PORT constants don't exist in GrpcObservationDocumentation.LowCardinalityKeyNames, and the GrpcServerObservationContext class lacks getPeerName()/getPeerPort() methods. The vulnerable code pattern was introduced in version 1.15.0 and fixed in 1.15.12/1.16.6. The CVE correctly states \"Older versions than 1.15.0 are not affected.\"",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-40983"
      },
      "impact_statement": "Micrometer v1.12.12 is NOT affected by CVE-2026-40983. The vulnerability requires PEER_NAME and PEER_PORT to be used in low-cardinality metric dimensions for gRPC server observations, causing unbounded metric creation when clients connect from different IPs/ports. In version 1.12.12, the PEER_NAME and PEER_PORT constants don't exist in GrpcObservationDocumentation.LowCardinalityKeyNames, and the GrpcServerObservationContext class lacks getPeerName()/getPeerPort() methods. The vulnerable code pattern was introduced in version 1.15.0 and fixed in 1.15.12/1.16.6. The CVE correctly states \"Older versions than 1.15.0 are not affected.\""
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/io.micrometer/micrometer-registry-stackdriver@1.12.12-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.micrometer/micrometer-registry-stackdriver@1.12.12-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-16T19:26:00.107044+00:00",
      "status_notes": "Vulnerability CVE-2026-40984 is fixed in version 1.12.12-tuxcare.1 of io.micrometer:micrometer-registry-stackdriver.",
      "vulnerability": {
        "name": "CVE-2026-40984"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/io.micrometer/micrometer-registry-stackdriver@1.12.12-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.micrometer/micrometer-registry-stackdriver@1.12.12-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-16T19:26:00.107044+00:00",
      "status_notes": "Vulnerability CVE-2026-59295 is fixed in version 1.12.12-tuxcare.1 of io.micrometer:micrometer-registry-stackdriver.",
      "vulnerability": {
        "name": "CVE-2026-59295"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/io.micrometer/micrometer-registry-stackdriver@1.12.12-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.micrometer/micrometer-registry-stackdriver@1.12.12-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-16T19:26:00.107044+00:00",
      "status_notes": "Vulnerability CVE-2026-59296 is fixed in version 1.12.12-tuxcare.1 of io.micrometer:micrometer-registry-stackdriver.",
      "vulnerability": {
        "name": "CVE-2026-59296"
      }
    }
  ]
}