Export limit exceeded: 429114 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (714 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-129930 | 2026-11-19 | 4.7 Medium | ||
| 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. | ||||
| CVE-2026-129939 | 2026-11-19 | 5.5 Medium | ||
| The MongoDB C Driver places a submitted connection-string option value into a diagnostic message without redaction when that option fails validation. The message is returned to the calling application and is also written to the process's standard error by the driver's default logging behavior. A party that can influence the connection string given to an application using the driver may cause that field's contents to be recorded, which may result in unintended disclosure of information the application placed in that field. | ||||
| CVE-2026-129924 | 2026-11-19 | 5.5 Medium | ||
| 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. | ||||
| CVE-2026-129934 | 2026-11-19 | 4.7 Medium | ||
| 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. | ||||
| CVE-2026-129928 | 2026-11-19 | 5.5 Medium | ||
| The MongoDB PHP extension includes the full connection string it was given in the error it raises when that string cannot be parsed. A party able to influence any part of the connection string, including a part that holds no secret, can cause the resulting message to carry credentials into the application's standard error output and log files. This may result in unintended disclosure of authentication material to anyone able to read that output. | ||||
| CVE-2026-120298 | 2026-11-19 | 5.3 Medium | ||
| InfoScan fails to properly handle certain malformed or incomplete requests to its login and password-reset endpoints. These requests can trigger unhandled server exceptions that return detailed Node.js stack traces to the requester. The responses disclose internal filesystem paths, application directory names, source file locations, and line numbers. | ||||
| CVE-2026-108316 | 1 Tanium | 2 Server, Tanium Server | 2026-11-19 | 4.3 Medium |
| Tanium addressed an information disclosure vulnerability in Tanium Server. | ||||
| CVE-2026-78693 | 1 Ash-project | 1 Ash Graphql | 2026-11-19 | N/A |
| Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_graphql allows a remote client to read internal field names that an application configured its error_handler to redact. In AshGraphql.Errors, each error is passed to the configured error_handler and the returned map is merged with the pre-handler path via Map.put_new(handled, :path, path). Because put_new defers to the handler only when the handler itself set :path, a sanitizing handler that returns a fresh map or deletes :path has that decision reverted. The re-injected path comes from build_error_path/5, which falls back to raw internal Ash attribute and argument names when no field_names mapping is configured. A validation failure on a non-exposed or nested field therefore returns internal names in the GraphQL error path, defeating the application's redaction. This issue affects ash_graphql: from 1.9.0 before 1.11.0. | ||||
| CVE-2026-82580 | 1 Ash-project | 1 Ash Ai | 2026-11-19 | N/A |
| Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_ai discloses internal error text to chat users. In AshAi.ToolLoop and AshAi.Tools, an exception raised while executing a tool was serialized verbatim with Exception.message/1 into the tool-result content. That content is appended to the conversation, emitted as a {:tool_result, ...} stream event, and sent back to the model, which typically relays it to the user. No filtering happened first, so anything raised inside a tool callback or lifecycle hook (database constraint messages, adapter errors, query fragments, policy or validation internals) was echoed as-is. A chat user who can steer tool arguments into a raising code path receives the raw internal text. The fix routes raised tool errors through the same safe formatter used for other tool errors. This issue affects ash_ai: from 0.6.0 before 1.0.0. | ||||
| CVE-2026-75760 | 1 Ash-project | 1 Ash Ai | 2026-11-19 | N/A |
| Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_ai discloses provider request state and credentials in a user-facing validation error. In AshAi.Changes.Vectorize, when the embedding provider call fails the change added a changeset error whose message inspected the raw error term (An error occurred while generating embeddings: #{inspect(error)}). A plain-string add_error produces an Ash.Error.Changes.InvalidChanges in the :invalid class, which AshJsonApi and AshGraphql render back to the caller. The embedding client's error term is not sanitized, so it can carry the request URL, the provider response body, and, for HTTP clients that keep the request in the error struct, the outbound Authorization header with the provider API key. Failures are attacker-reachable via oversized or malformed vectorized content. The fix logs the raw error and returns a generic message. This issue affects ash_ai: from 0.1.0 before 1.0.0. | ||||
| CVE-2026-82727 | 1 Ash-project | 1 Ash Phoenix | 2026-11-19 | N/A |
| Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_phoenix writes the entire raw submitted param map into an exception message, so secrets submitted alongside a union form field leak into logs, crash reports and the dev error page. When AshPhoenix.Form.Auto builds a union sub-form and the submitted _union_type does not match a configured type, both raise sites built the message with inspect(params, pretty: true), embedding the full untrusted param map, and also inspected the internal union constraints[:types]. Because the message is constructed by the library rather than Phoenix's parameter logger, config :phoenix, :filter_parameters never redacts it. An attacker controls both the trigger and the contents: submitting %{"_union_type" => "nope", "password" => "..."} puts the password verbatim in the raised message. The fix reports only the offending _union_type and the valid type names, dropping the param and constraints dumps. This issue affects ash_phoenix: from 1.2.17 before 2.3.25. | ||||
| CVE-2026-77950 | 1 Ash-project | 1 Ash Typescript | 2026-11-19 | N/A |
| Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_typescript allows an unauthenticated attacker to receive unredacted internal error data by provoking an error shape the configured error handler does not match. apply_error_handler/3 in lib/ash_typescript/rpc/errors.ex is the only hook an application has for redacting or suppressing errors before they reach the client, with a nil return dropping the error entirely. Its rescue clause logs a warning and then returns the original, pre-handler error map. Error handlers are conventionally written as pattern-matching functions over expected error shapes, so an unmatched shape raises FunctionClauseError and the raw transformed error, including any secrets carried in vars, is emitted instead. An intent to suppress an error becomes an intent to publish it. The rescue catches exceptions only, so a handler that throws or exits still propagates. This issue affects ash_typescript: from 0.8.0 before 0.18.0. | ||||
| CVE-2026-82733 | 1 Ash-project | 1 Ash Typescript | 2026-11-19 | N/A |
| Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_typescript allows an unauthenticated attacker to read internal application data from an HTTP 500 response body. When a typed-controller route handler returns anything other than a %Plug.Conn{}, dispatch/3 in lib/ash_typescript/typed_controller/request_handler.ex passes the value to unexpected_return/2, which interpolates inspect(value, limit: 50) directly into the response message. The limit option bounds elements per collection rather than the term as a whole, so a handler falling through with a term such as {:error, %User{}} or a changeset serialises its full field set, including hashed passwords, tokens, and tenant identifiers, into the JSON error returned to the caller. This contradicts the module's own posture elsewhere: the rescue clause gates Exception.message/1 behind AshTypescript.typed_controller_show_raised_errors?/0 and otherwise returns a generic message, while this path is ungated and always echoes. This issue affects ash_typescript: from 0.15.0 before 0.18.0. | ||||
| CVE-2026-82739 | 1 Ash-project | 1 Ash | 2026-11-19 | N/A |
| Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash discloses the stored value of a confirmed field to an actor who fails its confirmation check. Ash.Resource.Validation.Confirm's atomic implementation (atomic/2 in lib/ash/resource/validation/confirm.ex) built the mismatch error with its value set to the field being confirmed. When the actor supplies only the confirmation argument and not the field itself, value resolves through atomic_ref/2 to the field's current stored value, so the mismatch error echoes that stored value back to the actor. Against a confirmation guarding a sensitive attribute, an actor can submit a deliberately wrong confirmation and read the real value from the returned error. The fix reports the actor-supplied confirmation in the error instead of the stored field value. This issue affects ash: from 2.17.20 before 3.32.2. | ||||
| CVE-2026-125160 | 1 Typo3 | 2 Typo3, Typo3 Cms | 2026-11-17 | N/A |
| Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. If storing an uploaded file failed, for example because of a file name exceeding the file system's length limit, the raw error message was shown to the frontend user disclosing the storage path including the unguessable folder name and the server's temporary upload directory. With this information, attackers could determine the public URL of files they upload through the form. If a form allows uploading files that browsers can execute, such as HTML documents, this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder. This vulnerability is known to be actively exploited. | ||||
| CVE-2026-113456 | 1 Visualnet | 1 Visualticket | 2026-11-17 | N/A |
| visualTicket exposes sensitive information in error messages in the cinema report generator. An authenticated attacker with an admin privileges can supply an invalid date_from value causing the application to return a detailed error page that discloses the full SELECT statement (table and column names, JOIN, GROUP BY and ORDER BY clauses, bind parameter placeholders) and a PHP DateTime parsing exception. This issue was fixed in version 20260817. | ||||
| CVE-2026-113454 | 1 Visualnet | 1 Visualticket | 2026-11-17 | N/A |
| visualTicket exposes sensitive information in error messages in the administrative report generator. Because application exception details and SQL queries are rendered in the HTTP response in the production environment, an authenticated administrator submitting an invalid date_from value in the report request receives a detailed error page disclosing the full SELECT statement, table and column names, JOINs, bind parameters, and a PHP DateTime exception. This issue was fixed in version 20260817. | ||||
| CVE-2026-123871 | 1 Nodejs | 1 Nodejs | 2026-11-16 | 6.2 Medium |
| Node.js discloses proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. CVE-2026-48615 established that a proxy credential must not appear in a Node.js error message and redacted the username and password from ProxyConfig.href, but that fix missed four error paths in the same subsystem, one of them inside the same constructor, which interpolate the raw proxy URL, credentials included, into an ERR_PROXY_INVALID_CONFIG message. The proxy URL comes from the environment, but the defect is the sink: a secret that Node.js redacts everywhere else is emitted verbatim into a much wider audience than the process environment, such as stderr, container logs, log aggregation, and crash reporting services. This vulnerability affects Node.js 26.x, 24.x, and 22.x. | ||||
| CVE-2026-113445 | 1 Visualnet | 1 Visualticket | 2026-11-16 | N/A |
| visualTicket is vulnerable to information exposure through an error message in the order creation functionality. Because detailed data-layer exceptions are returned to the client instead of being logged server-side only, a remote unauthenticated attacker can submit a valid checkout request with an invalid payment_type value, causing the application to return a detailed SQL/ORM error that discloses the database name, table and column names, query structure, and foreign key constraint name. This issue was fixed in version 20260817. | ||||
| CVE-2026-126991 | 1 Misp | 1 Misp-modules | 2026-11-16 | N/A |
| The Wikidata Lookup expansion module (wiki.py) in MISP misp-modules contained a SPARQL injection vulnerability. The handler function constructed a SPARQL query by directly concatenating the user-supplied text value into the query string without any escaping or parameterization: 'SELECT ?item WHERE { ?item rdfs:label"' + request.get("text") + '" @en }'. An authenticated MISP user with access to the module could supply a crafted text attribute value containing SPARQL syntax (quotes, closing braces, UNION, SERVICE, LIMIT, etc.) to alter the structure of the query sent to the Wikidata SPARQL endpoint. This could allow an attacker to modify the query logic, extract unintended data, or cause the query to fail in ways that expose internal error details. Additionally, the old error handling path formatted raw exception objects into the response string ('wikidata API not accessible {}'.format(e)), potentially leaking internal information such as proxy credentials, query contents, or response bodies. The module also used a spoofed browser user-agent string and the deprecated Wikidata endpoint. The vulnerability required authenticated access to the MISP instance and the ability to invoke the wiki expansion module with a text attribute. The impact is limited to manipulation of the enrichment query and potential disclosure of internal error details; it does not directly compromise the MISP server or its stored data. | ||||