{
  "affected": [
    {
      "ecosystem_specific": {
        "fix": null,
        "range_state": "affected",
        "resource": "concurrent-ruby",
        "resource_purl": "pkg:gem/concurrent-ruby@1.2.3",
        "upstream_fixed_in": "1.3.7"
      },
      "package": {
        "ecosystem": "Homebrew",
        "name": "asciidoctor",
        "purl": "pkg:brew/asciidoctor"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "confidence": "high",
    "source": "matched",
    "strategy": "registry",
    "upstream_evidence": [
      {
        "ecosystem": "RubyGems",
        "key": "pkg:gem/concurrent-ruby@1.2.3",
        "name": "concurrent-ruby",
        "resource": "concurrent-ruby",
        "strategy": "registry",
        "subject_version": "1.2.3"
      }
    ]
  },
  "details": "### Summary\n`Concurrent::ReadWriteLock#release_write_lock` does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can then enter its critical section while the first writer is still running.\n\n`Concurrent::ReadWriteLock#release_read_lock` also decrements the shared counter even when no read lock is held. Calling it on a fresh lock changes the counter from `0` to `-1`, after which normal read acquisition raises `Concurrent::ResourceLimitError`.\n\nThis is a synchronization correctness issue in the public `Concurrent::ReadWriteLock` API. It should not be framed as an authorization bypass; the lock is an in-process concurrency primitive, not an access-control boundary.\n\n###  Version\nSoftware: concurrent-ruby\nVersion: 1.3.6\nCommit: 7a1b78941c081106c20a9ca0144ac73a48d254ab\n\n### Details\n\n`release_write_lock` checks only whether the global counter indicates that a writer is running. It does not track or verify ownership:\n\n```ruby\ndef release_write_lock\n  return true unless running_writer?\n  c = @Counter.update { |counter| counter - RUNNING_WRITER }\n  @ReadLock.broadcast\n  @WriteLock.signal if waiting_writers(c) \u003e 0\n  true\nend\n```\n\nBecause ownership is not checked, a different thread can clear the `RUNNING_WRITER` bit while the original writer is still inside its critical section. Another writer can then acquire the write lock and run concurrently with the first writer.\n\n`release_read_lock` unconditionally decrements the shared counter:\n\n```ruby\ndef release_read_lock\n  while true\n    c = @Counter.value\n    if @Counter.compare_and_set(c, c-1)\n      if waiting_writer?(c) \u0026\u0026 running_readers(c) == 1\n        @WriteLock.signal\n      end\n      break\n    end\n  end\n  true\nend\n```\n\nOn a fresh lock, this changes the counter from `0` to `-1`. A later `acquire_read_lock` raises `Concurrent::ResourceLimitError` because the maximum-reader check masks the negative counter as saturated.\n\n# Reproduce\n\nFrom the root of a `concurrent-ruby` checkout, run:\n\n```bash\nruby -Ilib/concurrent-ruby - \u003c\u003c\u0027RUBY\u0027\nrequire \u0027concurrent/atomic/read_write_lock\u0027\nrequire \u0027concurrent/version\u0027\nrequire \u0027thread\u0027\n\nputs \"ruby=#{RUBY_DESCRIPTION}\"\nputs \"concurrent_ruby_version=#{Concurrent::VERSION}\"\nputs \"poc=ReadWriteLock release methods corrupt or bypass lock state\"\n\nlock = Concurrent::ReadWriteLock.new\nevents = Queue.new\nwriter1_inside = false\n\nwriter1 = Thread.new do\n  lock.acquire_write_lock\n  writer1_inside = true\n  events \u003c\u003c :writer1_acquired\n  sleep 0.5\n  writer1_inside = false\n  lock.release_write_lock\n  events \u003c\u003c :writer1_finished\nend\n\nevents.pop\nputs \u0027writer1_acquired=true\u0027\n\nintruder_result = nil\nintruder = Thread.new do\n  intruder_result = lock.release_write_lock\nend\nintruder.join\n\nputs \"wrong_thread_release_write_lock_returned=#{intruder_result}\"\n\nwriter2_entered_while_writer1_inside = nil\nwriter2 = Thread.new do\n  lock.acquire_write_lock\n  writer2_entered_while_writer1_inside = writer1_inside\n  lock.release_write_lock\nend\n\nwriter2.join(0.25)\n\nputs \"writer2_acquired_while_writer1_inside=#{writer2_entered_while_writer1_inside}\"\n\nwriter1.join\n\nlock2 = Concurrent::ReadWriteLock.new\nstray_read_release_result = lock2.release_read_lock\ncounter_after_stray_read_release = lock2.instance_eval { @Counter.value }\nread_after_stray_release = begin\n  lock2.acquire_read_lock\n  \u0027acquired\u0027\nrescue =\u003e error\n  \"#{error.class}: #{error.message}\"\nend\n\nputs \"stray_release_read_lock_returned=#{stray_read_release_result}\"\nputs \"counter_after_stray_read_release=#{counter_after_stray_read_release}\"\nputs \"acquire_read_after_stray_release=#{read_after_stray_release}\"\n\nif intruder_result \u0026\u0026 writer2_entered_while_writer1_inside \u0026\u0026 counter_after_stray_read_release == -1\n  puts \u0027result=REPRODUCED wrong-thread write release and stray read-release corruption\u0027\nelse\n  puts \u0027result=NOT_REPRODUCED\u0027\nend\n```\nExpected result:\n\n- A second thread successfully calls `release_write_lock` while the first writer still holds the lock.\n- A second writer enters while the first writer is still inside the write critical section.\n- Calling `release_read_lock` on a fresh lock changes the counter to `-1`.\n- A subsequent read acquisition fails with `Concurrent::ResourceLimitError`.\n\n### Log evidence\n\nLocal reproduction output:\n\n```text\nruby=ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.arm64e-darwin25]\nconcurrent_ruby_version=1.3.6\npoc=ReadWriteLock release methods corrupt or bypass lock state\nwriter1_acquired=true\nwrong_thread_release_write_lock_returned=true\nwriter2_acquired_while_writer1_inside=true\nstray_release_read_lock_returned=true\ncounter_after_stray_read_release=-1\nacquire_read_after_stray_release=Concurrent::ResourceLimitError: Too many reader threads\nresult=REPRODUCED wrong-thread write release and stray read-release corruption\n```\n\n### Impact\nThis can break the write-lock mutual exclusion guarantee and can also leave a lock unusable after a stray read release.\nThe impact is local to applications that expose or misuse the manual `acquire_*` / `release_*` APIs. If the lock protects integrity-sensitive mutable state, wrong-thread write release can allow concurrent writers and data races. The stray read-release path can cause denial of service by corrupting the lock counter.\n\n### Credit\nPranjali Thakur - depthfirst ([depthfirst.com](\u003chttp://depthfirst.com\u003e))",
  "id": "BREW-asciidoctor-CVE-2026-54906",
  "modified": "2026-08-13T16:36:07Z",
  "published": "2026-08-13T16:36:07Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-6wx8-w4f5-wwcr"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Concurrent Ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption",
  "upstream": [
    "GHSA-6wx8-w4f5-wwcr",
    "CVE-2026-54906"
  ]
}

{
  "affected": [
    {
      "ecosystem_specific": {
        "fix": null,
        "range_state": "affected",
        "resource": "concurrent-ruby",
        "resource_purl": "pkg:gem/concurrent-ruby@1.3.6",
        "upstream_fixed_in": "1.3.7"
      },
      "package": {
        "ecosystem": "Homebrew",
        "name": "imap-backup",
        "purl": "pkg:brew/imap-backup"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "confidence": "high",
    "source": "matched",
    "strategy": "registry",
    "upstream_evidence": [
      {
        "ecosystem": "RubyGems",
        "key": "pkg:gem/concurrent-ruby@1.3.6",
        "name": "concurrent-ruby",
        "resource": "concurrent-ruby",
        "strategy": "registry",
        "subject_version": "1.3.6"
      }
    ]
  },
  "details": "### Summary\n`Concurrent::ReadWriteLock#release_write_lock` does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can then enter its critical section while the first writer is still running.\n\n`Concurrent::ReadWriteLock#release_read_lock` also decrements the shared counter even when no read lock is held. Calling it on a fresh lock changes the counter from `0` to `-1`, after which normal read acquisition raises `Concurrent::ResourceLimitError`.\n\nThis is a synchronization correctness issue in the public `Concurrent::ReadWriteLock` API. It should not be framed as an authorization bypass; the lock is an in-process concurrency primitive, not an access-control boundary.\n\n###  Version\nSoftware: concurrent-ruby\nVersion: 1.3.6\nCommit: 7a1b78941c081106c20a9ca0144ac73a48d254ab\n\n### Details\n\n`release_write_lock` checks only whether the global counter indicates that a writer is running. It does not track or verify ownership:\n\n```ruby\ndef release_write_lock\n  return true unless running_writer?\n  c = @Counter.update { |counter| counter - RUNNING_WRITER }\n  @ReadLock.broadcast\n  @WriteLock.signal if waiting_writers(c) \u003e 0\n  true\nend\n```\n\nBecause ownership is not checked, a different thread can clear the `RUNNING_WRITER` bit while the original writer is still inside its critical section. Another writer can then acquire the write lock and run concurrently with the first writer.\n\n`release_read_lock` unconditionally decrements the shared counter:\n\n```ruby\ndef release_read_lock\n  while true\n    c = @Counter.value\n    if @Counter.compare_and_set(c, c-1)\n      if waiting_writer?(c) \u0026\u0026 running_readers(c) == 1\n        @WriteLock.signal\n      end\n      break\n    end\n  end\n  true\nend\n```\n\nOn a fresh lock, this changes the counter from `0` to `-1`. A later `acquire_read_lock` raises `Concurrent::ResourceLimitError` because the maximum-reader check masks the negative counter as saturated.\n\n# Reproduce\n\nFrom the root of a `concurrent-ruby` checkout, run:\n\n```bash\nruby -Ilib/concurrent-ruby - \u003c\u003c\u0027RUBY\u0027\nrequire \u0027concurrent/atomic/read_write_lock\u0027\nrequire \u0027concurrent/version\u0027\nrequire \u0027thread\u0027\n\nputs \"ruby=#{RUBY_DESCRIPTION}\"\nputs \"concurrent_ruby_version=#{Concurrent::VERSION}\"\nputs \"poc=ReadWriteLock release methods corrupt or bypass lock state\"\n\nlock = Concurrent::ReadWriteLock.new\nevents = Queue.new\nwriter1_inside = false\n\nwriter1 = Thread.new do\n  lock.acquire_write_lock\n  writer1_inside = true\n  events \u003c\u003c :writer1_acquired\n  sleep 0.5\n  writer1_inside = false\n  lock.release_write_lock\n  events \u003c\u003c :writer1_finished\nend\n\nevents.pop\nputs \u0027writer1_acquired=true\u0027\n\nintruder_result = nil\nintruder = Thread.new do\n  intruder_result = lock.release_write_lock\nend\nintruder.join\n\nputs \"wrong_thread_release_write_lock_returned=#{intruder_result}\"\n\nwriter2_entered_while_writer1_inside = nil\nwriter2 = Thread.new do\n  lock.acquire_write_lock\n  writer2_entered_while_writer1_inside = writer1_inside\n  lock.release_write_lock\nend\n\nwriter2.join(0.25)\n\nputs \"writer2_acquired_while_writer1_inside=#{writer2_entered_while_writer1_inside}\"\n\nwriter1.join\n\nlock2 = Concurrent::ReadWriteLock.new\nstray_read_release_result = lock2.release_read_lock\ncounter_after_stray_read_release = lock2.instance_eval { @Counter.value }\nread_after_stray_release = begin\n  lock2.acquire_read_lock\n  \u0027acquired\u0027\nrescue =\u003e error\n  \"#{error.class}: #{error.message}\"\nend\n\nputs \"stray_release_read_lock_returned=#{stray_read_release_result}\"\nputs \"counter_after_stray_read_release=#{counter_after_stray_read_release}\"\nputs \"acquire_read_after_stray_release=#{read_after_stray_release}\"\n\nif intruder_result \u0026\u0026 writer2_entered_while_writer1_inside \u0026\u0026 counter_after_stray_read_release == -1\n  puts \u0027result=REPRODUCED wrong-thread write release and stray read-release corruption\u0027\nelse\n  puts \u0027result=NOT_REPRODUCED\u0027\nend\n```\nExpected result:\n\n- A second thread successfully calls `release_write_lock` while the first writer still holds the lock.\n- A second writer enters while the first writer is still inside the write critical section.\n- Calling `release_read_lock` on a fresh lock changes the counter to `-1`.\n- A subsequent read acquisition fails with `Concurrent::ResourceLimitError`.\n\n### Log evidence\n\nLocal reproduction output:\n\n```text\nruby=ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.arm64e-darwin25]\nconcurrent_ruby_version=1.3.6\npoc=ReadWriteLock release methods corrupt or bypass lock state\nwriter1_acquired=true\nwrong_thread_release_write_lock_returned=true\nwriter2_acquired_while_writer1_inside=true\nstray_release_read_lock_returned=true\ncounter_after_stray_read_release=-1\nacquire_read_after_stray_release=Concurrent::ResourceLimitError: Too many reader threads\nresult=REPRODUCED wrong-thread write release and stray read-release corruption\n```\n\n### Impact\nThis can break the write-lock mutual exclusion guarantee and can also leave a lock unusable after a stray read release.\nThe impact is local to applications that expose or misuse the manual `acquire_*` / `release_*` APIs. If the lock protects integrity-sensitive mutable state, wrong-thread write release can allow concurrent writers and data races. The stray read-release path can cause denial of service by corrupting the lock counter.\n\n### Credit\nPranjali Thakur - depthfirst ([depthfirst.com](\u003chttp://depthfirst.com\u003e))",
  "id": "BREW-imap-backup-CVE-2026-54906",
  "modified": "2026-08-13T16:59:45Z",
  "published": "2026-08-13T16:59:45Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-6wx8-w4f5-wwcr"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Concurrent Ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption",
  "upstream": [
    "GHSA-6wx8-w4f5-wwcr",
    "CVE-2026-54906"
  ]
}

{
  "affected": [
    {
      "ecosystem_specific": {
        "fix": null,
        "range_state": "affected",
        "resource": "concurrent-ruby",
        "resource_purl": "pkg:gem/concurrent-ruby@1.3.6",
        "upstream_fixed_in": "1.3.7"
      },
      "package": {
        "ecosystem": "Homebrew",
        "name": "krane",
        "purl": "pkg:brew/krane"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "confidence": "high",
    "source": "matched",
    "strategy": "registry",
    "upstream_evidence": [
      {
        "ecosystem": "RubyGems",
        "key": "pkg:gem/concurrent-ruby@1.3.6",
        "name": "concurrent-ruby",
        "resource": "concurrent-ruby",
        "strategy": "registry",
        "subject_version": "1.3.6"
      }
    ]
  },
  "details": "### Summary\n`Concurrent::ReadWriteLock#release_write_lock` does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can then enter its critical section while the first writer is still running.\n\n`Concurrent::ReadWriteLock#release_read_lock` also decrements the shared counter even when no read lock is held. Calling it on a fresh lock changes the counter from `0` to `-1`, after which normal read acquisition raises `Concurrent::ResourceLimitError`.\n\nThis is a synchronization correctness issue in the public `Concurrent::ReadWriteLock` API. It should not be framed as an authorization bypass; the lock is an in-process concurrency primitive, not an access-control boundary.\n\n###  Version\nSoftware: concurrent-ruby\nVersion: 1.3.6\nCommit: 7a1b78941c081106c20a9ca0144ac73a48d254ab\n\n### Details\n\n`release_write_lock` checks only whether the global counter indicates that a writer is running. It does not track or verify ownership:\n\n```ruby\ndef release_write_lock\n  return true unless running_writer?\n  c = @Counter.update { |counter| counter - RUNNING_WRITER }\n  @ReadLock.broadcast\n  @WriteLock.signal if waiting_writers(c) \u003e 0\n  true\nend\n```\n\nBecause ownership is not checked, a different thread can clear the `RUNNING_WRITER` bit while the original writer is still inside its critical section. Another writer can then acquire the write lock and run concurrently with the first writer.\n\n`release_read_lock` unconditionally decrements the shared counter:\n\n```ruby\ndef release_read_lock\n  while true\n    c = @Counter.value\n    if @Counter.compare_and_set(c, c-1)\n      if waiting_writer?(c) \u0026\u0026 running_readers(c) == 1\n        @WriteLock.signal\n      end\n      break\n    end\n  end\n  true\nend\n```\n\nOn a fresh lock, this changes the counter from `0` to `-1`. A later `acquire_read_lock` raises `Concurrent::ResourceLimitError` because the maximum-reader check masks the negative counter as saturated.\n\n# Reproduce\n\nFrom the root of a `concurrent-ruby` checkout, run:\n\n```bash\nruby -Ilib/concurrent-ruby - \u003c\u003c\u0027RUBY\u0027\nrequire \u0027concurrent/atomic/read_write_lock\u0027\nrequire \u0027concurrent/version\u0027\nrequire \u0027thread\u0027\n\nputs \"ruby=#{RUBY_DESCRIPTION}\"\nputs \"concurrent_ruby_version=#{Concurrent::VERSION}\"\nputs \"poc=ReadWriteLock release methods corrupt or bypass lock state\"\n\nlock = Concurrent::ReadWriteLock.new\nevents = Queue.new\nwriter1_inside = false\n\nwriter1 = Thread.new do\n  lock.acquire_write_lock\n  writer1_inside = true\n  events \u003c\u003c :writer1_acquired\n  sleep 0.5\n  writer1_inside = false\n  lock.release_write_lock\n  events \u003c\u003c :writer1_finished\nend\n\nevents.pop\nputs \u0027writer1_acquired=true\u0027\n\nintruder_result = nil\nintruder = Thread.new do\n  intruder_result = lock.release_write_lock\nend\nintruder.join\n\nputs \"wrong_thread_release_write_lock_returned=#{intruder_result}\"\n\nwriter2_entered_while_writer1_inside = nil\nwriter2 = Thread.new do\n  lock.acquire_write_lock\n  writer2_entered_while_writer1_inside = writer1_inside\n  lock.release_write_lock\nend\n\nwriter2.join(0.25)\n\nputs \"writer2_acquired_while_writer1_inside=#{writer2_entered_while_writer1_inside}\"\n\nwriter1.join\n\nlock2 = Concurrent::ReadWriteLock.new\nstray_read_release_result = lock2.release_read_lock\ncounter_after_stray_read_release = lock2.instance_eval { @Counter.value }\nread_after_stray_release = begin\n  lock2.acquire_read_lock\n  \u0027acquired\u0027\nrescue =\u003e error\n  \"#{error.class}: #{error.message}\"\nend\n\nputs \"stray_release_read_lock_returned=#{stray_read_release_result}\"\nputs \"counter_after_stray_read_release=#{counter_after_stray_read_release}\"\nputs \"acquire_read_after_stray_release=#{read_after_stray_release}\"\n\nif intruder_result \u0026\u0026 writer2_entered_while_writer1_inside \u0026\u0026 counter_after_stray_read_release == -1\n  puts \u0027result=REPRODUCED wrong-thread write release and stray read-release corruption\u0027\nelse\n  puts \u0027result=NOT_REPRODUCED\u0027\nend\n```\nExpected result:\n\n- A second thread successfully calls `release_write_lock` while the first writer still holds the lock.\n- A second writer enters while the first writer is still inside the write critical section.\n- Calling `release_read_lock` on a fresh lock changes the counter to `-1`.\n- A subsequent read acquisition fails with `Concurrent::ResourceLimitError`.\n\n### Log evidence\n\nLocal reproduction output:\n\n```text\nruby=ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.arm64e-darwin25]\nconcurrent_ruby_version=1.3.6\npoc=ReadWriteLock release methods corrupt or bypass lock state\nwriter1_acquired=true\nwrong_thread_release_write_lock_returned=true\nwriter2_acquired_while_writer1_inside=true\nstray_release_read_lock_returned=true\ncounter_after_stray_read_release=-1\nacquire_read_after_stray_release=Concurrent::ResourceLimitError: Too many reader threads\nresult=REPRODUCED wrong-thread write release and stray read-release corruption\n```\n\n### Impact\nThis can break the write-lock mutual exclusion guarantee and can also leave a lock unusable after a stray read release.\nThe impact is local to applications that expose or misuse the manual `acquire_*` / `release_*` APIs. If the lock protects integrity-sensitive mutable state, wrong-thread write release can allow concurrent writers and data races. The stray read-release path can cause denial of service by corrupting the lock counter.\n\n### Credit\nPranjali Thakur - depthfirst ([depthfirst.com](\u003chttp://depthfirst.com\u003e))",
  "id": "BREW-krane-CVE-2026-54906",
  "modified": "2026-08-13T17:01:45Z",
  "published": "2026-08-13T17:01:45Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-6wx8-w4f5-wwcr"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Concurrent Ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption",
  "upstream": [
    "GHSA-6wx8-w4f5-wwcr",
    "CVE-2026-54906"
  ]
}

{
  "affected": [
    {
      "ecosystem_specific": {
        "fix": null,
        "range_state": "affected",
        "resource": "concurrent-ruby",
        "resource_purl": "pkg:gem/concurrent-ruby@1.3.1",
        "upstream_fixed_in": "1.3.7"
      },
      "package": {
        "ecosystem": "Homebrew",
        "name": "travis",
        "purl": "pkg:brew/travis"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "confidence": "high",
    "source": "matched",
    "strategy": "registry",
    "upstream_evidence": [
      {
        "ecosystem": "RubyGems",
        "key": "pkg:gem/concurrent-ruby@1.3.1",
        "name": "concurrent-ruby",
        "resource": "concurrent-ruby",
        "strategy": "registry",
        "subject_version": "1.3.1"
      }
    ]
  },
  "details": "### Summary\n`Concurrent::ReadWriteLock#release_write_lock` does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can then enter its critical section while the first writer is still running.\n\n`Concurrent::ReadWriteLock#release_read_lock` also decrements the shared counter even when no read lock is held. Calling it on a fresh lock changes the counter from `0` to `-1`, after which normal read acquisition raises `Concurrent::ResourceLimitError`.\n\nThis is a synchronization correctness issue in the public `Concurrent::ReadWriteLock` API. It should not be framed as an authorization bypass; the lock is an in-process concurrency primitive, not an access-control boundary.\n\n###  Version\nSoftware: concurrent-ruby\nVersion: 1.3.6\nCommit: 7a1b78941c081106c20a9ca0144ac73a48d254ab\n\n### Details\n\n`release_write_lock` checks only whether the global counter indicates that a writer is running. It does not track or verify ownership:\n\n```ruby\ndef release_write_lock\n  return true unless running_writer?\n  c = @Counter.update { |counter| counter - RUNNING_WRITER }\n  @ReadLock.broadcast\n  @WriteLock.signal if waiting_writers(c) \u003e 0\n  true\nend\n```\n\nBecause ownership is not checked, a different thread can clear the `RUNNING_WRITER` bit while the original writer is still inside its critical section. Another writer can then acquire the write lock and run concurrently with the first writer.\n\n`release_read_lock` unconditionally decrements the shared counter:\n\n```ruby\ndef release_read_lock\n  while true\n    c = @Counter.value\n    if @Counter.compare_and_set(c, c-1)\n      if waiting_writer?(c) \u0026\u0026 running_readers(c) == 1\n        @WriteLock.signal\n      end\n      break\n    end\n  end\n  true\nend\n```\n\nOn a fresh lock, this changes the counter from `0` to `-1`. A later `acquire_read_lock` raises `Concurrent::ResourceLimitError` because the maximum-reader check masks the negative counter as saturated.\n\n# Reproduce\n\nFrom the root of a `concurrent-ruby` checkout, run:\n\n```bash\nruby -Ilib/concurrent-ruby - \u003c\u003c\u0027RUBY\u0027\nrequire \u0027concurrent/atomic/read_write_lock\u0027\nrequire \u0027concurrent/version\u0027\nrequire \u0027thread\u0027\n\nputs \"ruby=#{RUBY_DESCRIPTION}\"\nputs \"concurrent_ruby_version=#{Concurrent::VERSION}\"\nputs \"poc=ReadWriteLock release methods corrupt or bypass lock state\"\n\nlock = Concurrent::ReadWriteLock.new\nevents = Queue.new\nwriter1_inside = false\n\nwriter1 = Thread.new do\n  lock.acquire_write_lock\n  writer1_inside = true\n  events \u003c\u003c :writer1_acquired\n  sleep 0.5\n  writer1_inside = false\n  lock.release_write_lock\n  events \u003c\u003c :writer1_finished\nend\n\nevents.pop\nputs \u0027writer1_acquired=true\u0027\n\nintruder_result = nil\nintruder = Thread.new do\n  intruder_result = lock.release_write_lock\nend\nintruder.join\n\nputs \"wrong_thread_release_write_lock_returned=#{intruder_result}\"\n\nwriter2_entered_while_writer1_inside = nil\nwriter2 = Thread.new do\n  lock.acquire_write_lock\n  writer2_entered_while_writer1_inside = writer1_inside\n  lock.release_write_lock\nend\n\nwriter2.join(0.25)\n\nputs \"writer2_acquired_while_writer1_inside=#{writer2_entered_while_writer1_inside}\"\n\nwriter1.join\n\nlock2 = Concurrent::ReadWriteLock.new\nstray_read_release_result = lock2.release_read_lock\ncounter_after_stray_read_release = lock2.instance_eval { @Counter.value }\nread_after_stray_release = begin\n  lock2.acquire_read_lock\n  \u0027acquired\u0027\nrescue =\u003e error\n  \"#{error.class}: #{error.message}\"\nend\n\nputs \"stray_release_read_lock_returned=#{stray_read_release_result}\"\nputs \"counter_after_stray_read_release=#{counter_after_stray_read_release}\"\nputs \"acquire_read_after_stray_release=#{read_after_stray_release}\"\n\nif intruder_result \u0026\u0026 writer2_entered_while_writer1_inside \u0026\u0026 counter_after_stray_read_release == -1\n  puts \u0027result=REPRODUCED wrong-thread write release and stray read-release corruption\u0027\nelse\n  puts \u0027result=NOT_REPRODUCED\u0027\nend\n```\nExpected result:\n\n- A second thread successfully calls `release_write_lock` while the first writer still holds the lock.\n- A second writer enters while the first writer is still inside the write critical section.\n- Calling `release_read_lock` on a fresh lock changes the counter to `-1`.\n- A subsequent read acquisition fails with `Concurrent::ResourceLimitError`.\n\n### Log evidence\n\nLocal reproduction output:\n\n```text\nruby=ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.arm64e-darwin25]\nconcurrent_ruby_version=1.3.6\npoc=ReadWriteLock release methods corrupt or bypass lock state\nwriter1_acquired=true\nwrong_thread_release_write_lock_returned=true\nwriter2_acquired_while_writer1_inside=true\nstray_release_read_lock_returned=true\ncounter_after_stray_read_release=-1\nacquire_read_after_stray_release=Concurrent::ResourceLimitError: Too many reader threads\nresult=REPRODUCED wrong-thread write release and stray read-release corruption\n```\n\n### Impact\nThis can break the write-lock mutual exclusion guarantee and can also leave a lock unusable after a stray read release.\nThe impact is local to applications that expose or misuse the manual `acquire_*` / `release_*` APIs. If the lock protects integrity-sensitive mutable state, wrong-thread write release can allow concurrent writers and data races. The stray read-release path can cause denial of service by corrupting the lock counter.\n\n### Credit\nPranjali Thakur - depthfirst ([depthfirst.com](\u003chttp://depthfirst.com\u003e))",
  "id": "BREW-travis-CVE-2026-54906",
  "modified": "2026-08-13T17:44:53Z",
  "published": "2026-08-13T17:44:53Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-6wx8-w4f5-wwcr"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Concurrent Ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption",
  "upstream": [
    "GHSA-6wx8-w4f5-wwcr",
    "CVE-2026-54906"
  ]
}

{
  "affected": [
    {
      "ecosystem_specific": {
        "fix": null,
        "range_state": "affected",
        "resource": "concurrent-ruby",
        "resource_purl": "pkg:gem/concurrent-ruby@1.3.5",
        "upstream_fixed_in": "1.3.7"
      },
      "package": {
        "ecosystem": "Homebrew",
        "name": "uffizzi",
        "purl": "pkg:brew/uffizzi"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "confidence": "high",
    "source": "matched",
    "strategy": "registry",
    "upstream_evidence": [
      {
        "ecosystem": "RubyGems",
        "key": "pkg:gem/concurrent-ruby@1.3.5",
        "name": "concurrent-ruby",
        "resource": "concurrent-ruby",
        "strategy": "registry",
        "subject_version": "1.3.5"
      }
    ]
  },
  "details": "### Summary\n`Concurrent::ReadWriteLock#release_write_lock` does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can then enter its critical section while the first writer is still running.\n\n`Concurrent::ReadWriteLock#release_read_lock` also decrements the shared counter even when no read lock is held. Calling it on a fresh lock changes the counter from `0` to `-1`, after which normal read acquisition raises `Concurrent::ResourceLimitError`.\n\nThis is a synchronization correctness issue in the public `Concurrent::ReadWriteLock` API. It should not be framed as an authorization bypass; the lock is an in-process concurrency primitive, not an access-control boundary.\n\n###  Version\nSoftware: concurrent-ruby\nVersion: 1.3.6\nCommit: 7a1b78941c081106c20a9ca0144ac73a48d254ab\n\n### Details\n\n`release_write_lock` checks only whether the global counter indicates that a writer is running. It does not track or verify ownership:\n\n```ruby\ndef release_write_lock\n  return true unless running_writer?\n  c = @Counter.update { |counter| counter - RUNNING_WRITER }\n  @ReadLock.broadcast\n  @WriteLock.signal if waiting_writers(c) \u003e 0\n  true\nend\n```\n\nBecause ownership is not checked, a different thread can clear the `RUNNING_WRITER` bit while the original writer is still inside its critical section. Another writer can then acquire the write lock and run concurrently with the first writer.\n\n`release_read_lock` unconditionally decrements the shared counter:\n\n```ruby\ndef release_read_lock\n  while true\n    c = @Counter.value\n    if @Counter.compare_and_set(c, c-1)\n      if waiting_writer?(c) \u0026\u0026 running_readers(c) == 1\n        @WriteLock.signal\n      end\n      break\n    end\n  end\n  true\nend\n```\n\nOn a fresh lock, this changes the counter from `0` to `-1`. A later `acquire_read_lock` raises `Concurrent::ResourceLimitError` because the maximum-reader check masks the negative counter as saturated.\n\n# Reproduce\n\nFrom the root of a `concurrent-ruby` checkout, run:\n\n```bash\nruby -Ilib/concurrent-ruby - \u003c\u003c\u0027RUBY\u0027\nrequire \u0027concurrent/atomic/read_write_lock\u0027\nrequire \u0027concurrent/version\u0027\nrequire \u0027thread\u0027\n\nputs \"ruby=#{RUBY_DESCRIPTION}\"\nputs \"concurrent_ruby_version=#{Concurrent::VERSION}\"\nputs \"poc=ReadWriteLock release methods corrupt or bypass lock state\"\n\nlock = Concurrent::ReadWriteLock.new\nevents = Queue.new\nwriter1_inside = false\n\nwriter1 = Thread.new do\n  lock.acquire_write_lock\n  writer1_inside = true\n  events \u003c\u003c :writer1_acquired\n  sleep 0.5\n  writer1_inside = false\n  lock.release_write_lock\n  events \u003c\u003c :writer1_finished\nend\n\nevents.pop\nputs \u0027writer1_acquired=true\u0027\n\nintruder_result = nil\nintruder = Thread.new do\n  intruder_result = lock.release_write_lock\nend\nintruder.join\n\nputs \"wrong_thread_release_write_lock_returned=#{intruder_result}\"\n\nwriter2_entered_while_writer1_inside = nil\nwriter2 = Thread.new do\n  lock.acquire_write_lock\n  writer2_entered_while_writer1_inside = writer1_inside\n  lock.release_write_lock\nend\n\nwriter2.join(0.25)\n\nputs \"writer2_acquired_while_writer1_inside=#{writer2_entered_while_writer1_inside}\"\n\nwriter1.join\n\nlock2 = Concurrent::ReadWriteLock.new\nstray_read_release_result = lock2.release_read_lock\ncounter_after_stray_read_release = lock2.instance_eval { @Counter.value }\nread_after_stray_release = begin\n  lock2.acquire_read_lock\n  \u0027acquired\u0027\nrescue =\u003e error\n  \"#{error.class}: #{error.message}\"\nend\n\nputs \"stray_release_read_lock_returned=#{stray_read_release_result}\"\nputs \"counter_after_stray_read_release=#{counter_after_stray_read_release}\"\nputs \"acquire_read_after_stray_release=#{read_after_stray_release}\"\n\nif intruder_result \u0026\u0026 writer2_entered_while_writer1_inside \u0026\u0026 counter_after_stray_read_release == -1\n  puts \u0027result=REPRODUCED wrong-thread write release and stray read-release corruption\u0027\nelse\n  puts \u0027result=NOT_REPRODUCED\u0027\nend\n```\nExpected result:\n\n- A second thread successfully calls `release_write_lock` while the first writer still holds the lock.\n- A second writer enters while the first writer is still inside the write critical section.\n- Calling `release_read_lock` on a fresh lock changes the counter to `-1`.\n- A subsequent read acquisition fails with `Concurrent::ResourceLimitError`.\n\n### Log evidence\n\nLocal reproduction output:\n\n```text\nruby=ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.arm64e-darwin25]\nconcurrent_ruby_version=1.3.6\npoc=ReadWriteLock release methods corrupt or bypass lock state\nwriter1_acquired=true\nwrong_thread_release_write_lock_returned=true\nwriter2_acquired_while_writer1_inside=true\nstray_release_read_lock_returned=true\ncounter_after_stray_read_release=-1\nacquire_read_after_stray_release=Concurrent::ResourceLimitError: Too many reader threads\nresult=REPRODUCED wrong-thread write release and stray read-release corruption\n```\n\n### Impact\nThis can break the write-lock mutual exclusion guarantee and can also leave a lock unusable after a stray read release.\nThe impact is local to applications that expose or misuse the manual `acquire_*` / `release_*` APIs. If the lock protects integrity-sensitive mutable state, wrong-thread write release can allow concurrent writers and data races. The stray read-release path can cause denial of service by corrupting the lock counter.\n\n### Credit\nPranjali Thakur - depthfirst ([depthfirst.com](\u003chttp://depthfirst.com\u003e))",
  "id": "BREW-uffizzi-CVE-2026-54906",
  "modified": "2026-08-13T17:46:08Z",
  "published": "2026-08-13T17:46:08Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-6wx8-w4f5-wwcr"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ruby-concurrency/concurrent-ruby"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Concurrent Ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption",
  "upstream": [
    "GHSA-6wx8-w4f5-wwcr",
    "CVE-2026-54906"
  ]
}

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data versions v4.8 \u00e0 v5.3.x ant\u00e9rieures \u00e0 v5.4 patch 3",
      "product": {
        "name": "Db2",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "AIX versions 7.3.x sans le correctif de s\u00e9curit\u00e9 curl_fix11.tar",
      "product": {
        "name": "AIX",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "QRadar Data Synchronization App versions ant\u00e9rieures \u00e0 4.0.0",
      "product": {
        "name": "QRadar",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "QRadar Pulse App versions ant\u00e9rieures \u00e0 2.2.17",
      "product": {
        "name": "QRadar",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "WebSphere Application Server versions 9.0.x sans les correctifs de s\u00e9curit\u00e9 temporaires ant\u00e9rieures \u00e0 9.0.5.29 (disponibilit\u00e9 pr\u00e9vue pour le troisi\u00e8me trimestre 2026)",
      "product": {
        "name": "WebSphere Application Server",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "Sterling Control Center versions 6.3.1.0 sans le correctif iFix10",
      "product": {
        "name": "Sterling Control Center",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "WebSphere Application Server versions 8.5.x sans les correctifs de s\u00e9curit\u00e9 temporaires ant\u00e9rieures \u00e0 8.5.5.31 (disponibilit\u00e9 pr\u00e9vue pour le troisi\u00e8me trimestre 2026)",
      "product": {
        "name": "WebSphere Application Server",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "Sterling Control Center versions 6.4.2.0 sans le correctif iFix05",
      "product": {
        "name": "Sterling Control Center",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "Sterling External Authentication Server versions 6.1.x ant\u00e9rieures \u00e0 6.1.1.4 GA",
      "product": {
        "name": "Sterling",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "QRadar SIEM versions 7.5.x ant\u00e9rieures \u00e0 7.5.0 UP15 IF05",
      "product": {
        "name": "QRadar",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "Sterling B2B Integrator et Sterling File Gateway versions 6.2.0.x ant\u00e9rieures \u00e0 6.2.0.6_1",
      "product": {
        "name": "Sterling B2B Integrator",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "Sterling B2B Integrator et Sterling File Gateway versions 6.2.1.x ant\u00e9rieures \u00e0 6.2.1.2",
      "product": {
        "name": "Sterling B2B Integrator",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "Sterling Control Center versions 6.4.1.0 sans le correctif iFix04",
      "product": {
        "name": "Sterling Control Center",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "Sterling B2B Integrator et Sterling File Gateway versions 6.2.2.x ant\u00e9rieures \u00e0 6.2.2.1",
      "product": {
        "name": "Sterling B2B Integrator",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    },
    {
      "description": "WebSphere Application Server Liberty versions ant\u00e9rieures \u00e0 26.0.0.9 (disponibilit\u00e9 pr\u00e9vue pour le troisi\u00e8me trimestre 2026)",
      "product": {
        "name": "WebSphere Application Server",
        "vendor": {
          "name": "IBM",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": "",
  "content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
  "cves": [
    {
      "name": "CVE-2026-5588",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-5588"
    },
    {
      "name": "CVE-2026-45505",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-45505"
    },
    {
      "name": "CVE-2025-66199",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-66199"
    },
    {
      "name": "CVE-2026-3449",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-3449"
    },
    {
      "name": "CVE-2026-59871",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-59871"
    },
    {
      "name": "CVE-2026-42588",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42588"
    },
    {
      "name": "CVE-2026-33845",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-33845"
    },
    {
      "name": "CVE-2026-44025",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44025"
    },
    {
      "name": "CVE-2026-42253",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42253"
    },
    {
      "name": "CVE-2026-39830",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39830"
    },
    {
      "name": "CVE-2026-42041",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42041"
    },
    {
      "name": "CVE-2026-42508",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42508"
    },
    {
      "name": "CVE-2026-41716",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41716"
    },
    {
      "name": "CVE-2026-16184",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-16184"
    },
    {
      "name": "CVE-2026-15328",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-15328"
    },
    {
      "name": "CVE-2025-15469",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-15469"
    },
    {
      "name": "CVE-2020-13956",
      "url": "https://www.cve.org/CVERecord?id=CVE-2020-13956"
    },
    {
      "name": "CVE-2025-47944",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-47944"
    },
    {
      "name": "CVE-2025-56200",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-56200"
    },
    {
      "name": "CVE-2026-59874",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-59874"
    },
    {
      "name": "CVE-2026-42258",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42258"
    },
    {
      "name": "CVE-2026-7769",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-7769"
    },
    {
      "name": "CVE-2026-30827",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-30827"
    },
    {
      "name": "CVE-2026-22752",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-22752"
    },
    {
      "name": "CVE-2026-39833",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39833"
    },
    {
      "name": "CVE-2025-22228",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-22228"
    },
    {
      "name": "CVE-2026-8458",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-8458"
    },
    {
      "name": "CVE-2026-2391",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-2391"
    },
    {
      "name": "CVE-2026-1605",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-1605"
    },
    {
      "name": "CVE-2026-46605",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-46605"
    },
    {
      "name": "CVE-2026-22013",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-22013"
    },
    {
      "name": "CVE-2026-53655",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-53655"
    },
    {
      "name": "CVE-2026-29145",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-29145"
    },
    {
      "name": "CVE-2026-22018",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-22018"
    },
    {
      "name": "CVE-2026-39832",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39832"
    },
    {
      "name": "CVE-2020-13955",
      "url": "https://www.cve.org/CVERecord?id=CVE-2020-13955"
    },
    {
      "name": "CVE-2026-39829",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39829"
    },
    {
      "name": "CVE-2026-41988",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41988"
    },
    {
      "name": "CVE-2026-14528",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14528"
    },
    {
      "name": "CVE-2026-6357",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-6357"
    },
    {
      "name": "CVE-2026-23745",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-23745"
    },
    {
      "name": "CVE-2026-2006",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-2006"
    },
    {
      "name": "CVE-2026-53550",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-53550"
    },
    {
      "name": "CVE-2026-41721",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41721"
    },
    {
      "name": "CVE-2026-54905",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54905"
    },
    {
      "name": "CVE-2026-0994",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-0994"
    },
    {
      "name": "CVE-2026-49157",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-49157"
    },
    {
      "name": "CVE-2021-47154",
      "url": "https://www.cve.org/CVERecord?id=CVE-2021-47154"
    },
    {
      "name": "CVE-2026-44494",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44494"
    },
    {
      "name": "CVE-2026-54899",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54899"
    },
    {
      "name": "CVE-2026-39834",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39834"
    },
    {
      "name": "CVE-2025-15284",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-15284"
    },
    {
      "name": "CVE-2026-41635",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41635"
    },
    {
      "name": "CVE-2026-46595",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-46595"
    },
    {
      "name": "CVE-2026-54901",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54901"
    },
    {
      "name": "CVE-2026-42036",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42036"
    },
    {
      "name": "CVE-2026-2005",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-2005"
    },
    {
      "name": "CVE-2022-39135",
      "url": "https://www.cve.org/CVERecord?id=CVE-2022-39135"
    },
    {
      "name": "CVE-2026-39821",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39821"
    },
    {
      "name": "CVE-2026-33558",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-33558"
    },
    {
      "name": "CVE-2026-33846",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-33846"
    },
    {
      "name": "CVE-2021-23337",
      "url": "https://www.cve.org/CVERecord?id=CVE-2021-23337"
    },
    {
      "name": "CVE-2026-5758",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-5758"
    },
    {
      "name": "CVE-2026-34500",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34500"
    },
    {
      "name": "CVE-2026-54502",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54502"
    },
    {
      "name": "CVE-2026-22795",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-22795"
    },
    {
      "name": "CVE-2026-29146",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-29146"
    },
    {
      "name": "CVE-2026-34043",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34043"
    },
    {
      "name": "CVE-2025-64718",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-64718"
    },
    {
      "name": "CVE-2026-9277",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-9277"
    },
    {
      "name": "CVE-2026-27136",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-27136"
    },
    {
      "name": "CVE-2025-62718",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-62718"
    },
    {
      "name": "CVE-2026-4800",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-4800"
    },
    {
      "name": "CVE-2026-10536",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-10536"
    },
    {
      "name": "CVE-2026-41844",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41844"
    },
    {
      "name": "CVE-2026-8932",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-8932"
    },
    {
      "name": "CVE-2026-4424",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-4424"
    },
    {
      "name": "CVE-2026-45292",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-45292"
    },
    {
      "name": "CVE-2024-38820",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-38820"
    },
    {
      "name": "CVE-2026-40356",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-40356"
    },
    {
      "name": "CVE-2026-15325",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-15325"
    },
    {
      "name": "CVE-2026-14976",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14976"
    },
    {
      "name": "CVE-2026-5598",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-5598"
    },
    {
      "name": "CVE-2026-42256",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42256"
    },
    {
      "name": "CVE-2026-42033",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42033"
    },
    {
      "name": "CVE-2025-59375",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-59375"
    },
    {
      "name": "CVE-2026-54906",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54906"
    },
    {
      "name": "CVE-2026-34040",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34040"
    },
    {
      "name": "CVE-2026-42035",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42035"
    },
    {
      "name": "CVE-2026-41842",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41842"
    },
    {
      "name": "CVE-2026-44495",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44495"
    },
    {
      "name": "CVE-2026-41695",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41695"
    },
    {
      "name": "CVE-2026-14512",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14512"
    },
    {
      "name": "CVE-2026-11856",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-11856"
    },
    {
      "name": "CVE-2026-44160",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44160"
    },
    {
      "name": "CVE-2026-42009",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42009"
    },
    {
      "name": "CVE-2026-33750",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-33750"
    },
    {
      "name": "CVE-2026-5038",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-5038"
    },
    {
      "name": "CVE-2026-34478",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34478"
    },
    {
      "name": "CVE-2026-2359",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-2359"
    },
    {
      "name": "CVE-2026-42043",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42043"
    },
    {
      "name": "CVE-2025-11143",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-11143"
    },
    {
      "name": "CVE-2026-34480",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34480"
    },
    {
      "name": "CVE-2026-59869",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-59869"
    },
    {
      "name": "CVE-2025-7783",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-7783"
    },
    {
      "name": "CVE-2025-12758",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-12758"
    },
    {
      "name": "CVE-2026-40175",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-40175"
    },
    {
      "name": "CVE-2026-5079",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-5079"
    },
    {
      "name": "CVE-2026-5795",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-5795"
    },
    {
      "name": "CVE-2024-23953",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-23953"
    },
    {
      "name": "CVE-2025-68161",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-68161"
    },
    {
      "name": "CVE-2026-44930",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44930"
    },
    {
      "name": "CVE-2026-14974",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14974"
    },
    {
      "name": "CVE-2024-29869",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-29869"
    },
    {
      "name": "CVE-2026-42010",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42010"
    },
    {
      "name": "CVE-2026-42506",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42506"
    },
    {
      "name": "CVE-2026-34479",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34479"
    },
    {
      "name": "CVE-2026-22796",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-22796"
    },
    {
      "name": "CVE-2026-26960",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-26960"
    },
    {
      "name": "CVE-2026-42040",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42040"
    },
    {
      "name": "CVE-2026-4867",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-4867"
    },
    {
      "name": "CVE-2026-2303",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-2303"
    },
    {
      "name": "CVE-2024-6763",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-6763"
    },
    {
      "name": "CVE-2026-27903",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-27903"
    },
    {
      "name": "CVE-2026-14981",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14981"
    },
    {
      "name": "CVE-2026-39831",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39831"
    },
    {
      "name": "CVE-2026-39828",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39828"
    },
    {
      "name": "CVE-2026-8924",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-8924"
    },
    {
      "name": "CVE-2024-45337",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-45337"
    },
    {
      "name": "CVE-2026-14529",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14529"
    },
    {
      "name": "CVE-2026-59875",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-59875"
    },
    {
      "name": "CVE-2026-41843",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41843"
    },
    {
      "name": "CVE-2026-54896",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54896"
    },
    {
      "name": "CVE-2026-25680",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-25680"
    },
    {
      "name": "CVE-2026-34487",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34487"
    },
    {
      "name": "CVE-2026-39835",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39835"
    },
    {
      "name": "CVE-2026-42578",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42578"
    },
    {
      "name": "CVE-2026-41850",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41850"
    },
    {
      "name": "CVE-2026-4519",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-4519"
    },
    {
      "name": "CVE-2026-34197",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34197"
    },
    {
      "name": "CVE-2024-12905",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-12905"
    },
    {
      "name": "CVE-2024-52046",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-52046"
    },
    {
      "name": "CVE-2026-59873",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-59873"
    },
    {
      "name": "CVE-2026-24842",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-24842"
    },
    {
      "name": "CVE-2025-47935",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-47935"
    },
    {
      "name": "CVE-2026-40198",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-40198"
    },
    {
      "name": "CVE-2026-4111",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-4111"
    },
    {
      "name": "CVE-2024-38827",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-38827"
    },
    {
      "name": "CVE-2026-41694",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41694"
    },
    {
      "name": "CVE-2026-23950",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-23950"
    },
    {
      "name": "CVE-2026-40046",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-40046"
    },
    {
      "name": "CVE-2022-22968",
      "url": "https://www.cve.org/CVERecord?id=CVE-2022-22968"
    },
    {
      "name": "CVE-2026-16192",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-16192"
    },
    {
      "name": "CVE-2026-2950",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-2950"
    },
    {
      "name": "CVE-2026-54500",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54500"
    },
    {
      "name": "CVE-2026-3304",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-3304"
    },
    {
      "name": "CVE-2026-40895",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-40895"
    },
    {
      "name": "CVE-2018-10237",
      "url": "https://www.cve.org/CVERecord?id=CVE-2018-10237"
    },
    {
      "name": "CVE-2026-14515",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14515"
    },
    {
      "name": "CVE-2026-22016",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-22016"
    },
    {
      "name": "CVE-2026-22021",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-22021"
    },
    {
      "name": "CVE-2026-6100",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-6100"
    },
    {
      "name": "CVE-2026-54904",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54904"
    },
    {
      "name": "CVE-2026-22007",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-22007"
    },
    {
      "name": "CVE-2025-68160",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-68160"
    },
    {
      "name": "CVE-2026-13149",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-13149"
    },
    {
      "name": "CVE-2026-54897",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54897"
    },
    {
      "name": "CVE-2026-34268",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34268"
    },
    {
      "name": "CVE-2026-41852",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41852"
    },
    {
      "name": "CVE-2021-22569",
      "url": "https://www.cve.org/CVERecord?id=CVE-2021-22569"
    },
    {
      "name": "CVE-2026-3520",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-3520"
    },
    {
      "name": "CVE-2026-29786",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-29786"
    },
    {
      "name": "CVE-2026-41006",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41006"
    },
    {
      "name": "CVE-2026-41711",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41711"
    },
    {
      "name": "CVE-2026-27830",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-27830"
    },
    {
      "name": "CVE-2026-44487",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44487"
    },
    {
      "name": "CVE-2026-2482",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-2482"
    },
    {
      "name": "CVE-2026-42038",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42038"
    },
    {
      "name": "CVE-2026-49844",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-49844"
    },
    {
      "name": "CVE-2026-25854",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-25854"
    },
    {
      "name": "CVE-2026-2332",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-2332"
    },
    {
      "name": "CVE-2026-41851",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41851"
    },
    {
      "name": "CVE-2026-42039",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42039"
    },
    {
      "name": "CVE-2026-8149",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-8149"
    },
    {
      "name": "CVE-2026-6009",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-6009"
    },
    {
      "name": "CVE-2026-9358",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-9358"
    },
    {
      "name": "CVE-2026-14446",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14446"
    },
    {
      "name": "CVE-2026-42502",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42502"
    },
    {
      "name": "CVE-2020-8908",
      "url": "https://www.cve.org/CVERecord?id=CVE-2020-8908"
    },
    {
      "name": "CVE-2026-42245",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42245"
    },
    {
      "name": "CVE-2026-8723",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-8723"
    },
    {
      "name": "CVE-2026-40988",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-40988"
    },
    {
      "name": "CVE-2026-41841",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41841"
    },
    {
      "name": "CVE-2026-25681",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-25681"
    },
    {
      "name": "CVE-2025-69418",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-69418"
    },
    {
      "name": "CVE-2026-54903",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54903"
    },
    {
      "name": "CVE-2026-39304",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39304"
    },
    {
      "name": "CVE-2026-49270",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-49270"
    },
    {
      "name": "CVE-2025-15468",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-15468"
    },
    {
      "name": "CVE-2026-25639",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-25639"
    },
    {
      "name": "CVE-2026-15064",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-15064"
    },
    {
      "name": "CVE-2026-42044",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42044"
    },
    {
      "name": "CVE-2026-54900",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54900"
    },
    {
      "name": "CVE-2018-16487",
      "url": "https://www.cve.org/CVERecord?id=CVE-2018-16487"
    },
    {
      "name": "CVE-2023-22899",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-22899"
    },
    {
      "name": "CVE-2026-42034",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42034"
    },
    {
      "name": "CVE-2026-8927",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-8927"
    },
    {
      "name": "CVE-2026-41846",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41846"
    },
    {
      "name": "CVE-2025-5889",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-5889"
    },
    {
      "name": "CVE-2026-41035",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41035"
    },
    {
      "name": "CVE-2026-40199",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-40199"
    },
    {
      "name": "CVE-2025-27789",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-27789"
    },
    {
      "name": "CVE-2026-46598",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-46598"
    },
    {
      "name": "CVE-2026-44024",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44024"
    },
    {
      "name": "CVE-2026-42246",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42246"
    },
    {
      "name": "CVE-2025-66566",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-66566"
    },
    {
      "name": "CVE-2025-66168",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-66168"
    },
    {
      "name": "CVE-2026-41409",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41409"
    },
    {
      "name": "CVE-2025-11187",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-11187"
    },
    {
      "name": "CVE-2026-14980",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14980"
    },
    {
      "name": "CVE-2026-54898",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54898"
    },
    {
      "name": "CVE-2026-12143",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-12143"
    },
    {
      "name": "CVE-2026-44431",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44431"
    },
    {
      "name": "CVE-2026-26996",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-26996"
    },
    {
      "name": "CVE-2026-44486",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44486"
    },
    {
      "name": "CVE-2026-33227",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-33227"
    },
    {
      "name": "CVE-2026-42264",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42264"
    },
    {
      "name": "CVE-2026-46597",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-46597"
    },
    {
      "name": "CVE-2026-44161",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44161"
    },
    {
      "name": "CVE-2026-4786",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-4786"
    },
    {
      "name": "CVE-2025-64756",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-64756"
    },
    {
      "name": "CVE-2026-34483",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34483"
    },
    {
      "name": "CVE-2026-44496",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44496"
    },
    {
      "name": "CVE-2026-0636",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-0636"
    },
    {
      "name": "CVE-2026-44492",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44492"
    },
    {
      "name": "CVE-2025-48997",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-48997"
    },
    {
      "name": "CVE-2026-24880",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-24880"
    },
    {
      "name": "CVE-2021-22570",
      "url": "https://www.cve.org/CVERecord?id=CVE-2021-22570"
    },
    {
      "name": "CVE-2026-9547",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-9547"
    },
    {
      "name": "CVE-2026-41007",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41007"
    },
    {
      "name": "CVE-2026-42037",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42037"
    },
    {
      "name": "CVE-2026-2004",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-2004"
    },
    {
      "name": "CVE-2026-42042",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42042"
    },
    {
      "name": "CVE-2025-21502",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-21502"
    },
    {
      "name": "CVE-2026-35554",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-35554"
    },
    {
      "name": "CVE-2025-48387",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-48387"
    },
    {
      "name": "CVE-2026-12590",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-12590"
    },
    {
      "name": "CVE-2026-27727",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-27727"
    },
    {
      "name": "CVE-2026-34477",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34477"
    },
    {
      "name": "CVE-2026-54902",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54902"
    },
    {
      "name": "CVE-2026-44490",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44490"
    },
    {
      "name": "CVE-2026-54592",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-54592"
    },
    {
      "name": "CVE-2023-5752",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-5752"
    },
    {
      "name": "CVE-2026-39827",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39827"
    },
    {
      "name": "CVE-2025-12183",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-12183"
    },
    {
      "name": "CVE-2025-7338",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-7338"
    },
    {
      "name": "CVE-2026-15280",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-15280"
    },
    {
      "name": "CVE-2026-41848",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41848"
    },
    {
      "name": "CVE-2025-14813",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-14813"
    },
    {
      "name": "CVE-2026-31802",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-31802"
    },
    {
      "name": "CVE-2025-13465",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-13465"
    },
    {
      "name": "CVE-2026-13311",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-13311"
    },
    {
      "name": "CVE-2026-41907",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-41907"
    },
    {
      "name": "CVE-2026-44488",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-44488"
    },
    {
      "name": "CVE-2025-59343",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-59343"
    },
    {
      "name": "CVE-2026-34481",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-34481"
    },
    {
      "name": "CVE-2026-27904",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-27904"
    },
    {
      "name": "CVE-2026-8286",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-8286"
    },
    {
      "name": "CVE-2026-42257",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42257"
    },
    {
      "name": "CVE-2026-42338",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42338"
    }
  ],
  "initial_release_date": "2026-07-31T00:00:00",
  "last_revision_date": "2026-07-31T00:00:00",
  "links": [],
  "reference": "CERTFR-2026-AVI-0958",
  "revisions": [
    {
      "description": "Version initiale",
      "revision_date": "2026-07-31T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    },
    {
      "description": "Injection de code indirecte \u00e0 distance (XSS)"
    },
    {
      "description": "Injection de requ\u00eates ill\u00e9gitimes par rebond (CSRF)"
    },
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    },
    {
      "description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
    },
    {
      "description": "Injection SQL (SQLi)"
    },
    {
      "description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
    },
    {
      "description": "Falsification de requ\u00eates c\u00f4t\u00e9 serveur (SSRF)"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    },
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    },
    {
      "description": "\u00c9l\u00e9vation de privil\u00e8ges"
    }
  ],
  "summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans les produits IBM. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance, une \u00e9l\u00e9vation de privil\u00e8ges et un d\u00e9ni de service \u00e0 distance.",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans les produits IBM",
  "vendor_advisories": [
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281450",
      "url": "https://www.ibm.com/support/pages/node/7281450"
    },
    {
      "published_at": "2026-07-28",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281625",
      "url": "https://www.ibm.com/support/pages/node/7281625"
    },
    {
      "published_at": "2026-07-30",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281949",
      "url": "https://www.ibm.com/support/pages/node/7281949"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7277692",
      "url": "https://www.ibm.com/support/pages/node/7277692"
    },
    {
      "published_at": "2026-07-28",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281628",
      "url": "https://www.ibm.com/support/pages/node/7281628"
    },
    {
      "published_at": "2026-07-24",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281135",
      "url": "https://www.ibm.com/support/pages/node/7281135"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281375",
      "url": "https://www.ibm.com/support/pages/node/7281375"
    },
    {
      "published_at": "2026-07-29",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281743",
      "url": "https://www.ibm.com/support/pages/node/7281743"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281373",
      "url": "https://www.ibm.com/support/pages/node/7281373"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281388",
      "url": "https://www.ibm.com/support/pages/node/7281388"
    },
    {
      "published_at": "2026-07-28",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281721",
      "url": "https://www.ibm.com/support/pages/node/7281721"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281369",
      "url": "https://www.ibm.com/support/pages/node/7281369"
    },
    {
      "published_at": "2026-07-28",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281648",
      "url": "https://www.ibm.com/support/pages/node/7281648"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281374",
      "url": "https://www.ibm.com/support/pages/node/7281374"
    },
    {
      "published_at": "2026-07-24",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281136",
      "url": "https://www.ibm.com/support/pages/node/7281136"
    },
    {
      "published_at": "2026-07-28",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281641",
      "url": "https://www.ibm.com/support/pages/node/7281641"
    },
    {
      "published_at": "2026-07-28",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281631",
      "url": "https://www.ibm.com/support/pages/node/7281631"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281371",
      "url": "https://www.ibm.com/support/pages/node/7281371"
    },
    {
      "published_at": "2026-07-28",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281633",
      "url": "https://www.ibm.com/support/pages/node/7281633"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281438",
      "url": "https://www.ibm.com/support/pages/node/7281438"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281370",
      "url": "https://www.ibm.com/support/pages/node/7281370"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281565",
      "url": "https://www.ibm.com/support/pages/node/7281565"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281368",
      "url": "https://www.ibm.com/support/pages/node/7281368"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281350",
      "url": "https://www.ibm.com/support/pages/node/7281350"
    },
    {
      "published_at": "2026-07-28",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281651",
      "url": "https://www.ibm.com/support/pages/node/7281651"
    },
    {
      "published_at": "2026-07-30",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281950",
      "url": "https://www.ibm.com/support/pages/node/7281950"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281567",
      "url": "https://www.ibm.com/support/pages/node/7281567"
    },
    {
      "published_at": "2026-07-23",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7280950",
      "url": "https://www.ibm.com/support/pages/node/7280950"
    },
    {
      "published_at": "2026-07-27",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281441",
      "url": "https://www.ibm.com/support/pages/node/7281441"
    },
    {
      "published_at": "2026-07-28",
      "title": "Bulletin de s\u00e9curit\u00e9 IBM 7281649",
      "url": "https://www.ibm.com/support/pages/node/7281649"
    }
  ]
}

{
  "affected": [
    {
      "package": {
        "ecosystem": "CleanStart",
        "name": "ruby-fluentd-1.18"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.18.0-r5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "credits": [],
  "database_specific": {},
  "details": "Multiple security vulnerabilities affect the ruby-fluentd-1.18 package. These issues are resolved in later releases. See references for individual vulnerability details.",
  "id": "CLEANSTART-2026-DE16221",
  "modified": "2026-09-18T11:59:01.768079Z",
  "published": "2026-07-21T08:19:55.189420Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-DE16221.json"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54171"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54297"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54522"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54904"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54905"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54906"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-6wx8-w4f5-wwcr"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-98m9-hrrm-r99r"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-h8w8-99g7-qmvj"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-wv3x-4vxv-whpp"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54171"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54297"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54522"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54904"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54905"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54906"
    }
  ],
  "related": [],
  "schema_version": "1.7.3",
  "summary": "Security fixes for CVE-2026-54171, CVE-2026-54297, CVE-2026-54522, CVE-2026-54904, CVE-2026-54905, CVE-2026-54906, ghsa-6wx8-w4f5-wwcr, ghsa-98m9-hrrm-r99r, ghsa-h8w8-99g7-qmvj, ghsa-wv3x-4vxv-whpp applied in versions: 1.18.0-r4, 1.18.0-r5",
  "upstream": [
    "CVE-2026-54171",
    "CVE-2026-54297",
    "CVE-2026-54522",
    "CVE-2026-54904",
    "CVE-2026-54905",
    "CVE-2026-54906",
    "ghsa-6wx8-w4f5-wwcr",
    "ghsa-98m9-hrrm-r99r",
    "ghsa-h8w8-99g7-qmvj",
    "ghsa-wv3x-4vxv-whpp"
  ],
  "withdrawn": "2026-09-18T11:59:01.768079Z"
}

{
  "affected": [
    {
      "package": {
        "ecosystem": "CleanStart",
        "name": "logstash-fips"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "9.4.3-r1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "CleanStart",
        "name": "ruby-fluentd-1.18"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.18.0-r4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "CleanStart",
        "name": "ruby-fluentd-1.19"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.19.2-r3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "credits": [],
  "database_specific": {},
  "details": "CVE-2026-54906 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.",
  "id": "CLEANSTART-2026-JE87878",
  "modified": "2026-07-08T04:44:58Z",
  "published": "2026-09-18T09:55:57.338231Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-JE87878.json"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54906"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54906"
    }
  ],
  "related": [],
  "schema_version": "1.7.3",
  "summary": "Security fix for CVE-2026-54906 applied in: logstash-fips 9.4.3-r1, ruby-fluentd-1.18 1.18.0-r4, ruby-fluentd-1.19 1.19.2-r3",
  "upstream": [
    "CVE-2026-54906"
  ]
}

{
  "affected": [
    {
      "package": {
        "ecosystem": "CleanStart",
        "name": "ruby-fluentd-1.19"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.19.2-r4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "credits": [],
  "database_specific": {},
  "details": "Multiple security vulnerabilities affect the ruby-fluentd-1.19 package. These issues are resolved in later releases. See references for individual vulnerability details.",
  "id": "CLEANSTART-2026-UT74115",
  "modified": "2026-09-18T11:59:01.768079Z",
  "published": "2026-07-21T08:19:01.995115Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-UT74115.json"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-33637"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-41316"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-42245"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-42246"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-42256"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-42257"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-42258"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54171"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54297"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54696"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54904"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54905"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/CVE-2026-54906"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-5rv5-xj5j-3484"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-6wx8-w4f5-wwcr"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-75xq-5h9v-w6px"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-87pf-fpwv-p7m7"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-98m9-hrrm-r99r"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-h8w8-99g7-qmvj"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-hm49-wcqc-g2xg"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-q2mw-fvj9-vvcw"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-vcgp-9326-pqcp"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/ghsa-wv3x-4vxv-whpp"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33637"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-41316"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42245"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42246"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42256"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42257"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42258"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54171"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54297"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54696"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54904"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54905"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54906"
    }
  ],
  "related": [],
  "schema_version": "1.7.3",
  "summary": "Security fixes for CVE-2026-33637, CVE-2026-41316, CVE-2026-42245, CVE-2026-42246, CVE-2026-42256, CVE-2026-42257, CVE-2026-42258, CVE-2026-54171, CVE-2026-54297, CVE-2026-54696, CVE-2026-54904, CVE-2026-54905, CVE-2026-54906, ghsa-5rv5-xj5j-3484, ghsa-6wx8-w4f5-wwcr, ghsa-75xq-5h9v-w6px, ghsa-87pf-fpwv-p7m7, ghsa-98m9-hrrm-r99r, ghsa-h8w8-99g7-qmvj, ghsa-hm49-wcqc-g2xg, ghsa-q2mw-fvj9-vvcw, ghsa-vcgp-9326-pqcp, ghsa-wv3x-4vxv-whpp applied in versions: 1.19.2-r2, 1.19.2-r3, 1.19.2-r4",
  "upstream": [
    "CVE-2026-33637",
    "CVE-2026-41316",
    "CVE-2026-42245",
    "CVE-2026-42246",
    "CVE-2026-42256",
    "CVE-2026-42257",
    "CVE-2026-42258",
    "CVE-2026-54171",
    "CVE-2026-54297",
    "CVE-2026-54696",
    "CVE-2026-54904",
    "CVE-2026-54905",
    "CVE-2026-54906",
    "ghsa-5rv5-xj5j-3484",
    "ghsa-6wx8-w4f5-wwcr",
    "ghsa-75xq-5h9v-w6px",
    "ghsa-87pf-fpwv-p7m7",
    "ghsa-98m9-hrrm-r99r",
    "ghsa-h8w8-99g7-qmvj",
    "ghsa-hm49-wcqc-g2xg",
    "ghsa-q2mw-fvj9-vvcw",
    "ghsa-vcgp-9326-pqcp",
    "ghsa-wv3x-4vxv-whpp"
  ],
  "withdrawn": "2026-09-18T11:59:01.768079Z"
}

{
  "affected": [
    {
      "package": {
        "ecosystem": "CleanStart",
        "name": "logstash-fips"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "9.4.3-r1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "9.4.3-r1"
      ]
    }
  ],
  "credits": [],
  "database_specific": {},
  "details": "Package logstash-fips version 9.4.3-r1 fixes 76 vulnerabilities: CVE-2026-55831, CVE-2026-55833, CVE-2026-56745, CVE-2026-50020, CVE-2026-56746...",
  "id": "CLEANSTART-2026-VR87787",
  "modified": "2026-09-18T11:59:01.768079Z",
  "published": "2026-08-13T12:10:09Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/elastic/logstash"
    }
  ],
  "related": [],
  "schema_version": "1.7.3",
  "summary": "Security fixes in logstash-fips 9.4.3-r1",
  "upstream": [
    "CVE-2026-55831",
    "CVE-2026-55833",
    "CVE-2026-56745",
    "CVE-2026-50020",
    "CVE-2026-56746",
    "CVE-2026-59898",
    "CVE-2026-59899",
    "CVE-2026-59921",
    "ghsa-jppx-w49h-x2qq",
    "ghsa-6jqx-86gh-f27w",
    "ghsa-mvh2-crg5-v77c",
    "ghsa-6cqp-g7gg-8hr5",
    "ghsa-4mp9-239f-g9hg",
    "ghsa-gcjf-9mgh-3p7g",
    "ghsa-q4f6-jm68-57ww",
    "ghsa-hvcg-qmg6-jm4c",
    "CVE-2026-59901",
    "ghsa-558v-64gr-wgg4",
    "CVE-2026-54512",
    "CVE-2026-54513",
    "CVE-2026-54514",
    "CVE-2026-54515",
    "CVE-2026-59888",
    "CVE-2026-54516",
    "CVE-2026-54517",
    "CVE-2026-54518",
    "CVE-2026-59889",
    "ghsa-5gvw-p9qm-jgwh",
    "ghsa-5hh8-q8hv-fr38",
    "ghsa-rcqc-6cw3-h962",
    "ghsa-9fxm-vc8v-hj55",
    "ghsa-mhm7-754m-9p8w",
    "ghsa-j3rv-43j4-c7qm",
    "ghsa-rmj7-2vxq-3g9f",
    "ghsa-5jmj-h7xm-6q6v",
    "ghsa-3pjw-73gf-8qr5",
    "ghsa-hgj6-7826-r7m5",
    "CVE-2025-14813",
    "CVE-2026-0636",
    "CVE-2026-5598",
    "ghsa-574f-3g2m-x479",
    "ghsa-p93r-85wp-75v3",
    "ghsa-c3fc-8qff-9hwx",
    "CVE-2026-5588",
    "ghsa-wg6q-6289-32hp",
    "ghsa-r7wm-3cxj-wff9",
    "ghsa-72hv-8253-57qq",
    "CVE-2026-59949",
    "ghsa-xx22-p4ch-683r",
    "CVE-2026-47240",
    "CVE-2026-47242",
    "CVE-2026-47241",
    "ghsa-8p34-64r3-mwg8",
    "ghsa-46q3-7gv7-qmgg",
    "ghsa-c4fp-cxrr-mj66",
    "CVE-2026-47736",
    "CVE-2026-47737",
    "ghsa-qpgp-93vx-g8v8",
    "ghsa-2vqw-3mp8-cgmx",
    "CVE-2026-54906",
    "CVE-2026-54904",
    "CVE-2026-54905",
    "ghsa-h8w8-99g7-qmvj",
    "ghsa-6wx8-w4f5-wwcr",
    "ghsa-wv3x-4vxv-whpp",
    "CVE-2026-54696",
    "ghsa-x2f5-4prf-w687",
    "ghsa-5prr-v3j2-97mh",
    "ghsa-5v8h-3h3q-446p",
    "ghsa-8678-w3jw-xfc2",
    "ghsa-9cv2-cfxc-v4v2",
    "ghsa-p67v-3w7g-wjg7",
    "ghsa-phwj-rprq-35pp",
    "ghsa-wfpw-mmfh-qq69",
    "ghsa-wjv4-x9w8-wm3h",
    "ghsa-g9g8-vgvw-g3vf"
  ],
  "withdrawn": "2026-09-18T11:59:01.768079Z"
}