π¨ CVE-2026-82643
WWBN AVideo contains an unauthenticated credential submission vulnerability in plugin/Live/api/preauthorize.json.php that accepts credentials over GET without rate limiting. Attackers can submit correct credentials repeatedly to trigger uncapped two-factor confirmation emails and perform sustained password guessing attacks against user accounts.
π@cveNotify
WWBN AVideo contains an unauthenticated credential submission vulnerability in plugin/Live/api/preauthorize.json.php that accepts credentials over GET without rate limiting. Attackers can submit correct credentials repeatedly to trigger uncapped two-factor confirmation emails and perform sustained password guessing attacks against user accounts.
π@cveNotify
GitHub
Unauthenticated credential submission with no rate limiting in plugin/Live/api/preauthorize.json.php, reachable over GET whereβ¦
### Summary
`plugin/Live/api/preauthorize.json.php` accepts a username and password from an unauthenticated caller and applies no rate limiting of any kind. It reads credentials from `$_GET` as ...
`plugin/Live/api/preauthorize.json.php` accepts a username and password from an unauthenticated caller and applies no rate limiting of any kind. It reads credentials from `$_GET` as ...
π¨ CVE-2026-82644
WWBN AVideo (current e01e41ecc and earlier) contains a brute-force rate limiting bypass in enforceRateLimit(), which protects login.json.php and 13 other endpoints. The function stores its attempt counter via a cache layer (ObjectYPT::setCacheGlobal) that silently discards writes for any client identified as a bot by isBot(). Because isBot() treats a missing User-Agent header as a bot by default β and also matches common bot identifiers such as 'curl', 'bot', 'crawler', and 'spider' β the counter never increments for such clients, so the rate limit never fires. An unauthenticated attacker can therefore submit unlimited login attempts (e.g., by omitting the User-Agent header or using curl's default User-Agent), enabling unrestricted password-guessing attacks.
π@cveNotify
WWBN AVideo (current e01e41ecc and earlier) contains a brute-force rate limiting bypass in enforceRateLimit(), which protects login.json.php and 13 other endpoints. The function stores its attempt counter via a cache layer (ObjectYPT::setCacheGlobal) that silently discards writes for any client identified as a bot by isBot(). Because isBot() treats a missing User-Agent header as a bot by default β and also matches common bot identifiers such as 'curl', 'bot', 'crawler', and 'spider' β the counter never increments for such clients, so the rate limit never fires. An unauthenticated attacker can therefore submit unlimited login attempts (e.g., by omitting the User-Agent header or using curl's default User-Agent), enabling unrestricted password-guessing attacks.
π@cveNotify
GitHub
Brute-force rate limiting is inert for any bot-like User-Agent: enforceRateLimit stores its counter through a cache layer thatβ¦
### Summary
`enforceRateLimit()` is the brute-force control for 14 endpoints, including `login.json.php`. It does not work against any client that looks like a bot β and the simplest way to look...
`enforceRateLimit()` is the brute-force control for 14 endpoints, including `login.json.php`. It does not work against any client that looks like a bot β and the simplest way to look...
π¨ CVE-2026-82645
AVideo (current commit e01e41ecc and earlier) exposes stream credentials through the plugin/Live/view/Live_restreams/getLiveKey.json.php endpoint. Supplying a 'token' request parameter waives both the Live::canRestream() access gate and the restream ownership check, causing the endpoint to return any restream's stream_key and stream_url (credentials for external platforms such as YouTube, Facebook, and Twitch) without authentication. The token is merely encryptString() of an integer id with no user binding, expiry, or authentication tag. Because encryption uses AES-256-CBC with a deterministic IV and no MAC, and because intval() accepts any string beginning with a digit, an unauthenticated attacker can forge valid tokens using the public encryption oracle in view/url2Embed.json.php, disclosing arbitrary users' stream credentials.
π@cveNotify
AVideo (current commit e01e41ecc and earlier) exposes stream credentials through the plugin/Live/view/Live_restreams/getLiveKey.json.php endpoint. Supplying a 'token' request parameter waives both the Live::canRestream() access gate and the restream ownership check, causing the endpoint to return any restream's stream_key and stream_url (credentials for external platforms such as YouTube, Facebook, and Twitch) without authentication. The token is merely encryptString() of an integer id with no user binding, expiry, or authentication tag. Because encryption uses AES-256-CBC with a deterministic IV and no MAC, and because intval() accepts any string beginning with a digit, an unauthenticated attacker can forge valid tokens using the public encryption oracle in view/url2Embed.json.php, disclosing arbitrary users' stream credentials.
π@cveNotify
GitHub
Unauthenticated disclosure of any restream stream_key / stream_url: the token parameter waives both the Live gate and the ownershipβ¦
### Summary
`plugin/Live/view/Live_restreams/getLiveKey.json.php` returns a restream's `stream_key` and `stream_url` β the credentials the site holds for a user's external streaming dest...
`plugin/Live/view/Live_restreams/getLiveKey.json.php` returns a restream's `stream_key` and `stream_url` β the credentials the site holds for a user's external streaming dest...
π¨ CVE-2026-82646
WWBN AVideo contains an unauthenticated reflected cross-site scripting vulnerability in the url2Embed.json.php endpoint that allows attackers to inject malicious scripts by supplying URLs with HTML metacharacters. Attackers can mint an encrypted evideo payload containing unescaped markup, then deliver it as a legitimate-looking link on the site's own domain to execute JavaScript in victims' sessions and steal cookies or CSRF tokens.
π@cveNotify
WWBN AVideo contains an unauthenticated reflected cross-site scripting vulnerability in the url2Embed.json.php endpoint that allows attackers to inject malicious scripts by supplying URLs with HTML metacharacters. Attackers can mint an encrypted evideo payload containing unescaped markup, then deliver it as a legitimate-looking link on the site's own domain to execute JavaScript in victims' sessions and steal cookies or CSRF tokens.
π@cveNotify
GitHub
Unauthenticated reflected XSS via the evideo payload: url2Embed.json.php mints a site-encrypted link whose videoLink is printedβ¦
### Summary
`view/url2Embed.json.php` will mint a site-encrypted `evideo` payload for any unauthenticated caller, from a URL the caller supplies. `Video::decodeEvideo()` then hands that URL to t...
`view/url2Embed.json.php` will mint a site-encrypted `evideo` payload for any unauthenticated caller, from a URL the caller supplies. `Video::decodeEvideo()` then hands that URL to t...
π¨ CVE-2026-82647
WWBN AVideo contains a cross-site request forgery vulnerability in sendEmail.json.php that allows authenticated administrators to send mail from the site's contact address by bypassing origin checks and captcha validation. Attackers can craft a malicious web page that, when visited by an authenticated admin, sends emails with attacker-controlled subject and body to arbitrary recipients, passing SPF/DKIM/DMARC validation for phishing and brand impersonation attacks.
π@cveNotify
WWBN AVideo contains a cross-site request forgery vulnerability in sendEmail.json.php that allows authenticated administrators to send mail from the site's contact address by bypassing origin checks and captcha validation. Attackers can craft a malicious web page that, when visited by an authenticated admin, sends emails with attacker-controlled subject and body to arbitrary recipients, passing SPF/DKIM/DMARC validation for phishing and brand impersonation attacks.
π@cveNotify
GitHub
CSRF in sendEmail.json.php: an authenticated admin's browser can be made to send mail From the site's own address to any recipient
### Summary
`objects/sendEmail.json.php` is on the built-in CSRF bypass list in `autoCSRFGuard()`, so it is exempt from the site's origin check. It also grants `$valid = true` to administrat...
`objects/sendEmail.json.php` is on the built-in CSRF bypass list in `autoCSRFGuard()`, so it is exempt from the site's origin check. It also grants `$valid = true` to administrat...
π¨ CVE-2026-82648
WWBN AVideo contains a server-side request forgery filter bypass vulnerability in the isSSRFSafeURL function that fails to normalize NAT64 addresses written in hexadecimal form. Attackers can bypass SSRF protections by supplying hex-encoded NAT64 addresses like 64:ff9b::a9fe:a9fe to reach cloud metadata services and loopback interfaces.
π@cveNotify
WWBN AVideo contains a server-side request forgery filter bypass vulnerability in the isSSRFSafeURL function that fails to normalize NAT64 addresses written in hexadecimal form. Attackers can bypass SSRF protections by supplying hex-encoded NAT64 addresses like 64:ff9b::a9fe:a9fe to reach cloud metadata services and loopback interfaces.
π@cveNotify
GitHub
SSRF filter bypass: hex-form NAT64 addresses (64:ff9b::a9fe:a9fe) reach cloud metadata and loopback
### Summary
`isSSRFSafeURL()` normalises NAT64 addresses by matching the textual form of the address rather than its value, so it covers only one of several spellings of the same 128-bit address...
`isSSRFSafeURL()` normalises NAT64 addresses by matching the textual form of the address rather than its value, so it covers only one of several spellings of the same 128-bit address...
π¨ CVE-2026-82649
SiYuan Windows installer before version 3.8.1 (affected versions >= 2.0.14) contains an uncontrolled search path element vulnerability in its NSIS installer, which invokes system executables such as TASKKILL by name rather than by absolute path. Because NSIS nsExec::Exec resolves these calls using a search path that includes the installer's own launch directory ahead of System32, an attacker who plants a malicious executable (e.g., a renamed TASKKILL.exe) in that directory can have it executed when the installer runs. These calls occur in electron-builder's preInit hook before the license page is displayed, and with an all-users (elevated) install the planted binary executes with an elevated token, resulting in local privilege escalation.
π@cveNotify
SiYuan Windows installer before version 3.8.1 (affected versions >= 2.0.14) contains an uncontrolled search path element vulnerability in its NSIS installer, which invokes system executables such as TASKKILL by name rather than by absolute path. Because NSIS nsExec::Exec resolves these calls using a search path that includes the installer's own launch directory ahead of System32, an attacker who plants a malicious executable (e.g., a renamed TASKKILL.exe) in that directory can have it executed when the installer runs. These calls occur in electron-builder's preInit hook before the license page is displayed, and with an all-users (elevated) install the planted binary executes with an elevated token, resulting in local privilege escalation.
π@cveNotify
GitHub
:bookmark: Release v3.8.0 Β· siyuan-note/siyuan@251596f
Signed-off-by: Daniel <845765@qq.com>
π¨ CVE-2026-82650
SiYuan 3.8.0 contains a path traversal / sensitive file exposure vulnerability in the RenderTemplate function (kernel/model/template.go), reachable via the POST /api/template/render endpoint (kernel/api/template.go). The endpoint restricts the supplied path only to the workspace directory (util.IsAbsPathInWorkspace) but, unlike the file API's refuseToAccess() blocklist, applies no sensitive-path exclusion. This allows an authenticated attacker to read sensitive workspace files, including conf/conf.json, which contains the API token and cookie signing key. The issue is fixed in v3.8.1.
π@cveNotify
SiYuan 3.8.0 contains a path traversal / sensitive file exposure vulnerability in the RenderTemplate function (kernel/model/template.go), reachable via the POST /api/template/render endpoint (kernel/api/template.go). The endpoint restricts the supplied path only to the workspace directory (util.IsAbsPathInWorkspace) but, unlike the file API's refuseToAccess() blocklist, applies no sensitive-path exclusion. This allows an authenticated attacker to read sensitive workspace files, including conf/conf.json, which contains the API token and cookie signing key. The issue is fixed in v3.8.1.
π@cveNotify
GitHub
Sensitive workspace files (including conf.json secrets) readable via /api/template/render, inconsistent with the file API's ownβ¦
**Product:** SiYuan (`github.com/siyuan-note/siyuan`)
**Component:** `kernel/model/template.go` (`RenderTemplate`), reachable via `kernel/api/template.go`
**Affected versions:** current `v3.8.0...
**Component:** `kernel/model/template.go` (`RenderTemplate`), reachable via `kernel/api/template.go`
**Affected versions:** current `v3.8.0...
π¨ CVE-2026-82651
SiYuan before v3.8.1 does not apply the IsForbiddenAbsPath guard (introduced in GHSA-c8r8-95hg-mp34) to the /history/*path and /repo/diff/*path endpoints in kernel/server/serve.go. These routes require admin authentication but construct file paths independently, so an authenticated administrator can retrieve historical snapshots of sensitive files that the guard is meant to block, including data/.siyuan/publishAccess.json (plaintext publish-mode passwords) and files under data/templates/.
π@cveNotify
SiYuan before v3.8.1 does not apply the IsForbiddenAbsPath guard (introduced in GHSA-c8r8-95hg-mp34) to the /history/*path and /repo/diff/*path endpoints in kernel/server/serve.go. These routes require admin authentication but construct file paths independently, so an authenticated administrator can retrieve historical snapshots of sensitive files that the guard is meant to block, including data/.siyuan/publishAccess.json (plaintext publish-mode passwords) and files under data/templates/.
π@cveNotify
GitHub
/history/*path and /repo/diff/*path were not updated to use the new IsForbiddenAbsPath guard added in GHSA-c8r8-95hg-mp34, potentiallyβ¦
### Summary
`GHSA-c8r8-95hg-mp34` added a centralized guard,
`util.IsForbiddenAbsPath()`, specifically to block access to a small
set of sensitive files: `conf/conf.json` (plaintext
`accessAuth...
`GHSA-c8r8-95hg-mp34` added a centralized guard,
`util.IsForbiddenAbsPath()`, specifically to block access to a small
set of sensitive files: `conf/conf.json` (plaintext
`accessAuth...
π¨ CVE-2026-82652
SiYuan before v3.8.1 fails to filter invisible-tier content from SQL embed blocks, attribute-view keys, and attribute-view backlinks in publish mode. Anonymous readers can enumerate invisible content through these three listing mechanisms despite admin configuration marking content unlisted.
π@cveNotify
SiYuan before v3.8.1 fails to filter invisible-tier content from SQL embed blocks, attribute-view keys, and attribute-view backlinks in publish mode. Anonymous readers can enumerate invisible content through these three listing mechanisms despite admin configuration marking content unlisted.
π@cveNotify
GitHub
Publish-mode "invisible" content is not filtered from SQL embed blocks, attribute-view keys, or attribute-view backlinks
**Product:** SiYuan (`github.com/siyuan-note/siyuan`)
**Component:** `kernel/model/publish_access.go`, reachable via `kernel/api/search.go` and `kernel/api/av.go`
**Affected versions:** current `...
**Component:** `kernel/model/publish_access.go`, reachable via `kernel/api/search.go` and `kernel/api/av.go`
**Affected versions:** current `...
π¨ CVE-2026-82653
SiYuan before v3.8.1 contains a stored cross-site scripting vulnerability in confirmDialog() where unescaped package names and notebook names are interpolated directly into innerHTML assignments. Attackers can submit malicious bazaar packages with HTML/script payloads in the name field that execute in users' browsers when uninstalling packages or unlocking encrypted notebooks.
π@cveNotify
SiYuan before v3.8.1 contains a stored cross-site scripting vulnerability in confirmDialog() where unescaped package names and notebook names are interpolated directly into innerHTML assignments. Attackers can submit malicious bazaar packages with HTML/script payloads in the name field that execute in users' browsers when uninstalling packages or unlocking encrypted notebooks.
π@cveNotify
GitHub
Stored HTML/script injection via unescaped confirmDialog() content in bazaar package name handling
**Product:** SiYuan (`github.com/siyuan-note/siyuan`)
**Component:** `app/src/config/bazaar.ts`, `app/src/util/mount.ts`, rendered via `app/src/dialog/confirmDialog.ts` / `app/src/dialog/index.ts`...
**Component:** `app/src/config/bazaar.ts`, `app/src/util/mount.ts`, rendered via `app/src/dialog/confirmDialog.ts` / `app/src/dialog/index.ts`...
π¨ CVE-2026-82654
SiYuan before v3.8.1 fails to properly escape block name, alias, and memo fields in hint, backlink, and breadcrumb rendering functions. Attackers can set a block's name to contain HTML/script tags that execute when another user views documents referencing or displaying that block.
π@cveNotify
SiYuan before v3.8.1 fails to properly escape block name, alias, and memo fields in hint, backlink, and breadcrumb rendering functions. Attackers can set a block's name to contain HTML/script tags that execute when another user views documents referencing or displaying that block.
π@cveNotify
GitHub
Stored HTML/script injection via block name in hint, backlink, and breadcrumb rendering (regression of a prior fix, plus two unpatchedβ¦
**Product:** SiYuan (`github.com/siyuan-note/siyuan`)
**Component:** `app/src/protyle/hint/extend.ts`, `app/src/protyle/wysiwyg/renderBacklink.ts`, `app/src/protyle/breadcrumb/index.ts`
**Affecte...
**Component:** `app/src/protyle/hint/extend.ts`, `app/src/protyle/wysiwyg/renderBacklink.ts`, `app/src/protyle/breadcrumb/index.ts`
**Affecte...
π¨ CVE-2026-82655
Admidio before 5.0.12 contains a blind SQL injection vulnerability in the relation_type_list parameter of lists_show.php that allows unauthenticated attackers to execute arbitrary SQL queries. Attackers can bypass authentication by providing a dummy UUID in role_list and inject SQL through relation_type_list to extract database contents including password hashes and user credentials.
π@cveNotify
Admidio before 5.0.12 contains a blind SQL injection vulnerability in the relation_type_list parameter of lists_show.php that allows unauthenticated attackers to execute arbitrary SQL queries. Attackers can bypass authentication by providing a dummy UUID in role_list and inject SQL through relation_type_list to extract database contents including password hashes and user credentials.
π@cveNotify
GitHub
Pre-auth(Unauthentication) Blind SQL Injection in admidio
### Summary
The membership management feature allows access even to users who are not logged in. Additionally, the system fails to adequately validate user input for the `relation_type_list` param...
The membership management feature allows access even to users who are not logged in. Additionally, the system fails to adequately validate user input for the `relation_type_list` param...
π¨ CVE-2026-82656
Admidio before 5.0.12 fails to sanitize album names in the photo ZIP download functionality, allowing authenticated users with album-creation rights to include path traversal segments in archive entry names. Attackers can craft malicious album names containing directory traversal sequences that escape the intended directory when recipients extract the archive, potentially writing files outside the target directory.
π@cveNotify
Admidio before 5.0.12 fails to sanitize album names in the photo ZIP download functionality, allowing authenticated users with album-creation rights to include path traversal segments in archive entry names. Attackers can craft malicious album names containing directory traversal sequences that escape the intended directory when recipients extract the archive, potentially writing files outside the target directory.
π@cveNotify
GitHub
Photo ZIP download uses the unsanitized album name as an archive path segment
## Summary
The photo ZIP download basenames each photo filename before adding it to the archive but uses the album name verbatim as the enclosing directory. The album name comes from the databas...
The photo ZIP download basenames each photo filename before adding it to the archive but uses the album name verbatim as the enclosing directory. The album name comes from the databas...
π¨ CVE-2026-82657
Admidio before 5.0.12 fails to enforce login-only module restrictions in RSS feed endpoints for forum and announcements modules. Unauthenticated attackers can retrieve forum topics and announcements by sending GET requests to rss/forum.php or rss/announcements.php, disclosing titles, full post text, author names, and timestamps.
π@cveNotify
Admidio before 5.0.12 fails to enforce login-only module restrictions in RSS feed endpoints for forum and announcements modules. Unauthenticated attackers can retrieve forum topics and announcements by sending GET requests to rss/forum.php or rss/announcements.php, disclosing titles, full post text, author names, and timestamps.
π@cveNotify
GitHub
RSS feeds leak forum posts in login-only mode
## Summary
The GHSA-cf48 fix added the missing `forum_module_enabled === 2 && !$gValidLogin` login gate to `modules/forum.php`, so that when the forum is configured as "login-only&q...
The GHSA-cf48 fix added the missing `forum_module_enabled === 2 && !$gValidLogin` login gate to `modules/forum.php`, so that when the forum is configured as "login-only&q...
π¨ CVE-2026-82658
Admidio versions before 5.0.12 contain a broken access control vulnerability in profile_function.php that allows authenticated low-privilege users to read another user's future role memberships. Attackers can bypass profile-level authorization by directly calling the reload_future_memberships endpoint with a victim's user UUID to disclose sensitive membership information.
π@cveNotify
Admidio versions before 5.0.12 contain a broken access control vulnerability in profile_function.php that allows authenticated low-privilege users to read another user's future role memberships. Attackers can bypass profile-level authorization by directly calling the reload_future_memberships endpoint with a victim's user UUID to disclose sensitive membership information.
π@cveNotify
GitHub
Broken access control in profile_function.php leaks future memberships
### Summary
Authenticated low-privilege users can read another user's future role memberships through profile_function.php, bypassing the profile-level authorization check.
### Details
Thi...
Authenticated low-privilege users can read another user's future role memberships through profile_function.php, bypassing the profile-level authorization check.
### Details
Thi...
π¨ CVE-2026-78699
Unchecked Return Value vulnerability in ash-project ash_postgres allows a user who can drive a tenant rename to a name that collides with an existing tenant's schema to have their tenant record repointed at that other tenant's live schema, gaining access to its data.
AshPostgres.MultiTenancy.rename_tenant/3 issues the ALTER SCHEMA ... RENAME TO ... with the non-raising Ecto.Adapters.SQL.query/2, discards its {:ok, _} | {:error, _} result, and unconditionally returns :ok. PostgreSQL rejects the rename when the target schema already exists (and on insufficient privilege or lock timeout), but that failure never reaches the caller. The calling manage_tenant update action therefore sees success and commits the tenant row with the new name, which is the schema of a different existing tenant, so subsequent reads and writes for that tenant run against the other tenant's data.
This issue affects ash_postgres: from 0.25.0 before 2.13.0.
π@cveNotify
Unchecked Return Value vulnerability in ash-project ash_postgres allows a user who can drive a tenant rename to a name that collides with an existing tenant's schema to have their tenant record repointed at that other tenant's live schema, gaining access to its data.
AshPostgres.MultiTenancy.rename_tenant/3 issues the ALTER SCHEMA ... RENAME TO ... with the non-raising Ecto.Adapters.SQL.query/2, discards its {:ok, _} | {:error, _} result, and unconditionally returns :ok. PostgreSQL rejects the rename when the target schema already exists (and on insufficient privilege or lock timeout), but that failure never reaches the caller. The calling manage_tenant update action therefore sees success and commits the tenant row with the new name, which is the schema of a different existing tenant, so subsequent reads and writes for that tenant run against the other tenant's data.
This issue affects ash_postgres: from 0.25.0 before 2.13.0.
π@cveNotify
π¨ CVE-2026-82549
A vulnerability was identified in Linux Foundation Magma 1.9.0. This affects an unknown function of the component SecurityModeComplete Handler. Such manipulation leads to improper validation of integrity check value. The attack may be launched remotely. The exploit is publicly available and might be used.
π@cveNotify
A vulnerability was identified in Linux Foundation Magma 1.9.0. This affects an unknown function of the component SecurityModeComplete Handler. Such manipulation leads to improper validation of integrity check value. The attack may be launched remotely. The exploit is publicly available and might be used.
π@cveNotify
GitHub
UE Capability with integrity IA0 is accepted and allowed to proceed registration (No Integrity Check) Β· Issue #16024 Β· magma/magma
Environment Version: v1.9.0 Affected Component: Access Gateway Affected Subcomponent: AMF Deployment Environment: Docker based AGW Issue If UE declares capability IA0 only, AMF allows it to proceed...
π¨ CVE-2026-82550
A security flaw has been discovered in Linux Foundation Magma 1.9.0. This impacts an unknown function of the component NGSetupRequest Handler. Performing a manipulation of the argument NG-IoT-DefaultPagingDRX results in improper input validation. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
π@cveNotify
A security flaw has been discovered in Linux Foundation Magma 1.9.0. This impacts an unknown function of the component NGSetupRequest Handler. Performing a manipulation of the argument NG-IoT-DefaultPagingDRX results in improper input validation. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
π@cveNotify
GitHub
[Bug] Valid NGSetupRequest with NG-IoT-DefaultPagingDRX gets decoder error Β· Issue #16023 Β· magma/magma
Environment Version: v1.9.0 Affected Component: Access Gateway Affected Subcomponent: AMF Deployment Environment: Docker based AGW Issue If AMF receives a valid NGSetupRequest with NG-IoT-DefaultPa...
π¨ CVE-2026-82551
A weakness has been identified in Linux Foundation Magma 1.9.0. Affected is an unknown function of the file ngap_amf_handlers.c of the component NGSetup Handler. Executing a manipulation can lead to state issue. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks.
π@cveNotify
A weakness has been identified in Linux Foundation Magma 1.9.0. Affected is an unknown function of the file ngap_amf_handlers.c of the component NGSetup Handler. Executing a manipulation can lead to state issue. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks.
π@cveNotify
GitHub
[Bug] AMF accepts message without NGSetup is successful Β· Issue #16021 Β· magma/magma
Environment Version: v1.9.0 Affected Component: Access Gateway Affected Subcomponent: AMF Deployment Environment: Docker based AGW Issue AMF accepts message without NGSetup process has been success...
π¨ CVE-2026-82552
A security vulnerability has been detected in Linux Foundation Magma 1.9.0. Affected by this vulnerability is an unknown functionality of the file tasks/ngap/ngap_amf.c of the component gNB Termination Handler. The manipulation leads to denial of service. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used.
π@cveNotify
A security vulnerability has been detected in Linux Foundation Magma 1.9.0. Affected by this vulnerability is an unknown functionality of the file tasks/ngap/ngap_amf.c of the component gNB Termination Handler. The manipulation leads to denial of service. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used.
π@cveNotify
GitHub
[Bug] No context cleanup on gNB termination which can cause Denial Of Service Β· Issue #16019 Β· magma/magma
Environment Version: v1.9.0 Affected Component: AMF Affected Subcomponent: Deployment Environment: local docker compose (orc8r) Issue AMF doesn't clear up the contexts when a gNB is restarted o...