WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Published from 2009-05-01✕
Overview 389,764 matches · 16,418 in Waratek scope · 1,766 protected · 5,708 exploited · 1,764 CISA KEV · 18,003 public PoC · 3,750 EPSS ≥ 0.5
split by peak 101,213 / year
Withdrawn CVE: 18,812Not applicable: 349,990Outside Waratek scope: 4,544No exploit published: 14,282Mitigation candidate: 351Rule in development: 7Protected by Waratek: 1,778 Unknown: 22,867None: 79Low: 15,668Medium: 157,983High: 149,229Critical: 43,938 not established: 10not blocked: 387,976partly blocked: 12blocked by ARMR today: 1,766 No public exploit: 322,818Forecast only: 801Proof of concept only: 47,005Working exploit published: 13,432Exploited: 5,708
20093,484 Protected by Waratek6 Mitigation candidate7 No exploit published102 Outside Waratek scope44 Not applicable3,302 Withdrawn CVE23 Critical12 High1,653 Medium1,676 Low120 Unknown23 blocked by ARMR today6 not blocked3,478 Exploited51 Working exploit published1,461 Proof of concept only2 Forecast only2 No public exploit1,968 20104,667 Protected by Waratek9 Mitigation candidate12 No exploit published162 Outside Waratek scope86 Not applicable4,370 Withdrawn CVE28 Critical28 High2,093 Medium2,241 Low277 Unknown28 blocked by ARMR today9 not blocked4,658 Exploited73 Working exploit published1,313 Proof of concept only1 Forecast only9 No public exploit3,271 20114,172 Protected by Waratek6 Mitigation candidate9 No exploit published178 Outside Waratek scope116 Not applicable3,841 Withdrawn CVE22 Critical5 High1,784 Medium2,101 Low260 Unknown22 blocked by ARMR today6 not blocked4,166 Exploited50 Working exploit published691 Proof of concept only5 Forecast only4 No public exploit3,422 20125,351 Protected by Waratek9 Mitigation candidate24 No exploit published278 Outside Waratek scope94 Not applicable4,883 Withdrawn CVE63 Critical21 High1,724 Medium3,035 Low508 Unknown63 blocked by ARMR today9 not blocked5,340 not established2 Exploited59 Working exploit published831 Proof of concept only7 Forecast only46 No public exploit4,408 20135,324 Protected by Waratek26 Mitigation candidate18 No exploit published305 Outside Waratek scope300 Not applicable4,538 Withdrawn CVE137 Critical23 High1,735 Medium2,914 Low515 Unknown137 blocked by ARMR today26 not blocked5,297 not established1 Exploited97 Working exploit published520 Proof of concept only3 Forecast only21 No public exploit4,683 20148,008 Protected by Waratek41 Mitigation candidate12 No exploit published282 Outside Waratek scope253 Not applicable7,340 Withdrawn CVE80 Critical20 High1,938 Medium5,314 Low656 Unknown80 blocked by ARMR today41 not blocked7,967 Exploited97 Working exploit published795 Proof of concept only13 Forecast only16 No public exploit7,087 20156,595 Protected by Waratek32 Mitigation candidate6 No exploit published285 Outside Waratek scope202 Not applicable5,969 Withdrawn CVE101 Critical51 High2,354 Medium3,501 Low588 Unknown101 blocked by ARMR today32 not blocked6,563 Exploited96 Working exploit published647 Proof of concept only16 Forecast only19 No public exploit5,817 20166,517 Protected by Waratek59 Mitigation candidate11 No exploit published465 Outside Waratek scope129 Not applicable5,785 Withdrawn CVE68 Critical887 High2,895 Medium2,446 Low221 Unknown68 blocked by ARMR today57 partly blocked2 not blocked6,457 not established1 Exploited103 Working exploit published429 Proof of concept only27 Forecast only32 No public exploit5,926 201718,113 Protected by Waratek106 Mitigation candidate13 No exploit published681 Outside Waratek scope245 Not applicable13,597 Withdrawn CVE3,471 Critical2,113 High6,608 Medium5,687 Low234 Unknown3,471 blocked by ARMR today102 partly blocked4 not blocked18,007 Exploited212 Working exploit published1,259 Proof of concept only52 Forecast only23 No public exploit16,567 201818,154 Protected by Waratek176 Mitigation candidate16 No exploit published697 Outside Waratek scope338 Not applicable15,283 Withdrawn CVE1,644 Critical2,616 High7,571 Medium6,163 Low160 Unknown1,644 blocked by ARMR today175 partly blocked1 not blocked17,978 Exploited236 Working exploit published1,069 Proof of concept only87 Forecast only33 No public exploit16,729 201918,938 Protected by Waratek123 Rule in development1 Mitigation candidate23 No exploit published756 Outside Waratek scope514 Not applicable15,888 Withdrawn CVE1,633 Critical2,657 High7,227 Medium7,117 Low304 Unknown1,633 blocked by ARMR today121 partly blocked2 not blocked18,814 not established1 Exploited327 Working exploit published784 Proof of concept only126 Forecast only51 No public exploit17,650 202019,222 Protected by Waratek154 Mitigation candidate34 No exploit published898 Outside Waratek scope503 Not applicable16,733 Withdrawn CVE900 Critical2,780 High7,782 Medium7,359 Low401 Unknown900 blocked by ARMR today154 not blocked19,068 Exploited344 Working exploit published602 Proof of concept only156 Forecast only66 No public exploit18,054 202121,950 Protected by Waratek124 Rule in development1 Mitigation candidate24 No exploit published649 Outside Waratek scope491 Not applicable18,860 Withdrawn CVE1,801 Critical2,850 High8,770 Medium8,137 Low392 Unknown1,801 blocked by ARMR today124 not blocked21,826 Exploited489 Working exploit published446 Proof of concept only217 Forecast only167 No public exploit20,631 202226,431 Protected by Waratek214 Rule in development1 Mitigation candidate20 No exploit published895 Outside Waratek scope401 Not applicable23,542 Withdrawn CVE1,358 Critical4,441 High10,337 Medium9,908 Low385 Unknown1,360 blocked by ARMR today214 not blocked26,217 Exploited478 Working exploit published566 Proof of concept only2,768 Forecast only97 No public exploit22,522 202330,949 Protected by Waratek161 Mitigation candidate40 No exploit published876 Outside Waratek scope263 Not applicable27,476 Withdrawn CVE2,133 Critical5,031 High11,637 Medium11,824 Low323 Unknown2,134 blocked by ARMR today161 not blocked30,786 not established2 Exploited566 Working exploit published557 Proof of concept only5,593 Forecast only110 No public exploit24,123 202440,704 Protected by Waratek108 Mitigation candidate27 No exploit published617 Outside Waratek scope237 Not applicable38,964 Withdrawn CVE751 Critical4,874 High15,332 Medium18,998 Low740 None1 Unknown759 blocked by ARMR today106 partly blocked2 not blocked40,596 Exploited746 Working exploit published403 Proof of concept only7,467 Forecast only83 No public exploit32,005 202549,972 Protected by Waratek103 Rule in development4 Mitigation candidate25 No exploit published723 Outside Waratek scope151 Not applicable47,144 Withdrawn CVE1,822 Critical4,490 High16,670 Medium23,043 Low3,040 None10 Unknown2,719 blocked by ARMR today103 not blocked49,867 not established2 Exploited725 Working exploit published594 Proof of concept only10,991 Forecast only17 No public exploit37,645 2026101,213 Protected by Waratek321 Mitigation candidate30 No exploit published5,433 Outside Waratek scope177 Not applicable92,475 Withdrawn CVE2,777 Critical11,039 High41,119 Medium36,519 Low6,544 None68 Unknown5,924 blocked by ARMR today320 partly blocked1 not blocked100,891 not established1 Exploited959 Working exploit published465 Proof of concept only19,474 Forecast only5 No public exploit80,310
201020122014201620182020202220242026
389,764 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 2 of 3,898 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2026-130356 Medium 2026-11-17 Not applicable Proof of concept only phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass that lets category- or language-restricted editors rewrite visibility ACLs and tags of any FAQ. Attackers send faq/update requests with a target faqId and an untranslated lang to expose restricted FAQs, wipe tags, or overwrite orphaned FAQs.
CVE-2026-130355 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability in POST /admin/api/faq/import that lets FAQ_ADD users bypass the FAQ_PUBLISH right. Authenticated contributors can upload a CSV with column 8 set to true to publish unreviewed, optionally sticky FAQs such as phishing content.
CVE-2026-130354 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authentication bypass vulnerability in POST /api/webauthn/prepare that creates accounts as active, bypassing manual activation and domain whitelisting. Anonymous attackers can obtain the freely issued CSRF token and register an activated account with an unverified email to access registered-user-only content and functions.
CVE-2026-130353 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability in its public FAQ REST API that exposes author names and e-mail addresses to unauthenticated callers. Attackers can query the faq and paginated faqs endpoints to bulk-harvest e-mails and de-anonymise users who opted out of GDPR author visibility.
CVE-2026-130352 Medium 2026-11-17 Not applicable Proof of concept only phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability that allows unauthenticated attackers to read editor-only Private Notes by querying the public FAQ list API. Attackers can page through GET /api/v4.0/faqs or /api/v3.1/faqs without credentials to retrieve the notes field of every anonymously readable FAQ, exposing internal remarks and ticket details.
CVE-2026-130351 High 2026-11-17 Not applicable No public exploit phpMyFAQ from 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the multisite Redis configuration store that is not tenant-scoped. As a result, tenant administrators can read and overwrite the master instance's effective configuration. Attackers can save configuration through /admin/api/configuration, optionally resetting storage.redisPrefix, to redirect master SMTP, set a known API token, or alter authentication settings.
CVE-2026-130350 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an incorrect authorization vulnerability that allows delegated group or user admins to remove rights they do not hold by submitting empty rights lists. Attackers can send an empty rightIds or userRights array to group/permissions or user/update-rights to wipe all rights of more-privileged groups or administrators.
CVE-2026-130349 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability that allows category- or language-restricted editors to bypass scoped rights via public REST write endpoints. Attackers with a scoped right and the shared API token can use PUT faq/update, POST faq/create, and POST category to rewrite published FAQs and create root categories outside their scope.
CVE-2026-130348 Medium 2026-11-17 Not applicable Proof of concept only phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a missing authorization vulnerability that exposes restricted and inactive category metadata to unauthenticated visitors. Attackers can enumerate category IDs via /category/{id}/{slug}.html or query /api/v4.0/categories to read names, descriptions, images and FAQ counts of restricted categories.
CVE-2026-130347 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authentication bypass in password reset, letting external-identity accounts receive local passwords. Attackers with mailbox access can request reset tokens for OIDC, Keycloak, Entra ID, LDAP, SSO, or WebAuthn accounts and log in locally, skipping IdP MFA and deprovisioning.
CVE-2026-130346 Low 2026-11-17 Not applicable No public exploit AdminNeo before 5.9.1 contains an sql injection vulnerability in the ClickHouse driver because idf_escape() doubles backticks but does not escape backslashes in identifiers. Attackers can lure a logged-in user into opening a GET link with a column name ending in a backslash in columns, where, or order parameters, causing query text to be parsed as SQL.
CVE-2026-130345 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability that allows authenticated frontend users to receive restricted FAQ titles by subscribing to Web Push notifications. When editors publish user/group-restricted FAQs, WebPushService::sendToAll() delivers the question, FAQ id, category, and slugified URL to every subscriber, bypassing the FAQ ACL.
CVE-2026-130344 Low 2026-11-17 Not applicable Proof of concept only AdminNeo before 5.9.1 contains a stored cross-site scripting vulnerability in Admin::printTablePartitions() that allows authenticated users to inject HTML by placing markup in partition column names. Attackers with CREATE or ALTER privileges can create a partitioned table whose unescaped partition expression executes script when another user opens the table-structure page.
CVE-2026-130343 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ 3.2.5 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the user/request-removal API endpoint that lets authenticated users file account removal requests as other users. The ownership check calls getUserById() with the attacker-supplied userId on the session user object, so it compares the input against the target's own record. Attackers who know a victim's login name and email can submit that userId, loginname, and email, sending administrators a spoofed Remove User Request email. This may lead an admin to delete the victim's account and data.
CVE-2026-130342 Low 2026-11-17 Not applicable No public exploit phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an improper reference counting flaw on multisite deployments, allowing editors to delete other instances' attachment files. Because linkedRecords() counts only the local faqattachment table, deleting an attachment with shared md5 content makes File::delete() unlink the shared blob, destroying another instance's files.
CVE-2026-130341 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a stored cross-site scripting vulnerability that allows registered users to inject javascript: links via FAQ comments. When the comment editor is enabled, Utils::parseUrl() strips https:// from sanitized hrefs, turning an allowed https://javascript:443/ link into executable script that runs on the shared admin origin when clicked.
CVE-2026-130340 Low 2026-11-17 Not applicable Proof of concept only AdminNeo before 5.9.1 contains a stored HTML injection vulnerability that allows database users to inject markup into another user's session via column type names rendered with innerHTML. Attackers can create a PostgreSQL type or table with markup in its name to render live elements in the help popup, enabling content spoofing and requests to attacker servers.
CVE-2026-130339 Medium 2026-11-17 Not applicable No public exploit phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability that allows authenticated low-privilege users to read unpublished FAQ titles via bookmark_action. Attackers can request FAQ detail pages with bookmark_action=add across sequential ids, then view /user/bookmarks to reveal draft and pending submission question text.
CVE-2026-130338 Low 2026-11-17 Not applicable No public exploit AdminNeo before 5.9.1 contains a stored sql injection vulnerability in the MySQL driver that allows database users with table creation rights to inject SQL through unescaped geometry column names in unconvert_field(). Attackers can craft a column name containing an SQL expression that executes with another AdminNeo user's privileges when they edit a row, save it, or export the table.
CVE-2026-130335 Low 2026-11-17 Not applicable No public exploit Info-ZIP Zip 3.0 (and 3.1 beta through 3.1c) allows OS command injection by an attacker who controls the command line. The victim must use the -T option followed by a filename containing shell metacharacters, on a platform (such as Linux) where a suitable shell is run. This occurs because the system C library function is used. NOTE: there is no known common scenario in which an untrusted filename reaches a zip -T call.
CVE-2026-129448 Critical 2026-11-17 Not applicable No public exploit Deserialization of Untrusted Data in Apache Roller versions 4.0.0 through 6.1.4 allows an unauthenticated remote attacker to execute arbitrary code. The XML-RPC endpoint accepts vendor extension types and deserializes them before authenticating the requester. This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. Users who cannot upgrade right away should set "enabledForExtensions" to "false" in WEB-INF/web.xml, or remove the "/roller-services/xmlrpc" servlet mapping, and restart Roller. Disabling XML-RPC in the administration UI is not enough, because older versions deserialize the request before checking that setting.
CVE-2026-129321 Medium 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with planner-role permissions to set a future merge scheduling date on merge requests they authored, a capability restricted to developer-role permissions and above, due to insufficient permission enforcement on the merge scheduling field during merge request updates.
CVE-2026-129287 High 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 processes XML external entities in software repository files. An attacker able to supply or modify the repository files received by the server can read files accessible to the N-central service account or cause the server to make outbound requests.
CVE-2026-129286 Critical 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 does not validate version values and download locations in software update metadata. An attacker able to supply or modify the update metadata received by the server can write files outside the download directory and execute code as the N-central service account.
CVE-2026-129285 Medium 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 does not verify that an action response received over XMPP originates from the appliance the request was sent to. An attacker with the credentials of one appliance can forge responses on behalf of another appliance.
CVE-2026-129284 Medium 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 does not validate connection targets in the Report Manager and Data Export settings. An authenticated attacker can cause the server to connect to arbitrary hosts, including loopback and internal addresses, and can use the responses to probe internal network services.
CVE-2026-129283 High 2026-11-17 Not applicable No public exploit The custom service import in N-able N-central before 2026.4.1 HF3 processes XML external entities. An authenticated attacker can upload a crafted service definition to read files accessible to the N-central service account or cause the server to make outbound requests.
CVE-2026-129282 High 2026-11-17 Not applicable No public exploit The test email delivery function in N-able N-central before 2026.4.1 HF3 does not check permissions, lacks CSRF protection, and passes sender and recipient values to the mail program without neutralising option characters. An authenticated attacker can inject arguments into the mail command executed on the server.
CVE-2026-129281 High 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 checks only a view permission for ServerII2 operations that write device execution configuration. An authenticated user with view-only access to a device can set configuration that the Windows agent on that device acts on.
CVE-2026-129280 Critical 2026-11-17 Not applicable No public exploit Multiple ServerUI and ServerUI2 SOAP operations in N-able N-central before 2026.4.1 HF3 do not verify the caller's session, permissions or customer scope. A remote attacker, in some cases without authentication, can read device and patch data, test passwords of user accounts, send messages to managed agents, and modify device and service settings belonging to other customers.
CVE-2026-129279 Medium 2026-11-17 Not applicable No public exploit The password reset function in N-able N-central before 2026.4.1 HF3 returns distinguishable responses for valid and invalid accounts. A remote, unauthenticated attacker can enumerate the email addresses of valid user accounts.
CVE-2026-129278 Medium 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 does not authenticate callers of the ServerII2 remoteControlMSPAStartEndTimeSubmit operation. A remote, unauthenticated attacker can alter the recorded state and times of Take Control remote control tasks and the associated audit log entries.
CVE-2026-129277 Medium 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 does not authenticate callers of the MaintActionGet operation. A remote, unauthenticated attacker can read and cancel the pending maintenance actions of any appliance.
CVE-2026-129276 Medium 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 does not authenticate callers of the ServerMMS2 AssetDiscoSimplifiedInfoSubmit operation. A remote, unauthenticated attacker can overwrite the asset data recorded for any appliance.
CVE-2026-129275 High 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 allows the repositoryItemGet operation to be called without authentication. A remote, unauthenticated attacker who knows a policy identifier can download the Automation Manager policy of any customer, including embedded scripts and parameter values.
CVE-2026-129274 High 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 does not authenticate callers of the ServerMMS2 RemoteExecutionTaskSubmit operation or verify task ownership. A remote, unauthenticated attacker can submit forged results for remote execution tasks belonging to any customer.
CVE-2026-129273 High 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 does not neutralise control characters in an Audit Export setting before writing it to the system logging configuration. An authenticated attacker with product administrator privileges can inject configuration and execute commands as root on the N-central server.
CVE-2026-129272 Critical 2026-11-17 Not applicable No public exploit N-able N-central before 2026.4.1 HF3 uses a predictable credential to authenticate appliances to an agent-facing API. A remote, unauthenticated attacker who knows or guesses an appliance identifier can obtain a valid appliance token and session and impersonate that appliance.
CVE-2026-129271 High 2026-11-17 Not applicable No public exploit The Patch Management Engine in N-central is vulnerable to LPE via attacker controlled metadata
CVE-2026-129253 Medium 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with developer-role permissions to bypass admin-configured AI tool governance controls in a governed namespace due to improper binding of authorization tokens to their intended workflow execution context.
CVE-2026-129252 Low 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with an unconfirmed email address to be automatically granted Group Owner-level membership during a group import operation, due to insufficient email verification enforcement in the member identity mapping process.
CVE-2026-129246 Unknown 2026-11-17 Not applicable No public exploit Due to a Debian-specific patch, the directory used to share data between the LightDM and the users logging in was writable by the lightdm user of the unprivileged greeter process. A process running under the lightdm identity could leverage write access to that directory to force the LightDM process (running as root) to change ownership and permissions on other root-owned directories and escalate privileges from the lightdm user to root.
CVE-2026-129031 Medium 2026-11-17 Not applicable No public exploit Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Cool Plugins Conditional Fields for Elementor Form – Display Conditions conditional-fields-for-elementor-form allows Stored XSS.This issue affects Conditional Fields for Elementor Form – Display Conditions: from n/a through 1.7.7.
CVE-2026-129012 Medium 2026-11-17 Not applicable No public exploit Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LeapWorx Premium Addons for Elementor premium-addons-for-elementor allows Stored XSS.This issue affects Premium Addons for Elementor: from n/a through 4.11.118.
CVE-2026-129008 Medium 2026-11-17 Not applicable No public exploit Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPExperts Gutena Forms – Contact Form, Survey Form, Feedback Form, Booking Form, and Custom Form Builder gutena-forms allows Stored XSS.This issue affects Gutena Forms – Contact Form, Survey Form, Feedback Form, Booking Form, and Custom Form Builder: from n/a through 2.1.1.
CVE-2026-128849 Medium 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to start a Duo Workflow session with elevated privileges beyond those declared by the foundational flow due to improper enforcement of privilege boundaries in certain client environments.
CVE-2026-128038 Medium 2026-11-17 Not applicable No public exploit The All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name' parameter in all versions up to, and including, 5.0.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that an administrator has placed the AIOSEO breadcrumb on the author template, that the site is running WordPress 6.6 or later with the core Interactivity runtime loaded (e.g., via a block theme or core/navigation block), and that a victim clicks the rendered breadcrumb link on the author archive page.
CVE-2026-127174 Medium 2026-11-17 Not applicable No public exploit When changing the settings of a scheduled export, no permission checks are done to see whether the user making the change has access to the exporter after the change. This way, an attacker with access to change organizer settings and e.g. access to all orders could change the export to refer to gift cards instead, even if they do not have access to gift cards. The fix for this is technically a breaking API change, since changing the export type of existing scheduled exports is no longer allowed, but we don't expect this to affect any typical API usage.
CVE-2026-127140 Low 2026-11-17 Not applicable No public exploit Our WordPress plugin for the pretix Widget performs HTTP calls to pre-fetch CSS and JS files into a local cache and stores them publicly on the WordPress instance. These HTTP calls are made with wp_remote_get, not wp_safe_remote_get, and therefore allow SSRF with body extraction. Exploiting this requires sufficient WordPress permissions to create or modify pages.
CVE-2026-127139 Medium 2026-11-17 Not applicable No public exploit pretixSCAN Proxy does not use a secure random generator to generate initialization tokens and API keys for the connection between pretixSCAN devices and the pretixSCAN Proxy. This could allow a skilled attacker with access to at least some of the tokens to predict the value of other tokens more easily. pretixSCAN is usually used on local networks and the level of exposure heavily depends on the structure of that network. If you want to be extra careful, it might make sense to reconnect your devices to the proxy after the update.
CVE-2026-127138 Medium 2026-11-17 Not applicable No public exploit pretix provides a mechanism where ticket QR codes are cryptographically signed and can be verified by our pretixSCAN apps in offline mode without any database of valid tickets. pretixSCAN checks the signature to verify that the ticket was issued by the correct pretix event and compares the QR code against a list of revoked QR codes. A QR code becomes revoked when the order is canceled, or the ticket is changed in a way that a new QR code needs to be generated. However, the parsing of the QR code in all of our pretixSCAN apps contained a faulty computation, rendering the check for the correct length of the contents faulty. This way, an attacker is able to craft multiple QR codes for the same ticket which have the same content, but look different and therefore do not match against the revocation list. This does not allow to fabricate entirely new tickets, but it does allow to enter the event with e.g. a canceled ticket. This attack requires pretixSCAN to be scanning in offline mode and the "pretix signature scheme 1" to be used for the event's QR codes. If the attack is executed, the ticket unfortunately shows as valid (green) on the scanner but as invalid (red) on the server since the server later cannot match it to a ticket. We scanned the entire database of scans on pretix Hosted and could not find any traces of this being exploited in the past.
CVE-2026-126558 High 2026-11-17 Not applicable No public exploit OS Command Injection, Incomplete List of Disallowed Inputs vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows OS Command Injection, Command Delimiters.This issue affects AutoSys Workload Automation: from 12.1 through 24.2.00.
CVE-2026-126557 Medium 2026-11-17 Not applicable No public exploit Out-of-bounds Write vulnerability in Broadcom AutoSys Workload Automation (AutoSys engine (AE) native clients modules) on Windows, Linux allows Overflow Buffers.This issue affects AutoSys Workload Automation: from 12.1.00.00-0305 through 24.2.00-0210.
CVE-2026-126556 Medium 2026-11-17 Not applicable No public exploit Invocation of Process Using Visible Sensitive Information, Insufficiently Protected Credentials vulnerability in Broadcom AutoSys Workload Automation (AutoSys engine (AE) native clients modules) on Windows, Linux allows Collect Data from Common Resource Locations.This issue affects AutoSys Workload Automation: 24.2.00-0210 and earlier (verified on 24.2.00-0210; earlier range unestablished), 24.2.01 (when the -pw/-pwx options are used).
CVE-2026-126555 Medium 2026-11-17 Not applicable No public exploit Missing Authorization, Hidden Functionality vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Accessing Functionality Not Properly Constrained by ACLs, Exploit Non-Production Interfaces.This issue affects AutoSys Workload Automation: from 12.1.00 through 24.2.00.
CVE-2026-126553 Critical 2026-11-17 Not applicable No public exploit Deserialization of Untrusted Data vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Object Injection.This issue affects AutoSys Workload Automation: from 12.1 through 24.0.01.
CVE-2026-126552 Critical 2026-11-17 Not applicable No public exploit Missing Authentication for Critical Function, OS Command Injection vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows OS Command Injection.This issue affects AutoSys Workload Automation: from 12.1 through 24.0.01.
CVE-2026-126551 Critical 2026-11-17 Not applicable No public exploit Use of Hard-coded Cryptographic Key vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Session Credential Falsification through Forging.This issue affects AutoSys Workload Automation: from 12.1 through 24.2.00.
CVE-2026-126550 High 2026-11-17 Not applicable No public exploit Insertion of Sensitive Information into Log File, Insufficiently Protected Credentials vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Reusing Session IDs (Session Replay).This issue affects AutoSys Workload Automation: from 12.1.00 through 24.2.00.
CVE-2026-126549 Medium 2026-11-17 Not applicable No public exploit Insertion of Sensitive Information into Log File vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Collect Data from Common Resource Locations.This issue affects AutoSys Workload Automation: from 12.1.00 through 24.2.00.
CVE-2026-126548 High 2026-11-17 Not applicable No public exploit Server-Side Request Forgery (SSRF) vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Server Side Request Forgery.This issue affects AutoSys Workload Automation: from 12.1.01 Cum 03 through 12.1.01 Cum 06, from 24.0 through 24.2.00.
CVE-2026-126547 High 2026-11-17 Not applicable No public exploit Missing Authorization vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects AutoSys Workload Automation: from 12.1 through 24.2.00.
CVE-2026-126141 Low 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.11 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to make requests to internal network services through repository import functionality due to insufficient validation of destination addresses.
CVE-2026-125920 Medium 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 17.4 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to cause a denial of service affecting Duo usage analytics due to improper input validation.
CVE-2026-125275 High 2026-11-17 Not applicable Proof of concept only Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in device certificate verification in nerves-hub nerves_hub_web allows an unauthenticated remote attacker to cause a denial of service via a TLS client certificate whose CA is not registered. When a client certificate chains to a root in the device endpoint's trust store but no CA in the chain is registered in NervesHub, NervesHub.SSL.decide/2 refuses it with the reason :unknown_ca. Erlang/OTP ssl reads that reason as a missing trust anchor, looks for an alternative root, finds the same root and validates again without end. The handshake process queries the database on each pass and keeps running after the client disconnects, until the node restarts. The device endpoint trusts the public roots from CAStore unless DEVICE_SSL_CACERTFILE is set, so a client certificate from a public CA whose chain allows client authentication is sufficient. A chain that ends at a root outside the trust store is refused once. This issue affects nerves_hub: from 1.0.0 before 2.5.4.
CVE-2026-125165 Medium 2026-11-17 Not applicable No public exploit The RSS widget of the dashboard allows backend users to configure the URL of the RSS feed in the widget settings. The URL was fetched by the server without restricting the target host. Backend users with access to the dashboard could therefore make the server send HTTP requests to arbitrary hosts, including internal network services and cloud metadata endpoints, which are not reachable from the outside.
CVE-2026-125164 Medium 2026-11-17 Not applicable No public exploit The file dump controller (eID=dumpFile) delivers files, file references and processed files identified by their uid, protected by a token. The token only covered the uid value, but not the type of the requested resource. A valid token issued for a file could therefore be reused to request a file reference or a processed file with the same uid. As a result, unauthenticated visitors could download files, for example from non-public storages, for which no token had been issued.
CVE-2026-125163 Medium 2026-11-17 Not applicable No public exploit The FileUpload and ImageUpload elements of the Form Framework use the property allowedMimeTypes as an allow list of MIME types accepted for upload. An empty allowedMimeTypes list was treated as "no restriction". Forms containing upload elements without any configured MIME type, for example in manually created form definitions or when all MIME types were deselected in the form editor, accepted any file except those blocked by the file deny pattern, which only covers PHP-related file extensions. This allowed unauthenticated users to upload files with browser-executable content, such as HTML or SVG documents, to the configured upload folder, which by default is located in a public storage. If attackers know the URL of an uploaded file (see TYPO3-CORE-SA-2026-029), this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder.
CVE-2026-125162 High 2026-11-17 Not applicable No public exploit The cHash argument, which ensures that only URL arguments originally generated by TYPO3 create separate page cache entries, was treated inconsistently when it was passed as an array. The cHash validation treated such a value as missing, while the page cache identifier treated it as present and included all URL arguments. As a result, unauthenticated visitors could create an unlimited number of page cache entries and trigger uncached page renderings by adding an array cHash with arbitrary values to any URL. This could exhaust server resources and fill the page cache storage. Only installations where the cHash validation is not enforced via $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['enforceValidation'] are affected. This setting is enabled by default for new installations since TYPO3 v12, but is often still disabled in installations upgraded from older versions.
CVE-2026-125161 Medium 2026-11-17 Not applicable No public exploit The fix for TYPO3-CORE-SA-2026-009 was incomplete. GeneralUtility::sanitizeLocalUrl performed its checks on the URL-decoded value, but returned the original, URL-encoded value. URLs containing certain percent-encoded characters therefore passed the sanitization checks as local URLs, although they point to an external host. Applications that use the sanitized URL for redirects are vulnerable to open redirect attacks. This enables attackers to redirect users to external content and carry out phishing attacks. In the TYPO3 core, this affects redirects in the backend, which require the victim to be logged in to the backend.
CVE-2026-125160 Medium 2026-11-17 Not applicable No public exploit Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. If storing an uploaded file failed, for example because of a file name exceeding the file system's length limit, the raw error message was shown to the frontend user disclosing the storage path including the unguessable folder name and the server's temporary upload directory. With this information, attackers could determine the public URL of files they upload through the form. If a form allows uploading files that browsers can execute, such as HTML documents, this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder. This vulnerability is known to be actively exploited.
CVE-2026-125159 High 2026-11-17 Not applicable No public exploit ImageMagick and GraphicsMagick use small modules, called "coders", to read each image format. When processing images, TYPO3 determined the coder from the file type detected by the file contents, as long as the detected mime-type started with image/. A file containing MVG (Magick Vector Graphics) instructions, uploaded with an image file extension like .png, was therefore processed with the MVG coder. MVG instructions can read local files into the processed image, which allows disclosing the contents of arbitrary files readable by the web server, for example configuration files containing credentials, through a publicly accessible processed image. Exploiting this vulnerability requires a way to upload files without a mime-type check, for example a public form of the Form Framework using a FileUpload or ImageUpload element without configured allowedMimeTypes (see TYPO3-CORE-SA-2026-032), which allows exploitation by unauthenticated visitors. Additionally, ImageMagick must be used for image processing, and its default system configuration must allow the MVG coder.
CVE-2026-12487 High 2026-11-17 Not applicable No public exploit An incorrect authorization vulnerability in the SNMP parameter of Zyxel EE5301-00 customized firmware version 5.63(ACLD.2)b3_D0 could allow an unauthenticated attacker to cause a denial-of-service (DoS) condition on an affected device.
CVE-2026-124709 Unknown 2026-11-17 Not applicable No public exploit Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary.
CVE-2026-124646 High 2026-11-17 Not applicable No public exploit This vulnerability exists in e-Sushrut HMIS due to insufficient server side object level authorization validation in the API endpoint. An unauthenticated remote attacker could exploit this vulnerability by modifying the parameter value in the API request. Successful exploitation of this vulnerability could allow the attacker to enumerate and gain unauthorized access to sensitive information of patients on the targeted healthcare organization.
CVE-2026-124645 High 2026-11-17 Not applicable No public exploit This vulnerability exists in e-Sushrut HIMS due to the use of a static and predictable value in the client-side password hashing mechanism, which is embedded in the login page and accessible to unauthenticated users. An unauthenticated remote attacker could exploit this vulnerability by accessing the login page, extracting the embedded value and using it to reproduce the password hashing process. Successful exploitation of this vulnerability could weaken the security of the authentication mechanism and potentially facilitate authentication related attacks on the targeted healthcare organization.
CVE-2026-124644 Medium 2026-11-17 Not applicable No public exploit This vulnerability exists in e-Sushrut HMIS due to the exposure of internal hospital operational statistics through data structure embedded in the HTML response of the login page. An unauthenticated remote attacker could exploit this vulnerability by accessing the affected login page and extracting the returned HTML content. Successful exploitation of this vulnerability could allow the attacker to gain unauthorized access to internal hospital operational information associated with the targeted healthcare organization.
CVE-2026-124643 High 2026-11-17 Not applicable No public exploit This vulnerability exists in e-Sushrut HMIS due to insufficient authentication and session validation in the dashboard functionality. An unauthenticated remote attacker could exploit this vulnerability by sending specially crafted HTTP requests to the affected endpoint. Successful exploitation of this vulnerability could allow the attacker to gain unauthorized access to the dashboard information associated with the targeted healthcare organization.
CVE-2026-123142 Medium 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user holding an MCP-scoped OAuth token to perform unauthorized issuable state changes on issues and merge requests, including approving and merging, due to incorrect authorization checks.
CVE-2026-123052 Medium 2026-11-17 Not applicable No public exploit The CeliachiaRL integration component distributed with Farmasimplex uses shared OAuth credentials across multiple customer installations. An attacker who obtains the credentials from one installation could reuse them against services associated with other installations, potentially leading to unauthorized access to sensitive information or modification of integration data.
CVE-2026-123051 Low 2026-11-17 Not applicable No public exploit The REV.exe module distributed with Farmasimplex contains embedded OAuth client credentials for integration with the IZS platform. An attacker with access to the executable could extract and reuse the credentials, potentially leading to unauthorized access to integration resources or manipulation of associated information, depending on the privileges granted and authentication controls in place.
CVE-2026-123050 High 2026-11-17 Not applicable No public exploit Multiple Farmasimplex healthcare integration modules do not properly validate TLS certificates, allowing an attacker who can intercept network traffic to impersonate trusted healthcare services and perform man-in-the-middle attacks, potentially leading to disclosure or modification of sensitive data.
CVE-2026-12239 High 2026-11-17 Not applicable No public exploit The WP Abstracts plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.7.6. This is due to a missing capability check on the wpabs_save_regform AJAX action and the use of a static, frontend-exposed nonce that allows any authenticated user to persist attacker-controlled form schemas with arbitrary wpSync mappings that are later used as user meta keys in the wpabstracts_sync_wpfields function. This makes it possible for authenticated attackers, with subscriber-level access and above, to elevate their privileges to administrator.
CVE-2026-122226 Low 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to access GitLab Duo features restricted by group-based access rules due to improper handling of failed updates to those rules.
CVE-2026-122153 Unknown 2026-11-17 Not applicable No public exploit The TouchOffice API `clerkList` endpoint appears to return sensitive clerk authentication data, including clerk PINs and iButton serial numbers. If the endpoint is accessible to callers who do not require access to these values, the API exposes reusable authentication material beyond the minimum information necessary for clerk-list functionality.
CVE-2026-122152 Unknown 2026-11-17 Not applicable No public exploit The ICRTouch white-label TouchTakeaway Cordova applications do not implement certificate or public-key pinning for backend HTTPS connections. The applications therefore rely exclusively on the device’s system trust store when validating server certificates. An attacker who can cause a device to trust an attacker-controlled certificate authority, or who operates through a compromised or improperly issued trusted certificate, may be able to intercept and modify application traffic.
CVE-2026-122150 Unknown 2026-11-17 Not applicable No public exploit The PocketTouch and TouchPoint POS `CHECKPAYMENT` workflow accepts a caller-supplied clerk number without adequately verifying that the requesting client is authorized to act as that clerk. An attacker with access to the POS protocol may be able to specify another employee’s clerk identifier and submit payment-related requests under that identity.
CVE-2026-122149 Unknown 2026-11-17 Not applicable No public exploit The PocketTouch and TouchPoint POS protocol includes a `SAVECONFIG` command that appears capable of overwriting till configuration files remotely. An attacker with network access to the POS socket service may be able to submit a crafted `SAVECONFIG` command and replace or modify terminal configuration data.
CVE-2026-122147 Unknown 2026-11-17 Not applicable No public exploit ICRTouch PocketTouch version 1.700 build 2025.3726 defines hard-coded default values for multiple credential fields, including a socket password and configuration and shutdown passwords. An additional email-related password field is initialized without a value.
CVE-2026-122145 Unknown 2026-11-17 Not applicable No public exploit ICRTouch PocketTouch version 1.700 build 2025.3726 transmits the POS socket password in plaintext XML over an unencrypted TCP connection. The protocol does not provide transport-layer encryption to protect credentials from interception. An attacker able to observe network traffic between a PocketTouch device and a TouchPoint POS terminal can recover the socket password from captured packets.
CVE-2026-122143 Unknown 2026-11-17 Not applicable No public exploit ICRTouch Commander administrative interface performs security-sensitive operations through HTTP GET requests and includes an API key in the request query string. GET requests are commonly retained in browser history, proxy logs, server logs, analytics systems, referrer headers, and other intermediary records.
CVE-2026-122142 Unknown 2026-11-17 Not applicable No public exploit ICRTouch Commander administrative login interface does not adequately restrict repeated authentication attempts. The interface also returns distinguishable responses for multiple authentication states, including different behavior when a `siteID` value is supplied.
CVE-2026-122141 Unknown 2026-11-17 Not applicable No public exploit The wallet top-up functionality in ICRTouch ByTable and TouchTakeaway does not adequately protect state-changing requests against CSRF. An attacker-controlled website can cause an authenticated customer’s browser to submit a wallet top-up request and add an attacker-selected charge to the customer’s active cart.
CVE-2026-122125 Unknown 2026-11-17 Not applicable No public exploit ICRTouch ByTable and TouchTakeaway do not consistently implement anti-CSRF protections for state-changing web requests. The affected functionality does not require a per-session CSRF token or otherwise verify that requests originated from an authorized application context. An attacker who convinces an authenticated user to visit a malicious website may cause the user’s browser to submit unauthorized requests to the platform using the user’s active session.
CVE-2026-122122 Unknown 2026-11-17 Not applicable No public exploit The order-tracking functionality in ICRTouch ByTable and TouchTakeaway does not adequately verify that a requester is authorized to access the specified order. An unauthenticated remote attacker can modify an order identifier to retrieve information associated with other customers’ orders.
CVE-2026-122055 Unknown 2026-11-17 Not applicable No public exploit ICRTouch PocketTouch version 1.700 build 2025.3726 contains a default socket password set to the literal value password. Where the default value remains unchanged and is accepted by a TouchPoint POS terminal, an attacker with network access to the terminal’s socket service may authenticate using publicly known credentials.
CVE-2026-122045 Medium 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 16.10 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to configure GitLab Duo settings for groups without an eligible license due to missing authorization checks.
CVE-2026-121948 Low 2026-11-17 Not applicable No public exploit GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to change the GitLab Duo Code Review consent setting of a parent group due to incorrect authorization checks.
CVE-2026-121865 High 2026-11-17 Not applicable No public exploit In nanobot, the WebSocket gateway allows a standard client holding a valid client token to select an existing directory outside the operator-configured workspace as the root of a new conversation. The agent can then read and expose files in that directory that are readable by the nanobot service account. This issue affects nanobot (nanobot-ai) from 0.3.5 before 0.4.1.
CVE-2026-121864 High 2026-11-17 Not applicable No public exploit In nanobot, when sandboxed exec is enabled, the shell executable used to run commands can be selected by the caller and is launched before the sandbox is applied. An attacker who can induce the agent to create an executable in the workspace and select it as the shell can cause that executable to run outside the sandbox (e.g. Linux bubblewrap), with the operating-system permissions of the nanobot process. This issue affects nanobot (nanobot-ai) from 0.2.1 before 0.4.1.
‹ prev page 2 of 3,898 next ›