Search: network-lab.info
911 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Medium | 6.3 | EPSS 0.5% | CVE-2026-54206Tobit Laboratories TeamDavid · Improper Input Validation Medium6.3EPSS 0.5%CVE Database V5CVE-2026-54206 Tobit Laboratories AG TeamDavid's Webbox 's sending email, fax, SMS, etc. functionality accepts a @@INCLUDE command, which can be set to network locations using UNC paths (e.g., “\\Server\Share”). The server processes these paths without validation, resulting in outbound connection attempts to attacker-controlled SMB servers. This enables authenticated attackers to trigger the server to authenticate to arbitrary SMB endpoints, potentially exposing NTLM authentication information (such as NTLM hashes). If outbound connections to port 445 (SMB) are permitted, attackers can use this to conduct SMB relay or credential theft attacks. Exploitation of the “pathname” parameter is possible without authentication. This issue affects TeamDavid before Rollout 528. Starting with Rollout 528 (June 30, 2026), the affected functionality is disabled by default and the vulnerabilities are therefore no longer exposed through this functionality. | CVE Database V5 | ||
| High | 7.7 | EPSS 0.6% | CVE-2026-54204Tobit Laboratories TeamDavid · Improper Input Validation High7.7EPSS 0.6%CVE Database V5CVE-2026-54204 Tobit Laboratories AG TeamDavid's Webbox 's search functionality accepts a “pathnameroot” parameter, which can be set to network locations using UNC paths (e.g., “\\Server\Share”). The server processes these paths without validation, resulting in outbound connection attempts to attacker-controlled SMB servers. This enables unauthenticated attackers to trigger the server to authenticate to arbitrary SMB endpoints, potentially exposing NTLM authentication information (such as NTLM hashes). If outbound connections to port 445 (SMB) are permitted, attackers can use this to conduct SMB relay or credential theft attacks. Exploitation of the “pathnameroot” parameter is possible without authentication.This issue affects TeamDavid before Rollout 528. Starting with Rollout 528 (June 30, 2026), the affected functionality is disabled by default and the vulnerabilities are therefore no longer exposed through this functionality. | CVE Database V5 | ||
| Critical | 9.3 | EPSS 0.7% | CVE-2026-59118Microsoft Power Apps · Improper Authorization Critical9.3EPSS 0.7%GCVE DatabaseCVE-2026-59118 CVE-2026-59118 is a critical vulnerability in Microsoft Power Apps involving improper authorization that allows an unauthorized attacker to elevate privileges over a network. The flaw enables privilege escalation without requiring prior authentication, with high impact on confidentiality and integrity but no impact on availability. No affected versions or patch information are provided. | GCVE Database | ||
| Low | 2.1 | EPSS 0.3% | Low2.1EPSS 0.3%GCVE DatabaseCVE-2026-71326 ## Summary There is a low severity vulnerability in Traefik's BasicAuth middleware. Concurrent password verifications are deduplicated through a singleflight group whose key was the delimiter-free concatenation of the submitted password and the stored secret, so a request carrying an unconfigured username — whose secret is empty — can produce the same key as a configured user's valid request and receive that request's successful result. Exploitation requires the attacker to already hold a valid credential **and** to read the stored password hash, which is only reachable through paths that are themselves privileged: the API is documented as admin-only, the Kubernetes path requires read access to the Secret, and the Docker path requires access to the socket. The key now encodes the password length as a prefix, so distinct (password, secret) pairs can no longer collide. Only the v3.6 line from v3.6.11 onwards and the v3.7 line are affected; earlier v3 releases and the v2 line do not carry the vulnerable deduplication path. ## Patches - https://github.com/traefik/traefik/releases/tag/v3.6.25 - https://github.com/traefik/traefik/releases/tag/v3.7.10 ## For more information If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues). <details> <summary>Original Description</summary> ## Summary Traefik's BasicAuth middleware deduplicates concurrent password checks with a `singleflight.Group`. Its key is the delimiter-free concatenation `password + secret`. For an existing user with password `P` and stored hash `H`, the key is `P || H`. An unknown user can select the password `P || H`; because its secret is the empty string, its key is also `P || H`. If the existing user's request starts the shared calculation, the unknown user receives the existing user's successful Boolean result. Traefik then continues processing the unknown user's original request and propagates the attacker-selected username through `URL.User`, the access log, and the configured BasicAuth `headerField`. A user who knows one valid username/password/hash tuple can therefore authenticate concurrently under any unconfigured username. This becomes a privilege escalation when a backend uses the BasicAuth `headerField` as a trusted identity, which is the documented purpose of that option. ## Details The vulnerable logic is in `pkg/middlewares/auth/basic_auth.go:118-131`: ```go func (b *basicAuth) checkPassword(user, password string) bool { secret := b.auth.Secrets(user, b.auth.Realm) key := password + secret match, _, _ := b.singleflightGroup.Do(key, func() (any, error) { if secret == "" { _ = b.checkSecret(password, b.notFoundSecret) return false, nil } return b.checkSecret(password, secret), nil }) return match.(bool) } ``` For a configured user `viewer`: ```text password = P secret = H key = P || H result = true ``` For an unconfigured user `admin`: ```text password = P || H secret = "" key = (P || H) || "" = P || H ``` `singleflight.Group.Do` shares the first in-flight result for equal keys. If the configured user's check is first, the unknown user's closure is not run and the unknown request receives `true`. The authorization result is not bound to the username. After the shared result is accepted, `ServeHTTP` uses the username parsed from the unknown request: ```go req.URL.User = url.User(user) if b.headerField != "" { req.Header.Del(b.headerField) req.Header[b.headerField] = []string{user} } ``` Consequently, the backend sees the attacker-selected `admin` identity, not the valid request's `viewer` identity. ### Attack prerequisites The attacker needs: 1. network access to a route protected by the affected BasicAuth middleware; 2. one valid low-privilege username and password; 3. the corresponding stored password hash. The hash is often present in deployment labels or routing configuration. Traefik's API is also a direct source when the attacker can access it: `GET /api/http/middlewares/{id}` serializes `basicAuth.users`, including the hash, despite the field carrying `loggable:"false"`. The official v3.7.8 binary returned the hash in the validation environment. The attacker does not need another user's password or a victim-generated request. The attacker creates both concurrent requests: one with their valid credentials and one with an arbitrary, unconfigured target username. ### Security impact When `headerField` is configured, an authenticated low-privilege user can impersonate an arbitrary identity to the backend. Depending on downstream authorization, this can allow: - access to administrative data; - execution of privileged state-changing operations; - corruption of audit attribution; - bypass of identity-based tenant or role separation. Without `headerField`, the unknown request is still admitted through the BasicAuth middleware. The practical consequence then depends on whether the protected route treats | GCVE Database | ||
| Malicious | – | MaliciousGCVE Database The shiftmarkets-sdk npm package version 2.1.0 contains malicious code that executes a postinstall script collecting extensive system and environment information. This script gathers hostname, usernames, network interface details, and environment variable names filtered for credential-like keywords, then sends this data unencrypted to a hardcoded external IP address. The package mislabels this data collection as 'NON-SENSITIVE telemetry,' while it clearly performs reconnaissance for sensitive credentials. | GCVE Database | |||
| Medium | 6.5 | EPSS 0.2% | CVE-2026-24077Qualcomm Snapdragon · Integer Underflow Medium6.5EPSS 0.2%CVE Database V5CVE-2026-24077 CVE-2026-24077 is an integer underflow vulnerability (CWE-191) in Qualcomm Snapdragon products that can lead to information disclosure when processing wireless network channel switch information with improperly formatted length fields. The vulnerability has a CVSS score of 6.5, indicating a medium severity. It affects a wide range of Qualcomm Snapdragon chipsets and related components. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time. | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.3% | Medium5.3EPSS 0.3%GCVE DatabaseCVE-2026-14202 CVE-2026-14202 is an observable response discrepancy vulnerability in Bilin Software and Informatics Consultancy Inc.'s HUMANIST Digital Human Resources product. This vulnerability allows account footprinting by observing differences in responses. It affects versions from 26.0 up to but not including 26.1. The vulnerability has a CVSS 3.1 base score of 5.3, indicating medium severity, with network attack vector, low attack complexity, no privileges required, no user interaction, and limited confidentiality impact. No known exploits are reported in the wild, and no patch or remediation information is currently available. | GCVE Database | ||
| Critical | 9.8 | EPSS 0.5% | CVE-2026-14175Bilin Software and Informatics Consultancy HUMANIST Digital Human Resources · Unrestricted File Upload Critical9.8EPSS 0.5%CVE Database V5CVE-2026-14175 CVE-2026-14175 is a critical vulnerability in Bilin Software and Informatics Consultancy Inc.'s HUMANIST Digital Human Resources product. It allows unrestricted upload of files with dangerous types, enabling an attacker to upload a web shell to the web server. This affects version 26.0 of the software prior to 26.1. The vulnerability has a CVSS score of 9.8, indicating high severity with network attack vector, no required privileges or user interaction, and full confidentiality, integrity, and availability impact. | CVE Database V5 | ||
| –Not rated | – | Reddit BlueTeam This entry discusses the challenge of obtaining publicly available post-infection network traffic captures (PCAPs) showing command-and-control (C2) beaconing and data exfiltration from compromised hosts. While pre-infection traffic sources such as malware delivery URLs and exploit attempts are readily accessible, sustained post-infection traffic captures are scarce or limited to older datasets, small-scale analyst investigations, or short sandbox runs. The community-driven abuse.ch platform provides extensive threat intelligence but does not currently offer continuous post-infection PCAP data. The discussion highlights the difficulty in sourcing long-duration post-infection captures for research and detection development. | Reddit BlueTeam | |||
| High | 7.8 | EPSS 0.7% | CVE-2026-67309Traefik · Kubernetes Ingress NGINX RewriteTarget Path Traversal Allows Route-Level Authentication Bypass High7.8EPSS 0.7%GCVE DatabaseCVE-2026-67309 ## Summary There is a high severity vulnerability in Traefik's Kubernetes Ingress NGINX provider. When an Ingress uses the `nginx.ingress.kubernetes.io/rewrite-target` annotation with a regular expression that captures attacker-controlled text without requiring a path separator (for example path `/api(.*)` with rewrite target `/$1`), the generated `RewriteTarget` middleware can turn an initially safe request path into a dot-segment traversal path after the router has already been selected. ## Patches - https://github.com/traefik/traefik/releases/tag/v3.7.8 ## For more information If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues). <details> <summary>Original Description</summary> ## Summary Traefik's Kubernetes Ingress NGINX provider creates an internal `RewriteTarget` middleware for the `nginx.ingress.kubernetes.io/rewrite-target` annotation. When an Ingress path captures attacker-controlled text without requiring a path separator, the middleware can turn an initially safe path into a dot-segment traversal path after Traefik has already selected the router. For example, with Ingress path `/api(.*)` and rewrite target `/$1`, an unauthenticated request to `/api../admin` follows this flow: 1. The default entry-point path sanitizer leaves `/api../admin` unchanged because `api..` is one ordinary segment. 2. The public router's `PathRegexp("(?i)^/api(.*)")` rule matches. 3. `RewriteTarget` captures `../admin` and creates `/../admin`. 4. The middleware forwards `/../admin` without checking whether path normalization changes it. 5. A backend that normalizes paths resolves `/../admin` to `/admin`. 6. The request reaches content intended to be reachable only through a separate `/admin` router with BasicAuth, DigestAuth, or ForwardAuth. This is an unpatched sibling of [GHSA-cxjq-mrr5-89rv](https://github.com/traefik/traefik/security/advisories/GHSA-cxjq-mrr5-89rv), which added post-replacement normalization validation to `ReplacePathRegex`. The separate ingress-nginx `RewriteTarget` implementation did not receive the same validation. The bypass remains exploitable in the patched Traefik v3.7.7 release. ## Severity **Proposed severity:** Critical **CVSS 3.1:** 9.1 — `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N` - Attack vector: Network - Attack complexity: Low once the affected routing pattern exists - Privileges required: None - User interaction: None - Scope: Unchanged - Confidentiality: High - Integrity: High - Availability: None **Primary weakness:** CWE-22 — Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) **Secondary weakness:** CWE-288 — Authentication Bypass Using an Alternate Path or Channel The practical impact depends on the protected backend paths. If they are read-only or low sensitivity, environmental severity may be lower. ### Exploitation Preconditions - The Kubernetes Ingress NGINX provider is enabled. - A public Ingress uses `rewrite-target` with a regex that can capture `..` adjacent to the matched prefix, such as `/api(.*)` with `/$1`. - A protected router exposes another path on the same backend, such as `/admin`, and relies on a Traefik authentication or authorization middleware. - The backend normalizes dot segments before dispatching the request. These are deployment prerequisites; the remote attacker needs no credentials or special timing. ## Affected Components ### Confirmed versions - Traefik v3.7.0 through v3.7.7 - Current `master` at commit `b93f02cd07b79490fb8c8f02e301a7a1ec553195` - Current `v3.7` branch at `69259c3acc9d4bdc065cb2e3b83336f7de3e7038` The vulnerable middleware is present in every stable v3.7 release checked. The v2.11 and v3.6 branches do not contain this ingress-nginx `RewriteTarget` implementation. ### Code locations - `pkg/provider/kubernetes/ingress-nginx/middleware.go:257-274` - Converts the Ingress path and `rewrite-target` annotation directly into `dynamic.RewriteTarget` configuration. - `pkg/middlewares/ingressnginx/rewritetarget/rewrite_target.go:85-157` - Performs capture-based path rewriting and forwards the rewritten path without normalization validation. - `pkg/server/middleware/middlewares.go:346-353` - Instantiates the vulnerable middleware in the live HTTP chain. ## Root Cause The provider passes the route regex and annotation replacement into the middleware: ```go loc.RewriteTarget = &dynamic.RewriteTarget{ Regex: loc.Path, Replacement: rewrite, } ``` `RewriteTarget.ServeHTTP` then derives a path from attacker-controlled capture groups: ```go newTarget = rt.regexp.ReplaceAllString(currentPath, rt.replacement) req.URL.RawPath = newTarget req.URL.Path, err = url.PathUnescape(req.URL.RawPath) req.RequestURI = req.URL.RequestURI() rt.next.ServeHTTP(rw, req) ``` There is no invariant check between `PathUnescape` and forwarding to ensure that `req.URL.Path` equals its normalized form. Because routing happen | GCVE Database | ||
| Low | 3.7 | EPSS 0.3% | Low3.7EPSS 0.3%CVE Database V5CVE-2026-56571 HCL iControl was affected by Improper Error Handling vulnerabilities. It involves Out of memory, null pointer exceptions, system call failure, database unavailable, network timeout, and hundreds of other common conditions can cause errors to be generated. | CVE Database V5 | ||
| Critical | 9.8 | EPSS 1.0% | Critical9.8EPSS 1.0%GCVE DatabaseCVE-2026-15969 Overview Six vulnerabilities have been discovered within the SGLang project, including remote code execution (RCE), server-side request forgery (SSRF), local file read, credential leakage, and model weight exfiltration on a target server. Exploitation does not require authentication in most cases, and some vulnerabilities require only network access with no API keys or user credentials. At the time of publication, no patches are available from the project maintainers, and coordination attempts have been unsuccessful. Description SGLang is an open-source framework for serving large language models (LLMs) and multimodal AI models, supporting models such as Qwen, DeepSeek, Mistral, and Skywork, and is compatible with OpenAI APIs. Six vulnerabilities have been discovered within the tool and are tracked as follows: CVE-2026-15969 SGLang contains unauthenticated RCE in /load_lora_adapter_from_tensors by bypass of SafeUnpickler’s incomplete denylist, allowing arbitrary command execution through crafted base64-encoded pickle payloads. CVE-2026-15971 SGLang contains an RCE vulnerability when the optional dumper subsystem is enabled, which allows for a sandbox escape when DUMPER_SERVER_PORT is set, enabling code execution on inference requests. CVE-2026-15974 SGLang contains an SSRF and local file read in the multimodal generation endpoint /v1/chat/completions because image_url input is unsanitized, allowing access to internal metadata, secrets, and services. CVE-2026-15976 SGLang contains a RCE vulnerability when attempting to load model weights from a HuggingFace repository, specifically within the /update_weights_from_disk , where torch.load(..., weights_only=False) fallback enables pickle deserialization of .bin files. CVE-2026-15977 SGLang contains a credential leakage vulnerability in the /server_info endpoint, which returns API keys and SSL keyfile information when only the --admin-api-key is configured. CVE-2026-15978 SGLang contains a model weight exfiltration vulnerability when no API keys are configured, because SGLang will expose two endpoints that allow a remote attacker to trigger distributed weight broadcasting using NCCL and then triggering data transfer, attackers can exfiltrate all model weights. Impact If exploited, these vulnerabilities could allow an unauthenticated attacker to achieve remote code execution, exfiltrate model weights, or overwrite arbitrary files on the host machine running SGLang. Deployments that expose the affected interface to untrusted networks are at the highest risk of exploitation. Solution Until a patch is available, affected users should consider the following mitigations: Mitigations Restrict access to the service interfaces and ensure they are not exposed to untrusted networks. Implement network segmentation and access controls to prevent unauthorized interaction with the vulnerable endpoints. Change SGLANG_USE_PICKLE_IPC to "false" within environ.py . Disable endpoints not in use to remove potential attack vectors. The SGLang maintainers have begun addressing pickle deserialization vulnerabilities and are working to refactor the code base with msgpack to prevent deserialization issues such as CVE-2026-14890, but the SGLANG_USE_PICKLE_IPC defaults to true within the codebase at the time of writing. Acknowledgements Thanks to the reporter, Apoorv Dayal [apoorvdayal@outlook.com]. This document was written by Christopher Cullen. Vendor Information One or more vendors are listed for this advisory. Please reference the full report for more information. References https://github.com/sgl-project/sglang/security/advisories/GHSA-2wvm-gjg7-5jfm https://github.com/sgl-project/sglang/security/advisories/GHSA-h6rf-77vv-9mvj https://github.com/sgl-project/sglang/security/advisories/GHSA-wf98-gv64-5wrf https://github.com/sgl-project/sglang/security/advisories/GHSA-x7w5-h7rp-gfp9 https://github.com/sgl-project/sglang/security/advisories/GHSA-jx7q-p32r-7wx8 https://github.com/sgl-project/sglang/security/a… | GCVE Database | ||
| –Not rated | – | Krebs on Security Security experts have been sounding the alarm for years about the risks of using generic TV boxes that promise unlimited content streaming for a one-time fee, warning that they secretly rent the user’s Internet connection out to strangers. But a groundbreaking new analysis finds these devices also routinely spoof themselves as mobile phones clicking ads on AI-generated websites as part of a sprawling operation that seeks to defraud online merchants and advertising networks. Pedro Falé is a threat researcher with the security firm Bitsight . Falé told KrebsOnSecurity he was able to peer inside a vast and complex ad fraud network by registering an expired domain name that was used to coordinate fake ad clicks across a particularly popular brand of these streaming devices known as H96 . An H96 TV streaming device currently advertised for sale on Amazon. Falé said the domain he scooped up was previously used for telemetry, periodically collecting full hardware information and the entire list of installed apps from tens of thousands of H96 streaming sticks plugged into television sets around the globe. But upon inspecting the traffic being funneled to the domain, he discovered nearly all of the TV boxes transmitting data claimed to be mobile phone models from a variety of manufacturers, including Samsung, Vivo, Huawei, and Xiaomi. “We noticed something was wildly wrong,” Falé said. “Multiple devices reporting to this factory Android TV Box backdoor were ‘phones.'” Image: Bitsight. The researcher found all of the devices reported having the same two apps installed, and that those apps were made by a company called Zhejiang Fengwo IoT Technology Ltd , an entity founded in 2019 in mainland China which operates an ad-publishing portfolio under the name Fengwo Group . Further investigation into the Fengwo Group revealed it has registered multiple patents that match the inner workings of these apps. “Bitsight TRACE identified several Hong Kong, Singapore, and single person ‘legal’ shell identities used to collect the monetization and traced the operation back to a mainland China company known as Zhejiang Fengwo IoT Technology Co., Ltd, which operates under the Fengwo Group,” Falé wrote in a report released today about their findings. Falé said an analysis of the apps shows they help to coordinate an ad fraud network that uses these H96 devices as a captive traffic source to click on ads at AI-generated websites operated by the Fengwo Group. Bitsight discovered the websites contain machine-generated news articles and graphics across a range of categories, including finance, health, education, gaming, music and food blogs. But they also found none of those sites displayed ads unless the device visiting the page matched the spoofed mobile profile of these H96 devices. AI DIGITAL HUMANS The domain for the Fengwo Group — fwgcloud[.]com — claims the company is “redefining the boundaries of human-AI interaction,” and that it has created more than 120,000 “AI digital humans” available to rent for everything from emotional companionship to 24/7 customer service and creative design. The homepage for fwgcloud dot com. Falé said the Fengwo Group’s domain shared its SSL certificate data with other domains associated with the apps found on H96 devices, specifically the phone spoofing mechanism. He noted the domain also has an internal wiki platform that directly ties the Fengwo Group to a proprietary implementation of a Google-built visual programming language called Blockly , which was originally designed to help kids learn how to write software. According to Bitsight, the Fengwo Group’s employees use Blockly to build the sham websites, allowing low-skilled operators to drag blocks of code together in their Blockly editor — without any need to understand what the underlying code blocks do or how they work. The Blockly homepage. “An operator can drag blocks together in their Blockly editor, to define each fraud routine, given a task type,” reads Bitsi… | Krebs on Security | |||
| Critical | 9.3 | EPSS 0.7% | Critical9.3EPSS 0.7%GCVE Database CVE-2026-44090 is a critical vulnerability in Phoenix Contact CHARX SEC-3150 devices caused by missing authentication on the MQTT broker. This allows unauthenticated remote attackers to access the broker and potentially cause denial-of-service conditions. The vulnerability can be exploited by network-adjacent attackers without any authentication. No patch or official fix information is currently available. | GCVE Database | ||
| High | 8.8 | EPSS 0.7% | High8.8EPSS 0.7%GCVE Database CVE-2026-44092 is a high-severity vulnerability affecting Phoenix Contact CHARX SEC-3150 devices. It allows an unauthenticated remote attacker to inject malicious input into the ModbusServer application due to lack of input validation. This vulnerability enables network-adjacent attackers to bypass firewall rules without requiring authentication. No patch or remediation information is currently available. | GCVE Database | ||
| Medium | – | MediumGCVE Database The aws-network-policy-agent package version 1.3.2-r0 addresses one security vulnerability identified as ghsa-xmrv-pmrh-hhx2. A patch is available in this version to fix the issue. No CVSS score or detailed technical impact information is provided. There are no known exploits in the wild for this vulnerability. | GCVE Database | |||
| Medium | 4.3 | EPSS 0.2% | CVE-2026-17857Network · Inappropriate Implementation Medium4.3EPSS 0.2%GCVE DatabaseCVE-2026-17857 A vulnerability in the Network component of Google Chrome prior to version 151.0.7922.72 allows a remote attacker to leak cross-origin data via a crafted HTML page. The issue is classified with medium severity and involves an inappropriate implementation that could lead to information disclosure without integrity or availability impact. | GCVE Database | ||
| Medium | 4.3 | EPSS 0.3% | CVE-2026-17907Google Chrome · Side-channel Information Leakage Medium4.3EPSS 0.3%CVE Database V5CVE-2026-17907 A side-channel information leakage vulnerability exists in the Network component of Google Chrome prior to version 151.0.7922.72. This flaw allows a remote attacker to leak cross-origin data by tricking a user into visiting a crafted HTML page. The vulnerability has a CVSS score of 4.3, indicating medium severity, and does not impact integrity or availability. No known exploits in the wild have been reported. Google has released Chrome version 151.0.7922.72 which addresses this issue. EPSS 0.3%Vulnerability | CVE Database V5 | ||
| Medium | 5.4 | EPSS 0.3% | Medium5.4EPSS 0.3%GCVE Database A vulnerability in GitLab Enterprise Edition versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 could allow sensitive information disclosure due to improper handling of upstream requests in virtual registries. This issue has been remediated by GitLab in the specified fixed versions. The vulnerability is classified as CWE-522 and has a CVSS 3.1 vector indicating network attack vector, low attack complexity, low privileges required, no user interaction, unchanged scope, limited confidentiality impact, no integrity impact, and low availability impact. No known exploits in the wild have been reported. | GCVE Database | ||
| –Not rated | – | Bleeping Computer CubePilot, an Australian drone flight controller manufacturer, experienced a significant operational disruption due to a DNS hijacking attack. This attack allowed interception of network traffic, impacting their software development operations. No specific technical details or affected software versions have been disclosed. There is no information about active exploitation or available patches. | Bleeping Computer |
Page 27 of 49