Latest CVE

Latest Vulnerabilities

  • CVE-2026-104885 - OpenRemote: Cross-realm MQTT session disconnect without authorization

    CVE ID :CVE-2026-104885
    Published : Nov. 19, 2026, 7:42 p.m. | 16 minutes ago
    Description :OpenRemote is an open-source internet-of-things platform. Prior to 1.31.0, an authenticated user who obtains another user's MQTT session ID can disconnect that session across realm boundaries through the GET route GET /disconnect/. In manager/src/main/java/org/openremote/manager/security/UserResourceImpl.java, disconnectUserSession ignores the requested realm and calls mqttBrokerService.disconnectSession(sessionID) without checking session ownership; model/src/main/java/org/openremote/model/security/UserResource.java exposes the route without an @RolesAllowed restriction. The earlier cross-realm read-method guards did not cover this disconnect method, and same-realm users can also disconnect sessions they do not own. Session IDs are not trivially brute-forceable but may be exposed through monitoring, logs, or correlated API calls, and the unauthorized disconnect can disrupt MQTT connectivity across tenant boundaries without directly disclosing session data. This issue is fixed in 1.31.0.
    Severity: 0.0 | NA
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
  • CVE-2026-118977 - Cross-node trusted facts overwrite in PuppetDB facts terminus

    CVE ID :CVE-2026-118977
    Published : Nov. 19, 2026, 7:38 p.m. | 20 minutes ago
    Description :Authorization bypass through a user-controlled key in the PuppetDB facts terminus used by Puppet Server allows a client holding any valid agent certificate to overwrite the facts, including trusted facts, that PuppetDB stores for a different node. In Puppet Enterprise deployments where task permissions are scoped to node groups defined by facts or trusted facts, this can allow a user to run tasks on nodes outside their permitted scope.
    Severity: 7.3 | HIGH
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
  • CVE-2026-129926 - Authentication identity confusion via NUL-byte injection in SASL PLAIN credentials

    CVE ID :CVE-2026-129926
    Published : Nov. 19, 2026, 7:28 p.m. | 30 minutes ago
    Description :The MongoDB Python Driver does not neutralize NUL characters in the user name and password values it places into the message it builds for SASL PLAIN authentication. A party who can choose the login values that an application passes to the driver can alter where the fields of that message begin and end. This may result in a receiving system reading a login name and secret that differ from the values the application supplied. Authenticating as a different account still requires that account's password. Only deployments that use SASL PLAIN authentication are affected.
    Severity: 6.3 | MEDIUM
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
  • CVE-2026-129927 - Credential exposure via unmasked option value in Python driver object text output

    CVE ID :CVE-2026-129927
    Published : Nov. 19, 2026, 7:28 p.m. | 31 minutes ago
    Description :A credential-handling weakness in the MongoDB Python Driver allows a configuration option value that protects private key material to be written in clear text into the embedding application's own output and log records when a driver object is converted to text. A party able to read that output may obtain the credential. Obtaining it requires read access to the application's local output or log files.
    Severity: 5.7 | MEDIUM
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
  • CVE-2026-129925 - Authentication identity confusion via NUL-byte injection in SASL PLAIN credentials

    CVE ID :CVE-2026-129925
    Published : Nov. 19, 2026, 7:26 p.m. | 33 minutes ago
    Description :The MongoDB Ruby Driver does not neutralize NUL characters in the user name and password values it places into the message it builds for SASL PLAIN authentication. A party who can choose the login values that an application passes to the driver can alter where the fields of that message begin and end. This may result in a receiving system reading a login name and secret that differ from the values the application supplied. Authenticating as a different account still requires that account's password. Only deployments that use SASL PLAIN authentication are affected.
    Severity: 6.3 | MEDIUM
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
  • CVE-2026-129924 - Credential exposure via unmasked connection string in driver parse-error messages for the Ruby driver

    CVE ID :CVE-2026-129924
    Published : Nov. 19, 2026, 7:25 p.m. | 34 minutes ago
    Description :The MongoDB Ruby driver can include unmasked connection string content in the error it raises when a connection string cannot be parsed. If that connection string carries a secret, the secret may be disclosed in cleartext through the application's error output or logs. No privileges on the driver and no network access are needed to produce the error; a party able to read the application's error output may obtain the secret.
    Severity: 6.8 | MEDIUM
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
  • CVE-2026-129923 - Authentication identity confusion via NUL-byte injection in SASL PLAIN credentials

    CVE ID :CVE-2026-129923
    Published : Nov. 19, 2026, 7:23 p.m. | 36 minutes ago
    Description :The MongoDB Rust Driver does not neutralize NUL characters in the user name and password values it places into the message it builds for SASL PLAIN authentication. A party who can choose the login values that an application passes to the driver can alter where the fields of that message begin and end. This may result in a receiving system reading a login name and secret that differ from the values the application supplied. Authenticating as a different account still requires that account's password. Only deployments that use SASL PLAIN authentication are affected.
    Severity: 6.3 | MEDIUM
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
  • CVE-2026-129934 - Credential exposure via unmasked option values in Go driver connection string parse errors

    CVE ID :CVE-2026-129934
    Published : Nov. 19, 2026, 7:22 p.m. | 37 minutes ago
    Description :The MongoDB Go driver's connection string parser includes the raw, undecoded value of a query option in the error it returns when that value contains invalid percent encodings. When the option holds a secret, such as a TLS key file password or an AWS session token, the secret appears in plain text in the error. A party with low-privileged read access to wherever the application records or displays that error may learn the secret.
    Severity: 5.7 | MEDIUM
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
  • CVE-2026-129935 - Authentication identity confusion via NUL-byte injection in SASL PLAIN credentials

    CVE ID :CVE-2026-129935
    Published : Nov. 19, 2026, 7:21 p.m. | 38 minutes ago
    Description :The MongoDB Go Driver does not neutralize NUL characters in the user name and password values it places into the message it builds for SASL PLAIN authentication. A party who can choose the login values that an application passes to the driver can alter where the fields of that message begin and end. This may result in a receiving system reading a login name and secret that differ from the values the application supplied. Authenticating as a different account still requires that account's password. Only deployments that use SASL PLAIN authentication are affected.
    Severity: 6.3 | MEDIUM
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
  • CVE-2026-129930 - Credential exposure via unmasked connection string in driver parse-error messages for the Node driver

    CVE ID :CVE-2026-129930
    Published : Nov. 19, 2026, 7:18 p.m. | 41 minutes ago
    Description :A weakness in the MongoDB Node.js driver can place sensitive information taken from an application-supplied connection string into the text of an error produced while that connection string is being parsed. The error is generated inside the application process before any database connection is made, so no database account and no network access are needed for it to occur. A party able to read the application's error output or log files may thereby obtain database credentials that the application's configuration source would otherwise keep to a narrower audience.
    Severity: 5.7 | MEDIUM
    Visit the link for more details, such as CVSS details, affected products, timeline, and more...
| Date published: Thu, 19 Nov 2026 19:42:46 +0000
Back to newsfeed list