Unauthenticated retrieval of cached service mesh leaf certificates and their private keys affects HashiCorp Consul and Consul Enterprise 1.17.0 through 2.0.4 through the agent's service mesh leaf certificate API, which fails to enforce ACL authorization (CWE-862). A remote attacker who can reach the affected agent API can obtain the certificate and private key for services whose leaf certificates are already cached, allowing impersonation of those mesh services without a valid ACL token or user interaction. HashiCorp has released fixes in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19; no public exploit code or CISA KEV entry was identified at time of analysis, and the issue is prioritized for remediation this week.
Routinator, NLnet Labs' RPKI relying-party validator, can be driven into memory exhaustion by an AS range in RPKI data whose maximum value is lower than its minimum, leaving the validator unable to continue. The issue is remotely reachable without authentication per the CVSS vector and affects availability only; exploitation requires an attacker to place the malformed range into RPKI objects that a target Routinator instance fetches and validates. No CISA KEV entry or public exploit code is identified in the supplied data.
Routinator exits when it encounters an RRDP-delivered rsync URI whose path cannot be stored on disk, producing a denial of service in RPKI validation. The flaw affects Routinator instances that fetch repository content over RRDP (the default transport) and validate a publication point the attacker operates, compromises, or otherwise controls; an arbitrary off-path attacker cannot trigger it. The assessed impact is availability-only (CVSS 7.5), with no confidentiality or integrity effect, and no public exploit identified at time of analysis.
Routinator, NLnet Labs' RPKI relying-party validator, can be hung or terminated by a CRL fetched from the repository hierarchy it validates: a CRL carrying a very large number of entries drives the hang or out-of-memory path, while a CRL with an incorrect encoding causes the process to exit, producing an availability-only denial of service (CVSS 7.5, A:H, with no confidentiality or integrity impact). The CPE entry cpe:2.3:a:nlnet_labs:routinator is unversioned, so all releases are presumed affected until the vendor advisory names fixed versions. No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical barrier is that an attacker must be able to serve the crafted CRL from a repository or CA inside a trusted RPKI validation path, and no authentication to Routinator itself is required.
Process abort denial of service in the Rust `zip` crate (versions 1.3.0 through 8.x) allows a tiny, crafted archive to kill any application that calls `ZipArchive::extract()` on untrusted input. The symlink branch of extraction reserves a buffer using the attacker-declared ZIP64 `uncompressed_size` before reading a single byte; `Vec::with_capacity` is infallible, so a 112-byte archive declaring 2^62 bytes terminates the process via `SIGABRT` - an abort that `catch_unwind`, `panic = "unwind"` and worker-thread isolation all fail to contain. Impact is availability only (C:N/I:N/A:H, 7.5); the vendor GHSA publishes a public reproducer, no confirmed active exploitation is reported in the available data, and the flaw is fixed in 9.0.0.
Denial of service in the Rust zip2 crate affects versions 5.1.0 through 8.x when an application is built with the opt-in `legacy-zip` feature and extracts an attacker-supplied archive containing a Shrink, Reduce, or Implode entry with a forged ZIP64 uncompressed size. The declared size is passed to `Vec::reserve` before the compressed stream is validated, causing a deterministic capacity-overflow panic (CWE-400/CWE-789) that can terminate the archive-processing process. The issue is fixed in 9.0.0; a public proof-of-concept reproducer is documented in the GHSA advisory, there is no CISA KEV confirmation in the provided intelligence, and exposure is limited by the non-default `legacy-zip` build configuration and a `ZipArchive::extract()`-style read path.
XML external entity (XXE) processing in Apache Camel's camel-saxon XQuery support lets remote unauthenticated attackers read files readable by the Camel process and make the process issue requests to attacker-named hosts when untrusted XML is evaluated as a stream-based javax.xml.transform.Source. The flaw affects Apache Camel 4.0.0 through 4.18.4 and 4.19.0 through 4.22.1; String, byte[] and InputStream bodies are not exposed because Camel's XML converters are already hardened. Vendor patches are available in 4.23.0, with branch fixes in 4.22.2 and 4.18.5, and no public exploit has been identified at time of analysis.
Password-protected private-key exports produced by the Erlang/Elixir `jose` library between 1.10.0 and 1.11.12 are encrypted with a hardcoded, drastically under-strength key-derivation step, so anyone who obtains such an exported blob can crack the export password offline at roughly 300 times less cost than modern guidance intends and recover the full private key. Only the password-based export path is affected (JOSE.JWK.to_der/2, jose_jwk:to_der/2, the PEM equivalents and their _file variants); the attack requires possession of the exported DER/PEM file and succeeds only where the export password is weak or moderate, since a long randomly generated password still resists 2048 PBKDF2 iterations. EPSS is very low (0.06%) and there is no KEV listing, but a public proof-of-concept script accompanies the upstream advisory; a public PoC reference exists and demonstrates parameter extraction plus dictionary recovery, though it is not verified here as working exploit code. The vendor fixed the parameters in 1.11.13, and the CVSS vector indicates no privileges are required (PR:N), with the practical gating factors being blob exposure and password strength rather than any network-reachable interface.
Arbitrary file write outside the extraction directory in the Rust zip2 crate 7.2.0 through 9.0.0 lets a crafted ZIP create or overwrite files with the extracting process's privileges when an application calls ZipArchive::extract or ZipArchive::extract_unwrapped_root_dir. The symlink-target check is purely lexical, so an attacker who knows or can guess the absolute destination path can supply a chain whose apparent target stays under the destination while an intermediate link resolves outside it; on Windows a single link is enough because drive and UNC prefixes are discarded, provided the extracting process holds SeCreateSymbolicLinkPrivilege. The GitHub advisory ships proof-of-concept reproduction detail, including a real-hardware Windows test, but no CISA KEV entry exists and public working exploit code is not confirmed in the supplied data; severity is rated 7.4 with AC:H reflecting the destination-path precondition.
Seroval deserialization can invoke attacker-chosen callables when an application passes untrusted input to fromJSON and registers a plugin whose deserialize result is a function or an object exposing an on method; a crafted AsyncIteratorFactoryInstance node reuses an identifier so the rebuild calls source.on(listener) on that plugin-produced value. All versions through 1.6.7 are affected, although 1.6.4 through 1.6.7 block the originally reported payload only to remain bypassable via node-id reuse. Practical risk is constrained by the non-default plugin prerequisite and by what the plugin's own callable does, and no public exploit was identified at time of analysis; version 1.6.8 fixes the flaw.
SQL injection in Dolibarr ERP CRM 19.0.0 through 23.0.3 (fixed in 23.0.4) allows an authenticated REST API user holding only the low-privilege societe/creer (third-party creation) permission to break out of the unescaped 'type' value when creating a company bank account. The injected payload reaches an unescaped string concatenation in CompanyBankAccount::create() and can be used in time-based blind subqueries to read password hashes and API keys from the database. Exploitation requires the REST API to be enabled and reachable plus valid credentials with that specific permission, so this is a conditional, credentialed attack rather than a drive-by one; no public exploit code has been identified at time of analysis and the vulnerability is not in CISA KEV.
A heap use-after-free in Asterisk's PJSIP TCP/SDP handling lets an authenticated SIP user crash the process by sending an INVITE over a connection-oriented transport and dropping the TCP connection before Asterisk returns 200 OK, giving availability impact only. Reproduction so far requires an Address Sanitizer build, which the maintainer states is never used in production, so a crash against standard production binaries is not demonstrated in the available sources. Scoring signals conflict sharply - the published CVSS 4.0 score is 7.1 while the assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L - and no public exploit code or active exploitation is reported.
Case-sensitivity defects in MISP Guard's feed-distribution policy checks allow an authenticated MISP event creator to slip events past configured TLP taxonomy, allowed-tag, blocked-attribute-category and blocked sharing-group rules simply by changing the letter case of a tag, category or UUID string, with the result that threat-intelligence data the operator meant to restrict is still forwarded to feed consumers. Only deployments running misp-guard 1.3 or earlier that actually rely on these allow/block policies are exposed, and the impact is confidentiality-only - no integrity or availability effect. No public exploit code was identified at time of analysis; the vendor has published an upstream fix commit (9868b1d9) that normalizes case on both sides of every affected comparison and adds regression tests reproducing the bypass.
Local-network attackers can cause unexpected system termination or process memory corruption on Apple macOS versions before 15.8.2, 26.7.2, and 27.2 by triggering a double-free memory-management bug. The issue is fixed in macOS Sequoia 15.8.2, macOS Tahoe 26.7.2, and macOS Golden Gate 27.2, and no public exploit has been identified at time of analysis; EPSS is low at 0.35% and CISA KEV status is not indicated.
A NULL pointer dereference in libcss through 0.9.2 lets remote attackers crash any application that parses an attacker-supplied stylesheet whose @media or @import media query list ends in a trailing comma, taking down NetSurf and other embedders of the library. The fault sits in mq_parse_media_query() (src/parse/mq.c), where the final iteration of the media-list loop hands a NULL token to a branch that dereferences it unchecked; the regression tests added with the fix ('@media),', '@media ),,,', '@media (color),') confirm the exact trigger. Impact is availability only - a client-side parse-time crash with no code execution or data disclosure, and it requires the victim to load the hostile CSS (passive user interaction). No confirmed public exploit code was identified at time of analysis, though a public technical writeup describing the dereference exists; EPSS is low at 0.33% (26th percentile) and there is no CISA KEV listing, so this is a moderate-priority denial-of-service issue rather than a top-tier emergency.
YesWiki releases up to and including 4.6.7 let a self-registered, low-privileged account read wiki pages and Bazar entries whose read ACLs are restricted to other users or groups. The flaw is a read-ACL bypass: AclService builds its access filter with a SQL LIKE pattern built from the account name, and the escaping applied (mysqli_real_escape_string) neutralises quotes but not the LIKE metacharacters _ and %, so a name such as '___' or '%%%' over-matches ACL tokens it was never granted. Exploitation is confirmed to require only self-registration (on by default) plus a call to the public Bazar listing API; the upstream advisory includes reproduction steps but no independently verified working exploit code is referenced, EPSS is low at 0.28% (20th percentile), and there is no CISA KEV entry. Impact is confidentiality-only - no write or availability effect was demonstrated, and the practical exposure depends on access-restricted Bazar entries actually existing on the target.
OpenPanel before 3.0.0 leaks secrets into standard-output logs through two separate code paths, allowing anyone who can read application, container, CI or centralized logs to recover sensitive data. Database migration startup banners print the full DATABASE_URL and CLICKHOUSE_URL including user-info credentials and credential-like query parameters, and the email fallback path used when both SMTP_HOST and RESEND_API_KEY are unset serializes the recipient address, subject and full template data - which for the password-reset flow includes the reset-token URL. Exploitation is not remote against the service itself: it requires pre-existing read access to log stores plus, in the migration case, that the code-migration command was run, or, in the email case, the non-default double-unset provider configuration and a triggered email flow; no public exploit code is identified at time of analysis and EPSS is low (0.28%, 20th percentile), consistent with a moderate-priority information exposure rather than an emergency.
SQL injection in OpenPanel's conversion analytics query allows project-read members and share-link holders to read other tenants' ClickHouse analytics data. Before version 3.0.0, ConversionService.getConversion interpolates series event names and startDate/endDate values raw inside single quotes, so a payload such as x' OR 1=1 neutralizes the project_id tenant scoping; the projectId value itself is passed through sqlstring.escape, so the omission is confined to the event-name and date fields. Exploitation requires an authenticated low-privilege actor (CVSS 4.0 PR:L) or a valid share link, and cross-tenant impact depends on a multi-tenant deployment in which the ClickHouse reader credential can read all rows. The advisory includes a PoC payload description that is not verified as working exploit code; SSVC records exploitation as none and EPSS is 0.23% (14th percentile), so this is a real but moderate-priority exposure focused purely on confidentiality.
SQL injection in OpenPanel's cohort preview query lets any user holding project-read access on any project read ClickHouse data belonging to other tenants; this is a genuine but access-gated data-disclosure issue rather than a drop-everything emergency. The flaw is confined to the ClickHouse analytics backend (the default) in multi-tenant deployments, requires a valid low-privileged account (authenticated, project READ only, no write or admin role), and affects OpenPanel versions before 3.0.0. Exploitation permits read-only cross-tenant disclosure with no integrity or availability impact, there is no CISA KEV listing, EPSS is low at 0.23% (14th percentile), and a public PoC reference exists in the vendor advisory (a cohort.preview payload using operator isNotNull with an empty value array); it is not verified as working exploit code. A vendor patch is available, and the source-level fix is to apply the PROFILE_COLUMNS allowlist to profileColumnAccess.
Unauthenticated screen-content disclosure in WolfVision Cynap Pro and Cynap Core Pro devices with vSolution Matrix enabled lets hosts on the same network segment view or capture the current presentation through an unencrypted RTSP/RTP stream. The issue affects versions below 1.78a and is limited to confidentiality; the vendor has released 1.78a, and no public exploit was identified at time of analysis. Exposure is bounded by the non-default Matrix feature requirement and network adjacency.
Bluetooth Object Transfer Service (OTS) servers in Zephyr (>= 3.3.0 through <= 4.4.2) mishandle failed Calculate Checksum responses: oacp_ind_send() appends a four-byte Checksum Value field based only on the requested op code, then calls net_buf_simple_pull_le32() on a zero-length stack buffer whenever validation failed. Any peer within radio range can abuse this with a nine-byte OACP write and no pairing, encryption or authentication, because the OACP characteristic and its CCC are exposed with unauthenticated write permissions. On CONFIG_ASSERT builds the zero-length pull trips the assertion in net_buf_simple_pull_mem() and panics the device (remote DoS); with assertions compiled out the same path copies four bytes of uninitialized stack memory into the indication sent to the peer, repeatable per request and bounded to four bytes with no memory corruption; the reporter's reproducer demonstrates the panic and no public exploit tooling beyond it is confirmed.
The Mosquitto MQTT broker baked into boneIO black_debian_images uses one shared default username/password across every device, and those credentials are published on GitHub with no instruction to change them. Any host that can reach the broker on the same LAN/Wi-Fi segment can connect unauthenticated in the CVSS sense (PR:N - no prior account or privilege needed) by simply presenting the published defaults, gaining full read and write access to the broker and therefore control over connected relays, blinds and gates, plus the ability to inject fake entities into a linked Home Assistant instance. Version 1.6.0 generates per-device MQTT passwords at first boot, but devices upgraded from earlier images keep their old broker credentials, so the flaw persists until the owner manually changes them; no public exploit code was identified at time of analysis, and the CERT-PL report is prioritised as 'this_week'. The vendor's CVSS 4.0 score is 7.1 (AV:A/AC:L/PR:N/UI:N/VC:H/VI:N/VA:N), which understates the described write/integrity and potential physical-safety consequences.
Cross-site request forgery in the Webasyst Framework Photos app through 4.4.0 allows a malicious page to submit forged POST requests as a logged-in backend user, deleting photos and changing access rights. The Photos app does not enable the framework's opt-in CSRF check, and exploitation requires the victim to hold an active authenticated session and to be induced into loading the attacker's page; the attacker needs no privileges of their own (PR:N), but the victim interaction prevents unattended mass exploitation. Impact is confined to the photo/delete, album/save, photo/manageAccessSave and photo/saveField endpoints with high integrity impact and no confidentiality or system-level effect; this is a moderate, not emergency, priority and no public exploit was identified at time of analysis.
Blind SQL injection in the Mautic dashboard widget data API (/api/data/{type}) allows an authenticated account holding API access to read arbitrary contents of the Mautic database, including contact and marketing records and user accounts with password hashes. Exploitation requires two conditions to hold simultaneously: the Mautic API must be enabled on the instance, and the attacker must hold a valid account with API access (CVSS PR:L); no unauthenticated path exists, and instances with the API disabled or restricted to trusted users are not exploitable. Integrity impact is none - data modification is not possible - while availability impact is limited to attacker-induced query slowdowns; no public exploit code or CISA KEV entry was identified at time of analysis, and the vendor has released fixed versions 7.2.2, 6.0.10 and 5.2.12.
Authenticated SQL injection in Mautic's contact lookup AJAX endpoint (/s/ajax) allows any valid user account, regardless of role or assigned permissions, to run blind boolean-based or time-based queries against the Mautic database and read data the database user can access, including user email addresses and password hashes, contact records, and campaign and email content. The flaw affects Mautic releases from 2.1.0 before 5.2.12, 6.0.x before 6.0.10, and 7.0.x before 7.2.2; anonymous access is not sufficient because a valid account is required. No public exploit code has been identified at time of analysis, and the priority signal is this_week rather than an emergency.
Missing authorization in Frappe CRM before 1.89.1 lets an authenticated low-privileged user read CRM Lead records they are not permitted to see by supplying a known phone number to the crm.integrations.api.get_contact_by_phone_number endpoint, which resolves matches with raw database queries instead of the permission system. Any user holding a valid session and a low-privilege role (the patch's tests use a 'Sales User' account) can enumerate phone numbers to disclose lead details otherwise blocked by standard API and UI controls; no public exploit was identified at time of analysis and the issue is not in CISA KEV. Severity is high for confidentiality (CVSS 7.1 in the 4.0 scoring, with the assessed 3.1 vector at AV:N/AC:L/PR:L/UI:N/C:H) but the impact is disclosure-only and requires a known or guessed phone number per record, which keeps this a moderate-priority, patch-this-week item rather than an emergency. The vendor shipped a fix in v1.89.1.
Out-of-bounds reads in the SOEM EtherCAT master library (2.0.0 and earlier) let a malicious or compromised device on the same EtherCAT segment make the master read past the end of allocated buffers, disclosing memory contents or crashing the master process. No authentication or user interaction is required, but the attack surface is confined to the adjacent Layer-2 fieldbus segment - typically an isolated OT control network rather than anything internet-routable. No public exploit code or confirmed in-the-wild exploitation is identified in the available data, and the vuln.today decision label is this_week, reflecting a genuine but bounded industrial/OT priority rather than an internet-wide emergency.
OpenPanel deployments before 3.0.0 are exposed to SQL injection through the tRPC `event.events` query, which splices an unconstrained `profile.*` filter name directly into the profiles-JOIN subquery, letting any authenticated user with read access to a single project comment out the `WHERE project_id` scoping and read events (path, country, city, profile_id, revenue) from every other tenant. The same unsanitized JOIN construction also appears in `getEventsCount` and the funnel service, so the exposure is not limited to a single endpoint. A public PoC reference with reproduction steps accompanies the GitHub advisory (GHSA-pc3q-gw7f-p2x2); it is not verified as working exploit code and there is no KEV entry. EPSS is low at 0.27% (19th percentile), and the vendor fixed the flaw with an allowlist in the 3.0.0 release.
SQL injection in the @aws-cdk/aws-redshift-alpha database-query custom resource handlers, affecting versions before 2.274.0-alpha.0, lets an actor who can influence construct property values - specifically the user name, comment, or password fields - execute arbitrary SQL against Amazon Redshift with superuser privileges, including granting access to all cluster users. The assessed vector is local with low privileges and required user interaction: a CDK stack deployment must actually run with the attacker-influenced values, so this is not remotely reachable against a running service and deployments built only from trusted, static property values are not realistically exposed. AWS has released 2.274.0-alpha.0 to address the flaw, and no public exploit code has been identified at time of analysis.
Heap-based buffer overflow in NXP MCUXpresso SDK USB middleware before 2.13.0 lets a malicious USB device exploit unvalidated bNumEndpoints and bLength descriptor fields in the host audio, video, and CDC class drivers, writing past the fixed-size endpoint list and corrupting heap memory. The affected component must run as a USB host with one of those class drivers active, and the attack requires physical attachment of the crafted device (CVSS 4.0 AV:P); no remote path is described. Successful exploitation can lead to code execution or denial of service, but no public exploit was identified at time of analysis and KEV status is not indicated.