A path traversal vulnerability (CWE-22) exists in the NTP configuration module of OPNsense core prior to version 26.1.9 and BE/opnsense/core prior to 26.4_20. This flaw allows an attacker with access to the NTP configuration and high privileges to overwrite arbitrary files on the system as root by manipulating GPS or PPS serial port parameters. The vulnerability is patched in versions 26.1.9 and 26.4_20 respectively.
Home Assistant is open source home automation software focused on local control and privacy. Prior to 2026.5.0, the iOS Companion app treats tag links (NFC or QR) delivered through an OS-level routing mechanism such as iOS universal links as if they were physically scanned, without validating the calling app or prompting the user. As a result, any untrusted app on the device can forward an arbitrary tag to Home Assistant, causing it to execute the associated automation as though a legitimate user had scanned an authorized tag. This allows silent, unattended automation execution by untrusted local callers. This issue has been fixed in version 2026.5.0.
Home Assistant is open source home automation software focused on local control and privacy. Prior to 2026.5.3, the Companion app treats tag links (NFC or QR) delivered through an OS-level routing mechanism as if they were physically scanned, without validating the calling app or prompting the user. As a result, any untrusted app on the device can forward an arbitrary tag to Home Assistant, causing it to execute the associated automation as though a legitimate user had scanned an authorized tag. This allows silent, unattended automation execution by untrusted local callers. This issue is fixed in version 2026.8.1.
Hubzilla 11.2.1 contains a cross-site request forgery vulnerability in the OAuth2 /authorize endpoint handled by Zotlabs\Module\Authorize::post() that allows unauthenticated attackers to register arbitrary OAuth2 applications under an authenticated user's account by submitting a cross-origin POST request without CSRF token or Origin/Referer validation. Attackers can craft a malicious HTML form that autosubmits attacker-chosen OAuth2 parameters including client_id, client_secret, redirect_uri, and scope to silently register a persistent OAuth2 application, enabling interception of future OAuth2 authorization codes when the victim later authenticates against the attacker-controlled client.
REDAXO is a PHP-based content management system. From 5.18.2 until 5.21.1, rex_mediapool::isAllowedExtension in redaxo/src/addons/mediapool/lib/mediapool.php lets an authenticated backend user with media[upload] permission upload a JPEG/PHP polyglot named shell.php.any.jpg, which web servers with multi-extension PHP handlers can execute as the web-server user. This issue is fixed in version 5.21.1.
ownCloud Core is the server-side component of the file storage, synchronization, and sharing application ownCloud Classic. In versions prior to 10.15.3, the Updater on ownCloud 10 before 10.15.3 has an exposed dangerous method or function. Attackers with administrative privileges may leverage functionality to execute arbitrary code. This issue has been fixed in version 10.15.3.
## Summary
The API Platform serializer's `AbstractItemNormalizer` does not validate the resource type returned when resolving relation IRIs, allowing type confusion where a resource of an unintended type can be silently assigned to a relation property.
## Impact
An attacker who can submit write requests (POST/PUT/PATCH) to an API Platform endpoint with writable relations can supply a relation IRI pointing to a resource of a different type than the relation's declared class. Because `getResourceFromIri()` does not pass an `$operation` to `IriConverter::getResourceFromIri()`, the `is_a` type guard at `IriConverter.php:86` is skipped. For untyped relation properties (legacy `@var`-only style), the wrong-typed object is silently assigned, corrupting invariants and potentially feeding downstream logic that assumes the declared type (CWE-843). For typed properties (modern PHP 8.x), the substitution is blocked by Symfony's PropertyAccessor with an `InvalidTypeException`.
## Affected versions
- `api-platform/core` `< 4.1.30`
- `api-platform/core` `>= 4.2.0, < 4.2.26`
- `api-platform/core` `>= 4.3.0, < 4.3.12`
Older major series (`2.x`, `3.x`) ship the same vulnerable code path and are end-of-life; no fix is planned.
## Patched versions
- `4.1.30`
- `4.2.26`
- `4.3.12`
## Fix
An `is_a` guard is added inside `AbstractItemNormalizer::getResourceFromIri()` (and the equivalent inline call sites on 4.1) so that a mismatched IRI throws `InvalidArgumentException`, mirroring the operation-aware check the `IriConverter` already performs when an operation is supplied. This forces a `400 Bad Request` response for cross-type IRIs instead of a silent assignment.
## Workarounds
Declare a PHP type on every writable relation property (e.g. `public ?Foo $relation = null;` instead of `@var Foo $relation`). Symfony's `PropertyAccessor` will then reject a mismatched object with `InvalidTypeException`. This does not cover collections of mixed-type interfaces; upgrading to a patched version is the only complete fix.
## Proof of concept
A functional test posts a `Bar` IRI to a `Foo`-declared relation on an untyped property. Without the fix the server responds with `HTTP 201` and the Bar IRI appears in the response payload. With the fix the server responds with `HTTP 400` (`Invalid IRI "/bars/1"`).
Full PoC: `tests/Functional/Security/TypeConfusionRelationIriTest.php` in the patched branches.
## References
- `src/Serializer/AbstractItemNormalizer.php` — vulnerable relation IRI load
- `src/Symfony/Routing/IriConverter.php` — conditional `is_a` guard (operation-aware path)
## Credit
Reported by @alexandre-daubois.
Home Assistant is open source home automation software that puts local control and privacy first. Prior to 2025.5.0, The iOS companion app ignores the SSID allowlist for internal networks. The app uses SSID to detect when to use the internal URL, but whenever the app cannot find any other URL to be used, it fallbacks to the internal URL as well, which can expose user's token when connected to a not secure network. This vulnerability is fixed in 2025.5.0.
Home Assistant is open source home automation software that puts local control and privacy first. Prior to 2026.5.3, the LocationSensorManager BroadcastReceiver is exported with no permission. Any installed app, with zero runtime permissions, can broadcast a forged Google Play Services LocationResult directly to it; the receiver trusts the extra and forwards it to the user's Home Assistant server as the device's real location. This bypasses Android's developer-mode "Mock Location" gate and allows a local malicious app to drive zone-based automations (unlock door / disarm alarm / open garage) by faking the user's GPS position. This vulnerability is fixed in 2026.5.3.
Home Assistant is open source home automation software that puts local control and privacy first. Prior to 2026.4.1 for iOS and 2026.4.4 for Android, he Home Assistant Companion apps for Android and iOS expose a JavaScript bridge to the in-app WebView window.externalApp on Android and webkit.messageHandlers.getExternalAuth (alongside revokeExternalAuth and externalBus) on iOS. Two flaws expose the bridge to all frames (including cross-origin iframes) and unsanitized interpolation of the JavaScript callback identifier allows a cross-origin iframe rendered inside the Companion app to execute arbitrary JavaScript in the Home Assistant frontend's main-frame origin and exfiltrate the signed-in user's access token. This vulnerability is fixed in 2026.4.1 for iOS and 2026.4.4 for Android.
CVE-2026-44473 is a high-severity vulnerability in ellanetworks core (Ella Core), a 5G core designed for private networks. Versions prior to 1.10.0 allow a radio with a valid NG Setup to send a forged PDUSessionResourceSetupResponse containing any UE's AMF-UE-NGAP-ID. The core fails to verify that the message arrived on the SCTP association bound to that UE's logical NG-connection, resulting in the creation of a GTP tunnel towards the radio. This improper security check can lead to denial of service or disruption of network operations. The vulnerability is fixed in version 1.10.0. No known exploits in the wild have been reported.
Ella Core versions prior to 1.10.0 contain a vulnerability where the UE Security Capabilities received in NGAP PathSwitchRequest messages are not verified against locally stored values. This allows a malicious gNB to overwrite stored UE security capabilities with arbitrary values by sending a crafted PathSwitchRequest message. The vulnerability is fixed in version 1.10.0. The CVSS score is 6.1, indicating a medium severity issue with potential integrity and availability impacts but no confidentiality loss.
Ella Core is a 5G core designed for private networks. Prior to 1.10.0, Ella Core didn't enforce security rules on concurrent running of security procedures defined in TS 33.501 §6.9.5.1 — it could send a NAS Security Mode Command while an N2 handover was still pending (and vice versa). Concurrent Security Mode Command and N2 handover produce a KgNB mismatch between the UE and target gNB, causing the handover to fail. Requires a stalled gNB + re-registration race to trigger. This vulnerability is fixed in 1.10.0.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in the Publish Audit API endpoints (/api/auditPublishing/get and /api/auditPublishing/getAll) in dotCMS Core 25.11.04-1 through 26.04.28-02 allows remote unauthenticated attackers to read, modify, or destroy arbitrary database content. The endpoints did not enforce authentication and accepted unsanitized input used in dynamically constructed SQL. The fix in dotCMS Core 26.04.28-03 requires an authenticated backend user with the publishing-queue portlet permission. LTS releases are not affected as the vulnerable code path was never backported.
CVE-2026-45158 is a critical vulnerability in OPNsense core versions prior to 26.1.8. It involves improper neutralization of argument delimiters in a command, specifically in the DHCP configuration processing. Unsanitized user input is passed to a shell script, enabling remote code execution as root on the underlying FreeBSD operating system. This vulnerability is fixed in version 26.1.8. The CVSS score is 9.1, indicating a high severity with network attack vector, low attack complexity, and full impact on confidentiality, integrity, and availability.
OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.8, an authenticated Remote Code Execution (RCE) vulnerability in the OPNsense core allows a user with user-management privileges to execute arbitrary system commands as root. An attacker can bypass input validation by formatting their malicious payload as a compliant email address, allowing shell commands to reach the underlying operating system. The flaw exists in the local user synchronization flow, within core/src/opnsense/scripts/auth/sync_user.php. This vulnerability is fixed in 26.1.8.
A logic flaw in OPNsense core versions prior to 26.1.7 allows an unauthenticated attacker to bypass the authentication failure lockout mechanism. By submitting a crafted username containing success keywords between brute-force attempts, the attacker can reset the failure counter for their IP address, preventing lockout. This vulnerability is identified as CWE-307 and has a CVSS score of 5.3 (medium severity). The issue is fixed in version 26.1.7.
OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.7, the XMLRPC method opnsense.restore_config_section fails to sanitize user supplied input leading to Remote Code Execution. This vulnerability is fixed in 26.1.7.
FlightPHP versions prior to 3.18.1 contain a vulnerability where the Request::getMethod() function unconditionally trusts the X-HTTP-Method-Override header and the $_REQUEST['_method'] parameter for all HTTP verbs, including safe ones like GET. This allows an attacker to change the HTTP method of a request silently, potentially turning a GET request into a DELETE or PUT. This behavior can lead to Cross-Site Request Forgery (CSRF) escalation against destructive endpoints, bypass middleware protections based on HTTP verbs, and cause cache poisoning between CDN and origin. The issue is fixed in version 3.18.1.
FlightPHP core versions prior to 3.18.1 contain a reflected cross-site scripting (XSS) vulnerability in the Flight::jsonp() function. This occurs because the ? jsonp= query parameter is concatenated directly into a JavaScript response without validating that it is a legal JavaScript identifier. An attacker can exploit this to inject arbitrary JavaScript code that executes in the context of the response origin. The vulnerability is assigned CVE-2026-42548 and has a high severity score of 8.6. The issue is fixed in FlightPHP version 3.18.