{
  "@id": "urn:uuid:bc7e0223-ec9a-47c3-8ddb-51744bd286ab",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 2,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-10-13T17:27:06.546701+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.micrometer/micrometer-registry-wavefront@1.9.17-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.micrometer/micrometer-registry-wavefront@1.9.17-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-13T17:26:25.302027+00:00",
      "status_notes": "Vulnerability CVE-2026-40983 does not affect version 1.9.17-tuxcare.1 of io.micrometer:micrometer-registry-wavefront. Micrometer version 1.9.17 is NOT affected by CVE-2026-40983. The vulnerability requires the Observation API architecture (ObservationRegistry, DefaultMeterObservationHandler, ObservationGrpcServerInterceptor, DefaultGrpcServerObservationConvention) which was introduced in version 1.15.0. Version 1.9.17 uses a completely different gRPC instrumentation mechanism (MetricCollectingServerInterceptor) that does not extract or tag peer.name/peer.port values at all, making the metric cardinality explosion attack impossible. The CVE's version range stating \"older versions than 1.15.0 are not affected\" is accurate in this case.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-40983"
      },
      "impact_statement": "Micrometer version 1.9.17 is NOT affected by CVE-2026-40983. The vulnerability requires the Observation API architecture (ObservationRegistry, DefaultMeterObservationHandler, ObservationGrpcServerInterceptor, DefaultGrpcServerObservationConvention) which was introduced in version 1.15.0. Version 1.9.17 uses a completely different gRPC instrumentation mechanism (MetricCollectingServerInterceptor) that does not extract or tag peer.name/peer.port values at all, making the metric cardinality explosion attack impossible. The CVE's version range stating \"older versions than 1.15.0 are not affected\" is accurate in this case."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.micrometer/micrometer-registry-wavefront@1.9.17-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.micrometer/micrometer-registry-wavefront@1.9.17-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-13T17:26:25.302027+00:00",
      "status_notes": "Vulnerability CVE-2026-40984 affects version 1.9.17-tuxcare.1 of io.micrometer:micrometer-registry-wavefront.",
      "vulnerability": {
        "name": "CVE-2026-40984"
      },
      "action_statement": "Vulnerability CVE-2026-40984 affects version 1.9.17-tuxcare.1 of io.micrometer:micrometer-registry-wavefront."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/io.micrometer/micrometer-registry-wavefront@1.9.17-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.micrometer/micrometer-registry-wavefront@1.9.17-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-13T17:27:06.546701+00:00",
      "status_notes": "Vulnerability CVE-2026-59295 is fixed in version 1.9.17-tuxcare.1 of io.micrometer:micrometer-registry-wavefront.",
      "vulnerability": {
        "name": "CVE-2026-59295"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/io.micrometer/micrometer-registry-wavefront@1.9.17-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.micrometer/micrometer-registry-wavefront@1.9.17-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-13T17:27:06.546701+00:00",
      "status_notes": "Vulnerability CVE-2026-59296 is fixed in version 1.9.17-tuxcare.1 of io.micrometer:micrometer-registry-wavefront.",
      "vulnerability": {
        "name": "CVE-2026-59296"
      }
    }
  ]
}