Export limit exceeded: 429957 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429957 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429957 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-130442 | 2026-11-20 | 5.5 Medium | ||
| Multiple protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-130443 | 2026-11-20 | 5.5 Medium | ||
| Multiple protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-130440 | 2026-11-20 | 5.5 Medium | ||
| Multiple protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-49756 | 1 Wojtekmach | 1 Req | 2026-11-20 | 3.7 Low |
| Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in wojtekmach Req allows multipart parameter smuggling via attacker-influenced part metadata. Req.Utils.encode_form_part/2 in lib/req/utils.ex builds the per-part headers by interpolating the caller-supplied name, filename, and content_type values directly into the content-disposition and content-type lines with no escaping or CRLF stripping. A value containing ", \r, or \n closes the surrounding quoted value and starts a new header line; an additional \r\n--<boundary> terminates the current part and prepends a smuggled part of the attacker's choosing. This is reachable through every supported way of supplying a part. It is particularly easy when value is a %File.Stream{}, because filename then defaults to Path.basename(stream.path) and POSIX filenames may legitimately contain \r and \n. Any application that forwards user-controlled filenames (or field names / MIME types) through Req.post/2 with form_multipart: lets an attacker inject arbitrary headers into the outgoing multipart body or smuggle additional fields and parts into the request the victim service sends downstream. This issue affects req: from 0.5.3 before 0.6.0. | ||||
| CVE-2026-133625 | 2026-11-20 | 5.5 Medium | ||
| iLBC audio codec crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-130439 | 2026-11-20 | 5.5 Medium | ||
| Multiple protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-130441 | 2026-11-20 | 5.5 Medium | ||
| Dissection engine crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-130438 | 2026-11-20 | 5.5 Medium | ||
| Multiple protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-133624 | 2026-11-20 | 5.5 Medium | ||
| SCTP protocol dissector heap disclosure in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 might enable denial of service or code execution | ||||
| CVE-2026-130444 | 2026-11-20 | 5.5 Medium | ||
| PROFINET protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-130437 | 2026-11-20 | 5.5 Medium | ||
| Multiple protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-130436 | 2026-11-20 | 5.5 Medium | ||
| Multiple protocol dissector memory leaks in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-130435 | 2026-11-20 | 5.5 Medium | ||
| SDP protocol dissector crash in 4.6.0 to 4.6.9 allows denial of service | ||||
| CVE-2026-130434 | 2026-11-20 | 5.5 Medium | ||
| Protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service | ||||
| CVE-2026-49755 | 1 Wojtekmach | 1 Req | 2026-11-20 | 7.5 High |
| Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in wojtekmach Req allows attacker-controlled HTTP servers to exhaust memory in a Req client via decompression-bomb response bodies. Req's default response pipeline includes Req.Steps.decode_body/1 and Req.Steps.decompress_body/1 in lib/req/steps.ex. decode_body/1 dispatches on the server-supplied content-type (or URL extension) and calls :zip.extract(body, [:memory]) for application/zip, :erl_tar.extract({:binary, body}, [:memory]) for application/x-tar, and :erl_tar.extract({:binary, body}, [:memory, :compressed]) for application/gzip / .tgz. Each returns the full decompressed archive contents as a [{name, bytes}] list in memory, with no per-entry or total size cap. decompress_body/1 walks the content-encoding header and chains :zlib/:brotli/:ezstd decoders, so a response advertising content-encoding: gzip, gzip, gzip inflates through multiple layers without bound. Both steps are enabled by default, no caller opt-in is required, and the attacker controls the content-type and content-encoding headers on their own server (or on any host reached via Req's automatic redirect following). A sub-megabyte response can expand to multiple gigabytes on the victim, crashing the BEAM process. This issue affects req: from 0.1.0 before 0.6.1. | ||||
| CVE-2026-131727 | 2026-11-20 | 6.5 Medium | ||
| Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Blubrry Podcasting PowerPress Podcasting powerpress allows Stored XSS.This issue affects PowerPress Podcasting: from n/a through 11.18.4. | ||||
| CVE-2026-49754 | 1 Elixir-mint | 1 Mint | 2026-11-20 | N/A |
| Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client (HTTP/2 CONTINUATION flood). When Mint's HTTP/2 receive path observes a HEADERS frame without the END_HEADERS flag, the unparsed header-block fragment is parked in conn.headers_being_processed, and every subsequent CONTINUATION frame on that stream is appended to the accumulator. Nothing in the receive path caps the accumulator: there is no per-stream size limit, no CONTINUATION frame-count limit, and max_header_list_size is only enforced on outgoing requests, never on inbound header blocks (its default is :infinity). A malicious or compromised HTTP/2 server can stream an endless sequence of CONTINUATION frames (each up to the peer-advertised SETTINGS_MAX_FRAME_SIZE) and drive the client's iolist to arbitrary size, causing memory exhaustion and BEAM process death. A single connection to an attacker-controlled HTTP/2 endpoint is sufficient. This issue affects mint: from 0.1.0 before 1.9.0. | ||||
| CVE-2026-131757 | 2026-11-20 | 5.3 Medium | ||
| Insertion of Sensitive Information Into Sent Data vulnerability in WProyal Royal Elementor Addons royal-elementor-addons allows Retrieve Embedded Sensitive Data.This issue affects Royal Elementor Addons: from n/a through 1.7.1069. | ||||
| CVE-2026-130625 | 2026-11-20 | 5.3 Medium | ||
| Insertion of Sensitive Information Into Sent Data vulnerability in Metaphor Creations, LLC Ditty ditty-news-ticker allows Retrieve Embedded Sensitive Data.This issue affects Ditty: from n/a through 3.1.73. | ||||
| CVE-2026-49753 | 1 Elixir-mint | 1 Mint | 2026-11-20 | N/A |
| Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in elixir-mint Mint allows attacker-controlled HTTP/1 servers to desynchronise response framing on shared connections. Mint's HTTP/1 Content-Length parser, Mint.HTTP1.Parse.content_length_header/1 in lib/mint/http1/parse.ex, parses the header value with Integer.parse/1, which accepts an optional + or - sign prefix. The length >= 0 guard rejects negatives, but inputs such as +0 or +123 are returned as valid lengths. RFC 7230 specifies Content-Length = 1*DIGIT, with no sign character permitted. A fronting proxy or load balancer that strictly enforces the grammar will reject or reframe a header like Content-Length: +0, while Mint silently treats it as zero. When Mint reuses the socket (keep-alive, pipelining, or any pooled connection shared across requesters), the parser disagreement is a response-smuggling primitive: the proxy delimits the body one way, Mint another, and bytes from one response get attributed to the next. Where the same Mint connection is shared across trust boundaries, an attacker-controlled upstream can leak bytes into a different consumer's response stream. This issue affects mint: from 0.1.0 before 1.9.0. | ||||