1. Forum
  2. Mailing Lists
  3. Cybersecurity & Infrastru

  • Vulnerability Summary for the Week of June 22, 2026

    From CISA@cisa@messages.cisa.gov to cisa@toolazy.synchro.net on Mon Jun 29 18:31:10 2026
    --===============4218377396049682665==
    Content-Type: multipart/alternative; boundary="===============4830605103477052940=="
    MIME-Version: 1.0

    --===============4830605103477052940==
    Content-Type: text/plain; charset="utf-8"
    MIME-Version: 1.0
    Content-Transfer-Encoding: quoted-printable

    Cybersecurity and Infrastructure Security Agency (CISA)

    You are subscribed to Vulnerability Bulletins for Cybersecurity and Infrast= ructure Security Agency. This information has recently been updated and is = now available.

    The CISA Vulnerability Bulletin provides a summary of new vulnerabilities t= hat have been recorded in the past week. In some cases, the vulnerabilities=
    in the bulletin may not yet have assigned CVSS scores.

    Vulnerabilities are based on the=C2=A0Common Vulnerabilities and Exposures =
    [ https://www.cve.org/ ]=C2=A0(CVE) vulnerability naming standard and are o= rganized according to severity, determined by the=C2=A0Common Vulnerability=
    Scoring System [ https://www.cve.org/about/relatedefforts ]=C2=A0(CVSS) st= andard. The division of high, medium, and low severities correspond to the = following scores:


    * *High*: vulnerabilities with a CVSS base score of 7.0=E2=80=9310.0=20
    * *Medium*: vulnerabilities with a CVSS base score of 4.0=E2=80=936.9=20
    * *Low*: vulnerabilities with a CVSS base score of 0.0=E2=80=933.9=20

    Entries may include additional information provided by organizations and ef= forts sponsored by CISA. This information may include identifying informati= on, values, definitions, and related links. Patch information is provided w= hen available. Please note that some of the information in the bulletin is = compiled from external, open-source reports and is not a direct result of C= ISA analysis.

    =C2=A0

    Vulnerability Summary for the Week of June 22, 2026 [ https://www.cisa.gov/= news-events/bulletins/sb26-180 ] 06/29/2026 2:30 PM EDT=20

    High Vulnerabilities

    Primary
    Vendor -- Product Description Published CVSS Score Source Info abhisheksaha= 11--URL Preview The URL Preview plugin for WordPress is vulnerable to Serve= r-Side Request Forgery in all versions up to, and including, 1.0 via the 'u= rl' parameter. This makes it possible for unauthenticated attackers to make=
    web requests to arbitrary locations originating from the web application a=
    nd can be used to query and modify information from internal services. 2026= -06-24 7.2 CVE-2026-12100 [ https://www.cve.org/CVERecord?id=3DCVE-2026-121=
    00 ] adegans--AdRotate Banner Manager The AdRotate Banner Manager plugin fo=
    r WordPress is vulnerable to PHP Code Injection in all versions up to, and = including, 5.17.7 via the 'banner' attribute of the adrotate shortcode. Thi=
    s is due to insufficient input validation and sanitization of the banner sh= ortcode attribute before concatenation into a PHP code string wrapped in W3=
    Total Cache mfunc or Borlabs Cache fragment markers. This makes it possibl=
    e for authenticated attackers, with Contributor-level access and above, to = execute arbitrary PHP code on the server. This vulnerability requires W3 To= tal Cache or Borlabs Cache support to be enabled in AdRotate settings. 2026= -06-24 8.8 CVE-2026-12242 [ https://www.cve.org/CVERecord?id=3DCVE-2026-122=
    42 ] Adenion--Blog2Social Unauthenticated Cross Site Scripting (XSS) in Blo= g2Social <=3D 8.9.2 versions. 2026-06-26 7.1 CVE-2026-56044 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-56044 ] Adobe--Acrobat Reader Acrobat Reader=
    versions 2020.009.20074, 2020.001.30002, 2017.011.30171, 2015.006.30523 an=
    d earlier are affected by an out-of-bounds write vulnerability that could r= esult in arbitrary code execution in the context of the current user. Explo= itation of this issue requires user interaction in that a victim must open =
    a malicious file. 2026-06-23 7.8 CVE-2020-9695 [ https://www.cve.org/CVERec= ord?id=3DCVE-2020-9695 ] Adrian Tobey--Groundhogg Sales Representative SQL = Injection in Groundhogg <=3D 4.5 versions. 2026-06-26 8.5 CVE-2026-57667 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-57667 ] Ads WPQuads--Ads by WPQ= uads Unauthenticated Sensitive Data Exposure in Ads by WPQuads <=3D 3.0.3 v= ersions. 2026-06-26 7.5 CVE-2026-54824 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54824 ] AF themes--WP Post Author Contributor SQL Injection in =
    WP Post Author <=3D 3.9.1 versions. 2026-06-26 8.5 CVE-2026-57643 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-57643 ] Ahmad--JS Help Desk Subscriber=
    Arbitrary File Deletion in JS Help Desk <=3D 3.1.1 versions. 2026-06-25 7.=
    7 CVE-2026-56054 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56054 ] AKIN=
    Software Computer Import Export Industry and Trade Ltd.--CafePlus Missing = authentication for critical function vulnerability in AKIN Software Compute=
    r Import Export Industry and Trade Ltd. CafePlus allows Accessing Functiona= lity Not Properly Constrained by ACLs. This issue affects CafePlus: from 12= .05.03 before 12.05.04. 2026-06-23 8.8 CVE-2026-10711 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-10711 ] akosglys--Syncee Premium Dropshipping & Wh= olesale Unauthenticated Broken Access Control in Syncee Premium Dropshippin=
    g &amp; Wholesale <=3D 1.0.27 versions. 2026-06-26 7.5 CVE-2026-54846 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-54846 ] Algolplus--Advanced Order = Export For WooCommerce Customer Cross Site Scripting (XSS) in Advanced Orde=
    r Export For WooCommerce <=3D 4.0.9 versions. 2026-06-25 7.1 CVE-2026-56042=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-56042 ] Amazon Web Services-= -Language Servers for AWS Improper trust boundary enforcement in Language S= ervers for AWS before version 1.65.0 on all supported platforms may allow a=
    for arbitrary code execution. If a local user opens a maliciously crafted = workspace, any commands within the project configuration files may be autom= atically executed. This issue requires the user to trust the workspace when=
    prompted. To remediate this issue, users should upgrade to Language Server=
    s for AWS version 1.65.0 or higher. 2026-06-23 7.8 CVE-2026-12957 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-12957 ] Amazon Web Services--Language = Servers for AWS Missing symlink validation in Language Servers for AWS may = allow an arbitrary file write outside of the workspace trust boundary. This=
    may occur when a local user opens a workspace with a maliciously crafted s= ymlink that resolves to a file path outside the workspace trust boundary. T=
    o remediate this issue, users should upgrade to version 1.69.0 or higher. 2= 026-06-23 7.8 CVE-2026-12958 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 12958 ] Anthropic--Claude Desktop Cowork Anthropic Claude Desktop Cowork VM=
    image handling (confirmed across v1.1348.0 through v1.2278.0, including v1= .1348.0, v1.1617.0, and v1.2278.0) validates only file presence and a versi=
    on marker string before booting rootfs.img, but does not verify image conte=
    nt integrity at time-of-use. A local attacker with unprivileged code execut= ion as the victim macOS user can modify the VM root filesystem image and ha=
    ve it trusted on subsequent Cowork VM boots, enabling persistent arbitrary = code execution in the VM and access to host-mounted directories. The estima= ted CWE mapping is CWE-353 (Missing Support for Integrity Check). 2026-06-2=
    3 8.7 CVE-2026-7574 [ https://www.cve.org/CVERecord?id=3DCVE-2026-7574 ] an= tlr--ANTLR4 A weakness has been identified in antlr ANTLR4 up to 4.13.2. Af= fected is an unknown function of the file tool/src/org/antlr/v4/codegen/mod= el/OutputFile.java of the component Grammar Action Block Handler. Executing=
    a manipulation can lead to code injection. The attack may be launched remo= tely. The exploit has been made available to the public and could be used f=
    or attacks. The vendor was contacted early about this disclosure but did no=
    t respond in any way. 2026-06-28 7.3 CVE-2026-13500 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-13500 ] Appsbd--Vitepos Unauthenticated Sensitive Da=
    ta Exposure in Vitepos <=3D 3.4.2 versions. 2026-06-25 7.5 CVE-2026-54841 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-54841 ] appsmithorg--appsmith = Appsmith is a platform to build admin panels, internal tools, and dashboard=
    s. Prior to 2.1, the bundled Caddy reverse-proxy's admin API - which has no=
    authentication by default - is bound on 0.0.0.0:2019 inside the container.=
    While this listener is not directly published to the host by docker-compos= e.yml, it is reachable from the Appsmith server process itself or a SSRF vu= lnerability. An authenticated low-privileged user can therefore drive the S= SRF to issue POST /load (or any other admin-API call) against http://0.0.0.= 0:2019/, fully replacing the live Caddy configuration and taking over the r= everse proxy. This vulnerability is fixed in 2.1. 2026-06-24 9.9 CVE-2026-5= 5454 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55454 ] ARforms--ARforms=
    The ARForms plugin for WordPress is vulnerable to Stored Cross-Site Script= ing via the `value` parameter of the `arf_save_incomplete_form_data` AJAX a= ction in all versions up to, and including, 7.1.3 due to insufficient input=
    sanitization and output escaping. This makes it possible for unauthenticat=
    ed attackers to inject arbitrary web scripts that will execute whenever an = administrator views the "Partial Filled Form Entries" page in the ARForms d= ashboard. 2026-06-24 7.2 CVE-2026-3652 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-3652 ] Autodesk--Fusion A maliciously crafted webpage, when vis= ited by a user with Autodesk Fusion Desktop running and the MCP extension e= nabled, can trigger a vulnerability in the MCP extension that could allow a= rbitrary code execution. A successful exploit may allow code to execute wit=
    h the privileges of the current user. 2026-06-22 9.6 CVE-2026-10789 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-10789 ] Averta--Master Slider Unauth= enticated Cross Site Scripting (XSS) in Master Slider <=3D 3.11.2 versions.=
    2026-06-25 7.1 CVE-2026-56014 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-56014 ] Ays Pro--Popup box Administrator SQL Injection in Popup box <=3D = 6.0.1 versions. 2026-06-26 7.6 CVE-2026-57631 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-57631 ] bestwebsoft--Gallery Contributor SQL Injection in = Gallery <=3D 4.7.8 versions. 2026-06-26 8.5 CVE-2026-57642 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-57642 ] bitwarden--server Bitwarden Server be= fore 2026.5.0 contains a privilege escalation vulnerability that allows aut= henticated Custom users with ManageUsers permission to remove Admin account=
    s from an organization by exploiting a missing role hierarchy check in the = bulk user-remove endpoint. Attackers can supply Admin organization-user IDs=
    in a bulk DELETE request to bypass the guard enforced on the single-user r= emoval path, effectively removing one or more Admin accounts from an organi= zation. 2026-06-25 7.1 CVE-2026-57520 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-57520 ] Bootstrapped Ventures--Visual Link Preview Subscriber Sens= itive Data Exposure in Visual Link Preview <=3D 2.3.1 versions. 2026-06-25 = 7.4 CVE-2026-54821 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54821 ] bP= lugins--MailChimp Block Unauthenticated Broken Access Control in MailChimp = Block <=3D 1.1.15 versions. 2026-06-26 8.3 CVE-2026-56063 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-56063 ] bPlugins--Panorama Viewer 360 Degree I= mage + Video Viewer Contributor Local File Inclusion in Panorama Viewer - 3=
    60 Degree Image + Video Viewer <=3D 1.6.1 versions. 2026-06-26 7.5 CVE-2026= -57647 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57647 ] BuddyBoss--Bud= dyboss Platform Subscriber PHP Object Injection in Buddyboss Platform <=3D = 3.0.4 versions. 2026-06-26 9.8 CVE-2026-56032 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-56032 ] Budibase--budibase Budibase is an open-source low-= code platform. Prior to 3.39.12, an unauthenticated visitor of any publishe=
    d Budibase app reads every document of the backing MongoDB, CouchDB, Elasti= csearch, DynamoDB-PartiQL, or REST-with-JSON-body collection and, where the=
    builder has published a PUBLIC write query, modifies every document of tha=
    t collection with one HTTP request. enrichContext at packages/server/src/sd= k/workspace/queries/queries.ts:121-138 substitutes parameter values into th=
    e raw JSON body of a query, then JSON.parses the result. The validator vali= dateQueryInputs at packages/server/src/api/controllers/query/index.ts:61-71=
    rejects only Handlebars markers ({{, }}) in user input and does not escape=
    JSON metacharacters (", \, }). A parameter value containing a closing quot=
    e and additional keys lifts attacker-controlled fields into the parsed filt=
    er object. For Mongo find, the parsed filter passes directly to collection.= find() (packages/server/src/integrations/mongodb.ts:506-510). Duplicate-key=
    JSON parsing overrides the builder's {name: "..."} with {name: {$exists: t= rue}} and returns every document. The same primitive against an updateMany = query (mongodb.ts:577-585) widens the filter scope to the full collection w= hile the builder-controlled $set body runs against every matched document. = The authorized middleware at packages/server/src/middleware/authorized.ts:1= 41-148 short-circuits when the query's role is PUBLIC. CSRF is not enforced=
    on this path. POST /api/v2/queries/:queryId (packages/server/src/api/route= s/query.ts:63) accepts the call with no session, only an x-budibase-app-id = header that is public from the published-app URL. This vulnerability is fix=
    ed in 3.39.12. 2026-06-26 10 CVE-2026-54350 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-54350 ] Budibase--budibase Budibase is an open-source low-co=
    de platform. Prior to 3.39.9, `POST /api/pwa/process-zip` at packages/serve= r/src/api/routes/static.ts:24 accepts a builder-uploaded .zip, extracts it = with extract-zip@2.0.1 into a temp directory, then for each entry listed in=
    icons.json validates the icon path, opens it, and streams the bytes into M= inIO. The resulting object is served back via GET /api/assets/{appId}/pwa/{= uuid}.png. extract-zip@2.0.1 preserves absolute symlink targets when restor= ing symlink entries. The icon-source validator at packages/server/src/api/c= ontrollers/static/index.ts:259-268 resolves the icon source string against = baseDir (path.resolve), checks resolvedSrc.startsWith(baseDir + path.sep) a= gainst that string, and calls fs.existsSync(resolvedSrc) which follows symb= olic links to confirm the target exists. None of the three calls reject sym= bolic-link entries. packages/backend-core/src/objectStore/objectStore.ts:30=
    2 then calls (await fsp.open(path)).createReadStream() on the resolved path=
    . fsp.open follows the symlink, the target file's bytes stream into MinIO, = and the response of the asset-fetch endpoint returns those bytes verbatim. = Result: a workspace-level builder reads any file the server process can ope=
    n. This vulnerability is fixed in 3.39.9. 2026-06-26 9.6 CVE-2026-54352 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-54352 ] Budibase--budibase Budib= ase is an open-source low-code platform. Prior to 3.39.9, the webhook trigg=
    er endpoint in Budibase is publicly accessible and passes the full HTTP req= uest body into automation execution parameters. A mass assignment vulnerabi= lity in externalTrigger() allows an attacker to overwrite the internal appI=
    d property by including it in the webhook POST body. When the automation is=
    processed asynchronously (the default path for webhooks without a collect = step), the worker executes the attacker-defined automation in the context o=
    f the victim's workspace, granting full read/write access to the victim's d= atabase. This vulnerability is fixed in 3.39.9. 2026-06-26 8.2 CVE-2026-543=
    51 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54351 ] Budibase--budibase=
    Budibase is an open-source low-code platform. Prior to 3.39.9, authenticat=
    ed users with automation permissions can bypass Budibase's SSRF blacklist t= hrough DNS rebinding. The outbound fetch flow validates a hostname against = the blacklist before the request is sent, but the actual socket connection = later performs a separate DNS lookup through node-fetch. Since the validate=
    d IPs are never pinned to the connection, an attacker-controlled hostname c=
    an return a public IP during validation and a private/internal IP during th=
    e real connection. This results in a non-blind SSRF primitive against inter= nal services reachable from the Budibase host, including loopback, RFC1918 = ranges, and cloud metadata endpoints. This vulnerability is fixed in 3.39.9=
    . 2026-06-26 8.5 CVE-2026-54353 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-54353 ] Budibase--budibase Budibase is an open-source low-code platform.=
    Prior to 3.39.0, `GET /api/chat-links/:instance/:token/handoff` is a publi=
    c endpoint (no auth required) that performs a permanent, state-changing ope= ration: it binds an external chat identity (Slack/Discord/MS Teams) to an a= uthenticated Budibase user account, with no consent UI and no CSRF protecti= on. The session token in the URL is created by the attacker (from their own=
    /link slash command) and embeds the attacker's externalUserId. When an aut= henticated Budibase victim visits the URL, their account is silently and pe= rmanently linked to the attacker's Slack/Discord identity. The server respo= nds with "Authentication succeeded." - no indication of what was linked. Th=
    is vulnerability is fixed in 3.39.0. 2026-06-26 7.3 CVE-2026-50132 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-50132 ] Budibase--budibase Budibase i=
    s an open-source low-code platform. Prior to 3.39.3, the application server=
    exposes an unauthenticated endpoint that generates S3 PutObject presigned = URLs using credentials stored in a workspace datasource. The route is prote= cted only by the recaptcha middleware and does not require authentication, = table permission, datasource permission, or builder access. A public caller=
    who knows a workspace ID and S3 datasource ID can request a signed upload = URL for attacker-controlled bucket and key values. This vulnerability is fi= xed in 3.39.3. 2026-06-26 7.4 CVE-2026-50136 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-50136 ] bytuncay--Kargo Takip The Kargo Takip plugin for Wo= rdPress is vulnerable to Server-Side Request Forgery in all versions up to,=
    and including, 1.2 via the 'api_url' parameter. This makes it possible for=
    unauthenticated attackers to make web requests to arbitrary locations orig= inating from the web application and can be used to query and modify inform= ation from internal services. The script echoes internal API response data = (specifically the value of any 'auth' key in a JSON response body) verbatim=
    back to the attacker's browser, enabling direct exfiltration of responses = from internal services such as cloud instance metadata endpoints. 2026-06-2=
    4 7.2 CVE-2026-12095 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12095 ] = Cacti--cacti Cacti is an open source performance and fault management frame= work. In versions 1.2.30 and prior, the rfilter request variable was concat= enated into a RLIKE SQL clause without sanitization. The endpoint does not = require authentication (graph viewing supports guest access via the configu= red guest user), so the SQLi was reachable pre-auth on installs with guest = viewing enabled. This issue was fixed in version 1.2.31. 2026-06-24 9.8 CVE= -2026-39893 [ https://www.cve.org/CVERecord?id=3DCVE-2026-39893 ] Cacti--ca= cti Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior have unauthenticated LFI through graph_theme and rrd= tool IPC serialization hardening. This issue has been resolved in version 1= .2.31. 2026-06-24 9.8 CVE-2026-39938 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-39938 ] Cacti--cacti Cacti is an open source performance and fault = management framework. Versions 1.2.30 and prior have pre-authentication SQL=
    Injection via unanchored FILTER_VALIDATE_REGEXP in graph_view.php. This is= sue has been fixed in version 1.2.31. 2026-06-24 9.8 CVE-2026-39955 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-39955 ] Cacti--cacti Cacti is an ope=
    n source performance and fault management framework. Versions 1.2.30 and pr= ior have a Stored SQL Injection vulnerability through graph_name_regexp in = the Reports feature. This issue has been fixed in version 1.2.31. 2026-06-2=
    4 7.6 CVE-2026-39951 [ https://www.cve.org/CVERecord?id=3DCVE-2026-39951 ] = Cacti--cacti Cacti is an open source performance and fault management frame= work. Versions 1.2.30 and prior have SQL Injection through unsanitized unse= rialize+implode in managers.php. At line 756 of managers.php, the applicati=
    on assigns $selected_items by calling cacti_unserialize(stripslashes(gnrv('= selected_graphs_array'))). The cacti_unserialize() function calls unseriali= ze() with allowed_classes set to false, which prevents object injection but=
    still allows arbitrary string arrays to be deserialized. Then, at lines 76=
    0 to 766, the deserialized array values are passed directly into db_execute= ('DELETE FROM snmpagent_managers WHERE id IN (' . implode(',', $selected_it= ems) . ')'), where they are imploded into the SQL statement without any int= eger validation, resulting in SQL Injection when using SNMP agent managemen=
    t permissions. This issue has been fixed in version 1.2.31. 2026-06-25 7.2 = CVE-2026-40083 [ https://www.cve.org/CVERecord?id=3DCVE-2026-40083 ] caddys= erver--caddy Caddy is an extensible server platform that uses TLS by defaul=
    t. From 2.7.0 until 2.11.3, the FastCGI transport's splitPos() in modules/c= addyhttp/reverseproxy/fastcgi/fastcgi.go misuses golang.org/x/text/search w= ith search.IgnoreCase when the request path contains a non-ASCII byte. Two = distinct flaws in that fallback let an attacker mislead Caddy's FastCGI spl= itting into treating a non-.php (or other configured split_path extension) = file as a script. In any deployment where the attacker can place content in=
    to a file served via FastCGI (uploads, file storage, etc.), this can be esc= alated to remote code execution by crafting a URL whose path triggers eithe=
    r flaw. This vulnerability is fixed in 2.11.3. 2026-06-23 8.1 CVE-2026-4513=
    5 [ https://www.cve.org/CVERecord?id=3DCVE-2026-45135 ] caddyserver--caddy = Caddy is an extensible server platform that uses TLS by default. Prior to 2= .11.4, forward_auth copy_headers deletes the exact client-supplied identity=
    header before copying the trusted value from the auth gateway. But when th=
    e request later goes through php_fastcgi, Caddy normalizes HTTP headers int=
    o CGI variables by replacing - with _. This lets a client send an underscor=
    e alias that survives the forward_auth delete step but becomes the same PHP= /FastCGI variable. Result: a remote client can inject or sometimes override=
    identity/group headers trusted by PHP/FastCGI applications behind Caddy. T= his vulnerability is fixed in 2.11.4. 2026-06-23 8.1 CVE-2026-52845 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-52845 ] caddyserver--caddy Caddy is =
    an extensible server platform that uses TLS by default. Prior to 2.11.4, on=
    Windows, Caddy path matchers treat /private\secret.txt as outside /private= /*, but file_server later resolves the same request path as private\secret.= txt on disk. An unauthenticated remote client can bypass Caddy path-scoped = auth/deny routes protecting /private/*. This vulnerability is fixed in 2.11= .4. 2026-06-23 7.5 CVE-2026-52844 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-52844 ] canboat--canboat CANBoat through 6.22, fixed in commit a5a22b7=
    , contains an off-by-one global buffer overflow in the searchForPgn() funct= ion in analyzer/pgn.c that allows remote attackers to crash the application=
    . Attackers can deliver a crafted NMEA-2000 message with an out-of-range PG=
    N value over CAN bus or N2K-over-IP to trigger an out-of-bounds array acces=
    s and denial of service. 2026-06-25 7.3 CVE-2026-56790 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-56790 ] Canonical--LXD A privilege escalation vul= nerability exists in LXD from 6.0 before 6.9, 5.21.0 before 5.21.5, and 5.0=
    .0 before 5.0.7 regarding the handling of project-restriction policies duri=
    ng snapshot restoration.. An authenticated project operator in a restricted=
    multi-tenant environment can bypass policy restrictions by importing a mal= iciously crafted instance backup containing restricted configuration keys w= ithin a snapshot. When the snapshot is restored, these restricted keys are = applied to the live instance without policy validation. Starting the modifi=
    ed instance grants the operator unauthorized host root access. 2026-06-26 7=
    .2 CVE-2026-9640 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9640 ] Canon= ical--lxd Broken Access Control in the devLXDInstancePatchHandler component=
    of Canonical LXD allows an untrusted guest to mount, read, and overwrite a= nother guest's custom storage volume via a crafted device PATCH request ove=
    r /dev/lxd when security.devlxd.management.volumes is enabled. 2026-06-26 8=
    .4 CVE-2026-12411 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12411 ] Cap= -go--capgo Supabase Capgo before 12.128.2 contains an authorization bypass = vulnerability in the SECURITY DEFINER record_build_time RPC function that a= llows unauthenticated attackers to insert arbitrary build-time records. Att= ackers can exploit this by calling POST /rest/v1/rpc/record_build_time with=
    a public API key to poison billing and quota data for any organization, en= abling resource exhaustion and cross-tenant billing manipulation. 2026-06-2=
    4 8.2 CVE-2026-56245 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56245 ] = Cap-go--capgo Cap-go capgo (capgo-backend) before 12.128.12 contains an una= uthenticated denial-of-service vulnerability arising from the audit_logs ta= ble's Row-Level Security (RLS) policy when accessed via the Supabase PostgR= EST API. Because the PostgreSQL query planner executes costly logic before = RLS rejection, unfiltered queries to the public.audit_logs endpoint using t=
    he public anon key consistently trigger statement timeouts (PostgREST error=
    57014). Under concurrency, this exhausts database resources and causes cas= cading HTTP 500 failures on unrelated endpoints (e.g. /orgs), resulting in =
    an application-layer denial of service. 2026-06-23 7.5 CVE-2026-56248 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-56248 ] Cap-go--capgo Cap-go befor=
    e 12.128.2 contains a privilege inversion vulnerability in GET /build/logs/= :jobId that allows read-only API key holders to cancel running native build=
    s. The endpoint registers an abort listener on the SSE stream that uncondit= ionally invokes cancelBuildOnDisconnect() using the privileged server-side = BUILDER_API_KEY when clients disconnect, bypassing the app.build_native per= mission check required by the explicit POST /build/cancel/:jobId endpoint. = Attackers with read-only API keys can repeatedly disrupt native build opera= tions and CI/CD workflows by opening the log stream and dropping the connec= tion. 2026-06-22 7.1 CVE-2026-56280 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-56280 ] Capgo--Capgo Capgo before 12.128.2 contains a broken authent= ication vulnerability in its API key generation mechanism. API keys are exp= osed in frontend requests, and the backend fails to validate that keys are = securely generated and bound to the authenticated user. An attacker can tam= per with the API key parameter in the generation request and supply arbitra=
    ry values, generating custom API keys without proper authorization, which c=
    an lead to unauthorized access to protected endpoints. 2026-06-24 9.1 CVE-2= 026-56237 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56237 ] Capgo--Capg=
    o Capgo before 12.128.2 contains a cross-domain SSO account takeover vulner= ability in the provision-user endpoint that allows attackers to merge arbit= rary victim accounts based on email match without validating SSO provider d= omain authorization. An attacker with enterprise org admin access and a mal= icious IdP can forge SAML assertions containing victim email addresses to t= rigger account merge and gain full access to victim accounts, organizations=
    , and data. 2026-06-24 8.7 CVE-2026-56223 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-56223 ] Capgo--Capgo Capgo before 12.128.2 contains an authori= zation bypass vulnerability in its public API key management handlers (get/= put/delete/post). API keys created with mode=3Dall but restricted to a sing=
    le app via limited_to_apps are only checked for limited_to_orgs and not for=
    limited_to_apps, so an app-scoped key can enumerate, update, and delete si= bling API keys belonging to the same account that are outside its declared = app scope, enabling tampering with account-level credentials. 2026-06-23 8.=
    3 CVE-2026-56225 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56225 ] Capg= o--Capgo Capgo before 12.128.2 fails to enforce limited_to_orgs and limited= _to_apps constraints on subkeys provided via x-limited-key-id header in mid= dlewareKey function. Attackers can bypass subkey scope restrictions by refe= rencing their own subkeys, causing all downstream route handlers to use the=
    unrestricted parent key instead of the scoped subkey. 2026-06-24 8.8 CVE-2= 026-56232 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56232 ] Capgo--Capg=
    o Capgo before 12.128.2 contains a security control bypass vulnerability wh= ere the PostgREST/RLS plane accepts plaintext API keys through the capgkey = header despite enforce_hashed_api_keys being enabled. Attackers can bypass = org-level hashed-key enforcement by sending plaintext API keys directly to = the PostgREST/RLS plane to access protected resources. 2026-06-23 8.1 CVE-2= 026-56243 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56243 ] Capgo--Capg=
    o Capgo before 12.128.2 contains a rate limit bypass vulnerability in the c= hannel_self endpoint that allows attackers to circumvent rate limiting by r= otating the user-controlled device_id parameter. Attackers can send multipl=
    e requests per second by changing device_id values to flood the channel_dev= ices table and cause database exhaustion. 2026-06-22 8.2 CVE-2026-56324 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-56324 ] Capgo--Capgo Capgo befor=
    e 12.128.2 contains an authorization bypass vulnerability in POST /private/= role_bindings that fails to verify app_id ownership during app-scoped role = binding creation. An attacker with administrative privileges in one organiz= ation can create role bindings targeting applications owned by other organi= zations, enabling unauthorized read and modification of victim applications=
    . 2026-06-23 7.2 CVE-2026-56222 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-56222 ] Capgo--Capgo Capgo before 12.128.2 contains a broken object leve=
    l authorization (BOLA) vulnerability in the POST /build/start/:jobId and PO=
    ST /build/cancel/:jobId endpoints. The handlers authorize the request based=
    only on the attacker-controlled app_id supplied in the request body and ne= ver verify that the jobId in the URL belongs to that app_id (or the same te= nant/org) before issuing privileged builder commands with the server-held b= uilder API key. An authenticated user with the app.build_native permission = for any app they control can start or cancel arbitrary builder jobs belongi=
    ng to other tenants by supplying a victim jobId, resulting in cross-tenant = build sabotage (denial of service), unauthorized compute actions, and poten= tial billing impact. 2026-06-24 7.6 CVE-2026-56231 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-56231 ] Capgo--Capgo Capgo before 12.128.2 allows non= -admin API keys to read webhook signing secrets via Supabase REST due to in= sufficient row-level security policies on the webhooks table. Attackers can=
    retrieve the webhook secret and forge valid X-Capgo-Signature headers to s= end authenticated webhook events to configured receivers, breaking webhook = authenticity and integrity. 2026-06-24 7.1 CVE-2026-56244 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-56244 ] Capgo--Capgo Capgo before 12.128.2 enf= orces mandatory two-factor authentication only at the UI level. Sensitive O= rganization (ORG) management API endpoints (e.g., editing organization deta= ils, inviting users) do not validate 2FA completion on the backend. An auth= enticated Admin user who has not enabled 2FA can replay or modify a previou= sly captured ORG API request to perform privileged organization actions, by= passing the globally enforced 2FA requirement. 2026-06-24 7.1 CVE-2026-5625=
    6 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56256 ] Capgo--Capgo Capgo = before 12.128.2 allows direct patching of public.apps.owner_org through Pos= tgREST, bypassing the transfer_app() workflow and creating split-brain owne= rship. Attackers can directly update apps.owner_org while leaving app_versi= ons.owner_org unchanged, enabling old-org keys to retain access to version = data while new-org keys control the app record. 2026-06-24 7.1 CVE-2026-562=
    57 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56257 ] Capgo--Capgo Capgo=
    before 12.128.12 fails to filter deleted app versions when joining channel=
    s during /updates resolution, allowing deleted bundles to remain selectable=
    . Attackers can continue deploying deleted bundles to devices by exploiting=
    the missing app_versions.deleted filter in channel version joins. 2026-06-=
    22 7.1 CVE-2026-56314 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56314 ]=
    Capgo--Capgo Capgo before 12.128.2 contains an information disclosure vuln= erability in the unauthenticated /updates endpoint that resolves the defaul= tChannel parameter before enforcing privacy restrictions, allowing attacker=
    s to enumerate private channels and leak version/config state. Unauthentica= ted attackers can probe private channel names and distinguish valid channel=
    s from nonexistent ones based on response differences, revealing assigned b= undle versions and platform-specific configuration details. 2026-06-23 7.5 = CVE-2026-56322 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56322 ] Capgo-= -Capgo Capgo before 12.128.2 contains an information disclosure vulnerabili=
    ty in the /functions/v1/channel_self endpoint that allows unauthenticated a= ttackers to enumerate non-public channel names and determine app existence = and subscription status. Remote attackers can send GET requests with arbitr= ary app_id parameters to disclose internal rollout channels, enumerate vali=
    d applications across tenants, and leak billing status without authenticati=
    on or device binding. 2026-06-22 7.5 CVE-2026-56323 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-56323 ] cgarvey--Email JavaScript Cloak The Email Ja= vaScript Cloak plugin for WordPress is vulnerable to Stored Cross-Site Scri= pting via the plugin's 'email' shortcode in all versions up to, and includi= ng, 1.03 due to insufficient input sanitization and output escaping on user=
    supplied attributes. This makes it possible for authenticated attackers, w= ith contributor-level access and above, to inject arbitrary web scripts in = pages that will execute whenever a user accesses an injected page. 2026-06-=
    24 7.2 CVE-2026-10091 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10091 ]=
    Chainlit--chainlit Chainlit before 2.10.1 contains a session hijacking vul= nerability that allows unauthenticated attackers to restore and inherit aut= henticated user sessions by presenting a valid sessionId during WebSocket s= ession restoration without ownership verification. Attackers can exploit th=
    e restore_existing_session path to assume a victim's permissions and roles,=
    enabling unauthorized invocation of tools and access to data restricted to=
    the authenticated victim. 2026-06-22 8.2 CVE-2026-56104 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-56104 ] CheckView--CheckView Automated Testing = Unauthenticated Broken Access Control in CheckView Automated Testing <=3D 2= .1.0 versions. 2026-06-25 7.5 CVE-2026-54844 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-54844 ] chimurai--http-proxy-middleware http-proxy-middlewa=
    re is node.js http-proxy middleware. From 3.0.4 until 3.0.7 and 4.1.1, fixR= equestBody() is the library's documented helper for re-emitting a request b= ody that was already consumed by a body parser. When the outgoing Content-T= ype is multipart/form-data, it rebuilds the body with handlerFormDataBodyDa= ta(), which interpolates each req.body key and value directly into the mult= ipart wire format without neutralizing CR/LF. A \r\n inside a value (or key=
    ) lets an attacker close the current part and inject an entirely new form p= art. Because the proxy's own body parser saw a single opaque value, any gat= eway-side policy or validation performed on req.body is evaluated against a=
    different set of fields than the upstream backend ultimately parses a requ= est/parameter desynchronization across the trust boundary. This vulnerabili=
    ty is fixed in 3.0.7 and 4.1.1. 2026-06-22 7.5 CVE-2026-55603 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-55603 ] chrisvrichardson--MapPress Maps fo=
    r WordPress Unauthenticated Cross Site Scripting (XSS) in MapPress Maps for=
    WordPress <=3D 2.97.3 versions. 2026-06-26 7.1 CVE-2026-56011 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-56011 ] clearsale--ClearSale Total The Cl= earSale Total plugin for WordPress is vulnerable to SQL Injection via the `= pagseguro[metodo]` POST parameter of the `clearsale_total_push` AJAX action=
    in all versions up to, and including, 3.4.2. The handler is registered for=
    unauthenticated users (`wp_ajax_nopriv_clearsale_total_push`), and althoug=
    h a `wp_verify_nonce()` check exists, the failing branch's `die()` is comme= nted out so execution continues regardless of nonce validity. On PHP < 8.0 = the attacker-supplied `$metodo` value bypasses the `switch ($metodo) { case=
    4: ... }` guard via loose type juggling (the string `"4 AND SLEEP(5)"` com= pares equal to integer `4`), reaching an unquoted `UPDATE wp_cs_total_dados= extras SET metodo=3D$metodo, ...` query. This makes it possible for unauthe= nticated attackers to append additional SQL queries into already existing q= ueries that can be used to extract sensitive information from the database.=
    Exploitation requires the target server to be running PHP < 8.0. 2026-06-2=
    4 7.5 CVE-2026-8705 [ https://www.cve.org/CVERecord?id=3DCVE-2026-8705 ] co= demstory-- Unauthenticated SQL Injection in =C3=AC=E2=80=BA=C5=92=C3=AB=E2= =80=9C=C5=93=C3=AD=E2=80=9D=E2=80=9E=C3=AB=C2=A0=CB=86=C3=AC=C5=A0=C2=A4 = =C3=AA=C2=B2=C2=B0=C3=AC=C2=A0=C5=93 =C3=AC=E2=80=B9=C2=AC=C3=AD=E2=80=9D= =C5=92=C3=AD=C5=BD=CB=9C=C3=AC=C2=9D=C2=B4 <=3D 5.5.6 versions. 2026-06-26 = 9.3 CVE-2026-56036 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56036 ] co= ntempoinc--Real Estate 7 Unauthenticated SQL Injection in Real Estate 7 <=
    =3D 3.5.9 versions. 2026-06-26 9.3 CVE-2026-54827 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-54827 ] corvuspay--CorvusPay WooCommerce Payment Gatew=
    ay Unauthenticated Broken Authentication in CorvusPay WooCommerce Payment G= ateway <=3D 2.7.4 versions. 2026-06-26 7.5 CVE-2026-56029 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-56029 ] Cory Marsh--BitFire Security Unauthent= icated Multiple Vulnerabilities in BitFire Security <=3D 5.0.3 versions. 20= 26-06-26 8.6 CVE-2026-56035 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 6035 ] Crawl4AI--Crawl4AI Crawl4AI before 0.8.8 contains an arbitrary file = write vulnerability in the screenshot and PDF endpoints that allows unauthe= nticated attackers to write files outside the intended directory via symlin=
    k and time-of-check-time-of-use (TOCTOU) attacks on the output_path paramet= er. Remote attackers can exploit insufficient path validation and symlink f= ollowing to achieve arbitrary file write and potential code execution on sy= stems where the runtime user has write access to executable or cron locatio= ns. 2026-06-23 8.1 CVE-2026-56258 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-56258 ] Crawl4AI--Crawl4AI Crawl4AI before 0.8.7 contains a server-sid=
    e request forgery vulnerability in the /crawl, /crawl/stream, /md, and /llm=
    endpoints that fetch arbitrary user-supplied URLs without validation. Unau= thenticated attackers can bypass the internal-address blocklist using IPv6-= mapped IPv4 addresses to reach internal services and cloud metadata endpoin= ts. 2026-06-22 8.6 CVE-2026-56266 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-56266 ] Creative Themes--Blocksy Companion Pro Contributor Remote Code=
    Execution (RCE) in Blocksy Companion Pro <=3D 2.1.45 versions. 2026-06-26 = 8.5 CVE-2026-57315 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57315 ] Cr= ocoblock. Jetimpex Inc.--JetBooking Unauthenticated SQL Injection in JetBoo= king <=3D 4.0.4.1 versions. 2026-06-26 9.3 CVE-2026-54820 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-54820 ] Crocoblock. Jetimpex Inc.--JetEngine U= nauthenticated SQL Injection in JetEngine <=3D 3.8.10.2 versions. 2026-06-2=
    6 9.3 CVE-2026-56068 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56068 ] = Crocoblock. Jetimpex Inc.--JetSmartFilters Unauthenticated SQL Injection in=
    JetSmartFilters <=3D 3.8.3 versions. 2026-06-26 9.3 CVE-2026-56067 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-56067 ] CusRev--Customer Reviews for=
    WooCommerce Unauthenticated Cross Site Scripting (XSS) in Customer Reviews=
    for WooCommerce <=3D 5.110.1 versions. 2026-06-26 7.1 CVE-2026-56043 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-56043 ] Daan.dev--OMGF Pro Unrestr= icted Upload of File with Dangerous Type vulnerability in Daan.Dev OMGF Pro=
    allows Using Malicious Files. This issue affects OMGF Pro: from n/a throug=
    h 5.2.6. 2026-06-25 10 CVE-2026-57700 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-57700 ] Daktronics--VFC-DMP-5000 Various versions of Daktronics Co= ntroller Firmware could allow authenticated and unauthenticated remote user=
    s to escape the intended directory and enumerate arbitrary file system path=
    s. 2026-06-26 9.8 CVE-2026-28701 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-28701 ] Daktronics--VFC-DMP-5000 The DMP-5000 devices are shipped with =
    a default administrative web account with weak authentication controls, whi=
    ch are not required to be changed during initial configuration or operation=
    . Using these accounts provides full system access. 2026-06-26 8.1 CVE-2026= -31928 [ https://www.cve.org/CVERecord?id=3DCVE-2026-31928 ] Daktronics--VF= C-DMP-5000 The DMP-5000 file service exposes authenticated arbitrary file u= pload functionality. There are exposed endpoints which allows authenticated=
    users to upload files of any type without validation. No file extension fi= ltering or content inspection is enforced which allows executable binaries = and scripts to be accepted and written directly to the server. 2026-06-26 7=
    .1 CVE-2026-33560 [ https://www.cve.org/CVERecord?id=3DCVE-2026-33560 ] dan= ny-avila--LibreChat LibreChat is an enhanced ChatGPT clone that supports mu= ltiple AI providers. Prior to 0.8.5, LibreChat's MCP OAuth implementation d= oes not validate that the resource parameter from OAuth Protected Resource = metadata (RFC 9728) matches the configured MCP server URL, allowing a malic= ious MCP server to steal access tokens intended for a legitimate server. Th=
    is vulnerability is fixed in 0.8.5. 2026-06-25 8 CVE-2026-54030 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-54030 ] danny-avila--LibreChat LibreChat=
    is an enhanced ChatGPT clone that supports multiple AI providers. Prior to=
    0.8.4-rc1, LibreChat allows users to configure custom OpenAI-compatible AP=
    I endpoints by setting a baseURL. This URL is used to construct HTTP reques=
    ts without any SSRF validation - no private IP check, no scheme restriction=
    , no DNS pinning. An authenticated user can set baseURL to internal network=
    addresses. This vulnerability is fixed in 0.8.4-rc1. 2026-06-25 7.7 CVE-20= 26-54033 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54033 ] danpros--htm=
    ly HTMLy CMS through 3.1.1 contains a path traversal vulnerability that all= ows low-privileged authenticated attackers to relocate arbitrary files by s= upplying directory traversal sequences in the oldfile parameter at the admi=
    n autosave endpoint. Attackers can pass unsanitized traversal sequences dir= ectly to file_exists() and rename() functions in admin.php without canonica= lization or directory boundary enforcement to cause unintended relocation o=
    f any file writable by the web server process to an attacker-specified draf=
    t location. 2026-06-25 8.1 CVE-2026-45233 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-45233 ] daytonaio--daytona Daytona is a secure and elastic inf= rastructure runtime for AI-generated code execution and agent workflows. Pr= ior to 0.184.0, organization invitations could be accepted (and declined) b=
    y a user whose email matched the invitation but had not been verified. Dayt= ona authenticates users via OIDC and matches an invitation's target email a= gainst the email in the caller's token, but the invitation accept and decli=
    ne paths did not require that email to be verified, unlike organization cre= ation, which already enforced verification. On identity providers that allo=
    w self-service signup and issue a session before the email is verified, an = actor could register an address matching a pending invitation, leave it unv= erified, and accept the invitation, joining the target organization with th=
    e role the invitation carried (up to Owner). This vulnerability is fixed in=
    0.184.0. 2026-06-23 8.4 CVE-2026-54320 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54320 ] daytonaio--daytona Daytona is a secure and elastic infr= astructure runtime for AI-generated code execution and agent workflows. Fro=
    m 0.101.0 until 0.184.0, sandbox previews that were switched from public to=
    private could remain reachable without authentication for a short period a= fter the change, due to a cached visibility state that was not invalidated = when the sandbox's visibility changed. This vulnerability is fixed in 0.184= .0. 2026-06-23 7 CVE-2026-54321 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-54321 ] daytonaio--daytona Daytona is a secure and elastic infrastructur=
    e runtime for AI-generated code execution and agent workflows. Prior to 0.1= 85.0, Daytona's organization role update and delete endpoints authorized th=
    e caller as an owner of the organization named in the request path, but res= olved and mutated the target role by its identifier alone, without verifyin=
    g the role belonged to that organization. An authenticated user who owns an=
    y organization (organizations are self-service) could therefore modify the = permissions of, or delete, a role belonging to a different organization, gi= ven that role's identifier. This vulnerability is fixed in 0.185.0. 2026-06= -23 7.7 CVE-2026-54322 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54322 =
    ] Dell--Container Storage Modules Dell Dell Container Storage Modules, vers= ion(s) csi-powerstore v2.16.0, csi-unity v2.16.0, csi-powerflex v2.16.0, cs= i-powermax v2.16.0, contain(s) an Improper Neutralization of Special Elemen=
    ts used in an OS Command ('OS Command Injection') vulnerability. A high pri= vileged attacker with remote access could potentially exploit this vulnerab= ility, leading to Command execution. 2026-06-26 8 CVE-2026-40711 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-40711 ] Dell--Display and Peripheral Ma= nager Dell Display and Peripheral Manager (DDPM Windows), versions prior to=
    2.3, contain an Improper Access Control vulnerability. A low-privileged at= tacker with local access could potentially exploit this vulnerability, lead= ing to Code execution. 2026-06-25 7.8 CVE-2026-46733 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-46733 ] Dell--Display and Peripheral Manager Dell D= isplay and Peripheral Manager (DDPM Mac), versions prior to 2.3, contain an=
    Improper Certificate Validation vulnerability. A low-privileged attacker w= ith local access could potentially exploit this vulnerability, leading to P= rotection mechanism bypass. 2026-06-25 7.3 CVE-2026-46734 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-46734 ] Dell--Display and Peripheral Manager D= ell Display and Peripheral Manager (DDPM Mac), versions prior to 2.3, conta=
    in an Improper Neutralization of Special Elements used in an OS Command ('O=
    S Command Injection') vulnerability. A low-privileged attacker with local a= ccess could potentially exploit this vulnerability, leading to Command exec= ution. 2026-06-25 7.8 CVE-2026-46735 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-46735 ] Dell--Wyse Management Suite Dell Wyse Management Suite, ver= sions prior to WMS 5.5 HF1, contain an Acceptance of Extraneous Untrusted D= ata With Trusted Data vulnerability. A low-privileged attacker with remote = access could potentially exploit this vulnerability, leading to Remote Code=
    Execution. 2026-06-25 9.8 CVE-2026-41120 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-41120 ] Dell--Wyse Management Suite Dell Wyse Management Suite=
    , versions prior to WMS 5.5 HF1, contain an Improper Limitation of a Pathna=
    me to a Restricted Directory ('Path Traversal') vulnerability. A high privi= leged attacker with remote access could potentially exploit this vulnerabil= ity, leading to Remote Code Execution. 2026-06-25 7.2 CVE-2026-49506 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-49506 ] Dell--Wyse Management Suite=
    (WMS) Dell Wyse Management Suite (WMS), versions prior to WMS 2605, contai=
    n an Improper Neutralization of Special Elements used in an SQL Command ('S=
    QL Injection') vulnerability. A low-privileged attacker with remote access = could potentially exploit this vulnerability, leading to Unauthorized acces=
    s. 2026-06-22 8.1 CVE-2026-44271 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-44271 ] Dell--Wyse Management Suite (WMS) Dell Wyse Management Suite (W= MS), versions prior to WMS 2605, contain an Improper Neutralization of Spec= ial Elements used in an SQL Command ('SQL Injection') vulnerability. A low-= privileged attacker with remote access could potentially exploit this vulne= rability, leading to Unauthorized access. 2026-06-22 8.8 CVE-2026-44272 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-44272 ] Dell--Wyse Management Su= ite (WMS) Dell Wyse Management Suite (WMS), versions prior to WMS 2605, con= tain an Improper Link Resolution Before File Access vulnerability. A low-pr= ivileged attacker with local access could potentially exploit this vulnerab= ility, leading to Unauthorized access. 2026-06-22 7.8 CVE-2026-44274 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-44274 ] denoland--deno Deno is a Ja= vaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.10, Deno's node= :child_process implementation provided an escapeShellArg() helper used when=
    callers passed shell: true to spawn / spawnSync / exec and friends. On Win= dows, the helper failed to quote arguments that contained cmd.exe metachara= cters and did not neutralize % (which cmd.exe expands even inside double-qu= oted strings). An attacker who controlled any portion of an argument passed=
    to such a call could inject arbitrary additional commands into the spawned=
    cmd.exe invocation. This vulnerability is fixed in 2.7.10. 2026-06-23 8.1 = CVE-2026-49402 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49402 ] denola= nd--deno Deno is a JavaScript, TypeScript, and WebAssembly runtime. From 2.= 0.0 until 2.7.8, a flaw in Deno's Node.js tls compatibility layer could cau=
    se a TLS client to transmit application data in plaintext after a connectio=
    n retry. When `autoSelectFamily was enabled and the first address-family at= tempt failed, the socket reinitialization path reused a stale TLS upgrade h= ook that was bound to the original, failed handle. As a result, the replace= ment TCP connection was never upgraded to TLS, and any data the application=
    wrote before the secureConnect event travelled over the network unencrypte=
    d. A network attacker positioned to cause the initial connection attempt to=
    fail (for example, by dropping IPv6 traffic on a dual-stack host) could de= terministically trigger the fallback path and observe or tamper with traffi=
    c that the application believed was TLS-protected. This vulnerability is fi= xed in 2.7.8. 2026-06-23 7.4 CVE-2026-44726 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-44726 ] denoland--deno Deno is a JavaScript, TypeScript, and=
    WebAssembly runtime. Prior to 2.7.14, Deno's permission system enforces fi= lesystem and execution restrictions by comparing the requested path against=
    the path supplied to --deny-read, --deny-write, --deny-run, or --deny-ffi.=
    On macOS, that comparison was done at the raw-byte level while the APFS fi= lesystem treats different Unicode spellings of the same name as the same fi= le. That means a program could reach a denied path by spelling it different=
    ly than the deny rule. This vulnerability is fixed in 2.7.14. 2026-06-23 7.=
    3 CVE-2026-49401 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49401 ] deno= land--deno Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior=
    to 2.8.1, node:crypto.checkPrime(candidate[, options][, callback]) and cry= pto.checkPrimeSync(candidate[, options]) ran no Miller-Rabin rounds at all = when the caller left options.checks at its default of 0. In that mode, the = only test applied to the candidate was trial division by the primes up to 1= 7,863. Any composite whose smallest prime factor exceeds that bound - for e= xample the product of two primes just above it, such as 17,881 =C3=83=E2=80= =94 17,891 - was reported as true ("probably prime"). The same divergence a= ffected the lower-level op_node_check_prime / op_node_check_prime_bytes pat=
    hs that the polyfill calls into. This vulnerability is fixed in 2.8.1. 2026= -06-23 7.4 CVE-2026-49440 [ https://www.cve.org/CVERecord?id=3DCVE-2026-494=
    40 ] Design--Stylish Cost Calculator Unauthenticated Broken Access Control =
    in Stylish Cost Calculator <=3D 8.3.9 versions. 2026-06-26 7.5 CVE-2026-548=
    47 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54847 ] Dev Kabir--Enable = CORS Unauthenticated Backdoor in Enable CORS <=3D 2.0.3 versions. 2026-06-2=
    6 7.4 CVE-2026-54833 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54833 ] = dFactory--Responsive Lightbox Unauthenticated Cross Site Scripting (XSS) in=
    Responsive Lightbox <=3D 2.7.6 versions. 2026-06-26 7.1 CVE-2026-56041 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-56041 ] Digiwin--EasyFlow .NET E= asyFlow .NET developed by Digiwin has a Session Fixation vulnerability. If = unauthenticated remote attackers replace a specific session ID for a user, = they can gain the user's privilege once the user logs in. 2026-06-22 7.5 CV= E-2026-12581 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12581 ] docling-= project--docling Docling simplifies document processing by parsing diverse = formats and providing integrations with the generative AI ecosystem. FIn ve= rsions >=3D 2.82.0, < 2.91.0, if the HTML backend was explicitly configured=
    for rendering (rendering option by default deactivated), then the Playwrig= ht-based rendering feature could allow JavaScript execution and unrestricte=
    d network access when processing untrusted HTML documents. An attacker coul=
    d craft malicious HTML that executes arbitrary JavaScript in the rendering = context or makes unauthorized network requests to internal services, potent= ially leading to SSRF attacks, data exfiltration, or remote code execution =
    in the rendering environment. This vulnerability is fixed in 2.91.0. 2026-0= 6-24 8.2 CVE-2026-44016 [ https://www.cve.org/CVERecord?id=3DCVE-2026-44016=
    ] docling-project--docling Docling simplifies document processing by parsi=
    ng diverse formats and providing integrations with the generative AI ecosys= tem. Prior to 2.91.0, the EasyOCR model download functionality extracted ZI=
    P archives without validating member paths, enabling Zip Slip attacks. If a=
    n attacker could compromise the model download source (via supply chain att= ack, DNS spoofing, or MITM), they could write arbitrary files to any locati=
    on writable by the process, potentially achieving remote code execution by = overwriting Python files or system binaries, persistent backdoors by modify= ing startup scripts or SSH keys, and data corruption or system compromise. = This vulnerability is fixed in 2.91.0. 2026-06-24 7.5 CVE-2026-44017 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-44017 ] docling-project--docling Do= cling simplifies document processing by parsing diverse formats and providi=
    ng integrations with the generative AI ecosystem. From 2.13.0 until 2.74.0,=
    the USPTO patent XML parser used the standard xml.sax.parseString() withou=
    t protection against XML External Entity (XXE) attacks. An attacker could c= raft malicious USPTO patent XML files with external entity references that = could read arbitrary files from the server filesystem, perform Server-Side = Request Forgery (SSRF) attacks, or cause denial of service through entity e= xpansion (Billion Laughs attack). The vulnerability affects three USPTO pat= ent format parsers: ICE (v4.x), Grant v2.5, and Application v1.x. This vuln= erability is fixed in 2.74.0. 2026-06-24 7.5 CVE-2026-44020 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-44020 ] docling-project--docling Docling sim= plifies document processing by parsing diverse formats and providing integr= ations with the generative AI ecosystem. Prior to 2.94.0, the HTML backend = has unsafe URI and path handling. This vulnerability is fixed in 2.94.0. 20= 26-06-26 7.1 CVE-2026-47214 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 7214 ] Dokan Multivendor Plugin--Dokan Pro Unauthenticated Privilege Escala= tion in Dokan Pro <=3D 5.0.4 versions. 2026-06-26 9.8 CVE-2026-56033 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-56033 ] dokku--dokku Dokku is a doc= ker-powered PaaS. Prior to 0.38.2, the git:from-archive and certs:add comma= nds extract user-supplied tar/zip archives into temporary directories witho=
    ut sanitizing member paths or preventing symlink traversal. GNU tar creates=
    symlinks during extraction and follows them for subsequent entries, allowi=
    ng an attacker to write arbitrary files anywhere writable by the dokku user=
    - including overwriting ~/.ssh/authorized_keys to gain unrestricted shell = access. This vulnerability is fixed in 0.38.2. 2026-06-26 9 CVE-2026-45405 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-45405 ] dokku--dokku Dokku is=
    a docker-powered PaaS. Prior to 0.38.2, the openresty-vhosts plugin copies=
    files from an app's openresty/http-includes/ git repository directory to t=
    he host and then interpolates their filenames, unescaped, into a single-quo= ted shell string that is later parsed by eval. A filename containing a sing=
    le quote breaks the quoting and allows command substitution to execute arbi= trary commands on the host as the dokku user during the app's next deploy. = This vulnerability is fixed in 0.38.2. 2026-06-26 9 CVE-2026-45406 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-45406 ] dokku--dokku Dokku is a docke= r-powered PaaS. Prior to 0.38.2, the app name validation regex (^[a-z0-9][^= /:_A-Z]*$) permits shell metacharacters. When an authenticated user pushes =
    to a git remote with a crafted app name, the name is embedded unquoted into=
    a bash pre-receive hook script via an unquoted heredoc (<<EOF instead of <= <'EOF') in fn-git-create-hook() at plugins/git/internal-functions:378. On g=
    it push, bash interprets the semicolon as a command separator, executing ar= bitrary commands as the dokku user. This vulnerability is fixed in 0.38.2. = 2026-06-26 9 CVE-2026-45408 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 5408 ] dokku--dokku Dokku is a docker-powered PaaS. Prior to 0.38.7, the cr=
    on plugin utilizes commands in the app.json file to manage system cron runn= ing as the Dokku user. An app.json cron command utilizing special shell cha= racters - including, but not limited to, > or ; - can break out of the Dock=
    er container and execute commands on the host as the Dokku user. This vulne= rability is fixed in 0.38.7. 2026-06-26 9 CVE-2026-54636 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-54636 ] dragonflydb--dragonfly Dragonfly is an = in-memory data store built for modern application workloads. Prior to 1.39.=
    0, a crafted RESTORE payload triggers an out-of-bounds read in DragonflyDB'=
    s listpack collection loaders, crashing the entire server process (SIGSEGV)=
    . Because DragonflyDB requires no authentication by default and RESTORE is =
    a normal keyspace command, an unauthenticated remote attacker can crash the=
    server with a single ~24-byte command - a remote, repeatable denial of ser= vice. This vulnerability is fixed in 1.39.0. 2026-06-26 7.5 CVE-2026-54341 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-54341 ] Eagle-Themes--Eagle B= ooking Unauthenticated Cross Site Request Forgery (CSRF) in Eagle Booking <= =3D 1.3.4.3 versions. 2026-06-26 8.8 CVE-2025-68052 [ https://www.cve.org/C= VERecord?id=3DCVE-2025-68052 ] earendil-works--pi Pi is a minimal terminal = coding harness. From 0.74.0 until 0.78.1, Pi versions with temporary npm or=
    git extension package installs used predictable paths under the operating = system temporary directory. On Linux-based multi-user systems, a local atta= cker who can write to the shared temporary directory could prepare the expe= cted package location before another user runs pi with a temporary extensio=
    n package source. Pi could then load attacker-controlled extension code in = the victim user's process. This vulnerability is fixed in 0.78.1. 2026-06-2=
    3 7.3 CVE-2026-54328 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54328 ] = envoyproxy--envoy Envoy is an open source edge and service proxy designed f=
    or cloud-native applications. From 1.37.0 until 1.37.5 and 1.38.3, when the=
    %REQUESTED_SERVER_NAME(X:Y)% is used in log format and host related option=
    s is specified, like HOST_FIRST, SNI_FIRST, it's possible to crash Envoy wh=
    en the specified host header is missing in the request headers. This vulner= ability is fixed in 1.37.5 and 1.38.3. 2026-06-26 7.5 CVE-2026-47220 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-47220 ] envoyproxy--envoy Envoy is =
    an open source edge and service proxy designed for cloud-native application=
    s. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, destructor of JSON Object = results in stack overflow when deeply O(100K) nested objects are present. T= his vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, and 1.38.1. 2026-06-=
    26 7.5 CVE-2026-48042 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48042 ]=
    envoyproxy--envoy Envoy is an open source edge and service proxy designed = for cloud-native applications. From 1.23.0 until 1.35.11, 1.36.7, 1.37.3, a=
    nd 1.38.1, a vulnerability has been identified in Envoy's zstd decompressor=
    implementation (ZstdDecompressorImpl). When zstd decompression is enabled,=
    processing a specially crafted, highly compressed zstd payload can lead to=
    massive memory allocation. An attacker can exploit this to cause severe me= mory exhaustion, potentially resulting in an Out-Of-Memory (OOM) kill and D= enial of Service (DoS) for the Envoy proxy. This vulnerability is fixed in = 1.35.11, 1.36.7, 1.37.3, and 1.38.1. 2026-06-26 7.5 CVE-2026-48044 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-48044 ] envoyproxy--envoy Envoy is an=
    open source edge and service proxy designed for cloud-native applications.=
    Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, Envoy can translate a downst= ream HTTP/3 request that is complete at the transport layer (HEADERS with F=
    IN / headers-only close) but still carries a nonzero Content-Length into a = complete upstream HTTP/1 request with unresolved body debt. In an HTTP/1 up= stream deployment where the origin replies before reading the declared body=
    and keeps the connection reusable, the beginning of the next Envoy-generat=
    ed upstream request can be consumed as the first request's body. The remain= ing bytes are then parsed by the origin as a new HTTP/1 request. This was r= eproduced as a route-bypass/desync: direct /pwn was denied by Envoy, but th=
    e second downstream H3 stream received the response for backend-parsed GET = /pwn HTTP/1.1. This vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, and = 1.38.1. 2026-06-26 7.5 CVE-2026-48743 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-48743 ] Etoile Web Design Incorporated--Five Star Restaurant Reser= vations Unauthenticated Broken Access Control in Five Star Restaurant Reser= vations <=3D 2.7.19 versions. 2026-06-25 7.5 CVE-2026-54830 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-54830 ] EventPrime--EventPrime Subscriber PH=
    P Object Injection in EventPrime <=3D 4.3.4.1 versions. 2026-06-25 8.8 CVE-= 2026-56053 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56053 ] Everthemes= s--Goya Core Contributor Local File Inclusion in Goya Core < 1.0.9.4 versio= ns. 2026-06-26 7.5 CVE-2025-68064 [ https://www.cve.org/CVERecord?id=3DCVE-= 2025-68064 ] EVoke--EVoke CSMS WebSocket endpoints lack proper authenticati=
    on mechanisms, enabling attackers to impersonate charging stations. As a re= sult, attackers can exploit this weakness to gain unauthorized access to se= nsitive data or perform unauthorized actions. Given that no authentication =
    is required, this can lead to privilege escalation and potentially compromi=
    se the security of the entire system. 2026-06-25 9.4 CVE-2026-40702 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-40702 ] EVoke--EVoke CSMS The WebSoc= ket Application Programming Interface lacks restrictions on the number of a= uthentication requests. This absence of rate limiting may allow an attacker=
    to conduct denial-of-service attacks or brute-force attacks to gain unauth= orized access. 2026-06-25 7.5 CVE-2026-50176 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-50176 ] EVoke--EVoke CSMS The WebSocket backend uses chargi=
    ng station identifiers to uniquely associate sessions but allows multiple e= ndpoints to connect using the same session identifier. This implementation = results in predictable session identifiers. This vulnerability may allow un= authorized users to authenticate as other users or enable a malicious actor=
    to cause a denial-of-service condition by overwhelming the backend with va= lid session requests. 2026-06-25 7.3 CVE-2026-54479 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-54479 ] expr-eval--expr-eval All versions of the pac= kage expr-eval are vulnerable to Code Execution via the toJSFunction() API.=
    An attacker can execute arbitrary JavaScript by supplying crafted expressi= ons that are compiled into native code using new Function(). Because user-c= ontrolled expressions are transformed directly into executable JavaScript, = attackers can escape the intended expression sandbox and run arbitrary code=
    within the application's context. 2026-06-23 9.8 CVE-2026-12866 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-12866 ] FasterXML--jackson-databind jac= kson-databind contains the general-purpose data-binding functionality and t= ree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and=
    3.1.4, jackson-databind's PolymorphicTypeValidator (PTV) is the primary sa= fety mechanism guarding polymorphic deserialization. When polymorphic typin=
    g is enabled and a type identifier contains generic parameters (i.e. the ty=
    pe ID string contains <), DatabindContext._resolveAndValidateGeneric() vali= dates only the raw container class name (the substring before <) against th=
    e configured PTV. If the container type is approved, the method parses the = full canonical type string via TypeFactory.constructFromCanonical() and ret= urns the fully parameterized type without ever validating the nested type a= rguments against the PTV. The nested type arguments are then resolved, inst= antiated, and populated as beans during deserialization. An attacker who co= ntrols the type ID can therefore place a denied class as a generic type par= ameter of an allowed container - for example java.util.ArrayList<com.evil.G= adget> when only java.util.ArrayList is allow-listed. The container passes = the PTV check; com.evil.Gadget is loaded via Class.forName(name, true, load= er), instantiated, and its properties are set from attacker-controlled JSON=
    . This completely bypasses an explicitly configured PTV allow-list. This vu= lnerability is fixed in 2.18.8, 2.21.4, and 3.1.4. 2026-06-23 8.1 CVE-2026-= 54512 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54512 ] FasterXML--jack= son-databind jackson-databind contains the general-purpose data-binding fun= ctionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.1= 8.8, 2.21.4, and 3.1.4, BasicPolymorphicTypeValidator.Builder.allowIfSubTyp= eIsArray() allowlists any array type based only on clazz.isArray(), without=
    validating the array's component (element) type against the configured all= owlist. A PTV built with allowIfSubTypeIsArray() plus an explicit concrete-= type allowlist therefore still permits EvilType[] even though EvilType is n=
    ot allowlisted. When Jackson deserializes the elements and no per-element t= ype IDs are present, it instantiates the component type directly with no fu= rther PTV check, bypassing the allowlist. This vulnerability is fixed in 2.= 18.8, 2.21.4, and 3.1.4. 2026-06-23 8.1 CVE-2026-54513 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-54513 ] feast-dev--feast Feast before 0.63.0 cont= ains an unsafe deserialization vulnerability that allows unauthenticated or=
    unauthorized attackers to achieve remote code execution by sending a craft=
    ed gRPC request to the registry server. The user_defined_function.body fiel=
    d of an OnDemandFeatureView spec is decoded from base64 and passed to dill.= loads() before any authorization check is performed, enabling attackers to = embed a malicious serialized Python object with an arbitrary __reduce__ met= hod to execute OS commands as the feast service account. 2026-06-24 9.8 CVE= -2026-56121 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56121 ] FFmpeg--F= Fmpeg FFmpeg's RASC video decoder (decode_dlta in libavcodec/rasc.c) perfor=
    ms 32-bit reads and writes at the row cursor before the NEXT_LINE row-bound= ary check and validates the DLTA region in pixel rather than byte units, so=
    a DLTA run on a PAL8 frame can access several bytes past the row allocatio=
    n. A crafted media stream using the RASC FourCC, decoded by libavcodec, tri= ggers a bitstream-controlled out-of-bounds heap write and adjacent out-of-b= ounds read, leading to memory corruption. 2026-06-28 8.6 CVE-2026-58049 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-58049 ] filamentphp--filament Fi= lament is a collection of full-stack components for accelerated Laravel dev= elopment. From 4.0.0 until 4.11.5 and 5.6.5, a flaw in the handling of reco= very codes for app-based multi-factor authentication allows the same recove=
    ry code to be reused via concurrent submission. This issue does not affect = email-based MFA. It also only applies when recovery codes are enabled. If a=
    n attacker gains access to both the user's password and their recovery code=
    s, they get two authenticated sessions per recovery code burned instead of = one, or more if they batch the parallel submissions wider, materially exten= ding the attacker's window of access compared to what the single-use guaran= tee implies. This vulnerability is fixed in 4.11.5 and 5.6.5. 2026-06-22 7.=
    4 CVE-2026-48505 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48505 ] fila= mentphp--filament Filament is a collection of full-stack components for acc= elerated Laravel development. From 3.0.0 until 3.3.53, a disabled RichEdito=
    r field rendered its raw state without sanitizing HTML. Where the data stor=
    ed in this field's state isn't sanitized already when the form state was fi= lled, an attacker could plant malicious HTML or JavaScript and achieve XSS = that executes for users who view the form. This vulnerability is fixed in 3= .3.53. 2026-06-22 7.6 CVE-2026-55409 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-55409 ] filebrowser--filebrowser File Browser is a file managing in= terface for uploading, deleting, previewing, renaming, and editing files wi= thin a specified directory. Starting with 2.0.0-rc.1, when FileBrowser is c= onfigured with proxy authentication (auth.method=3Dproxy), any unauthentica= ted attacker who can reach the server directly can impersonate any user - i= ncluding admin - by sending a single forged HTTP header. No credentials are=
    required. Additionally, specifying a non-existent username causes the serv=
    er to automatically create a new user account, providing an account creatio=
    n primitive with no authorization. This is an already known issue that has = been documented in the documentation for several years, but has not been do= cumented as a vulnerability before. 2026-06-25 9.1 CVE-2026-54089 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-54089 ] filebrowser--filebrowser File = Browser is a file managing interface for uploading, deleting, previewing, r= enaming, and editing files within a specified directory. Prior to 2.63.7, `= POST /api/share/<path>` accepts an authenticated request for an arbitrary p= ath and stores a public share record without checking whether the target fi=
    le currently exists. Later, when a file is created at that same path, the p= reviously created public share immediately becomes valid and exposes the ne=
    w file through `GET /api/public/dl/<hash>`. This vulnerability is fixed in = 2.63.7. 2026-06-25 8.4 CVE-2026-54096 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-54096 ] filebrowser--filebrowser File Browser is a file managing i= nterface for uploading, deleting, previewing, renaming, and editing files w= ithin a specified directory. Prior to 2.63.16, a scoped, non-admin File Bro= wser user holding only the Create permission can delete arbitrary files out= side their scope (other tenants' data, and the application's own database) = via the upload failure-cleanup path. ScopedFs.RemoveAll is the one derefere= ncing operation that skips the symlink guard every other method enforces. T=
    he direct-upload handler runs RemoveAll on the user-controlled path during = failed-upload cleanup, gated only by Perm.Create. If an escaping directory = symlink already exists inside the user's scope, an authenticated create-onl=
    y user can delete an out-of-scope target, bypassing both the ScopedFs bound= ary and the Perm.Delete gate. This vulnerability is fixed in 2.63.16. 2026-= 06-25 8.2 CVE-2026-55667 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5566=
    7 ] filebrowser--filebrowser File Browser is a file managing interface for = uploading, deleting, previewing, renaming, and editing files within a speci= fied directory. Prior to 2.63.6, File Browser's public share handlers rebas=
    e the share owner's filesystem root to the shared directory and then evalua=
    te descendant paths against the owner's global and per-user rules using the=
    rebased relative path instead of the original path relative to the owner's=
    scope. As a result, an attacker who knows a public directory share URL can=
    access files and subdirectories that the owner explicitly blocked with rul= es, as long as those blocked paths are located underneath the shared direct= ory. In the simplest case this is an unauthenticated information disclosure=
    through `GET /api/public/share/*` and `GET /api/public/dl/*`. This vulnera= bility is fixed in 2.63.6. 2026-06-25 7.5 CVE-2026-54091 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-54091 ] filebrowser--filebrowser File Browser i=
    s a file managing interface for uploading, deleting, previewing, renaming, = and editing files within a specified directory. Prior to 2.63.14, it does n=
    ot stop the HTTP file handlers from following symbolic links before they op= en, serve, write, share, or list a file. As a result, a scoped user - and i=
    n some cases an unauthenticated public-share recipient - can cross the inte= nded scope boundary by following a symlink whose path is lexically inside t= heir scope but whose target is outside it. This vulnerability is fixed in 2= .63.14. 2026-06-25 7.5 CVE-2026-54094 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-54094 ] FlatPress--FlatPress FlatPress contains a stored cross-sit=
    e scripting vulnerability in comment and contact forms where name, URL, and=
    email fields are rendered without proper output encoding in Smarty templat= es. Attackers can inject arbitrary HTML and JavaScript through these fields=
    to execute malicious scripts in browsers of viewers including administrato= rs, or bypass URL scheme validation to inject javascript: or data: URIs. 20= 26-06-23 8.2 CVE-2026-56785 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 6785 ] Flowise--Flowise Flowise contains a path traversal vulnerability in = the /api/v1/document-store/loader/process endpoint that allows unauthentica= ted attackers to write arbitrary files to the filesystem. Attackers can exp= loit unsanitized fileName parameters with ../ sequences to overwrite critic=
    al files like package.json and achieve remote code execution when the appli= cation restarts. 2026-06-25 10 CVE-2025-71338 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2025-71338 ] Flowise--Flowise Flowise contains an authenticatio=
    n bypass vulnerability in the unprotected /api/v1/account/register endpoint=
    that allows unauthenticated attackers to create user accounts. Remote atta= ckers can exploit this endpoint to register arbitrary accounts and authenti= cate to the system, gaining full API access without credentials. 2026-06-25=
    9.1 CVE-2025-71327 [ https://www.cve.org/CVERecord?id=3DCVE-2025-71327 ] F= lowise--Flowise Flowise before 3.0.6 (affected versions 2.2.8 and earlier) = contains an arbitrary file access vulnerability due to missing validation t= hat the chatflowId and chatId parameters are UUIDs or numbers in file handl= ing operations. By supplying a path-traversal value (e.g., '../../../../../= tmp') as the chatflow id, an unauthenticated attacker can use the /api/v1/c= hatflows endpoint (via addBase64FilesToStorage) to write arbitrary files, a=
    nd the /api/v1/get-upload-file and /api/v1/openai-assistants-file/download = endpoints (via streamStorageFile) to read arbitrary files. Arbitrary file w= rite may lead to remote code execution. 2026-06-25 9.8 CVE-2025-71334 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2025-71334 ] Flowise--Flowise Flowise b= efore 3.0.6 (affected versions 2.2.7-patch.1 and earlier) contains an unsan= dboxed remote code execution vulnerability in the Custom MCP feature, which=
    is designed to execute OS commands such as launching local MCP servers. Be= cause Flowise's authentication and authorization model is minimal and lacks=
    role-based access control, and the default installation runs without authe= ntication unless FLOWISE_USERNAME and FLOWISE_PASSWORD are set, an attacker=
    can send a crafted JSON payload with the header 'x-request-from: internal'=
    to the /api/v1/node-load-method/customMCP endpoint to execute arbitrary OS=
    commands, resulting in complete compromise of the platform container or se= rver. 2026-06-25 9.8 CVE-2025-71336 [ https://www.cve.org/CVERecord?id=3DCV= E-2025-71336 ] Flowise--Flowise Flowise before 3.1.2 contains multiple OS c= ommand injection vulnerabilities in the Custom MCP Server feature due to in= complete command-flag validation and a regex bypass in local file access re= strictions. An attacker with a Flowise account of any role, or API access w= ith view/update permissions for chatflows, can configure a malicious MCP se= rver to bypass the validateCommandFlags blocklist (for example, 'docker bui= ld' is not blocked, and 'npx --yes' is not blocked while only '-y' is) and = the validateArgsForLocalFileAccess checks, resulting in execution of arbitr= ary commands on the Flowise host. 2026-06-23 9.9 CVE-2026-56274 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-56274 ] Flowise--Flowise Flowise before = 3.0.10 contains an unverified password change vulnerability. An authenticat=
    ed user can change their account password through the account settings (Sec= urity) section without supplying the current password or any additional ver= ification, as the application does not enforce a current-password check on = the credential change. This can lead to full account takeover, particularly=
    if an attacker can hijack or coerce an authenticated session. 2026-06-25 8=
    .3 CVE-2025-71328 [ https://www.cve.org/CVERecord?id=3DCVE-2025-71328 ] Flo= wise--Flowise Flowise before 3.0.10 (affected versions 3.0.7 and earlier) f= ails to invalidate existing sessions and session tokens after a user change=
    s their password. An attacker who already holds an active session, for exam= ple via a stolen session token or a device left logged in, remains authenti= cated as the legitimate user even after the user rotates their credentials,=
    undermining the security purpose of the password change. 2026-06-25 8.1 CV= E-2025-71335 [ https://www.cve.org/CVERecord?id=3DCVE-2025-71335 ] Flowise-= -Flowise Flowise before 3.0.10 (affected versions 3.0.7 and earlier) contai=
    ns an unverified email change vulnerability. An authenticated user can chan=
    ge the account email address, used as a login identifier and password-recov= ery channel, via the account profile endpoint without confirming the change=
    to the original email address or re-entering the current password. By chan= ging the recovery email, an attacker can take over the account and abuse pa= ssword reset mechanisms. 2026-06-23 8.3 CVE-2025-71337 [ https://www.cve.or= g/CVERecord?id=3DCVE-2025-71337 ] Flowise--Flowise Flowise before 3.0.6 con= tains an arbitrary file read vulnerability in the chatId parameter of the /= api/v1/get-upload-file and /api/v1/openai-assistants-file/download endpoint=
    s. The chatId value is not validated and is passed to streamStorageFile(), = where a fallback file-lookup path constructed without the orgId is evaluate=
    d after the storage-directory containment check, allowing path traversal be= yond the intended storage directory. Unauthenticated attackers can read sen= sitive files such as /root/.flowise/database.sqlite, exposing all database = content in the default configuration. 2026-06-25 7.5 CVE-2025-71324 [ https= ://www.cve.org/CVERecord?id=3DCVE-2025-71324 ] Flowise--Flowise Flowise bef= ore 3.1.2 contains an information disclosure vulnerability in the /api/v1/c= hatflows/apikey/:apikey endpoint. When the keyonly query parameter is omitt=
    ed (the default), the endpoint returns not only the chatflows bound to the = supplied API key but also all chatflows across every workspace that have no=
    API key assigned, because the underlying query lacks any workspace filter.=
    An attacker with a valid API key for one workspace can therefore retrieve = the full ChatFlow configuration (including flowData with system prompts and=
    node configurations, chatbotConfig, apiConfig, and credential IDs) of unpr= otected chatflows belonging to other workspaces. 2026-06-22 7.7 CVE-2026-56= 268 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56268 ] Flowise--Flowise = Flowise before 3.1.0 (versions 3.0.13 and earlier) contains a missing authe= ntication vulnerability in the /api/v1/loginmethod endpoint that allows una= uthenticated users to retrieve an organization's complete SSO configuration=
    , including OAuth client secrets in cleartext, by providing an organization=
    Id parameter. Remote attackers can send a GET request to harvest sensitive = API credentials for Google, Microsoft/Azure, GitHub, and Auth0 integrations=
    . This affects FlowiseAI Cloud and self-hosted instances where the endpoint=
    is exposed. 2026-06-24 7.5 CVE-2026-56270 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-56270 ] fpuenteonline--Object Cache 4 everyone Unauthenticate=
    d Sensitive Data Exposure in Object Cache 4 everyone <=3D 2.3.2 versions. 2= 026-06-26 7.5 CVE-2026-54834 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 54834 ] Frisbii--Frisbii Pay Contributor Privilege Escalation in Frisbii Pa=
    y <=3D 1.8.2 versions. 2026-06-26 8.8 CVE-2026-56038 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-56038 ] FunnelKit--Funnel Builder by FunnelKit Impr= oper Neutralization of Special Elements used in an SQL Command ('SQL Inject= ion') vulnerability in FunnelKit Funnel Builder by FunnelKit allows Blind S=
    QL Injection. This issue affects Funnel Builder by FunnelKit: from n/a thro= ugh 3.15.0.5. 2026-06-24 7.6 CVE-2026-56052 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-56052 ] garybowers--bootimus Bootimus through 0.1.70 contain=
    s a broken access control vulnerability that allows authenticated low-privi= leged users to perform administrative actions by exploiting missing role en= forcement in the JWTMiddleware function in internal/auth/auth.go, which val= idates JWT tokens and account status but fails to inspect the is_admin flag=
    . Attackers can send requests to any endpoint under the /api/users path to = create new administrator accounts or reset administrator passwords, thereby=
    gaining full control of the server and the ability to modify boot menus an=
    d installation scripts served to PXE clients. 2026-06-23 8.8 CVE-2026-56115=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-56115 ] GeoVision Inc.--GV-I=
    /O Box 4E GV-I/O Box 4E is a smart embedded device with 4 input and 4 relay=
    s output that can be controlled over Ethernet and RS-485. DVRSearch is a se= rvice running by default on the IOBox listening for UDP messages on port 10= 001. Any user on the network can send messages to this service and interact=
    with it. Upon receiving a UDP message, the server reads at most 1460 bytes=
    into a local buffer and a pointer to the buffer is stored in a global vari= able: #### IP field stack overflow The following code is vulnerable to a st= ack overflow that is attacker-controlled: v3 =3D strlen(g_network_config->i= p_addr); memcpy(&reply_buf[36], g_network_config->ip_addr, v3); 2026-06-24 =
    10 CVE-2026-12485 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12485 ] Geo= Vision Inc.--GV-I/O Box 4E GV-I/O Box 4E is a smart embedded device with 4 = input and 4 relays output that can be controlled over Ethernet and RS-485. = DVRSearch is a service running by default on the IOBox listening for UDP me= ssages on port 10001. Any user on the network can send messages to this ser= vice and interact with it. Upon receiving a UDP message, the server reads a=
    t most 1460 bytes into a local buffer and a pointer to the buffer is stored=
    in a global variable: #### Net Mask field stack overflow The following cod=
    e is vulnerable to a stack overflow that is attacker-controlled: v6 =3D str= len(g_network_config->net_mask); memcpy(&reply_buf[184], g_network_config->= net_mask, v6); 2026-06-24 10 CVE-2026-12846 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-12846 ] GeoVision Inc.--GV-I/O Box 4E GV-I/O Box 4E is a sma=
    rt embedded device with 4 input and 4 relays output that can be controlled = over Ethernet and RS-485. DVRSearch is a service running by default on the = IOBox listening for UDP messages on port 10001. Any user on the network can=
    send messages to this service and interact with it. Upon receiving a UDP m= essage, the server reads at most 1460 bytes into a local buffer and a point=
    er to the buffer is stored in a global variable: #### Gateway field stack o= verflow The following code is vulnerable to a stack overflow that is attack= er-controlled: v7 =3D strlen(g_network_config->gateway); memcpy(&reply_buf[= 216], g_network_config->gateway, v7); 2026-06-24 10 CVE-2026-12847 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-12847 ] GeoVision Inc.--GV-I/O Box 4E=
    GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output = that can be controlled over Ethernet and RS-485. DVRSearch is a service run= ning by default on the IOBox listening for UDP messages on port 10001. Any = user on the network can send messages to this service and interact with it.=
    Upon receiving a UDP message, the server reads at most 1460 bytes into a l= ocal buffer and a pointer to the buffer is stored in a global variable: ###=
    # DNS field stack overflow The following code is vulnerable to a stack over= flow that is attacker-controlled: v8 =3D strlen(g_network_config->dns_addr)=
    ; memcpy(&reply_buf[248], g_network_config->dns_addr, v8); 2026-06-24 10 CV= E-2026-12848 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12848 ] GeoVisio=
    n Inc.--GV-I/O Box 4E Multiple OS command injection vulnerabilities exist i=
    n the libNetSetObj.so functionality of GeoVision GV-I/O Box 4E 2.09. A spec= ially crafted network packet can lead to command execution. An attacker can=
    send a network request to trigger this vulnerability. `libNetSetObj.so` is=
    an internal library used by various binaries on the device to configure th=
    e network stack (start and stop various services, configure IP, Netmask, ga= teway, dns, etc.) #### CNetSetObj::m_F_n_Set_IP_Addr command injection The = following function takes a string as an ip address, performs no sanitizatio=
    n and calls `system`. This is a classic command injection vulnerability. Th=
    e function is reachable from both the network-exposed `DVRSearch` service a=
    nd the `Network.cgi` endpoint. int __fastcall CNetSetObj::m_F_n_Set_IP_Addr= (const char **this, char *ip_addr) { bool v2; // zf char v4[72]; // [sp+0h]=
    [bp-48h] BYREF v2 =3D *this =3D=3D 0; if ( *this ) v2 =3D ip_addr =3D=3D 0=
    ; if ( v2 ) return 0; sprintf(v4, "/sbin/ifconfig %s %s", *this, ip_addr); =
    // attacker controlled ip address system(v4); return 1; } 2026-06-24 9.1 CV= E-2026-12486 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12486 ] GeoVisio=
    n Inc.--GV-I/O Box 4E Multiple OS command injection vulnerabilities exist i=
    n the libNetSetObj.so functionality of GeoVision GV-I/O Box 4E 2.09. A spec= ially crafted network packet can lead to command execution. An attacker can=
    send a network request to trigger this vulnerability. `libNetSetObj.so` is=
    an internal library used by various binaries on the device to configure th=
    e network stack (start and stop various services, configure IP, Netmask, ga= teway, dns, etc.) #### CNetSetObj::m_F_n_Set_Net_Mask command injection The=
    following function takes a string as a net mask address, performs no sanit= ization on it and calls `system`. This is a classic command injection vulne= rability. The function is reachable from both the network-exposed `DVRSearc=
    h` service and the `Network.cgi` endpoint. int __fastcall CNetSetObj::m_F_n= _Set_Net_Mask(const char **this, char *netmask_addr) { bool v2; // zf char = v4[72]; // [sp+0h] [bp-48h] BYREF v2 =3D *this =3D=3D 0; if ( *this ) v2 =
    =3D netmask_addr =3D=3D 0; if ( v2 ) return 0; sprintf(v4, "/sbin/ifconfig =
    %s netmask %s", *this, netmask_addr); // attacker controlled netmask_addr s= ystem(v4); return 1; } 2026-06-24 9.1 CVE-2026-12849 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-12849 ] GeoVision Inc.--GV-I/O Box 4E Multiple OS c= ommand injection vulnerabilities exist in the libNetSetObj.so functionality=
    of GeoVision GV-I/O Box 4E 2.09. A specially crafted network packet can le=
    ad to command execution. An attacker can send a network request to trigger = this vulnerability. `libNetSetObj.so` is an internal library used by variou=
    s binaries on the device to configure the network stack (start and stop var= ious services, configure IP, Netmask, gateway, dns, etc.) #### CNetSetObj::= m_F_n_Set_Gate_way command injection The following function takes a string =
    as a gatewy address, performs no sanitization on it and calls `system`. Thi=
    s is a classic command injection vulnerability. The function is reachable f= rom both the network-exposed `DVRSearch` service and the `Network.cgi` endp= oint. int __fastcall CNetSetObj::m_F_n_Set_Gate_way(const char **this, char=
    *gw, char *dev) { char s[324]; // [sp+4h] [bp-144h] BYREF if ( !dev && !*t= his || !gw ) return 0; system("/sbin/route del -net 224.0.0.0 netmask 224.0= .0.0"); system("/sbin/route del default "); if ( dev ) sprintf(s, "/sbin/ro= ute add default gw %s dev %s", gw, dev); //attacker controlled gw string el=
    se sprintf(s, "/sbin/route add default gw %s dev %s", gw, *this); //attacke=
    r controlled gw string system(s); sprintf(s, "/sbin/route add -net 224.0.0.=
    0 netmask 224.0.0.0 gw %s dev %s", gw, *this); //attacker controlled gw str= ing system(s); return 1; } 2026-06-24 9.1 CVE-2026-12850 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-12850 ] GeoVision Inc.--GV-I/O Box 4E Multiple =
    OS command injection vulnerabilities exist in the libNetSetObj.so functiona= lity of GeoVision GV-I/O Box 4E 2.09. A specially crafted network packet ca=
    n lead to command execution. An attacker can send a network request to trig= ger this vulnerability. `libNetSetObj.so` is an internal library used by va= rious binaries on the device to configure the network stack (start and stop=
    various services, configure IP, Netmask, gateway, dns, etc.) #### CNetSetO= bj::m_F_n_Set_DNS_Addr command injection The following function can take up=
    to two addresses, performs no sanitization and then calls `system`. This i=
    s a classic command injection vulnerability. The function is reachable from=
    both the network-exposed `DVRSearch` service and the `Network.cgi` endpoin=
    t. int __fastcall CNetSetObj::m_F_n_Set_DNS_Addr(CNetSetObj *this, char *dn= s1, char *dns2) { int result; // r0 char v5[80]; // [sp+0h] [bp-50h] BYREF =
    if ( !dns1 ) result =3D 0; if ( dns1 ) { sprintf(v5, "/bin/echo nameserver =
    %s > /etc/resolv.conf", dns1); // attacker controlled dns1 field system(v5)=
    ; if ( dns2 ) { sprintf(v5, "/bin/echo nameserver %s >> /etc/resolv.conf", = dns2); system(v5); } return 1; } return result; 2026-06-24 9.1 CVE-2026-128=
    51 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12851 ] GeoVision Inc.--GV= -LPCLPC2011/2211 An unauthenticated stack-based buffer overflow vulnerabili=
    ty exists in thttpd in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlie=
    r. The vulnerability is caused by insufficient bounds checking when process= ing web request parameters in a specific request path. A remote attacker ma=
    y exploit this vulnerability by sending a crafted HTTP request with overly = long input, resulting in memory corruption, denial of service, or potential=
    ly arbitrary code execution. 2026-06-26 9.8 CVE-2026-57878 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-57878 ] GeoVision Inc.--GV-LPCLPC2011/2211 An=
    unauthenticated stack-based buffer overflow vulnerability exists in ssvr i=
    n GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability =
    is caused by insufficient bounds checking when processing RTSP custom authe= ntication data. A remote attacker may exploit this vulnerability by sending=
    a crafted RTSP request, resulting in memory corruption, denial of service,=
    or potentially arbitrary code execution. 2026-06-26 9.8 CVE-2026-57879 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-57879 ] GeoVision Inc.--GV-LPCLP= C2011/2211 An unauthenticated stack-based buffer overflow vulnerability exi= sts in ssvr in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The v= ulnerability is caused by insufficient bounds checking when parsing RTSP Di= gest authentication fields. A remote attacker may exploit this vulnerabilit=
    y by sending a crafted RTSP request containing overly long authentication d= ata, resulting in memory corruption, denial of service, or potentially arbi= trary code execution. 2026-06-26 9.8 CVE-2026-57880 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-57880 ] GeoVision Inc.--GV-LPCLPC2011/2211 An unauth= enticated stack-based buffer overflow vulnerability exists in vlsvr in GeoV= ision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is cau= sed by insufficient length validation when processing remote login data. A = remote attacker may exploit this vulnerability by sending crafted login dat=
    a with overly long input, resulting in memory corruption, denial of service=
    , or potentially arbitrary code execution. 2026-06-26 9.8 CVE-2026-57881 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-57881 ] GeoVision Inc.--GV-LPCL= PC2011/2211 An unauthenticated format string vulnerability exists in vlsvr =
    in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability=
    is caused by improper handling of externally controlled input during log m= essage formatting in the login processing path. A remote attacker may explo=
    it this vulnerability by sending crafted login data, potentially causing in= formation disclosure, memory corruption, or a denial of service. 2026-06-26=
    8.6 CVE-2026-57877 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57877 ] G= eoVision Inc.--GV-LPCLPC2011/2211 An unauthenticated directory traversal vu= lnerability exists in get_fcont.cgi in GeoVision GV-LPC2011 and GV-LPC2211 = V1.12 and earlier. The vulnerability is caused by insufficient validation o=
    f user-supplied file path input before the requested file is accessed by th=
    e CGI component. A remote attacker may exploit this vulnerability by sendin=
    g a crafted request to read arbitrary files accessible to the affected proc= ess, resulting in information disclosure. 2026-06-26 7.5 CVE-2026-57872 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-57872 ] GeoVision Inc.--GV-LPCLP= C2011/2211 An unauthenticated NULL pointer dereference vulnerability exists=
    in IEEE8021x_upload.cgi in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and e= arlier. The vulnerability is caused by improper validation of multipart upl= oad headers when processing certificate-related upload fields. A remote att= acker may exploit this vulnerability by sending a malformed multipart reque= st, causing the affected CGI process to crash and resulting in a denial of = service. 2026-06-26 7.5 CVE-2026-57873 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-57873 ] GeoVision Inc.--GV-LPCLPC2011/2211 An unauthenticated b= uffer overflow vulnerability exists in IEEE8021x_upload.cgi in GeoVision GV= -LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by i= nsufficient bounds checking when parsing filename values in multipart uploa=
    d data. A remote attacker may exploit this vulnerability by sending a craft=
    ed upload request with overly long input, causing memory corruption and res= ulting in a denial of service. 2026-06-26 7.5 CVE-2026-57874 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-57874 ] GeoVision Inc.--GV-LPCLPC2011/2211 =
    An unauthenticated NULL pointer dereference vulnerability exists in the HTT=
    P request parsing logic of multiple CGI components in GeoVision GV-LPC2011 = and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by improper v= alidation of required HTTP request metadata before it is used by the affect=
    ed components. A remote attacker may exploit this vulnerability by sending =
    a specially crafted HTTP request, causing the affected process to crash and=
    resulting in a denial of service. 2026-06-26 7.5 CVE-2026-57875 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-57875 ] GeoVision Inc.--GV-LPCLPC2011/2= 211 An unauthenticated out-of-bounds write vulnerability exists in onvif.cg=
    i in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerabili=
    ty is caused by insufficient bounds checking when processing HTTP request b= ody data. A remote attacker may exploit this vulnerability by sending a cra= fted request with excessive input, causing memory corruption and resulting =
    in a denial of service. 2026-06-26 7.5 CVE-2026-57876 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-57876 ] getmaxun--maxun Maxun before 0.0.42 contai=
    ns a cross-tenant insecure direct object reference vulnerability in storage=
    and webhook API handlers that allows authenticated users to access other u= sers' robots and OAuth tokens. Attackers can read plaintext Google and Airt= able access tokens, modify, delete, or execute other users' robots by bypas= sing ownership checks in API endpoints. 2026-06-25 8.8 CVE-2026-56767 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-56767 ] getsentry--sentry Sentry i=
    s an error tracking and performance monitoring tool. From 24.4.0 until 26.5= .2, a Regular Expression Denial of Service (ReDoS) vulnerability exists in = Sentry's event ingestion pipeline, where a regex applied to attacker-contro= lled fields on incoming events can be made to consume disproportionate CPU = time. This vulnerability is fixed in 26.5.2. 2026-06-24 7.5 CVE-2026-52794 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-52794 ] Gitea--act_runner Git=
    ea act_runner with the Docker backend (through act 0.262.0) passes a workfl= ow's container.options string to the Docker job container's HostConfig and,=
    when configured with privileged: false, forces only the Privileged flag of=
    f while merging options such as --pid=3Dhost, --cap-add, and --security-opt=
    unchanged. A user who can run a workflow on a Docker-backed runner can cre= ate a job container with host namespaces and broad capabilities and escape =
    to the host as root despite privileged mode being disabled. 2026-06-28 9.9 = CVE-2026-58053 [ https://www.cve.org/CVERecord?id=3DCVE-2026-58053 ] GitLab= --GitLab GitLab has remediated an issue in GitLab EE affecting all versions=
    from 16.4 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that = under certain conditions could have allowed an authenticated user with deve= loper-role permissions to execute arbitrary client-side code in the context=
    of another user's session, due to improper sanitization of user-supplied i= nput. 2026-06-25 8.7 CVE-2026-10086 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-10086 ] GitLab--GitLab GitLab has remediated an issue in GitLab CE/E=
    E affecting all versions from 18.10 before 18.11.6, 19.0 before 19.0.3, and=
    19.1 before 19.1.1 that under certain conditions could have allowed an una= uthenticated user to execute arbitrary JavaScript in a user's browser sessi=
    on due to improper path validation under certain conditions. 2026-06-25 8 C= VE-2026-10712 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10712 ] GitLab-= -GitLab GitLab has remediated an issue in GitLab EE affecting all versions = from 19.1 before 19.1.1 that under certain conditions could have allowed a = user to access sensitive information that had already been committed to a p= roject, due to insufficient output filtering in Duo Workflows. 2026-06-25 8=
    .6 CVE-2026-12053 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12053 ] gog= s--gogs Gogs is an open source self-hosted Git service. Prior to 0.14.3, or= ganization names containing path traversal sequences (../) are accepted by = Gogs, and repositories under them are written to paths following these path=
    traversals. This allows storing/retrieving data for repositories at arbitr= ary locations on the filesystem. By creating nested structure of Git reposi= tories, one can overwrite the other's hooks configuration to result in Remo=
    te Code Execution (RCE). This vulnerability is fixed in 0.14.3. 2026-06-24 =
    10 CVE-2026-52813 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52813 ] gog= s--gogs Gogs is an open source self-hosted Git service. Prior to 0.14.3, Go=
    gs allows authenticated users to achieve Remote Code Execution (RCE) on the=
    server by creating a pull request with a specially crafted branch name tha=
    t injects the --exec flag into the git rebase command during the "Rebase be= fore merging" merge operation. This vulnerability is fixed in 0.14.3. 2026-= 06-24 9.9 CVE-2026-52806 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5280=
    6 ] gogs--gogs Gogs is an open source self-hosted Git service. Prior to 0.1= 4.3, the fix for CVE-2022-1285 prevents adding webooks or running webhooks = with URLs with a hostname that resolves in localCIDRs. However, webhooks st= ill follow redirects allowing to access hostname inside localCIDRs. This vu= lnerability is fixed in 0.14.3. 2026-06-24 8.3 CVE-2026-47267 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-47267 ] gogs--gogs Gogs is an open source = self-hosted Git service. Prior to 0.14.0, as an authorized user, an intrude=
    r can dictate the value which is passed to the git diff command which, toge= ther with bypassing the filtering of the passed value, allows the user to b= ypass the target directory and write the result of the comparison to any ar= bitrary path. This vulnerability is fixed in 0.14.0. 2026-06-24 8.5 CVE-202= 6-52797 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52797 ] gogs--gogs Go=
    gs is an open source self-hosted Git service. Prior to 0.14.3, although .ip= ynb previews are sanitized on the server side via /-/api/sanitize_ipynb, th=
    e inserted content is re-rendered on the client side without sanitization u= sing marked() on elements with the .nb-markdown-cell class. During this pro= cess, links containing schemes such as javascript: can be regenerated. As a=
    result, when a victim views an attacker-crafted .ipynb file and clicks the=
    link, arbitrary JavaScript is executed in the Gogs origin, leading to a cl= ick-based Stored XSS. This vulnerability is fixed in 0.14.3. 2026-06-24 8.9=
    CVE-2026-52798 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52798 ] gogs-= -gogs Gogs is an open source self-hosted Git service. Prior to 0.14.3, orga= nization team member management can be performed via GET requests without C= SRF protection. If a victim who is an organization owner is logged in and i=
    s tricked into visiting a crafted link, an attacker-controlled user can be = added to the Owners team. As a result, the attacker gains organization owne= r-equivalent privileges. This vulnerability is fixed in 0.14.3. 2026-06-24 = 8.8 CVE-2026-52800 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52800 ] go= gs--gogs Gogs is an open source self-hosted Git service. Prior to 0.14.3, t=
    he Gogs Mirror Settings functionality provide an alternative way from the w= ell protected New Migration functionality for any authenticated users to im= port local repositories. This issue stems from a lack of validation of Save= Address function. This vulnerability is fixed in 0.14.3. 2026-06-24 8.1 CVE= -2026-52801 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52801 ] gogs--gog=
    s Gogs is an open source self-hosted Git service. Prior to 0.14.3, a Server= -Side Request Forgery (SSRF) vulnerability exists in the repository migrati=
    on functionality. The application validates only the initially submitted UR=
    L hostname, but git clone --mirror follows HTTP redirects. An authenticated=
    user can submit a public URL that redirects to a blocked internal endpoint=
    (e.g., 127.0.0.1), importing the internal repository's contents into an at= tacker-controlled repository. This vulnerability is fixed in 0.14.3. 2026-0= 6-24 8.7 CVE-2026-52805 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52805=
    ] gogs--gogs Gogs is an open source self-hosted Git service. Prior to 0.14= .3, GET /attachments/:uuid returns the raw attachment file without verifyin=
    g whether the requester has view permission for the associated Issue/Commen= t/Release or the repository. In a test environment with REQUIRE_SIGNIN_VIEW=
    =3D false, we confirmed that an unauthenticated user can download attachme= nts belonging to a private repository. This vulnerability is fixed in 0.14.=
    3. 2026-06-24 7.5 CVE-2026-52799 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-52799 ] gogs--gogs Gogs is an open source self-hosted Git service. Prio=
    r to 0.14.3, three API endpoints - PATCH /api/v1/repos/:owner/:repo/issue-t= racker, PATCH /api/v1/repos/:owner/:repo/wiki, and POST /api/v1/repos/:owne= r/:repo/mirror-sync - are gated by reqRepoWriter() rather than reqRepoAdmin= (). The equivalent operations in the web UI sit behind reqRepoAdmin, which = requires AccessMode >=3D AccessModeAdmin. A write-level collaborator (who h=
    as AccessMode =3D=3D AccessModeWrite < AccessModeAdmin) can therefore call = these API endpoints directly to disable the native issue tracker or wiki, i= nject attacker-controlled external tracker/wiki URLs that redirect all repo= sitory visitors, or trigger mirror sync - none of which they are authorized=
    to do. This vulnerability is fixed in 0.14.3. 2026-06-24 7.1 CVE-2026-5280=
    8 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52808 ] Google--AngularJS A=
    flaw in AngularJS' Strict Contextual Escaping (SCE) logic allows bypassing=
    certain SCE policies for resource URLs and can lead to arbitrary JavaScrip=
    t execution within the context of the victim's browser session. SCE's purpo=
    se is to ensure that only trusted or safe values are used in certain securi= ty-sensitive contexts, such as resource URLs, including URLs that define ex= ecutable JavaScript scripts, '<iframe>' documents, route templates, etc. A = flaw in the logic that tries to match entire URLs against regular expressio=
    n matchers can result in partial matches for certain types of regular expre= ssions, effectively bypassing the policies and allowing the use of unsafe v= alues as resource URLs. This issue affects AngularJS versions greater than =
    or equal to 1.2.0-rc.3. Note: The AngularJS project was already End-of-Life=
    when this CVE was published and will not receive any updates to address th=
    is issue. For more information see the=C2=A0 End-of-Life announcement https= ://docs.angularjs.org/misc/version-support-status . 2026-06-24 7.6 CVE-2026= -11998 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11998 ] Grafana--Grafa=
    na Enterprise The public dashboard query endpoint does not limit request bo=
    dy size before processing, allowing unauthenticated attackers to trigger ex= cessive memory allocation by sending arbitrarily large JSON payloads. This = can lead to denial of service through memory exhaustion. No valid dashboard=
    access token or authentication is required to exploit this vulnerability. = 2026-06-22 7.5 CVE-2026-42127 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -42127 ] Grafana--Grafana OSS The Loki datasource plugin's callResource han= dler contains a path traversal vulnerability. An authenticated Viewer-role = user can escape the plugin's resource sandbox and access administrative Lok=
    i endpoints (e.g. /config, /services, /ready) to extract sensitive backend = configuration and internal service information. 2026-06-22 7.7 CVE-2026-421=
    29 [ https://www.cve.org/CVERecord?id=3DCVE-2026-42129 ] Grafana--Grafana O=
    SS The geomap panel's XYZ tile layer has a sanitize-then-interpolate orderi=
    ng bug. sanitizeTextPanelContent() runs on the raw template string before g= etTemplateSrv().replace() substitutes the variable value, which uses the gl=
    ob format with no HTML escaping. The result is passed to OpenLayers via ele= ment.innerHTML. An Editor can set a textbox variable's default value to an = XSS payload that executes for every user who opens the dashboard. This is a=
    bypass of the CVE-2023-0507 fix 2026-06-22 7.3 CVE-2026-9029 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-9029 ] Grafana--Snowflake Datasource The S= nowflake datasource allows for GET/PUT commands, which can allow any user w= ith access to run queries against the data source to read/write files betwe=
    en the local grafana server and the connected Snowflake host. 2026-06-22 9.=
    6 CVE-2026-28381 [ https://www.cve.org/CVERecord?id=3DCVE-2026-28381 ] H.VI= EW--HV-500S6 IP Camera A vulnerability exists in H.View IP cameras that cou=
    ld allow an authenticated user to supply unsanitized XML fields to the devi= ce's certificate generation interface, which are incorporated into a backen=
    d certificate creation command without proper input validation. This may al= low for command execution with elevated privileges during certificate gener= ation. 2026-06-26 7.2 CVE-2026-55975 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-55975 ] H.VIEW--HV-500S6 IP Camera A vulnerability exists in H.View=
    IP cameras certificate-related upload interfaces allow authenticated users=
    to store arbitrary file content to fixed, persistent filesystem locations = without validating file type, structure, or size. This design omission enab= les the placement of unexpected or malformed data in locations intended for=
    trusted certificate material, which could affect system integrity or behav= ior even after reboot. 2026-06-26 7.2 CVE-2026-56414 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-56414 ] H5P--H5P Unauthenticated Cross Site Scripti=
    ng (XSS) in H5P <=3D 1.17.6 versions. 2026-06-25 7.1 CVE-2026-56006 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-56006 ] haiwen--seahub Seahub before=
    13.0.23 does not enforce SHARE_LINK_LOGIN_REQUIRED on GET /api/v2.1/share-= link-zip-task/, allowing unauthenticated users to bypass authentication. At= tackers with a folder share-link token can call the GET endpoint to obtain =
    a fileserver zip token and download entire shared directory trees. 2026-06-=
    25 8.8 CVE-2026-56768 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56768 ]=
    hancock11--WP Forms Connector The WP Forms Connector plugin for WordPress =
    is vulnerable to Information Exposure in all versions up to, and including,=
    1.8. The plugin registers the REST route wp/v3/user/list/<id> (callback us= erDetail()) with permission_callback set to '__return_true', and the functi= on's home-grown authentication only verifies that the supplied 'Username' H= TTP header maps to an administrator account and that a 'Password' HTTP head=
    er is non-empty. It never validates the password with wp_check_password() (= unlike the sibling delete_wc_user() function which does). This makes it pos= sible for unauthenticated attackers to retrieve sensitive information for a=
    ny registered user ID - including the WordPress password hash (user_pass) a=
    nd email address - by sending a request with a valid administrator login na=
    me (commonly the default 'admin') and any arbitrary password value. 2026-06= -24 7.5 CVE-2026-9178 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9178 ] = hancock11--WP Forms Connector The WP Forms Connector plugin for WordPress i=
    s vulnerable to SQL Injection via the 'order' parameter of the /wp-json/wp/= v3/post/list REST endpoint in versions up to and including 1.8. This is due=
    to insufficient escaping on the user-supplied 'order' parameter (read dire= ctly from $_GET['order'] into $shorting) and the lack of sufficient prepara= tion on the existing SQL query in the listPost() function, where the value =
    is concatenated unquoted into the ORDER BY clause and executed via $wpdb->g= et_results() without $wpdb->prepare(). The endpoint is registered with perm= ission_callback '__return_true' and performs only a broken header-based che=
    ck that validates the supplied 'Username' corresponds to an administrator a= ccount while never verifying the 'Password'. This makes it possible for una= uthenticated attackers to append additional SQL queries into already existi=
    ng queries that can be used to extract sensitive information from the datab= ase. 2026-06-24 7.5 CVE-2026-9179 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-9179 ] hcengineering--platform Huly Platform through 0.7.423, fixed in=
    commit 68cbf8a contains an authenticated server-side request forgery vulne= rability in the /import endpoint of front pod that allows workspace users t=
    o make arbitrary server requests. Attackers can exploit this by supplying m= alicious URLs to fetch internal services, exfiltrate responses, and replay = credentials against backend systems. 2026-06-25 8.5 CVE-2026-56769 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-56769 ] HCLSoftware--Traveler for Mic= rosoft Outlook HCL Traveler for Microsoft Outlook (HTMO) is susceptible to = vulnerabilities due to .NET Framework 4.5 being out of service. =C2=A0Since=
    .NET Framework 4.5 has reached end-of-life and no longer receives security=
    updates, it may expose the application to publicly known security weakness=
    es through vulnerable third-party components. 2026-06-27 7.7 CVE-2023-37524=
    [ https://www.cve.org/CVERecord?id=3DCVE-2023-37524 ] home-assistant--core=
    Home Assistant is open source home automation software that puts local con= trol and privacy first. Prior to 2026.6.0, the Konnected integration regist= ers an HTTP endpoint, KonnectedView (homeassistant/components/konnected/__i= nit__.py), that is marked as not requiring authentication (requires_auth =
    =3D False). A comment next to that line says auth is instead handled "via t=
    he access token from configuration." That promise is only half true. Write = requests (POST and PUT) are handled by update_sensor(), which does check th=
    e request's Authorization: Bearer <token> header against the integration's = stored access tokens (using hmac.compare_digest). Read requests (GET) are h= andled by a separate get() method that has no authentication check at all. = This vulnerability is fixed in 2026.6.0. 2026-06-23 7.6 CVE-2026-54317 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-54317 ] home-assistant--core Home=
    Assistant is open source home automation software that puts local control = and privacy first. Prior to 2026.5.3, the LocationSensorManager BroadcastRe= ceiver is exported with no permission. Any installed app, with zero runtime=
    permissions, can broadcast a forged Google Play Services LocationResult di= rectly to it; the receiver trusts the extra and forwards it to the user's H= ome Assistant server as the device's real location. This bypasses Android's=
    developer-mode "Mock Location" gate and allows a local malicious app to dr= ive zone-based automations (unlock door / disarm alarm / open garage) by fa= king the user's GPS position. This vulnerability is fixed in 2026.5.3. 2026= -06-23 7.1 CVE-2026-54318 [ https://www.cve.org/CVERecord?id=3DCVE-2026-543=
    18 ] honojs--hono Hono is a Web application framework that provides support=
    for any JavaScript runtime. Prior to 4.12.25, with credentials: true and n=
    o explicit origin (the default wildcard), the CORS Middleware reflects the = request's Origin and sends Access-Control-Allow-Credentials: true. Any site=
    can then make credentialed cross-origin requests and read the responses, e= xposing cookie-authenticated endpoints to arbitrary origins. This vulnerabi= lity is fixed in 4.12.25. 2026-06-22 7.1 CVE-2026-54290 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-54290 ] Hubbell--Aclara Metrum Cellular Web Inte= rface The Aclara Metrum Cellular Web Interface is vulnerable to unauthorize=
    d access due to the absence of authentication controls on critical system f= unctions. This weakness exposes essential configuration settings, allowing = attackers to alter operational parameters and trigger system restarts witho=
    ut restriction. Such unauthorized changes can disrupt normal functionality = and, if performed repeatedly, may lead to a loss of communications to the d= evice. 2026-06-24 7.5 CVE-2026-1840 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-1840 ] IBM--i IBM WebSphere Application Server and IBM WebSphere App= lication Server Liberty - when using Intelligent Management with the WebSph= ere WebServer Plug-in component - are vulnerable to remote code execution a=
    nd denial of service. This vulnerability can be exploited when an attacker = impersonates backend servers and sends crafted responses to the plug-in. 20= 26-06-22 8.1 CVE-2026-9072 [ https://www.cve.org/CVERecord?id=3DCVE-2026-90=
    72 ] IBM--i IBM WebSphere Application Server and IBM WebSphere Application = Server Liberty are vulnerable to remote code execution and denial of servic=
    e in the WebSphere Web Server Plug-in component. This vulnerability can be = exploited when an attacker impersonates the application server and sends cr= afted responses to the plug-in. 2026-06-22 7.5 CVE-2026-8858 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-8858 ] IBM--Langflow OSS IBM Langflow OSS 1= .0.0 through 1.9.3 has an vulnerability due to an improper isolation of Pyt= hon execution combined with an authentication bypass that allows an unauthe= nticated attacker to execute arbitrary code on the host system, resulting i=
    n complete compromise 2026-06-22 10 CVE-2026-10561 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-10561 ] IBM--Langflow OSS IBM Langflow OSS 1.0.0 thro= ugh 1.8.4 could allow unauthenticated attackers to access protected MCP pro= ject resources and execute MCP operations due to improper authorization enf= orcement in the Streamable MCP transport endpoint. 2026-06-22 9.8 CVE-2026-= 7664 [ https://www.cve.org/CVERecord?id=3DCVE-2026-7664 ] IBM--Storage Prot= ect Client IBM Storage Protect Client 8.1.0.0 through 8.2.1.0 and IBM Stora=
    ge Protect Snapshot For Windows 8.1.0.0 through 8.2.1.0 could allow a remot=
    e attacker to bypass authentication due to the use of a hardcoded credentia=
    l in the FlashCopy Manager (FCM) authentication mechanism. The application = contains a static credential embedded in multiple authentication code paths=
    , and does not properly validate authentication responses, which may allow =
    an unauthenticated attacker to establish a trusted session and access prote= cted services. This vulnerability affects client components across multiple=
    versions and may allow an attacker to impersonate legitimate clients, pote= ntially leading to unauthorized access to system resources. 2026-06-22 9.1 = CVE-2026-12628 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12628 ] IBM--W= ebSphere Application Server IBM WebSphere Application Server 9.0 and 8.5 an=
    d IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.6 are = vulnerable to HTTP request smuggling. A remote attacker could smuggle a spe= cially crafted request to the application server thereby allowing the attac= ker to bypass security controls, spoof identity, escalate privilege, and ex= pose sensitive information. 2026-06-22 7.4 CVE-2026-8646 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-8646 ] IBM--WebSphere Application Server IBM We= bSphere Application Server 9.0, and 8.5 is vulnerable to server-side reques=
    t forgery (SSRF) with the Ajax Proxy configured. This may allow an attacker=
    to send unauthorized requests from the system, resulting in a security byp= ass or information disclosure. 2026-06-22 7.4 CVE-2026-9006 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-9006 ] IBM--WebSphere Application Server IBM=
    WebSphere Application Server 9.0, and 8.5 and IBM WebSphere Application Se= rver - Liberty 17.0.0.3 through 26.0.0.6 are vulnerable to a denial of serv= ice, caused by sending a specially-crafted request. A remote attacker could=
    exploit this vulnerability to cause the server to consume memory resources=
    . 2026-06-22 7.5 CVE-2026-9071 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-9071 ] icc0rz--H5P Contributor Arbitrary File Deletion in H5P <=3D 1.17.7=
    versions. 2026-06-26 7.1 CVE-2026-57321 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-57321 ] Igor Benic--Recipe Maker For Your Food Blog from Zip Re= cipes Contributor SQL Injection in Recipe Maker For Your Food Blog from Zip=
    Recipes <=3D 8.2.7 versions. 2026-06-26 8.5 CVE-2026-57663 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-57663 ] immich-app--immich immich is a high = performance self-hosted photo and video management solution. From commit 4f= fa26c9 until 4eb1003, a reflected cross-site scripting (XSS) vulnerability =
    on the /auth/login page allows an attacker to fully compromise any authenti= cated user's account with a single link click. The continue query parameter=
    is read from the URL and passed to SvelteKit's redirect() without any sche=
    me or origin validation, allowing attacker-controlled JavaScript to execute=
    inside Immich's origin. The payload then uses the victim's existing sessio=
    n to mint an all-permission API key on their account, leading to persistent=
    account takeover. This vulnerability is fixed in commit 4eb1003. 2026-06-2=
    3 9.6 CVE-2026-53662 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53662 ] = InspiryThemes--RealHomes Subscriber PHP Object Injection in RealHomes <=3D = 4.5.3 versions. 2026-06-26 8.8 CVE-2026-56055 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-56055 ] Jacob N. Breetvelt--WP Photo Album Plus Improper N= eutralization of Special Elements used in an SQL Command ('SQL Injection') = vulnerability in Jacob N. Breetvelt WP Photo Album Plus allows Blind SQL In= jection. This issue affects WP Photo Album Plus: from n/a through 9.1.13.00=
    5. 2026-06-25 7.5 CVE-2026-54829 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-54829 ] Jay Versluis--Child Theme Wizard Unauthenticated Cross Site Req= uest Forgery (CSRF) in Child Theme Wizard <=3D 1.4 versions. 2026-06-26 8.2=
    CVE-2026-57655 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57655 ] jdx--= mise mise manages dev tools like node, python, cmake, and terraform. Prior =
    to 2026.3.10, mise processes .tool-versions files through the Tera template=
    engine during parsing, with the exec() function registered, enabling arbit= rary command execution. Unlike .mise.toml files, .tool-versions files are n=
    ot subject to trust verification in non-paranoid mode. This means an attack=
    er can place a malicious .tool-versions file in a git repository, and when =
    a victim with mise activated cds into the directory, arbitrary commands exe= cute without any trust prompt. This vulnerability is fixed in 2026.3.10. 20= 26-06-26 9.6 CVE-2026-33646 [ https://www.cve.org/CVERecord?id=3DCVE-2026-3= 3646 ] jdx--mise mise manages dev tools like node, python, cmake, and terra= form. Prior to 2026.6.4, mise's trust feature gates config files (mise.toml=
    , .tool-versions) through trust_check, but task-include files are loaded on=
    a path that never reaches it. When a directory has a task-include dir (mis= e-tasks/, .mise/tasks/,=C2=A6) but no config file, mise falls back to the d= efault includes and renders each task's tera fields - and that tera environ= ment has exec() registered. A {{ exec(command=3D=C2=A6') }} in any rendered=
    field runs arbitrary commands the moment the tasks are merely listed. Ther= e's no config file to gate on, so no trust prompt ever appears. Read-only c= ommands trigger it: mise tasks, mise task ls, mise run, mise tasks --usage = (the query shell completion runs on Tab). The victim only has to cd into a = cloned repo and list or tab-complete a task. This vulnerability is fixed in=
    2026.6.4. 2026-06-26 8.6 CVE-2026-55441 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-55441 ] Jegstudio--Gutenverse Companion Unauthenticated Broken = Access Control in Gutenverse Companion <=3D 2.5.0 versions. 2026-06-26 7.5 = CVE-2026-54832 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54832 ] jellyf= in--jellyfin Jellyfin is an open source self hosted media server. Prior to = 10.11.10, a potential FFmpeg argument injection vulnerability exists in the=
    subtitle conversion code path. SubtitleEncoder.ConvertTextSubtitleToSrtInt= ernal (SubtitleEncoder.cs, line 382) interpolates the subtitle file path in=
    to FFmpeg command-line arguments without calling EncodingUtils.NormalizePat= h(). On Linux, filenames can contain double-quote characters, which break t=
    he argument quoting and allow injection of arbitrary FFmpeg arguments. The = vulnerability is reachable without authentication via SubtitleController.Ge= tSubtitle, which has no [Authorize] attribute. An attacker who can place a = file in a Jellyfin media library directory (shared NAS, Samba share, guest = upload) can achieve arbitrary file write on the server and information disc= losure. This vulnerability is fixed in 10.11.10. 2026-06-24 8.8 CVE-2026-48= 793 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48793 ] jellyfin--jellyfi=
    n Jellyfin is an open source self hosted media server. From 10.9.0 until 10= .11.10, the POST /ClientLog/Document endpoint accepts the Authorization hea= der's Client and Version fields and uses them unsanitized as components of = the on-disk filename when persisting client-uploaded log documents. As a re= sult, any authenticated non-admin user can include ../ sequences in the Cli= ent field to cause Jellyfin to write attacker-controlled content to arbitra=
    ry paths reachable by the Jellyfin service user, with a forced .log suffix.=
    This vulnerability is fixed in 10.11.10. 2026-06-24 8.8 CVE-2026-49247 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-49247 ] Jellywp--NanoMag Unauthe= nticated Cross Site Scripting (XSS) in NanoMag <=3D 1.8 versions. 2026-06-2=
    6 7.1 CVE-2026-57325 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57325 ] = jetmonsters--Restaurant Menu by MotoPress Contributor SQL Injection in Rest= aurant Menu by MotoPress <=3D 2.4.10 versions. 2026-06-26 8.5 CVE-2026-5764=
    4 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57644 ] Johnson & Johnson--= Audit Tracking Management System Johnson & Johnson Audit Tracking Managemen=
    t System (ATMS) before 2026-04-21 allows viewing of meeting minutes and tra= nscripts. 2026-06-26 7.5 CVE-2026-57913 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-57913 ] Johnson & Johnson--Campus Recruiting Johnson & Johnson = Campus Recruiting before 2025-10-31 allows viewing of data provided by recr= uited students, and notes entered about students by interviewers. 2026-06-2=
    6 7.5 CVE-2026-57912 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57912 ] = joomunited--WP Meta SEO The WP Meta SEO plugin for WordPress is vulnerable =
    to Unauthenticated Stored Cross-Site Scripting via the REQUEST_URI server v= ariable in all versions up to, and including, 4.5.18. When the plugin's `wp= msTemplateRedirect()` hook detects a 404, it concatenates `$_SERVER['HTTP_H= OST']` with the raw `$_SERVER['REQUEST_URI']` and inserts that value verbat=
    im into the `wp_wpms_links.link_url` column via `$wpdb->insert()`. This mak=
    es it possible for unauthenticated attackers to inject arbitrary web script=
    s that execute whenever an administrator views the plugin's 404 & Redirects=
    admin page (`/wp-admin/admin.php?page=3Dmetaseo_broken_link`). 2026-06-24 = 7.2 CVE-2026-9643 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9643 ] jqla= ng--jq jq is a command-line JSON processor. Prior to 1.8.2,` jq --rawfile` = can turn a handled oversized-string error into invalid-state reuse and a re=
    al heap out-of-bounds write in assertion-disabled builds. When jv_load_file= (raw=3D1) reads an attacker-controlled file, it repeatedly appends file chu= nks to the same jv string accumulator. Once jv_string_append_buf() returns = jv_invalid_with_msg("String too long"), the raw-file loop does not stop. If=
    the file contains at least one more byte, the next loop iteration appends =
    a new chunk to an object that is already invalid. With assertions enabled t= his aborts in jvp_string_ptr(). With assertions disabled, the invalid objec=
    t is interpreted as a string object and ASan reports heap-buffer-overflow. = This vulnerability is fixed in 1.8.2. 2026-06-25 7.1 CVE-2026-49839 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-49839 ] kestra-io--kestra Kestra is =
    an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.= 3.21, AuthenticationFilter in Kestra OSS uses request.getPath().endsWith("/= configs") to whitelist the public configuration endpoint from Basic Auth. B= ecause the check is a suffix match rather than an exact path match, any API=
    path whose last segment is configs bypasses authentication entirely. An un= authenticated remote attacker can exploit this to create and execute arbitr= ary workflows without credentials. Because Kestra ships with script executi=
    on plugins (plugin-script-shell, plugin-script-python, etc.) enabled by def= ault, this directly results in unauthenticated Remote Code Execution as roo=
    t inside the Kestra worker container. This vulnerability is fixed in 1.0.45=
    and 1.3.21. 2026-06-26 10 CVE-2026-49869 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-49869 ] kestra-io--kestra Kestra is an open-source, event-driv=
    en orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication f= ilter for the REST API (@Filter("/api/v1/**")) treats any request whose pat=
    h ends in /configs as the public instance-config endpoint and forwards it w= ithout a credential check. kestra addresses its resources by URL path segme= nts that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{t= enant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}= /kv/{key}). An anonymous caller picks the literal configs as the final segm= ent, and the request bypasses Basic-Auth entirely. Because the bypass reach=
    es the flow-create and execution-trigger routes, an unauthenticated caller = creates a flow containing a Shell or Process task and runs it. The task exe= cutes as root inside the kestra container. The official docker-compose.yml = mounts /var/run/docker.sock, so root in the container reaches the host Dock=
    er daemon. This vulnerability is fixed in 1.0.45 and 1.3.21. 2026-06-26 10 = CVE-2026-53576 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53576 ] kestra= -io--kestra Kestra is an open-source, event-driven orchestration platform. = Prior to 1.3.24, this vulnerability exists in the BasicAuth authentication = component of the Kestra OSS workflow orchestration platform. An attacker wh=
    o gains read access to the PostgreSQL database can exploit SHA-512's high c= omputation speed to recover the administrator password offline. In Kubernet=
    es deployments, a successful crack further enables reading of the cluster S= erviceAccount Token and all K8s Secrets, achieving vertical privilege escal= ation. This vulnerability is fixed in 1.3.24. 2026-06-26 8.7 CVE-2026-55069=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-55069 ] kestra-io--kestra Ke= stra is an open-source, event-driven orchestration platform. Prior to 1.0.4=
    3 and 1.3.19, several Kestra API endpoints accept a kestra:// URI from the = client and pass it through StorageInterface.parentTraversalGuard before rea= ding the underlying file from the local storage backend. The guard only ins= pects the literal URI.toString(), so a URL-encoded .. written as %2E%2E sli=
    ps through. The downstream code then calls URI.getPath(), which decodes %2E= %2E back to .., and the resulting path is handed to Paths.get(...) without = normalization. The OS resolves the .. segments at open(2) time, so an authe= nticated user with a single execution can read any file the Kestra process = has access to on the host filesystem (/etc/passwd, mounted secrets, other t= enants' execution outputs, etc.). This vulnerability is fixed in 1.0.43 and=
    1.3.19. 2026-06-26 7.7 CVE-2026-45807 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-45807 ] kestra-io--kestra Kestra is an open-source, event-drive=
    n orchestration platform. Prior to 1.0.45 and 1.3.23, the local internal-st= orage backend validates user-supplied paths for .. traversal before it conv= erts Windows-style backslashes to forward slashes. An attacker can therefor=
    e smuggle a traversal sequence past the guard using backslashes (..\..\..\)=
    ; the guard sees a harmless string, and the path is only rewritten to ../..= /../ after validation, immediately before the file is opened. Any authentic= ated user who can view an execution (the lowest-privilege role) can call GE=
    T /api/v1/{tenant}/executions/{executionId}/file?path=3D=C2=A6 and read any=
    file on the server filesystem readable by the Kestra process, outside the = storage sandbox and across every tenant and namespace. This includes the em= bedded H2 database (all flows, all users, all stored secrets), internal sto= rage of every other tenant/namespace, mounted secret files, and the process=
    environment (/proc/self/environ) which contains configured database and se= cret-backend credentials. It is a complete breach of Kestra's storage isola= tion and multi-tenancy boundary. This vulnerability is fixed in 1.0.45 and = 1.3.23. 2026-06-26 7.7 CVE-2026-49984 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-49984 ] kingaddons--Trinity Backup =E2=80=9C Backup, Migrate, Rest= ore, Clone & Schedule Backups Unauthenticated Sensitive Data Exposure in Tr= inity Backup &#8211; Backup, Migrate, Restore, Clone &amp; Schedule Backups=
    <=3D 2.0.9 versions. 2026-06-26 7.5 CVE-2026-54839 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-54839 ] Kludex--python-multipart Python-Multipart is=
    a streaming multipart parser for Python. Prior to 0.0.30, when parsing app= lication/x-www-form-urlencoded bodies, QuerystringParser located the field = separator with a two step lookup: it first scanned the entire remaining buf= fer for &, and only when no & existed anywhere ahead did it fall back to sc= anning for ;. For a body that uses ; as the separator and contains no &, ev= ery field iteration performed a full failed & scan over the entire remainin=
    g buffer before locating the nearby ;. With N semicolon separated fields in=
    a chunk of size B, this yields O(B^2) byte comparisons per chunk. An attac= ker can submit a small crafted body of the form a;a;a;... and cause the par= ser to spend seconds of CPU per request. A handful of concurrent requests c=
    an exhaust worker processes. This vulnerability is fixed in 0.0.30. 2026-06= -22 7.5 CVE-2026-53539 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53539 =
    ] Kludex--starlette Starlette is a lightweight ASGI framework/toolkit. From=
    0.4.1 until 1.3.1, request.form() accepts max_fields and max_part_size to = bound resource consumption while parsing form data. These limits are enforc=
    ed for multipart/form-data, but silently ignored for application/x-www-form= -urlencoded. An unauthenticated attacker can therefore send a urlencoded bo=
    dy with an arbitrarily large number of fields or an arbitrarily large field=
    , even when the application configured limits it believed would apply. This=
    vulnerability is fixed in 1.3.1. 2026-06-22 7.5 CVE-2026-54283 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-54283 ] labstack--echo Echo is a Go web = framework. Prior to 4.15.3 and 5.2.0, Echo's router and static file handler=
    disagree on URL path decoding. The router matches routes using the raw enc= oded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2=
    F to / before resolving filesystem paths. This allows an attacker to bypass=
    route-level access controls and read static files without authorization. T= his vulnerability is fixed in 4.15.3 and 5.2.0. 2026-06-26 7.5 CVE-2026-556=
    77 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55677 ] langflow-ai--langf= low Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.9.2, the "Shareable Playground" (or "Public Flows" in co= de) contains a critical RCE vulnerability. Shareable Playground feature wor=
    ks by enabling the execution of workflows by unauthenticated users, by acce= ssing a link. Specifically, it enables the route /api/v1/build_public_tmp t=
    o execute any public flow, given a public flow ID. When the route executes = the flow, it allows for providing arbitrary custom Python code as the nodes=
    code, inside the JSON payload. The vulnerable field is data.nodes[X].data.= node.template.code.value. This vulnerability is fixed in 1.9.2. 2026-06-23 = 9.6 CVE-2026-48519 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48519 ] la= ngflow-ai--langflow Langflow is a tool for building and deploying AI-powere=
    d agents and workflows. Prior to 1.9.2, an Insecure Direct Object Reference=
    (IDOR) vulnerability in /api/v1/responses endpoint allows an authenticated=
    attacker to execute any flow belonging to another user by specifying the v= ictim's flow ID in the request. This vulnerability is fixed in 1.9.2. 2026-= 06-23 9.9 CVE-2026-55255 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5525=
    5 ] langflow-ai--langflow Langflow is a tool for building and deploying AI-= powered agents and workflows. Prior to 1.9.2, by controlling a files that a=
    re digested into the RAG, an attacker can direct the node to read any file =
    on the file-system by absolute path. All components based on BaseFileCompon= ent are vulnerable to the vulnerability. This includes Docling (DoclingInli= neComponent), Docling Serve, DoclingRemoteComponent), Read File (FileCompon= ent), NVIDIA Retriever Extraction (NvidiaIngestComponent), Video File (Vide= oFileComponent), and Unstructured API (UnstructuredComponent). This vulnera= bility is fixed in 1.9.2. 2026-06-23 9.6 CVE-2026-55447 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-55447 ] langflow-ai--langflow Langflow is a tool=
    for building and deploying AI-powered agents and workflows. Prior to 1.9.1=
    , unauthenticated users can upload any amount of data to the server without=
    any limitations. No need for any prior knowledge, only network access to L= angflow. This can lead to space exhaustion on the server. In addition, in t=
    he response, the absolute path of the uploaded file is reported to the atta= cker, which is an information leak that can assist in chaining other primit= ives. This vulnerability is fixed in 1.9.1. 2026-06-23 9.3 CVE-2026-55450 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-55450 ] langflow-ai--langflow = Langflow is a tool for building and deploying AI-powered agents and workflo= ws. Prior to 1.9.0, Langflow's /api/v1/monitor router exposes 7 endpoints t= hat perform read, write, and delete operations on user-owned resources - me= ssages, sessions, build artifacts, and LLM transaction logs - without verif= ying that the authenticated requester owns the targeted resource. Any authe= nticated user can read, modify, rename, or permanently delete another user'=
    s data by supplying the target's resource ID or flow_id. This is a classic = IDOR/BOLA vulnerability. Notably, the same source file (monitor.py) contain=
    s one correctly-implemented endpoint that uses an ownership check, demonstr= ating the correct pattern was known but inconsistently applied. This vulner= ability is fixed in 1.9.0. 2026-06-23 8.8 CVE-2026-33760 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-33760 ] langflow-ai--langflow Langflow is a too=
    l for building and deploying AI-powered agents and workflows. Prior to 1.0.= 19, an attacker can send a /api/v1/files/upload/ request without any authen= tication token/cookies and abuse a very long multipart form boundary to mak=
    e the langflow app unusable for all users for an indefinite amount of time.=
    This vulnerability is fixed in 1.0.19. 2026-06-23 7.5 CVE-2026-55446 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-55446 ] libssh2--libssh2 libssh2 t= hrough 1.11.1 reads an attacker-controlled 32-bit attribute count from a pu= blickey-subsystem response and uses it in the allocation num_attrs * sizeof= (libssh2_publickey_attribute) without bounds checking, so on 32-bit platfor=
    ms the multiplication overflows to an undersized buffer. A malicious SSH se= rver can then drive the attribute-parsing loop to write past the allocation=
    , causing a heap buffer overflow in a connecting libssh2 client. 2026-06-28=
    7 CVE-2026-58050 [ https://www.cve.org/CVERecord?id=3DCVE-2026-58050 ] Lin= ux--Linux In the Linux kernel, the following vulnerability has been resolve=
    d: batman-adv: fix fragment reassembly length accounting batman-adv keeps a=
    running payload length for queued fragments and uses it to validate a frag= ment chain before reassembly. That accounting currently allows the accumula= ted fragment length to be truncated during updates. As a result, malformed = fragment chains can bypass the intended validation and drive reassembly wit=
    h inconsistent length state, leading to a local denial of service. Fix the = accounting by storing the accumulated length in a length-typed field and re= jecting update overflows before the existing validation logic runs. The fix=
    was verified against the original reproducer and against valid fragment re= assembly paths. 2026-06-24 9.8 CVE-2026-52914 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-52914 ] Linux--Linux In the Linux kernel, the following vu= lnerability has been resolved: sctp: purge outqueue on stale COOKIE-ECHO ha= ndling sctp_stream_update() is only invoked when the association is moved i= nto COOKIE_WAIT during association setup/reconfiguration. In this path, the=
    outbound stream scheduler state (stream->out_curr) is expected to be clean=
    , since no user data should have been transmitted yet unless the state mach= ine has already partially progressed. However, a corner case exists in sctp= _sf_do_5_2_6_stale(): when a Stale Cookie ERROR is received, the associatio=
    n is rolled back from COOKIE_ECHOED to COOKIE_WAIT. In this scenario, user = data may already have been queued and even bundled with the COOKIE-ECHO chu= nk. During the rollback, sctp_stream_update() frees the old stream table an=
    d installs a new one, but it does not invalidate stream->out_curr. As a res= ult, out_curr may still point to a freed sctp_stream_out entry from the pre= vious stream state. Later, SCTP scheduler dequeue paths (FCFS, RR, PRIO, et= c.) rely on stream->out_curr->ext, which can lead to use-after-free once th=
    e old stream state has been released via sctp_stream_free(). This results i=
    n crashes such as (reported by Yuqi): BUG: KASAN: slab-use-after-free in sc= tp_sched_fcfs_dequeue+0x13a/0x140 Read of size 8 at addr ff1100004d4d3208 b=
    y task mini_poc/9312 CPU: 1 UID: 1001 PID: 9312 Comm: mini_poc Not tainted = 7.1.0-rc1-00305-gbd3a4795d574 #5 PREEMPT(full) sctp_sched_fcfs_dequeue+0x13= a/0x140 sctp_outq_flush+0x1603/0x33e0 sctp_do_sm+0x31c9/0x5d30 sctp_assoc_b= h_rcv+0x392/0x6f0 sctp_inq_push+0x1db/0x270 sctp_rcv+0x138d/0x3c10 Fix this=
    by fully purging the association outqueue when handling the Stale Cookie c= ase. This ensures all pending transmit and retransmit state is dropped, and=
    any scheduler cached pointers are invalidated, making it safe to rebuild s= tream state during COOKIE_WAIT restart. Updating only stream->out_curr woul=
    d be insufficient, since queued and retransmittable data would still refere= nce the old stream state and trigger later use-after-free in dequeue paths.=
    2026-06-24 9.8 CVE-2026-52924 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-52924 ] Linux--Linux In the Linux kernel, the following vulnerability has=
    been resolved: batman-adv: tp_meter: avoid use of uninit sender vars batad= v_tp_recv_ack() and batadv_tp_stop() are only valid for tp_vars in the BATA= DV_TP_SENDER role. When called with a BATADV_TP_RECEIVER role, it proceeds =
    to read sender-only members that were never initialized, leading to undefin=
    ed behavior. This can be triggered when a node that is currently acting as =
    a receiver in an ongoing tp_meter session receives a malicious ACK packet. = Guard against this by checking tp_vars->role immediately after the lookup a=
    nd bailing out if it is not BATADV_TP_SENDER, before any of those members a=
    re accessed. 2026-06-24 9.8 CVE-2026-52931 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-52931 ] Linux--Linux In the Linux kernel, the following vulne= rability has been resolved: libceph: Fix potential out-of-bounds access in = crush_decode() A message of type CEPH_MSG_OSD_MAP containing a crush map wi=
    th at least one bucket has two fields holding the bucket algorithm. If the = values in these two fields differ, an out-of-bounds access can occur. This =
    is the case because the first algorithm field (alg) is used to allocate the=
    correct amount of memory for a bucket of this type, while the second algor= ithm field inside the bucket (b->alg) is used in the subsequent processing.=
    This patch fixes the issue by adding a check that compares alg and b->alg = and aborts the processing in case they differ. Furthermore, b->alg is set t=
    o 0 in this case, because the destruction of the crush map also uses this f= ield to determine the bucket type, which can again result in an out-of-boun=
    ds access when trying to free the memory pointed to by the fields of the bu= cket. To correctly free the memory allocated for the bucket in such a case,=
    the corresponding call to kfree is moved from the algorithm-specific crush= _destroy_bucket functions to the generic crush_destroy_bucket(). 2026-06-24=
    9.8 CVE-2026-52955 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52955 ] L= inux--Linux In the Linux kernel, the following vulnerability has been resol= ved: libceph: Fix potential out-of-bounds access in osdmap_decode() When de= coding osd_state and osd_weight from an incoming osdmap in osdmap_decode(),=
    both are decoded for each osd, i.e., map->max_osd times. The ceph_decode_n= eed() check only accounts for sizeof(*map->osd_weight) once. This can poten= tially result in an out-of-bounds memory access if the incoming message is = corrupted such that the max_osd value exceeds the actual content of the osd= map message. This patch fixes the issue by changing the corresponding part =
    in the ceph_decode_need() check to account for map->max_osd*sizeof(*map->os= d_weight). 2026-06-24 9.1 CVE-2026-52958 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-52958 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: net: usb: rtl8150: fix use-after-free in rtl8150_= start_xmit() syzbot reported a KASAN slab-use-after-free read in rtl8150_st= art_xmit() when accessing skb->len for tx statistics after usb_submit_urb()=
    has been called: BUG: KASAN: slab-use-after-free in rtl8150_start_xmit+0x7= 1f/0x760 drivers/net/usb/rtl8150.c:712 Read of size 4 at addr ffff88810eb7a= 930 by task kworker/0:4/5226 The URB completion handler write_bulk_callback=
    () frees the skb via dev_kfree_skb_irq(dev->tx_skb). The URB may complete o=
    n another CPU in softirq context before usb_submit_urb() returns in the sub= mitter, so by the time the submitter reads skb->len the skb has already bee=
    n queued to the per-CPU completion_queue and freed by net_tx_action(): CPU =
    A (xmit) CPU B (USB completion softirq) ------------ ----------------------= -------- dev->tx_skb =3D skb; usb_submit_urb() --+ |-------> write_bulk_cal= lback() | dev_kfree_skb_irq(dev->tx_skb) | net_tx_action() | napi_skb_cache= _put() <-- free netdev->stats.tx_bytes | +=3D skb->len; <-- UAF read Fix it=
    by caching skb->len before submitting the URB and using the cached value w= hen updating the tx_bytes counter. The pre-existing tx_bytes semantics are = preserved: the counter tracks the original frame length (skb->len), not the=
    ETH_ZLEN/USB-alignment padded "count" value that is handed to the device. = Changing that would be a user-visible accounting change and is out of scope=
    for this UAF fix. 2026-06-24 9.8 CVE-2026-52982 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-52982 ] Linux--Linux In the Linux kernel, the following=
    vulnerability has been resolved: netfilter: nf_conntrack_sip: don't use si= mple_strtoul Replace unsafe port parsing in epaddr_len(), ct_sip_parse_head= er_uri(), and ct_sip_parse_request() with a new sip_parse_port() helper tha=
    t validates each digit against the buffer limit, eliminating the use of sim= ple_strtoul() which assumes NUL-terminated strings. The previous code deref= erenced pointers without bounds checks after sip_parse_addr() and relied on=
    simple_strtoul() on non-NUL-terminated skb data. A port that reaches the b= uffer limit without a trailing character is also rejected as malformed. Als=
    o get rid of all simple_strtoul() usage in conntrack, prefer a stricter ver= sion instead. There are intentional changes: - Bail out if number is > UINT= _MAX and indicate a failure, same for too long sequences. While we do accep=
    t 05535 as port 5535, we will not accept e.g. 'sip:10.0.0.1:005060'. While = its syntactically valid under RFC 3261, we should restrict this to not wast=
    e cycles when presented with malformed packets with 64k '0' characters. - F= orce base 10 in ct_sip_parse_numerical_param(). This is used to fetch 'expi= re=3D' and 'rports=3D'; both are expected to use base-10. - In nf_nat_sip.c=
    , only accept the parsed value if its within the 1k-64k range. - epaddr_len=
    now returns 0 if the port is invalid, as it already does for invalid ip ad= dresses. This is intentional. nf_conntrack_sip performs lots of guesswork t=
    o find the right parts of the message to parse. Being stricter could break = existing setups. Connection tracking helpers are designed to allow traffic =
    to pass, not to block it. Based on an earlier patch from Jenny Guanni Qu <q= guanni@gmail.com>. 2026-06-24 9.8 CVE-2026-52986 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-52986 ] Linux--Linux In the Linux kernel, the following=
    vulnerability has been resolved: nvmet-tcp: propagate nvmet_tcp_build_pdu_= iovec() errors to its callers Currently, when nvmet_tcp_build_pdu_iovec() d= etects an out-of-bounds PDU length or offset, it triggers nvmet_tcp_fatal_e= rror(cmd->queue) and returns early. However, because the function returns v= oid, the callers are entirely unaware that a fatal error has occurred and t= hat the cmd->recv_msg.msg_iter was left uninitialized. Callers such as nvme= t_tcp_handle_h2c_data_pdu() proceed to blindly overwrite the queue state wi=
    th queue->rcv_state =3D NVMET_TCP_RECV_DATA Consequently, the socket receiv= ing loop may attempt to read incoming network data into the uninitialized i= terator. Fix this by shifting the error handling responsibility to the call= ers. 2026-06-24 9.8 CVE-2026-52989 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-52989 ] Linux--Linux In the Linux kernel, the following vulnerability=
    has been resolved: tipc: fix double-free in tipc_buf_append() tipc_msg_val= idate() can potentially reallocate the skb it is validating, freeing the ol=
    d one. In tipc_buf_append(), it was being called with a pointer to a local = variable which was a copy of the caller's skb pointer. If the skb was reall= ocated and validation subsequently failed, the error handling path would fr=
    ee the original skb pointer, which had already been freed, leading to doubl= e-free. Fix this by checking if head now points to a newly allocated reasse= mbled skb. If it does, reassign *headbuf for later freeing operations. 2026= -06-24 9.8 CVE-2026-52993 [ https://www.cve.org/CVERecord?id=3DCVE-2026-529=
    93 ] Linux--Linux In the Linux kernel, the following vulnerability has been=
    resolved: netfilter: nfnetlink_osf: fix out-of-bounds read on option match= ing In nf_osf_match(), the nf_osf_hdr_ctx structure is initialized once and=
    passed by reference to nf_osf_match_one() for each fingerprint checked. Du= ring TCP option parsing, nf_osf_match_one() advances the shared ctx->optp p= ointer. If a fingerprint perfectly matches, the function returns early with= out restoring ctx->optp to its initial state. If the user has configured NF= _OSF_LOGLEVEL_ALL, the loop continues to the next fingerprint. However, bec= ause ctx->optp was not restored, the next call to nf_osf_match_one() starts=
    parsing from the end of the options buffer. This causes subsequent matches=
    to read garbage data and fail immediately, making it impossible to log mor=
    e than one match or logging incorrect matches. Instead of using a shared ct= x->optp pointer, pass the context as a constant pointer and use a local poi= nter (optp) for TCP option traversal. This makes nf_osf_match_one() strictl=
    y stateless from the caller's perspective, ensuring every fingerprint check=
    starts at the correct option offset. 2026-06-24 9.1 CVE-2026-52999 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-52999 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: netfilter: conntrack: = remove sprintf usage Replace it with scnprintf, the buffer sizes are expect=
    ed to be large enough to hold the result, no need for snprintf+overflow che= ck. Increase buffer size in mangle_content_len() while at it. BUG: KASAN: s= tack-out-of-bounds in vsnprintf+0xea5/0x1270 Write of size 1 at addr [..] v= snprintf+0xea5/0x1270 sprintf+0xb1/0xe0 mangle_content_len+0x1ac/0x280 nf_n= at_sdp_session+0x1cc/0x240 process_sdp+0x8f8/0xb80 process_invite_request+0= x108/0x2b0 process_sip_msg+0x5da/0xf50 sip_help_tcp+0x45e/0x780 nf_confirm+= 0x34d/0x990 [..] 2026-06-24 9.8 CVE-2026-53002 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-53002 ] Linux--Linux In the Linux kernel, the following v= ulnerability has been resolved: ipv6: fix possible UAF in icmpv6_rcv() Cach= ing saddr and daddr before pskb_pull() is problematic since skb->head can c= hange. Remove these temporary variables: - We only access &ipv6_hdr(skb)->s= addr and &ipv6_hdr(skb)->daddr when net_dbg_ratelimited() is called in the = slow path. - Avoid potential future misuse after pskb_pull() call. 2026-06-=
    24 9.8 CVE-2026-53006 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53006 ]=
    Linux--Linux In the Linux kernel, the following vulnerability has been res= olved: ksmbd: fix use-after-free in smb2_open during durable reconnect In s= mb2_open, the call to ksmbd_put_durable_fd(fp) drops the reference to the d= urable file descriptor early during the durable reconnect process. If an er= ror occurs subsequently (eg, ksmbd_iov_pin_rsp fails) or a scavenger access=
    es the file, it leads to a use-after-free when accessing fp properties (eg = fp->create_time). Move the single put to the end of the function below err_= out2 so fp stays valid until smb2_open returns. 2026-06-24 9.8 CVE-2026-530=
    10 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53010 ] Linux--Linux In th=
    e Linux kernel, the following vulnerability has been resolved: ocfs2/dlm: v= alidate qr_numregions in dlm_match_regions() Patch series "ocfs2/dlm: fix t=
    wo bugs in dlm_match_regions()". In dlm_match_regions(), the qr_numregions = field from a DLM_QUERY_REGION network message is used to drive loops over t=
    he qr_regions buffer without sufficient validation. This series fixes two i= ssues: - Patch 1 adds a bounds check to reject messages where qr_numregions=
    exceeds O2NM_MAX_REGIONS. The o2net layer only validates message byte leng= th; it does not constrain field values, so a crafted message can set qr_num= regions up to 255 and trigger out-of-bounds reads past the 1024-byte qr_reg= ions buffer. - Patch 2 fixes an off-by-one in the local-vs-remote compariso=
    n loop, which uses '<=3D' instead of '<', reading one entry past the valid = range even when qr_numregions is within bounds. This patch (of 2): The qr_n= umregions field from a DLM_QUERY_REGION network message is used directly as=
    loop bounds in dlm_match_regions() without checking against O2NM_MAX_REGIO= NS. Since qr_regions is sized for at most O2NM_MAX_REGIONS (32) entries, a = crafted message with qr_numregions > 32 causes out-of-bounds reads past the=
    qr_regions buffer. Add a bounds check for qr_numregions before entering th=
    e loops. 2026-06-24 9.1 CVE-2026-53043 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53043 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: memory: tegra124-emc: Fix dll_change check The co=
    de checking whether the specified memory timing enables DLL in the EMRS reg= ister was reversed. DLL is enabled if bit A0 is low. Fix the check. 2026-06= -24 9.8 CVE-2026-53045 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53045 =
    ] Linux--Linux In the Linux kernel, the following vulnerability has been re= solved: ksmbd: fix use-after-free from async crypto on Qualcomm crypto engi=
    ne ksmbd_crypt_message() sets a NULL completion callback on AEAD requests a=
    nd does not handle the -EINPROGRESS return code from async hardware crypto = engines like the Qualcomm Crypto Engine (QCE). When QCE returns -EINPROGRES=
    S, ksmbd treats it as an error and immediately frees the request while the = hardware DMA operation is still in flight. The DMA completion callback then=
    dereferences freed memory, causing a NULL pointer crash: pc : qce_skcipher= _done+0x24/0x174 lr : vchan_complete+0x230/0x27c ... el1h_64_irq+0x68/0x6c = ksmbd_free_work_struct+0x20/0x118 [ksmbd] ksmbd_exit_file_cache+0x694/0xa4c=
    [ksmbd] Use the standard crypto_wait_req() pattern with crypto_req_done() =
    as the completion callback, matching the approach used by the SMB client in=
    fs/smb/client/smb2ops.c. This properly handles both synchronous engines (i= mmediate return) and async engines (-EINPROGRESS followed by callback notif= ication). 2026-06-24 9.8 CVE-2026-53046 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53046 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: gfs2: add some missing log locking Function gfs2_= logd() calls the log flushing functions gfs2_ail1_start(), gfs2_ail1_wait()=
    , and gfs2_ail1_empty() without holding sdp->sd_log_flush_lock, but these f= unctions require exclusion against concurrent transactions. To fix that, ad=
    d a non-locking __gfs2_log_flush() function. Then, in gfs2_logd(), take sdp= ->sd_log_flush_lock before calling the above mentioned log flushing functio=
    ns and __gfs2_log_flush(). 2026-06-24 9.8 CVE-2026-53049 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-53049 ] Linux--Linux In the Linux kernel, the f= ollowing vulnerability has been resolved: crypto: hisilicon/sec2 - prevent = req used-after-free for sec During packet transmission, if the system is un= der heavy load, the hardware might complete processing the packet and free = the request memory (req) before the transmission function finishes. If the = software subsequently accesses this req, a use-after-free error will occur.=
    The qp_ctx memory exists throughout the packet sending process, so replace=
    the req with the qp_ctx. 2026-06-24 9.8 CVE-2026-53055 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-53055 ] Linux--Linux In the Linux kernel, the fo= llowing vulnerability has been resolved: net: bcmgenet: fix racing timeout = handler The bcmgenet_timeout handler tries to take down all tx queues when =
    a single queue times out. This is over zealous and causes many race conditi= ons with queues that are still chugging along. Instead lets only restart th=
    e timed out queue. 2026-06-24 9.8 CVE-2026-53086 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-53086 ] Linux--Linux In the Linux kernel, the following=
    vulnerability has been resolved: net: bcmgenet: fix off-by-one in bcmgenet= _put_txcb The write_ptr points to the next open tx_cb. We want to return th=
    e tx_cb that gets rewinded, so we must rewind the pointer first then return=
    the tx_cb that it points to. That way the txcb can be correctly cleaned up=
    . 2026-06-24 9.8 CVE-2026-53088 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-53088 ] Linux--Linux In the Linux kernel, the following vulnerability ha=
    s been resolved: netfilter: require Ethernet MAC header before using eth_hd= r() `ip6t_eui64`, `xt_mac`, the `bitmap:ip,mac`, `hash:ip,mac`, and `hash:m= ac` ipset types, and `nf_log_syslog` access `eth_hdr(skb)` after either ass= uming that the skb is associated with an Ethernet device or checking only t= hat the `ETH_HLEN` bytes at `skb_mac_header(skb)` lie between `skb->head` a=
    nd `skb->data`. Make these paths first verify that the skb is associated wi=
    th an Ethernet device, that the MAC header was set, and that it spans at le= ast a full Ethernet header before accessing `eth_hdr(skb)`. 2026-06-25 9.4 = CVE-2026-53131 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53131 ] Linux-= -Linux In the Linux kernel, the following vulnerability has been resolved: = rxrpc: Fix the ACK parser to extract the SACK table for parsing Fix modific= ation of the received skbuff in rxrpc_input_soft_acks() and a potential inc= orrect access of the buffer in a fragmented UDP packet (the packet would pr= obably have to be deliberately pre-generated as fragmented) when AF_RXRPC t= ries to extract the contents of the SACK table by copying out the contents =
    of the SACK table into a buffer before attempting to parse AF_RXRPC assumes=
    that it can just call skb_condense() and then validly access the SACK tabl=
    e from skb->data and that it will be a flat buffer - but skb_condense() can=
    silently fail to do anything under some circumstances. Note that whilst rx= rpc_input_soft_acks() should be able to parse extended ACKs, the rest of AF= _RXRPC doesn't currently support that. Further, there's then no need to cal=
    l skb_condense() in rxrpc_input_ack(), so don't. 2026-06-25 9.8 CVE-2026-53= 151 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53151 ] Linux--Linux In t=
    he Linux kernel, the following vulnerability has been resolved: inet: frags=
    : fix use-after-free caused by the fqdir_pre_exit() flush On netns teardown=
    , fqdir_pre_exit() walks the fqdir rhashtable and flushes every fragment qu= eue that is not yet complete using inet_frag_queue_flush(). That helper fre=
    es all the skbs queued on the fragment queue but does not set INET_FRAG_COM= PLETE, and leaves q->fragments_tail and q->last_run_head pointing at the fr= eed skbs. The queue itself stays in the rhashtable. fqdir_pre_exit() first = lowers high_thresh to 0 to stop new queue lookups, but it cannot stop a fra= gment that already obtained the queue through inet_frag_find() earlier and = stalled just before taking the queue lock. Once that fragment resumes after=
    the flush and takes the queue lock, it passes the INET_FRAG_COMPLETE check=
    and then dereferences the freed fragments_tail. inet_frag_queue_insert() r= eads FRAG_CB() and ->len of that pointer and, on the append path, writes ->= next_frag, causing a slab use-after-free. IPv6, nf_conntrack_reasm6 and 6lo= wpan reassembly share the same flush path and are affected as well. Reset r= b_fragments, fragments_tail and last_run_head in inet_frag_queue_flush() so=
    a flushed queue no longer points at the freed skbs. A fragment that resume=
    s after the flush and takes the queue lock then finds an empty queue and st= arts a new run instead of dereferencing the freed fragments_tail. ip_frag_r= einit() already performed this reset after its own flush, so drop the now d= uplicate code there. 2026-06-25 9.8 CVE-2026-53175 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-53175 ] Linux--Linux In the Linux kernel, the followi=
    ng vulnerability has been resolved: IB/isert: Reject login PDUs shorter tha=
    n ISER_HEADERS_LEN In drivers/infiniband/ulp/isert/ib_isert.c, isert_login_= recv_done() computes the login request payload length as wc->byte_len minus=
    ISER_HEADERS_LEN with no lower bound, and login_req_len is a signed int. A=
    remote iSER initiator can post a login Send work request carrying fewer th=
    an ISER_HEADERS_LEN (76) bytes, so the subtraction underflows and login_req= _len becomes negative. isert_rx_login_req() then reads that negative length=
    back into a signed int, takes size =3D min(rx_buflen, MAX_KEY_VALUE_PAIRS)=
    , and because the min() is signed it keeps the negative value; the value is=
    then passed as the memcpy() length and sign-extended to a multi-gigabyte s= ize_t. The copy into the 8192-byte login->req_buf runs far out of bounds an=
    d faults, crashing the target node. The login phase precedes iSCSI authenti= cation, so no credentials are required to reach this path. Reject any login=
    PDU shorter than ISER_HEADERS_LEN before the subtraction, mirroring the ex= isting early return on a failed work completion, so login_req_len can never=
    go negative. The upper bound was already safe: a posted login buffer canno=
    t deliver more than ISER_RX_PAYLOAD_SIZE, so the difference stays at or bel=
    ow MAX_KEY_VALUE_PAIRS and the existing min() clamps it; only the missing l= ower bound needs to be added. 2026-06-25 9.8 CVE-2026-53176 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-53176 ] Linux--Linux In the Linux kernel, th=
    e following vulnerability has been resolved: RDMA/srp: bound SRP_RSP sense = copy by the received length srp_process_rsp() copies sense data from rsp->d= ata + resp_data_len, where resp_data_len is the full 32-bit value supplied =
    by the SRP target and is never checked against the number of bytes actually=
    received (wc->byte_len). The copy length is bounded to SCSI_SENSE_BUFFERSI= ZE, so at most 96 bytes are copied, but the source offset is not bounded. A=
    malicious or compromised SRP target on the InfiniBand/RoCE fabric that the=
    initiator has logged into can return an SRP_RSP with SRP_RSP_FLAG_SNSVALID=
    set and a large resp_data_len. The receive buffer is allocated at the targ= et-chosen max_ti_iu_len, so the source of the sense copy lands past the byt=
    es actually received; with resp_data_len near 0xFFFFFFFF it is gigabytes pa=
    st the buffer and the read faults. Copy the sense data only if it has not b= een truncated, that is, only if the response header, the response data, and=
    the sense region fit within the bytes actually received; otherwise drop th=
    e sense and log. The in-tree iSER and NVMe-RDMA receive paths already bound=
    their parse by wc->byte_len; this brings ib_srp into line with them. 2026-= 06-25 9.1 CVE-2026-53186 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5318=
    6 ] Linux--Linux In the Linux kernel, the following vulnerability has been = resolved: net: mvpp2: refill RX buffers before XDP or skb use The RX error = path returns the current descriptor buffer to the hardware BM pool. That is=
    only valid while the driver still owns the buffer. mvpp2_rx_refill() can f= ail after the current buffer has been handed to XDP or attached to an skb. =
    In those cases mvpp2_run_xdp() may have recycled, redirected, or queued the=
    page for XDP_TX, and an skb free also retires the data buffer. Returning s= uch a buffer to BM lets hardware DMA into memory that is no longer owned by=
    the RX ring. Refill the BM pool before handing the current buffer to XDP o=
    r to the skb. If the allocation fails there, drop the packet and return the=
    still-owned current buffer to BM, preserving the pool depth. Once the refi=
    ll succeeds, later local drops retire/free the current buffer instead of re= turning it to BM. 2026-06-25 9.8 CVE-2026-53215 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-53215 ] Linux--Linux In the Linux kernel, the following = vulnerability has been resolved: net: mvpp2: limit XDP frame size to the RX=
    buffer mvpp2 has short and long BM pools, and short pool buffers can be sm= aller than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff = with PAGE_SIZE as frame size. XDP helpers use frame_sz to validate tail gro= wth and to derive the hard end of the data area. Advertising PAGE_SIZE for = short buffers can let bpf_xdp_adjust_tail() grow a packet past the real all= ocation, corrupting memory or later tripping skb tailroom checks. Initializ=
    e the XDP buffer with bm_pool->frag_size so XDP tailroom matches the actual=
    buffer backing the packet. 2026-06-25 9.8 CVE-2026-53216 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-53216 ] Linux--Linux In the Linux kernel, the = following vulnerability has been resolved: ip6_vti: fix incorrect tunnel ma= tching in vti6_tnl_lookup() In vti6_tnl_lookup(), when an exact match for a=
    tunnel fails, the code falls back to searching for wildcard tunnels: - Tun= nels matching the packet's local address, with any remote address wildcard = remote). - Tunnels matching the packet's remote address, with any local add= ress (wildcard local). However, vti6 stores all these different types of tu= nnels in the same hash table (ip6n->tnls_r_l) prone to hash collisions. The=
    bug is that the fallback search loops in vti6_tnl_lookup() were missing ch= ecks to ensure that the candidate tunnel actually has a wildcard address. 2= 026-06-25 9.8 CVE-2026-53221 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 53221 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: sctp: validate embedded INIT chunk and address list lengths i=
    n cookie sctp_unpack_cookie() only checked that the embedded INIT chunk len= gth did not exceed the remaining cookie payload, but did not ensure that th=
    e INIT chunk is large enough to contain a complete INIT header. A malformed=
    COOKIE_ECHO can therefore carry a truncated INIT chunk whose length field =
    is smaller than sizeof(struct sctp_init_chunk). Later, sctp_process_init() = accesses INIT parameters unconditionally, which may lead to out-of-bounds r= eads. In addition, raw_addr_list_len is not fully validated against the rem= aining cookie payload. When cookie authentication is disabled, an attacker = can supply an oversized raw_addr_list_len and cause sctp_raw_to_bind_addrs(=
    ) to read beyond the end of the cookie. The address parser also lacks suffi= cient bounds checks for parameter headers and lengths, allowing malformed a= ddress parameters to trigger out-of-bounds reads. Fix this by: - requiring = the embedded INIT chunk length to be at least sizeof(struct sctp_init_chunk=
    ); - validating that the INIT chunk and raw address list together fit withi=
    n the cookie payload; - verifying sufficient data exists for each address p= arameter header and payload before parsing it. Note that sctp_verify_init()=
    must be called after sctp_unpack_cookie() and before sctp_process_init() w= hen cookie authentication is disabled. This will be addressed in a separate=
    patch. 2026-06-25 9.1 CVE-2026-53224 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-53224 ] Linux--Linux In the Linux kernel, the following vulnerabil= ity has been resolved: sctp: fix uninit-value in __sctp_rcv_asconf_lookup()=
    __sctp_rcv_asconf_lookup() in net/sctp/input.c only checks that the ASCONF=
    chunk can hold the ADDIP header and a parameter header, then calls af->fro= m_addr_param(), which reads the full address (16 bytes for IPv6) trusting t=
    he parameter's declared length. An unauthenticated peer can send a truncate=
    d trailing ASCONF chunk that declares an IPv6 address parameter but stops a= fter the 4-byte parameter header; reached from the no-association lookup pa= th, from_addr_param() then reads uninitialized bytes past the parameter. Im= pact: an unauthenticated SCTP peer makes the receive path read up to 16 byt=
    es of uninitialized memory past a truncated ASCONF address parameter. The s= ibling __sctp_rcv_init_lookup() bounds parameters with sctp_walk_params(); = this path open-codes the fetch and omits the bound. Verify the whole addres=
    s parameter lies within the chunk before from_addr_param() reads it, the sa=
    me class of fix as commit 51e5ad549c43 ("net: sctp: fix KMSAN uninit-value =
    in sctp_inq_pop"). 2026-06-25 9.1 CVE-2026-53225 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-53225 ] Linux--Linux In the Linux kernel, the following=
    vulnerability has been resolved: ipv6: sit: reload inner IPv6 header after=
    GSO offloads ipip6_tunnel_xmit() caches the inner IPv6 header pointer at f= unction entry and continues using it after iptunnel_handle_offloads(). For = GSO skbs, iptunnel_handle_offloads() calls skb_header_unclone(). When the s=
    kb header is cloned, skb_header_unclone() can call pskb_expand_head(), whic=
    h may move the skb head. The pskb_expand_head() contract requires pointers = into the skb header to be reloaded after the call. If the later skb_realloc= _headroom() branch is not taken, SIT uses the stale iph6 pointer to read th=
    e inner hop limit and DS field. That can read from a freed skb head after t=
    he old head's remaining clone is released. Reload iph6 after the offload he= lper succeeds and before subsequent reads from the inner IPv6 header. Keep = the existing reload after skb_realloc_headroom(), since that branch can als=
    o replace the skb. 2026-06-25 9.8 CVE-2026-53228 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-53228 ] Linux--Linux In the Linux kernel, the following=
    vulnerability has been resolved: sctp: validate cached peer INIT chunk len= gth in COOKIE_ECHO processing When a listening SCTP server processes a COOK= IE_ECHO chunk, the cached peer INIT chunk embedded after the cookie is pars=
    ed and its parameters are later walked by sctp_process_init() using sctp_wa= lk_params(). However, the chunk header length of this cached INIT chunk was=
    not validated against the remaining buffer in the COOKIE_ECHO payload. If = the length field is inflated, the parameter walk can run beyond the actual = received data, leading to out-of-bounds reads and potential memory corrupti=
    on during later parameter handling (e.g. STATE_COOKIE processing and kmemdu= p() copies). Add a bounds check in sctp_unpack_cookie() to ensure the cache=
    d INIT chunk length does not exceed the available data in the COOKIE_ECHO b= uffer before it is used. 2026-06-25 9.8 CVE-2026-53246 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-53246 ] Linux--Linux In the Linux kernel, the fol= lowing vulnerability has been resolved: net: ethernet: mtk_eth_soc: Fix use= -after-free in metadata dst teardown mtk_free_dev() calls metadata_dst_free=
    () which frees the metadata_dst with kfree() immediately, bypassing the RCU=
    grace period. In the RX path, skb_dst_set_noref() sets a non-refcounted po= inter from the skb to the metadata_dst. This function requires RCU read-sid=
    e protection and the dst must remain valid until all RCU readers complete. = Since metadata_dst_free() calls kfree() directly, a use-after-free can occu=
    r if any skb still holds a noref pointer to the dst when the driver tears i=
    t down. Replace metadata_dst_free() with dst_release() which properly goes = through the refcount path: when the refcount drops to zero, it schedules th=
    e actual free via call_rcu_hurry(), ensuring all RCU readers have completed=
    before the memory is freed. 2026-06-25 9.8 CVE-2026-53247 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-53247 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: tcp: Add preempt_{disable,enabl= e}_nested() in reqsk_queue_hash_req(). syzbot reported a weird reqsk->rsk_r= efcnt underflow in __inet_csk_reqsk_queue_drop(). The captured reqsk_put() =
    in __inet_csk_reqsk_queue_drop() is called only when it successfully remove=
    s reqsk from ehash. Moreover, reqsk_timer_handler() calls another reqsk_put=
    () after that. This indicates that the reqsk was missing both refcnts for e= hash and the timer itself. Since all the syzbot reports had PREEMPT_RT enab= led, the only possible scenario is that reqsk_queue_hash_req() is preempted=
    after mod_timer() and before refcount_set(), and then the timer triggered = after 1s aborts the reqsk due to its listener's close(). Let's wrap mod_tim= er() and refcount_set() with preempt_disable_nested() and preempt_enable_ne= sted(). Note that inet_ehash_insert() holds the normal spin_lock() (mutex i=
    n PREEMPT_RT), so it must be called outside of preempt_disable_nested(), bu=
    t this is fine. The lookup path just ignores 0 sk_refcnt entries in ehash a=
    nd tries to create another reqsk, but this will fail at inet_ehash_insert()=
    . [0]: refcount_t: underflow; use-after-free. WARNING: lib/refcount.c:28 at=
    refcount_warn_saturate+0xb2/0x110 lib/refcount.c:28, CPU#0: ktimers/0/16 M= odules linked in: CPU: 0 UID: 0 PID: 16 Comm: ktimers/0 Tainted: G L syzkal= ler #0 PREEMPT_{RT,(full)} Tainted: [L]=3DSOFTLOCKUP Hardware name: Google = Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 00= 10:refcount_warn_saturate+0xb2/0x110 lib/refcount.c:28 Code: e4 7d d1 0a 67=
    48 0f b9 3a eb 4a e8 38 3d 23 fd 48 8d 3d e1 7d d1 0a 67 48 0f b9 3a eb 37=
    e8 25 3d 23 fd 48 8d 3d de 7d d1 0a <67> 48 0f b9 3a eb 24 e8 12 3d 23 fd =
    48 8d 3d db 7d d1 0a 67 48 0f RSP: 0000:ffffc90000157948 EFLAGS: 00010246 R= AX: ffffffff84a1301b RBX: 0000000000000003 RCX: ffff88801ca98000 RDX: 00000= 00000000100 RSI: 0000000000000000 RDI: ffffffff8f72ae00 RBP: ffffffff99ae3b=
    01 R08: ffff88801ca98000 R09: 0000000000000005 R10: 0000000000000100 R11: 0= 000000000000004 R12: ffff8880425ef568 R13: ffff8880425ef4f8 R14: ffff888042= 5ef578 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff888126386000= (0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050= 033 CR2: 00007f7b46710e9c CR3: 000000000dbb6000 CR4: 00000000003526f0 Call = Trace: <TASK> __refcount_sub_and_test include/linux/refcount.h:400 [inline]=
    __refcount_dec_and_test include/linux/refcount.h:432 [inline] refcount_dec= _and_test include/linux/refcount.h:450 [inline] reqsk_put include/net/reque= st_sock.h:136 [inline] __inet_csk_reqsk_queue_drop+0x3ce/0x440 net/ipv4/ine= t_connection_sock.c:1007 reqsk_timer_handler+0x651/0xdf0 net/ipv4/inet_conn= ection_sock.c:1137 call_timer_fn+0x192/0x5e0 kernel/time/timer.c:1748 expir= e_timers kernel/time/timer.c:1799 [inline] __run_timers kernel/time/timer.c= :2374 [inline] __run_timer_base+0x6a3/0x9f0 kernel/time/timer.c:2386 run_ti= mer_base kernel/time/timer.c:2395 [inline] run_timer_softirq+0x67/0x170 ker= nel/time/timer.c:2403 handle_softirqs+0x1de/0x6d0 kernel/softirq.c:622 __do= _softirq kernel/softirq.c:656 [inline] run_ktimerd+0x69/0x100 kernel/softir= q.c:1151 smpboot_thread_fn+0x541/0xa50 kernel/smpboot.c:160 kthread+0x388/0= x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process= .c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> 20= 26-06-25 9.8 CVE-2026-53260 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 3260 ] Linux--Linux In the Linux kernel, the following vulnerability has be=
    en resolved: ocfs2/dlm: fix off-by-one in dlm_match_regions() region compar= ison The local-vs-remote region comparison loop uses '<=3D' instead of '<',=
    causing it to read one entry past the valid range of qr_regions. The other=
    loops in the same function correctly use '<'. Fix the loop condition to us=
    e '<' for consistency and correctness. 2026-06-26 9.8 CVE-2026-53309 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-53309 ] Linux--Linux In the Linux k= ernel, the following vulnerability has been resolved: Bluetooth: serialize = accept_q access bt_sock_poll() walks the accept queue without synchronizati= on, while child teardown can unlink the same socket and drop its last refer= ence. The unsynchronized accept queue walk has existed since the initial Bl= uetooth import. Protect accept_q with a dedicated lock for queue updates an=
    d polling. Also rework bt_accept_dequeue() to take temporary child referenc=
    es under the queue lock before dropping it and locking the child socket. 20= 26-06-24 8.8 CVE-2026-52918 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 2918 ] Linux--Linux In the Linux kernel, the following vulnerability has be=
    en resolved: netfilter: xt_policy: fix strict mode inbound policy matching = match_policy_in() walks sec_path entries from the last transform to the fir=
    st one, but strict policy matching needs to consume info->pol[] in the same=
    forward order as the rule layout. Derive the strict-match policy position = from the number of transforms already consumed so that multi-element inboun=
    d rules are matched consistently. 2026-06-24 8.3 CVE-2026-52920 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-52920 ] Linux--Linux In the Linux kernel=
    , the following vulnerability has been resolved: batman-adv: tvlv: reject o= versized TVLV packets batadv_tvlv_container_ogm_append() builds a TVLV pack=
    et section from the tvlv.container_list. The total size of this section is = computed by batadv_tvlv_container_list_size(), which sums the sizes of all = registered containers. The return type and accumulator in batadv_tvlv_conta= iner_list_size() were u16. If the accumulated size exceeds U16_MAX, the val=
    ue wraps around, causing the subsequent allocation in batadv_tvlv_container= _ogm_append() to be undersized. The memcpy-style copy that follows would th=
    en write beyond the end of the allocated buffer, corrupting kernel memory. = Fix this by widening the return type of batadv_tvlv_container_list_size() t=
    o size_t. In batadv_tvlv_container_ogm_append(), check the computed length = against U16_MAX before proceeding, and bail out as if the allocation had fa= iled when the limit is exceeded. 2026-06-24 8.8 CVE-2026-52934 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-52934 ] Linux--Linux In the Linux kernel,=
    the following vulnerability has been resolved: iommu: Fix WARN_ON in __iom= mu_group_set_domain_nofail() due to reset In __iommu_group_set_domain_inter= nal(), concurrent domain attachments are rejected when any device in the gr= oup is recovering. This is necessary to fence concurrent attachments to a m= ulti-device group where devices might share the same RID due to PCI DMA ali=
    as quirks, but triggers the WARN_ON in __iommu_group_set_domain_nofail(). O= ther IOMMU_SET_DOMAIN_MUST_SUCCEED callers in detach/teardown paths, such a=
    s __iommu_group_set_core_domain and __iommu_release_dma_ownership, should n=
    ot be rejected, as the domain would be freed anyway in these nofail paths w= hile group->domain is still pointing to it. So pci_dev_reset_iommu_done() c= ould trigger a UAF when re-attaching group->domain. Honor the IOMMU_SET_DOM= AIN_MUST_SUCCEED flag, allowing the callers through the group->recovery_cnt=
    fence, so as to update the group->domain pointer. Instead add a gdev->bloc= ked check in the device iteration loop, to prevent any concurrent per-devic=
    e detachment. 2026-06-24 8.8 CVE-2026-52952 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-52952 ] Linux--Linux In the Linux kernel, the following vuln= erability has been resolved: smb/client: fix possible infinite loop and oob=
    read in symlink_data() On 32-bit architectures, the infinite loop is as fo= llows: len =3D p->ErrorDataLength =3D=3D 0xfffffff8 u8 *next =3D p->ErrorCo= ntextData + len next =3D=3D p On 32-bit architectures, the out-of-bounds re=
    ad is as follows: len =3D p->ErrorDataLength =3D=3D 0xfffffff0 u8 *next =3D=
    ErrorContextData + len next =3D=3D (u8 *)p - 8 2026-06-24 8.1 CVE-2026-= 52967 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52967 ] Linux--Linux In=
    the Linux kernel, the following vulnerability has been resolved: iommu/amd=
    : Fix clone_alias() to use the original device's devid Currently clone_alia= s() assumes first argument (pdev) is always the original device pointer. Th=
    is function is called by pci_for_each_dma_alias() which based on topology d= ecides to send original or alias device details in first argument. This mea=
    nt that the source devid used to look up and copy the DTE may be incorrect,=
    leading to wrong or stale DTE entries being propagated to alias device. Fi=
    x this by passing the original pdev as the opaque data argument to both the=
    direct clone_alias() call and pci_for_each_dma_alias(). Inside clone_alias= (), retrieve the original device from data and compute devid from it. 2026-= 06-24 8.8 CVE-2026-53053 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5305=
    3 ] Linux--Linux In the Linux kernel, the following vulnerability has been = resolved: iommu/riscv: Add IOTINVAL after updating DDT/PDT entries Add risc= v_iommu_iodir_iotinval() to perform required TLB and context cache invalida= tions after updating DDT or PDT entries, as mandated by the RISC-V IOMMU sp= ecification (Section 6.3.1 and 6.3.2). 2026-06-24 8.8 CVE-2026-53057 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-53057 ] Linux--Linux In the Linux k= ernel, the following vulnerability has been resolved: Bluetooth: l2cap: Add=
    missing chan lock in l2cap_ecred_reconf_rsp l2cap_ecred_reconf_rsp() calls=
    l2cap_chan_del() without holding l2cap_chan_lock(). Every other l2cap_chan= _del() caller in the file acquires the lock first. A remote BLE device can = send a crafted L2CAP ECRED reconfiguration response to corrupt the channel = list while another thread is iterating it. Add l2cap_chan_hold() and l2cap_= chan_lock() before l2cap_chan_del(), and l2cap_chan_unlock() and l2cap_chan= _put() after, matching the pattern used in l2cap_ecred_conn_rsp() and l2cap= _conn_del(). 2026-06-24 8.8 CVE-2026-53071 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-53071 ] Linux--Linux In the Linux kernel, the following vulne= rability has been resolved: Bluetooth: fix locking in hci_conn_request_evt(=
    ) with HCI_PROTO_DEFER When protocol sets HCI_PROTO_DEFER, hci_conn_request= _evt() calls hci_connect_cfm(conn) without hdev->lock. Generally hci_connec= t_cfm() assumes it is held, and if conn is deleted concurrently -> UAF. Onl=
    y SCO and ISO set HCI_PROTO_DEFER and only for defer setup listen, and HCI_= EV_CONN_REQUEST is not generated for ISO. In the non-deferred listening soc= ket code paths, hci_connect_cfm(conn) is called with hdev->lock held. Fix b=
    y holding the lock. 2026-06-24 8.8 CVE-2026-53072 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-53072 ] Linux--Linux In the Linux kernel, the followin=
    g vulnerability has been resolved: ppp: require CAP_NET_ADMIN in target net=
    ns for unattached ioctls /dev/ppp open is currently authorized against file= ->f_cred->user_ns, while unattached administrative ioctls operate on curren= t->nsproxy->net_ns. As a result, a local unprivileged user can create a new=
    user namespace with CLONE_NEWUSER, gain CAP_NET_ADMIN only in that new use=
    r namespace, and still issue PPPIOCNEWUNIT, PPPIOCATTACH, or PPPIOCATTCHAN = against an inherited network namespace. Require CAP_NET_ADMIN in the user n= amespace that owns the target network namespace before handling unattached = PPP administrative ioctls. This preserves normal pppd operation in the netw= ork namespace it is actually privileged in, while rejecting the userns-only=
    inherited-netns case. 2026-06-24 8.8 CVE-2026-53075 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-53075 ] Linux--Linux In the Linux kernel, the follo= wing vulnerability has been resolved: net: pull headers in qdisc_pkt_len_se= gs_init() Most ndo_start_xmit() methods expects headers of gso packets to b=
    e already in skb->head. net/core/tso.c users are particularly at risk, beca= use tso_build_hdr() does a memcpy(hdr, skb->data, hdr_len); qdisc_pkt_len_s= egs_init() already does a dissection of gso packets. Use pskb_may_pull() in= stead of skb_header_pointer() to make sure drivers do not have to reimpleme=
    nt this. Some malicious packets could be fed, detect them so that we can dr=
    op them sooner with a new SKB_DROP_REASON_SKB_BAD_GSO drop_reason. 2026-06-=
    24 8.4 CVE-2026-53091 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53091 ]=
    Linux--Linux In the Linux kernel, the following vulnerability has been res= olved: thunderbolt: Validate XDomain request packet size before type cast t= b_xdp_handle_request() casts the received packet buffer to protocol-specifi=
    c structs without verifying that the allocation is large enough for the tar= get type. A peer can send a minimal XDomain packet that passes the generic = header length check but is shorter than the struct accessed after the cast,=
    causing out-of- bounds reads from the kmemdup allocation. Plumb the packet=
    length through xdomain_request_work and validate it against the expected s= truct size before each cast. 2026-06-25 8.1 CVE-2026-53147 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-53147 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: accel/ethosu: reject DMA comman=
    ds with uninitialized length cmd_state_init() initializes the command state=
    with memset(0xff), leaving dma->len at U64_MAX to signal missing setup. Th=
    e only setter is NPU_SET_DMA0_LEN; if userspace omits this command and issu=
    es NPU_OP_DMA_START, dma->len remains U64_MAX. In dma_length(), a positive = stride added to U64_MAX wraps to a small value. With size0 =3D=3D 1, check_= mul_overflow() does not trigger and dma_length() returns 0 instead of U64_M= AX. The caller's U64_MAX check then passes, region_size[] stays 0, and the = bounds check in ethosu_job.c is bypassed, allowing hardware to execute DMA = with stale physical addresses. Fix by checking for U64_MAX at the start of = dma_length() before any arithmetic, consistent with the sentinel value used=
    throughout the driver to detect uninitialized fields. 2026-06-25 8.8 CVE-2= 026-53170 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53170 ] Linux--Linu=
    x In the Linux kernel, the following vulnerability has been resolved: accel= /ethosu: fix arithmetic issues in dma_length() dma_length() derives DMA reg= ion usage from command stream values and updates region_size[]: len =3D ((l=
    en + stride[0]) * size0 + stride[1]) * size1 region_size[region] =3D max(..=
    ., len + dma->offset) Several arithmetic issues can corrupt the derived reg= ion size: - signed stride values may underflow when added to len - intermed= iate multiplications may overflow - len + dma->offset may overflow during r= egion_size updates - dma_length() error returns were not validated by the c= aller region_size[] is later used by ethosu_job.c to validate command strea=
    m accesses against GEM buffer sizes. Arithmetic wraparound can therefore un= der-report region usage and bypass the bounds validation. Fix by validating=
    signed additions, using overflow helpers for multiplications and offset up= dates, and propagating dma_length() failures to the caller. 2026-06-25 8.8 = CVE-2026-53171 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53171 ] Linux-= -Linux In the Linux kernel, the following vulnerability has been resolved: = staging: rtl8723bs: rtw_mlme: add bounds checks before ie_length subtractio=
    n Add guards to ensure ie_length is large enough before subtracting fixed I=
    E offsets to prevent unsigned integer underflow. 2026-06-25 8.1 CVE-2026-53= 178 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53178 ] Linux--Linux In t=
    he Linux kernel, the following vulnerability has been resolved: RDMA/core: = Validate the passed in fops for ib_get_ucaps() Sashiko pointed out it is no=
    t safe to rely only on the devt because char/block alias so if the user fin=
    ds a block device with the same dev_t it can masquerade as a ucap cdev fd. = Test the f_ops to only accept authentic cdevs. 2026-06-25 8.8 CVE-2026-5318=
    8 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53188 ] Linux--Linux In the=
    Linux kernel, the following vulnerability has been resolved: ksmbd: fix us= e-after-free of a deferred file_lock on double SMB2_CANCEL A deferred byte-= range lock (an SMB2_LOCK that blocks) registers an async work on conn->asyn= c_requests via setup_async_work(), with cancel_fn =3D smb2_remove_blocked_l= ock and cancel_argv[0] pointing at the struct file_lock. When the request i=
    s cancelled, the worker frees the file_lock with locks_free_lock() and take=
    s the cancelled early-exit, which "goto out"s and never reaches release_asy= nc_work() -- the only site that unlinks the work from conn->async_requests = and clears cancel_fn/cancel_argv. The work therefore stays matchable on asy= nc_requests with a live cancel_fn pointing at the freed file_lock, until co= nnection teardown finally runs release_async_work(). smb2_cancel() fires ca= ncel_fn unconditionally with no state guard, so a second SMB2_CANCEL for th=
    e same AsyncId, arriving in that window, re-runs smb2_remove_blocked_lock()=
    on the freed file_lock -- a slab use-after-free: BUG: KASAN: slab-use-afte= r-free in __locks_delete_block __locks_delete_block locks_delete_block ksmb= d_vfs_posix_lock_unblock smb2_remove_blocked_lock smb2_cancel <- 2nd SMB2_C= ANCEL fires cancel_fn handle_ksmbd_work Allocated by ...: locks_alloc_lock =
    <- smb2_lock Freed by ...: locks_free_lock <- smb2_lock (cancelled branch) = ... cache file_lock_cache of size 192 Reproduced on mainline with KASAN by =
    an authenticated SMB client. Skip a work whose state is already KSMBD_WORK_= CANCELLED so its cancel callback cannot be fired a second time. 2026-06-25 = 8.8 CVE-2026-53198 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53198 ] Li= nux--Linux In the Linux kernel, the following vulnerability has been resolv= ed: KVM: arm64: nv: Fix handling of XN[0] when !FEAT_XNX XN has already bee=
    n extracted from its bitfield position so using FIELD_PREP() on the mask th=
    at clears XN[0] is completely broken, having the effect of unconditionally = granting execute permissions... Fix the obvious mistake by manipulating the=
    right bit. 2026-06-25 8.8 CVE-2026-53200 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-53200 ] Linux--Linux In the Linux kernel, the following vulner= ability has been resolved: net: mvpp2: sync RX data at the hardware packet = offset mvpp2 programs the RX queue packet offset, so hardware writes receiv=
    ed data at dma_addr + MVPP2_SKB_HEADROOM. The current CPU sync starts at dm= a_addr and only covers rx_bytes + MVPP2_MH_SIZE bytes, which syncs the unus=
    ed headroom and misses the same number of bytes at the packet tail. On non-= coherent DMA systems this can leave the CPU reading stale cache contents fo=
    r the end of the received frame. Use dma_sync_single_range_for_cpu() with M= VPP2_SKB_HEADROOM as the range offset so the sync covers the Marvell header=
    and packet data actually written by hardware. 2026-06-25 8.6 CVE-2026-5321=
    7 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53217 ] Linux--Linux In the=
    Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix=
    slab-out-of-bounds in mlx5_query_nic_vport_mac_list mlx5_query_nic_vport_m= ac_list() sizes its firmware command buffer using the PF's log_max_current_= uc/mc_list capabilities. When querying a VF vport with a larger configured = max (via devlink), the firmware response can overflow this buffer: BUG: KAS= AN: slab-out-of-bounds in mlx5_query_nic_vport_mac_list+0x453/0x4c0 [mlx5_c= ore] Read of size 4 at addr ff1100013ffc8a12 by task kworker/u96:2/385 CPU:=
    12 UID: 0 PID: 385 Comm: kworker/u96:2 Not tainted 7.0.0-rc6+ #1 PREEMPT H= ardware name: QEMU Standard PC (Q35 + ICH9, 2009) Workqueue: mlx5_esw_wq es= w_vport_change_handler [mlx5_core] Call Trace: <TASK> dump_stack_lvl+0x69/0= xa0 print_report+0x176/0x4e4 kasan_report+0xc8/0x100 mlx5_query_nic_vport_m= ac_list+0x453/0x4c0 [mlx5_core] esw_update_vport_addr_list+0x2e3/0xda0 [mlx= 5_core] esw_vport_change_handle_locked+0xa1f/0x1060 [mlx5_core] esw_vport_c= hange_handler+0x6a/0x90 [mlx5_core] process_one_work+0x87f/0x15e0 worker_th= read+0x62b/0x1020 kthread+0x375/0x490 ret_from_fork+0x4dc/0x810 ret_from_fo= rk_asm+0x11/0x20 </TASK> Fix by querying the vport's own HCA caps to size t=
    he buffer correctly. Refactor the function to allocate and return the MAC l= ist internally, removing the caller's dependency on knowing the correct max=
    . 2026-06-25 8.7 CVE-2026-53230 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-53230 ] Linux--Linux In the Linux kernel, the following vulnerability ha=
    s been resolved: net: phy: clean the sfp upstream if phy probing fails Sash= iko reported that we don't call sfp_bus_del_upstream() in the probe failure=
    path, so let's add it, otherwise the sfp-bus is left with a dangling 'upst= ream' field, that may be used later on during SFP events. This issue existe=
    d before the generic phylib sfp support, back when drivers were calling phy= _sfp_probe themselves. 2026-06-25 8.8 CVE-2026-53232 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-53232 ] Linux--Linux In the Linux kernel, the follo= wing vulnerability has been resolved: xfrm: iptfs: fix use-after-free on fi= rst_skb in __input_process_payload __input_process_payload() stores first_s=
    kb into xtfs->ra_newskb under drop_lock when starting partial reassembly, t= hen unlocks and breaks out of the processing loop. The post-loop check read=
    s xtfs->ra_newskb without the lock to decide whether first_skb is still own= ed: if (first_skb && first_iplen && !defer && first_skb !=3D xtfs->ra_newsk=
    b) Between spin_unlock and this read, a concurrent CPU running iptfs_reasse= m_cont() (or the drop_timer hrtimer) can complete reassembly, NULL xtfs->ra= _newskb, and free the skb. The check then evaluates first_skb !=3D NULL as = true, and pskb_trim/ip_summed/consume_skb operate on the freed skb - a use-= after-free in skbuff_head_cache. Replace the unlocked read with a local boo=
    l that records whether first_skb was handed to the reassembly state in the = current call. The flag is set after the existing spin_unlock, before the br= eak, using the pointer equality that is stable at that point (first_skb =3D= =3D skb iff first_skb was stored in ra_newskb). 2026-06-25 8.8 CVE-2026-532=
    40 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53240 ] Linux--Linux In th=
    e Linux kernel, the following vulnerability has been resolved: net: airoha:=
    Fix use-after-free in metadata dst teardown airoha_metadata_dst_free() run=
    s metadata_dst_free() which frees the metadata_dst with kfree() immediately=
    , bypassing the RCU grace period. In the RX path, skb_dst_set_noref() sets =
    a non-refcounted pointer from the skb to the metadata_dst. This function re= quires RCU read-side protection and the dst must remain valid until all RCU=
    readers complete. Since metadata_dst_free() calls kfree() directly, an use= -after-free can occur if any skb still holds a noref pointer to the dst whe=
    n the driver tears it down. Replace metadata_dst_free() with dst_release() = which properly goes through the refcount path: when the refcount drops to z= ero, it schedules the actual free via call_rcu_hurry(), ensuring all RCU re= aders have completed before the memory is freed. 2026-06-25 8.8 CVE-2026-53= 248 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53248 ] Linux--Linux In t=
    he Linux kernel, the following vulnerability has been resolved: Bluetooth: = RFCOMM: validate skb length in MCC handlers The RFCOMM MCC handlers cast sk= b->data to protocol-specific structs without validating skb->len first. A m= alicious remote device can send truncated MCC frames and trigger out-of-bou= nds reads in these handlers. Fix this by using skb_pull_data() to validate = and access the required data before dereferencing it. rfcomm_recv_rpn() req= uires special handling since ETSI TS 07.10 allows 1-byte RPN requests. Hand=
    le this by validating only the DLCI byte first, and validating the full str= uct only when len > 1. 2026-06-25 8.1 CVE-2026-53254 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-53254 ] Linux--Linux In the Linux kernel, the follo= wing vulnerability has been resolved: Bluetooth: RFCOMM: hold listener sock=
    et in rfcomm_connect_ind() rfcomm_get_sock_by_channel() scans rfcomm_sk_lis=
    t under the list lock, but returns the selected listener after dropping tha=
    t lock without taking a reference. rfcomm_connect_ind() then locks the list= ener, queues a child socket on it, and may notify it after unlocking it. Th=
    e buggy scenario involves two paths, with each column showing the order wit= hin that path: rfcomm_connect_ind(): listener close: 1. Find parent in 1. c= lose() enters rfcomm_get_sock_by_channel() rfcomm_sock_release(). 2. Drop r= fcomm_sk_list.lock 2. rfcomm_sock_shutdown() without pinning parent. closes=
    the listener. 3. Call lock_sock(parent) and 3. rfcomm_sock_kill() bt_accep= t_enqueue(parent, unlinks and puts parent. sk, true). 4. Read parent flags = and may 4. parent can be freed. call sk_state_change(). If close wins the r= ace, parent can be freed before rfcomm_connect_ind() reaches lock_sock(), b= t_accept_enqueue(), or the deferred-setup callback. Take a reference on the=
    listener before leaving rfcomm_sk_list.lock. After lock_sock() succeeds, r= echeck that it is still in BT_LISTEN before queueing a child, cache the def= erred-setup bit while the parent is locked, and drop the reference after th=
    e last parent use. KASAN reported a slab-use-after-free in lock_sock_nested=
    () from rfcomm_connect_ind(), with the freeing stack going through rfcomm_s= ock_kill() and rfcomm_sock_release(). 2026-06-25 8 CVE-2026-53256 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-53256 ] Linux--Linux In the Linux kern= el, the following vulnerability has been resolved: netfilter: bridge: make = ebt_snat ARP rewrite writable The ebtables SNAT target keeps the Ethernet s= ource address rewrite behind skb_ensure_writable(skb, 0). This is intention= al: at the bridge ebtables hooks the Ethernet header is addressed through s= kb_mac_header()/eth_hdr(), while skb->data points at the Ethernet payload. = Asking skb_ensure_writable() for ETH_HLEN bytes would check the payload, no=
    t the Ethernet header, and would reintroduce the small packet regression fi= xed by commit 63137bc5882a. However, the optional ARP sender hardware addre=
    ss rewrite is different. It writes through skb_store_bits() at an offset re= lative to skb->data: skb_store_bits(skb, sizeof(struct arphdr), info->mac, = ETH_ALEN) skb_header_pointer() only safely reads the ARP header; it does no=
    t make the later sender hardware address range writable. If that range is s= till held in a nonlinear skb fragment backed by a splice-imported file page=
    , skb_store_bits() maps the frag page and copies the new MAC address direct=
    ly into it. Ensure the ARP SHA range is writable before reading the ARP hea= der and before calling skb_store_bits(). 2026-06-25 8.8 CVE-2026-53266 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-53266 ] Linux--Linux In the Linux=
    kernel, the following vulnerability has been resolved: netfilter: conntrac= k_irc: fix possible out-of-bounds read When parsing fails after we've match=
    ed the command string we should bail out instead of trying to match a diffe= rent command. This helper should be deprecated, given prevalence of TLS I d= oubt it has any relevance in 2026. 2026-06-25 8.2 CVE-2026-53268 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-53268 ] Linux--Linux In the Linux kerne=
    l, the following vulnerability has been resolved: ipv6: mcast: Fix use-afte= r-free when processing MLD queries When processing an MLD query, a pointer =
    to the multicast group address is retrieved when initially parsing the pack= et. This pointer is later dereferenced without being reloaded despite the f= act that the skb header might have been reallocated following the pskb_may_= pull() calls, leading to a use-after-free [1]. Fix by copying the multicast=
    group address when the packet is initially parsed. [1] BUG: KASAN: slab-us= e-after-free in __mld_query_work (net/ipv6/mcast.c:1512) Read of size 8 at = addr ffff8881154b8e90 by task kworker/4:1/118 Workqueue: mld mld_query_work=
    Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:12=
    0) print_address_description.constprop.0 (mm/kasan/report.c:378) print_repo=
    rt (mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:595) __mld_query= _work (net/ipv6/mcast.c:1512) mld_query_work (net/ipv6/mcast.c:1563) proces= s_one_work (kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3397=
    kernel/workqueue.c:3478) kthread (kernel/kthread.c:436) ret_from_fork (arc= h/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:24=
    5) </TASK> [...] Freed by task 118: kasan_save_stack (mm/kasan/common.c:57)=
    kasan_save_track (mm/kasan/common.c:78) kasan_save_free_info (mm/kasan/gen= eric.c:584) __kasan_slab_free (mm/kasan/common.c:253 mm/kasan/common.c:285)=
    kfree (./include/linux/kasan.h:235 mm/slub.c:2689 mm/slub.c:6251 mm/slub.c= :6566) pskb_expand_head (net/core/skbuff.c:2335) __pskb_pull_tail (net/core= /skbuff.c:2878 (discriminator 4)) __mld_query_work (net/ipv6/mcast.c:1495 (= discriminator 1)) mld_query_work (net/ipv6/mcast.c:1563) process_one_work (= kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3397 kernel/work= queue.c:3478) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel= /process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) 2026-06-2=
    5 8.8 CVE-2026-53275 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53275 ] = Linux--Linux In the Linux kernel, the following vulnerability has been reso= lved: KVM: arm64: Take the SRCU lock for page table walks in fault injectio=
    n and AT emulation walk_s1() and kvm_walk_nested_s2() expect to be called w= hile holding kvm->srcu to guard against memslot changes. While this is gene= rally the case, __kvm_at_s12() and __kvm_find_s1_desc_level() call into the=
    respective walkers without taking kvm->srcu. Fix by acquiring kvm->srcu pr= ior to the table walk in both instances. 2026-06-25 8.8 CVE-2026-53277 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-53277 ] Linux--Linux In the Linux=
    kernel, the following vulnerability has been resolved: iommu/vt-d: Avoid N= ULL pointer dereference or refcount corruption Commit 60f030f7418d ("iommu/= vt-d: Avoid use of NULL after WARN_ON_ONCE") fixed a NULL pointer dereferen=
    ce in an unlikely situation partly. If dev_pasid is not found in the dev_pa= sids list, it remains NULL. However, the teardown operations are executed u= nconditionally, this lead to a NULL pointer dereference or refcount corrupt= ion. If the domain was never attached to this IOMMU, info will be NULL, whi=
    ch would cause an immediate dereference when checking --info->refcnt. Even =
    if info is not NULL, decrementing the refcount without having removed a val=
    id PASID might unbalance the count. This could lead to premature dropping o=
    f the refcount to 0, potentially causing a use-after-free for the remaining=
    active devices sharing the domain. Fix it by returning early if dev_pasid =
    is NULL, before executing the teardown operations. Issue found by AI review=
    and suggested by Kevin Tian. https://sashiko.dev/#/patchset/20260421031347= .1408890-1-zhenzhong.duan%40intel.com 2026-06-26 8.8 CVE-2026-53281 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-53281 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: vfio/pci: Clean up DMA= BUFs before disabling function On device shutdown, make vfio_pci_core_close= _device() call vfio_pci_dma_buf_cleanup() before the function is disabled v=
    ia vfio_pci_core_disable(). This ensures that all access via DMABUFs is rev= oked before the function's BARs become inaccessible. This fixes an issue wh= ere, if the function is disabled first, a tiny window exists in which the f= unction's MSE is cleared and yet BARs could still be accessed via the DMABU=
    F. The resources would also be freed and up for grabs by a different driver=
    . 2026-06-26 8.8 CVE-2026-53322 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-53322 ] Linux--Linux In the Linux kernel, the following vulnerability ha=
    s been resolved: netfilter: nf_queue: hold bridge skb->dev while queued br_= pass_frame_up() rewrites skb->dev from the ingress port to the bridge maste=
    r before queueing bridge LOCAL_IN packets. NFQUEUE only holds references on=
    state.in/out and bridge physdevs, so a queued bridge packet can retain a f= reed bridge master in skb->dev until reinjection. When the verdict is reinj= ected later, br_netif_receive_skb() re-enters the receive path with skb->de=
    v still pointing at the freed bridge master, triggering a use-after-free. S= tore skb->dev in the queue entry, hold a reference on it for the queue life= time, and use the saved device when dropping queued packets during NETDEV_D= OWN handling. 2026-06-24 7.8 CVE-2026-52912 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-52912 ] Linux--Linux In the Linux kernel, the following vuln= erability has been resolved: netfilter: ip6t_hbh: reject oversized option l= ists struct ip6t_opts stores at most IP6T_OPTS_OPTSNR option descriptors, b=
    ut hbh_mt6_check() does not reject larger optsnr values supplied from users= pace. Validate optsnr in the rule setup path so only match data that fits t=
    he fixed-size opts array can be installed. This follows the existing xtable=
    s pattern of rejecting invalid user-provided counts in checkentry() and kee=
    ps the packet matching path unchanged. `struct ip6t_opts` has a fixed `opts= [IP6T_OPTS_OPTSNR]` array, where `IP6T_OPTS_OPTSNR` is 16, then off-by-one = array access is possible: [ 137.924693][ T8692] UBSAN: array-index-out-of-b= ounds in ../net/ipv6/netfilter/ip6t_hbh.c:110:29 [ 137.926167][ T8692] inde=
    x 16 is out of range for type '__u16 [16]' 2026-06-24 7.1 CVE-2026-52915 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-52915 ] Linux--Linux In the Lin=
    ux kernel, the following vulnerability has been resolved: sctp: diag: rejec=
    t stale associations in dump_one path The SCTP exact sock_diag lookup can h= old a transport reference, block on lock_sock(sk), and then resume after sc= tp_association_free() has marked the association dead and freed its bind ad= dress list. When that happens, inet_assoc_attr_size() and inet_diag_msg_sct= pasoc_fill() can still dereference association state that is no longer vali=
    d for reporting. In particular, inet_diag_msg_sctpasoc_fill() may read an e= mpty bind-address list as a real sctp_sockaddr_entry and trigger an out-of-= bounds read from unrelated association memory. Reject the association after=
    taking the socket lock if it has been reaped or detached from the endpoint=
    , and report the lookup as stale. This keeps the exact dump-one path from f= ormatting torn association state. 2026-06-24 7.1 CVE-2026-52917 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-52917 ] Linux--Linux In the Linux kernel=
    , the following vulnerability has been resolved: batman-adv: fix tp_meter c= ounter underflow during shutdown batadv_tp_sender_shutdown() unconditionall=
    y decrements the "sending" atomic counter. If multiple paths (e.g. timeout,=
    user cancel, and normal finish) call this function, the counter can underf= low to -1. Since the sender logic treats any non-zero value as "still sendi= ng", a negative value causes the sender kthread to loop indefinitely. This = leads to a use-after-free when the interface is removed while the zombie th= read is still active. Fix this by using atomic_xchg() to ensure the counter=
    only transitions from 1 to 0 once. [sven: added missing change in batadv_t= p_send] 2026-06-24 7.8 CVE-2026-52919 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-52919 ] Linux--Linux In the Linux kernel, the following vulnerabil= ity has been resolved: batman-adv: dat: handle forward allocation error bat= adv_dat_forward_data() calls pskb_copy_for_clone() to duplicate an skb for = each DHT candidate, but does not check the return value before passing it t=
    o batadv_send_skb_prepare_unicast_4addr(). That function dereferences the s=
    kb unconditionally, so a failed allocation triggers a NULL pointer derefere= nce. Skip forwarding to the current DHT candidate on allocation failure. 20= 26-06-24 7.5 CVE-2026-52922 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 2922 ] Linux--Linux In the Linux kernel, the following vulnerability has be=
    en resolved: ipc: limit next_id allocation to the valid ID range The checkp= oint/restore sysctl path can request the next SysV IPC id through ids->next= _id. ipc_idr_alloc() currently forwards that request to idr_alloc() with an=
    open-ended upper bound. If the valid tail of the SysV IPC id space is full=
    , the allocation can spill beyond ipc_mni. The returned SysV IPC id still u= ses the normal index encoding, so later lookup and removal can target the w= rong slot. This leaves the real IDR entry behind and breaks the IDR state f=
    or the object. The bug is in ipc_idr_alloc() in the checkpoint/restore path=
    . 1. ids->next_id is passed to: idr_alloc(&ids->ipcs_idr, new, ipcid_to_idx= (next_id), 0, ...) 2. The zero upper bound makes the allocation effectively=
    open-ended. Once the valid SysV IPC tail is occupied, idr_alloc() can spil=
    l past ipc_mni and allocate an entry beyond the valid IPC id range. 3. The = new object id is still encoded with the narrower SysV IPC index width: new-= >id =3D (new->seq << ipcmni_seq_shift()) + idx 4. Later removal goes throug=
    h ipc_rmid(), which uses: ipcid_to_idx(ipcp->id) That truncates the real ID=
    R index. An object actually stored at a high index can then be removed as i=
    f it lived at a low in-range index. 5. For shared memory, shm_destroy() fre=
    es the current object anyway, but the real high IDR slot is left behind as =
    a dangling pointer. 6. A subsequent walk of /proc/sysvipc/shm reaches the s= tale IDR entry and dereferences freed memory. Prevent this by bounding the = requested allocation to ipc_mni so the checkpoint/restore path fails once t=
    he valid range is exhausted. 2026-06-24 7.8 CVE-2026-52923 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-52923 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: netfilter: ebtables: fix OOB re=
    ad in compat_mtw_from_user Luxiao Xu says: The function compat_mtw_from_use= r() converts ebtables extensions from 32-bit user structures to kernel nati=
    ve structures. However, it lacks proper validation of the user-supplied mat= ch_size/target_size. When certain extensions are processed, the kernel-side=
    translation logic may perform memory accesses based on the extension's exp= ected size. If the user provides a size smaller than what the extension req= uires, it results in an out-of-bounds read as reported by KASAN. This fix i= ntroduces a check to ensure match_size is at least as large as the extensio= n's required compatsize. This covers matches, watchers, and targets, while = maintaining compatibility with standard targets. AFAIU this is relevant for=
    matches that need to go though match->compat_from_user() call. Those that = use plain memcpy with the user-provided size are ok because the caller chec=
    ks that size vs the start of the next rule entry offset (which itself is ch= ecked vs. total size copied from userspace). The ->compat_from_user() callb= acks assume they can read compatsize bytes, so they need this extra check. = Based on an earlier patch from Luxiao Xu. 2026-06-24 7.8 CVE-2026-52927 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-52927 ] Linux--Linux In the Linu=
    x kernel, the following vulnerability has been resolved: sctp: stream: full=
    y roll back denied add-stream state When ADD_OUT_STREAMS is denied, SCTP on=
    ly shrinks the queued chunks and then lowers outcnt. That leaves removed st= ream metadata behind, so a later re-add can reuse a stale ext and hit a nul= l-pointer dereference in the scheduler get path. Fix the rollback by tearin=
    g down the removed stream state the same way other stream resizes do. Unsch= edule the current scheduler state, drop the removed stream ext state with s= ctp_stream_outq_migrate(), and then reschedule the remaining streams. This = keeps scheduler-private RR/FC/PRIO lists consistent while fully rolling bac=
    k denied outgoing stream additions. 2026-06-24 7.5 CVE-2026-52929 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-52929 ] Linux--Linux In the Linux kern= el, the following vulnerability has been resolved: xfrm: ipcomp: Free desti= nation pages on acomp errors Move the out_free_req label up by a couple of = lines so that the allocated dst SG list gets freed on error as well as succ= ess. 2026-06-24 7.5 CVE-2026-52932 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-52932 ] Linux--Linux In the Linux kernel, the following vulnerability=
    has been resolved: io_uring/poll: fix signed comparison in io_poll_get_own= ership() io_poll_get_ownership() uses a signed comparison to check whether = poll_refs has reached the threshold for the slowpath: if (unlikely(atomic_r= ead(&req->poll_refs) >=3D IO_POLL_REF_BIAS)) atomic_read() returns int (sig= ned). When IO_POLL_CANCEL_FLAG (BIT(31)) is set in poll_refs, the value bec= omes negative in signed arithmetic, so the >=3D 128 comparison always evalu= ates to false and the slowpath is never taken. Fix this by casting the atom= ic_read() result to unsigned int before the comparison, so that the cancel = flag is treated as a large positive value and correctly triggers the slowpa= th. 2026-06-24 7.8 CVE-2026-52933 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-52933 ] Linux--Linux In the Linux kernel, the following vulnerability = has been resolved: xfrm: espintcp: do not reuse an in-progress partial send=
    espintcp keeps a single in-flight transmit in ctx->partial. Before buildin=
    g a new sk_msg, espintcp_sendmsg() first tries to flush that state through = espintcp_push_msgs(). For blocking callers, espintcp_push_msgs() may return=
    success even when the previous partial send is still pending. espintcp_sen= dmsg() would then reinitialize emsg->skmsg and reuse ctx->partial while the=
    old transfer still owns that state. Do not rebuild the send message when c= tx->partial is still in progress. If espintcp_push_msgs() returns with emsg= ->len still set, fail the new send instead of overwriting the live partial = state. This is a memory-safety fix: reusing the live partial-send state can=
    leave a stale offset attached to a new sk_msg and lead to an out-of- bound=
    s read in the send path. tcp_sendmsg_locked() already handles waiting for s= end buffer memory, so the fix here is just to preserve espintcp's one-messa= ge-at-a-time transmit state. 2026-06-24 7.8 CVE-2026-52935 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-52935 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: netfilter: nf_log: validate MAC=
    header was set before dumping it The fallback path of dump_mac_header() gu= ards the MAC header access only with "skb->mac_header !=3D skb->network_hea= der", without checking skb_mac_header_was_set(). When the MAC header is uns= et, mac_header is 0xffff, so the test passes and skb_mac_header(skb) return=
    s skb->head + 0xffff, ~64 KiB past the buffer; the loop then reads dev->har= d_header_len bytes out of bounds into the kernel log. This is reachable via=
    the netdev logger: nf_log_unknown_packet() calls dump_mac_header() uncondi= tionally, and an skb sent through AF_PACKET with PACKET_QDISC_BYPASS reache=
    s the egress hook with mac_header still unset (__dev_queue_xmit(), which wo= uld reset it, is bypassed). Add the skb_mac_header_was_set() check the ARPH= RD_ETHER path already uses, and replace the open-coded MAC header length te=
    st with skb_mac_header_len(). Only skbs with an unset MAC header are affect= ed; valid ones are dumped as before. BUG: KASAN: slab-out-of-bounds in dump= _mac_header (net/netfilter/nf_log_syslog.c:831) Read of size 1 at addr ffff= 88800ea49d3f by task exploit/148 Call Trace: kasan_report (mm/kasan/report.= c:595) dump_mac_header (net/netfilter/nf_log_syslog.c:831) nf_log_netdev_pa= cket (net/netfilter/nf_log_syslog.c:938 net/netfilter/nf_log_syslog.c:963) = nf_log_packet (net/netfilter/nf_log.c:260) nft_log_eval (net/netfilter/nft_= log.c:60) nft_do_chain (net/netfilter/nf_tables_core.c:285) nft_do_chain_ne= tdev (net/netfilter/nft_chain_filter.c:307) nf_hook_slow (net/netfilter/cor= e.c:619) nf_hook_direct_egress (net/packet/af_packet.c:257) packet_xmit (ne= t/packet/af_packet.c:280) packet_sendmsg (net/packet/af_packet.c:3114) __sy= s_sendto (net/socket.c:2265) 2026-06-24 7.1 CVE-2026-52942 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-52942 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: net: skbuff: fix missing zeroco=
    py reference in pskb_carve helpers pskb_carve_inside_header() and pskb_carv= e_inside_nonlinear() both copy the old skb_shared_info header into a new bu= ffer via memcpy(), which includes the destructor_arg pointer (uarg) for MSG= _ZEROCOPY skbs. Neither function calls net_zcopy_get() for the new shinfo, = creating an unaccounted holder: every skb_shared_info with destructor_arg s=
    et will call skb_zcopy_clear() once when freed, but the corresponding net_z= copy_get() was never called for the new copy. Repeated calls drive uarg->re= fcnt to zero prematurely, freeing ubuf_info_msgzc while TX skbs still hold = live destructor_arg pointers. KASAN reports use-after-free on a freed ubuf_= info_msgzc: BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810=
    Read of size 8 at addr ffff88801574d3e8 by task poc/220 Call Trace: skb_re= lease_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0= x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440=
    rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x1=
    80 Allocated by task 219: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_lock= ed+0x2892/0x3ba0 Freed by task 219: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0= x475/0x530 The skb consuming the late access still referenced the same uarg=
    via shinfo->destructor_arg copied by pskb_carve_inside_nonlinear() without=
    a refcount bump. This has been verified to be reliably exploitable: a work= ing proof-of-concept achieves full root privilege escalation from an unpriv= ileged local user on a default kernel configuration. The fix follows the pa= ttern of pskb_expand_head() which has the same memcpy/cloned structure. For=
    pskb_carve_inside_header(), net_zcopy_get() is placed after skb_orphan_fra= gs() succeeds, so the orphan error path needs no cleanup. For pskb_carve_in= side_nonlinear(), net_zcopy_get() is placed after all failure points and ju=
    st before skb_release_data(), so no error path needs cleanup at all -- matc= hing pskb_expand_head() more closely and avoiding the need for a balancing = net_zcopy_put(). 2026-06-24 7.8 CVE-2026-52943 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-52943 ] Linux--Linux In the Linux kernel, the following v= ulnerability has been resolved: Revert "wireguard: device: enable threaded = NAPI" This reverts commit 933466fc50a8e4eb167acbd0d8ec96a078462e9c which is=
    commit db9ae3b6b43c79b1ba87eea849fd65efa05b4b2e upstream. We have had thre=
    e independent production user reports in combination with Cilium utilizing = WireGuard as encryption underneath that k8s Pod E/W traffic to certain peer=
    nodes fully stalled. The situation appears as follows: - Occurs very rarel=
    y but at random times under heavy networking load. - Once the issue trigger=
    s the decryption side stops working completely for that WireGuard peer, oth=
    er peers keep working fine. The stall happens also for newly initiated conn= ections towards that particular WireGuard peer. - Only the decryption side =
    is affected, never the encryption side. - Once it triggers, it never recove=
    rs and remains in this state, the CPU/mem on that node looks normal, no lea=
    k, busy loop or crash. - bpftrace on the affected system shows that wg_prev= _queue_enqueue fails, thus the MAX_QUEUED_PACKETS (1024 skbs!) for the peer=
    's rx_queue is reached. - Also, bpftrace shows that wg_packet_rx_poll for t= hat peer is never called again after reaching this state for that peer. For=
    other peers wg_packet_rx_poll does get called normally. - Commit db9ae3b (= "wireguard: device: enable threaded NAPI") switched WireGuard to threaded N= API by default. The default has not been changed for triggering the issue, = neither did CPU hotplugging occur (i.e. 5bd8de2 ("wireguard: queueing: alwa=
    ys return valid online CPU in wg_cpumask_choose_online()")). - The issue ha=
    s been observed with stable kernels of v5.15 as well as v6.1. It was report=
    ed to us that v5.10 stable is working fine, and no report on v6.6 stable ei= ther (somewhat related discussion in [0] though). - In the WireGuard driver=
    the only material difference between v5.10 stable and v5.15 stable is the = switch to threaded NAPI by default. [0] https://lore.kernel.org/netdev/CA+w= XwBTT74RErDGAnj98PqS=3Dwvdh8eM1pi4q6tTdExtjnokKqA@mail.gmail.com/ Breakdown=
    of the problem: 1) skbs arriving for decryption are enqueued to the peer->= rx_queue in wg_packet_consume_data via wg_queue_enqueue_per_device_and_peer=
    . 2) The latter only moves the skb into the MPSC peer queue if it does not = surpass MAX_QUEUED_PACKETS (1024) which is kept track in an atomic counter = via wg_prev_queue_enqueue. 3) In case enqueueing was successful, the skb is=
    also queued up in the device queue, round-robin picks a next online CPU, a=
    nd schedules the decryption worker. 4) The wg_packet_decrypt_worker, once s= cheduled, picks these up from the queue, decrypts the packets and once done=
    calls into wg_queue_enqueue_per_peer_rx. 5) The latter updates the state t=
    o PACKET_STATE_CRYPTED on success and calls napi_schedule on the per peer->= napi instance. 6) NAPI then polls via wg_packet_rx_poll. wg_prev_queue_peek=
    checks on the peer->rx_queue. It will wg_prev_queue_dequeue if the queue->= peeked skb was not cached yet, or just return the latter otherwise. (wg_pre= v_queue_drop_peeked later clears the cache.) 7) From an ordering perspectiv=
    e, the peer->rx_queue has skbs in order while the device queue with the per= -CPU worker threads from a global ordering PoV can finish the decryption an=
    d signal the skb PACKET_STATE_CRYPTED out of order. 8) A situation can be o= bserved that the first packet coming in will be stuck waiting for the decry= ption worker to be scheduled for a longer time when the system is under pre= ssure. 9) While this is the case, the other CPUs in the meantime finish dec= ryption and call into napi_schedule. 10) Now in wg_packet_rx_poll it picks =
    up the first in-order skb from the peer->rx_queue and sees that its state i=
    s still PACKET_STATE_UNCRYPTED. The NAPI poll routine then exits e ---trunc= ated--- 2026-06-24 7.5 CVE-2026-52945 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-52945 ] Linux--Linux In the Linux kernel, the following vulnerabil= ity has been resolved: fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync si= gnaling A SOFTIRQ-safe to SOFTIRQ-unsafe lock order deadlock can occur in s= end_sigio() and send_sigurg() when a process group receives a signal. When = FASYNC is configured for a process group (PIDTYPE_PGID), both functions use=
    read_lock(&tasklist_lock) to traverse the task list. However, they are fre= quently called from softirq context: - send_sigio() via input_inject_event =
    kill_fasync - send_sigurg() via tcp_check_urg -> sk_send_sigurg (NET_RX_=
    SOFTIRQ) The deadlock is caused by the rwlock writer fairness mechanism: 1.=
    CPU 0 (process context) holds read_lock(&tasklist_lock) in do_wait(). 2. C=
    PU 1 (process context) attempts write_lock(&tasklist_lock) in fork() or exi= t() and spins, which blocks all new readers. 3. CPU 0 is interrupted by a s= oftirq (e.g., TCP URG packet reception). 4. The softirq calls send_sigurg()=
    and attempts to acquire read_lock(&tasklist_lock), deadlocking because CPU=
    1 is waiting. Since PID hashing and do_each_pid_task() traversals are alre= ady RCU-protected, the read_lock on tasklist_lock is no longer strictly req= uired for safe traversal. Fix this by replacing tasklist_lock with rcu_read= _lock(), aligning the process group signaling path with the single-PID path=
    . This also mitigates a potential remote denial of service vector via TCP U=
    RG packets. Lockdep splat: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D WARNING: SOFTIRQ-safe -> SOFTIRQ-unsaf=
    e lock order detected [...] Chain exists of: &dev->event_lock --> &f_owner-= >lock --> tasklist_lock Possible interrupt unsafe locking scenario: CPU0 CP=
    U1 ---- ---- lock(tasklist_lock); local_irq_disable(); lock(&dev->event_loc= k); lock(&f_owner->lock); <Interrupt> lock(&dev->event_lock); *** DEADLOCK = *** 2026-06-24 7.5 CVE-2026-52946 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-52946 ] Linux--Linux In the Linux kernel, the following vulnerability = has been resolved: net: qrtr: fix refcount saturation and potential UAF in = qrtr_port_remove In qrtr_port_remove(), the socket reference count is decre= mented via __sock_put() before the port is removed from the qrtr_ports XArr=
    ay and before the RCU grace period elapses. This breaks the fundamental RCU=
    update paradigm. It exposes a race window where a concurrent RCU reader (s= uch as qrtr_reset_ports() or qrtr_port_lookup()) can obtain a pointer to th=
    e socket from the XArray, and attempt to call sock_hold() on a socket whose=
    reference count has already dropped to zero. This exact race condition was=
    hit during syzkaller fuzzing, leading to the following refcount saturation=
    warning and a potential Use-After-Free: refcount_t: saturated; leaking mem= ory. WARNING: CPU: 3 PID: 1273 at lib/refcount.c:22 refcount_warn_saturate+= 0xae/0x1d0 Modules linked in: qrtr(+) bochs drm_shmem_helper ... Call Trace=
    : <TASK> qrtr_reset_ports net/qrtr/af_qrtr.c:768 [inline] [qrtr] __qrtr_bin= d.isra.0+0x48b/0x570 net/qrtr/af_qrtr.c:805 [qrtr] qrtr_bind+0x17d/0x210 ne= t/qrtr/af_qrtr.c:901 [qrtr] kernel_bind+0xe4/0x120 net/socket.c:3592 qrtr_n= s_init+0x1a6/0x380 net/qrtr/ns.c:715 [qrtr] qrtr_proto_init+0x3b/0xff0 net/= qrtr/af_qrtr.c:169 [qrtr] do_one_initcall+0xf5/0x5e0 init/main.c:1283 ... <= /TASK> Fix this by deferring the reference count decrement until after the = xa_erase() and the synchronize_rcu() complete. (Note: The v1 of this patch = incorrectly replaced __sock_put() with sock_put(). As Simon Horman pointed = out, the callers of qrtr_port_remove() still hold a reference to the socket=
    , so freeing the socket memory here would lead to a subsequent UAF in the c= aller. Thus, the __sock_put() is kept, but only repositioned to close the R=
    CU race.) 2026-06-24 7.8 CVE-2026-52947 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-52947 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: drm/xe/dma-buf: fix UAF with retry loop Retry doe= sn't work here, since bo will be freed on error, leading to UAF. However, n=
    ow that we do the alloc & init before the attach, we can now combine this a=
    s one unit and have the init do the alloc for us. This should make the retr=
    y safe. Reported by Sashiko. v2: Fix up the error unwind (CI) (cherry picke=
    d from commit 479669418253e0f27f8cf5db01a731352ea592e7) 2026-06-24 7.8 CVE-= 2026-52950 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52950 ] Linux--Lin=
    ux In the Linux kernel, the following vulnerability has been resolved: drm/= xe/dma-buf: handle empty bo and UAF races There look to be some nasty races=
    here when triggering the invalidate_mappings hook: 1) We do xe_bo_alloc() = followed by the attach, before the actual full bo init step in xe_dma_buf_i= nit_obj(). However the bo is visible on the attachments list after the atta= ch. This is bad since exporter driver, say amdgpu, can at any time call bac=
    k into our invalidate_mappings hook, with an empty/bogus bo, leading to pot= ential bugs/crashes. 2) Similar to 1) but here we get a UAF, when the inval= idate_mappings hook is triggered. For example, we get as far as xe_bo_init_= locked() but this fails in some way. But here the bo will be freed on error=
    , but we still have it attached from dma-buf pov, so if the invalidate_mapp= ings is now triggered then the bo we access is gone and we trigger UAF and = more bugs/crashes. To fix this, move the attach step until after we actuall=
    y have a fully set up buffer object. Note that the bo is not published to u= serspace until later, so not sure what the comment "Don't publish the bo un= til we have a valid attachment", is referring to. We have at least two diff= erent customers reporting hitting a NULL ptr deref in evict_flags when impo= rting something from amdgpu, followed by triggering the evict flow. Hit rat=
    e is also pretty low, which would hint at some kind of race, so something l= ike 1) or 2) might explain this. v2: - Shuffle the order of the ops slightl=
    y (no functional change) - Improve the comment to better explain the orderi=
    ng (Matt B) (cherry picked from commit af1f2ad0c59fe4e2f924c526f66e968289d7= 7971) 2026-06-24 7.8 CVE-2026-52951 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-52951 ] Linux--Linux In the Linux kernel, the following vulnerabilit=
    y has been resolved: iommu/vt-d: Fix oops due to out of scope access Below = oops triggers when kill QEMU process: Oops: general protection fault, proba= bly for non-canonical address 0x7fffffff844eaaa7: 0000 [#1] SMP NOPTI Call = Trace: <TASK> do_raw_spin_lock+0xaa/0xc0 _raw_spin_lock_irqsave+0x21/0x40 d= omain_remove_dev_pasid+0x52/0x160 intel_nested_set_dev_pasid+0x1b9/0x1e0 __= iommu_set_group_pasid+0x56/0x120 pci_dev_reset_iommu_done+0xe3/0x180 pcie_f= lr+0x65/0x160 __pci_reset_function_locked+0x5b/0x120 vfio_pci_core_close_de= vice+0x63/0xe0 [vfio_pci_core] vfio_df_close+0x4f/0xa0 vfio_df_unbind_iommu= fd+0x2d/0x60 vfio_device_fops_release+0x3e/0x40 __fput+0xe5/0x2c0 task_work= _run+0x58/0xa0 do_exit+0x2c8/0x600 do_group_exit+0x2f/0xa0 get_signal+0x863= /0x8c0 arch_do_signal_or_restart+0x24/0x100 exit_to_user_mode_loop+0x87/0x3=
    80 do_syscall_64+0x2ff/0x11e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The = global static blocked domain is a dummy domain without corresponding dmar_d= omain structure, accessing beyond iommu_domain structure triggers oops easi= ly. Fix it by return early in domain_remove_dev_pasid() like identity domai=
    n. 2026-06-24 7.1 CVE-2026-52953 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-52953 ] Linux--Linux In the Linux kernel, the following vulnerability h=
    as been resolved: libceph: handle rbtree insertion error in decode_choose_a= rgs() A message of type CEPH_MSG_OSD_MAP contains an OSD map that itself co= ntains a CRUSH map. The received CRUSH map may optionally contain choose_ar=
    gs that get decoded in decode_choose_args(). In this function, num_choose_a= rg_maps is read from the message, and a corresponding number of crush_choos= e_arg_maps gets decoded afterwards. Each crush_choose_arg_map has a choose_= args_index, which serves as the key when inserting it into the choose_args = rbtree of the decoded crush_map. If a (potentially corrupted) message conta= ins two crush_choose_arg_maps with the same index, the assertion in insert_= choose_arg_map() triggers a kernel BUG when trying to insert the second cru= sh_choose_arg_map. This patch fixes the issue by switching to the non-asser= ting rbtree insertion function and rejecting the message if the insertion f= ails. [ idryomov: changelog ] 2026-06-24 7.5 CVE-2026-52954 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-52954 ] Linux--Linux In the Linux kernel, th=
    e following vulnerability has been resolved: libceph: Fix potential out-of-= bounds access in __ceph_x_decrypt() In __ceph_x_decrypt(), a part of the bu= ffer p is interpreted as a ceph_x_encrypt_header, and the magic field of th=
    is struct is accessed. This happens without any guarantee that the buffer i=
    s large enough to hold this struct. The function parameter ciphertext_len r= epresents the length of the ciphertext to decrypt and is guaranteed to be a=
    t most the remaining size of the allocated buffer p. However, this value is=
    not necessarily greater than sizeof(ceph_x_encrypt_header). E.g., a messag=
    e frame of type FRAME_TAG_AUTH_REPLY_MORE, that is just as long to hold the=
    ciphertext at its end with a ciphertext_len of 8 or less, can trigger an o= ut-of-bounds memory access when accessing hdr->magic. This patch fixes the = issue by adding a check to ensure that the decrypted plaintext in the buffe=
    r is large enough to represent at least the ceph_x_encrypt_header. 2026-06-=
    24 7.5 CVE-2026-52956 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52956 ]=
    Linux--Linux In the Linux kernel, the following vulnerability has been res= olved: libceph: Fix potential null-ptr-deref in decode_choose_args() A mess= age of type CEPH_MSG_OSD_MAP contains an OSD map that itself contains a CRU=
    SH map. When decoding this CRUSH map in crush_decode(), an array of max_buc= kets CRUSH buckets is decoded, where some indices may not refer to actual b= uckets and are therefore set to NULL. The received CRUSH map may optionally=
    contain choose_args that get decoded in decode_choose_args(). When decodin=
    g a crush_choose_arg_map, a series of choose_args for different buckets is = decoded, with the bucket_index being read from the incoming message. It is = only checked that the bucket index does not exceed max_buckets, but not tha=
    t it doesn't point to an index with a NULL bucket. If a (potentially corrup= ted) message contains a crush_choose_arg_map including such a bucket_index,=
    a null pointer dereference may occur in the subsequent processing when att= empting to access the bucket with the given index. This patch fixes the iss=
    ue by extending the affected check. Now, it is only attempted to access the=
    bucket if it is not NULL. 2026-06-24 7.5 CVE-2026-52957 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-52957 ] Linux--Linux In the Linux kernel, the f= ollowing vulnerability has been resolved: virt: sev-guest: Do not use host-= controlled page order in cleanup path When issuing an extended guest reques=
    t (SVM_VMGEXIT_EXT_GUEST_REQUEST), get_ext_report() allocates a buffer to r= etrieve a certificate blob from the host, keeping track of its size in repo= rt_req->certs_len. However, the host may return SNP_GUEST_VMM_ERR_INVALID_L= EN, indicating an invalid buffer size, as well as the expected length of su=
    ch buffer. get_ext_report() subsequently updates report_req->certs_len with=
    the host-controlled value, and cleans up the buffer by computing a page or= der from such value. This is incorrect, as the host-provided length may not=
    match the page order of the original allocation, potentially resulting in = corruption in the page allocator. Fix this by using alloc_pages_exact() ins= tead, and reusing @npages to compute the size passed to free_pages_exact().=
    For consistency, also use @npages to compute the size when allocating the = pages, even though this last change has no functional effect. 2026-06-24 7.=
    8 CVE-2026-52959 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52959 ] Linu= x--Linux In the Linux kernel, the following vulnerability has been resolved=
    : ceph: put folios not suitable for writeback The batch holds references to=
    the folios (see `filemap_get_folios`, `folio_batch_release`), so we need t=
    o `folio_put` the folios we remove. Tested on v6.18. 2026-06-24 7.5 CVE-202= 6-52960 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52960 ] Linux--Linux =
    In the Linux kernel, the following vulnerability has been resolved: net: en=
    a: PHC: Fix potential use-after-free in get_timestamp Move the phc->active = check and resp pointer assignment to after acquiring the spinlock. Previous= ly, phc->active was checked without holding the lock, and resp was cached f= rom ena_dev->phc.virt_addr before the lock was acquired. If ena_com_phc_des= troy() runs between the lockless active check and the lock acquisition, it = sets active=3Dfalse, releases the lock, frees the DMA memory, and sets virt= _addr=3DNULL. The get_timestamp path would then read a NULL virt_addr and d= ereference it. With both the active check and the pointer read under the lo= ck, destroy cannot free the memory while get_timestamp is using it. 2026-06= -24 7.8 CVE-2026-52971 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52971 =
    ] Linux--Linux In the Linux kernel, the following vulnerability has been re= solved: futex: Drop CLONE_THREAD requirement for private default hash alloc=
    Currently need_futex_hash_allocate_default() depends on strict pthread sem= antics, abusing CLONE_THREAD. This breaks the non-concurrency assumptions w= hen doing the mm->futex_ref pcpu allocations, leading to bugs[0] when shari=
    ng the mm in other ways; ie: BUG: KASAN: slab-use-after-free in futex_hash_= put ... where the +1 bias can end up on a percpu counter that mm->futex_ref=
    no longer points at. Loosen the check to cover any CLONE_VM clone, except = vfork(). Excluding vfork keeps the existing paths untouched (no overhead), = and we can't race in the first place: either the parent is suspended and th=
    e child runs alone, or mm->futex_ref is already allocated from an earlier C= LONE_VM. 2026-06-24 7.8 CVE-2026-52973 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-52973 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: net: tls: fix strparser anchor skb leak on offloa=
    d RX setup failure When tls_set_device_offload_rx() fails at tls_dev_add(),=
    the error path calls tls_sw_free_resources_rx() to clean up the SW context=
    that was initialized by tls_set_sw_offload(). This function calls tls_sw_r= elease_resources_rx() (which stops the strparser via tls_strp_stop()) and t= ls_sw_free_ctx_rx() (which kfrees the context), but never frees the anchor = skb that was allocated by alloc_skb(0) in tls_strp_init(). Note that tls_sw= _free_resources_rx() is exclusively used for this "failed to start offload"=
    code path, there's no other caller. The leak did not exist before commit 8= 4c61fe1a75b ("tls: rx: do not use the standard strparser"), because the sta= ndard strparser doesn't try to pre-allocate an skb. The normal close path i=
    n tls_sk_proto_close() handles cleanup by calling tls_sw_strparser_done() (= which calls tls_strp_done()) after dropping the socket lock, because tls_st= rp_done() does cancel_work_sync() and the strparser work handler takes the = socket lock. 2026-06-24 7.5 CVE-2026-52974 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-52974 ] Linux--Linux In the Linux kernel, the following vulne= rability has been resolved: bonding: 3ad: implement proper RCU rules for po= rt->aggregator syzbot found a data-race in bond_3ad_get_active_agg_info / b= ond_3ad_state_machine_handler [1] which hints at lack of proper RCU impleme= ntation. Add __rcu qualifier to port->aggregator, and add proper RCU API. [=
    1] BUG: KCSAN: data-race in bond_3ad_get_active_agg_info / bond_3ad_state_m= achine_handler write to 0xffff88813cf5c4b0 of 8 bytes by task 36 on cpu 0: = ad_port_selection_logic drivers/net/bonding/bond_3ad.c:1659 [inline] bond_3= ad_state_machine_handler+0x9d5/0x2d60 drivers/net/bonding/bond_3ad.c:2569 p= rocess_one_work kernel/workqueue.c:3302 [inline] process_scheduled_works+0x= 4f0/0x9c0 kernel/workqueue.c:3385 worker_thread+0x58a/0x780 kernel/workqueu= e.c:3466 kthread+0x22a/0x280 kernel/kthread.c:436 ret_from_fork+0x146/0x330=
    arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/e= ntry_64.S:245 read to 0xffff88813cf5c4b0 of 8 bytes by task 22063 on cpu 1:=
    __bond_3ad_get_active_agg_info drivers/net/bonding/bond_3ad.c:2858 [inline=
    ] bond_3ad_get_active_agg_info+0x8c/0x230 drivers/net/bonding/bond_3ad.c:28=
    81 bond_fill_info+0xe0f/0x10f0 drivers/net/bonding/bond_netlink.c:853 rtnl_= link_info_fill net/core/rtnetlink.c:906 [inline] rtnl_link_fill+0x1d7/0x4e0=
    net/core/rtnetlink.c:927 rtnl_fill_ifinfo+0xf8e/0x1380 net/core/rtnetlink.= c:2168 rtmsg_ifinfo_build_skb+0x11c/0x1b0 net/core/rtnetlink.c:4453 rtmsg_i= finfo_event net/core/rtnetlink.c:4486 [inline] rtmsg_ifinfo+0x6d/0x110 net/= core/rtnetlink.c:4495 __dev_notify_flags+0x76/0x390 net/core/dev.c:9790 net= if_change_flags+0xac/0xd0 net/core/dev.c:9823 do_setlink+0x905/0x2950 net/c= ore/rtnetlink.c:3180 rtnl_group_changelink net/core/rtnetlink.c:3813 [inlin=
    e] __rtnl_newlink net/core/rtnetlink.c:3981 [inline] rtnl_newlink+0xf55/0x1= 400 net/core/rtnetlink.c:4109 rtnetlink_rcv_msg+0x64b/0x720 net/core/rtnetl= ink.c:6995 netlink_rcv_skb+0x123/0x220 net/netlink/af_netlink.c:2550 rtnetl= ink_rcv+0x1c/0x30 net/core/rtnetlink.c:7022 netlink_unicast_kernel net/netl= ink/af_netlink.c:1318 [inline] netlink_unicast+0x5a8/0x680 net/netlink/af_n= etlink.c:1344 netlink_sendmsg+0x5c8/0x6f0 net/netlink/af_netlink.c:1894 soc= k_sendmsg_nosec net/socket.c:787 [inline] __sock_sendmsg net/socket.c:802 [= inline] ____sys_sendmsg+0x563/0x5b0 net/socket.c:2698 ___sys_sendmsg+0x195/= 0x1e0 net/socket.c:2752 __sys_sendmsg net/socket.c:2784 [inline] __do_sys_s= endmsg net/socket.c:2789 [inline] __se_sys_sendmsg net/socket.c:2787 [inlin=
    e] __x64_sys_sendmsg+0xd4/0x160 net/socket.c:2787 x64_sys_call+0x194c/0x302=
    0 arch/x86/include/generated/asm/syscalls_64.h:47 do_syscall_x64 arch/x86/e= ntry/syscall_64.c:63 [inline] do_syscall_64+0x12c/0x3b0 arch/x86/entry/sysc= all_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f value changed: 0x00000= 00000000000 -> 0xffff88813cf5c400 Reported by Kernel Concurrency Sanitizer = on: CPU: 1 UID: 0 PID: 22063 Comm: syz.0.31122 Tainted: G W syzkaller #0 PR= EEMPT(full) Tainted: [W]=3DWARN Hardware name: Google Google Compute Engine= /Google Compute Engine, BIOS Google 04/18/2026 2026-06-24 7.8 CVE-2026-5297=
    5 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52975 ] Linux--Linux In the=
    Linux kernel, the following vulnerability has been resolved: drm/xe: Fix e= rror cleanup in xe_exec_queue_create_ioctl() Two error handling issues exis=
    t in xe_exec_queue_create_ioctl(): 1. When xe_hw_engine_group_add_exec_queu= e() fails, the error path jumps to put_exec_queue which skips xe_exec_queue= _kill(). If the VM is in preempt fence mode, xe_vm_add_compute_exec_queue()=
    has already added the queue to the VM's compute exec queue list. Skipping = the kill leaves the queue on that list, leading to a dangling pointer after=
    the queue is freed. 2. When xa_alloc() fails after xe_hw_engine_group_add_= exec_queue() has succeeded, the error path does not call xe_hw_engine_group= _del_exec_queue() to remove the queue from the hw engine group list. The qu= eue is then freed while still linked into the hw engine group, causing a us= e-after-free. Fix both by: - Changing the xe_hw_engine_group_add_exec_queue=
    () failure path to jump to kill_exec_queue so that xe_exec_queue_kill() pro= perly removes the queue from the VM's compute list. - Adding a del_hw_engin= e_group label before kill_exec_queue for the xa_alloc() failure path, which=
    removes the queue from the hw engine group before proceeding with the rest=
    of the cleanup. (cherry picked from commit 37c831f401746a45d510b312b0ed7a7= 7b1e06ec8) 2026-06-24 7.8 CVE-2026-52976 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-52976 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: neigh: let neigh_xmit take skb ownership neigh_xm=
    it always releases the skb, except when no neighbour table is found. But ev=
    en the first added user of neigh_xmit (mpls) relied on neigh_xmit to releas=
    e the skb (or queue it for tx). sashiko reported: If neigh_xmit() is called=
    with an uninitialized neighbor table (for example, NEIGH_ND_TABLE when IPv=
    6 is disabled), it returns -EAFNOSUPPORT and bypasses its internal out_kfre= e_skb error path. Because the return value of neigh_xmit() is ignored here,=
    does this leak the SKB? Assume full ownership and remove the last code pat=
    h that doesn't xmit or free skb. 2026-06-24 7.5 CVE-2026-52981 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-52981 ] Linux--Linux In the Linux kernel,=
    the following vulnerability has been resolved: net: airoha: fix BQL imbala= nce in TX path Fix a possible BQL imbalance in airoha_dev_xmit(), where inf= light packets are accounted only for the AIROHA_NUM_TX_RING netdev TX queue=
    s. The queue index is computed as: qid =3D skb_get_queue_mapping(skb) % ARR= AY_SIZE(qdma->q_tx) txq =3D netdev_get_tx_queue(dev, qid); However, airoha_= qdma_tx_napi_poll() accounts completions across all netdev TX queues (num_t= x_queues), leading to inconsistent BQL accounting. Also reset all netdev TX=
    queues in the ndo_stop callback. 2026-06-24 7.5 CVE-2026-52983 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-52983 ] Linux--Linux In the Linux kernel=
    , the following vulnerability has been resolved: drm/amdgpu: avoid double d= rm_exec_fini() in userq validate When new_addition is true, amdgpu_userq_vm= _validate() calls drm_exec_fini(&exec) before iterating over the collected = HMM ranges and calling amdgpu_ttm_tt_get_user_pages(). If amdgpu_ttm_tt_get= _user_pages() fails in that path, the code jumps to unlock_all and calls dr= m_exec_fini(&exec) a second time on the same exec object. drm_exec_fini() i=
    s not idempotent: it frees exec->objects and may also drop exec->contended = and finalize the ww acquire context. Route that error path directly to the = range cleanup once exec has already been finalized. Issue found using a pro= totype static analysis tool and confirmed by code review. (cherry picked fr=
    om commit 2802952e4a07306da6ebe813ff1acacc5691851a) 2026-06-24 7.8 CVE-2026= -52987 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52987 ] Linux--Linux I=
    n the Linux kernel, the following vulnerability has been resolved: netfilte=
    r: nf_tables: join hook list via splice_list_rcu() in commit phase Publish = new hooks in the list into the basechain/flowtable using splice_list_rcu() =
    to ensure netlink dump list traversal via rcu is safe while concurrent rule= set update is going on. 2026-06-24 7.1 CVE-2026-52988 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-52988 ] Linux--Linux In the Linux kernel, the foll= owing vulnerability has been resolved: sched/psi: fix race between file rel= ease and pressure write A potential race condition exists between pressure = write and cgroup file release regarding the priv member of struct kernfs_op= en_file, which triggers the uaf reported in [1]. Consider the following sce= nario involving execution on two separate CPUs: CPU0 CPU1 =3D=3D=3D=3D =3D= =3D=3D=3D vfs_rmdir() kernfs_iop_rmdir() cgroup_rmdir() cgroup_kn_lock_live=
    () cgroup_destroy_locked() cgroup_addrm_files() cgroup_rm_file() kernfs_rem= ove_by_name() kernfs_remove_by_name_ns() vfs_write() __kernfs_remove() new_= sync_write() kernfs_drain() kernfs_fop_write_iter() kernfs_drain_open_files=
    () cgroup_file_write() kernfs_release_file() pressure_write() cgroup_file_r= elease() ctx =3D of->priv; kfree(ctx); of->priv =3D NULL; cgroup_kn_unlock(=
    ) cgroup_kn_lock_live() cgroup_get(cgrp) cgroup_kn_unlock() if (ctx->psi.tr= igger) // here, trigger uaf for ctx, that is of->priv The cgroup_rmdir() is=
    protected by the cgroup_mutex, it also safeguards the memory deallocation =
    of of->priv performed within cgroup_file_release(). However, the operations=
    involving of->priv executed within pressure_write() are not entirely cover=
    ed by the protection of cgroup_mutex. Consequently, if the code in pressure= _write(), specifically the section handling the ctx variable executes after=
    cgroup_file_release() has completed, a uaf vulnerability involving of->pri=
    v is triggered. Therefore, the issue can be resolved by extending the scope=
    of the cgroup_mutex lock within pressure_write() to encompass all code pat=
    hs involving of->priv, thereby properly synchronizing the race condition oc= curring between cgroup_file_release() and pressure_write(). And, if an live=
    kn lock can be successfully acquired while executing the pressure write op= eration, it indicates that the cgroup deletion process has not yet reached = its final stage; consequently, the priv pointer within open_file cannot be = NULL. Therefore, the operation to retrieve the ctx value must be moved to a=
    point *after* the live kn lock has been successfully acquired. In another = situation, specifically after entering cgroup_kn_lock_live() but before acq= uiring cgroup_mutex, there exists a different class of race condition: CPU0=
    : write memory.pressure CPU1: write cgroup.pressure=3D0 =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D kernfs_fop_write_iter() kernfs_get_active_of(of) pressure_write() cgrou= p_kn_lock_live(memory.pressure) cgroup_tryget(cgrp) kernfs_break_active_pro= tection(kn) ... blocks on cgroup_mutex cgroup_pressure_write() cgroup_kn_lo= ck_live(cgroup.pressure) cgroup_file_show(memory.pressure, false) kernfs_sh= ow(false) kernfs_drain_open_files() cgroup_file_release(of) kfree(ctx) of->= priv =3D NULL cgroup_kn_unlock() ... acquires cgroup_mutex ctx =3D of->priv=
    ; // may now be NULL if (ctx->psi.trigger) // NULL dereference Consequently=
    , there is a possibility that of->priv is NULL, the pressure write needs to=
    check for this. Now that the scope of the cgroup_mutex has been expanded, = the original explicit cgroup_get/put operations are no longer necessary, th=
    is is because acquiring/releasing the live kn lock inherently executes a cg= roup get/put operation. [1] BUG: KASAN: slab-use-after-free in pressure_wri= te+0xa4/0x210 kernel/cgroup/cgroup.c:4011 Call Trace: pressure_write+0xa4/0= x210 kernel/cgroup/cgroup.c:4011 cgroup_file_write+0x36f/0x790 kernel/cgrou= p/cgroup.c:43 ---truncated--- 2026-06-24 7.8 CVE-2026-52991 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-52991 ] Linux--Linux In the Linux kernel, th=
    e following vulnerability has been resolved: netfilter: nfnetlink_osf: fix = potential NULL dereference in ttl check The nf_osf_ttl() function accessed = skb->dev to perform a local interface address lookup without verifying that=
    the device pointer was valid. Additionally, the implementation utilized an=
    in_dev_for_each_ifa_rcu loop to match the packet source address against lo= cal interface addresses. It assumed that packets from the same subnet shoul=
    d not see a decrement on the initial TTL. A packet might appear it is from = the same subnet but it actually isn't especially in modern environments wit=
    h containers and virtual switching. Remove the device dereference and inter= face loop. Replace the logic with a switch statement that evaluates the TTL=
    according to the ttl_check. 2026-06-24 7.5 CVE-2026-52998 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-52998 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: netfilter: nat: use kfree_rcu t=
    o release ops Florian Westphal says: "Historically this is not an issue, ev=
    en for normal base hooks: the data path doesn't use the original nf_hook_op=
    s that are used to register the callbacks. However, in v5.14 I added the ab= ility to dump the active netfilter hooks from userspace. This code will pee=
    k back into the nf_hook_ops that are available at the tail of the pointer-a= rray blob used by the datapath. The nat hooks are special, because they are=
    called indirectly from the central nat dispatcher hook. They are currently=
    invisible to the nfnl hook dump subsystem though. But once that changes th=
    e nat ops structures have to be deferred too." Update nf_nat_register_fn() =
    to deal with partial exposition of the hooks from error path which can be a= lso an issue for nfnetlink_hook. 2026-06-24 7.8 CVE-2026-53000 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-53000 ] Linux--Linux In the Linux kernel,=
    the following vulnerability has been resolved: pppoe: drop PFC frames RFC = 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMEN= DED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE=
    sessions, and the current PPPoE driver assumes an uncompressed (2-byte) pr= otocol field. However, the generic PPP layer function ppp_input() is not aw= are of the negotiation result, and still accepts PFC frames. If a peer with=
    a broken implementation or an attacker sends a frame with a compressed (1-= byte) protocol field, the subsequent PPP payload is shifted by one byte. Th=
    is causes the network header to be 4-byte misaligned, which may trigger una= ligned access exceptions on some architectures. To reduce the attack surfac=
    e, drop PPPoE PFC frames. Introduce ppp_skb_is_compressed_proto() helper fu= nction to be used in both ppp_generic.c and pppoe.c to avoid open-coding. 2= 026-06-24 7.5 CVE-2026-53003 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 53003 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: af_unix: Drop all SCM attributes for SOCKMAP. SOCKMAP can hid=
    e inflight fd from AF_UNIX GC. When a socket in SOCKMAP receives skb with i= nflight fd, sk_psock_verdict_data_ready() looks up the mapped socket and en= queue skb to its psock->ingress_skb. Since neither the old nor the new GC c=
    an inspect the psock queue, the hidden skb leaks the inflight sockets. Note=
    that this cannot be detected via kmemleak because inflight sockets are lin= ked to a global list. In addition, SOCKMAP redirect breaks the Tarjan-based=
    GC's assumption that unix_edge.successor is always alive, which is no long=
    er true once skb is redirected, resulting in use-after-free below. [0] More= over, SOCKMAP does not call scm_stat_del() properly, so unix_show_fdinfo() = could report an incorrect fd count. sk_msg_recvmsg() does not support any S=
    CM attributes in the first place. Let's drop all SCM attributes before pass= ing skb to the SOCKMAP layer. [0]: BUG: KASAN: slab-use-after-free in unix_= del_edges (net/unix/garbage.c:118 net/unix/garbage.c:181 net/unix/garbage.c= :251) Read of size 8 at addr ffff888125362670 by task kworker/56:1/496 CPU:=
    56 UID: 0 PID: 496 Comm: kworker/56:1 Not tainted 7.0.0-rc7-00263-gb9d8b85= 6689d #3 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996=
    ), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 Workqueue: events sk_psock_backlo=
    g Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:122) print_report (mm= /kasan/report.c:379) kasan_report (mm/kasan/report.c:597) unix_del_edges (n= et/unix/garbage.c:118 net/unix/garbage.c:181 net/unix/garbage.c:251) unix_d= estroy_fpl (net/unix/garbage.c:317) unix_destruct_scm (./include/net/scm.h:=
    80 ./include/net/scm.h:86 net/unix/af_unix.c:1976) sk_psock_backlog (./incl= ude/linux/skbuff.h:?) process_scheduled_works (kernel/workqueue.c:?) worker= _thread (kernel/workqueue.c:?) kthread (kernel/kthread.c:438) ret_from_fork=
    (arch/x86/kernel/process.c:164) ret_from_fork_asm (arch/x86/entry/entry_64= .S:258) </TASK> Allocated by task 955: kasan_save_track (mm/kasan/common.c:=
    58 mm/kasan/common.c:78) __kasan_slab_alloc (mm/kasan/common.c:369) kmem_ca= che_alloc_noprof (mm/slub.c:4539) sk_prot_alloc (net/core/sock.c:2240) sk_a= lloc (net/core/sock.c:2301) unix_create1 (net/unix/af_unix.c:1099) unix_cre= ate (net/unix/af_unix.c:1169) __sock_create (net/socket.c:1606) __sys_socke= tpair (net/socket.c:1811) __x64_sys_socketpair (net/socket.c:1863 net/socke= t.c:1860 net/socket.c:1860) do_syscall_64 (arch/x86/entry/syscall_64.c:?) e= ntry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Freed by task=
    496: kasan_save_track (mm/kasan/common.c:58 mm/kasan/common.c:78) kasan_sa= ve_free_info (mm/kasan/generic.c:587) __kasan_slab_free (mm/kasan/common.c:= 287) kmem_cache_free (mm/slub.c:6165) __sk_destruct (net/core/sock.c:2282 n= et/core/sock.c:2384) sk_psock_destroy (./include/net/sock.h:?) process_sche= duled_works (kernel/workqueue.c:?) worker_thread (kernel/workqueue.c:?) kth= read (kernel/kthread.c:438) ret_from_fork (arch/x86/kernel/process.c:164) r= et_from_fork_asm (arch/x86/entry/entry_64.S:258) 2026-06-24 7.8 CVE-2026-53= 005 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53005 ] Linux--Linux In t=
    he Linux kernel, the following vulnerability has been resolved: ice: fix do= uble-free of tx_buf skb If ice_tso() or ice_tx_csum() fail, the error path =
    in ice_xmit_frame_ring() frees the skb, but the 'first' tx_buf still points=
    to it and is marked as valid (ICE_TX_BUF_SKB). 'next_to_use' remains uncha= nged, so the potential problem will likely fix itself when the next packet =
    is transmitted and the tx_buf gets overwritten. But if there is no next pac= ket and the interface is brought down instead, ice_clean_tx_ring() -> ice_u= nmap_and_free_tx_buf() will find the tx_buf and free the skb for the second=
    time. The fix is to reset the tx_buf type to ICE_TX_BUF_EMPTY in the error=
    path, so that ice_unmap_and_free_tx_buf(). Move the initialization of 'fir= st' up, to ensure it's already valid in case we hit the linearization error=
    path. The bug was spotted by AI while I had it looking for something else.=
    It also proposed an initial version of the patch. I reproduced the bug and=
    tested the fix by adding code to inject failures, on a build with KASAN. I=
    looked for similar bugs in related Intel drivers and did not find any. 202= 6-06-24 7.8 CVE-2026-53009 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53= 009 ] Linux--Linux In the Linux kernel, the following vulnerability has bee=
    n resolved: net/sched: taprio: fix use-after-free in advance_sched() on sch= edule switch In advance_sched(), when should_change_schedules() returns tru=
    e, switch_schedules() is called to promote the admin schedule to oper. swit= ch_schedules() queues the old oper schedule for RCU freeing via call_rcu(),=
    but 'next' still points into an entry of the old oper schedule. The subseq= uent 'next->end_time =3D end_time' and rcu_assign_pointer(q->current_entry,=
    next) are use-after-free. Fix this by selecting 'next' from the new oper s= chedule immediately after switch_schedules(), and using its pre-calculated = end_time. setup_first_end_time() sets the first entry's end_time to base_ti=
    me + interval when the schedule is installed, so the value is already corre= ct. The deleted 'end_time =3D sched_base_time(admin)' assignment was also h= armful independently: it would overwrite the new first entry's pre-calculat=
    ed end_time with just base_time. 2026-06-24 7.8 CVE-2026-53011 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-53011 ] Linux--Linux In the Linux kernel,=
    the following vulnerability has been resolved: crypto: ccp - copy IV using=
    skcipher ivsize AF_ALG rfc3686-ctr-aes-ccp requests pass an 8-byte IV to t=
    he driver. ccp_aes_complete() restores AES_BLOCK_SIZE bytes into the caller=
    's IV buffer while RFC3686 skciphers expose an 8-byte IV, so the restore ov= erruns the provided buffer. Use crypto_skcipher_ivsize() to copy only the a= lgorithm's IV length. 2026-06-24 7.8 CVE-2026-53016 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-53016 ] Linux--Linux In the Linux kernel, the follow= ing vulnerability has been resolved: um: Fix potential race condition in TL=
    B sync During the TLB sync, we need to traverse and modify the page table, =
    so we should hold the page table lock. Since full SMP support for threads w= ithin the same process is still missing, let's disable the split page table=
    lock for simplicity. 2026-06-24 7.8 CVE-2026-53020 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-53020 ] Linux--Linux In the Linux kernel, the follow= ing vulnerability has been resolved: greybus: raw: fix use-after-free if wr= ite is called after disconnect If a user writes to the chardev after discon= nect has been called, the kernel panics with the following trace (with CONF= IG_INIT_ON_FREE_DEFAULT_ON=3Dy): BUG: kernel NULL pointer dereference, addr= ess: 0000000000000218 ... Call Trace: <TASK> gb_operation_create_common+0x6= 1/0x180 gb_operation_create_flags+0x28/0xa0 gb_operation_sync_timeout+0x6f/= 0x100 raw_write+0x7b/0xc7 [gb_raw] vfs_write+0xcf/0x420 ? task_mm_cid_work+= 0x136/0x220 ksys_write+0x63/0xe0 do_syscall_64+0xa4/0x290 entry_SYSCALL_64_= after_hwframe+0x77/0x7f Disconnect calls gb_connection_destroy, which ends =
    up freeing the connection object. When gb_operation_sync is called in the w= rite file operations, its gets a freed connection as parameter and the kern=
    el panics. The gb_connection_destroy cannot be moved out of the disconnect = function, as the Greybus subsystem expect all connections belonging to a bu= ndle to be destroyed when disconnect returns. To prevent this bug, use a rw=
    lock to synchronize access between write and disconnect. This guarantees t= hat the write function doesn't try to use a disconnected connection. 2026-0= 6-24 7.8 CVE-2026-53024 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53024=
    ] Linux--Linux In the Linux kernel, the following vulnerability has been r= esolved: greybus: raw: fix use-after-free on cdev close This addresses a us= e-after-free bug when a raw bundle is disconnected but its chardev is still=
    opened by an application. When the application releases the cdev, it cause=
    s the following panic when init on free is enabled (CONFIG_INIT_ON_FREE_DEF= AULT_ON=3Dy): refcount_t: underflow; use-after-free. WARNING: CPU: 0 PID: 1=
    39 at lib/refcount.c:28 refcount_warn_saturate+0xd0/0x130 ... Call Trace: <= TASK> cdev_put+0x18/0x30 __fput+0x255/0x2a0 __x64_sys_close+0x3d/0x80 do_sy= scall_64+0xa4/0x290 entry_SYSCALL_64_after_hwframe+0x77/0x7f The cdev is co= ntained in the "gb_raw" structure, which is freed in the disconnect operati= on. When the cdev is released at a later time, cdev_put gets an address tha=
    t points to freed memory. To fix this use-after-free, convert the struct de= vice from a pointer to being embedded, that makes the lifetime of the cdev = and of this device the same. Then, use cdev_device_add, which guarantees th=
    at the device won't be released until all references to the cdev have been = released. Finally, delegate the freeing of the structure to the device rele= ase function, instead of freeing immediately in the disconnect callback. 20= 26-06-24 7.8 CVE-2026-53025 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 3025 ] Linux--Linux In the Linux kernel, the following vulnerability has be=
    en resolved: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_t= o_wrdeleg In nfsd4_add_rdaccess_to_wrdeleg, if fp->fi_fds[O_RDONLY] is alre= ady set by another thread, __nfs4_file_get_access should not be called to i= ncrement the nfs4_file access count since that was already done by the thre=
    ad that added READ access to the file. The extra fi_access count in nfs4_fi=
    le can prevent the corresponding nfsd_file from being freed. When stopping = nfs-server service, these extra access counts trigger a BUG in kmem_cache_d= estroy() that shows nfsd_file object remaining on __kmem_cache_shutdown. Th=
    is problem can be reproduced by running the Git project's test suite over N= FS. 2026-06-24 7.5 CVE-2026-53026 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-53026 ] Linux--Linux In the Linux kernel, the following vulnerability = has been resolved: bpf: Validate node_id in arena_alloc_pages() arena_alloc= _pages() accepts a plain int node_id and forwards it through the entire all= ocation chain without any bounds checking. Validate node_id before passing =
    it down the allocation chain in arena_alloc_pages(). 2026-06-24 7.8 CVE-202= 6-53031 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53031 ] Linux--Linux =
    In the Linux kernel, the following vulnerability has been resolved: bpf, so= ckmap: Take state lock for af_unix iter When a BPF iterator program updates=
    a sockmap, there is a race condition in unix_stream_bpf_update_proto() whe=
    re the `peer` pointer can become stale[1] during a state transition TCP_EST= ABLISHED -> TCP_CLOSE. CPU0 bpf CPU1 close -------- ---------- // unix_stre= am_bpf_update_proto() sk_pair =3D unix_peer(sk) if (unlikely(!sk_pair)) ret= urn -EINVAL; // unix_release_sock() skpair =3D unix_peer(sk); unix_peer(sk)=
    =3D NULL; sock_put(skpair) sock_hold(sk_pair) // UaF More practically, thi=
    s fix guarantees that the iterator program is consistently provided with a = unix socket that remains stable during iterator execution. [1]: BUG: KASAN:=
    slab-use-after-free in unix_stream_bpf_update_proto+0x155/0x490 Write of s= ize 4 at addr ffff8881178c9a00 by task test_progs/2231 Call Trace: dump_sta= ck_lvl+0x5d/0x80 print_report+0x170/0x4f3 kasan_report+0xe4/0x1c0 kasan_che= ck_range+0x125/0x200 unix_stream_bpf_update_proto+0x155/0x490 sock_map_link= +0x71c/0xec0 sock_map_update_common+0xbc/0x600 sock_map_update_elem+0x19a/0= x1f0 bpf_prog_bbbf56096cdd4f01_selective_dump_unix+0x20c/0x217 bpf_iter_run= _prog+0x21e/0xae0 bpf_iter_unix_seq_show+0x1e0/0x2a0 bpf_seq_read+0x42c/0x1= 0d0 vfs_read+0x171/0xb20 ksys_read+0xff/0x200 do_syscall_64+0xf7/0x5e0 entr= y_SYSCALL_64_after_hwframe+0x76/0x7e Allocated by task 2236: kasan_save_sta= ck+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_slab_alloc+0x63/0x80 kmem_c= ache_alloc_noprof+0x1d5/0x680 sk_prot_alloc+0x59/0x210 sk_alloc+0x34/0x470 = unix_create1+0x86/0x8a0 unix_stream_connect+0x318/0x15b0 __sys_connect+0xfd= /0x130 __x64_sys_connect+0x72/0xd0 do_syscall_64+0xf7/0x5e0 entry_SYSCALL_6= 4_after_hwframe+0x76/0x7e Freed by task 2236: kasan_save_stack+0x30/0x50 ka= san_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x70 __kasan_slab_free+0= x47/0x70 kmem_cache_free+0x11c/0x590 __sk_destruct+0x432/0x6e0 unix_release= _sock+0x9b3/0xf60 unix_release+0x8a/0xf0 __sock_release+0xb0/0x270 sock_clo= se+0x18/0x20 __fput+0x36e/0xac0 fput_close_sync+0xe5/0x1a0 __x64_sys_close+= 0x7d/0xd0 do_syscall_64+0xf7/0x5e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e=
    2026-06-24 7.8 CVE-2026-53033 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-53033 ] Linux--Linux In the Linux kernel, the following vulnerability has=
    been resolved: bpf, arm64: Fix off-by-one in check_imm signed range check = check_imm(bits, imm) is used in the arm64 BPF JIT to verify that a branch d= isplacement (in arm64 instruction units) fits into the signed N-bit immedia=
    te field of a B, B.cond or CBZ/CBNZ encoding before it is handed to the enc= oder. The macro currently tests for (imm > 0 && imm >> bits) || (imm < 0 &&=
    ~imm >> bits) which admits values in [-2^N, 2^N) - effectively a signed (N= +1)-bit range. A signed N-bit field only holds [-2^(N-1), 2^(N-1)), so the = check admits one extra bit of range on each side. In particular, for check_= imm19(), values in [2^18, 2^19) slip past the check but do not fit into the=
    19-bit signed imm19 field of B.cond. aarch64_insn_encode_immediate() then = masks the raw value into the 19-bit field, setting bit 18 (the sign bit) an=
    d flipping a forward branch into a backward one. Same class of issue exists=
    for check_imm26() and the B/BL encoding. Shift by (bits - 1) instead of bi=
    ts so the actual signed N-bit range is enforced. 2026-06-24 7.8 CVE-2026-53= 036 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53036 ] Linux--Linux In t=
    he Linux kernel, the following vulnerability has been resolved: ocfs2: vali= date bg_bits during freefrag scan [BUG] A crafted filesystem can trigger an=
    out-of-bounds bitmap walk when OCFS2_IOC_INFO is issued with OCFS2_INFO_FL= _NON_COHERENT. BUG: KASAN: use-after-free in instrument_atomic_read include= /linux/instrumented.h:68 [inline] BUG: KASAN: use-after-free in _test_bit i= nclude/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] BUG: KASAN=
    : use-after-free in test_bit_le include/asm-generic/bitops/le.h:21 [inline]=
    BUG: KASAN: use-after-free in ocfs2_info_freefrag_scan_chain fs/ocfs2/ioct= l.c:495 [inline] BUG: KASAN: use-after-free in ocfs2_info_freefrag_scan_bit= map fs/ocfs2/ioctl.c:588 [inline] BUG: KASAN: use-after-free in ocfs2_info_= handle_freefrag fs/ocfs2/ioctl.c:662 [inline] BUG: KASAN: use-after-free in=
    ocfs2_info_handle_request+0x1c66/0x3370 fs/ocfs2/ioctl.c:754 Read of size =
    8 at addr ffff888031bce000 by task syz.0.636/1435 Call Trace: __dump_stack = lib/dump_stack.c:94 [inline] dump_stack_lvl+0xbe/0x130 lib/dump_stack.c:120=
    print_address_description mm/kasan/report.c:378 [inline] print_report+0xd1= /0x650 mm/kasan/report.c:482 kasan_report+0xfb/0x140 mm/kasan/report.c:595 = check_region_inline mm/kasan/generic.c:186 [inline] kasan_check_range+0x11c= /0x200 mm/kasan/generic.c:200 __kasan_check_read+0x11/0x20 mm/kasan/shadow.= c:31 instrument_atomic_read include/linux/instrumented.h:68 [inline] _test_= bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] test_= bit_le include/asm-generic/bitops/le.h:21 [inline] ocfs2_info_freefrag_scan= _chain fs/ocfs2/ioctl.c:495 [inline] ocfs2_info_freefrag_scan_bitmap fs/ocf= s2/ioctl.c:588 [inline] ocfs2_info_handle_freefrag fs/ocfs2/ioctl.c:662 [in= line] ocfs2_info_handle_request+0x1c66/0x3370 fs/ocfs2/ioctl.c:754 ocfs2_in= fo_handle+0x18d/0x2a0 fs/ocfs2/ioctl.c:828 ocfs2_ioctl+0x632/0x6e0 fs/ocfs2= /ioctl.c:913 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597=
    [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x197/0x1e=
    0 fs/ioctl.c:583 ... [CAUSE] ocfs2_info_freefrag_scan_chain() uses on-disk = bg_bits directly as the bitmap scan limit. The coherent path reads group de= scriptors through ocfs2_read_group_descriptor(), which validates the descri= ptor before use. The non-coherent path uses ocfs2_read_blocks_sync() instea=
    d and skips that validation, so an impossible bg_bits value can drive the b= itmap walk past the end of the block. [FIX] Compute the bitmap capacity fro=
    m the filesystem format with ocfs2_group_bitmap_size(), report descriptors = whose bg_bits exceeds that limit, and clamp the scan to the computed capaci= ty. This keeps the freefrag report going while avoiding reads beyond the bu= ffer. 2026-06-24 7.1 CVE-2026-53040 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-53040 ] Linux--Linux In the Linux kernel, the following vulnerabilit=
    y has been resolved: ocfs2: fix listxattr handling when the buffer is full = [BUG] If an OCFS2 inode has both inline and block-based xattrs, listxattr()=
    can return a size larger than the caller's buffer when the inline names co= nsume that buffer exactly. kernel BUG at mm/usercopy.c:102! Oops: invalid o= pcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010:usercopy_abort+0xb7/0xd0 mm/user= copy.c:102 Call Trace: __check_heap_object+0xe3/0x120 mm/slub.c:8243 check_= heap_object mm/usercopy.c:196 [inline] __check_object_size mm/usercopy.c:25=
    0 [inline] __check_object_size+0x5c5/0x780 mm/usercopy.c:215 check_object_s= ize include/linux/ucopysize.h:22 [inline] check_copy_size include/linux/uco= pysize.h:59 [inline] copy_to_user include/linux/uaccess.h:219 [inline] list= xattr+0xb0/0x170 fs/xattr.c:926 filename_listxattr fs/xattr.c:958 [inline] = path_listxattrat+0x137/0x320 fs/xattr.c:988 __do_sys_listxattr fs/xattr.c:1= 001 [inline] __se_sys_listxattr fs/xattr.c:998 [inline] __x64_sys_listxattr= +0x7f/0xd0 fs/xattr.c:998 ... [CAUSE] Commit 936b8834366e ("ocfs2: Refactor=
    xattr list and remove ocfs2_xattr_handler().") replaced the old per-handle=
    r list accounting with ocfs2_xattr_list_entry(), but it kept using size =3D= =3D 0 to detect probe mode. That assumption stops being true once ocfs2_lis= txattr() finishes the inline-xattr pass. If the inline names fill the calle=
    r buffer exactly, the block-xattr pass runs with a non-NULL buffer and a re= maining size of zero. ocfs2_xattr_list_entry() then skips the bounds check,=
    keeps counting block names, and returns a positive size larger than the su= pplied buffer. [FIX] Detect probe mode by testing whether the destination b= uffer pointer is NULL instead of whether the remaining size is zero. That r= estores the pre-refactor behavior and matches the OCFS2 getxattr helpers. O= nce the remaining buffer reaches zero while more names are left, the block-= xattr pass now returns -ERANGE instead of reporting a size larger than the = allocated list buffer. 2026-06-24 7.1 CVE-2026-53041 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-53041 ] Linux--Linux In the Linux kernel, the follo= wing vulnerability has been resolved: soc/tegra: cbb: Fix incorrect ARRAY_S= IZE in fabric lookup tables Fix incorrect ARRAY_SIZE usage in fabric lookup=
    tables which could cause out-of-bounds access during target timeout lookup=
    . 2026-06-24 7.1 CVE-2026-53044 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-53044 ] Linux--Linux In the Linux kernel, the following vulnerability ha=
    s been resolved: quota: Fix race of dquot_scan_active() with quota deactiva= tion dquot_scan_active() can race with quota deactivation in quota_release_= workfn() like: CPU0 (quota_release_workfn) CPU1 (dquot_scan_active) =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D spin_lock(&dq_list_lock); list_replace_init( &r= eleasing_dquots, &rls_head); /* dquot X on rls_head, dq_count =3D=3D 0, DQ_= ACTIVE_B still set */ spin_unlock(&dq_list_lock); synchronize_srcu(&dquot_s= rcu); spin_lock(&dq_list_lock); list_for_each_entry(dquot, &inuse_list, dq_= inuse) { /* finds dquot X */ dquot_active(X) -> true atomic_inc(&X->dq_coun= t); } spin_unlock(&dq_list_lock); spin_lock(&dq_list_lock); dquot =3D list_= first_entry(&rls_head); WARN_ON_ONCE(atomic_read(&dquot->dq_count)); The pr= oblem is not only a cosmetic one as under memory pressure the caller of dqu= ot_scan_active() can end up working on freed dquot. Fix the problem by maki=
    ng sure the dquot is removed from releasing list when we acquire a referenc=
    e to it. 2026-06-24 7.8 CVE-2026-53050 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53050 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: drm/msm: Fix VM_BIND UNMAP locking Wrong argument=
    meant that the objs involved in UNMAP ops were not always getting locked. = Since _NO_SHARE objs share a common resv with the VM (which is always locke=
    d) this would only show up with non-_NO_SHARE BOs. Patchwork: https://patch= work.freedesktop.org/patch/713898/ 2026-06-24 7.8 CVE-2026-53054 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-53054 ] Linux--Linux In the Linux kerne=
    l, the following vulnerability has been resolved: dm cache policy smq: fix = missing locks in invalidating cache blocks In passthrough mode, the policy = invalidate_mapping operation is called simultaneously from multiple workers=
    , thus it should be protected by a lock. Otherwise, we might end up with da=
    ta races on the allocated blocks counter, or even use-after-free issues wit=
    h internal data structures when doing concurrent writes. Note that the exis= ting FIXME in smq_invalidate_mapping() doesn't affect passthrough mode sinc=
    e migration tasks don't exist there, but would need attention if supporting=
    fast device shrinking via suspend/resume without target reloading. Reprodu=
    ce steps: 1. Create a cache device consisting of 1024 cache entries dmsetup=
    create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --tab=
    le "0 131072 linear /dev/sdc 8192" dmsetup create corig --table "0 262144 l= inear /dev/sdc 262144" dd if=3D/dev/zero of=3D/dev/mapper/cmeta bs=3D4k cou= nt=3D1 oflag=3Ddirect dmsetup create cache --table "0 262144 cache /dev/map= per/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethroug=
    h smq 0" 2. Populate the cache, and record the number of cached blocks fio = --name=3Dpopulate --filename=3D/dev/mapper/cache --rw=3Drandwrite --bs=3D4k=
    \ --size=3D64m --direct=3D1 nr_cached=3D$(dmsetup status cache | awk '{spl= it($7, a, "/"); print a[1]}') 3. Reload the cache into passthrough mode dms= etup suspend cache dmsetup reload cache --table "0 262144 cache /dev/mapper= /cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough sm=
    q 0" dmsetup resume cache 4. Write to the passthrough cache. By setting mul= tiple jobs with I/O size equal to the cache block size, cache blocks are in= validated concurrently from different workers. fio --filename=3D/dev/mapper= /cache --name=3Dtest --rw=3Drandwrite --bs=3D64k \ --direct=3D1 --numjobs=
    =3D2 --randrepeat=3D0 --size=3D64m 5. Check if demoted matches cached block=
    count. These numbers should match but may differ due to the data race. nr_= demoted=3D$(dmsetup status cache | awk '{print $12}') echo "$nr_cached, $nr= _demoted" 2026-06-24 7.8 CVE-2026-53062 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53062 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: drm/komeda: fix integer overflow in AFBC framebuf= fer size check The AFBC framebuffer size validation calculates the minimum = required buffer size by adding the AFBC payload size to the framebuffer off= set. This addition is performed without checking for integer overflow. If t=
    he addition oveflows, the size check may incorrectly succed and allow users= pace to provide an undersized drm_gem_object, potentially leading to out-of= -bounds memory access. Add usage of check_add_overflow() to safely compute = the minimum required size and reject the framebuffer if an overflow is dete= cted. This makes the AFBC size validation more robust against malformed. Fo= und by Linux Verification Center (linuxtesting.org) with SVACE. 2026-06-24 = 7.1 CVE-2026-53068 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53068 ] Li= nux--Linux In the Linux kernel, the following vulnerability has been resolv= ed: net, bpf: fix null-ptr-deref in xdp_master_redirect() for down master s= yzkaller reported a kernel panic in bond_rr_gen_slave_id() reached via xdp_= master_redirect(). Full decoded trace: https://syzkaller.appspot.com/bug?ex= tid=3D80e046b8da2820b6ba73 bond_rr_gen_slave_id() dereferences bond->rr_tx_= counter, a per-CPU counter that bonding only allocates in bond_open() when = the mode is round-robin. If the bond device was never brought up, rr_tx_cou= nter stays NULL. The XDP redirect path can still reach that code on a bond = that was never opened: bpf_master_redirect_enabled_key is a global static k= ey, so as soon as any bond device has native XDP attached, the XDP_TX -> xd= p_master_redirect() interception is enabled for every slave system-wide. Th=
    e path xdp_master_redirect() -> bond_xdp_get_xmit_slave() -> bond_xdp_xmit_= roundrobin_slave_get() -> bond_rr_gen_slave_id() then runs against a bond t= hat has no rr_tx_counter and crashes. Fix this in the generic xdp_master_re= direct() by refusing to call into the master's ->ndo_xdp_get_xmit_slave() w= hen the master device is not up. IFF_UP is only set after ->ndo_open() has = successfully returned, so this reliably excludes masters whose XDP state ha=
    s not been fully initialized. Drop the frame with XDP_ABORTED so the except= ion is visible via trace_xdp_exception() rather than silently falling throu= gh. This is not specific to bonding: any current or future master that defe=
    rs XDP state allocation to ->ndo_open() is protected. 2026-06-24 7.5 CVE-20= 26-53069 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53069 ] Linux--Linux=
    In the Linux kernel, the following vulnerability has been resolved: sctp: = disable BH before calling udp_tunnel_xmit_skb() udp_tunnel_xmit_skb() / udp= _tunnel6_xmit_skb() are expected to run with BH disabled. After commit 6f1a= 9140ecda ("add xmit recursion limit to tunnel xmit functions"), on the path=
    : udp(6)_tunnel_xmit_skb() -> ip(6)tunnel_xmit() dev_xmit_recursion_inc()/d= ec() must stay balanced on the same CPU. Without local_bh_disable(), the co= ntext may move between CPUs, which can break the inc/dec pairing. This may = lead to incorrect recursion level detection and cause packets to be dropped=
    in ip(6)_tunnel_xmit() or __dev_queue_xmit(). Fix it by disabling BH aroun=
    d both IPv4 and IPv6 SCTP UDP xmit paths. In my testing, after enabling the=
    SCTP over UDP: # ip net exec ha sysctl -w net.sctp.udp_port=3D9899 # ip ne=
    t exec ha sysctl -w net.sctp.encap_port=3D9899 # ip net exec hb sysctl -w n= et.sctp.udp_port=3D9899 # ip net exec hb sysctl -w net.sctp.encap_port=3D98=
    99 # ip net exec ha iperf3 -s - without this patch: # ip net exec hb iperf3=
    -c 192.168.0.1 --sctp [ 5] 0.00-10.00 sec 37.2 MBytes 31.2 Mbits/sec sende=
    r [ 5] 0.00-10.00 sec 37.1 MBytes 31.1 Mbits/sec receiver - with this patch=
    : # ip net exec hb iperf3 -c 192.168.0.1 --sctp [ 5] 0.00-10.00 sec 3.14 GB= ytes 2.69 Gbits/sec sender [ 5] 0.00-10.00 sec 3.14 GBytes 2.69 Gbits/sec r= eceiver 2026-06-24 7.5 CVE-2026-53070 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-53070 ] Linux--Linux In the Linux kernel, the following vulnerabil= ity has been resolved: bpf: Fix OOB in pcpu_init_value An out-of-bounds rea=
    d occurs when copying element from a BPF_MAP_TYPE_CGROUP_STORAGE map to ano= ther pcpu map with the same value_size that is not rounded up to 8 bytes. T=
    he issue happens when: 1. A CGROUP_STORAGE map is created with value_size n=
    ot aligned to 8 bytes (e.g., 4 bytes) 2. A pcpu map is created with the sam=
    e value_size (e.g., 4 bytes) 3. Update element in 2 with data in 1 pcpu_ini= t_value assumes that all sources are rounded up to 8 bytes, and invokes cop= y_map_value_long to make a data copy, However, the assumption doesn't stand=
    since there are some cases where the source may not be rounded up to 8 byt= es, e.g., CGROUP_STORAGE, skb->data. the verifier verifies exactly the size=
    that the source claims, not the size rounded up to 8 bytes by kernel, an O=
    OB happens when the source has only 4 bytes while the copy size(4) is round=
    ed up to 8. 2026-06-24 7.1 CVE-2026-53076 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-53076 ] Linux--Linux In the Linux kernel, the following vulner= ability has been resolved: net/rds: Restrict use of RDS/IB to the initial n= etwork namespace Prevent using RDS/IB in network namespaces other than the = initial one. The existing RDS/IB code will not work properly in non-initial=
    network namespaces. 2026-06-24 7.8 CVE-2026-53077 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-53077 ] Linux--Linux In the Linux kernel, the followi=
    ng vulnerability has been resolved: bpf: Fix same-register dst/src OOB read=
    and pointer leak in sock_ops When a BPF sock_ops program accesses ctx fiel=
    ds with dst_reg =3D=3D src_reg, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIEL= D() macros fail to zero the destination register in the !fullsock / !locked= _tcp_sock path. Both macros borrow a temporary register to check is_fullsoc=
    k / is_locked_tcp_sock when dst_reg =3D=3D src_reg, because dst_reg holds t=
    he ctx pointer. When the check is false (e.g., TCP_NEW_SYN_RECV state with =
    a request_sock), dst_reg should be zeroed but is not, leaving the stale ctx=
    pointer: - SOCK_OPS_GET_SK: dst_reg retains the ctx pointer, passes NULL c= hecks as PTR_TO_SOCKET_OR_NULL, and can be used as a bogus socket pointer, = leading to stack-out-of-bounds access in helpers like bpf_skc_to_tcp6_sock(=
    ). - SOCK_OPS_GET_FIELD: dst_reg retains the ctx pointer which the verifier=
    believes is a SCALAR_VALUE, leaking a kernel pointer. Fix both macros by: =
    - Changing JMP_A(1) to JMP_A(2) in the fullsock path to skip the added inst= ruction. - Adding BPF_MOV64_IMM(si->dst_reg, 0) after the temp register res= tore in the !fullsock path, placed after the restore because dst_reg =3D=3D=
    src_reg means we need src_reg intact to read ctx->temp. 2026-06-24 7.8 CVE= -2026-53078 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53078 ] Linux--Li= nux In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Enforce regsafe base id consistency for BPF_ADD_CONST scalars When regsaf= e() compares two scalar registers that both carry BPF_ADD_CONST, check_scal= ar_ids() maps their full compound id (aka base | BPF_ADD_CONST flag) as one=
    idmap entry. However, it never verifies that the underlying base ids, that=
    is, with the flag stripped are consistent with existing idmap mappings. Th=
    is allows construction of two verifier states where the old state has R3 =
    =3D R2 + 10 (both sharing base id A) while the current state has R3 =3D R4 =
    + 10 (base id C, unrelated to R2). The idmap creates two independent entrie=
    s: A->B (for R2) and A|flag->C|flag (for R3), without catching that A->C co= nflicts with A->B. State pruning then incorrectly succeeds. Fix this by add= itionally verifying base ID mapping consistency whenever BPF_ADD_CONST is s= et: after mapping the compound ids, also invoke check_ids() on the base IDs=
    (flag bits stripped). This ensures that if A was already mapped to B from = comparing the source register, any ADD_CONST derivative must also derive fr=
    om B, not an unrelated C. 2026-06-24 7.8 CVE-2026-53081 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-53081 ] Linux--Linux In the Linux kernel, the fo= llowing vulnerability has been resolved: bpf: fix mm lifecycle in open-code=
    d task_vma iterator The open-coded task_vma iterator reads task->mm lockles= sly and acquires mmap_read_trylock() but never calls mmget(). If the task e= xits concurrently, the mm_struct can be freed as it is not SLAB_TYPESAFE_BY= _RCU, resulting in a use-after-free. Safely read task->mm with a trylock on=
    alloc_lock and acquire an mm reference. Drop the reference via bpf_iter_mm= put_async() in _destroy() and error paths. bpf_iter_mmput_async() is a loca=
    l wrapper around mmput_async() with a fallback to mmput() on !CONFIG_MMU. R= eject irqs-disabled contexts (including NMI) up front. Operations used by _= next() and _destroy() (mmap_read_unlock, bpf_iter_mmput_async) take spinloc=
    ks with IRQs disabled (pool->lock, pi_lock). Running from NMI or from a tra= cepoint that fires with those locks held could deadlock. A trylock on alloc= _lock is used instead of the blocking task_lock() (get_task_mm) to avoid a = deadlock when a softirq BPF program iterates a task that already holds its = alloc_lock on the same CPU. 2026-06-24 7.8 CVE-2026-53085 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-53085 ] Linux--Linux In the Linux kernel, the = following vulnerability has been resolved: net: bcmgenet: fix leaking free_= bds While reclaiming the tx queue we fast forward the write pointer to drop=
    any data in flight. These dropped frames are not added back to the pool of=
    free bds. We also need to tell the netdev that we are dropping said data. = 2026-06-24 7.5 CVE-2026-53087 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -53087 ] Linux--Linux In the Linux kernel, the following vulnerability has = been resolved: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usag=
    e of ld_{abs,ind} instructions got extended into subprogs some time ago via=
    commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only a= llowed in subprograms when the latter are BTF annotated and have scalar ret= urn types. The code generator in bpf_gen_ld_abs() has an abnormal exit path=
    (r0=3D0 + exit) from legacy cBPF times. While the enforcement is on scalar=
    return types, the verifier must also simulate the path of abnormal exit if=
    the packet data load via ld_{abs,ind} failed. This is currently not the ca= se. Fix it by having the verifier simulate both success and failure paths, = and extend it in similar ways as we do for tail calls. The success path (r0= =3Dunknown, continue to next insn) is pushed onto stack for later validatio=
    n and the r0=3D0 and return to the caller is done on the fall-through side.=
    2026-06-24 7.8 CVE-2026-53090 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-53090 ] Linux--Linux In the Linux kernel, the following vulnerability has=
    been resolved: bpf: Fix linked reg delta tracking when src_reg =3D=3D dst_= reg Consider the case of rX +=3D rX where src_reg and dst_reg are pointers =
    to the same bpf_reg_state in adjust_reg_min_max_vals(). The latter first mo= difies the dst_reg in-place, and later in the delta tracking, the subsequen=
    t is_reg_const(src_reg)/reg_const_value(src_reg) reads the post-{add,sub} v= alue instead of the original source. This is problematic since it sets an i= ncorrect delta, which sync_linked_regs() then propagates to linked register=
    s, thus creating a verifier-vs-runtime mismatch. Fix it by just skipping th=
    is corner case. 2026-06-24 7.8 CVE-2026-53092 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-53092 ] Linux--Linux In the Linux kernel, the following vu= lnerability has been resolved: bpf: Fix stale offload->prog pointer after c= onstant blinding When a dev-bound-only BPF program (BPF_F_XDP_DEV_BOUND_ONL=
    Y) undergoes JIT compilation with constant blinding enabled (bpf_jit_harden=
    =3D 2), bpf_jit_blind_constants() clones the program. The original prog i=
    s then freed in bpf_jit_prog_release_other(), which updates aux->prog to po= int to the surviving clone, but fails to update offload->prog. This leaves = offload->prog pointing to the freed original program. When the network name= space is subsequently destroyed, cleanup_net() triggers bpf_dev_bound_netde= v_unregister(), which iterates ondev->progs and calls __bpf_prog_offload_de= stroy(offload->prog). Accessing the freed prog causes a page fault: BUG: un= able to handle page fault for address: ffffc900085f1038 Workqueue: netns cl= eanup_net RIP: 0010:__bpf_prog_offload_destroy+0xc/0x80 Call Trace: __bpf_o= ffload_dev_netdev_unregister+0x257/0x350 bpf_dev_bound_netdev_unregister+0x= 4a/0x90 unregister_netdevice_many_notify+0x2a2/0x660 ... cleanup_net+0x21a/= 0x320 The test sequence that triggers this reliably is: 1. Set net.core.bpf= _jit_harden=3D2 (echo 2 > /proc/sys/net/core/bpf_jit_harden) 2. Run xdp_met= adata selftest, which creates a dev-bound-only XDP program on a veth inside=
    a netns (./test_progs -t xdp_metadata) 3. cleanup_net -> page fault in __b= pf_prog_offload_destroy Dev-bound-only programs are unique in that they hav=
    e an offload structure but go through the normal JIT path instead of bpf_pr= og_offload_compile(). This means they are subject to constant blinding's pr=
    og clone-and-replace, while also having offload->prog that must stay in syn=
    c. Fix this by updating offload->prog in bpf_jit_prog_release_other(), alon= gside the existing aux->prog update. Both are back-pointers to the prog tha=
    t must be kept in sync when the prog is replaced. 2026-06-24 7.8 CVE-2026-5= 3094 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53094 ] Linux--Linux In = the Linux kernel, the following vulnerability has been resolved: bpf: Use R= CU-safe iteration in dev_map_redirect_multi() SKB path The DEVMAP_HASH bran=
    ch in dev_map_redirect_multi() uses hlist_for_each_entry_safe() to iterate = hash buckets, but this function runs under RCU protection (called from xdp_= do_generic_redirect_map() in softirq context). Concurrent writers (__dev_ma= p_hash_update_elem, dev_map_hash_delete_elem) modify the list using RCU pri= mitives (hlist_add_head_rcu, hlist_del_rcu). hlist_for_each_entry_safe() pe= rforms plain pointer dereferences without rcu_dereference(), missing the ac= quire barrier needed to pair with writers' rcu_assign_pointer(). On weakly-= ordered architectures (ARM64, POWER), a reader can observe a partially-cons= tructed node. It also defeats CONFIG_PROVE_RCU lockdep validation and KCSAN=
    data-race detection. Replace with hlist_for_each_entry_rcu() using rcu_rea= d_lock_bh_held() as the lockdep condition, consistent with the rcu_derefere= nce_check() used in the DEVMAP (non-hash) branch of the same functions. Als=
    o fix the same incorrect lockdep_is_held(&dtab->index_lock) condition in de= v_map_enqueue_multi(), where the lock is not held either. 2026-06-24 7.8 CV= E-2026-53096 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53096 ] Linux--L= inux In the Linux kernel, the following vulnerability has been resolved: s3= 90/bpf: Zero-extend bpf prog return values and kfunc arguments s390x ABI re= quires callers to zero-extend unsigned arguments and sign-extend signed arg= uments, and callees to zero-extend unsigned return values and sign-extend s= igned return values. s390 BPF JIT currently implements only sign extension.=
    Fix this omission and implement zero extension too. 2026-06-24 7.8 CVE-202= 6-53110 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53110 ] Linux--Linux =
    In the Linux kernel, the following vulnerability has been resolved: fs/omfs=
    : reject s_sys_blocksize smaller than OMFS_DIR_START omfs_fill_super() reje= cts oversized s_sys_blocksize values (> PAGE_SIZE), but it does not reject = values smaller than OMFS_DIR_START (0x1b8 =3D 440). Later, omfs_make_empty(=
    ) uses sbi->s_sys_blocksize - OMFS_DIR_START as the length argument to mems= et(). Since s_sys_blocksize is u32, a crafted filesystem image with s_sys_b= locksize < OMFS_DIR_START causes an unsigned underflow there, wrapping to a=
    value near 2^32. That drives a ~4 GiB memset() from bh->b_data + OMFS_DIR_= START and overwrites kernel memory far beyond the backing block buffer. Add=
    the corresponding lower-bound check alongside the existing upper-bound che=
    ck in omfs_fill_super(), so that malformed images are rejected during super= block validation before any filesystem data is processed. 2026-06-24 7.8 CV= E-2026-53130 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53130 ] Linux--L= inux In the Linux kernel, the following vulnerability has been resolved: vs= ock/virtio: fix potential unbounded skb queue virtio_transport_inc_rx_pkt()=
    checks vvs->rx_bytes + len > vvs->buf_alloc. virtio_transport_recv_enqueue=
    () skips coalescing for packets with VIRTIO_VSOCK_SEQ_EOM. If fed with pack= ets with len =3D=3D 0 and VIRTIO_VSOCK_SEQ_EOM, a very large number of pack= ets can be queued because vvs->rx_bytes stays at 0. Fix this by estimating = the skb metadata size: (Number of skbs in the queue) * SKB_TRUESIZE(0) 2026= -06-25 7.1 CVE-2026-53132 [ https://www.cve.org/CVERecord?id=3DCVE-2026-531=
    32 ] Linux--Linux In the Linux kernel, the following vulnerability has been=
    resolved: RDMA/umem: Fix truncation for block sizes >=3D 4G When the iommu=
    is used the linearization of the mapping can give a single block that is v= ery large split across multiple SG entries. When __rdma_block_iter_next() r= eassembles the split SG entries it is overflowing the 32 bit stack values a=
    nd computed the wrong DMA addresses for blocks after the truncation. Use th=
    e right types to hold DMA addresses. 2026-06-25 7.8 CVE-2026-53133 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-53133 ] Linux--Linux In the Linux ker= nel, the following vulnerability has been resolved: drm/gem: Try to fix cha= nge_handle ioctl, attempt 4 [airlied: just added some comments on how to re= enable] On-list because the cat is out of the bag and we're clearly not goo=
    d enough to figure this out in private. The story thus far: 5e28b7b94408 ("= drm: Set old handle to NULL before prime swap in change_handle") tried to f=
    ix a race condition between the gem_close and gem_change_handle ioctls, but=
    got a few things wrong: - There's a confusion with the local variable hand= le, which is actually the new handle, and so the two-stage trick was actual=
    ly applied to the wrong idr slot. 7164d78559b0 ("drm/gem: fix race between = change_handle and handle_delete") tried to fix that by adding yet another c= ode block, but forgot to add the error handling. Which meant we now have tw=
    o paths, both kinda wrong. - dc366607c41c ("drm: Replace old pointer to new=
    idr") tried to apply another fix, but inconsistently, again because of the=
    handle confusion - this would be the right fix (kinda, somewhat, it's a me= ss) if we'd do the two-stage approach for the new handle. Except that wasn'=
    t the intent of the original fix. We also didn't have an igt merged for the=
    original ioctl, which is a big no-go. This was attempted to address off-li=
    st in the original bugfix, and amd QA people claimed the bug was fixed now.=
    Very clearly that's not the case. Here's my attempt to sort this out: - Re= name the local variable to new_handle, the old aliasing with args->handle i=
    s just too dangerously confusing. - Merge the gem obj lookup with the two-s= tage idr_replace so that we avoid getting ourselves confused there. - This = means we don't have a surplus temporary reference anymore, only an inherite=
    d from the idr. A concurrent gem_close on the new_handle could steal that. = Fix that with the same two-stage approach create_tail uses. This is a bit o= verkill as documented in the comment, but I also don't trust my ability to = understand this all correctly, so go with the established pattern we have f= rom other ioctls instead for maximum paranoia. - Adjust error paths. I've t= ried to make the error and success paths common, because they are identical=
    except for which handle is removed and on which we call idr_replace to (re= )install the object again. But that made things messier to read, so I've le=
    ft it at the more verbose version, which unfortunately hides the symmetry i=
    n the entire code flow a bit. - While at it, also replace the 7 space inden=
    t with 1 tab. And finally, because I flat out don't trust my abilities here=
    at all anymore: - Disable the ioctl until we have the igt situation and ev= erything else sorted out on-list and with full consensus. v2: Sashiko notic=
    ed that I didn't handle the error path for idr_replace correctly, it must b=
    e checked with IS_ERR_OR_NULL like in gem_handle_delete. So yeah, definitel=
    y should just the existing paths 1:1 because this is endless amounts of tri= cky. Also add the Fixes: line for the original ioctl, I forgot that too. 20= 26-06-25 7.8 CVE-2026-53145 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 3145 ] Linux--Linux In the Linux kernel, the following vulnerability has be=
    en resolved: thunderbolt: Limit XDomain response copy to actual frame size = tb_xdomain_copy() copies req->response_size bytes from the received packet = buffer regardless of the actual frame size. When a short response arrives, = this reads past the valid frame data in the DMA pool buffer into stale cont= ents from previous transactions. Use the minimum of frame size and expected=
    response size for the copy length. 2026-06-25 7.1 CVE-2026-53146 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-53146 ] Linux--Linux In the Linux kern= el, the following vulnerability has been resolved: mm/list_lru: drain befor=
    e clearing xarray entry on reparent memcg_reparent_list_lrus() clears the d= ying memcg's xarray entry with xas_store(&xas, NULL) before reparenting its=
    per-node lists into the parent. This opens a window where a concurrent lis= t_lru_del() arriving for the dying memcg sees xa_load() =3D=3D NULL, walks =
    to the parent in lock_list_lru_of_memcg(), takes the parent's per-node lock=
    , and calls list_del_init() on an item still physically linked on the dying=
    memcg's list. If another in-flight thread holds the dying memcg's per-node=
    lock at the same moment (another list_lru_del, or a list_lru_walk_one runn= ing an isolate callback), both threads modify ->next/->prev pointers on the=
    same physical list under different locks. Adjacent items can corrupt each = other's links. Fix it by reversing the order: reparent each per-node list a=
    nd mark the child's list lru dead and then clear the xarray entry. Any conc= urrent list_lru op that finds the still-set xarray entry either takes the d= ying memcg's per-node lock (synchronizing with the drain) or sees LONG_MIN = and walks to the parent, where the items now live. 2026-06-25 7.8 CVE-2026-= 53153 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53153 ] Linux--Linux In=
    the Linux kernel, the following vulnerability has been resolved: misc: fas= trpc: fix use-after-free race in fastrpc_map_create fastrpc_map_lookup retu= rns a raw pointer after releasing fl->lock. The caller fastrpc_map_create t= hen calls fastrpc_map_get (kref_get_unless_zero) on this unprotected pointe=
    r. A concurrent MEM_UNMAP can free the map between the lock release and the=
    kref operation, resulting in a use-after-free on the freed slab object. Re= store the take_ref parameter to fastrpc_map_lookup so the reference is acqu= ired atomically under fl->lock before the pointer is exposed to the caller.=
    2026-06-25 7.8 CVE-2026-53160 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-53160 ] Linux--Linux In the Linux kernel, the following vulnerability has=
    been resolved: misc: fastrpc: fix use-after-free of fastrpc_user in workqu= eue context There is a race between fastrpc_device_release() and the workqu= eue that processes DSP responses. When the user closes the file descriptor,=
    fastrpc_device_release() frees the fastrpc_user structure. Concurrently, a=
    n in-flight DSP invocation can complete and fastrpc_rpmsg_callback() schedu= les context cleanup via schedule_work(&ctx->put_work). If the workqueue run=
    s fastrpc_context_free() in parallel with or after fastrpc_device_release()=
    has freed the user structure, it dereferences the freed fastrpc_user. Depe= nding on the state of the context at the time of the race, any one of the f= ollowing accesses can be hit: 1. fastrpc_buf_free() calls fastrpc_ipa_to_dm= a_addr(buf->fl->cctx, ...) to strip the SID bits from the stored IOVA befor=
    e passing the physical address to dma_free_coherent(). 2. fastrpc_free_map(=
    ) reads map->fl->cctx->vmperms[0].vmid to reconstruct the source permission=
    bitmask needed for the qcom_scm_assign_mem() call that returns memory from=
    the DSP VM back to HLOS. 3. fastrpc_free_map() acquires map->fl->lock to s= afely remove the map node from the fl->maps list. The resulting use-after-f= ree manifests as: pc : fastrpc_buf_free+0x38/0x80 [fastrpc] lr : fastrpc_co= ntext_free+0xa8/0x1b0 [fastrpc] fastrpc_context_free+0xa8/0x1b0 [fastrpc] f= astrpc_context_put_wq+0x78/0xa0 [fastrpc] process_one_work+0x180/0x450 work= er_thread+0x26c/0x388 Add kref-based reference counting to fastrpc_user. Ha=
    ve each invoke context take a reference on the user at allocation time and = release it when the context is freed. Release the initial reference in fast= rpc_device_release() at file close. Move the teardown of the user structure=
    - freeing pending contexts, maps, mmaps, and the channel context reference=
    - into the kref release callback fastrpc_user_free(), so that it runs only=
    when the last reference is dropped, regardless of whether that happens at = device close or after the final in-flight context completes. 2026-06-25 7.8=
    CVE-2026-53161 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53161 ] Linux= --Linux In the Linux kernel, the following vulnerability has been resolved:=
    memcg: use round-robin victim selection in refill_stock Harry Yoo reported=
    that get_random_u32_below() is not safe to call in the nmi context and mem=
    cg charge draining can happen in nmi context. More specifically get_random_= u32_below() is neither reentrant- nor NMI-safe: it acquires a per-cpu local= _lock via local_lock_irqsave() on the batched_entropy_u32 state. An NMI tha=
    t lands on a CPU mid-update of the ChaCha batch state and recurses into the=
    random subsystem would corrupt that state. The memcg_stock local_trylock p= revents re-entry on the percpu stock itself, but cannot protect an unrelate=
    d subsystem's per-cpu lock. Replace the random pick with a per-cpu round-ro= bin counter stored in memcg_stock_pcp and serialized by the same local_tryl= ock that already guards cached[] and nr_pages[]. No atomics, no random call=
    s, no extra locks needed. 2026-06-25 7.8 CVE-2026-53162 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-53162 ] Linux--Linux In the Linux kernel, the fo= llowing vulnerability has been resolved: iomap: avoid potential null folio-= >mapping deref during error reporting When a buffered read fails, iomap_fin= ish_folio_read() reports the error with fserror_report_io(folio->mapping->h= ost, ...). This is called after ifs->read_bytes_pending has been decremente=
    d by the bytes attempted to be read. For a folio split across multiple read=
    completions, the folio is only guaranteed to stay locked while read_bytes_= pending > 0. Once iomap_finish_folio_read() decrements read_bytes_pending, = another in-flight read can complete and end the read on the folio, which un= locks it. This allows truncate logic to run and detach the folio (set folio= ->mapping to NULL). The error reporting path then can dereference a NULL fo= lio->mapping. As reported by Sam Sun, this is the race that can occur: CPU0=
    : failed completion CPU1: final completion CPU2: truncate -----------------= ------ ---------------------- -------------- read_bytes_pending -=3D len fi= nished =3D false /* preempted before fserror_report_io() */ read_bytes_pend= ing -=3D len finished =3D true folio_end_read() truncate clears folio->mapp= ing fserror_report_io( folio->mapping->host, ...) ^ NULL deref Fix this by = reporting the error first before decrementing ifs->read_bytes_pending. 2026= -06-25 7.5 CVE-2026-53165 [ https://www.cve.org/CVERecord?id=3DCVE-2026-531=
    65 ] Linux--Linux In the Linux kernel, the following vulnerability has been=
    resolved: accel/ethosu: fix IFM region index out-of-bounds in command stre=
    am parser NPU_SET_IFM_REGION extracts the region index with param & 0x7f, g= iving a maximum value of 127. However region_size[] and output_region[] in = struct ethosu_validated_cmdstream_info are both sized to NPU_BASEP_REGION_M=
    AX (8), giving valid indices [0..7]. Every other region assignment in the s= ame switch uses param & 0x7: NPU_SET_OFM_REGION: st.ofm.region =3D param & = 0x7; NPU_SET_IFM2_REGION: st.ifm2.region =3D param & 0x7; NPU_SET_WEIGHT_RE= GION: st.weight[0].region =3D param & 0x7; NPU_SET_SCALE_REGION: st.scale[0= ].region =3D param & 0x7; The 0x7f mask on IFM is inconsistent and appears =
    to be a typo. feat_matrix_length() and calc_sizes() use the region index di= rectly as an array subscript into the kzalloc'd info struct: info->region_s= ize[fm->region] =3D max(...); A userspace caller supplying NPU_SET_IFM_REGI=
    ON with param > 7 causes a write up to 127*8 =3D 1016 bytes past the start =
    of region_size[], corrupting adjacent kernel heap data. Fix by applying the=
    same & 0x7 mask used by all other region assignments. 2026-06-25 7.8 CVE-2= 026-53172 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53172 ] Linux--Linu=
    x In the Linux kernel, the following vulnerability has been resolved: accel= /ethosu: fix OOB write in ethosu_gem_cmdstream_copy_and_validate() The comm= and stream parsing loop increments the index variable a second time when a = 64-bit command word is encountered (bit 14 set), but does not re-check the = loop bound before writing the second word: for (i =3D 0; i < size / 4; i++)=
    { bocmds[i] =3D cmds[0]; if (cmd & 0x4000) { i++; bocmds[i] =3D cmds[1]; /=
    * unchecked */ } } The buffer bocmds is backed by a DMA allocation of exact=
    ly size bytes from drm_gem_dma_create(ddev, size), giving valid indices [0,=
    size/4-1]. When i =3D=3D size/4 - 1 on entry to an iteration and bit 14 of=
    cmds[0] is set, bocmds[size/4-1] is written in bounds, i is then increment=
    ed to size/4, and bocmds[size/4] writes four bytes past the end of the allo= cation. Userspace controls both the buffer contents and the size argument v=
    ia the ioctl, making this a userspace-triggerable heap out-of-bounds write.=
    Fix by checking the incremented index against the buffer bound before the = second write and returning -EINVAL if the buffer is too small to contain th=
    e extended command. 2026-06-25 7.8 CVE-2026-53173 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-53173 ] Linux--Linux In the Linux kernel, the followin=
    g vulnerability has been resolved: ovl: keep err zero after successful ovl_= cache_get() ovl_iterate_merged() stores PTR_ERR(cache) in err before checki=
    ng IS_ERR(cache). On success err holds the truncated cache pointer and can =
    be returned as a bogus non-zero error. The syzbot reproducer reaches this t= hrough overlay-on-overlay readdir: getdents64 iterate_dir(outer overlay fil=
    e) ovl_iterate_merged() ovl_cache_get() ovl_dir_read_merged() ovl_dir_read(=
    ) iterate_dir(inner overlay file) ovl_iterate_merged() Only compute PTR_ERR= (cache) on the error path. 2026-06-25 7.8 CVE-2026-53174 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-53174 ] Linux--Linux In the Linux kernel, the f= ollowing vulnerability has been resolved: timers/migration: Fix livelock in=
    tmigr_handle_remote_up() tmigr_handle_remote_cpu() skips timer_expire_remo= te() when cpu =3D=3D smp_processor_id(), assuming the local softirq path al= ready handled this CPU's timers. This assumption is wrong because jiffies c=
    an advance after the handling of the CPU's global timers in run_timer_base(= BASE_GLOBAL) and before tmigr_handle_remote() evaluates the expiry times. A=
    s a consequence a timer which expires after the CPU local timer wheel advan= ced and becomes expired in the remote handling is ignored and the callback =
    is never invoked and removed from the timer wheel. What's worse is that fet= ch_next_timer_interrupt_remote() keeps reporting it as expired, and the eve=
    nt is re-queued with expires =3D=3D now on each iteration. The goto-again l= oop spins indefinitely. Fix this by calling timer_expire_remote() unconditi= onally. That's minimal overhead for the common case as __run_timer_base() r= eturns immediately if there is nothing to expire in the local wheel. [ tglx=
    : Amend change log and add a comment ] 2026-06-25 7.5 CVE-2026-53180 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-53180 ] Linux--Linux In the Linux k= ernel, the following vulnerability has been resolved: wifi: nl80211: reject=
    oversized EMA RNR lists nl80211_parse_rnr_elems() stores the parsed elemen=
    t count in a u8-backed cfg80211_rnr_elems::cnt field and uses that count to=
    size the flexible array allocation. Reject nested NL80211_ATTR_EMA_RNR_ELE=
    MS input once the count reaches 255, before incrementing it again. This kee=
    ps the parser aligned with the data structure it fills and matches the exis= ting bound check used by nl80211_parse_mbssid_elems(). 2026-06-25 7.8 CVE-2= 026-53182 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53182 ] Linux--Linu=
    x In the Linux kernel, the following vulnerability has been resolved: mptcp=
    : allow subflow rcv wnd to shrink In MPTCP connection, the `window` field i=
    n the TCP header refers to the MPTCP-level rcv_nxt and it's right edge shou=
    ld not move backward. Such constraint is enforced at DSS option generation = time. At the same time, the TCP stack ensures independently that the TCP-le= vel rcv wnd right's edge does not move backward. That in turn causes artifi= cial inflating of the MPTCP rcv window when the incoming data is acked at t=
    he TCP level and is OoO in the MPTCP sequence space (or lands in the backlo= g). As a consequence, the incoming traffic can exceed the receiver rcvbuf s= ize even when the sender is not misbehaving. Prevent such scenario forcibly=
    allowing the TCP subflow to shrink the TCP-level rcv wnd regardless of the=
    current netns setting. 2026-06-25 7.5 CVE-2026-53183 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-53183 ] Linux--Linux In the Linux kernel, the foll= owing vulnerability has been resolved: udp: clear skb->dev before running a=
    sockmap verdict On the UDP receive path skb->dev is repurposed as dev_scra= tch (the truesize/state cache set by udp_set_dev_scratch()), through the un= ion { struct net_device *dev; unsigned long dev_scratch; } in sk_buff. When=
    a UDP socket is in a sockmap, sk_data_ready is sk_psock_verdict_data_ready= (), which calls udp_read_skb() -> recv_actor() (sk_psock_verdict_recv) to r=
    un the attached SK_SKB verdict program in softirq. If that program calls a = socket-lookup helper (bpf_sk_lookup_tcp/udp, bpf_skc_lookup_tcp), bpf_skc_l= ookup() does: if (skb->dev) caller_net =3D dev_net(skb->dev); skb->dev stil=
    l holds the dev_scratch value (a non-NULL integer), so dev_net() dereferenc=
    es it as a struct net_device * and the kernel takes a general protection fa= ult on a non-canonical address in softirq: Oops: general protection fault, = probably for non-canonical address 0x1010000800004a0 CPU: 1 UID: 0 PID: 140=
    6 Comm: syz.2.19 Not tainted 7.1.0-rc6 #1 PREEMPT(full) RIP: 0010:bpf_skc_l= ookup net/core/filter.c:7033 [inline] RIP: 0010:bpf_sk_lookup+0x45/0x160 ne= t/core/filter.c:7047 Call Trace: <IRQ> bpf_prog_4675cb904b7071f8+0x12e/0x14=
    e bpf_prog_run_pin_on_cpu+0xc6/0x1f0 sk_psock_verdict_recv+0x1ba/0x350 udp_= read_skb+0x31a/0x370 sk_psock_verdict_data_ready+0x2e3/0x600 __udp_enqueue_= schedule_skb+0x4c8/0x650 udpv6_queue_rcv_one_skb+0x3ec/0x740 udp6_unicast_r= cv_skb+0x11d/0x140 ip6_protocol_deliver_rcu+0x61e/0x950 ip6_input_finish+0x= a9/0x150 NF_HOOK+0x286/0x2f0 ip6_input+0x117/0x220 NF_HOOK+0x286/0x2f0 __ne= tif_receive_skb+0x85/0x200 process_backlog+0x374/0x9a0 __napi_poll+0x4f/0x1=
    c0 net_rx_action+0x3b0/0x770 handle_softirqs+0x15a/0x460 do_softirq+0x57/0x=
    80 </IRQ> The rmem charge that dev_scratch accounted for is released by skb= _recv_udp() on dequeue, just above, so the scratch is dead by the time recv= _actor() runs. Clear skb->dev so bpf_skc_lookup() falls back to sock_net(sk= b->sk), which skb_set_owner_sk_safe() set just above. 2026-06-25 7.5 CVE-20= 26-53184 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53184 ] Linux--Linux=
    In the Linux kernel, the following vulnerability has been resolved: zram: = fix use-after-free in zram_bvec_write_partial() zram_read_page() picks the = sync or async backing device read path based on whether the parent bio is N= ULL. zram_bvec_write_partial() passes its parent bio down, so for ZRAM_WB s= lots the read is dispatched asynchronously and zram_read_page() returns 0 w= hile the bio is still in flight. The caller then runs memcpy_from_bvec(), z= ram_write_page() and __free_page() on the buffer, leaving the async read to=
    write into a freed page. zram_bvec_read_partial() was switched to NULL in = commit 4e3c87b9421d ("zram: fix synchronous reads") for the same reason; th=
    e write_partial counterpart was missed. 2026-06-25 7.8 CVE-2026-53185 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-53185 ] Linux--Linux In the Linux = kernel, the following vulnerability has been resolved: RDMA/core: Validate = cpu_id against nr_cpu_ids in DMAH alloc The cpu_id attribute supplied by us=
    er space through UVERBS_ATTR_ALLOC_DMAH_CPU_ID is passed directly to cpumas= k_test_cpu() without first verifying that the value is within the valid CPU=
    range. Passing such untrusted data to cpumask_test_cpu() may lead to an ou= t-of-bounds read of the underlying cpumask bitmap: the helper expands to a = test_bit() that indexes the bitmap by cpu_id / BITS_PER_LONG with no bound = check. In addition, on kernels built with CONFIG_DEBUG_PER_CPU_MAPS it trip=
    s the WARN_ON_ONCE() in cpumask_check(); combined with panic_on_warn this t= urns a bad user input into a machine reboot. Reject any cpu_id that is not = smaller than nr_cpu_ids with -EINVAL before it is used. Reported by Smatch.=
    2026-06-25 7.1 CVE-2026-53187 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-53187 ] Linux--Linux In the Linux kernel, the following vulnerability has=
    been resolved: mm/huge_memory: update file PMD counter before folio_put() = __split_huge_pmd_locked() updates the file/shmem RSS counter after dropping=
    the PMD mapping's folio reference. If folio_put() drops the last reference=
    , mm_counter_file() can later read freed folio state via folio_test_swapbac= ked(). Move the counter update before folio_put(). 2026-06-25 7.8 CVE-2026-= 53189 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53189 ] Linux--Linux In=
    the Linux kernel, the following vulnerability has been resolved: io_uring/= net: inherit IORING_CQE_F_BUF_MORE across bundle recv retries When a bundle=
    recv retries inside io_recv_finish(), the merge logic OR the saved cflags = from the previous iteration with the cflags returned by the new iteration: = cflags =3D req->cqe.flags | (cflags & CQE_F_MASK); Bits listed in CQE_F_MAS=
    K are inherited from the new iteration, and all other bits (notably IORING_= CQE_F_BUFFER and the buffer ID) come from the saved cflags. Before this cha= nge CQE_F_MASK covered only IORING_CQE_F_SOCK_NONEMPTY and IORING_CQE_F_MOR=
    E. When using provided buffer rings (IOU_PBUF_RING_INC) with incremental mo= de, and bundle recv, io_kbuf_inc_commit() can leave the head ring entry par= tially consumed, __io_put_kbufs() then sets IORING_CQE_F_BUF_MORE on the re= turned cflags so userspace knows the buffer ID will be reused for subsequen=
    t completions. Because IORING_CQE_F_BUF_MORE was not in CQE_F_MASK, the mer=
    ge above silently dropped it whenever the final retry iteration partially c= onsumed the buffer, and the subsequent req->cqe.flags =3D cflags & ~CQE_F_M= ASK save would have left a stale IORING_CQE_F_BUF_MORE in the carried-over = cflags had one been present. Userspace would then wrongfully advance it rin=
    g head past an entry the kernel still uses. Add IORING_CQE_F_BUF_MORE to CQ= E_F_MASK so it is both inherited from the new iteration into the user-visib=
    le CQE and stripped from the saved cflags between iterations. 2026-06-25 7.=
    8 CVE-2026-53191 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53191 ] Linu= x--Linux In the Linux kernel, the following vulnerability has been resolved=
    : ALSA: timer: Fix UAF at snd_timer_user_params() At releasing a timer obje= ct, e.g. when a userspace timer (CONFIG_SND_UTIMER) gets closed and snd_tim= er_free() is called, it tries to detach the timer instances and release the=
    resources. However, it's still possible that other in-flight tasks are hol= ding the timer instance where the to-be-deleted timer object is associated,=
    and this may lead to racy accesses. Fortunately, most of ioctls dealing wi=
    th the timer instance list already have the protection with register_mutex,=
    and this also avoids such races. But, SNDRV_TIMER_IOCTL_PARAMS isn't prote= cted, hence the concurrent ioctl may lead to use-after-free. This patch jus=
    t adds the guard with register_mutex to protect snd_timer_user_params() for=
    covering the code path as a quick workaround. It's no hot-path but rather =
    a rarely issued ioctl, so the performance penalty doesn't matter. 2026-06-2=
    5 7.8 CVE-2026-53192 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53192 ] = Linux--Linux In the Linux kernel, the following vulnerability has been reso= lved: ALSA: timer: Forcibly close timer instances at closing When snd_timer=
    object is freed via snd_timer_free() and still pending snd_timer_instance = objects are assigned to the timer object, it tries to unlink all instances = and just set NULL to each ti->timer, then releases the resources immediatel=
    y. The problem is, however, when there are slave timer instances that are a= ssociated with a master instance linked to this timer: namely, those slave = instances still point to the freed timer object although the master instanc=
    e is unlinked, which may lead to user-after-free. The bug can be easily tri= ggered particularly when a new userspace-driven timers (CONFIG_SND_UTIMER) =
    is involved, since it can create and delete the timer object via a simple f= ile open/close, while the other applications may keep accessing to that tim= er. This patch is an attempt to paper over the problem above: now instead o=
    f just unlinking, call snd_timer_close[_locked]() forcibly for each pending=
    timer instance, so that all assigned slave timer instances are properly de= tached, too. Since snd_timer_close() might be called later by the driver th=
    at created that instance, the check of SNDRV_TIMER_IFLG_DEAD is added at th=
    e beginning, too. 2026-06-25 7.8 CVE-2026-53193 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-53193 ] Linux--Linux In the Linux kernel, the following = vulnerability has been resolved: USB: serial: kl5kusb105: fix bulk-out buff=
    er overflow klsi_105_prepare_write_buffer() is called by the generic write = path with the bulk-out buffer and its size (bulk_out_size, 64 bytes). It st= ores a two-byte length header at the start of the buffer and copies the pay= load from the write fifo starting at buf + KLSI_HDR_LEN, but passes the ful=
    l buffer size as the number of bytes to copy: count =3D kfifo_out_locked(&p= ort->write_fifo, buf + KLSI_HDR_LEN, size, &port->lock); When the fifo hold=
    s at least size bytes, size bytes are copied starting two bytes into the si= ze-byte buffer, writing KLSI_HDR_LEN bytes past its end. Copy at most size =
    - KLSI_HDR_LEN bytes instead, leaving room for the header as safe_serial al= ready does. Writing bulk_out_size or more bytes to the tty triggers a slab = out-of-bounds write, observed with KASAN by emulating the device with dummy= _hcd and raw-gadget: BUG: KASAN: slab-out-of-bounds in kfifo_copy_out+0x83/= 0xc0 Write of size 64 at addr ffff888112c62202 by task python3 kfifo_copy_o=
    ut klsi_105_prepare_write_buffer [kl5kusb105] usb_serial_generic_write_star=
    t [usbserial] Allocated by task 139: usb_serial_probe [usbserial] The buggy=
    address is located 2 bytes inside of allocated 64-byte region The out-of-b= ounds write no longer occurs with this change applied. 2026-06-25 7.8 CVE-2= 026-53194 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53194 ] Linux--Linu=
    x In the Linux kernel, the following vulnerability has been resolved: hv_ne= tvsc: use kmap_local_page in netvsc_copy_to_send_buf netvsc_copy_to_send_bu= f() copies page buffer entries into the VMBus send buffer using phys_to_vir= t() on the entry PFN. Entries for the RNDIS header and the skb linear data = come from kmalloc'd memory and are always in the kernel direct map, but ent= ries for skb fragments reference page cache or user pages, which on 32-bit = x86 with CONFIG_HIGHMEM=3Dy can live above the LOWMEM boundary. For such a = page phys_to_virt() returns an address outside the direct map and the subse= quent memcpy() faults on the transmit softirq path, which is fatal. Map the=
    pages with kmap_local_page() instead, handling two properties of the page = buffer entries: - pb[i].pfn is a Hyper-V PFN at HV_HYP_PAGE_SIZE (4K) granu= larity, not a native PFN. Reconstruct the physical address first and derive=
    the native page from it, so the mapping stays correct where PAGE_SIZE > HV= _HYP_PAGE_SIZE (e.g. arm64 with 64K pages). - Since commit 41a6328b2c55 ("h= v_netvsc: Preserve contiguous PFN grouping in the page buffer array"), an e= ntry describes a full physically contiguous fragment and pb[i].len can exce=
    ed PAGE_SIZE, while kmap_local_page() maps a single page. Copy page by page=
    , splitting at native page boundaries. The copy path only handles packets s= maller than the send section size (6144 bytes by default); larger packets t= ake the cp_partial path where only the RNDIS header is copied. So entries h= ere are bounded by the section size and a copy is split at most once on 4K-= page systems. On !CONFIG_HIGHMEM configs kmap_local_page() folds to page_ad= dress() and no mapping work is added. 2026-06-25 7.5 CVE-2026-53199 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-53199 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: Revert "drm/xe: Skip e= xec queue schedule toggle if queue is idle during suspend" This reverts com= mit 8533051ce92015e9cc6f75e0d52119b9d91610b6. The idle-skip optimization by= passes GuC suspend, so the GPU may not perform the context switch that flus= hes TLB entries for invalidated userptr VMAs. In LR/preempt-fence VM mode, = this can lead to missed TLB invalidation and page faults during userptr inv= alidation tests. Restore unconditional schedule toggling on suspend so the = context-switch TLB flush is always performed. This optimization will be rei= ntroduced with a fix that does not skip suspend in LR/preempt-fence VM mode=
    . (cherry picked from commit 6a1e7934d9a6cf46aecae00a99c2603d1295e170) 2026= -06-25 7.8 CVE-2026-53201 [ https://www.cve.org/CVERecord?id=3DCVE-2026-532=
    01 ] Linux--Linux In the Linux kernel, the following vulnerability has been=
    resolved: accel/ivpu: Fix signed integer truncation in IPC receive Fix pot= ential buffer overflow where firmware-supplied data_size is cast to signed = int before being used in min_t(). Large unsigned values (>=3D 0x80000000) b= ecome negative, causing unsigned wraparound and oversized memcpy operations=
    that can overflow the stack buffer. Change min_t(int, ...) to min() as bot=
    h values are unsigned and can be handled by min() without explicit cast. 20= 26-06-25 7.8 CVE-2026-53202 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 3202 ] Linux--Linux In the Linux kernel, the following vulnerability has be=
    en resolved: accel/ivpu: Add buffer overflow check in MS get_info_ioctl Add=
    validation that the info size returned from the metric stream info query i=
    s not exceeded when checked against the allocated buffer size. If the firmw= are returns a size larger than the buffer, reject the operation with -EOVER= FLOW instead of proceeding with an incorrect buffer copy. 2026-06-25 7.1 CV= E-2026-53203 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53203 ] Linux--L= inux In the Linux kernel, the following vulnerability has been resolved: ac= cel/ivpu: Add bounds checks for firmware log indices Add validation that re=
    ad and write indices in the firmware log buffer are within valid bounds (< = data_size) before using them. If out-of-bounds indices are encountered (fro=
    m firmware), clamp them to safe values instead of proceeding with invalid o= ffsets. This prevents potential out-of-bounds buffer access when firmware s= upplies invalid log indices. 2026-06-25 7.1 CVE-2026-53205 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-53205 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: Bluetooth: hci_sync: reject ove= rsized Broadcast Announcement prepend Existing advertising instances can al= ready hold the maximum extended advertising payload. When hci_adv_bcast_ann= oucement() prepends the Broadcast Announcement service data to that payload=
    , the combined data may no longer fit in the temporary buffer used to rebui=
    ld the advertising data. Reject that case before copying the existing paylo=
    ad and report the failure through the device log. This keeps the existing a= dvertising data intact and avoids overrunning the temporary buffer. 2026-06= -25 7.8 CVE-2026-53209 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53209 =
    ] Linux--Linux In the Linux kernel, the following vulnerability has been re= solved: netfilter: nft_tunnel: fix use-after-free on object destroy nft_tun= nel_obj_destroy() calls metadata_dst_free() which directly kfree()s the met= adata_dst, ignoring the dst_entry refcount. Packets that took a reference v=
    ia dst_hold() in nft_tunnel_obj_eval() and are still queued (e.g. in a nete=
    m qdisc) are left with a dangling pointer. When these packets are eventuall=
    y dequeued, dst_release() operates on freed memory. Replace metadata_dst_fr= ee() with dst_release() so the metadata_dst is freed only after all referen= ces are dropped. The dst subsystem already handles metadata_dst cleanup in = dst_destroy() when DST_METADATA is set. 2026-06-25 7.8 CVE-2026-53212 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-53212 ] Linux--Linux In the Linux = kernel, the following vulnerability has been resolved: net: guard timestamp=
    cmsgs to real error queue skbs skb_is_err_queue() treats PACKET_OUTGOING a=
    s the sole marker for an skb from sk_error_queue. That assumption is not tr=
    ue for AF_PACKET sockets: outgoing packet taps are also delivered to packet=
    sockets with skb->pkt_type =3D=3D PACKET_OUTGOING, but their skb->cb is ow= ned by AF_PACKET instead of struct sock_exterr_skb. If such an skb is recei= ved with timestamping enabled, the generic timestamp cmsg path can read AF_= PACKET control-buffer state as sock_exterr_skb::opt_stats. With SO_RXQ_OVFL=
    enabled, the packet drop counter overlaps opt_stats. An odd drop count mak=
    es the path emit SCM_TIMESTAMPING_OPT_STATS with skb->len and skb->data. Fo=
    r non-linear skbs this copies past the linear head and can trigger hardened=
    usercopy or disclose adjacent heap contents. Keep skb_is_err_queue() local=
    to net/socket.c, but make it verify that the PACKET_OUTGOING marker is pai= red with the sock_rmem_free destructor installed by sock_queue_err_skb(). A= F_PACKET receive skbs use normal receive ownership and no longer pass as er= ror-queue skbs, while legitimate sk_error_queue entries keep the PACKET_OUT= GOING marker and sock_rmem_free ownership. 2026-06-25 7.1 CVE-2026-53223 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-53223 ] Linux--Linux In the Lin=
    ux kernel, the following vulnerability has been resolved: net/mlx5e: xsk: F=
    ix DMA and xdp_frame leak on XDP_TX xmit failure In the XSK branch of mlx5e= _xmit_xdp_buff(), when sq->xmit_xdp_frame() returns false (e.g. XDPSQ is fu= ll), the function returns without unmapping the DMA address or freeing the = xdp_frame allocated by xdp_convert_zc_to_xdp_frame(). The xdpi_fifo push on=
    ly happens on success, so the completion path cannot recover these entries.=
    With CONFIG_DMA_API_DEBUG=3Dy, the leak surfaces on driver unbind: DMA-API=
    : pci 0000:08:00.0: device driver has pending DMA allocations while release=
    d from device [count=3D1116] One of leaked entries details: [device address= =3D0x000000010ffd7028] [size=3D1534 bytes] [mapped with DMA_TO_DEVICE] [map= ped as phy] WARNING: kernel/dma/debug.c:881 at dma_debug_device_change+0x12= 7/0x180 ... DMA-API: Mapped at: debug_dma_map_phys+0x4b/0xd0 dma_map_phys+0= xfd/0x2d0 mlx5e_xdp_handle+0x5ae/0xac0 [mlx5_core] mlx5e_xsk_skb_from_cqe_m= pwrq_linear+0xc4/0x170 [mlx5_core] mlx5e_handle_rx_cqe_mpwrq+0xc1/0x290 [ml= x5_core] Add the missing unmap + xdp_return_frame, matching the cleanup alr= eady done in mlx5e_xdp_xmit(). has_frags is rejected earlier in this branch=
    , so no per-frag unmap is needed. 2026-06-25 7.5 CVE-2026-53229 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-53229 ] Linux--Linux In the Linux kernel=
    , the following vulnerability has been resolved: net: add pskb_may_pull() t=
    o skb_gro_receive_list() skb_gro_receive_list() calls skb_pull(skb, skb_gro= _offset(skb)) without first ensuring the data is in the linear area via psk= b_may_pull(). When the skb arrives via napi_gro_frags(), skb_headlen can be=
    0 (all data in page fragments) while skb_gro_offset is non-zero (after IP+= TCP header parsing). The skb_pull() then decrements skb->len by skb_gro_off= set but skb->data_len stays unchanged, hitting BUG_ON(skb->len < skb->data_= len) in __skb_pull(). The UDP fraglist GRO path already contains this guard=
    at udp_offload.c:749. Adding it to skb_gro_receive_list() itself provides = centralized protection for all callers (TCP, UDP, and any future protocols)=
    , and ensures the precondition of skb_pull() is satisfied before it is call= ed. On pskb_may_pull() failure, set NAPI_GRO_CB(skb)->flush =3D 1 so the sk=
    b is not held as a new GRO head and is instead delivered through the normal=
    receive path, matching the UDP handling. 2026-06-25 7.5 CVE-2026-53235 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-53235 ] Linux--Linux In the Linu=
    x kernel, the following vulnerability has been resolved: xfrm: policy: fix = use-after-free on inexact bin in xfrm_policy_bysel_ctx() Fix the race by pr= uning the bin while still holding xfrm_policy_lock, before dropping it. Use=
    __xfrm_policy_inexact_prune_bin() directly since the lock is already held.=
    The wrapper xfrm_policy_inexact_prune_bin() becomes unused and is removed.=
    Race: CPU0 (XFRM_MSG_DELPOLICY) CPU1 (XFRM_MSG_NEWSPDINFO) =3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D xfrm_= policy_bysel_ctx(): spin_lock_bh(xfrm_policy_lock) bin =3D xfrm_policy_inex= act_lookup() __xfrm_policy_unlink(pol) spin_unlock_bh(xfrm_policy_lock) xfr= m_policy_kill(ret) // wide window, lock not held xfrm_hash_rebuild(): spin_= lock_bh(xfrm_policy_lock) __xfrm_policy_inexact_flush(): kfree_rcu(bin) // = bin freed spin_unlock_bh(xfrm_policy_lock) xfrm_policy_inexact_prune_bin(bi=
    n) // UAF: bin is freed 2026-06-25 7.8 CVE-2026-53239 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-53239 ] Linux--Linux In the Linux kernel, the foll= owing vulnerability has been resolved: ALSA: PCM: Fix wait queue list corru= ption in snd_pcm_drain() on linked streams snd_pcm_drain() uses init_waitqu= eue_entry which does not clear entry.prev/next, and add_wait_queue with a c= onditional remove_wait_queue that is skipped when to_check is no longer in = the group after concurrent UNLINK. The orphaned wait entry remains on the u= nlinked substream sleep queue. On the next drain iteration, add_wait_queue = adds the entry to a new queue while still linked on the old one, corrupting=
    both lists. A subsequent wake_up dereferences NULL at the func pointer (ma= pped from the spinlock at offset 0 of the misinterpreted wait_queue_head_t)=
    , causing a kernel panic. Replace init_waitqueue_entry/add_wait_queue/condi= tional remove_wait_queue with init_wait_entry/prepare_to_wait/ finish_wait.=
    init_wait_entry clears prev/next via INIT_LIST_HEAD on each iteration and = sets autoremove_wake_function which auto-removes the entry on wake-up. fini= sh_wait safely handles both the already-removed and still-queued cases. 202= 6-06-25 7.8 CVE-2026-53242 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53= 242 ] Linux--Linux In the Linux kernel, the following vulnerability has bee=
    n resolved: VFS: fix possible failure to unlock in nfsd4_create_file() atom= ic_create() in fs/namei.c drops the reference to the dentry when it returns=
    an error. This behaviour was imported into dentry_create() so that it will=
    drop the reference if an error is returned from atomic_create(), though no=
    t if vfs_create() returns an error (in the case where ->atomic_create is no=
    t supported). The caller - nfsd4_create_file() - is made aware of this by c= hecking path->dentry, which will either be a counted reference to a dentry,=
    or an error pointer. However the change to use start_creating()/end_creati= ng() (which landed shortly before the dentry_create() change landed, though=
    was likely developed around the same time) means that nfsd4_create_file() = *needs* a valid dentry so that it can unlock the parent. The net result is = that if NFSD exports a filesystem which uses ->atomic_create, and if a call=
    to ->atomic_create returns an error, then nfsd4_create_file() will pass an=
    error pointer to end_creating() and the parent will not be unlocked. Fix t= his by changing dentry_create() to make sure path->dentry is always a valid=
    dentry, never an error-pointer. The actual error is already returned a dif= ferent way. Note that if ->atomic_create() returns a different dentry (whic=
    h may not be possible in practice) we are guaranteed (because it is only ev=
    er provided by d_spliace_alias()) that it will have the same d_parent and s=
    o it will have the same effect when passed to end_creating(). 2026-06-25 7.=
    5 CVE-2026-53244 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53244 ] Linu= x--Linux In the Linux kernel, the following vulnerability has been resolved=
    : xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() The=
    TX metadata area resides in the UMEM buffer which is memory-mapped and con= currently writable by userspace. In xsk_skb_metadata(), csum_start and csum= _offset are read from shared memory for bounds validation, then read again = for skb assignment. A malicious userspace application can race to overwrite=
    these values between the two reads, bypassing the bounds check and causing=
    out-of-bounds memory access during checksum computation in the transmit pa= th. Fix this by reading csum_start and csum_offset into local variables onc=
    e, then using the local copies for both validation and assignment. Note tha=
    t other metadata fields (flags, launch_time) and the cached csum fields may=
    be mutually inconsistent due to concurrent userspace writes, but this is b= enign: the only security-critical invariant is that each field's validated = value is the same one used, which local caching guarantees. 2026-06-25 7.8 = CVE-2026-53250 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53250 ] Linux-= -Linux In the Linux kernel, the following vulnerability has been resolved: = Bluetooth: bnep: reject short frames before parsing A BNEP peer can send a = short BNEP SDU. bnep_rx_frame() reads the packet type byte immediately and,=
    for control packets, reads the control opcode and setup UUID-size byte bef= ore proving that those bytes are present. bnep_rx_control() also dereferenc=
    es the control opcode without rejecting an empty control payload. Use skb_p= ull_data() for the fixed fields in bnep_rx_frame() so a NULL return gates e= ach dereference. Split the control handler so the frame path can pass an op= code that has already been pulled, and keep the byte-buffer wrapper for ext= ension control payloads. For BNEP_SETUP_CONN_REQ, name the UUID-size byte b= efore pulling the setup payload. struct bnep_setup_conn_req carries destina= tion and source service UUIDs after that byte, each uuid_size bytes, so the=
    parser now documents that tuple explicitly instead of leaving the pull len= gth as an opaque multiplication. Validation reproduced this kernel report: = KASAN slab-out-of-bounds in bnep_rx_frame.isra.0+0x130c/0x1790 The buggy ad= dress belongs to the object at ffff88800c0f7908 which belongs to the cache = kmalloc-8 of size 8 The buggy address is located 0 bytes to the right of al= located 1-byte region [ffff88800c0f7908, ffff88800c0f7909) Read of size 1 C= all trace: dump_stack_lvl+0xb3/0x140 (?:?) print_address_description+0x57/0= x3a0 (?:?) bnep_rx_frame+0x130c/0x1790 (net/bluetooth/bnep/core.c:306) prin= t_report+0xb9/0x2b0 (?:?) __virt_addr_valid+0x1ba/0x3a0 (?:?) srso_alias_re= turn_thunk+0x5/0xfbef5 (?:?) kasan_addr_to_slab+0x21/0x60 (?:?) kasan_repor= t+0xe0/0x110 (?:?) process_one_work+0xfce/0x17e0 (kernel/workqueue.c:3200) = worker_thread+0x65c/0xe40 (?:?) __kthread_parkme+0x184/0x230 (?:?) kthread+= 0x35e/0x470 (?:?) _raw_spin_unlock_irq+0x28/0x50 (?:?) ret_from_fork+0x586/= 0x870 (?:?) __switch_to+0x74f/0xdc0 (?:?) ret_from_fork_asm+0x1a/0x30 (?:?)=
    2026-06-25 7.1 CVE-2026-53253 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-53253 ] Linux--Linux In the Linux kernel, the following vulnerability has=
    been resolved: ipv6: anycast: insert aca into global hash under idev->lock=
    syzbot reported a splat [1]: a slab-use-after-free in ipv6_chk_acast_addr(=
    ), which walks the global inet6_acaddr_lst[] hash under RCU and dereference=
    s a struct ifacaddr6 that has already been freed while still linked in the = hash, so a later reader walks into a dangling node. In __ipv6_dev_ac_inc() = the aca is allocated with refcount 1, then aca_get() bumps it to 2 to keep =
    it alive across the unlocked region. It is published to idev->ac_list under=
    idev->lock, but ipv6_add_acaddr_hash() runs after write_unlock_bh(). A con= current teardown (ipv6_ac_destroy_dev() from addrconf_ifdown(), under RTNL)=
    can slip into that window: CPU0 __ipv6_dev_ac_inc CPU1 ipv6_ac_destroy_dev=
    (RTNL) ------------------------------ ------------------------------------=
    aca_alloc() refcnt 1 aca_get() refcnt 2 write_lock_bh(idev->lock) add aca =
    to ac_list write_unlock_bh(idev->lock) write_lock_bh(idev->lock) pull aca o=
    ff ac_list write_unlock_bh(idev->lock) ipv6_del_acaddr_hash(aca) hlist_del_= init_rcu() is a no-op, aca is not in the hash yet aca_put() refcnt 2->1 ipv= 6_add_acaddr_hash(aca) aca now inserted into the hash aca_put() refcnt 1->0=
    call_rcu(aca_free_rcu) -> kfree(aca) The hash removal becomes a no-op beca= use the insertion has not happened yet, so once CPU0 inserts and drops the = last reference, the aca is freed while still linked in inet6_acaddr_lst[], = and readers dereference freed memory after the slab slot is reused. This wi= ndow opened once RTNL stopped serializing the join path against device tear= down. Move ipv6_add_acaddr_hash() inside the idev->lock section so the ac_l= ist and hash insertions are atomic with respect to teardown: a racing remov=
    er now either misses the aca entirely or finds it in both lists. acaddr_has= h_lock is now nested under idev->lock, which is acquired in softirq context=
    , so switch all acaddr_hash_lock sites to spin_lock_bh() to avoid the irq l= ock inversion reported in [2]. [1] https://syzkaller.appspot.com/bug?extid= =3Da01df04303c131efbf3a [2] https://lore.kernel.org/netdev/6a194ef7.ba3b151= 3.1890b4.0000.GAE@google.com/ 2026-06-25 7.8 CVE-2026-53259 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-53259 ] Linux--Linux In the Linux kernel, th=
    e following vulnerability has been resolved: l2tp: pppol2tp: hold reference=
    to session in pppol2tp_ioctl() pppol2tp_ioctl() read sock->sk->sk_user_dat=
    a directly without any locks or reference counting. If a controllable sleep=
    was induced during copy_from_user() (e.g. via a userfaultfd page fault sle= ep), a concurrent socket close could trigger pppol2tp_session_close() async= hronously. This frees the l2tp_session structure via the l2tp_session_del_w= ork workqueue. Upon resuming, the ioctl thread dereferences the stale sessi=
    on pointer, resulting in a Use-After-Free (UAF). Fix this by securely fetch= ing the session reference using the RCU-safe, refcounted helper pppol2tp_so= ck_to_session(sk) on entry. This locks the session's refcount across the sl= eep. We structured the function to exit via standard err breaks, guaranteei=
    ng that l2tp_session_put() is cleanly called on all return paths to drop th=
    e reference. To preserve existing behavior we validate the session and its = magic signature only for the specific L2TP commands that require it. This e= nsures that generic/unknown ioctls called on an unconnected socket still re= turn -ENOIOCTLCMD and correctly fall back to generic handlers (e.g. in sock= _do_ioctl()). 2026-06-25 7.8 CVE-2026-53262 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-53262 ] Linux--Linux In the Linux kernel, the following vuln= erability has been resolved: net/sched: act_api: use RCU with deferred free= ing for action lifecycle When NEWTFILTER and DELFILTER are run concurrently=
    it is possible to create a race with an associated action. Let's illustrat=
    e with CPU0 running NEWTFILTER and CPU1 running DELFILTER: 0: mutex_lock() = <-- holds the idr lock 0: rcu_read_lock() 0: p =3D idr_find(idr, index) <--=
    action p is valid (RCU protects IDR) 0: mutex_unlock() <-- releases the id=
    r lock 1: refcount_dec_and_mutex_lock() <-- refcnt 1->0, mutex held 1: idr_= remove(idr, index) <-- Action removed from IDR 1: mutex_unlock() <-- mutex = released allowing us to delete the action 1: tcf_action_cleanup(p); kfree(p=
    ) <-- Kfrees p immediately, no deferral 0: refcount_inc_not_zero(&p->tcfa_r= efcnt) <-- ouch, UAF p points to freed memory This patch fixes the race con= dition between NEWTFILTER and DELFILTER by adding struct rcu_head to tc_act= ion used in the deferral and introducing a call_rcu() in the delete path to=
    defer the final kfree(). Note: this is a revert of commit d7fb60b9cafb ("n= et_sched: get rid of tcfa_rcu") but also modernization/simplification to di= rectly use kfree_rcu(). Let's illustrate the new restored code path: 0: rcu= _read_lock() 1: refcount_dec_and_mutex_lock() <-- refcnt 1->0, mutex held 1=
    : idr_remove(idr, index) 1: mutex_unlock() 1: call_rcu(&p->tcfa_rcu, tcf_ac= tion_rcu_free) <-- defer kfree after grace period 0: p =3D idr_find(idr, in= dex) 0: refcount_inc_not_zero(&p->tcfa_refcnt) <-- fails, refcnt already 0 =
    1: rcu_read_unlock() <-- release so freeing can run after grace period Afte=
    r CPU1 calls idr_remove(), the object is no longer reachable through the ID=
    R. CPU0's subsequent idr_find() will return NULL, and even if it still held=
    a stale pointer, the immediate kfree() is now deferred until after the RCU=
    grace period, so no UAF can occur. 2026-06-25 7.8 CVE-2026-53264 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-53264 ] Linux--Linux In the Linux kern= el, the following vulnerability has been resolved: dm cache policy smq: che=
    ck allocation under invalidate lock commit 2d1f7b65f5de ("dm cache policy s= mq: fix missing locks in invalidating cache blocks") added mq->lock around = the destructive part of smq_invalidate_mapping(), but left the e->allocated=
    check outside the critical section. That leaves a check-then-act race. Two=
    concurrent invalidators can both observe e->allocated as true before eithe=
    r of them takes mq->lock. The first invalidator that acquires the lock remo= ves the entry from the queues and hash table and then calls free_entry(), w= hich clears e->allocated and puts the entry back on the free list. The seco=
    nd invalidator can then acquire mq->lock and continue with the stale result=
    of the unlocked check. This can corrupt the SMQ queues or hash table by de= leting an entry that is no longer on those structures. It can also hit the = allocation check in free_entry() when the same entry is freed again. Move t=
    he allocation check under mq->lock so the predicate and the destructive ope= rations are serialized by the same lock. 2026-06-25 7.8 CVE-2026-53265 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-53265 ] Linux--Linux In the Linux=
    kernel, the following vulnerability has been resolved: netfilter: nft_ct: = bail out on template ct in get eval I noticed this issue while looking at a=
    historic syzbot report [1]. A rule like the one below is enough to trigger=
    the bug: table ip t { chain pre { type filter hook prerouting priority raw=
    ; ct zone set 1 ct original saddr 1.2.3.4 accept } } The first expression a= ttaches a per-cpu template ct via nft_ct_set_zone_eval() (nf_ct_tmpl_alloc =
    kzalloc, tuple is all zero, nf_ct_l3num(ct) =3D=3D 0). The next expressi=
    on then calls nft_ct_get_eval() on the same skb, treats the template as a r= eal ct and hits the 16-byte memcpy path. With dreg at NFT_REG32_15 this ove= rflows past struct nft_regs on the kernel stack; with smaller dreg values i=
    t silently clobbers adjacent registers. Reject template ct at the eval entr=
    y and in nft_ct_get_fast_eval(), mirroring the check nft_ct_set_eval() alre= ady has. Additionally, bound the address copy in NFT_CT_SRC / NFT_CT_DST by=
    priv->len instead of by nf_ct_l3num(ct): nf_ct_get_tuple() zeroes the tupl=
    e before pkt_to_tuple() fills in only the protocol-relevant leading bytes, =
    so the trailing bytes of tuple->{src,dst}.u3.all are well-defined zero. pri= v->len is validated at rule load, so the copy size is now bounded by the de= stination register rather than by an untrusted field on the conntrack. [1]:=
    https://syzkaller.appspot.com/bug?id=3D389cf09cb72926114fce90dc85a2c3231dc= b647c 2026-06-25 7.8 CVE-2026-53267 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-53267 ] Linux--Linux In the Linux kernel, the following vulnerabilit=
    y has been resolved: ipvs: clear the svc scheduler ptr early on edit ip_vs_= edit_service() while unbinding the old scheduler clears the svc->scheduler = ptr after the scheduler module initiates RCU callbacks. This can cause pack= ets to use the old scheduler at the time when svc->sched_data is already fr= eed after RCU grace period. Fix it by clearing the ptr early in ip_vs_unbin= d_scheduler(), before the done_service method schedules any RCU callbacks. = Also, if the new scheduler fails to initialize when replacing the old sched= uler, try to restore the old scheduler while still returning the error code=
    . 2026-06-25 7.8 CVE-2026-53270 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-53270 ] Linux--Linux In the Linux kernel, the following vulnerability ha=
    s been resolved: tee: optee: prevent use-after-free when the client exits b= efore the supplicant Commit 70b0d6b0a199 ("tee: optee: Fix supplicant wait = loop") made the client wait as killable so it can be interrupted during shu= tdown or after a supplicant crash. This changes the original lifetime expec= tations: the client task can now terminate while the supplicant is still pr= ocessing its request. If the client exits first it removes the request from=
    its queue and kfree()s it, while the request ID remains in supp->idr. A su= bsequent lookup on the supplicant path then dereferences freed memory, lead= ing to a use-after-free. Serialise access to the request with supp->mutex: =
    * Hold supp->mutex in optee_supp_recv() and optee_supp_send() while looking=
    up and touching the request. * Let optee_supp_thrd_req() notice that the c= lient has terminated and signal optee_supp_send() accordingly. With these c= hanges the request cannot be freed while the supplicant still has a referen= ce, eliminating the race. 2026-06-25 7.8 CVE-2026-53273 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-53273 ] Linux--Linux In the Linux kernel, the fo= llowing vulnerability has been resolved: Bluetooth: ISO: Fix a use-after-fr=
    ee of the hci_conn pointer In iso_sock_rebind_bc(), the bis pointer is cach= ed, then the socket lock is dropped: bis =3D iso_pi(sk)->conn->hcon; /* Rel= ease the socket before lookups since that requires hci_dev_lock * which sha=
    ll not be acquired while holding sock_lock for proper * ordering. */ releas= e_sock(sk); hci_dev_lock(bis->hdev); During the unlocked window, could a co= ncurrent close() destroy the connection and free the bis structure, causing=
    hci_dev_lock(bis->hdev) to access memory after it is freed, fix this by us= ing the hdev reference which was safely acquired via iso_conn_get_hdev(). 2= 026-06-25 7.8 CVE-2026-53276 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 53276 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: btrfs: only release the dirty pages io tree after successful = writes [WARNING] With extra warning on dirty extent buffers at umount (aka,=
    the next patch in the series), test case generic/388 can trigger the follo= wing warning about dirty extent buffers at unmount time: BTRFS critical (de= vice dm-2 state E): emergency shutdown BTRFS error (device dm-2 state E): e= rror while writing out transaction: -30 BTRFS warning (device dm-2 state E)=
    : Skipping commit of aborted transaction. BTRFS error (device dm-2 state EA=
    ): Transaction 9 aborted (error -30) BTRFS: error (device dm-2 state EA) in=
    cleanup_transaction:2068: errno=3D-30 Readonly filesystem BTRFS info (devi=
    ce dm-2 state EA): forced readonly BTRFS info (device dm-2 state EA): last = unmount of filesystem 4fbf2e15-f941-49a0-bc7c-716315d2777c ------------[ cu=
    t here ]------------ WARNING: disk-io.c:3311 at invalidate_and_check_btree_= folios+0xfd/0x1ca [btrfs], CPU#8: umount/914368 CPU: 8 UID: 0 PID: 914368 C= omm: umount Tainted: G OE 7.1.0-rc1-custom+ #372 PREEMPT(full) 2de38db8d1de= ae71fde295430a0ff3ab98ccf596 Hardware name: QEMU Standard PC (Q35 + ICH9, 2= 009), BIOS unknown 02/02/2022 RIP: 0010:invalidate_and_check_btree_folios+0= xfd/0x1ca [btrfs] Call Trace: <TASK> close_ctree+0x52e/0x574 [btrfs d2f0b1c= d330d1287e7a9919d112eadfc0e914efd] generic_shutdown_super+0x89/0x1a0 kill_a= non_super+0x16/0x40 btrfs_kill_super+0x16/0x20 [btrfs d2f0b1cd330d1287e7a99= 19d112eadfc0e914efd] deactivate_locked_super+0x2d/0xb0 cleanup_mnt+0xdc/0x1=
    40 task_work_run+0x5a/0xa0 exit_to_user_mode_loop+0x123/0x4b0 do_syscall_64= +0x243/0x7c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> ---[ end trac=
    e 0000000000000000 ]--- BTRFS warning (device dm-2 state EA): unable to rel= ease extent buffer 30539776 owner 9 gen 9 refs 2 flags 0x7 BTRFS warning (d= evice dm-2 state EA): unable to release extent buffer 30621696 owner 257 ge=
    n 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to releas=
    e extent buffer 30638080 owner 258 gen 9 refs 2 flags 0x7 BTRFS warning (de= vice dm-2 state EA): unable to release extent buffer 30654464 owner 7 gen 9=
    refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release e= xtent buffer 30703616 owner 2 gen 9 refs 2 flags 0x7 BTRFS warning (device = dm-2 state EA): unable to release extent buffer 30720000 owner 10 gen 9 ref=
    s 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release exten=
    t buffer 30736384 owner 4 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2=
    state EA): unable to release extent buffer 30752768 owner 11 gen 9 refs 2 = flags 0x7 I'm using a stripped down version, which seems to trigger the war= ning more reliably: _fsstress_pid=3D"" workload() { dmesg -C mkfs.btrfs -f =
    -K $dev > /dev/null echo 1 > /sys/kernel/debug/clear_warn_once mount $dev $= mnt $fsstress -w -n 1024 -p 4 -d $mnt & _fsstress_pid=3D$! sleep 0 $godown = $mnt pkill --echo -PIPE fsstress > /dev/null wait $_fsstress_pid unset _fss= tress_pid umount $mnt if dmesg | grep -q "WARNING"; then fail fi } for (( i=
    =3D 0; i < $runtime; i++ )); do echo "=3D=3D=3D $i/$runtime =3D=3D=3D" wor= kload done [CAUSE] Inside btrfs_write_and_wait_transaction(), we first try =
    to write all dirty ebs, then wait for them to finish. After that we call bt= rfs_extent_io_tree_release() to free all extent states from dirty_pages io = tree. However if we hit an error from btrfs_write_marked_extent(), then we = still call btrfs_extent_io_tree_release() to clear that dirty_pages io tree=
    , which may contain dirty records that we haven't yet submitted. Furthermor=
    e, the later transaction cleanup path will utilize that dirty_pages io tree=
    to properly cleanup those dirty ebs, but since it's already empty, no dirt=
    y ebs are properly cleaned up, thus will later trigger the warnings inside = invalidate_btree_folios(). ---truncated--- 2026-06-26 7.5 CVE-2026-53284 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-53284 ] Linux--Linux In the Lin=
    ux kernel, the following vulnerability has been resolved: drm/xe/eustall: F=
    ix drm_dev_put called before stream disable in close In xe_eu_stall_stream_= close(), drm_dev_put() is called before the stream is disabled and its reso= urces are freed. If this drops the last reference, the device structures co= uld be freed while the subsequent cleanup code still accesses them, leading=
    to a use-after-free. Fix this by moving drm_dev_put() after all device acc= esses are complete. This matches the ordering in xe_oa_release(). (cherry p= icked from commit 35aff528f7297e949e5e19c9cd7fd748cf1cf21c) 2026-06-26 7.8 = CVE-2026-53290 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53290 ] Linux-= -Linux In the Linux kernel, the following vulnerability has been resolved: = net: enetc: fix NTMP DMA use-after-free issue The AI-generated review repor= ted a potential DMA use-after-free issue [1]. If netc_xmit_ntmp_cmd() times=
    out and returns an error, the pending command is not explicitly aborted, w= hile ntmp_free_data_mem() unconditionally frees the DMA buffer. If the buff=
    er has already been reallocated elsewhere, this may lead to silent memory c= orruption. Because the hardware eventually processes the pending command an=
    d perform a DMA write of the response to the physical address of the freed = buffer. To resolve this issue, this patch does the following modifications:=
    1. Convert cbdr->ring_lock from a spinlock to a mutex The lock was origina= lly a spinlock in case NTMP operations might be invoked from atomic context=
    . After downstream support for all NTMP tables, no such usage has materiali= zed. A mutex lock is now required because the driver now needs to reclaim u= sed BDs and release associated DMA memory within the lock's context, while = dma_free_coherent() might sleep. 2. Introduce software command BD (struct n= etc_swcbd) The hardware write-back overwrites the addr and len fields of th=
    e BD, so the driver cannot rely on the hardware BD to free the associated D=
    MA memory. The driver now maintains a software shadow BD storing the DMA bu= ffer pointer, DMA address, and size. And netc_xmit_ntmp_cmd() only reclaims=
    older BDs when the number of used BDs reaches NETC_CBDR_CLEAN_WORK (16). T=
    he software BD enables correct DMA memory release. With this, struct ntmp_d= ma_buf and ntmp_free_data_mem() are no longer needed and are removed. 3. Re= quire callers to hold ring_lock across netc_xmit_ntmp_cmd() netc_xmit_ntmp_= cmd() releases the ring_lock before the caller finishes consuming the respo= nse. At this point, if a concurrent thread submits a new command, it may tr= igger ntmp_clean_cbdr() and free the DMA buffer while it is still in use. M= ove ring_lock ownership to the caller to ensure the response buffer cannot =
    be reclaimed prematurely. So the helpers ntmp_select_and_lock_cbdr() and nt= mp_unlock_cbdr() are added. These changes eliminate the DMA use-after-free = condition and ensure safe and consistent BD reclamation and DMA buffer life= cycle management. 2026-06-26 7.8 CVE-2026-53300 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-53300 ] ljharb--shell-quote shell-quote prior to 1.8.5 f= inalizes parsed tokens in parse() using Array.prototype.concat as a reduce = accumulator, which reallocates and copies the entire growing array on every=
    iteration. As a result parse() runs in O(n^2) time relative to the number =
    of input tokens. An attacker who can supply an attacker-controlled string t=
    o any code path that calls parse() (no shell metacharacters are required; p= lain space-separated words suffice) can block the single-threaded Node.js e= vent loop for an extended period with a small input, resulting in a denial =
    of service. There is no code execution or data disclosure; impact is to ava= ilability only. Fixed in 1.8.5. 2026-06-25 7.5 CVE-2026-13311 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-13311 ] lobehub--lobehub LobeHub is a work= -and-lifestyle space to find, build, and collaborate with agent teammates t= hat grow with you. Prior to 2.1.57, the /webapi/proxy endpoint on app.lobeh= ub.com accepts a URL in the POST body and fetches it server-side without an=
    y authentication. An attacker can use this to make arbitrary outbound reque= sts from LobeHub's infrastructure, leak Vercel deployment details, and inje=
    ct cookies on the lobehub.com domain through reflected Set-Cookie headers. = This vulnerability is fixed in 2.1.57. 2026-06-23 9 CVE-2026-54157 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-54157 ] lostisland--faraday Faraday i=
    s an HTTP client library abstraction layer that provides a common interface=
    over many adapters. From 1.0.0 until 1.10.6 and 2.14.3, Faraday::NestedPar= amsEncoder, the default nested query parameter encoder/decoder in Faraday, = decodes nested query strings without enforcing a maximum nesting depth. A c= rafted query string causes Faraday to build a deeply nested Ruby Hash struc= ture. The internal dehash routine then recursively walks this attacker-cont= rolled structure without a depth limit. At sufficient depth, Ruby raises an=
    uncaught SystemStackError (stack level too deep), crashing the calling thr= ead or worker. This can lead to denial of service in applications that pass=
    attacker-controlled query strings to Faraday's nested query parsing or URL= -building paths. This vulnerability is fixed in 1.10.6 and 2.14.3. 2026-06-=
    24 7.5 CVE-2026-54297 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54297 ]=
    MainWP--MainWP Child Unauthenticated Broken Access Control in MainWP Child=
    <=3D 6.1.1 versions. 2026-06-25 7.5 CVE-2026-27366 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-27366 ] MarketingFire--Widget Options Contributor Re= mote Code Execution (RCE) in Widget Options <=3D 4.2.3 versions. 2026-06-25=
    9.9 CVE-2026-54823 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54823 ] M= arlinFirmware--Marlin Marlin Firmware through 2.1.2.7, fixed in commit 1f25= 5d1, when built with MESH_BED_LEVELING enabled, contains an out-of-bounds w= rite vulnerability in the M421 G-code handler that allows attackers to corr= upt firmware memory by supplying out-of-range X and Y grid indices. Attacke=
    rs can send a single crafted G-code command via USB serial, network interfa= ce, or malicious gcode file to write an attacker-controlled 32-bit float va= lue past the z_values array bounds, corrupting adjacent firmware variables = and causing denial of service or firmware state corruption. 2026-06-24 9.1 = CVE-2026-56111 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56111 ] mastod= on--mastodon Mastodon is a free, open-source social network server based on=
    ActivityPub. Prior to 4.5.10, 4.4.17, and 4.3.23, when using Ruby versions=
    older than 3.4, PrivateAddressCheck.private_address? returns false for IPv= 4-mapped IPv6 addresses (::ffff:a.b.c.d) corresponding to some private IPv4=
    addresses, depending on Ruby version, this can include loopback, RFC1918 p= rivate networks, and link-local space. An attacker who controls DNS for any=
    domain can publish an AAAA record with such a mapped address; any outbound=
    HTTP fetch Mastodon performs against that hostname then opens a real TCP c= onnection to the underlying IPv4 address, including 127.0.0.1 and cloud-met= adata endpoints such as 169.254.169.254. This vulnerability is fixed in 4.5= .10, 4.4.17, and 4.3.23. 2026-06-24 8.6 CVE-2026-47389 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-47389 ] mastodon--mastodon Mastodon is a free, op= en-source social network server based on ActivityPub. Prior to 4.5.11, 4.4.= 18, and 4.3.24, a DoS can be triggered by (Uncaught Exception vulerability)=
    , due to missing exception handling in the math sanitizer. Malformed <math>=
    nodes can result in a DoS of a whole server or targeted users services, de= pending on the type of action that includes the malformed nodes and the ser= vices interacting with it. This vulnerability is fixed in 4.5.11, 4.4.18, a=
    nd 4.3.24. 2026-06-24 7.5 CVE-2026-50129 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-50129 ] max-mapper--extract-zip extract-zip does not validate s= ymlink targets when extracting zip archives. When processing a malicious zi=
    p file containing a symlink with a relative path like '../../../../etc/pass= wd', extract-zip will extract the symlink without validation, allowing it t=
    o point outside the extraction directory. Depending on how extract-zip is u= sed, an attacker could read or write to arbitrary files. 2026-06-26 8.1 CVE= -2026-56876 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56876 ] MB connec=
    t line--mbCONNECT24 An high privileged remote attacker can access a hidden = configuration method, that should not be accessible by any user, to modify = critical program parameters. This can result in a total loss of confidentia= lity, integrity and availability. 2026-06-23 7.2 CVE-2026-10521 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-10521 ] Melapress--WP Activity Log Subsc= riber Cross Site Scripting (XSS) in WP Activity Log <=3D 5.6.3.1 versions. = 2026-06-25 7.1 CVE-2026-56005 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -56005 ] MessagePack-CSharp--MessagePack-CSharp MessagePack for C# is a Mes= sagePack serializer for C#. Prior to 2.5.301 and 3.1.7, A vulnerability exi= sts in the optional LZ4 decompression path used by MessagePack compression = modes Lz4Block and Lz4BlockArray. The decoder implementation is based on a = deprecated fast-decompression algorithm that does not take a source-length = bound. A remote attacker can send a crafted MessagePack payload with manipu= lated LZ4 token/length fields to force out-of-bounds reads from the compres= sed input buffer. In affected environments, this can trigger an AccessViola= tionException during decompression, causing process termination (denial of = service). Under some conditions, limited unintended memory disclosure from = over-read data may also be possible before failure. This vulnerability is f= ixed in 2.5.301 and 3.1.7. 2026-06-22 8.2 CVE-2026-48109 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-48109 ] MessagePack-CSharp--MessagePack-CSharp = MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301 and=
    3.1.7, MessagePackReader.TrySkip() recursively descends into nested arrays=
    and maps without incrementing the reader depth or calling the configured d= epth checks. This bypasses MessagePackSecurity.MaximumObjectGraphDepth, the=
    library's documented protection against deeply nested object graphs. Many = generated and dynamic formatters call reader.Skip() when they encounter unk= nown map keys, unknown array members, ignored fields, or data that should b=
    e skipped for forward compatibility. A deeply nested value in one of these = skipped positions can therefore cause unbounded recursion and an uncatchabl=
    e StackOverflowException. This vulnerability is fixed in 2.5.301 and 3.1.7.=
    2026-06-22 7.5 CVE-2026-48506 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-48506 ] MHSanaei--3x-ui 3X-UI is a web control panel for managing Xray-co=
    re servers. Prior to 3.3.1, an authenticated administrator can abuse the da= tabase import functionality to achieve arbitrary file write on the host by = modifying Xray configuration values stored in the database. This can be lev= eraged to obtain code execution and persistent access as the user running X= ray (including root when Xray is running as root). This vulnerability is fi= xed in 3.3.1. 2026-06-25 7.2 CVE-2026-55477 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-55477 ] miurahr--py7zr py7zr is a Python-based library and u= tility to support 7zip archive compression, decompression, encryption and d= ecryption. Versions 1.1.2 and below contain an an arbitrary file write vuln= erability, which allows symbolic links to be recreated outside the destinat= ion directory via crafted malicious symbolic link chains. When using extrac= tall to extract an archive, the library restores these symbolic links, link= ing them to arbitrary directories on the host file system. During extractio=
    n, the program only checks the link arcname within the destination director=
    y, but ignores the combined symlink path resolution. Attackers can exploit = this vulnerability by constructing malicious archives, thereby bypassing th=
    e directory boundary restrictions implemented by the extractor. Subsequent = extraction of regular files through these symbolic links can result in arbi= trary file writes. This vulnerability may lead to remote code execution, pr= ivilege escalation, data corruption, or denial of service. This issue has b= een fixed in version 1.1.3. 2026-06-24 8 CVE-2026-23879 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-23879 ] MyBB--MyBB MyBB 1.8.40 does not restrict=
    which usergroup a limited Admin Control Panel user may assign when creatin=
    g or editing users; the user module offers the Administrators group (gid 4)=
    and its datahandler's verify_usergroup() unconditionally returns true. An = admin holding only the delegated user-management permission can assign the = Administrators group to an account and escalate to the full Administrator p= ermission set. 2026-06-28 7.2 CVE-2026-58054 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-58054 ] n8n--n8n n8n before 2.20.0 contains a credential ex= filtration vulnerability in the POST /rest/dynamic-node-parameters/options = endpoint that allows authenticated users to bypass Allowed HTTP Request Dom= ains restrictions. Attackers with credential access can cause the n8n serve=
    r to issue HTTP requests with credentials to unauthorized hosts, exfiltrati=
    ng sensitive authentication data. 2026-06-22 9.1 CVE-2026-56348 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-56348 ] n8n--n8n n8n before version 2.4.=
    0 contains a sql injection vulnerability in MySQL, PostgreSQL, and Microsof=
    t SQL nodes that allows authenticated users to inject arbitrary SQL through=
    unescaped identifier values in node configuration parameters. Attackers wi=
    th workflow creation permissions can supply specially crafted table or colu=
    mn names to execute unauthorized database commands and compromise data inte= grity. 2026-06-24 8.2 CVE-2026-56351 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-56351 ] NetComm Wireless Pty Ltd--NF20MESH NetComm NF20MESH routers=
    running firmware R6B031 and earlier contain an authenticated remote code e= xecution vulnerability that allows authenticated attackers to execute arbit= rary commands as root by injecting shell metacharacters into the username J= SON parameter processed by the dalStorage_addUserAccount function. Attacker=
    s can exploit the unsafe concatenation of user-supplied input into a shell = command string passed to rut_doSystemAction without sanitization to achieve=
    full root-level command execution on the underlying operating system. 2026= -06-23 8.8 CVE-2026-35018 [ https://www.cve.org/CVERecord?id=3DCVE-2026-350=
    18 ] NetComm Wireless Pty Ltd--NF20MESH NetComm NF20MESH routers running fi= rmware R6B031 and earlier contain an authentication bypass vulnerability th=
    at allows unauthenticated attackers to gain administrative access by exploi= ting a hardcoded AES-256 key used to encrypt session cookies for the web ma= nagement interface. Attackers can forge a valid encrypted session cookie us= ing the shared hardcoded key and bypass authentication checks to obtain ful=
    l administrative control of the management interface while any legitimate a= dministrator session is active. 2026-06-23 8.1 CVE-2026-35019 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-35019 ] newscred--Welcome Software Publish= ing The Welcome Software Publishing plugin for WordPress is vulnerable to A= rbitrary Options Update in all versions up to and including 0.0.31. This is=
    due to a missing capability check in the nc_setOption() function, which is=
    exposed via the nc.setOption XML-RPC method. The function authenticates th=
    e user via $wp_xmlrpc_server->login() (verifying credentials are valid) but=
    does not perform any authorization check such as current_user_can('manage_= options'). This makes it possible for authenticated attackers, with Subscri= ber-level access and above, to update arbitrary WordPress options via XML-R=
    PC requests. This can be leveraged to change the default_role option to 'ad= ministrator' and then register a new administrator account, achieving full = privilege escalation and site takeover. 2026-06-24 8.8 CVE-2026-4297 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-4297 ] nicashmu--Cincopa video and = media plug-in The Cincopa video and media plug-in plugin for WordPress is v= ulnerable to Stored Cross-Site Scripting via cincopa Shortcode in Post Comm= ents in all versions up to, and including, 1.163 due to insufficient input = sanitization and output escaping. This makes it possible for unauthenticate=
    d attackers to inject arbitrary web scripts in pages that will execute when= ever a user accesses an injected page. Exploitation is possible because the=
    plugin processes the [cincopa] shortcode via a comment_text filter hook, a= llowing unauthenticated visitors who can post comments to supply a maliciou=
    s shortcode argument that persists in the database. 2026-06-24 7.2 CVE-2026= -10092 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10092 ] nicolargo--gla= nces Glances is an open-source system cross-platform monitoring tool. Prior=
    to 4.5.5, the Glances KVM/QEMU monitoring engine (glances/plugins/vms/engi= nes/virsh.py) passes VM domain names, read directly from virsh list --all o= utput, into f-string command templates that are processed by secure_popen()=
    . secure_popen() is explicitly designed to interpret &&, |, and > as shell = operators. Because domain names are never sanitised before interpolation, a=
    ny user with the ability to create or rename a KVM/QEMU virtual machine can=
    execute arbitrary commands as the OS user running Glances - commonly root =
    on hypervisor hosts. This vulnerability is fixed in 4.5.5. 2026-06-25 7.8 C= VE-2026-46606 [ https://www.cve.org/CVERecord?id=3DCVE-2026-46606 ] nicolar= go--glances Glances is an open-source system cross-platform monitoring tool=
    . Prior to 4.5.5, glances/outdated.py uses pickle.load() to read a version-= check cache file stored at a predictable, world-accessible path (~/.cache/g= lances/glances-version.db or $XDG_CACHE_HOME/glances/glances-version.db). N=
    o integrity check, signature verification, or format validation is performe=
    d before deserialization. An attacker with write access to that path - thro= ugh any of several realistic local or container-level scenarios - can plant=
    a malicious pickle file and achieve arbitrary code execution as the OS use=
    r running Glances the next time it starts with version checking enabled (th=
    e default). This vulnerability is fixed in 4.5.5. 2026-06-25 7.8 CVE-2026-4= 6607 [ https://www.cve.org/CVERecord?id=3DCVE-2026-46607 ] nicolargo--glanc=
    es Glances is an open-source system cross-platform monitoring tool. Prior t=
    o 4.5.5, the Glances XML-RPC server (glances -s) introduced a configurable = CORS origin list in version 4.5.3 as a mitigation for CVE-2026-33533. Howev= er, the implementation silently falls back to Access-Control-Allow-Origin: =
    * whenever cors_origins contains more than one entry. An operator who confi= gures an explicit two-entry allowlist (e.g. two internal dashboard origins)=
    intending to restrict browser access instead receives the unrestricted wil= dcard. A malicious web page served from any origin can issue a CORS simple = request to /RPC2 and read the full system monitoring dataset without the vi= ctim's knowledge. This vulnerability is fixed in 4.5.5. 2026-06-25 7.4 CVE-= 2026-46608 [ https://www.cve.org/CVERecord?id=3DCVE-2026-46608 ] nicolargo-= -glances Glances is an open-source system cross-platform monitoring tool. F= rom 4.0.8 until 4.5.5, the secure_popen() function in glances/secure.py int= erprets > (file redirection), | (pipe), and && (command chaining) operators=
    in command strings. These operators are applied without any validation on = the target file path, piped command, or chained command. When Application M= onitoring Process (AMP) modules load their command or service_cmd configura= tion values from glances.conf, those values are passed directly to secure_p= open() with no sanitization. This allows an attacker who can modify the Gla= nces configuration file to write arbitrary content to arbitrary filesystem = paths (via >), chain arbitrary commands (via &&), or pipe command output to=
    arbitrary programs (via |). This vulnerability is fixed in 4.5.5. 2026-06-=
    25 7.8 CVE-2026-53925 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53925 ]=
    nltk--nltk NLTK (Natural Language Toolkit) is a suite of open source Pytho=
    n modules, data sets, and tutorials supporting research and development in = Natural Language Processing. Prior to 3.10.0-rc1, nltk.data.load() in NLTK =
    is vulnerable to path traversal via URL-encoded path separators and travers=
    al segments when using the nltk: URL scheme. The unsafe-path regex check is=
    performed before url2pathname() decodes the %xx sequences (a classic decod= e-after-check / TOCTOU-style flaw), allowing an attacker to bypass the prot= ection documented in NLTK's SECURITY.md and read arbitrary files from the f= ilesystem. While literal traversal strings such as ../../../etc/passwd are = correctly blocked, encoded variants such as %2fetc%2fpasswd, %2e%2e%2f..., = and ..%2f..%2f slip past the regex and are subsequently decoded into a real=
    filesystem path. This vulnerability is fixed in 3.10.0-rc1. 2026-06-22 7.5=
    CVE-2026-54293 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54293 ] nmedi= a--Frontend File Manager Plugin The Frontend File Manager Plugin plugin for=
    WordPress is vulnerable to Authenticated Arbitrary File Deletion in versio=
    ns up to and including 23.6. This is due to a case-sensitive bypass of the = wpfm_dir_path parameter sanitization in the wpfm_file_meta_update AJAX hand= ler, where supplying WPFM_DIR_PATH in uppercase evades the unset check and =
    is normalized to wpfm_dir_path by sanitize_key() during update_post_meta(),=
    allowing an attacker to overwrite the stored file path with an arbitrary f= ilesystem path that is then passed directly to unlink() in delete_file_loca= lly() without any directory containment validation. This makes it possible = for authenticated attackers with Subscriber-level access to delete arbitrar=
    y files on the server, including sensitive files such as wp-config.php, pot= entially leading to full site takeover. 2026-06-27 8.1 CVE-2026-8095 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-8095 ] notepad-plus-plus--notepad-p= lus-plus Notepad++ is a free and open-source source code editor. Prior to 8= .9.6.1, the <GUIConfig name=3D"commandLineInterpreter"> tag in config.xml i=
    s read by NppXml::value() (Parameters.cpp:6430) and stored in _nppGUI._comm= andLineInterpreter without any validation, whitelist, or digital signature = check. When the user triggers IDM_FILE_OPEN_CMD (File =C3=A2=E2=80=A0=E2=80= =99 Open Containing Folder =C3=A2=E2=80=A0=E2=80=99 cmd), NppCommands.cpp:2=
    28 creates a Command object with this value and calls run(), which invokes = ShellExecute (RunDlg.cpp:221) with the attacker-controlled string as the ex= ecutable path. This vulnerability is fixed in 8.9.6.1. 2026-06-26 7.8 CVE-2= 026-48778 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48778 ] notepad-plu= s-plus--notepad-plus-plus Notepad++ is a free and open-source source code e= ditor. Prior to 8.9.6.1, the <Command> tag text content inside <UserDefined= Commands> in shortcuts.xml is read by NppXml::value(aNode) (Parameters.cpp:= 3658) in the feedUserCmds() function and stored in UserCommand._cmd without=
    any validation. When the user clicks the corresponding entry in the Run me= nu, NppCommands.cpp:4264 creates a Command object with string2wstring(ucmd.= getCmd()) and calls run(), which invokes ShellExecute (RunDlg.cpp:221) with=
    the attacker-controlled string as the executable path. The injected comman=
    d appears as a normal menu item in the Run menu, making it a viable persist= ence mechanism. This vulnerability is fixed in 8.9.6.1. 2026-06-26 7.8 CVE-= 2026-48800 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48800 ] notepad-pl= us-plus--notepad-plus-plus Notepad++ is a free and open-source source code = editor. In v8.9.6.1, isInTrustedDirectory() does NOT canonicalize the path = before checking. It uses a prefix-based check (PathIsPrefix() or equivalent=
    ) that matches paths starting with trusted directory strings. A path traver= sal using ..\..\ after a trusted directory prefix passes the check while re= solving to an untrusted location. The CVE-2026-48800 patch adds isInTrusted= Directory() validation in Command::run() (RunDlg.cpp) before calling ShellE= xecute(). This function checks whether the resolved executable path is unde=
    r a trusted directory. This vulnerability is fixed in 8.9.6.2. 2026-06-26 7=
    .8 CVE-2026-52884 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52884 ] NSq= uared--Simply Schedule Appointments Unauthenticated Cross Site Scripting (X= SS) in Simply Schedule Appointments <=3D 1.6.12.2 versions. 2026-06-26 7.1 = CVE-2026-57317 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57317 ] Online=
    Web Tutor--Library Management System Unauthenticated SQL Injection in Libr= ary Management System <=3D 3.5.7 versions. 2026-06-26 9.3 CVE-2026-56034 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-56034 ] oooorgle--Quotes llama = Unauthenticated SQL Injection in Quotes llama <=3D 3.1.5 versions. 2026-06-=
    26 9.3 CVE-2026-56062 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56062 ]=
    Open Health Imaging Foundation (OHIF)--DICOM Web Viewer Framework Two data=
    sources (DICOMWebProxy and DICOMJSON) shipped in the default configuration=
    fetch an arbitrary URL parameter without validation. A global authenticati=
    on service in OHIF automatically injects the authenticated user's OIDC Bear=
    er token into the resulting requests, sending it to the attacker-controlled=
    server. DICOMweb data sources are not impacted. 2026-06-25 8.2 CVE-2026-12= 473 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12473 ] open-webui--open-= webui Open WebUI is a self-hosted artificial intelligence platform designed=
    to operate entirely offline. Prior to 0.9.6, backend/open_webui/utils/oaut= h.py::_process_picture_url calls validate_url(picture_url) on the initial U=
    RL only, then invokes aiohttp.ClientSession.get(picture_url, ...) without a= llow_redirects=3DFalse. aiohttp's default is allow_redirects=3DTrue, max_re= directs=3D10; the function does not pass the project's AIOHTTP_CLIENT_ALLOW= _REDIRECTS env constant either. An attacker with a valid OAuth IdP identity=
    can therefore submit a public URL that 302-redirects to an internal addres=
    s and read the internal response body via the attacker's own profile_image_= url field. This vulnerability is fixed in 0.9.6. 2026-06-23 8.5 CVE-2026-54= 008 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54008 ] open-webui--open-= webui Open WebUI is a self-hosted artificial intelligence platform designed=
    to operate entirely offline. Prior to 0.9.6, Open WebUI lets an authentica= ted user attach arbitrary file_id values to their own chat message without = checking whether they own or can read those files. If the attacker then sha= res that chat and grants themselves read access, has_access_to_file() treat=
    s the victim file as accessible through the shared chat, and the file endpo= ints read or delete the victim file. This vulnerability is fixed in 0.9.6. = 2026-06-23 8.3 CVE-2026-54010 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -54010 ] open-webui--open-webui Open WebUI is a self-hosted artificial inte= lligence platform designed to operate entirely offline. Prior to 0.9.6,Open=
    WebUI renders Mermaid blocks from Markdown files in the file preview panel=
    and inserts the generated SVG into the DOM using innerHTML. Because Mermai=
    d is configured with securityLevel: 'loose', attacker-controlled Mermaid co= ntent can be rendered unsafely in this flow. A working payload was validate=
    d through the Markdown preview path, resulting in JavaScript execution in t=
    he victim's browser under the application origin. This vulnerability is fix=
    ed in 0.9.6. 2026-06-23 8.7 CVE-2026-54011 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-54011 ] open-webui--open-webui Open WebUI is a self-hosted ar= tificial intelligence platform designed to operate entirely offline. Prior =
    to 0.9.6, Open WebUI lets a user who can create, update, or import workspac=
    e models store arbitrary meta.knowledge entries on their model without chec= king whether they own or can read the referenced files. Open WebUI then tre= ats meta.knowledge entries of type file as an authorization source in two p= laces: the built-in view_file tool reads the file's extracted text, and has= _access_to_file()'s model branch authorizes the file content and file delet=
    e endpoints. A malicious model owner can therefore attach another user's fi=
    le ID to their model metadata and read or delete that private file. This vu= lnerability is fixed in 0.9.6. 2026-06-23 7.1 CVE-2026-54012 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-54012 ] open-webui--open-webui Open WebUI i=
    s a self-hosted artificial intelligence platform designed to operate entire=
    ly offline. Prior to 0.9.6, Open WebUI patched SVG XSS in user profile imag=
    es and webhook profile images but forgot to apply the same fix to model pro= file images. The ModelMeta class has no validate_profile_image_url field va= lidator, and the model image serving endpoint has no MIME allowlist or nosn= iff header. Any authenticated user with workspace.models permission (enable=
    d by default) can store a data:image/svg+xml;base64,... payload in a model'=
    s profile image and achieve full account takeover of anyone who navigates t=
    o the image URL. This vulnerability is fixed in 0.9.6. 2026-06-23 7.6 CVE-2= 026-54013 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54013 ] open-webui-= -open-webui Open WebUI is a self-hosted artificial intelligence platform de= signed to operate entirely offline. Prior to 0.9.6, the SafePlaywrightURLLo= ader implements a validate_url function to prevent SSRF attacks by checking=
    the IP address of the user-provided URL. However, this validation is perfo= rmed only on the initial URL. Since Playwright automatically follows HTTP r= edirects (301/302) by default, an attacker can bypass the validation by pro= viding a safe URL that redirects to a restricted internal network address (= e.g., localhost, Docker container network, or Cloud Metadata). This allows = the application to access internal services despite ENABLE_RAG_LOCAL_WEB_FE= TCH being set to False This vulnerability is fixed in 0.9.6. 2026-06-23 7.7=
    CVE-2026-54018 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54018 ] OpenB= SD--OpenBSD sys/kern/sysv_sem.c in OpenBSD through 7.9 has a use-after-free=
    allowing local privilege escalation to root. This is a context switch use-= after-free after tsleep in sys_semget(). 2026-06-25 7.4 CVE-2026-57589 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-57589 ] openremote--openremote Op= enRemote before 1.25.0 contains an insecure direct object reference (IDOR) = vulnerability in the bulk alarm deletion endpoint that allows authenticated=
    users to permanently delete alarms belonging to other tenants by supplying=
    arbitrary alarm IDs. The removeAlarms() method in AlarmResourceImpl.java o= mits realm-scoping validation in its JPA query, enabling any user with alar= m-write permissions to enumerate sequential auto-increment alarm IDs and de= lete cross-tenant alarm records without authorization. 2026-06-23 8.1 CVE-2= 026-56784 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56784 ] opf--openpr= oject OpenProject is open-source, web-based project management software. Pr= ior to , the official openproject/openproject Docker image ships ENV SECRET= _KEY_BASE=3DOVERWRITE_ME as the default Rails master key. Combined with coo= kies_serializer =3D :marshal, this gives any logged-in user a deterministic=
    Marshal-deserialization path reachable via the /my/two_factor_devices cook=
    ie reader This vulnerability is fixed in . 2026-06-26 9.9 CVE-2026-46386 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-46386 ] opf--openproject OpenPr= oject is open-source, web-based project management software. Prior to 17.3.=
    3 and 17.4.1, cache store poisoning leads to Remote Code Execution (RCE). T= his vulnerability is fixed in 17.3.3 and 17.4.1. 2026-06-26 9.6 CVE-2026-52= 780 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52780 ] opf--openproject = OpenProject is open-source, web-based project management software. Prior to=
    17.3.3 and 17.4.1, there is an IDOR through /projects/<A>/settings/project= _storages/<A_ps_id> via PATCH parameter "storages_project_storage[project_f= older_id]" leads to Access to Unauthorized Resources. A project-admin in on=
    e project can hijack the managed Nextcloud or OneDrive folder of another pr= oject on the same storage by writing the victim project's project_folder_id=
    into the attacker's Storages::ProjectStorage row. The next managed-folder = sync overwrites the ACL on the referenced folder with the attacker project'=
    s user list. This vulnerability is fixed in 17.3.3 and 17.4.1. 2026-06-26 9=
    .9 CVE-2026-52782 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52782 ] opf= --openproject OpenProject is open-source, web-based project management soft= ware. Prior to 17.3.3 and 17.4.1, there is a SQL injection in timestamps fu= nctionality. OpenProject baseline comparison allows callers to request hist= oric work-package attributes using the timestamps parameter. This vulnerabi= lity is fixed in 17.3.3 and 17.4.1. 2026-06-26 9.9 CVE-2026-52785 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-52785 ] opf--openproject OpenProject i=
    s open-source, web-based project management software. Prior to 17.3.3 and 1= 7.4.1, OpenProject's Storages module writes the OneDrive/SharePoint userles=
    s OAuth access_token plaintext to Rails.cache under the deterministic key s= torage.<id>.httpx_access_token, repopulated continuously by an hourly cron = and every userless-OAuth call site (see Write cadence). None of the three a= llowed cache backends (file_store, memcache, redis) encrypts at rest. An at= tacker with read access to the cache backend recovers the Azure-AD applicat= ion-tier bearer with an anonymous get over the memcached binary protocol (o=
    r the equivalent against Redis). This vulnerability is fixed in 17.3.3 and = 17.4.1. 2026-06-26 8.2 CVE-2026-52783 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-52783 ] opf--openproject OpenProject is open-source, web-based pro= ject management software. Prior to 17.3.3 and 17.4.1, there is a CSRF on TA= RGET through /users/:id via POST parameter "user[admin]". This vulnerabilit=
    y is fixed in 17.3.3 and 17.4.1. 2026-06-26 8.8 CVE-2026-52784 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-52784 ] opf--openproject OpenProject is o= pen-source, web-based project management software. Prior to 17.3.3 and 17.4= .1, the journal diff endpoint discloses hidden historical field values with= out enforcing object and field visibility. This vulnerability is fixed in 1= 7.3.3 and 17.4.1. 2026-06-26 7.5 CVE-2026-47193 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-47193 ] pagekit--pagekit Pagekit CMS 1.0.18 contains a p= rivilege escalation vulnerability that allows authenticated users with the = 'user: manage users' permission to escalate privileges by assigning arbitra=
    ry custom roles to themselves due to missing authorization checks in UserAp= iController::saveAction(). Attackers can assign themselves a custom role wi=
    th the 'system: manage packages' permission and then upload and install a m= alicious PHP package through the admin package installer to achieve remote = code execution. 2026-06-26 8.8 CVE-2026-57518 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-57518 ] Paolo--GeoDirectory Unauthenticated SQL Injection =
    in GeoDirectory <=3D 2.8.162 versions. 2026-06-26 9.3 CVE-2026-54831 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-54831 ] parse-community--parse-serv=
    er Parse Server before 4.10.0 contains a supply chain vulnerability where i= ncorrect version tags were pushed to the repository linking to unreviewed c= ode in a personal fork. Attackers could exploit this by specifying affected=
    version tags in dependency declarations to execute unreviewed and potentia= lly malicious code. 2026-06-25 7.5 CVE-2021-47986 [ https://www.cve.org/CVE= Record?id=3DCVE-2021-47986 ] parse-community--parse-server Parse Server bef= ore 4.10.0 was affected by a supply chain incident in which incorrect versi=
    on tags were pushed to the official repository pointing to an unreviewed pe= rsonal fork of a contributor with write access. No releases were published = with these tags; a project was exposed only if it defined a git-based depen= dency referencing one of the affected tags (for example, parse-server#4.9.3=
    ). The code behind the tags was not reviewed or approved, and although no m= alicious code was identified, the introduction of security vulnerabilities = could not be ruled out. 2026-06-25 7.5 CVE-2021-47987 [ https://www.cve.org= /CVERecord?id=3DCVE-2021-47987 ] Paymob--Paymob for WooCommerce Unauthentic= ated Broken Access Control in Paymob for WooCommerce <=3D 4.1.2 versions. 2= 026-06-26 7.5 CVE-2026-56025 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 56025 ] paytiumsupport--Paytium Unauthenticated Privilege Escalation in Pay= tium <=3D 5.0.2 versions. 2026-06-26 9.8 CVE-2026-56030 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-56030 ] Peplink--InControl Peplink InControl 2 t= hrough 2.14.2 before 2026-06-03 allows use of a semicolon to bypass access-= control rules for certain /rest/o/{orgId} endpoints. 2026-06-26 7.7 CVE-202= 6-57920 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57920 ] Perfmatters, = Powered Kinsta + GeneratePress Docs Changelog Feature requests Legal Affili= ate Contact--perfmatters Unauthenticated Cross Site Scripting (XSS) in perf= matters <=3D 2.6.3 versions. 2026-06-26 7.1 CVE-2026-56047 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-56047 ] PhysCode--Travel Booking Subscriber A= rbitrary File Upload in Travel Booking <=3D 2.2.5 versions. 2026-06-26 9.9 = CVE-2026-56059 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56059 ] Pickle= scan--Picklescan Picklescan before 0.0.33 fails to detect the numpy.f2py.cr= ackfortran._eval_length gadget in pickle __reduce__ methods, allowing arbit= rary code execution. Attackers can craft malicious pickle files that execut=
    e arbitrary Python code when loaded by victims who trust Picklescan's safet=
    y validation. 2026-06-22 8.1 CVE-2025-71339 [ https://www.cve.org/CVERecord= ?id=3DCVE-2025-71339 ] picklescan--picklescan picklescan before 1.0.4 fails=
    to block at least seven Python standard library modules (including uuid, _= osx_support, _aix_support, _pyrepl.pager, and imaplib) exposing eight funct= ions that provide direct arbitrary command execution. Attackers can craft m= alicious pickle files importing these unblocked modules to achieve remote c= ode execution while bypassing picklescan's safety validation entirely. 2026= -06-23 9.8 CVE-2026-56315 [ https://www.cve.org/CVERecord?id=3DCVE-2026-563=
    15 ] picklescan--picklescan picklescan through 0.0.26 fails to detect malic= ious pickle files that invoke idlelib.pyshell.ModifiedInterpreter.runcode i=
    n __reduce__ methods. Attackers can embed undetected code in pickle files t= hat executes arbitrary commands when the file is loaded via pickle.load(), = enabling supply chain attacks on PyTorch models and saved Python objects. T= his is fixed in version 0.0.30. 2026-06-25 8.1 CVE-2025-71340 [ https://www= .cve.org/CVERecord?id=3DCVE-2025-71340 ] picklescan--picklescan picklescan = before 0.0.29 fails to detect the profile.Profile.runctx function when anal= yzing pickle files, allowing attackers to embed undetected malicious code. = Remote attackers can craft malicious pickle files using profile.Profile.run= ctx in the reduce method to achieve remote code execution when the pickle f= ile is loaded. 2026-06-23 8.1 CVE-2025-71341 [ https://www.cve.org/CVERecor= d?id=3DCVE-2025-71341 ] picklescan--picklescan picklescan before 0.0.30 (af= fected versions 0.0.26 and earlier) fails to detect the ensurepip._run_pip = built-in function when scanning pickle files, allowing attackers to execute=
    arbitrary code. Malicious pickle files embedding ensurepip._run_pip calls =
    in __reduce__ methods bypass picklescan detection and achieve remote code e= xecution upon pickle.load() invocation. 2026-06-22 8.1 CVE-2025-71344 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2025-71344 ] picklescan--picklescan pic= klescan before 0.0.29 fails to detect malicious pickle files that exploit i= dlelib.debugobj.ObjectTreeItem.SetText function in reduce methods. Attacker=
    s can craft pickle files with embedded code that bypasses picklescan detect= ion and executes arbitrary commands when pickle.load() is called. 2026-06-2=
    4 8.1 CVE-2025-71354 [ https://www.cve.org/CVERecord?id=3DCVE-2025-71354 ] = picklescan--picklescan picklescan before 0.0.29 fails to detect malicious p= ickle files that exploit idlelib.autocomplete.AutoComplete.get_entity funct= ion in reduce methods. Attackers can embed undetected code in pickle files = that executes arbitrary commands when loaded by victims using pickle.load()=
    . 2026-06-22 8.1 CVE-2025-71358 [ https://www.cve.org/CVERecord?id=3DCVE-20= 25-71358 ] picklescan--picklescan picklescan before 0.0.29 fails to detect = malicious idlelib.calltip.Calltip.fetch_tip calls in pickle files, allowing=
    remote code execution. Attackers can embed undetected payloads in pickle f= iles that execute arbitrary code when loaded via pickle.load(). 2026-06-24 = 8.1 CVE-2025-71361 [ https://www.cve.org/CVERecord?id=3DCVE-2025-71361 ] pi= cklescan--picklescan picklescan before 0.0.33 fails to detect malicious pic= kle files that invoke numpy.f2py.crackfortran.myeval function through the r= educe method. Attackers can craft malicious pickle files embedding arbitrar=
    y code that evades picklescan detection and executes remote code when loade=
    d. 2026-06-23 8.1 CVE-2025-71365 [ https://www.cve.org/CVERecord?id=3DCVE-2= 025-71365 ] picklescan--picklescan picklescan before 0.0.28 fails to detect=
    malicious torch.jit.unsupported_tensor_ops.execWrapper function calls embe= dded in pickle files. Attackers can craft malicious pickle files that bypas=
    s picklescan detection and execute arbitrary code when loaded via pickle.lo= ad(). 2026-06-23 8.1 CVE-2025-71370 [ https://www.cve.org/CVERecord?id=3DCV= E-2025-71370 ] picklescan--picklescan picklescan before 0.0.29 fails to det= ect malicious pickle files using idlelib.autocomplete.AutoComplete.fetch_co= mpletions in reduce methods. Attackers can embed undetected code in pickle = files that executes arbitrary commands when loaded by victims. 2026-06-23 8=
    .1 CVE-2025-71376 [ https://www.cve.org/CVERecord?id=3DCVE-2025-71376 ] Pil= z--PMI v8xx A stored cross-site scripting vulnerability in the Runtime comp= onent of Pilz PASvisu before 1.14.1 and PMI v8xx up to and including 2.0.33= 992 allows a low-privileged remote unauthenticated attacker to manipulate p= rocess data with potential impact on integrity and/or availability. 2026-06= -22 8.1 CVE-2023-45796 [ https://www.cve.org/CVERecord?id=3DCVE-2023-45796 =
    ] Pilz--PMI v8xx A cross-site scripting vulnerability in the Builder Compon= ent of Pilz PASvisu before 1.14.1 allows a local unauthenticated attacker t=
    o inject malicious javascript and gain full control over the device. 2026-0= 6-22 7.8 CVE-2023-45795 [ https://www.cve.org/CVERecord?id=3DCVE-2023-45795=
    ] piscinajs--piscina piscina is a node.js worker pool implementation. Prio=
    r to 6.0.0-rc.2, 5.2.0, and 4.9.3, piscina's constructor and run() paths re=
    ad the filename option via plain member access. Both reads fall through the=
    prototype chain when the caller's options object doesn't have filename as =
    an own property. When Object.prototype.filename is polluted upstream the in= herited value flows to worker_threads.Worker import and the attacker's .mjs=
    runs in the worker. This vulnerability is fixed in 6.0.0-rc.2, 5.2.0, and = 4.9.3. 2026-06-22 8.1 CVE-2026-55388 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-55388 ] Pluggabl--Booster for WooCommerce Customer Arbitrary File U= pload in Booster for WooCommerce <=3D 8.0.1 versions. 2026-06-26 9.9 CVE-20= 26-56027 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56027 ] PluginUs.Net= --MDTF Unauthenticated SQL Injection in MDTF <=3D 1.3.7 versions. 2026-06-2=
    5 9.3 CVE-2026-54843 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54843 ] = PluginUs.Net--MDTF Unauthenticated Local File Inclusion in MDTF <=3D 1.3.8 = versions. 2026-06-25 8.1 CVE-2026-54845 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54845 ] pnpm--pnpm pnpm is a package manager. Prior to 10.34.0 = and 11.4.0, pnpm allows a transitive dependency alias from registry package=
    metadata to contain path traversal segments. During install, pnpm later us=
    es that alias as a filesystem path when linking dependency nodes. As a resu= lt, a registry package can cause `pnpm install --ignore-scripts` to replace=
    paths in the current project with symlinks to attacker-controlled dependen=
    cy package directories. This vulnerability is fixed in 10.34.0 and 11.4.0. = 2026-06-25 8.8 CVE-2026-50016 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -50016 ] pnpm--pnpm pnpm is a package manager. Prior to 10.34.2 and 11.5.3,=
    pnpm can persist package-manager bootstrap metadata in the first YAML docu= ment of pnpm-lock.yaml. Before the patch, direct pnpm execution trusted an = already resolved packageManagerDependencies entry when the committed env lo= ckfile contained matching pnpm and @pnpm/exe versions. A malicious reposito=
    ry could therefore commit package-manager lockfile package records and snap= shots that bypassed fresh package-manager resolution, then cause pnpm to in= stall and execute bytes selected by that committed lockfile state during au= tomatic version switching. This vulnerability is fixed in 10.34.2 and 11.5.=
    3. 2026-06-25 8.8 CVE-2026-55698 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-55698 ] pnpm--pnpm pnpm is a package manager. Prior to 10.34.0 and 11.4= .0, pnpm's patch application pipeline (@pnpm/patch-package) performs no pat=
    h validation on file paths extracted from .patch files. An attacker who con= tributes a malicious patch file via a pull request can write attacker-contr= olled content to or delete arbitrary files on the filesystem during pnpm in= stall, as the user running the install. The diff --git header paths contain= ing ../../ sequences traverse out of the package directory, and the travers=
    al is difficult to catch in code review because patch file diff headers are=
    opaque to most reviewers. This vulnerability is fixed in 10.34.0 and 11.4.=
    0. 2026-06-25 7.3 CVE-2026-50015 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-50015 ] pnpm--pnpm pnpm is a package manager. Prior to 10.34.2 and 11.5= .3, the generic peer-suffix normalizer also stripped parenthesized text fro=
    m git, URL, tarball, file, and other opaque locators. Approval for one sour=
    ce string could therefore authorize a different attacker-controlled source = whose locator normalized to the same value. This vulnerability is fixed in = 10.34.2 and 11.5.3. 2026-06-25 7.5 CVE-2026-55487 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-55487 ] pnpm--pnpm pnpm is a package manager. Prior to=
    10.34.2 and 11.5.3, pnpm can install configDependencies declared in pnpm-w= orkspace.yaml before command dispatch. Before the patch, a repository could=
    declare pacquet or @pnpm/pacquet as a config dependency and pnpm treated t= hat repository-controlled dependency as an install-engine opt-in. During in= stall, pnpm resolved a platform-specific @pacquet/<platform>-<arch>/pacquet=
    binary from node_modules/.pnpm-config/<packageName> and spawned it as the = developer or CI user. This vulnerability is fixed in 10.34.2 and 11.5.3. 20= 26-06-25 7.5 CVE-2026-55697 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 5697 ] pnpm--pnpm pnpm is a package manager. From 11.3.0 until 11.5.3, `pnp=
    m stage download` derived a local filename from registry-controlled package=
    name and version fields. A crafted manifest could escape the selected down= load directory and overwrite another reachable file. The merged fix validat=
    es both fields, derives one safe filename, and verifies the final destinati=
    on before writing. This vulnerability is fixed in 11.5.3. 2026-06-25 7.1 CV= E-2026-55700 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55700 ] podman-c= ontainer-tools--podman Podman is a tool for managing OCI containers and pod=
    s. From 1.8.1 until 5.8.4, a container image that contains a environment va= riable with just a key and no value can trick podman into passing that vari= able from the host into the container. This is made worse by the fact that = using an asterisk (*) will cause podman to pass all host variables into the=
    container. So essentially a malicious image can exfiltrate all podman envi= ronment variables that are set in the session from where the container is l= aunched. This vulnerability is fixed in 5.8.4 and 6.0.0. 2026-06-26 7.5 CVE= -2026-57231 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57231 ] Post Snip= pets--Post Snippets Contributor Remote Code Execution (RCE) in Post Snippet=
    s <=3D 4.0.19 versions. 2026-06-25 8.5 CVE-2026-56049 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-56049 ] poweradmin--poweradmin Poweradmin is a web= -based DNS administration tool for PowerDNS server. Versions prior to 4.2.4=
    and 4.3.3 use the attacker-controlled `HTTP_HOST` request header as the au= thoritative source for building callback URLs in its OIDC, SAML, and logout=
    authentication flows without any validation. An unauthenticated attacker c=
    an poison the `redirect_uri` sent to the Identity Provider, causing the IdP=
    to redirect the victim's authorization code to an attacker-controlled serv=
    er - resulting in full account takeover with no credentials required. Versi= ons 4.2.4 and 4.3.3 patch the issue. 2026-06-23 9.6 CVE-2026-54588 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-54588 ] PowerDNS--Recursor A maliciou=
    s authoritative server can send a crafted zone via the ZoneToCache function=
    that leads to cache poisoning. 2026-06-25 7.5 CVE-2026-33612 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-33612 ] pravel--Invoice Generator The Invo= ice Generator plugin for WordPress is vulnerable to privilege escalation du=
    e to a missing capability check on the pravel_invoice_edit_account() AJAX a= ction in versions up to, and including, 1.0.0. The handler is exposed via w= p_ajax_nopriv_pravel_invoice_edit_account, accepts an attacker-controlled u= ser_id and user_email from POST data, and calls wp_update_user() without ve= rifying authentication, ownership, or a nonce. This makes it possible for u= nauthenticated attackers to change the email address of any user, including=
    administrators, and then trigger WordPress's password reset flow to gain a= ccess to the targeted account. 2026-06-27 9.8 CVE-2026-12415 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-12415 ] pravel--Invoice Generator The Invoi=
    ce Generator plugin for WordPress is vulnerable to Account Takeover via Pas= sword Reset in all versions up to, and including, 1.0.0. This is due to the=
    `pravel_invoice_change_password()` function being registered as a nopriv A= JAX handler with no nonce verification and no authorization check, and perf= orming a loose equality comparison between the supplied `reset_activation_c= ode` POST parameter and the target user's stored `forgot_email` user meta -=
    a check that trivially evaluates to true (`'' =3D=3D ''`) for any user who=
    has never initiated a forgot-password request, which applies to administra= tors under normal conditions. This makes it possible for unauthenticated at= tackers to supply an arbitrary user ID via the `reset_user_id` POST paramet= er, bypass the activation code check entirely by omitting `reset_activation= _code`, and set the target account's password to an attacker-chosen value, = enabling full takeover of any account on the site, including administrator = accounts. 2026-06-24 9.8 CVE-2026-12416 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-12416 ] pravel--SignUp & SignIn The SignUp & SignIn plugin for = WordPress is vulnerable to Authentication Bypass via Weak Password Reset Va= lidation leading to Account Takeover in versions up to, and including, 1.0.=
    0. This is due to the `pravel_change_password()` AJAX handler - registered = via `wp_ajax_nopriv_pravel_change_password` and therefore accessible to una= uthenticated users - performing no nonce verification, no capability check,=
    and only a loose equality check between an attacker-supplied `reset_activa= tion_code` POST parameter and the target user's `forgot_email` user meta va= lue; when a user has never initiated a password reset, `get_user_meta()` re= turns an empty string that trivially satisfies this check against an omitte=
    d or empty attacker-supplied code. This makes it possible for unauthenticat=
    ed attackers to change the password of any WordPress user, including admini= strators, by sending a crafted POST request to `admin-ajax.php` with `actio= n=3Dpravel_change_password`, `reset_user_id` set to the target account's us=
    er ID, and `new_password_custom` set to an attacker-chosen password. Succes= sful exploitation allows the attacker to authenticate with the newly set pa= ssword and fully take over the targeted account, achieving administrator-le= vel privilege escalation on the affected site. 2026-06-24 9.8 CVE-2026-1241=
    7 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12417 ] Premmerce--Premmerc=
    e Wishlist for WooCommerce Unauthenticated SQL Injection in Premmerce Wishl= ist for WooCommerce <=3D 1.1.11 versions. 2026-06-25 9.3 CVE-2026-54849 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-54849 ] presire--qSnapper A time= -to-check-time-of-use in polkit authentication of qSnapper before version 1= .3.3 allowed a local attacker to bypass qSnappers authentication mechanism = and operate e.g. as root user. 2026-06-22 8.1 CVE-2026-41045 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-41045 ] presire--qSnapper A path traversal = attack when using a "configName" parameter in qSnapper before version 1.3.3=
    allowed a local attacker to use malicious config files for snapper and so = cause a denial of service or potentially escalate privileges to root. 2026-= 06-22 7.3 CVE-2026-41046 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4104=
    6 ] ProFTPD Project--ProFTPD ProFTPD through 1.3.9b and 1.3.10rc2 contains =
    an access control bypass vulnerability that allows authenticated FTP users =
    to circumvent Directory ACL restrictions by prefixing paths with /proc/self= /root in the RNFR command handler. Attackers can exploit the unresolved sym= link components in dir_canonical_path() to cause dir_check() to perform lex= ical path comparisons that match no configured Directory block, enabling re= name operations on files in DenyAll-protected directories and subsequent re= trieval of those files. Mitigation: Sessions configured with DefaultRoot (c= hroot) are not affected, as chroot changes the directory to which /proc/sel= f/root resolves. 2026-06-24 8.1 CVE-2026-35025 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-35025 ] protobufjs--protobuf.js protobufjs compiles proto= buf definitions into JavaScript (JS) functions. Prior to 7.6.1 and 8.4.1, p= rotobufjs could recurse without a depth limit while converting decoded mess= ages to plain objects or JSON. This affected generated toObject() conversio=
    n and the custom google.protobuf.Any JSON conversion path. A crafted protob=
    uf binary payload containing deeply nested Any values could cause the JavaS= cript call stack to be exhausted during conversion to JSON. This vulnerabil= ity is fixed in 7.6.1 and 8.4.1. 2026-06-22 7.5 CVE-2026-48712 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-48712 ] protobufjs--protobufjs-cli protob= ufjs-cli is the command line add-on for protobuf.js. Prior to 1.3.2 and 2.5= .0, a previous fix for unsafe name handling in pbjs static / static-module = code generation was incomplete. Affected versions of protobufjs-cli could s= till emit unsafe JavaScript references when generating static output from c= rafted JSON descriptor input. The common case of parsing schemas from .prot=
    o files is not affected. This is a bypass of CVE-2026-44295. An attacker wh=
    o can provide or influence pre-parsed JSON descriptors passed to pbjs stati=
    c code generation may be able to cause generated JavaScript output to conta=
    in attacker-controlled code. The injected code may execute if the generated=
    file is later executed or imported and an affected generated API path is i= nvoked. This vulnerability is fixed in 1.3.2 and 2.5.0. 2026-06-22 8.2 CVE-= 2026-54271 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54271 ] PSM Plugin= s--SupportCandy Subscriber Insecure Direct Object References (IDOR) in Supp= ortCandy <=3D 3.4.6 versions. 2026-06-26 7.6 CVE-2026-54826 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-54826 ] pydicom--pynetdicom Library The qrsc=
    p application's C-STORE handler uses a specific instance from attacker-supp= lied DICOM datasets directly in os.path.join() without sanitization, allowi=
    ng file writes to arbitrary paths. 2026-06-25 9.1 CVE-2026-56445 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-56445 ] Rapid7--InsightConnect AWK Plug=
    in OS Command Injection vulnerability in the process_string action of Rapid=
    7 InsightConnect AWK Plugin on Linux allows remote attackers to execute arb= itrary OS commands via the text or expression parameters due to unsafe shel=
    l command construction in the processing pipeline. 2026-06-25 7.7 CVE-2026-= 8592 [ https://www.cve.org/CVERecord?id=3DCVE-2026-8592 ] Rapid7--InsightCo= nnect Ping Plugin OS Command Injection vulnerability in the ping action of = Rapid7 InsightConnect Ping Plugin on Linux allows remote attackers to execu=
    te arbitrary OS commands via the host parameter due to insufficient input v= alidation when constructing shell commands. 2026-06-25 7.7 CVE-2026-8660 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-8660 ] Rapid7--InsightConnect S=
    ed Plugin OS Command Injection vulnerability in Rapid7 InsightConnect Sed P= lugin on Linux allows authenticated attackers to execute arbitrary OS comma= nds via the expression parameter due to insufficient input validation. 2026= -06-25 8.8 CVE-2026-9155 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9155=
    ] Rapid7--InsightConnect Sed Plugin Arbitrary File Write vulnerability in = Rapid7 InsightConnect Sed Plugin on Linux allows authenticated attackers to=
    write attacker-controlled content to arbitrary file paths via the expressi=
    on parameter. 2026-06-25 7.1 CVE-2026-9154 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-9154 ] Rapid7--InsightConnect TR Plugin OS Command Injection = vulnerability in the TR action of Rapid7 InsightConnect Translate=C2=A0Plug=
    in on Linux allows remote attackers to execute arbitrary OS commands via th=
    e text or expression parameters due to insufficient input sanitization in s= hell command construction. 2026-06-25 7.7 CVE-2026-8665 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-8665 ] Rapid7--InsightConnect Traceroute Plugin =
    OS Command Injection vulnerability in the traceroute action of Rapid7 Insig= htConnect Traceroute Plugin on Linux allows remote attackers to execute arb= itrary OS commands via the host, port, max_ttl, count, or time_out request = parameters due to insufficient input validation when constructing shell com= mands. 2026-06-25 7.7 CVE-2026-8666 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-8666 ] rasta-mouse--pwnlift pwnlift before d7a9544, in a privileged = deployment, contains a symlink following vulnerability in the upload handle=
    r in Components/Pages/Home.razor. 2026-06-23 7.4 CVE-2026-56815 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-56815 ] rclone--rclone Rclone is a comma= nd-line program to sync files and directories to and from different cloud s= torage providers. From 1.46.0 until 1.74.3, rclone rcd --rc-serve accepts u= nauthenticated GET and HEAD requests to paths of the form: /[remote:path]/o= bject. The remote value is parsed from the URL and passed to normal backend=
    initialization. Inline remote configuration can set backend options that e= xecute local commands during initialization. As a result, a single unauthen= ticated GET or HEAD request can execute a command as the rclone process use=
    r. This vulnerability is fixed in 1.74.3. 2026-06-24 9.8 CVE-2026-49980 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-49980 ] RealMag777--FOX Unauthen= ticated Cross Site Scripting (XSS) in FOX <=3D 1.4.8 versions. 2026-06-26 7=
    .1 CVE-2026-57319 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57319 ] Red=
    Hat--Red Hat Ansible Automation Platform 2.5 for RHEL 8 A missing authoriz= ation vulnerability was found in the Event-Driven Ansible (EDA) websocket A= PI. The /api/eda/ws/ansible-rulebook endpoint does not verify user permissi= ons when processing Worker messages. Any authenticated user can send a forg=
    ed message with an arbitrary activation_id to receive plaintext credentials=
    associated with that activation, including OAuth tokens, vault passwords, = and SSH keys. 2026-06-23 9.6 CVE-2026-11807 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-11807 ] Red Hat--Red Hat build of Apicurio Registry 3 A flaw=
    was found in Apicurio Registry. The ContentTypeUtil.isParsableXml() method=
    creates a SAXParserFactory without enabling secure processing features or = disabling external entity resolution. An attacker with artifact-write permi= ssion (or unauthenticated when the registry runs with default configuration=
    ) can upload a crafted XML document to trigger blind server-side request fo= rgery (SSRF) via external DTD/entity fetch, or cause denial of service via = entity expansion. 2026-06-25 8.5 CVE-2026-12975 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-12975 ] Red Hat--Red Hat build of Apicurio Registry 3 A = flaw was found in Apicurio Registry. The WSDLReaderAccessor creates a wsdl4=
    j WSDLReader without disabling the javax.wsdl.importDocuments feature. When=
    the VALIDITY rule is set to FULL, an attacker with Developer-role access c=
    an upload a WSDL document containing attacker-controlled import locations, = causing the registry to issue HTTP requests to arbitrary internal URLs (ser= ver-side request forgery). 2026-06-25 7.4 CVE-2026-12992 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-12992 ] Red Hat--Red Hat build of Keycloak 26.4=
    A flaw was found in Keycloak Policy Enforcer. This vulnerability allows an=
    y authenticated user to bypass all authorization policies, including role, = scope, and User-Managed Access (UMA) permission checks. By including the co= nfigured access-denied page path within a request URL, either as a path seg= ment or a query parameter, an attacker can gain unauthorized access to prot= ected resources. 2026-06-25 8.1 CVE-2026-9800 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-9800 ] Red Hat--Red Hat build of Keycloak 26.4 A flaw was = found in Keycloak. A remote attacker with administrative privileges, specif= ically those with `manage-client` permission or access to client registrati=
    on endpoints, could bypass client Uniform Resource Identifier (URI) validat= ion. This is achieved by registering a malicious client with a specially cr= afted redirect URI using a case-insensitive `javascript:` or `data:` scheme=
    . This Cross-Site Scripting (XSS) vulnerability allows for arbitrary code e= xecution in the Keycloak origin when a victim clicks the crafted link, such=
    as in the logout flow or the Admin Console. 2026-06-25 7.3 CVE-2026-9086 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-9086 ] Red Hat--Red Hat build =
    of Keycloak 26.4 A flaw was found in Keycloak. A missing authorization chec=
    k in the GroupResource.addChild() endpoint within the Admin REST API allows=
    an authenticated user with limited administrative privileges to reparent a=
    ny existing group. When Fine-Grained Admin Permissions v2 (FGAPv2) is enabl= ed, an attacker with management rights over a single low-privilege group ca=
    n reparent a highly privileged group (such as one possessing the realm-admi=
    n role) under their managed group. Because group permissions follow a hiera= rchical structure, this action unauthorizedly grants the attacker managemen=
    t and password-reset capabilities over the members of the targeted privileg=
    ed group. An attacker can exploit this to reset an administrator's password=
    , compromise the account, and achieve a full realm takeover, leading to a c= omplete compromise of confidentiality, integrity, and availability. 2026-06= -25 7.7 CVE-2026-9099 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9099 ] = Red Hat--Red Hat build of Keycloak 26.6 A flaw was found in Keycloak. This = JWT algorithm confusion vulnerability in the JWT Authorization Grant flow a= llows an attacker with valid client credentials to bypass signature verific= ation. By forging an assertion, the attacker can create unauthorized access=
    tokens. This enables the attacker to impersonate any federated user linked=
    to the affected Identity Provider, leading to unauthorized access and pote= ntial privilege escalation. 2026-06-25 8.1 CVE-2026-11800 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-11800 ] Red Hat--Red Hat OpenShift Container P= latform 4 A flaw was found in the Windows Machine Config Operator (WMCO) fo=
    r Red Hat OpenShift Container Platform. The WICD CSR auto-approver validate=
    s that a Certificate Signing Request contains the organization system:wicd-= nodes but does not reject additional organization values such as system:mas= ters. A compromised Windows worker node that holds WICD credentials can sub= mit a CSR that is auto-approved and signed by the cluster, yielding a clien=
    t certificate that grants cluster-administrator privileges and enabling ful=
    l cluster takeover. 2026-06-22 8.8 CVE-2026-54099 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-54099 ] Red Hat--Red Hat OpenShift Container Platform =
    4 A flaw was found in the Windows Machine Config Operator (WMCO) for Red Ha=
    t OpenShift Container Platform. WMCO establishes SSH connections to Windows=
    worker nodes without verifying the remote server host key. An adjacent-net= work attacker who can intercept or redirect WMCO's SSH session can capture = WICD and kubelet bootstrap credentials transferred during node configuratio=
    n, enabling compromise of Windows node identities in the cluster. 2026-06-2=
    2 8.3 CVE-2026-54100 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54100 ] = Red Hat--Red Hat OpenShift Virtualization 4 A flaw was found in KubeVirt's = migration proxy. When spec.configuration.migrations.disableTLS is set to tr=
    ue on the KubeVirt custom resource, the target virt-handler binds a plain T=
    CP listener on all interfaces (0.0.0.0/::) on a random port with no authent= ication, peer allow-list, or handshake token. This listener proxies directl=
    y into the target virt-launcher's virtqemud control socket. An attacker wit=
    h a running pod on the cluster network can connect to this listener and iss=
    ue unfiltered libvirt RPC commands against another tenant's virtual machine=
    , including reading VM memory and configuration, modifying VM state via QMP=
    , or destroying the VM. The bind address is unconditionally 0.0.0.0 - confi= guring a dedicated migration network via migrations.network only changes th=
    e advertised migration IP, not the listener bind address, so the port remai=
    ns reachable on the pod network even when a dedicated migration network is = configured. The API documentation describes disableTLS as removing "the add= itional layer of live migration encryption" without disclosing that it also=
    removes all mutual authentication. 2026-06-26 8.5 CVE-2026-13325 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-13325 ] Red Hat--Red Hat OpenShift Vir= tualization 4 A flaw was found in KubeVirt's safepath package used by virt-= handler. The OpenAtNoFollow function uses O_PATH|O_NOFOLLOW to obtain a fil=
    e descriptor to a path leaf, but downstream operations resolve the path via=
    /proc/self/fd/N using link-following syscalls. When the leaf is a symlink,=
    the kernel dereferences it, defeating the intended no-follow protection. A=
    n attacker with access to a virt-launcher pod can exploit this to redirect = virt-handler's IPC socket connections, including the notify socket used for=
    VM domain lifecycle events. By hijacking this socket, the attacker can inj= ect arbitrary domain events into virt-handler, causing it to take incorrect=
    lifecycle actions, corrupt VM state in the Kubernetes API, or crash - resu= lting in sustained denial of VM management services for all virtual machine=
    s on the affected node. Additionally, the same symlink following flaw allow=
    s virt-handler to apply file ownership or permission changes to unintended = host paths. 2026-06-24 7.3 CVE-2026-13201 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-13201 ] Red Hat--Red Hat Satellite 6.19 A flaw was found in th=
    e foreman-mcp-server. A session management vulnerability in the MCP Server = allows unauthenticated attackers to hijack active administrative sessions d=
    ue to an improper cache of authenticated client connections, by trusting a = non-secret session ID without re-validating authentication tokens and by lo= gging all newly created session IDs to standard logs. This issue can result=
    in privilege escalation and infrastructure-wide code execution. 2026-06-23=
    7.8 CVE-2026-12112 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12112 ] r= ickknowles--Winstone Servlet Container Winstone Servlet Engine through 0.9.=
    10 contains a path traversal vulnerability that allows unauthenticated atta= ckers to read arbitrary files by sending HTTP GET requests with dot-dot-sla=
    sh sequences that are not sanitized when serving static files from the conf= igured webroot. Attackers can traverse outside the webroot directory using = traversal-prefixed paths in a single HTTP request to read any file accessib=
    le to the servlet engine process, including sensitive system files when the=
    service runs with elevated privileges. 2026-06-25 7.5 CVE-2026-56122 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-56122 ] RocketChat--Rocket.Chat Ro= cket.Chat is an open-source, secure, fully customizable communications plat= form. Prior to 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.1=
    1, Rocket.Chat's CAS login handler forwards the client-supplied options.cas= .credentialToken value straight into a MongoDB findOne({_id: ...}) query wi= thout any runtime type check. TypeScript's string parameter annotation is e= rased at runtime, so an unauthenticated attacker can substitute a MongoDB q= uery operator ({"$gt": ""}, {"$ne": null}, etc.) for what the server expect=
    s to be an opaque ticket string. The injected operator matches the first un= expired document in the credential_tokens collection, bypassing the CAS tic= ket check entirely. When any legitimate CAS or SAML SSO login is in flight,=
    the attacker's next DDP login call matches the same credential-token row v=
    ia the NoSQL operator and is issued a full Meteor auth token (userId + toke=
    n) bound to the victim. The token is immediately usable against the complet=
    e REST and DDP surface as that user. If the victim is an administrator, thi=
    s escalates to full instance compromise via Apps-Engine app install. This v= ulnerability is fixed in 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, = and 7.10.11. 2026-06-24 9.1 CVE-2026-45688 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-45688 ] RocketChat--Rocket.Chat Rocket.Chat is an open-source=
    , secure, fully customizable communications platform. Prior to 8.5.0, 8.4.1=
    , 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11, an unauthenticated netwo=
    rk attacker obtains a valid Rocket.Chat OAuth access token for an arbitrary=
    user by sending a single HTTP POST with MongoDB query operators to /oauth/= token. The Rocket.Chat OAuth2 server does not validate that grant parameter=
    s are strings before forwarding them to findOne({...}) against the oauth_ap=
    ps and oauth_access_tokens collections, so an attacker substitutes {"$ne": = null} for client_id, client_secret, and refresh_token and receives a freshl=
    y minted {access_token, refresh_token} pair bound to whichever user's refre=
    sh token Mongo returned first. The resulting access token is a first-class = bearer credential against the full /api/v1/* surface as that user. By itera= ting with $nin / $regex operators the attacker walks the entire oauth_acces= s_tokens collection, collecting one fresh access token per user per request=
    . If any matched token belongs to an admin, the stolen bearer gives full ad= min API access (including Apps-Engine app installation, i.e. server-side co=
    de execution). No account, credentials, userId, or prior interaction with t=
    he instance are required. This vulnerability is fixed in 8.5.0, 8.4.1, 8.3.=
    3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11. 2026-06-24 9.1 CVE-2026-45689 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-45689 ] RocketChat--Rocket.Ch=
    at Rocket.Chat is an open-source, secure, fully customizable communications=
    platform. Prior to 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7= .10.11, Rocket.Chat's sendFileMessage DDP method passes the entire attacker= -supplied file object into Uploads.updateFileComplete, which merges it dire= ctly into a MongoDB $set update via Object.assign. There is no allow-list o=
    f writable fields. An attacker can therefore rewrite any column on their ow=
    n upload record, notably store and the store-specific path fields. This vul= nerability is fixed in 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, an=
    d 7.10.11. 2026-06-24 8.5 CVE-2026-45687 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-45687 ] RocketChat--Rocket.Chat Rocket.Chat is an open-source, = secure, fully customizable communications platform. Prior to 8.5.1, 8.4.4, = 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13, the POST /api/v1/fingerprint REST = endpoint enforces authentication (authRequired: true) but performs no autho= rization check. Any authenticated user - including a standard user role acc= ount - can call this endpoint with {"setDeploymentAs": "new-workspace"} to = permanently deregister the workspace from Rocket.Chat Cloud. This wipes all=
    cloud credentials, removes the workspace license, breaks push notification=
    s for all users, and requires manual re-registration to recover. This vulne= rability is fixed in 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13.=
    2026-06-24 8.1 CVE-2026-55762 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-55762 ] RocketChat--Rocket.Chat Rocket.Chat is an open-source, secure, fu= lly customizable communications platform. Prior to 8.5.1, 8.4.4, 8.3.6, 8.2= .6, 8.1.6, 8.0.7, and 7.10.13, Rocket.Chat's Apple Sign-In handler verifies=
    JWT signatures but skips claims validation. Any Apple-signed JWT with a no= n-empty iss is accepted regardless of aud, exp, nbf, or nonce. An attacker = who obtains a target user's Apple identity token (from server logs, an inte= rcepted sign-in flow, or another application sharing the same Apple develop=
    er team) can replay it to authenticate as that user, with no expiration on = the replay window. This vulnerability is fixed in 8.5.1, 8.4.4, 8.3.6, 8.2.=
    6, 8.1.6, 8.0.7, and 7.10.13. 2026-06-24 7.4 CVE-2026-55759 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-55759 ] Royal Plugins--Royal MCP Missing Aut= horization vulnerability in Royal Plugins Royal MCP allows Exploiting Incor= rectly Configured Access Control Security Levels. This issue affects Royal = MCP: from n/a through 1.4.25. 2026-06-25 8.1 CVE-2026-54842 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-54842 ] rtk-ai--rtk rtk filters and compress=
    es command outputs before they reach your LLM context. Prior to 0.42.2, the=
    permission splitter did not conservatively split or reject several shell c= onstructs that Bash treats as command execution boundaries or nested execut= ion. As a result, a command beginning with an allowed prefix such as git co= uld hide a second command behind one of these constructs. rtk rewrite retur= ned exit code 0, causing the Claude hook to emit permissionDecision: "allow=
    ". The rewritten command still contained the hidden command, so it ran with= out the user confirmation or denial that the permission rules were intended=
    to enforce. This vulnerability is fixed in 0.42.2. 2026-06-23 7.8 CVE-2026= -54555 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54555 ] Rustaurius--Fi=
    ve Star Restaurant Menu Unauthenticated Broken Access Control in Five Star = Restaurant Menu <=3D 2.5.2 versions. 2026-06-26 7.5 CVE-2026-54835 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-54835 ] RustDesk--RustDesk RustDesk g= ates incoming control messages on per-capability flags rather than on the s= ession's authorized connection type, and a file-transfer session does not c= lear those flags. A peer holding only a valid FileTransfer authorization ca=
    n inject keyboard and mouse input and reach the unguarded screenshot and di= splay-capture handlers, acting outside its granted scope. 2026-06-28 7.6 CV= E-2026-58056 [ https://www.cve.org/CVERecord?id=3DCVE-2026-58056 ] rustfs--= rustfs RustFS is a distributed object storage system built in Rust. In 1.0.= 0-beta.4, authenticated users with only PutObject permission on their own b= ucket can exploit a path traversal vulnerability in the Snowball auto-extra=
    ct feature to write arbitrary objects into other users' buckets, completely=
    breaking multi-tenant isolation. The vulnerability chains three flaws: No = ../ sanitization in tar entry key normalization; IAM wildcard matching uses=
    raw (uncleaned) paths; and Filesystem path cleaning resolves ../ across bu= cket boundaries. 2026-06-26 8.6 CVE-2026-49991 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-49991 ] rustfs--rustfs RustFS is a distributed object sto= rage system built in Rust. From 1.0.0-alpha.1 until 1.0.0-beta.9, RustFS co= ntains an authorization bypass in the bucket replication admin API. The Lis= tRemoteTargetHandler handler for listing remote replication targets only ch= ecks whether request credentials exist, but does not verify that the caller=
    has replication or administrator permissions. As a result, an authenticate=
    d user with no effective bucket or admin permissions can list remote replic= ation target configuration for a bucket. Because the returned BucketTarget = objects include remote target credentials, this can disclose replication ac= cess keys and secret keys. This vulnerability is fixed in 1.0.0-beta.9. 202= 6-06-26 8.2 CVE-2026-55188 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55= 188 ] rustfs--rustfs RustFS is a distributed object storage system built in=
    Rust. From 1.0.0-alpha.1 until 1.0.0-beta.9, when the FTP frontend is enab= led, the FTP read and probe handlers dispatch directly to the storage backe=
    nd without ever calling the IAM authorization function that the FTP write/l= ist handlers (and the entire HTTP S3 path) use. As a result, any user who c=
    an authenticate to the FTP listener - including a user whose IAM policy con= tains an explicit Deny on s3:GetObject - can read (RETR) and stat (SIZE/MDT=
    M) any object in any bucket, and probe any bucket (CWD), completely regardl= ess of their IAM policy. This vulnerability is fixed in 1.0.0-beta.9. 2026-= 06-26 7.7 CVE-2026-55189 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5518=
    9 ] Rymera Web Co--WC Vendors Marketplace Subscriber SQL Injection in WC Ve= ndors Marketplace <=3D 2.6.8 versions. 2026-06-25 8.5 CVE-2026-54838 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-54838 ] Saad Iqbal--APIExperts Squa=
    re for WooCommerce Insertion of Sensitive Information Into Sent Data vulner= ability in Saad Iqbal APIExperts Square for WooCommerce allows Retrieve Emb= edded Sensitive Data. This issue affects APIExperts Square for WooCommerce:=
    from n/a through 4.7.3. 2026-06-25 8.3 CVE-2026-54848 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-54848 ] sahlberg--libnfs libnfs through 6.0.2 bef= ore 935b8db has an xid integer underflow in READ_IOVEC in rpc_read_from_soc= ket in lib/socket.c during a connection to a crafted NFS server, when the e= xpected pdu size exceeds the absolute pdu size from the xid/record-marker. = 2026-06-26 7.1 CVE-2026-57918 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -57918 ] SALESmanago--SALESmanago & Leadoo Subscriber SQL Injection in SALE= Smanago & Leadoo <=3D 3.11.2 versions. 2026-06-25 8.5 CVE-2026-54822 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-54822 ] samuelclay--NewsBlur NewsBl=
    ur before version 14.5.0 contains a server-side request forgery vulnerabili=
    ty in the add_url endpoint that allows authenticated users to make arbitrar=
    y server requests to internal networks by failing to filter private IP addr= esses. Attackers can exploit this to access localhost services and cloud me= tadata endpoints, enabling internal network scanning and sensitive data exf= iltration. 2026-06-25 8.5 CVE-2026-56771 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-56771 ] schwehr--libais libais through 0.15 VdmStream::AddLine = uses an unchecked sentinel value as a vector index when processing AIS sent= ences with empty or out-of-range sequential message IDs. Remote attackers c=
    an crash services or vessel systems by sending crafted AIVDM sentences over=
    VHF marine radio or IP feeds, causing out-of-bounds memory access and pote= ntial corruption. 2026-06-25 7.5 CVE-2026-56770 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-56770 ] Shenzhen Cudy Technology Co., Ltd.--LT300 3.0 Cu=
    dy LT300 3.0 running firmware prior to version 2.5.12 contains an OS comman=
    d injection vulnerability that allows authenticated attackers to execute ar= bitrary commands by injecting shell metacharacters into the cbid.system.ntp= .current POST parameter in the system time configuration interface. Attacke=
    rs can submit malicious payloads through the NTP settings endpoint to achie=
    ve remote code execution on the underlying system. 2026-06-26 8.8 CVE-2026-= 32833 [ https://www.cve.org/CVERecord?id=3DCVE-2026-32833 ] Shenzhen i365-T= ech Co. Ltd.--Setracker2 Parental Control App (Android) package com.tgelec.= setracker Setracker2 Android Companion App com.tgelec.setracker versions 3.= 1.5 and prior only require the password hash when authenticating with backe=
    nd services from the client. This could allow an attacker, who knows the ha= sh, to authenticate and gain full access. 2026-06-25 8.1 CVE-2026-9222 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-9222 ] Shenzhen i365-Tech Co. Ltd= .--Setracker2 Parental Control App (Android) package com.tgelec.setracker S= etracker2 Android Companion App com.tgelec.setracker versions 3.1.5 and pri=
    or encrypts requests between the watch and its backend with static hardcode=
    d AES keys and initialization vectors. This allows an attacker to decrypt S= etracker2 watch traffic. 2026-06-25 7.5 CVE-2026-9220 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-9220 ] Shenzhen i365-Tech Co. Ltd.--Setracker2 Par= ental Control App (Android) package com.tgelec.setracker The Setracker2 And= roid Companion App (com.tgelec.setracker) versions 3.1.5 and earlier uses M=
    D5 to generate a request signature for authenticating communications betwee=
    n the mobile client and the backend REST API. Attackers could potentially r= everse the signature to recover the session ID. With the session ID exposed=
    , an attacker could impersonate the legitimate user and issue authenticated=
    API requests. 2026-06-25 7.5 CVE-2026-9221 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-9221 ] Significant-Gravitas--AutoGPT AutoGPT is a workflow a= utomation platform for creating, deploying, and managing continuous artific= ial intelligence agents. Prior to 0.6.52, an authenticated user can bypass = the SSRF / private-IP protections in SendWebRequestBlock and reach internal=
    network services. _is_ip_blocked() in backend/backend/util/request.py does=
    not normalize IPv4-mapped IPv6 addresses before checking resolved IPs agai= nst the blocked IPv4 ranges, and does not block special-use ranges such as = 100.64.0.0/10 (CGNAT, RFC 6598). A hostname that resolves to an IPv4-mapped=
    IPv6 address therefore passes validation and the request reaches the embed= ded internal IPv4 endpoint. This affects all AutoGPT Platform deployments. = This vulnerability is fixed in 0.6.52. 2026-06-26 8.5 CVE-2026-56663 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-56663 ] Significant-Gravitas--AutoG=
    PT AutoGPT is a workflow automation platform for creating, deploying, and m= anaging continuous artificial intelligence agents. In versions prior to 0.6= .52, the Fill Text Template block is vulnerable to a Denial of Service (DoS=
    ) attack. While the backend implements a SandboxedEnvironment to prevent un= authorized attribute access (e.g., blocking __class__), it fails to limit t=
    he computational complexity or execution time of the expressions. An attack=
    er can input computationally expensive Python/Jinja2 expressions that consu=
    me the server's CPU and memory, leading to a complete system hang or crash.=
    In multi-tenant or self-hosted environments, this results in a complete se= rvice outage and "noisy neighbor" effects that require manual administrativ=
    e intervention to recover. This issue has been fixed in version 0.6.52. 202= 6-06-24 7.7 CVE-2026-33235 [ https://www.cve.org/CVERecord?id=3DCVE-2026-33= 235 ] Site Building with Toolset--Toolset Forms Unauthenticated Insecure Di= rect Object References (IDOR) in Toolset Forms <=3D 2.6.24 versions. 2026-0= 6-26 7.5 CVE-2026-56069 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56069=
    ] siyuan-note--siyuan SiYuan is an open-source personal knowledge manageme=
    nt system. Prior to 3.7.0, SiYuan contains a stored cross-site scripting (X= SS) vulnerability in the Attribute View (database) asset cell renderer that=
    escalates to remote code execution (RCE) in the Electron desktop client. T= his vulnerability is fixed in 3.7.0. 2026-06-24 9.9 CVE-2026-50551 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-50551 ] siyuan-note--siyuan SiYuan is=
    an open-source personal knowledge management system. Prior to 3.7.0, CSS s= nippet body containing </style> breaks out of its surrounding <style> tag w= hen renderSnippet() interpolates it via insertAdjacentHTML. A payload like = runs arbitrary JavaScript in the renderer. On Electron desktop builds the r= enderer runs with nodeIntegration:true, so require('child_process') is reac= hable from the injected handler and the XSS chains to host RCE. Snippets sy=
    nc via the workspace repository, so an attacker with write access to any sy= nced workspace plants the payload once and it fires on every device that pu= lls. The bug also bypasses the user's enabledCSS / enabledJS separation. A = user who turned enabledJS off was making a deliberate call not to run untru= sted JavaScript; the CSS path runs it anyway. This vulnerability is fixed i=
    n 3.7.0. 2026-06-24 9.9 CVE-2026-54067 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54067 ] siyuan-note--siyuan SiYuan is an open-source personal k= nowledge management system. Prior to 3.7.0, the attribute-view (database) c= ell renderer genAVValueHTML interpolates cell content raw in four of its br= anches: text, url, phone, and mAsset. A cell value like </textarea><img src= =3Dx onerror=3D"..."> or "><img src=3Dx onerror=3D"..."> breaks out of its = surrounding tag and runs arbitrary JavaScript in the renderer when the vict=
    im opens the block-attribute panel. On Electron desktop the renderer runs w= ith nodeIntegration:true, so the XSS chains to host RCE via require('child_= process'). AV files live under the workspace and ride normal sync, so an at= tacker with write access to any synced workspace plants the payload once an=
    d it fires on every device that opens a panel containing that row.he kernel=
    doesn't escape on the way in either, so the malicious cell persists byte-f= or-byte. There's no equivalent of the html.EscapeAttrVal call that protects=
    block IAL attributes at kernel/model/blockial.go:261. This vulnerability i=
    s fixed in 3.7.0. 2026-06-24 9.9 CVE-2026-54158 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-54158 ] siyuan-note--siyuan SiYuan is an open-source per= sonal knowledge management system. Prior to 3.7.0, it does not escape the u= ntrusted fields (name, version, author, description) when they are serializ=
    ed into the data-obj HTML attribute of each marketplace card. Because the a= ttribute is single-quoted and the value is produced with JSON.stringify() (= which does not escape ', <, or >), a package whose name contains a single q= uote breaks out of the attribute and injects arbitrary HTML. In the desktop=
    client the main BrowserWindow runs with nodeIntegration: true, contextIsol= ation: false, so the injected markup escalates from DOM XSS to arbitrary OS=
    command execution. This is the same root cause and same impact as the orig= inal advisory, reached through a sibling sink the patch did not cover. This=
    vulnerability is fixed in 3.7.0. 2026-06-24 9 CVE-2026-55570 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-55570 ] siyuan-note--siyuan SiYuan is an o= pen-source personal knowledge management system. Prior to 3.7.0, the patch = for CVE-2026-41894 ("Path Traversal via Double URL Encoding") sanitized the=
    /export/ route but the identical root cause remains in the /assets/*path r= oute. In publish mode (anonymous read-only HTTP endpoint, default port 6808=
    ), an unauthenticated remote attacker can read arbitrary files inside Works= paceDir - including conf/conf.json (which contains the AccessAuthCode SHA25=
    6 hash, API token, and sync keys), temp/siyuan.db, temp/blocktree.db, and s= iyuan.log - by double-URL-encoding .. segments. This vulnerability is fixed=
    in 3.7.0. 2026-06-24 7.5 CVE-2026-54066 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54066 ] siyuan-note--siyuan SiYuan is an open-source personal k= nowledge management system. Prior to 3.7.0, renderPackageREADME in kernel/b= azaar/readme.go renders a Bazaar package README from Markdown to HTML with = the lute engine and SetSanitize(true). The lute sanitizer is an event-handl=
    er blocklist: allowAttr rejects only attribute names present in a fixed eve= ntAttrs map copied from the w3schools legacy handler list. That map omits m= odern event handlers. onpointerover, onpointerdown, onauxclick, onbeforetog= gle, onfocusin, onanimationstart, and ontransitionend are not in the list, =
    so the sanitizer passes them through verbatim on any tag. The frontend assi= gns the rendered HTML to mdElement.innerHTML in app/src/config/bazaar.ts wi=
    th no client-side DOMPurify on this path, into a normal element in the main=
    document (no iframe, no sandbox). The kernel sends no Content-Security-Pol= icy, X-Frame-Options, or X-Content-Type-Options header on any response, so =
    an inline handler runs when its event fires. The README is rendered when an=
    Administrator opens a package in Settings =C3=A2=E2=80=A0=E2=80=99 Marketp= lace, after the one-time marketplace trust consent. Install is not required=
    . Result: a third-party Bazaar package author runs JavaScript in the Admini= strator's authenticated SiYuan origin when the Administrator views and inte= racts with the package listing, and gains full control of the workspace. Th=
    is vulnerability is fixed in 3.7.0. 2026-06-24 7.1 CVE-2026-54070 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-54070 ] socat--socat socat versions 1.= 8.0.0 through 1.8.1.1 contain a heap-based buffer overflow vulnerability th=
    at allows a malicious SOCKS5 proxy server to overwrite adjacent heap memory=
    by exploiting a sign-extension flaw in the DOMAINNAME reply parser. During=
    connection setup, the domain name length byte is read through a signed cha=
    r field causing a negative bytes_to_read value that is implicitly converted=
    to size_t, resulting in an unbounded heap write into the 262-byte reply bu= ffer with attacker-controlled size and content. 2026-06-25 8.1 CVE-2026-561=
    23 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56123 ] SourceCodester--Cl= ass and Exam Timetabling System A vulnerability was found in SourceCodester=
    Class and Exam Timetabling System 1.0. This affects an unknown function of=
    the file /preview.php. Performing a manipulation of the argument course_ye= ar_section results in sql injection. The attack can be initiated remotely. = The exploit has been made public and could be used. 2026-06-28 7.3 CVE-2026= -13485 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13485 ] SourceCodester= --Class and Exam Timetabling System A vulnerability was determined in Sourc= eCodester Class and Exam Timetabling System 1.0/6.php. This impacts an unkn= own function of the file /preview6.php. Executing a manipulation of the arg= ument course_year_section can lead to sql injection. The attack can be laun= ched remotely. The exploit has been publicly disclosed and may be utilized.=
    2026-06-28 7.3 CVE-2026-13486 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-13486 ] SourceCodester--Class and Exam Timetabling System A vulnerability=
    was identified in SourceCodester Class and Exam Timetabling System 1.0. Af= fected is an unknown function of the file /archive.php. The manipulation of=
    the argument sy leads to sql injection. The attack may be initiated remote= ly. The exploit is publicly available and might be used. 2026-06-28 7.3 CVE= -2026-13487 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13487 ] SourceCod= ester--Class and Exam Timetabling System A security flaw has been discovere=
    d in SourceCodester Class and Exam Timetabling System 1.0/7.php. Affected b=
    y this vulnerability is an unknown functionality of the file /preview7.php.=
    The manipulation of the argument course_year_section results in sql inject= ion. The attack may be launched remotely. The exploit has been released to = the public and may be used for attacks. 2026-06-28 7.3 CVE-2026-13488 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-13488 ] Spring--Spring Statemachin=
    e Spring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Redi=
    s and ZooKeeper) deserialise persisted state-machine contexts without enfor= cing a class allowlist (CWE-502, deserialisation of untrusted data), which = can lead to remote code execution inside the application JVM. Affected vers= ions: Spring Statemachine 4.0.0 through 4.0.1 Spring Statemachine 3.2.0 thr= ough 3.2.4 2026-06-23 8.8 CVE-2026-41862 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-41862 ] Stranger Studios--Paid Memberships Pro - Add Member Fro=
    m Admin Unauthenticated Cross Site Request Forgery (CSRF) in Paid Membershi=
    ps Pro - Add Member From Admin <=3D 0.7.2 versions. 2026-06-26 8.8 CVE-2026= -57659 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57659 ] style-dictiona= ry--style-dictionary Style Dictionary, a build system for creating cross-pl= atform styles, has a prototype pollution vulnerability starting in version = 4.3.0 and prior to version 5.4.4. Impact users have: direct usage of `conve= rtTokenData(tokens, { output: 'object' });`; indirect usage, via using Expa=
    nd API; and/or indirect usage via SD's transform lifecycle. Impact is high = for this when style-dictionary is used as an integration in a NodeJS server=
    application. Impact is moderate for when style-dictionary is used as an in= tegration in a Web application. Impact is low for most common cases where t=
    he user of style-dictionary also maintains the tokens, and access is limite=
    d via read/write access to the repository/workflows where it is used. A pat=
    ch has been published in version `5.4.4`. The only known workaround is to s= anitize token data first. Whether using DTCG format or old Style Dictionary=
    format, check the token data object recursively for any object keys that i= nclude `__proto__`. 2026-06-24 8.8 CVE-2026-54639 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-54639 ] StylemixThemes--Motors Unauthenticated Broken = Access Control in Motors <=3D 1.4.109 versions. 2026-06-25 7.5 CVE-2026-548=
    28 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54828 ] StylemixThemes--Sp= lash - Sport Club WordPress Theme for Basketball, Football, Hockey Contribu= tor Local File Inclusion in Splash - Sport Club WordPress Theme for Basketb= all, Football, Hockey <=3D 4.4.3 versions. 2026-06-26 7.5 CVE-2025-68063 [ = https://www.cve.org/CVERecord?id=3DCVE-2025-68063 ] SureCart--SureCart Unau= thenticated Cross Site Scripting (XSS) in SureCart <=3D 4.3.2 versions. 202= 6-06-26 7.1 CVE-2026-57314 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57= 314 ] Syed Balkhi--Intranet & Private Site All-In-One Intranet Unauthentica= ted Broken Access Control in Intranet &amp; Private Site &#8211; All-In-One=
    Intranet <=3D 1.8.1 versions. 2026-06-26 7.5 CVE-2026-54837 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-54837 ] TablePress--TablePress Unauthentica= ted Cross Site Scripting (XSS) in TablePress <=3D 3.3.1 versions. 2026-06-2=
    5 7.1 CVE-2026-56051 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56051 ] = teableio--teable Teable's v2 REST API controller lacks @Permissions metadat=
    a on ORPC endpoints, allowing any authenticated user to bypass authorizatio=
    n checks. Attackers can read table schemas, create tables, and modify or de= lete records across bases and tables via endpoints like GET /api/v2/tables/= get and POST /api/v2/tables/updateRecords. 2026-06-26 8.8 CVE-2026-56773 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-56773 ] Templatespare--Template= Spare Administrator Arbitrary File Upload in TemplateSpare <=3D 4.2.0 versi= ons. 2026-06-26 9.1 CVE-2026-57658 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-57658 ] tenable--Tenable Identity Exposure Tenable Identity Exposure = contains multiple unauthenticated API endpoints under /w/api/* that expose = sensitive application configuration data including cleartext LDAP credentia= ls, SAML configuration, user accounts, and directory settings to unauthenti= cated remote attackers. Affected responses are served with Cache-Control: p= ublic headers and without Vary: Cookie, allowing reverse proxies and CDNs t=
    o cache and serve sensitive data to unauthenticated users even after authen= tication is applied. 2026-06-23 7.5 CVE-2026-13007 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-13007 ] Tenda--JD12L A security vulnerability has bee=
    n detected in Tenda JD12L 16.03.53.23. Impacted is the function formSetPPTP= Server of the file /goform/SetPptpServerCfg. Such manipulation of the argum= ent startIp leads to stack-based buffer overflow. The attack can be launche=
    d remotely. The exploit has been disclosed publicly and may be used. 2026-0= 6-28 8.8 CVE-2026-13515 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13515=
    ] Tenda--JD12L A vulnerability was detected in Tenda JD12L 16.03.53.23. Th=
    e affected element is the function fromSetWifiGusetBasic of the file /gofor= m/WifiGuestSet. Performing a manipulation of the argument shareSpeed result=
    s in stack-based buffer overflow. The attack may be initiated remotely. The=
    exploit is now public and may be used. 2026-06-28 8.8 CVE-2026-13516 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-13516 ] ThemeCatcher--Quform Subsc= riber Arbitrary File Upload in Quform <=3D 2.23.0 versions. 2026-06-26 9.9 = CVE-2026-56058 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56058 ] Themef= ic--Tourfic Subscriber SQL Injection in Tourfic <=3D 2.22.5 versions. 2026-= 06-26 8.5 CVE-2026-56064 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5606=
    4 ] themefic--Tourfic AI Powered Travel Booking, Hotel Booking & Car Rental=
    WordPress Plugin The Tourfic - AI Powered Travel Booking, Hotel Booking & = Car Rental WordPress Plugin plugin for WordPress is vulnerable to generic S=
    QL Injection via the 'post_id' parameter in all versions up to, and includi= ng, 2.22.7 due to insufficient escaping on the user supplied parameter and = lack of sufficient preparation on the existing SQL query. This makes it pos= sible for unauthenticated attackers to append additional SQL queries into a= lready existing queries that can be used to extract sensitive information f= rom the database. The AJAX handler is registered for unauthenticated users = via wp_ajax_nopriv_tf_room_availability, and the required nonce is emitted =
    on the public single-hotel page template, allowing unauthenticated attacker=
    s to freely obtain a valid nonce and reach the vulnerable code path. 2026-0= 6-25 7.5 CVE-2026-12937 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12937=
    ] ThemeFusion--Fusion Builder Contributor Privilege Escalation in Fusion B= uilder <=3D 3.15.4 versions. 2026-06-26 8.8 CVE-2026-56008 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-56008 ] ThemeHunk--Advance Product Search Una= uthenticated SQL Injection in Advance Product Search <=3D 1.4.4 versions. 2= 026-06-26 9.3 CVE-2026-56070 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 56070 ] themewant--Easy Elements for Elementor =E2=80=9C Addons & Website T= emplates Unauthenticated Privilege Escalation in Easy Elements for Elemento=
    r &#8211; Addons &amp; Website Templates <=3D 1.4.9 versions. 2026-06-26 9.=
    8 CVE-2026-56028 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56028 ] Tomd= ever--wpForo Forum Contributor SQL Injection in wpForo Forum <=3D 3.0.9 ver= sions. 2026-06-26 8.5 CVE-2026-57636 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-57636 ] tomojitakasu--RTKLIB RTKLIB through 2.4.3 contains an out-o= f-bounds write vulnerability in decode_type1033 function that fails to clam=
    p length counters to destination buffer size, allowing up to 191-byte overf= low into fixed 64-byte descriptor fields. An attacker controlling an NTRIP =
    or serial RTCM3 correction stream can craft a valid CRC-bearing type-1033 m= essage to corrupt adjacent rtcm_t object members, potentially achieving arb= itrary code execution or denial of service. 2026-06-25 9.8 CVE-2026-56786 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-56786 ] ToolJet--ToolJet ToolJ=
    et is the open-source foundation am AI-native platform for building and dep= loying internal tools, workflows and AI agents. Prior to 3.20.178-lts, ther= e's an SSRF in the RestAPI data source component. The RestAPI data source e= xecutes HTTP requests server-side, and its private IP filter only checks th=
    e hostname string - not the resolved IP. DNS names like 169.254.169.254.nip= .io resolve to the Azure IMDS link-local address and bypass the filter enti= rely. This allows any authenticated user (free tier) to steal Azure managed=
    identity tokens for the AKS production cluster. This vulnerability is fixe=
    d in 3.20.178-lts. 2026-06-25 8.3 CVE-2026-55412 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-55412 ] Traefik--Traefik Traefik before 2.10.5 and 3.0.= 0-beta4 is affected by a denial-of-service vulnerability in HTTP/2 request = handling inherited from the Go standard library's HTTP/2 implementation (CV= E-2023-44487 / CVE-2023-39325, the 'Rapid Reset' technique). A remote attac= ker can rapidly create and cancel HTTP/2 streams to exhaust server resource=
    s and cause service unavailability. 2026-06-23 7.5 CVE-2023-54365 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2023-54365 ] Tribulant Software--Newsletter=
    s newsletters_subscribers Broken Access Control in Newsletters <=3D 4.13 ve= rsions. 2026-06-26 8.1 CVE-2026-57645 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-57645 ] Tribulant Software--Newsletters Unauthenticated Broken Acc= ess Control in Newsletters <=3D 4.13 versions. 2026-06-26 7.3 CVE-2026-5484=
    0 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54840 ] TryGhost--Ghost Gho=
    st is a Node.js content management system. From until 6.37.0, when Ghost is=
    behind a shared caching layer that results in cached content being shared = between different visitors, an unauthenticated user could send an x-ghost-p= review header that altered the rendered frontend response. In affected cach=
    e configurations, that response could be stored and served to subsequent vi= sitors requesting the same page, allowing cache poisoning of request-specif=
    ic preview output. When running Ghost's frontend and admin panel on the sam=
    e domain this could be used to take over staff user accounts. When running = these on different domains staff accounts have no exposure. This vulnerabil= ity is fixed in 6.37.0. 2026-06-24 9.6 CVE-2026-53943 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-53943 ] TryGhost--Ghost @tryghost/activitypub is G= host's social/federation client app. Prior to 3.1.0, the ActivityPub client=
    in Ghost was vulnerable to JavaScript injection on posts shared by a malic= iously customised ActivityPub server. This vulnerability is fixed in 3.1.0.=
    2026-06-24 7.5 CVE-2026-53950 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-53950 ] twentyhq--twenty Twenty is an open-source CRM (customer relations= hip management) platform. Prior to 2.9.0, Twenty was vulnerable to a cross-= workspace insecure direct object reference (IDOR) in the AI agent monitor's=
    AgentTurnResolver, in packages/twenty-server/src/engine/metadata-modules/a= i/ai-agent-monitor/reso lvers/agent-turn.resolver.ts. The agentTurns(agentI=
    d) query and the evaluateAgentTurn(turnId) mutation looked up rows by agent=
    Id or id only; although AgentTurnEntity has a workspaceId column, it was no=
    t included in the WHERE clause, and the class-level guards only checked tha=
    t the caller was authenticated in some workspace rather than that the reque= sted object belonged to it, with the same flaw present in agent-turn-grader= .service.ts. As a result, any authenticated user with the AI settings flag,=
    a workspace owner by default, could target any other workspace on the same=
    instance given the victim's agentId or turnId: agentTurns returned the vic= tim's full chat history including message parts such as raw chat text, tool=
    calls, and tool outputs, while evaluateAgentTurn inserted an agentTurnEval= uation row with the victim's workspaceId and fed the victim's turn into the=
    default LLM. The agentId and turnId are non-guessable UUIDs but are expose=
    d in the URL of the settings page. This issue is fixed in version 2.9.0. 20= 26-06-24 7.6 CVE-2026-55583 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 5583 ] Tyche Softwares.--Abandoned Cart Pro for WooCommerce Subscriber Priv= ilege Escalation in Abandoned Cart Pro for WooCommerce <=3D 10.4.0 versions=
    . 2026-06-26 8.8 CVE-2026-56010 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-56010 ] tychesoftwares--Print Invoice & Delivery Notes for WooCommerce U= nauthenticated Sensitive Data Exposure in Print Invoice & Delivery Notes fo=
    r WooCommerce <=3D 7.1.1 versions. 2026-06-26 7.5 CVE-2026-56060 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-56060 ] Ubuntu--Canonical ADSys An issu=
    e was discovered in Canonical ADSys upstream versions through v0.16.2. Duri=
    ng Active Directory Certificate Services (AD CS) certificate auto-enrollmen=
    t via the vendored Samba client script (internal/policies/certificate/pytho= n/vendor_samba/gp/gp_cert_auto_enroll_ext.py), ADSys utilizes a plaintext H= TTP connection (http://) instead of a secure HTTPS connection (https://) to=
    request the CA certificate from the Active Directory Certificate Services = server (GetCACert). An unauthenticated network attacker positioned between = the managed Ubuntu host and the configured AD CS CA hostname can conduct a = Man-in-the-Middle (MITM) attack. By intercepting the plaintext HTTP request=
    , the attacker can supply an arbitrary, attacker-controlled Root CA certifi= cate. Because the system automatically accepts this certificate and registe=
    rs it into the local system trust store via update-ca-certificates, this re= sults in system-wide trust store poisoning. Consequently, TLS clients utili= zing the operating system trust store on the affected machine will accept r= ogue certificates for arbitrary domains, enabling persistent decryption and=
    interception of subsequent TLS connections. This issue is resolved in vers= ion v0.16.3. 2026-06-22 8.3 CVE-2026-12249 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-12249 ] ultimatemember--Ultimate Member User Profile, Registr= ation, Login, Member Directory, Content Restriction & Membership Plugin The=
    Ultimate Member plugin for WordPress is vulnerable to Account Takeover via=
    Password Reset Link Disclosure in all versions up to and including 2.11.4.=
    This is due to a chain of three logic bugs: (1) an MD5 hash fallback in ge= t_directory_by_hash() that allows any post to be used as a member directory=
    by computing SUBSTRING(MD5(post_id), 11, 5), (2) a strstr() parsing logic = flaw in post_data() that allows bypassing WordPress's protected meta key re= strictions by placing '_um_' anywhere in the meta key name rather than at t=
    he start, and (3) missing field name validation in build_user_card_data() t= hat allows arbitrary field names including 'password_reset_link' to be pass=
    ed to um_filtered_value(). This makes it possible for authenticated attacke=
    rs with Contributor-level access and above to create a malicious post via X= MLRPC with crafted meta fields, use the MD5 fallback to point the member di= rectory AJAX handler to their post, inject 'password_reset_link' into the t= agline_fields configuration, and leak live password reset URLs for all user=
    s in the member directory response, including administrators. 2026-06-24 8.=
    8 CVE-2026-7761 [ https://www.cve.org/CVERecord?id=3DCVE-2026-7761 ] Uncann=
    y Owl--Uncanny Automator Unauthenticated PHP Object Injection in Uncanny Au= tomator <=3D 7.3.1.2 versions. 2026-06-26 8.1 CVE-2026-56031 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-56031 ] Uncanny Owl--Uncanny Automator Pro = Subscriber PHP Object Injection in Uncanny Automator Pro <=3D 7.3.0.6 versi= ons. 2026-06-26 9.8 CVE-2026-56057 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-56057 ] unclecode--crawl4ai Crawl4AI is an open-source LLM friendly w=
    eb crawler & scraper. Prior to 0.8.7, the _safe_eval_expression() function =
    in the computed fields feature uses an AST validator that only blocks attri= butes starting with underscore. Python generator and frame object attribute=
    s (gi_frame, f_back, f_builtins) do NOT start with underscore, enabling a c= omplete sandbox escape to achieve arbitrary code execution. The attack requ= ires no authentication (JWT disabled by default) and is triggered via POST = /crawl with a crafted extraction schema. This vulnerability is fixed in 0.8= .7. 2026-06-23 9.8 CVE-2026-53753 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-53753 ] unclecode--crawl4ai Crawl4AI is an open-source LLM friendly we=
    b crawler & scraper. Prior to 0.8.9, the Docker API server applied its SSRF=
    destination check to the crawl target URL only, not to the proxy address. =
    An unauthenticated request could supply a proxy pointing at an internal IP = and route the browser through it, reaching internal services and cloud-meta= data endpoints, while using a perfectly valid crawl URL. The Docker API is = unauthenticated by default. /crawl, /crawl/stream, and /crawl/job accept a = browser_config (and crawler_config). The following all feed Chromium's egre=
    ss and were unchecked: browser_config.proxy_config.server, browser_config.p= roxy (deprecated field), crawler_config.proxy_config.server, and --proxy-se= rver / --proxy-pac-url / --proxy-bypass-list / --host-resolver-rules flags =
    in browser_config.extra_args. This vulnerability is fixed in 0.8.9. 2026-06= -23 8.6 CVE-2026-53755 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53755 =
    ] unclecode--crawl4ai Crawl4AI is an open-source LLM friendly web crawler &=
    scraper. Prior to 0.8.8, the Docker API server's SSRF protection (validate= _webhook_url / validate_url_destination in deploy/docker/utils.py) used an = explicit IPv4/IPv6 CIDR blocklist that missed several address families. An = attacker could reach internal services and cloud metadata endpoints (e.g. 1= 69.254.169.254) despite the filter by encoding an internal IPv4 address ins= ide an IPv6 transition form, or by using the IPv6 unspecified address. Beca= use the Docker API is unauthenticated by default (jwt_enabled: false), no c= redentials are required. This vulnerability is fixed in 0.8.8. 2026-06-23 7=
    .5 CVE-2026-53754 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53754 ] Val= vePress--Automatic Unauthenticated Cross Site Scripting (XSS) in Automatic =
    < 3.135.1 versions. 2026-06-26 7.1 CVE-2026-56045 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-56045 ] vanhauser-thc--thc-hydra Hydra through 9.7, fi= xed in commit 9cc84c2, contains a stack buffer overflow in NTLM authenticat= ion across SMTP, POP3, IMAP, NNTP, HTTP, HTTP-Proxy, and HTTP-Proxy-Urlenum=
    modules when processing malicious NTLM Type-2 challenges. A malicious serv=
    er can send a crafted NTLM Type-2 challenge with an excessively long domain=
    string, causing base64-encoded response data to overflow a 500-byte stack = buffer by 18 to 330 bytes, enabling remote code execution on systems withou=
    t stack protection. 2026-06-25 8.8 CVE-2026-56766 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-56766 ] vllm-project--vllm vLLM is an inference and se= rving engine for large language models (LLMs). From 0.3.0 until 0.22.0, a v= ulnerability in ASGI web servers and starlette's trust on those web servers=
    enables an authentication bypass of the OpenAI API AuthenticationMiddlewar=
    e. It allows to use the API without providing the configured VLLM_API_KEY o=
    r --api-key. This vulnerability is fixed in 0.22.0. 2026-06-22 9.1 CVE-2026= -48746 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48746 ] vllm-project--= vllm vLLM is an inference and serving engine for large language models (LLM= s). Prior to 0.22.1, the vLLM Dockerfile is vulnerable to a dependency conf= usion attack through the flashinfer-jit-cache package. The package is insta= lled from a custom index (flashinfer.ai/whl/) using --extra-index-url, but = the package name was not registered on PyPI, and UV_INDEX_STRATEGY=3D"unsaf= e-best-match" is set globally. An attacker who registers flashinfer-jit-cac=
    he on PyPI with version 0.6.11.post2 can execute arbitrary code as root dur= ing the Docker build and backdoor every resulting container image, enabling=
    exfiltration of all user prompts, API credentials, and model data from pro= duction vLLM deployments This vulnerability is fixed in 0.22.1. 2026-06-22 = 8.8 CVE-2026-54232 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54232 ] vl= lm-project--vllm vLLM is an inference and serving engine for large language=
    models (LLMs). Prior to 0.22.0, an assert-based security check in vLLM's a= ctivation function loading allows any unauthenticated attacker to achieve a= rbitrary code execution on the server by publishing a malicious HuggingFace=
    model, when vLLM runs in Python optimized mode (python -O or PYTHONOPTIMIZ= E=3D1). This vulnerability is fixed in 0.22.0. 2026-06-22 7.5 CVE-2026-4152=
    3 [ https://www.cve.org/CVERecord?id=3DCVE-2026-41523 ] vtk--vtk vtk vtk-di= com vtkDICOMItem::NewDataElement heap-based buffer overflow vulnerability 2= 026-06-25 8.1 CVE-2026-22879 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 22879 ] warpdotdev--warp Warp is an agentic development environment. From 0= .2023.10.24.08.03.stable_00 until 0.2026.05.06.15.42.stable_01, Warp may op=
    en executable local files through the operating system default file handler=
    . A malicious Markdown document or project can contain a local-file link th=
    at appears as normal rendered content. If a user opens the Markdown in Warp=
    and clicks the link, affected builds may route the resolved local file to =
    a platform file opener instead of limiting the action to safe viewer/editor=
    targets. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01. 2026= -06-24 8.8 CVE-2026-48704 [ https://www.cve.org/CVERecord?id=3DCVE-2026-487=
    04 ] warpdotdev--warp Warp is an agentic development environment. From 0.20= 25.08.06.08.12.stable_00 until 0.2026.05.06.15.42.stable_01, Warp contains =
    a command injection in the prompt branch selector. A user who can publish a=
    branch to a Git repository opened in Warp can cause a crafted branch name =
    to be interpreted by the victim's shell if the victim selects that branch f= rom the UI. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01. 20= 26-06-24 8 CVE-2026-48719 [ https://www.cve.org/CVERecord?id=3DCVE-2026-487=
    19 ] warpdotdev--warp Warp is an agentic development environment. From 0.20= 25.03.05.08.02.stable_00 until 0.2026.05.06.15.42.stable_01, Warp accepts n= on-inline `OSC 1337;File` payloads from terminal output and materialize the=
    decoded payload as a local file without an additional confirmation step. T= his vulnerability is fixed in 0.2026.05.06.15.42.stable_01. 2026-06-24 8.8 = CVE-2026-48720 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48720 ] warpdo= tdev--warp Warp is an agentic development environment. From 0.2025.10.08.08= .12.stable_00 until 0.2026.05.06.15.42.stable_01, Warp contains a command e= xecution permission-check bypass in the default unsandboxed CLI agent profi= le. The CLI profile is non-interactive and relies on a command denylist as =
    a safety boundary for commands that should require confirmation. Because co= mmand strings were checked before canonicalizing leading environment-variab=
    le assignments, an attacker who can influence the agent's command output ma=
    y cause denylisted commands to be treated as non-denylisted. This vulnerabi= lity is fixed in 0.2026.05.06.15.42.stable_01. 2026-06-24 8.6 CVE-2026-4872=
    1 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48721 ] warpdotdev--warp Wa=
    rp is an agentic development environment. From 0.2021.04.25.23.05.stable_00=
    until 0.2026.05.06.15.42.stable_01, Warp allows terminal output to request=
    access to the local system clipboard. A malicious remote host, remote prog= ram, or other attacker-controlled terminal output source can trigger clipbo= ard reads or writes without a separate confirmation step. This crosses the = trust boundary between untrusted terminal output and the user's local deskt=
    op clipboard. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01. = 2026-06-24 8.1 CVE-2026-48725 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -48725 ] warpdotdev--warp Warp is an agentic development environment. From = 0.2023.03.21.08.02.stable_00 until 0.2026.05.06.15.42.stable_01, Warp conta= ins a command injection issue in the legacy SSH background command path. Wa=
    rp used the remote working directory reported by the session when building = helper commands for SSH-backed metadata collection. A remote host, reposito= ry, or directory name controlled by an attacker could cause that helper com= mand to execute additional shell syntax on the remote host as the victim's = authenticated SSH account. This vulnerability is fixed in 0.2026.05.06.15.4= 2.stable_01. 2026-06-24 8.8 CVE-2026-48732 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-48732 ] warpdotdev--warp Warp is an agentic development envir= onment. From 0.2025.04.09.08.11.stable_00 until 0.2026.05.06.15.42.stable_0=
    1, Warp contains a command execution policy bypass in Agent code search too= ls. The affected Grep and FileGlob actions are authorized as read/search op= erations, but their implementations build shell command strings from Agent-= controlled inputs (search text, paths, glob patterns) and execute them in t=
    he active terminal session. This vulnerability is fixed in 0.2026.05.06.15.= 42.stable_01. 2026-06-24 7.8 CVE-2026-48703 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-48703 ] warpdotdev--warp Warp is an agentic development envi= ronment. From 0.2024.02.20.08.01.stable_01 until 0.2026.05.06.15.42.stable_= 01, Warp contains a command injection issue in the Linux external editor la= uncher. Warp expanded freedesktop .desktop Exec templates for affected edit=
    or integrations and executed the expanded command through a shell. A user w=
    ho opens an attacker-controlled local file path through an affected externa=
    l editor or system-default editor route can cause shell syntax embedded in = that path to execute as the local user. This vulnerability is fixed in 0.20= 26.05.06.15.42.stable_01. 2026-06-24 7.8 CVE-2026-48731 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-48731 ] warpdotdev--warp Warp is an agentic deve= lopment environment. From 0.2024.03.12.08.02.stable_01 until 0.2026.05.06.1= 5.42.stable_01, Warp contains an OS command injection vulnerability in the = WSL URL-opening fallback. When Warp is running under WSL and cannot open a = URL through wslview, it falls back to a Windows command processor path. A U=
    RL controlled through terminal output can reach that fallback when the user=
    opens the link. This vulnerability is fixed in 0.2026.05.06.15.42.stable_0=
    1. 2026-06-24 7.7 CVE-2026-54699 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-54699 ] Wasiliy Strecker--Contest Gallery Contributor SQL Injection in = Contest Gallery <=3D 30.0.0 versions. 2026-06-26 8.5 CVE-2026-57662 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-57662 ] webp-sh--webp_server_go WebP=
    Server Go through 0.14.4 contains a path traversal vulnerability on Window=
    s that allows unauthenticated attackers to read files outside the configure=
    d IMG_PATH directory by sending requests with percent-encoded backslashes (= %5C) that bypass the path.Clean() sanitization in handler/router.go. Attack= ers can exploit the discrepancy between Go's forward-slash-only path normal= ization and Windows file system APIs that treat backslashes and forward sla= shes as equivalent to access arbitrary files on the host filesystem accessi= ble to the server process. 2026-06-22 7.5 CVE-2026-53779 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-53779 ] wedevs--Dokan Pro The Dokan Pro plugin = for WordPress is vulnerable to time-based SQL Injection via the via 'latitu= de' and 'longitude' parameters in all versions up to, and including, 5.0.4 = due to insufficient escaping on the user supplied parameter and lack of suf= ficient preparation on the existing SQL query. This makes it possible for u= nauthenticated attackers to append additional SQL queries into already exis= ting queries that can be used to extract sensitive information from the dat= abase. 2026-06-25 7.5 CVE-2026-12077 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-12077 ] weDevs--weMail Unauthenticated Cross Site Scripting (XSS) i=
    n weMail <=3D 2.1.2 versions. 2026-06-26 7.1 CVE-2026-57322 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-57322 ] withastro--astro Astro is a web fram= ework. Prior to 6.3.3, when a component uses a client:* directive, Astro in= serts named slot content into a data-astro-template attribute without HTML = escaping the slot name allowing an attacker to break out of the attribute c= ontext and inject arbitrary HTML, resulting in reflected XSS during SSR. Th=
    is vulnerability is fixed in 6.3.3. 2026-06-22 7.1 CVE-2026-50146 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-50146 ] withastro--astro Astro is a we=
    b framework. Prior to 6.4.6, Astro SSR apps with prerendered error pages (/= 404 or /500 using export const prerender =3D true) fetch those pages over H= TTP at runtime when an error occurs. The URL for this fetch is derived from=
    request.url, which in turn gets its origin from the incoming Host header. = When the Host header is not validated against allowedDomains, an attacker c=
    an point the fetch at an arbitrary host and read the response. This vulnera= bility is fixed in 6.4.6. 2026-06-22 7.5 CVE-2026-54299 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-54299 ] WordPress.com--Gutenverse Form Unauthent= icated Cross Site Scripting (XSS) in Gutenverse Form <=3D 2.4.7 versions. 2= 026-06-26 7.1 CVE-2026-56040 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 56040 ] WordPress.com--Quick Interest Slider Unauthenticated Cross Site Scr= ipting (XSS) in Quick Interest Slider <=3D 3.1.6 versions. 2026-06-26 7.1 C= VE-2026-56039 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56039 ] WP All = Import--WP All Import Administrator SQL Injection in WP All Import <=3D 4.0=
    .1 versions. 2026-06-26 7.6 CVE-2026-57628 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-57628 ] WP Swings--Subscriptions for WooCommerce Unauthentica= ted Broken Access Control in Subscriptions for WooCommerce <=3D 1.9.5 versi= ons. 2026-06-26 7.5 CVE-2026-56061 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-56061 ] wpDataTables--wpDataTables Unauthenticated SQL Injection in w= pDataTables <=3D 7.4 versions. 2026-06-26 9.3 CVE-2026-54825 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-54825 ] wpeverest--Everest Forms Unauthenti= cated Cross Site Scripting (XSS) in Everest Forms <=3D 3.4.8 versions. 2026= -06-26 7.1 CVE-2026-57312 [ https://www.cve.org/CVERecord?id=3DCVE-2026-573=
    12 ] wpjobportal--WP Job Portal Contributor SQL Injection in WP Job Portal = <=3D 2.5.2 versions. 2026-06-26 8.5 CVE-2026-57653 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-57653 ] WPMU DEV--Forminator Unauthenticated Cross Si=
    te Scripting (XSS) in Forminator <=3D 1.53.1 versions. 2026-06-25 7.1 CVE-2= 026-56071 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56071 ] WSO2--WSO2 = API Manager The WSO2 API Manager's message flow component, when processing = WS-Addressing headers, does not sufficiently validate or restrict user-cont= rolled input within these headers. This omission allows an attacker to mani= pulate WS-Addressing headers to specify arbitrary destinations for server-i= nitiated requests. Successful exploitation allows an unauthenticated attack=
    er to control the destination of server-initiated requests originating from=
    the WSO2 API Manager. This direct control can enable unauthorized access t=
    o internal network resources or services that would typically be inaccessib=
    le from external networks. 2026-06-26 8.3 CVE-2026-2053 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-2053 ] Xtemos--WoodMart Unauthenticated Cross Si=
    te Scripting (XSS) in WoodMart <=3D 8.5.3 versions. 2026-06-26 7.1 CVE-2026= -56072 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56072 ] yashpokharna25= 55--restaurent-management-system A vulnerability was identified in yashpokh= arna2555 restaurent-management-system. This affects an unknown function of = the file /forgotpassword.php of the component POST Parameter Handler. Such = manipulation of the argument email leads to sql injection. The attack can b=
    e launched remotely. The exploit is publicly available and might be used. T= his product does not use versioning. This is why information about affected=
    and unaffected releases are unavailable. The project was informed of the p= roblem early through an issue report but has not responded yet. 2026-06-28 = 7.3 CVE-2026-13498 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13498 ] YM= C--YMC Filter Improper Neutralization of Special Elements used in an SQL Co= mmand ('SQL Injection') vulnerability in YMC Filter allows SQL Injection. T= his issue affects YMC Filter: from n/a through 3.11.5. 2026-06-25 9.3 CVE-2= 026-54836 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54836 ] yt-dlp--yt-= dlp yt-dlp is a command-line audio/video downloader. Prior to 2026.06.09, a=
    vulnerability exists in yt-dlp that allows a remote attacker to write arbi= trary OS-shortcut files (such as .desktop, .url, .webloc) to the user's fil= esystem, bypassing the remediation for CVE-2024-38519. The allowlist explic= itly included the unsafe extensions .desktop, .url, and .webloc so that the=
    functionality of the --write-link option (and its variants) could be prese= rved. These allowlist inclusions can be exploited by an attacker to write m= alicious OS-shortcut files in the context of a media or subtitles download.=
    This vulnerability is fixed in 2026.06.09. 2026-06-23 8.3 CVE-2026-50023 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-50023 ] yt-dlp--yt-dlp yt-dlp =
    is a command-line audio/video downloader. Prior to 2026.06.09, if aria2c is=
    used as an external downloader for a fragmented manifest format (such as a=
    n HLS/DASH stream), yt-dlp passes insufficiently sanitized input to aria2c = that allows an attacker to perform an arbitrary file write. On Windows plat= forms, this can lead to immediate arbitrary code execution. On non-Windows = platforms, this can lead to arbitrary code execution upon the next invocati=
    on of yt-dlp. This vulnerability is fixed in 2026.06.09. 2026-06-23 8.3 CVE= -2026-50574 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50574 ] zaproxy--= zap-extensions Zed Attack Proxy (ZAP) ViewState add-on before version 4 con= tains an insecure deserialization vulnerability that allows attackers who c= ontrol a proxied web server to achieve arbitrary code execution by embeddin=
    g a malicious serialized Java object in the javax.faces.ViewState HTTP resp= onse parameter. The JSFViewState.decode() method base64-decodes the ViewSta=
    te value and passes it directly to ObjectInputStream.readObject() without a=
    deserialization filter, allowlist, or type restriction, causing the malici= ous object to be deserialized within the ZAP JVM when the Desktop UI render=
    s the ViewState panel. 2026-06-26 8.8 CVE-2026-57527 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-57527 ] zephyrproject--zephyr Zephyr's IP socket re= cvmsg() implementation (subsys/net/lib/sockets/sockets_inet.c, insert_pktin= fo()) validated the user-supplied ancillary (msg_control) buffer using only=
    the payload length (msg-msg_controllen < pktinfo_len) before writing a ful=
    l control message consisting of an aligned cmsg header plus the payload. Be= cause the check omitted the cmsg header size, a control buffer whose length=
    falls in the under-checked window (e.g. 16-27 bytes for IPv4 IP_PKTINFO on=
    a 64-bit target, where a single element actually occupies 28 bytes) passes=
    the guard yet causes a fixed-size out-of-bounds write of up to one cmsg he= ader (~12 bytes) past the end of the buffer. Under CONFIG_USERSPACE the rec= vmsg verifier allocates a kernel-heap copy of the control buffer sized to m= sg_controllen and runs the implementation against it, so the overflow corru= pts kernel heap memory and is triggerable from an unprivileged userspace th= read; in supervisor mode it corrupts the caller's buffer. The path is reach= able on a UDP/IP socket with IP_PKTINFO/IPV6_RECVPKTINFO (or hoplimit/times= tamping) enabled when the application calls recvmsg() with an undersized co= ntrol buffer and a datagram is received; part of the overwritten bytes (the=
    destination IP in ipi_addr) is influenced by the received packet. The fix = makes the capacity check use NET_CMSG_SPACE(pktinfo_len) (aligned header + = aligned data) and returns -ENOMEM when the buffer is too small. Affected: v= 3.6.0 through v4.4.0. 2026-06-27 8.7 CVE-2026-10643 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-10643 ] zephyrproject--zephyr Zephyr's BSD-sockets g= etaddrinfo() implementation (subsys/net/lib/sockets/getaddrinfo.c) passes a=
    pointer to a stack-allocated state object (struct getaddrinfo_state ai_sta= te) as the user_data of an asynchronous DNS resolver query. The socket laye=
    r waits on a semaphore with a timeout deliberately set slightly longer than=
    the resolver's own per-query timeout. When that semaphore wait nonetheless=
    times out (-EAGAIN) - which can occur when the resolver's timeout work is = delayed by workqueue contention, or in the documented multi-retry configura= tion where CONFIG_NET_SOCKETS_DNS_TIMEOUT exceeds CONFIG_NET_SOCKETS_DNS_BA= CKOFF_INTERVAL - the pre-fix code retries the query (goto again) without ca= ncelling the previous one and without resetting the semaphore. The previous=
    query slot remains active in the resolver with its callback and the stack = pointer as user_data, and ai_state-dns_id is overwritten so the stale query=
    can no longer be cancelled. A subsequent DNS response delivered over UDP a=
    nd matched by its 16-bit transaction id (in dispatcher_cb()/dns_read()), or=
    the resolver's own delayed query-timeout work, then invokes dns_resolve_cb=
    () against the now out-of-scope stack frame, writing through the stale poin= ter (state-status, state-idx, state-ai_arr[], and k_sem_give()). Because th=
    e triggering response is network-delivered and its 16-bit id is spoofable/r= eplayable by an on- or off-path attacker, this is a network-influenceable u= se-after-return that can corrupt reused stack memory, leading to crashes/de= nial of service or memory corruption. The fix cancels the timed-out query b=
    y name and type before retrying and resets the local semaphore, eliminating=
    the stale callback path. Affected: Zephyr v4.0.0 through v4.4.0. 2026-06-2=
    8 7.4 CVE-2026-10646 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10646 ] = zephyrproject-rtos--Zephyr A malformed Bluetooth Classic SDP attribute can = trigger a reachable assertion in Zephyr's SDP parser. In subsys/bluetooth/h= ost/classic/sdp.c, bt_sdp_parse_attribute() accepts an input buffer once it=
    contains the 1-byte attribute type and 2-byte attribute id, but then uncon= ditionally pulls an additional byte for the value type without verifying th=
    at the byte is present. A truncated 3-byte attribute (for example 09 00 09)=
    therefore reaches net_buf_simple_pull() with insufficient remaining length=
    , triggering the __ASSERT_NO_MSG(buf->len >=3D len) check and a kernel pani=
    c in assert-enabled builds (denial of service). In builds where assertions = are disabled, parsing may continue past the end of the available buffer, le= ading to an out-of-bounds read and undefined behavior. 2026-06-22 7.1 CVE-2= 026-10651 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10651 ] zephyrproje= ct-rtos--Zephyr A missing length validation in the Zephyr Bluetooth Host IS=
    O receive path can be triggered by malformed HCI ISO data. In bt_iso_recv()=
    (subsys/bluetooth/host/iso.c), when processing PB=3DSTART/SINGLE fragments=
    , the code pulls a TS SDU header (8 bytes, ts=3D1) or a non-TS SDU header (=
    4 bytes, ts=3D0) without first verifying that buf->len contains at least th=
    at many bytes. The outer HCI ISO length check in hci_iso() validates payloa=
    d length consistency but not the minimum inner SDU header size, so a packet=
    with payload length 1 passes hci_iso() and then reaches net_buf_pull_mem()=
    , which asserts buf->len >=3D len. As a result, malformed ISO traffic deter= ministically triggers a kernel assert (denial of service) in assert-enabled=
    builds, and in non-assert builds the same path may proceed with an undersi= zed buffer, leading to out-of-bounds read behavior. The issue affects produ= cts using the Zephyr Host with CONFIG_BT_ISO_RX enabled, particularly where=
    incoming HCI data can be influenced by a malicious or compromised controll=
    er or malformed forwarded ISO traffic. 2026-06-22 7.1 CVE-2026-10658 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-10658 ] zephyrproject-rtos--Zephyr = Zephyr's IPv6 network stack can be prevented from receiving or processing f= uture incoming packets by sending a small number of maliciously fragmented = IPv6 packets. When such a packet is handled by the fragment-header processi=
    ng path, the associated RX network packet buffer (allocated from a memory s= lab) is not released back to the pool. Repeating the malicious packet exhau= sts all RX buffer slots, after which the device can no longer obtain RX buf= fers and stops receiving traffic, resulting in a denial of service. 2026-06= -25 7.5 CVE-2026-13351 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13351 =
    ] zohocorp--manageengine_adselfservice_plus In ManageEngine ADSelfService P= lus, RecoveryManager Plus, M365 Manager Plus, and ADAudit Plus, the SSO tic= kets generated to authenticate that session could be predicted by an unauth= enticated user, leading to account takeover. 2026-06-23 9 CVE-2026-11374 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-11374 ]=20

    Back to top [ #top ]

    Medium Vulnerabilities

    Primary
    Vendor -- Product Description Published CVSS Score Source Info 1Panel-dev--= MaxKB MaxKB before 2.10.0 contains a server-side request forgery vulnerabil= ity in tool creation and update endpoints that allows authenticated users t=
    o make arbitrary server requests by supplying unvalidated downloadCallbackU=
    rl and download_url parameters. Attackers with default workspace USER role = can exploit this to access internal network services by providing malicious=
    URLs to the ToolSerializer endpoints. 2026-06-25 6.4 CVE-2026-56779 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-56779 ] 24liveblog--24liveblog live=
    blog tool The 24liveblog - live blog tool plugin for WordPress is vulnerab=
    le to Exposure of Sensitive Information in versions up to, and including, 2= .2. This is due to the lb24_block_enqueue_scripts() function being hooked t=
    o enqueue_block_editor_assets and, for any non-administrator user, falling = back to loading the administrator-configured site-wide 24liveblog integrati=
    on secrets (lb24_token, lb24_refresh_token, lb24_uid, lb24_uname) from the = options table via get_option() and emitting them through wp_localize_script=
    () as the lb24BlockData JavaScript object. This makes it possible for authe= nticated attackers, with contributor-level access and above, to extract thi= rd-party 24liveblog account credentials (including the API token and refres=
    h token) by simply opening the block editor and inspecting the page source.=
    2026-06-24 4.3 CVE-2026-9183 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -9183 ] 24liveblog--24liveblog live blog tool The 24liveblog - live blog to=
    ol plugin for WordPress is vulnerable to unauthorized modification of data = due to a missing capability check on the update_lb24_token() AJAX function =
    in versions up to, and including, 2.2. The handler only verifies the 'lb24'=
    nonce (which is generated and localized to any user with block editor acce=
    ss via lb24_block_enqueue_scripts()) and does not verify the user's capabil= ities or that the supplied user_id belongs to the current user. This makes =
    it possible for authenticated attackers, with author-level access and above=
    , to overwrite the lb24_token, lb24_uid, lb24_refresh_token, and lb24_uname=
    user meta values of any user (including administrators) as well as the cor= responding site-wide options, effectively hijacking the plugin's integratio=
    n with the 24liveblog service. 2026-06-24 4.3 CVE-2026-9184 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-9184 ] ABB--Control Builder A Uncontrolled S= earch Path Element vulnerability in ABB Control Builder A, ABB 800xA for Ad= vant Master. This issue affects Control Builder A: through 1.4/4; 800xA for=
    Advant Master: through 6.0.3-1, through 6.1.1-1, 6.1.1-3, 6.2.0-1. 2026-06= -23 4.4 CVE-2025-13162 [ https://www.cve.org/CVERecord?id=3DCVE-2025-13162 =
    ] About Envato--BookPro Unauthenticated Insecure Direct Object References (= IDOR) in BookPro <=3D 1.1.0 versions. 2026-06-26 5.3 CVE-2025-66123 [ https= ://www.cve.org/CVERecord?id=3DCVE-2025-66123 ] Adobe--Acrobat Reader Acroba=
    t Reader versions 2020.009.20074, 2020.001.30002, 2017.011.30171, 2015.006.= 30523 and earlier are affected by an out-of-bounds read vulnerability that = could lead to disclosure of sensitive memory. An attacker could leverage th=
    is vulnerability to disclose sensitive information. Exploitation of this is= sue requires user interaction in that a victim must open a malicious file. = 2026-06-23 5.5 CVE-2020-9711 [ https://www.cve.org/CVERecord?id=3DCVE-2020-= 9711 ] Adobe--Acrobat Reader Adobe Acrobat and Reader versions 2020.009.200=
    74 and earlier, 2020.001.30002, 2017.011.30171 and earlier, and 2015.006.30= 523 and earlier are affected by an out-of-bounds read vulnerability that co= uld lead to disclosure of sensitive memory. An attacker could leverage this=
    vulnerability to disclose sensitive information. Exploitation of this issu=
    e requires user interaction in that a victim must open a malicious file. 20= 26-06-23 5.5 CVE-2020-9713 [ https://www.cve.org/CVERecord?id=3DCVE-2020-97=
    13 ] ailchev--SearchPlus The SearchPlus plugin for WordPress is vulnerable =
    to unauthorized modification and deletion of data in versions up to, and in= cluding, 1.7.1. This is due to a missing capability check and missing nonce=
    validation on the searchplus_save_token_action_callback() and searchplus_r= eset_token_action_callback() functions, both of which are exposed to unauth= enticated users through the wp_ajax_nopriv_ hooks. This makes it possible f=
    or unauthenticated attackers to overwrite or delete the plugin's stored acc= ount token and account name options (dym_token, dym_name, searchplus_token,=
    searchplus_name, sp_token, sp_name). 2026-06-24 5.3 CVE-2026-8617 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-8617 ] ajitdas--Devs Accounting Simpl=
    e Accounting and Invoicing Solution The Devs Accounting - Simple Accounting=
    and Invoicing Solution plugin for WordPress is vulnerable to unauthorized = modification/deletion of data due to a missing capability check on the dele= te_single_account() function in versions up to, and including, 1.2.0. The R= EST route 'devs-accounting/v1/delete-account/(?P<id>\d+)' is registered wit= hout any permission_callback, which causes WordPress to expose the endpoint=
    to public, unauthenticated access. This makes it possible for unauthentica= ted attackers to soft-delete arbitrary accounting account records (wp_dac_a= ccounts) by issuing a simple GET request to the endpoint with any account I=
    D. 2026-06-24 5.3 CVE-2026-9172 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-9172 ] ajitdas--Devs Accounting Simple Accounting and Invoicing Solution=
    The Devs Accounting - Simple Accounting and Invoicing Solution plugin for = WordPress is vulnerable to Missing Authorization in all versions up to, and=
    including, 1.2.0. This is due to the get_single_account() REST API callbac=
    k being registered with a permission_callback that unconditionally returns = true, providing no authentication or authorization checks on the /devs-acco= unting/v1/get-account/<id> endpoint. This makes it possible for unauthentic= ated attackers to read arbitrary private financial account records (includi=
    ng account name, bank name, and opening balance) by enumerating the numeric=
    account ID, resulting in sensitive information disclosure. 2026-06-24 5.3 = CVE-2026-9175 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9175 ] AKIN Sof= tware Computer Import Export Industry and Trade Ltd.--e-Commerce Improper n= eutralization of input during web page generation ('cross-site scripting') = vulnerability in AKIN Software Computer Import Export Industry and Trade Lt=
    d. E-Commerce allows Reflected XSS. This issue affects e-Commerce: before 1= .25.01.06. 2026-06-23 6.1 CVE-2026-10857 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-10857 ] Alps Electric Co., Ltd.--Remote Keyless Entry System (R= KES) R53R0 Remote Keyless Entry System (RKES), using the 433 MHz key fob be= aring FCC ID CWTR53R0 manufactured by ALPS ALPINE CO., LTD., is vulnerable =
    to a roll-back attack against its rolling-code authentication.=C2=A0 An att= acker within RF range who records two consecutive lock or unlock transmissi= ons from a legitimate key fob can later replay the same pair of transmissio=
    ns repeatedly. During testing, replaying the first captured transmission ca= used the RKES to enter a state in which replaying the second captured trans= mission resulted in a successful lock or unlock operation of the vehicle. T= ested and confirmed on=C2=A0a 2024 Suzuki Swift (SWIFT ISG GLS AC 1.2 5P 4x=
    2 TM). 2026-06-25 6.5 CVE-2026-49319 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-49319 ] alsa-project--alsa-lib The Advanced Linux Sound Architectur=
    e (ALSA) library before 1.2.16.1 contains a double-free vulnerability in pa= rse_def() in src/conf.c that allows attackers to corrupt memory by supplyin=
    g maliciously crafted ALSA configuration text. When parsing nested compound=
    or array configuration blocks, parse_def() fails to check return values be= fore continuing, causing snd_config_delete() to be called twice on the same=
    already-freed node, resulting in a NULL-pointer write or invalid memory re= ad. 2026-06-22 6.8 CVE-2026-56109 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-56109 ] antlr--ANTLR4 A security vulnerability has been detected in an= tlr ANTLR4 up to 4.13.2. Affected by this vulnerability is the function GoT= arget of the file tool/src/org/antlr/v4/codegen/target/GoTarget.java of the=
    component gofmt. The manipulation leads to command injection. The attack c=
    an only be performed from a local environment. The exploit has been disclos=
    ed publicly and may be used. The vendor was contacted early about this disc= losure but did not respond in any way. 2026-06-28 5.3 CVE-2026-13501 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-13501 ] antlr--ANTLR4 A vulnerabili=
    ty was detected in antlr ANTLR4 up to 4.13.2. Affected by this issue is the=
    function getImportedVocabFile of the file tool/src/org/antlr/v4/parse/Toke= nVocabParser.java of the component tokenVocab Grammar Option Handler. The m= anipulation results in path traversal. The attack can be executed remotely.=
    The exploit is now public and may be used. The vendor was contacted early = about this disclosure but did not respond in any way. 2026-06-28 5.3 CVE-20= 26-13503 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13503 ] antlr--ANTLR=
    4 A flaw has been found in antlr ANTLR4 up to 4.13.2. This affects the func= tion ObjectInputStream.readObject of the file antlr4-maven-plugin/src/main/= java/org/antlr/mojo/antlr4/GrammarDependencies.java of the component Maven = Plugin. This manipulation causes time-of-check time-of-use. The attack is r= estricted to local execution. A high degree of complexity is needed for the=
    attack. It is indicated that the exploitability is difficult. The exploit = has been published and may be used. The vendor was contacted early about th=
    is disclosure but did not respond in any way. 2026-06-28 4.5 CVE-2026-13502=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-13502 ] Arraytics--WPCafe Su= bscriber Broken Access Control in WPCafe <=3D 3.0.14 versions. 2026-06-26 4=
    .3 CVE-2026-57622 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57622 ] Art= ifexSoftware--mupdf MuPDF before 1.27.0-rc1 contains an uncontrolled recurs= ion vulnerability in the EPUB CSS rendering engine that allows remote attac= kers to cause a denial of service by supplying a maliciously crafted EPUB f= ile with deeply nested HTML elements and inline CSS styles. The function va= lue_from_inheritable_property() in css-apply.c recurses through the CSS pro= perty inheritance chain without a depth limit, exhausting the process stack=
    and causing a crash in any application using MuPDF for EPUB rendering. 202= 6-06-23 6.5 CVE-2025-71382 [ https://www.cve.org/CVERecord?id=3DCVE-2025-71= 382 ] assistioai--Assistio The Assistio plugin for WordPress is vulnerable =
    to unauthorized modification of data due to a missing capability check and = missing nonce verification on the assistio_plugin_delete_assistio_settings(=
    ) function in versions up to, and including, 1.1.2. This makes it possible = for authenticated attackers, with Subscriber-level access and above, to del= ete the plugin's options including the critical 'assistiobot_oauth_settings=
    ' option, which disrupts the plugin's integration with the Assistio bot ser= vice. 2026-06-24 4.3 CVE-2026-8614 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-8614 ] authlib--authlib Authlib is a Python library which builds OAut=
    h and OpenID Connect servers. Prior to 1.6.10 and 1.7.1, Authlib's OAuth 2.=
    0 authorization endpoint can be turned into an unauthenticated open redirec=
    t when a request uses an unsupported response_type and supplies an attacker= -controlled redirect_uri. The vulnerable behavior happens before client loo= kup and before any redirect URI validation. As a result, an attacker does n=
    ot need a valid client registration, an authenticated user, or any prior st= ate. A single request to the authorization endpoint is enough to obtain a 3=
    02 Location response to an arbitrary attacker-controlled URL. This vulnerab= ility is fixed in 1.6.10 and 1.7.1. 2026-06-22 5.4 CVE-2026-41479 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-41479 ] bdthemes--Live Copy Paste for = Elementor Contributor Broken Access Control in Live Copy Paste for Elemento=
    r <=3D 1.5.3 versions. 2026-06-26 4.3 CVE-2025-63079 [ https://www.cve.org/= CVERecord?id=3DCVE-2025-63079 ] berfect--Reviews and Rating Docplanner The = Reviews and Rating - Docplanner plugin for WordPress is vulnerable to autho= rization bypass in all versions up to, and including, 1.1.4. This is due to=
    the plugin not properly verifying that a user is authorized to perform an = action. This makes it possible for authenticated attackers, with subscriber= -level access and above, to trigger outbound scraping of external websites = and write scraped review data into the wp_dp_reviews database table, as wel=
    l as send feature-request emails from the site administrator's email addres=
    s. 2026-06-24 4.3 CVE-2026-9619 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-9619 ] bitwarden--server Bitwarden Server before 2026.5.0 contains a bro= ken access control vulnerability that allows any authenticated user to acce=
    ss arbitrary organization billing data by supplying an arbitrary organizati= onId to the PreviewInvoiceController endpoints without membership or author= ization checks. Attackers can exploit the missing ManageOrganizationBilling= Requirement on the preview invoice endpoints to retrieve Stripe-computed ta=
    x totals, subscription status, and billing details derived from any target = organization's real customer and subscription data. 2026-06-25 4.3 CVE-2026= -57521 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57521 ] BlockArt--Maga= zine Blocks Contributor Cross Site Scripting (XSS) in Magazine Blocks <=3D = 1.8.3 versions. 2026-06-26 6.5 CVE-2026-57650 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-57650 ] bPlugins--Flash & HTML5 Video Unauthenticated Brok=
    en Access Control in Flash & HTML5 Video <=3D 2.11.0 versions. 2026-06-26 5=
    .8 CVE-2026-57323 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57323 ] Cac= ti--cacti Cacti is an open source performance and fault management framewor=
    k. Versions 1.2.30 and prior are vulnerable to Open Redirect through a subs= tring check rather than a host check at str_contains($referer, CACTI_PATH_U= RL). When the user's login_opts =3D=3D '1' (redirect to referer after login=
    ), the function used $_SERVER['HTTP_REFERER'] directly. An attacker could c= raft a referer such as https://evil.com/cacti/. Where CACTI_PATH_URL is /ca= cti/, the substring matches and the user is redirected to evil.com after lo= gin. The pre-existing validate_redirect_url() helper at lib/html_utility.ph=
    p performed proper validation but was not invoked from auth_login_redirect(=
    ). This issue has been fixed in version 1.2.31. 2026-06-25 6.1 CVE-2026-400=
    80 [ https://www.cve.org/CVERecord?id=3DCVE-2026-40080 ] Cacti--cacti Cacti=
    is an open source performance and fault management framework. Versions 1.2= .30 and prior are vulnerable to Path Traversal through the Report format_fi=
    le Parameter, causing arbitrary file read. This vulnerability occurs in two=
    stages. In the first stage (stored injection), lib/html_reports.php at lin=
    e 283 stores $save['format_file'] =3D $post['format_file'] directly into th=
    e database without any validation. In the second stage (file read), lib/rep= orts.php at line 667 concatenates CACTI_PATH_FORMATS . '/' . $format_file, = and line 670 then calls file($format_file), reading arbitrary files from th=
    e filesystem. This issue has been fixed in version 1.2.31. 2026-06-25 6.5 C= VE-2026-40084 [ https://www.cve.org/CVERecord?id=3DCVE-2026-40084 ] Cacti--= cacti Cacti is an open source performance and fault management framework. V= ersions 1.2.30 and prior have missing session_regenerate_id() after login, = leading to Session Fixation. session_regenerate_id() is NOT called after su= ccessful login. The login flow at auth_login.php:203-207 directly sets $_SE= SSION[SESS_USER_ID] without rotating the session ID. The session cookie con= figuration is otherwise good (httponly=3Dtrue, samesite=3DStrict, secure=3D= true for HTTPS at include/global.php:513-537), but these do not prevent ses= sion fixation via same-site vectors. This issue has been fixed in version 1= .2.31. 2026-06-25 5.4 CVE-2026-40082 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-40082 ] caddyserver--caddy Caddy is an extensible server platform t= hat uses TLS by default. From 2.4.0 until 2.11.3, the authorization layer a=
    nd the /config traversal layer do not agree on what object the path refers = to. In this case, a path authorized for one config object is accepted, but = then resolves to a different config object during traversal. This happens b= ecause the authorization layer uses string prefix matching and the /config = traversal layer parses array indices numerically using strconv.Atoi(). This=
    vulnerability is fixed in 2.11.3. 2026-06-23 5.4 CVE-2026-45692 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-45692 ] caddyserver--caddy Caddy is an = extensible server platform that uses TLS by default. Prior to 2.11.4, Caddy=
    's stripHTML template function cannot reliably remove all HTML tags from in= put strings. Certain malformed HTML, such as <<>img src=3Dx onerror=3Dalert= ()>, can bypass the tag-stripping logic, potentially leaving dangerous cont= ent in the output if it is later rendered as HTML. This may allow client-si=
    de XSS in cases where untrusted strings are rendered unsafely. This vulnera= bility is fixed in 2.11.4. 2026-06-23 4.2 CVE-2026-52846 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-52846 ] Canonical--LXD Nil-pointer dereference =
    in CreateCustomVolumeFromBackup in LXD up to version 6.8 and 5.21 on Linux = allows an authenticated user with can_create_storage_volumes permissions to=
    cause a denial of service via a specially crafted custom-volume backup tar= ball that omits the expires_at snapshot field. 2026-06-26 6.5 CVE-2026-9639=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-9639 ] Canonical--lxd In Can= onical LXD versions 4.12 through 6.9, a Server-Side Request Forgery (SSRF) = vulnerability in the image import functionality allows authenticated users = with the can_create_images entitlement to interact with internal network in= frastructure via the /images endpoint. When importing an image from a URL s= ource, the LXD daemon fails to validate or restrict outbound destination IP=
    addresses, allowing connections to loopback, RFC1918 private ranges, and c= loud metadata endpoints. This enables error-based port scanning and unautho= rized interaction with internal HTTP services from the daemon's network pos= ition. 2026-06-26 5 CVE-2026-28385 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-28385 ] Cap-go--capgo Cap-go before 12.128.2 contains multiple SQL in= jection vulnerabilities in cloudflare.ts where user-controlled values from = API request bodies are interpolated directly into SQL query strings without=
    sanitization or parameterization. Authenticated users with read-level API = key permissions can inject arbitrary SQL through deviceIds, search, version= _name, cursor, and actions parameters to access analytics data belonging to=
    other users or applications. 2026-06-22 6.5 CVE-2026-56221 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-56221 ] Cap-go--capgo Cap-go before 12.128.2=
    contains an authorization bypass vulnerability in the GET /organization/me= mbers endpoint that allows org-limited API keys to bypass limited_to_orgs r= estrictions. Attackers with org-limited API keys can read membership data i= ncluding uid, email, image_url, role, and is_tmp from organizations outside=
    their assigned scope. 2026-06-24 4.3 CVE-2026-56310 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-56310 ] Capgo--Capgo Capgo before 12.128.2 contains=
    an unsecured images bucket lacking any row level security controls, allowi=
    ng unauthenticated attackers to read, insert, and delete stored app icons. = Remote attackers can exploit this misconfiguration to delete all icons and = leak sensitive app IDs and user IDs. 2026-06-24 6.5 CVE-2026-56302 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-56302 ] Capgo--Capgo Capgo before 12.= 128.2 contains a weak parsing vulnerability in the x-limited-key-id header = that allows attackers to bypass subkey enforcement by submitting malformed = values, zero, or duplicate headers that result in NaN or falsy values. Remo=
    te attackers can manipulate the x-limited-key-id header to disable limited = key scoping and execute requests using the main API key context instead of = restricted subkey permissions. 2026-06-22 6.4 CVE-2026-56306 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-56306 ] Capgo--Capgo Capgo before 12.128.2 = contains a credential validation vulnerability in the POST /functions/v1/pr= ivate/validate_password_compliance endpoint that is callable using only the=
    public Supabase key without authentication. The endpoint is CORS-permissiv=
    e with wildcard origin allowance and lacks rate limiting, enabling attacker=
    s to perform password spraying and credential stuffing attacks to compromis=
    e user accounts. 2026-06-23 5.3 CVE-2026-56234 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-56234 ] Capgo--Capgo Capgo before 12.128.2 contains an au= thorization bypass vulnerability in the public.get_current_plan_max_org RPC=
    function that allows unauthenticated attackers to retrieve arbitrary organ= ization plan limits. Attackers can call the RPC endpoint with any organizat= ion UUID using only the public Supabase key to disclose billing information=
    including MAU, bandwidth, storage, and build time limits for any organizat= ion. 2026-06-22 5.3 CVE-2026-56311 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-56311 ] Capgo--Capgo Capgo (backend Supabase edge functions) before 1= 2.128.2 does not apply the global authentication middleware to the GET /pri= vate/role_bindings/:org_id endpoint, unlike the POST and DELETE role_bindin=
    gs routes, so unauthenticated requests reach the handler instead of being r= ejected at the middleware layer. The handler still performs its own authori= zation check and returns Unauthorized, so no direct data exposure occurs; t=
    he flaw is inconsistent authentication enforcement across HTTP methods that=
    could enable authorization bypass if the handler logic changes. 2026-06-22=
    5.3 CVE-2026-56321 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56321 ] C= apgo--Capgo Capgo before 12.128.2 contains an information disclosure vulner= ability in the public.exist_app_v2 RPC function that allows unauthenticated=
    attackers to enumerate app_ids by calling POST /rest/v1/rpc/exist_app_v2 w= ith arbitrary appid parameters. Remote attackers can exploit this SECURITY = DEFINER function to determine whether specific app_ids exist in the public.= apps table, enabling cross-tenant app enumeration and privacy violations. 2= 026-06-24 5.3 CVE-2026-56337 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 56337 ] Capgo--Capgo Capgo before 12.128.2 contains a denial of service vul= nerability in the /auth/v1/otp endpoint that prevents email verification fo=
    r two-factor authentication due to captcha validation failures. Authenticat=
    ed users cannot complete 2FA enrollment as the backend consistently returns=
    HTTP 500 errors with captcha verification process failed messages, blockin=
    g access to security controls. 2026-06-24 5.3 CVE-2026-56338 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-56338 ] Capgo--Capgo Capgo before 12.128.2 = contains a denial of service vulnerability in the POST /app/demo endpoint t= hat allows authenticated users with org write permissions to create unlimit=
    ed demo applications without rate limiting or quota enforcement. Attackers = can repeatedly invoke this endpoint to generate approximately 138 database = write operations per request, causing degraded performance, increased costs=
    , and potential service instability. 2026-06-22 4.3 CVE-2026-56255 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-56255 ] Chris Carlevato--utm.codes Su= bscriber Server Side Request Forgery (SSRF) in utm.codes <=3D 1.9.0 version=
    s. 2026-06-26 6.4 CVE-2026-56026 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-56026 ] ChromeDevTools--chrome-devtools-mcp Chrome DevTools for agents = (chrome-devtools-mcp) lets your coding agent control and inspect a live Chr= ome browser. From 0.20.0 until 1.1.0, The chrome-devtools-mcp daemon writes=
    its PID file with fs.writeFileSync() to a deterministic runtime path. On t= ypical macOS environments, and on Linux sessions where $XDG_RUNTIME_DIR is = unset, that runtime path falls back to /tmp/chrome-devtools-mcp-<uid>/daemo= n.pid. Because the write does not use O_NOFOLLOW, a local low-privilege use=
    r on the same POSIX host can pre-create /tmp/chrome-devtools-mcp-<victim_ui= d>/daemon.pid as a symlink to a file writable by the victim. When the victi=
    m later starts daemon mode, fs.writeFileSync() follows the symlink and trun= cates the target file to the daemon PID string. This vulnerability is fixed=
    in 1.1.0. 2026-06-24 6.1 CVE-2026-53765 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53765 ] ChromeDevTools--chrome-devtools-mcp Chrome DevTools for=
    agents (chrome-devtools-mcp) lets your coding agent control and inspect a = live Chrome browser. From 0.24.0 until 1.1.0, McpContext.validatePath() enf= orces workspace roots by checking whether path.resolve(filePath) textually = falls under one of the configured root paths. path.resolve() does not canon= icalize symbolic links. As a result, a symlink inside a configured workspac=
    e root can point to a file outside that root, pass validation, and then be = followed by downstream file read/write operations. This bypass applies even=
    when the MCP client correctly declares the roots capability with a non-emp=
    ty list. It is separate from the documented legacy behavior where missing r= oots capability allows all paths. The practical impact is a workspace-bound= ary bypass. In the write direction, filePath-writing tools can overwrite ou= t-of-root files through an in-root symlink. In the read direction, upload_f= ile can read through the symlink and send the file to the currently selecte=
    d web page. This vulnerability is fixed in 1.1.0. 2026-06-24 6.1 CVE-2026-5= 3766 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53766 ] chuhpl--Book a R= oom Event Calendar The Book a Room Event Calendar plugin for WordPress is v= ulnerable to Cross-Site Request Forgery in all versions up to, and includin=
    g, 1.9. This is due to missing or incorrect nonce validation on the setting= s_form()/update_settings() functionality. The plugin's options page handler=
    dispatches on the 'action' POST parameter and calls update_settings(), whi=
    ch persists plugin configuration (including the external database host, use= rname, password, prefix, database name, encryption key, and registration pa=
    ge URL) via update_option(), without ever generating a nonce field in the s= ettings form or verifying one (no wp_nonce_field(), check_admin_referer(), =
    or wp_verify_nonce() exists anywhere in the plugin). This makes it possible=
    for unauthenticated attackers to modify the plugin's database connection s= ettings via a forged request granted they can trick a site administrator in=
    to performing an action such as clicking on a link. 2026-06-24 4.3 CVE-2026= -9721 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9721 ] Code Amp--Forget=
    About Shortcode Buttons Contributor Broken Access Control in Forget About = Shortcode Buttons <=3D 2.1.3 versions. 2026-06-26 5.4 CVE-2025-63041 [ http= s://www.cve.org/CVERecord?id=3DCVE-2025-63041 ] codepeople--CodePeople Post=
    Map for Google Maps The CodePeople Post Map for Google Maps plugin for Wor= dPress is vulnerable to Stored Cross-Site Scripting via 'cpm_point' Post Me=
    ta in all versions up to, and including, 1.2.6 due to insufficient input sa= nitization and output escaping. This makes it possible for authenticated at= tackers, with Contributor-level access and above, to inject arbitrary web s= cripts in pages that will execute whenever a user accesses an injected page=
    . 2026-06-27 6.4 CVE-2026-13335 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-13335 ] Contempoinc--Real Estate 7 Unauthenticated Cross Site Request Fo= rgery (CSRF) in Real Estate 7 <=3D 3.5.9 versions. 2026-06-26 6.5 CVE-2026-= 57641 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57641 ] Crawl4AI--Crawl= 4AI Crawl4AI before 0.8.7 contains an authentication bypass vulnerability i=
    n the monitor router endpoints that allows unauthenticated attackers to acc= ess destructive operations. Remote attackers can invoke the /monitor/action= s/cleanup endpoint and manipulate monitoring state without authentication, = causing service disruption. 2026-06-24 6.5 CVE-2026-56262 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-56262 ] Crawl4AI--Crawl4AI Crawl4AI before 0.8=
    .7 contains a stored cross-site scripting vulnerability in the monitor dash= board that renders crawl URLs and error messages via innerHTML without esca= ping. An attacker can submit a crafted crawl request with malicious markup = that executes in an operator's browser when viewing the dashboard. 2026-06-=
    23 6.1 CVE-2026-56263 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56263 ]=
    Creative Themes--Blocksy Companion Pro Unauthenticated Insecure Direct Obj= ect References (IDOR) in Blocksy Companion Pro <=3D 2.1.46 versions. 2026-0= 6-26 5.3 CVE-2026-57630 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57630=
    ] CridioStudio--ListingPro Subscriber Cross Site Scripting (XSS) in Listin= gPro <=3D 2.9.11 versions. 2026-06-26 6.5 CVE-2026-56046 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-56046 ] danny-avila--LibreChat LibreChat is an = enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.4-= rc1, the fix for CVE-2024-11171 (commit bb58a2d0) added limits: { fileSize =
    } to createMulterInstance() in the file upload routes. However, the POST /a= pi/convos/import endpoint uses a separate multer instance that was never up= dated with the same limits configuration. Combined with the application-lev=
    el size check being disabled by default (the CONVERSATION_IMPORT_MAX_FILE_S= IZE_BYTES env var is commented out in .env.example), an authenticated user = can upload arbitrarily large files to exhaust server disk space and memory.=
    This vulnerability is fixed in 0.8.4-rc1. 2026-06-25 6.5 CVE-2026-54024 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-54024 ] danny-avila--LibreChat = LibreChat is an enhanced ChatGPT clone that supports multiple AI providers.=
    Prior to 0.8.4-rc1, the POST /api/files/images endpoint allows any authent= icated user to upload files into any agent's tool_resources (e.g., context,=
    execute_code) without verifying ownership or EDIT permission on the target=
    agent. A permission check was added to the POST /api/files route in a prev= ious patch, but the image upload route was never updated with the same chec=
    k. An attacker can simply use the image endpoint instead of the file endpoi=
    nt to bypass the authorization entirely. This vulnerability is fixed in 0.8= .4-rc1. 2026-06-25 6.5 CVE-2026-54027 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-54027 ] danny-avila--LibreChat LibreChat is an enhanced ChatGPT cl= one that supports multiple AI providers. Prior to 0.8.4-rc1, the fix for CV= E-2025-7105 added forkIpLimiter and forkUserLimiter rate limiters to POST /= api/convos/fork to prevent rapid-fire conversation duplication. However, th=
    e POST /api/convos/duplicate endpoint - which is in the same file and perfo= rms the exact same expensive database operations - was not given any rate l= imiter. An authenticated user can bypass the CVE-2025-7105 fix by using /du= plicate instead of /fork to exhaust server resources. This vulnerability is=
    fixed in 0.8.4-rc1. 2026-06-25 6.5 CVE-2026-54037 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-54037 ] danny-avila--LibreChat LibreChat is an enhanc=
    ed ChatGPT clone that supports multiple AI providers. Prior to 0.8.4-rc1, t= here is a vulnerability in LibreChat's markdown artifact preview pipeline. = The marked library v15.0.12 does not HTML-escape double-quote characters in=
    image alt text when a custom renderer falls through to the default rendere=
    r. LibreChat's generateMarkdownHtml function (in client/src/utils/markdown.= ts) installs a custom image renderer that returns false for URLs passing th=
    e isSafeUrl allowlist check, which causes marked to fall back to its built-=
    in renderer. That built-in renderer inserts the raw alt text into the alt= =3D"..." attribute without escaping double-quote characters. An attacker ca=
    n craft an alt text such as " onload=3D"payload to break out of the attribu=
    te and inject an arbitrary event handler. The resulting HTML is then assign=
    ed to document.getElementById('content').innerHTML inside the Sandpack prev= iew iframe, causing the payload to execute in the victim's browser. This vu= lnerability is fixed in 0.8.4-rc1. 2026-06-25 5.4 CVE-2026-54025 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-54025 ] danny-avila--LibreChat LibreCha=
    t is an enhanced ChatGPT clone that supports multiple AI providers. Prior t=
    o 0.8.4-rc1, the DELETE /api/messages/:conversationId/:messageId endpoint a= llows any authenticated user to delete any other user's messages. The valid= ateMessageReq middleware only validates that the conversationId belongs to = the requesting user, but the handler calls deleteMessages({ messageId }) us= ing only the messageId as the MongoDB filter - without adding a user constr= aint. An attacker provides their own valid conversationId (to pass validati= on) and the victim's messageId (to target deletion), resulting in permanent=
    , irrecoverable message deletion. This vulnerability is fixed in 0.8.4-rc1.=
    2026-06-25 5.3 CVE-2026-54029 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-54029 ] danny-avila--LibreChat LibreChat is an enhanced ChatGPT clone tha=
    t supports multiple AI providers. Prior to 0.8.4-rc1, the GET /api/auth/2fa= /enable endpoint can be called by an authenticated user (or attacker with a=
    stolen session) even when 2FA is already fully enabled on the account. Thi=
    s endpoint overwrites the existing TOTP secret, generates new backup codes,=
    and sets twoFactorEnabled to false - all without requiring any TOTP or bac= kup code verification. An attacker with a valid session token can completel=
    y take over a victim's 2FA, locking the legitimate user out of their own tw= o-factor authentication. This vulnerability is fixed in 0.8.4-rc1. 2026-06-=
    25 5.3 CVE-2026-54036 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54036 ]=
    danny-avila--LibreChat LibreChat is an enhanced ChatGPT clone that support=
    s multiple AI providers. Prior to 0.8.4-rc1, the POST /api/auth/2fa/backup/= regenerate endpoint regenerates all 2FA backup codes without requiring any = TOTP token or existing backup code verification. An attacker with a stolen = session token can silently replace a victim's backup codes and use them to = bypass 2FA login or disable 2FA entirely. This vulnerability is fixed in 0.= 8.4-rc1. 2026-06-25 5.9 CVE-2026-54040 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54040 ] Databend--Databend A vulnerability was identified in Da= tabend up to 1.2.881 on HTTP. This affects the function ClientSessionManage= r::state_key of the file src/query/service/src/servers/http/v1/session/clie= nt_session_manager.rs of the component Tenant Handler. The manipulation lea=
    ds to authorization bypass. It is possible to initiate the attack remotely.=
    The exploit is publicly available and might be used. The pull request to f=
    ix this issue awaits acceptance. 2026-06-28 6.3 CVE-2026-13512 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-13512 ] daytonaio--daytona Daytona is a s= ecure and elastic infrastructure runtime for AI-generated code execution an=
    d agent workflows. Prior to 0.185.0, a cross-tenant authorization flaw in D= aytona's notification WebSocket gateway allowed any authenticated user to s= ubscribe to another organization's realtime notification channel and passiv= ely receive that organization's events. This vulnerability is fixed in 0.18= 5.0. 2026-06-23 6.5 CVE-2026-54324 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-54324 ] daytonaio--daytona Daytona is a secure and elastic infrastruc= ture runtime for AI-generated code execution and agent workflows. Prior to = 0.185.0, the daemon's git clone implementation disabled TLS certificate ver= ification. When a clone request carried Git credentials, the daemon sent th=
    e HTTP Basic Authorization header to the remote over a connection whose cer= tificate was never validated, on both the go-git and native git CLI code pa= ths. An attacker able to intercept clone traffic could present any TLS cert= ificate, capture the Git credentials supplied for the clone, and serve tamp= ered repository content into the sandbox. This vulnerability is fixed in 0.= 185.0. 2026-06-23 5.9 CVE-2026-54323 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-54323 ] daytonaio--daytona Daytona is a secure and elastic infrastr= ucture runtime for AI-generated code execution and agent workflows. Prior t=
    o 0.186, a sandbox volume reference (volumeId, which may also be a volume n= ame) was forwarded to the runner and used to build the host bind-mount sour=
    ce path without confinement. A reference containing path-traversal sequence=
    s could in principle resolve the mount source outside the intended per-volu=
    me base directory. This vulnerability is fixed in 0.186. 2026-06-23 4.2 CVE= -2026-54319 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54319 ] Dell--Dis= play and Peripheral Manager Dell Display and Peripheral Manager (DDPM Mac),=
    versions prior to 2.3, contain a Concurrent Execution using Shared Resourc=
    e with Improper Synchronization ('Race Condition') vulnerability. A low-pri= vileged attacker with local access could potentially exploit this vulnerabi= lity, leading to Elevation of Privileges. 2026-06-25 6.7 CVE-2026-46732 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-46732 ] Dell--Wyse Management Su= ite (WMS) Dell Wyse Management Suite (WMS), versions prior to WMS 2605, con= tain a Use of Default Credentials vulnerability. A high privileged attacker=
    with local access could potentially exploit this vulnerability, leading to=
    Information Disclosure. 2026-06-22 6 CVE-2026-44273 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-44273 ] denoland--deno Deno is a JavaScript, TypeSc= ript, and WebAssembly runtime. Prior to 2.8.0, the Node.js compatibility TC=
    P path checked the permission against the original hostname string before r= esolution and then did not re-check after resolution. A caller could theref= ore pass a numeric alias of an IP address (for example the decimal integer = 2130706433 or the hex form 0x7f000001, both of which resolve to 127.0.0.1) = and reach the denied destination through node:net.connect or node:http.requ= est's { host, port } options form. This vulnerability is fixed in 2.8.0. 20= 26-06-23 6.5 CVE-2026-49411 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 9411 ] denoland--deno Deno is a JavaScript, TypeScript, and WebAssembly run= time. Prior to 2.7.12, when Deno was run in BYONM mode (nodeModulesDir: "ma= nual"), the module resolver did not validate that a package's resolved entr= ypoint stayed within its node_modules/<pkg>/ directory. A malicious package= .json whose main field contained .. segments was able to resolve to an arbi= trary path on disk, and the resolver then read that file without consulting=
    the --allow-read allowlist. This let a require("evil-pkg") call return the=
    contents of a file that a direct Deno.readTextFileSync(...) call would hav=
    e been blocked from reading. This vulnerability is fixed in 2.7.12. 2026-06= -23 5.5 CVE-2026-49406 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49406 =
    ] denoland--deno Deno is a JavaScript, TypeScript, and WebAssembly runtime.=
    Prior to 2.8.1, when fetch() was called, Deno checked the destination host= name against --deny-net rules but did not re-check the IP addresses that ho= stname resolved to. An attacker-controlled script could use a specially cra= fted domain name that passes the hostname check yet resolves to a denied IP=
    , bypassing the network restriction entirely. This vulnerability is fixed i=
    n 2.8.1. 2026-06-23 5.2 CVE-2026-49859 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-49859 ] denoland--deno Deno is a JavaScript, TypeScript, and We= bAssembly runtime. Prior to 2.8.1, when a WebSocket connection was opened, = Deno checked the destination hostname against --deny-net rules but did not = re-check the IP addresses that hostname resolved to. An attacker-controlled=
    script could use a specially crafted domain name that passes the hostname = check yet resolves to a denied IP, bypassing the network restriction entire= ly. This vulnerability is fixed in 2.8.1. 2026-06-23 5.2 CVE-2026-49860 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-49860 ] denoland--deno Deno is a=
    JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8.1, environme=
    nt access is gated by the env permission. You can deny it with --deny-env, =
    or restrict it to a specific allowlist with --allow-env=3DFOO,BAR. The expe= ctation is that a program running without env permission cannot change proc= ess.env. process.loadEnvFile() (the Node-compatible API for loading variabl=
    es from a .env file) does not honor this. It only checks that the program h=
    as read permission for the dotenv file, then writes every key in that file = into the process environment - even when env access is denied. In effect, -= -allow-read plus a writable or attacker-controlled .env file is enough to d= efeat --deny-env. This vulnerability is fixed in 2.8.1. 2026-06-23 5.2 CVE-= 2026-49983 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49983 ] denoland--= deno Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.= 7.5, a Deno program that opens a client WebSocket connection could be crash=
    ed by the remote server. While handling the WebSocket handshake response, D= eno parsed the Sec-WebSocket-Protocol and Sec-WebSocket-Extensions response=
    headers in a way that assumed their bytes were always printable ASCII. A r= esponse header containing non-visible-ASCII bytes (0x80-0xFF) caused a pani=
    c that aborted the entire Deno process. This vulnerability is fixed in 2.7.=
    5. 2026-06-23 4.3 CVE-2026-55517 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-55517 ] Digiwin--EasyFlow .NET EasyFlow .NET developed by Digiwin has a=
    Stored Cross-Site Scripting vulnerability, allowing authenticated remote a= ttackers to inject persistent JavaScript code executed in users' browsers u= pon page load. 2026-06-22 5.4 CVE-2026-12580 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-12580 ] docling-project--docling Docling simplifies documen=
    t processing by parsing diverse formats and providing integrations with the=
    generative AI ecosystem. From 2.45.0 until 2.91.0, the METS-GBS backend's = XML parsing and the input document format detection lacked security control=
    s. An attacker could craft malicious METS-GBS archives that, when processed=
    , could read sensitive files, exhaust system resources, or cause applicatio=
    n crashes. This vulnerability is fixed in 2.91.0. 2026-06-26 5.5 CVE-2026-4= 4018 [ https://www.cve.org/CVERecord?id=3DCVE-2026-44018 ] docling-project-= -docling Docling simplifies document processing by parsing diverse formats = and providing integrations with the generative AI ecosystem. From 2.73.0 un= til 2.91.0, he LaTeX backend's handling of \includegraphics, \input, and \i= nclude commands lacked path containment validation. Attackers could craft m= alicious LaTeX documents with path traversal sequences to read arbitrary fi= les from the file system accessible to the process, include sensitive files=
    in the converted document output, or potentially access configuration file=
    s, credentials, or other sensitive data This vulnerability is fixed in 2.91= .0. 2026-06-24 5.5 CVE-2026-44022 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-44022 ] dokaninc--Dokan: AI Powered WooCommerce Multivendor Marketplac=
    e Solution Build Your Own Amazon, eBay, Etsy The Dokan: AI Powered WooComme= rce Multivendor Marketplace Solution - Build Your Own Amazon, eBay, Etsy pl= ugin for WordPress is vulnerable to Stored Cross-Site Scripting via Product=
    SKU in all versions up to, and including, 5.0.4 due to insufficient input = sanitization and output escaping. This makes it possible for authenticated = attackers, with custom-level access and above, to inject arbitrary web scri= pts in pages that will execute whenever a user accesses an injected page. T=
    he malicious payload is delivered to site visitors - including unauthentica= ted users - when the store search widget inserts the unescaped AJAX respons=
    e HTML into the DOM via jQuery's .html() method. 2026-06-27 6.4 CVE-2026-11= 783 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11783 ] dokaninc--Dokan: =
    AI Powered WooCommerce Multivendor Marketplace Solution Build Your Own Amaz= on, eBay, Etsy The Dokan: AI Powered WooCommerce Multivendor Marketplace So= lution - Build Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerab=
    le to Insecure Direct Object Reference in all versions up to, and including=
    , 5.0.4 via the 'id' parameter due to missing validation on a user controll=
    ed key. This makes it possible for authenticated attackers, with subscriber= -level access and above, to read any other vendor's products - including un= published draft and pending listings - exposing product names, prices, SKUs=
    , and descriptions belonging to other vendors. The permission callbacks for=
    both the collection endpoint and the single-item endpoint only verify the = generic vendor capability ('dokan_view_product_menu' / 'dokandar'), which e= very vendor holds, rather than confirming the requested author ID or produc=
    t ownership matches the authenticated user. 2026-06-27 4.3 CVE-2026-11987 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-11987 ] dokku--dokku Dokku is =
    a docker-powered PaaS. Prior to 0.38.2, the git:auth command creates $DOKKU= _ROOT/.netrc using bash's touch command, which applies the default umask of=
    0644. This pre-creation defeats the netrc binary's built-in 0600 permissio=
    n setting, leaving git credentials readable by any local user who can trave= rse the dokku home directory. This vulnerability is fixed in 0.38.2. 2026-0= 6-26 5 CVE-2026-45407 [ https://www.cve.org/CVERecord?id=3DCVE-2026-45407 ]=
    dornaweb--Product Specifications for Woocommerce The Product Specification=
    s for WooCommerce plugin for WordPress is vulnerable to unauthorized modifi= cation, creation, and deletion of data in versions up to and including 0.8.=
    9. This is due to a missing capability check and missing nonce verification=
    in the __invoke() methods of the AttributeGroupController and AttributeCon= troller classes, which are bound to the 'dwps_modify_groups' and 'dwps_modi= fy_attributes' AJAX actions. This makes it possible for authenticated attac= kers, with Subscriber-level access and above, to create, edit, and delete a= rbitrary product specification groups and attributes (taxonomy terms in the=
    'spec-group' and attribute taxonomies), corrupting business data and impac= ting the site's frontend display. 2026-06-27 4.3 CVE-2026-11364 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-11364 ] Dynabook Inc.--Generic IO & Memo=
    ry Access driver Generic IO & Memory Access driver for PCs provided by TOSH= IBA CORPORATION and Dynabook Inc. exposes its IOCTL with insufficient acces=
    s control. A logged-in user with no administrative privilege may access phy= sical memory. 2026-06-25 5.5 CVE-2026-56129 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-56129 ] earendil-works--pi Pi is a minimal terminal coding h= arness. Pi before 0.79.0 loaded project-local configuration and resources f= rom a repository's .pi directory without first asking the user to trust tha=
    t repository. This included project-local extensions, which are executable = TypeScript or JavaScript modules loaded into the Pi process. An attacker wh=
    o controls a repository could place Pi-specific project resources in that r= epository. If a user then started Pi from that working tree, the project-lo= cal extension code could run with the same privileges as the local Pi proce=
    ss without the user having a convenient way to make a trust decision. This = vulnerability is fixed in 0.79.0. 2026-06-23 4.4 CVE-2026-54325 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-54325 ] Eclipse Foundation--Eclipse Open=
    VSX Open VSX Registry does not sanitize SVG files uploaded as extension ic= ons prior to storage, and serves them with Content-Type: image/svg+xml with= out security headers such as Content-Security-Policy or Content-Disposition=
    : attachment. This allows an attacker to publish an extension with a malici= ous SVG icon and achieve stored cross-site scripting (XSS) when a user navi= gates directly to the icon URL. On deployments using local storage, script = execution occurs within the Open VSX application origin, enabling session h= ijacking, authentication token theft, and unauthorized extension publishing=
    . On deployments backed by external storage (such as open-vsx.org with an S= 3-backed CDN), execution is confined to the storage origin, reducing impact=
    but still permitting phishing attacks and credential harvesting through at= tacker-crafted pages. 2026-06-23 4.1 CVE-2026-4983 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-4983 ] Elementor--Elementor Website Builder Contribut=
    or Sensitive Data Exposure in Elementor Website Builder <=3D 4.1.3 versions=
    . 2026-06-25 6.5 CVE-2026-57619 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-57619 ] eLightUp--Slim SEO Contributor Broken Access Control in Slim SEO=
    <=3D 4.6.2 versions. 2026-06-25 6.5 CVE-2026-57429 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-57429 ] envoyproxy--envoy Envoy is an open source ed=
    ge and service proxy designed for cloud-native applications. From 1.26.0 un= til 1.35.13, 1.36.9, 1.37.5, and 1.38.3, the envoy.filters.http.grpc_stats = filter crashes (null pointer dereference / segfault) when a Connect protoco=
    l request (Content-Type: application/connect+proto or application/connect+j= son) hits a direct_response route. A single unauthenticated HTTP request cr= ashes the Envoy process. This vulnerability is fixed in 1.35.13, 1.36.9, 1.= 37.5, and 1.38.3. 2026-06-26 6.5 CVE-2026-47204 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-47204 ] envoyproxy--envoy Envoy is an open source edge a=
    nd service proxy designed for cloud-native applications. From 1.34.0 until = 1.35.13, 1.36.9, 1.37.5, and 1.38.3, Envoy crashes if an ext_proc server se= nds a single gRPC message containing multiple, specially crafted Processing= Response messages. This can occur when the first response in the batch caus=
    es the gRPC stream object to be destroyed, leading to a use-after-free erro=
    r when Envoy attempts to process subsequent responses in the same gRPC mess= age. This vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3. 20= 26-06-26 6.5 CVE-2026-47207 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 7207 ] envoyproxy--envoy Envoy is an open source edge and service proxy des= igned for cloud-native applications. Prior to 1.35.11, 1.36.7, 1.37.3, and = 1.38.1, the OAuth2 HTTP filter's encrypt()/decrypt() functions use AES-256-= CBC without an authentication tag (no HMAC, no AEAD). The /callback endpoin=
    t returns HTTP 302 on successful decryption and HTTP 401 on padding failure=
    , creating a padding oracle. An attacker who obtains the encrypted CodeVeri= fier cookie can recover the plaintext PKCE code_verifier in ~6,200 requests=
    (~100 seconds), then exchange it with a stolen authorization code to obtai=
    n the victim's access token. This vulnerability is fixed in 1.35.11, 1.36.7=
    , 1.37.3, and 1.38.1. 2026-06-26 6.8 CVE-2026-47775 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-47775 ] envoyproxy--envoy Envoy is an open source ed=
    ge and service proxy designed for cloud-native applications. From 1.36.0 un= til 1.36.9, 1.37.5, and 1.38.3, a Use-After-Free (UAF) vulnerability leadin=
    g to a sudden segmentation fault exists in Envoy's ext_authz HTTP filter wh=
    en processing per-route authorization overrides concurrently with rapid dow= nstream client disconnects. During standard request lifecycles, Envoy insta= ntiates the ext_authz filter with a foundational authorization client objec=
    t (client_). If a matched route dictates a dynamic per-route HTTP or gRPC a= uthorization service override, the filter generates a localized client. In = the vulnerable implementation, this transient client aggressively overwrote=
    the default client_ unique pointer by executing client_ =3D std::move(per_= route_client). When a client rapidly establishes and subsequently tears dow=
    n a stream (such as rapidly refreshing a protected WebSocket endpoint), the=
    downstream triggers the ConnectionManagerImpl::doDeferredStreamDestroy() -=
    ActiveStream::onResetStream() lifecycle. Envoy immediately sequences Filt=
    er::onDestroy() in an attempt to securely abort dispatched asynchronous aut= horization check transactions via client_->cancel(). By destructing the def= ault client abruptly during initiateCall, a memory lifecycle misalignment o= ccurs within the async client manager. The stream teardown fails to reliabl=
    y track and cancel the dynamically bound asynchronous authorization tasks, = orchestrating a sequence where a late asynchronous callback from the networ=
    k evaluates against a heavily destroyed ActiveStream validation span, gener= ating a UAF process crash. This vulnerability is fixed in 1.36.9, 1.37.5, a=
    nd 1.38.3. 2026-06-26 5.9 CVE-2026-47205 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-47205 ] envoyproxy--envoy Envoy is an open source edge and serv= ice proxy designed for cloud-native applications. From 1.18.0 until 1.35.13=
    , 1.36.9, 1.37.5, and 1.38.3, the router filter contains a null pointer der= eference vulnerability when handling HTTP 303 (See Other) internal redirect=
    s for body-less non-GET/HEAD requests. When a POST, PUT, DELETE, or PATCH r= equest without a body is sent to a route configured with internal redirect = policy that includes 303 in redirect_response_codes, and the upstream respo= nds with HTTP 303, the redirect handling code attempts to drain a request b= ody buffer that was never allocated. This results in a segmentation fault t= hat crashes the entire Envoy process. When route configured with internal_r= edirect_policy including 303 in redirect_response_codes and upstream must r= eturn HTTP 303 response, an unauthenticated attacker can exploit this to ca= use complete denial of service, terminating all active connections. This vu= lnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3. 2026-06-26 5.9=
    CVE-2026-47221 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47221 ] envoy= proxy--envoy Envoy is an open source edge and service proxy designed for cl= oud-native applications. From 1.37.0 until 1.37.5 and 1.38.3, the HTTP OAut=
    h2 filter (envoy.filters.http.oauth2) can leave an in-flight async token ex= change attached to a downstream stream that has already been torn down. A l= ate AsyncClient completion can still invoke OAuth2Filter methods that use S= treamDecoderFilterCallbacks after that object's lifetime has ended, causing=
    undefined behavior, worker crashes (availability loss), and use-after-free=
    / invalid-vptr failures under AddressSanitizer. This is a memory-safety / = lifetime issue in the data plane, not a trivial config bug. Remote code exe= cution is not claimed here; the primary demonstrated impact is DoS via cras=
    h and UB; any further impact would be deployment- and allocator-dependent. = This vulnerability is fixed in 1.37.5 and 1.38.3. 2026-06-26 5.9 CVE-2026-4= 8090 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48090 ] envoyproxy--envo=
    y Envoy is an open source edge and service proxy designed for cloud-native = applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, in cases where = UDP DNS filter is configured with local resolution containing a name with t=
    he length of 255 octets or remote resolution for a name of 255 octets long = can complete successfully, a query with such name will result in abnormal p= rocess termination. The abnormal process termination is triggered by an inv= alid runtime precondition that the query name is strictly less than 255 oct= ets, contradicting DNS specification rfc1035#section-2.3.4 that the name ca=
    n be 255 or less octets. This vulnerability is fixed in 1.35.11, 1.36.7, 1.= 37.3, and 1.38.1. 2026-06-26 5.9 CVE-2026-48497 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-48497 ] envoyproxy--envoy Envoy is an open source edge a=
    nd service proxy designed for cloud-native applications. From 1.34.0 until = 1.35.13, 1.36.9, 1.37.5, and 1.38.3, a vulnerability exists in Envoy's TCP = StatsD sink (TcpStatsdSink), where the thread-local flusher buffer can be o= verflowed by exceptionally long statistic names (e.g., >16KiB). During form= atting, TcpStatsdSink reserves a single contiguous memory slice of 16KiB (F= LUSH_SLICE_SIZE_BYTES). If formatting a single metric exceeds the remaining=
    capacity, the flusher initiates a buffer rotation but incorrectly continue=
    s to allocate another fixed 16KiB slice. If an attacker can trigger a stati= stic name longer than 16KiB-for example, by sending an HTTP or gRPC request=
    with an extremely long request path (:path) that is recorded by the grpc_s= tats filter configured with stats_for_all_methods: true-the flusher will at= tempt to copy the metric name using memcpy operations beyond the allocated = heap buffer boundaries. This leads to a heap write overflow, which can caus=
    e immediate denial-of-service (process crash) or potential remote code exec= ution (RCE). This vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.= 38.3. 2026-06-26 5.9 CVE-2026-48706 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-48706 ] envoyproxy--envoy Envoy is an open source edge and service p= roxy designed for cloud-native applications. From 1.34.0 until 1.35.13, 1.3= 6.9, 1.37.5, and 1.38.3, PROXY Protocol v2 header generator emits TLVs beyo=
    nd the maximum length of 65535 bytes, causing a mismatch between bytes writ= ten and the length field in the header. This can result in smuggled bytes o=
    n the upstream request. This vulnerability is fixed in 1.35.13, 1.36.9, 1.3= 7.5, and 1.38.3. 2026-06-26 4.8 CVE-2026-47692 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-47692 ] envoyproxy--envoy Envoy is an open source edge an=
    d service proxy designed for cloud-native applications. Prior to 1.35.11, 1= .36.7, 1.37.3, and 1.38.1, a structural flaw was identified in DefaultCertV= alidator::verifySubjectAltName where the extracted DNS SAN string is cast t=
    o a C-style string using .c_str() before being passed to the Utility::dnsNa= meMatch() algorithm. If the attacker serves a certificate with a dNSName SA=
    N containing an embedded NUL byte, the helper Utility::generalNameAsString = captures the complete string including the NUL. However, when .c_str() eval= uates it, implicit conversion to absl::string_view inside dnsNameMatch reli=
    es on strlen(), prematurely truncating the evaluation context. Envoy evalua= tes trucated string against the exact required config_san match and returns=
    true, thereby successfully validating the string with the Nul byte for an = upstream routing. This vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, a=
    nd 1.38.1. 2026-06-26 4.4 CVE-2026-47778 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-47778 ] EVoke--EVoke CSMS Charging station authentication ident= ifiers are publicly accessible via web-based mapping platforms. 2026-06-25 = 6.5 CVE-2026-44622 [ https://www.cve.org/CVERecord?id=3DCVE-2026-44622 ] ex= presstech--Quiz and Survey Master (QSM) Easy Quiz and Survey Maker The Quiz=
    and Survey Master (QSM) - Easy Quiz and Survey Maker plugin for WordPress =
    is vulnerable to authorization bypass in all versions up to, and including,=
    11.1.4. This is due to the plugin not properly verifying that a user is au= thorized to perform an action. This makes it possible for authenticated att= ackers, with contributor-level access and above, to create, modify, and del= ete quiz output templates stored in the mlw_quiz_output_templates database = table, including storing unsanitized HTML content such as arbitrary script = tags. 2026-06-27 4.3 CVE-2026-9233 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-9233 ] fabricjs--fabric.js Fabric.js is a Javascript HTML5 canvas lib= rary. Prior to 7.4.0, a potential Cross-Site Scripting (XSS) vulnerability = exists in Fabric.js due to improper escaping of user-controlled input durin=
    g SVG serialization via the toSVG() method. Specifically, the color field w= ithin the colorStops array of a fabric.Gradient object is not properly esca= ped when converted into SVG <stop> elements. If an application renders the = generated SVG string into the DOM, this may allow an attacker to inject arb= itrary HTML/SVG and execute JavaScript in the victim's browser. This vulner= ability is fixed in 7.4.0. 2026-06-22 5.4 CVE-2026-44311 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-44311 ] FasterXML--jackson-databind jackson-dat= abind contains the general-purpose data-binding functionality and tree-mode=
    l for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, Unwrapped= PropertyHandler.processUnwrappedCreatorProperties() replays buffered JSON i= nto creator parameters but never consults prop.visibleInView(activeView). T=
    he normal property-based creator path gates creator properties on the activ=
    e view, but this unwrapped-creator replay path bypasses that check, so a co= nstructor parameter annotated with both @JsonView(AdminView.class) and @Jso= nUnwrapped is populated from attacker JSON even when a more restrictive vie=
    w is active. This vulnerability is fixed in 2.21.4 and 3.1.4. 2026-06-23 6.=
    5 CVE-2026-54518 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54518 ] Fast= erXML--jackson-databind jackson-databind contains the general-purpose data-= binding functionality and tree-model for Jackson Data Processor. From 2.0.0=
    until 2.18.8, 2.21.4, and 3.1.4, JDKFromStringDeserializer constructed Ine= tSocketAddress with new InetSocketAddress(host, port), which performs eager=
    DNS name resolution for hostname inputs at deserialization time. An applic= ation that binds untrusted JSON into a type containing an InetSocketAddress=
    field issues an attacker-chosen DNS query during readValue, before any app= lication-level validation or connect logic. The fix uses InetSocketAddress.= createUnresolved(host, port), deferring DNS to an explicit connect. This vu= lnerability is fixed in 2.18.8, 2.21.4, and 3.1.4. 2026-06-23 5.3 CVE-2026-= 54514 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54514 ] FasterXML--jack= son-databind jackson-databind contains the general-purpose data-binding fun= ctionality and tree-model for Jackson Data Processor. From 2.8.0 until 2.18= .9, 2.21.5, and 3.1.4, in BeanDeserializerBase.createContextual(), per-prop= erty @JsonIgnoreProperties exclusions are applied by _handleByNameInclusion= (), producing a contextual deserializer whose BeanPropertyMap has the ignor=
    ed properties removed. The subsequent per-property case-insensitivity block=
    (triggered by @JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) rebuilds fr=
    om this._beanProperties (the original, unfiltered map) instead of contextua= l._beanProperties, then overwrites the filtered map - restoring every prope= rty _handleByNameInclusion had just removed. The ignored property becomes w= ritable again. This vulnerability is fixed in 2.18.9, 2.21.5, and 3.1.4. 20= 26-06-23 5.3 CVE-2026-54515 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 4515 ] FasterXML--jackson-databind jackson-databind contains the general-pu= rpose data-binding functionality and tree-model for Jackson Data Processor.=
    From 2.21.0 until 2.21.4 and 3.1.4, POJOPropertiesCollector._renamePropert= ies() allows a property with @JsonProperty("renamed") on the getter and @Js= onIgnore on the setter to be renamed rather than dropped. With MapperFeatur= e.INFER_PROPERTY_MUTATORS enabled (default), the private backing field is r= etained; during deserialization BeanDeserializerFactory.addBeanProps() sees=
    hasField()=3D=3Dtrue, builds a FieldProperty, and makes the backing field = writable. An attacker supplying the renamed JSON key writes the backing fie=
    ld directly, bypassing the @JsonIgnore on the setter. This vulnerability is=
    fixed in 3.1.4. 2026-06-23 5.3 CVE-2026-54516 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-54516 ] FasterXML--jackson-databind jackson-databind cont= ains the general-purpose data-binding functionality and tree-model for Jack= son Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, in BeanDeserializer= ._deserializeUsingPropertyBased, the active-view (@JsonView) filter was app= lied only to creator properties; the regular property-buffering branch perf= ormed no prop.visibleInView(activeView) check. A change making SetterlessPr= operty.isMerging() return true routed setterless Collection/Map properties = through this unguarded path, so a setterless collection annotated with a re= stricted @JsonView is populated from attacker JSON even when the active vie=
    w excludes it. This vulnerability is fixed in 2.21.4 and 3.1.4. 2026-06-23 = 5.3 CVE-2026-54517 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54517 ] fi= lamentphp--filament Filament is a collection of full-stack components for a= ccelerated Laravel development. From filament/actions 4.0.0 until 4.11.4 an=
    d 5.6.4 and from filament/tables 3.0.0 until 3.3.51, the recordSelectOption= sQuery() method may be used to scope the options available in the Select fi= eld for AttachAction and AssociateAction. However, the built-in validation = rule for these fields did not apply the same scope. As a result, a user who=
    can trigger these actions could tamper with the Livewire component's state=
    and submit an out-of-scope value. This vulnerability is fixed in filament/= actions 4.11.4 and 5.6.4 and filament/tables 3.3.51. 2026-06-22 6.5 CVE-202= 6-48067 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48067 ] filamentphp--= filament Filament is a collection of full-stack components for accelerated = Laravel development. From 4.0.0 until 4.11.5 and 5.6.5, the ImageColumn and=
    ImageEntry components render raw database values without escaping HTML. Wh= ere the data passed to these components isn't validated, an attacker could = plant malicious HTML or JavaScript and achieve stored XSS that executes for=
    users who view the table or schema. This vulnerability is fixed in 4.11.5 = and 5.6.5. 2026-06-22 6.4 CVE-2026-48167 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-48167 ] filamentphp--filament Filament is a collection of full-= stack components for accelerated Laravel development. From 3.0.0 until 3.3.= 52, 4.11.5, and 5.6.5, any schema can contain a file upload form field, so = Filament applies Livewire's WithFileUploads trait to the Livewire component=
    the schema is embedded in. However, some schemas, such as the panel login = form, do not require file uploads, and exposing unauthenticated temporary f= ile uploads on these components is not an acceptable risk. On these compone= nts, an unauthenticated attacker could upload arbitrary files to the applic= ation's temporary storage, which could be abused to exhaust disk space or i= nflate storage costs. This vulnerability is fixed in 3.3.52, 4.11.5, and 5.= 6.5. 2026-06-22 6.5 CVE-2026-48500 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-48500 ] filamentphp--filament Filament is a collection of full-stack = components for accelerated Laravel development. From 4.0.0 until 4.11.5 and=
    5.6.5, the login page has an observable timing discrepancy that allows una= uthenticated attackers to enumerate registered email addresses. The impact =
    is limited to disclosing whether an account exists for a given email. This = vulnerability is fixed in 4.11.5 and 5.6.5. 2026-06-22 5.3 CVE-2026-48166 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-48166 ] filebrowser--filebrows=
    er File Browser is a file managing interface for uploading, deleting, previ= ewing, renaming, and editing files within a specified directory. Prior to 2= .63.6, unchecked passwords maximums allow for an arbitrarily large password=
    to be passed into the login API. This spikes CPU and memory, and after tes= ting, crashes, heavily lags any container created, and has even made my doc= ker daemon start to send errors with status code 500 even after the contain=
    er was destroyed. This vulnerability is fixed in 2.63.6. 2026-06-25 6.5 CVE= -2026-54092 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54092 ] Flowise--= Flowise Flowise through 2.2.7 contains a SQL injection vulnerability in the=
    importChatflows API. Due to insufficient validation of the chatflow.id val= ue, an authenticated user can supply a crafted JSON import file whose id fi= eld is concatenated unsanitized into a SQL IN clause, allowing arbitrary SQ=
    L to be executed, including blind and error-based extraction of data from t=
    he credential table. 2026-06-24 6.5 CVE-2025-71332 [ https://www.cve.org/CV= ERecord?id=3DCVE-2025-71332 ] Flowise--Flowise Flowise before 3.1.3 validat=
    es Custom MCP stdio environment variables against a denylist using a case-s= ensitive comparison, so on Windows, where environment names are case-insens= itive, supplying 'node_options' bypasses the NODE_OPTIONS denylist entry. A=
    n authenticated user who can configure a Custom MCP node can thereby inject=
    NODE_OPTIONS --require and execute arbitrary code in the Flowise server co= ntext. 2026-06-28 5 CVE-2026-58057 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-58057 ] Flowise--Flowise Flowise before 3.1.0 (npm package flowise, v= ersions 3.0.13 and earlier) uses a weak hardcoded default value 'Secre$t' f=
    or the TOKEN_HASH_SECRET environment variable in packages/server/src/enterp= rise/utils/tempTokenUtils.ts when the variable is not configured. This secr=
    et derives the AES-256-CBC key used to encrypt user IDs and workspace IDs i=
    n the 'meta' field of JWT tokens. An attacker who knows the default secret = can decrypt this metadata to extract internal user and workspace identifier=
    s, and re-encrypt manipulated values such as altered user or workspace IDs.=
    Because the JWT signature is validated separately, decrypting or tampering=
    with this metadata does not by itself grant access, but the disclosure of = internal identifiers and possible metadata manipulation could aid privilege=
    escalation or unauthorized data access. 2026-06-24 4.6 CVE-2026-56269 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-56269 ] Flowise--Flowise Flowise = before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 = iterations instead of the OWASP-recommended minimum of 10 rounds. Attackers=
    can crack password hashes approximately 30 times faster with modern GPU ha= rdware, potentially compromising all user accounts in a database breach sce= nario. 2026-06-24 4.1 CVE-2026-56272 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-56272 ] Fortra--File Integrity Monitoring (FIM) Fortra File Integri=
    ty Monitoring (FIM), formerly Tripwire Enterprise, versions prior to 9.4.0.=
    1 contain a stored cross-site scripting (XSS) vulnerability in the Asset Vi=
    ew UI component. An authenticated user with sufficient privileges to create=
    or modify affected node or database configuration fields could store scrip=
    t content that may be rendered as HTML instead of safely escaped text when = the affected Asset View UI content is displayed. 2026-06-23 5.5 CVE-2026-12= 163 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12163 ] Fortra--File Inte= grity Monitoring (FIM) Fortra File Integrity Monitoring (FIM), formerly Tri= pwire Enterprise, versions prior to 9.4.0 may assign incorrect or elevated = effective permissions to users created by the=C2=A0tetool import=C2=A0comma=
    nd while FIM is running, particularly when the import also creates or chang=
    es roles or role-permission relationships. 2026-06-23 4.4 CVE-2026-12164 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-12164 ] freedesktop.org--libsli=
    rp An out-of-bounds heap read and integer underflow in the TCP urgent data = handling (sosendoob) in freedesktop.org libslirp version before v4.9.2 on h= ypervisor host environments (e.g., QEMU) allows a privileged guest VM attac= ker (root or CAP_NET_RAW) to leak gigabytes of sensitive host-process heap = memory via sending crafted TCP segments with manipulated URG flags and urge=
    nt pointers (ti_urp). 2026-06-24 6.5 CVE-2026-9539 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-9539 ] FunnelKit--FunnelKit Payment Gateway for Strip=
    e WooCommerce Unauthenticated Cross Site Request Forgery (CSRF) in FunnelKi=
    t Payment Gateway for Stripe WooCommerce <=3D 1.14.0.3 versions. 2026-06-26=
    6.5 CVE-2026-57635 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57635 ] G= emini Labs--Site Reviews Subscriber Sensitive Data Exposure in Site Reviews=
    <=3D 8.0.11 versions. 2026-06-26 6.5 CVE-2026-57318 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-57318 ] GeoVision Inc.--GeoVision A memory corrupti=
    on vulnerability exists in the GV-Cloud functionality of GeoVision GV-VMS V=
    20 20.0.2.=C2=A0 A specially crafted network request can lead to a denial o=
    f service. An attacker can impersonate the legitimate server to trigger thi=
    s vulnerability. 2026-06-24 6.2 CVE-2026-12488 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-12488 ] GhozyLab--Image Carousel Contributor Cross Site S= cripting (XSS) in Image Carousel <=3D 1.0.0.41 versions. 2026-06-26 6.5 CVE= -2025-68074 [ https://www.cve.org/CVERecord?id=3DCVE-2025-68074 ] github--g= ithub-mcp-server GitHub MCP Server is GitHub's official MCP Server. From 0.= 22.0 until 1.1.2, when running in HTTP mode with --lockdown-mode enabled, t=
    he RepoAccessCache is implemented as a process-global singleton initialized=
    with the first authenticated user's GraphQL client. All subsequent request=
    s from different users share this singleton and their lockdown-related Grap= hQL queries are executed using the first user's credentials. The singleton =
    is never updated to reflect later users' tokens. This vulnerability is fixe=
    d in 1.1.2. 2026-06-26 6 CVE-2026-48529 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-48529 ] GitLab--GitLab GitLab has remediated an issue in GitLab=
    EE affecting all versions from 13.11 prior to 18.11.6, 19.0 prior to 19.0.=
    3, and 19.1 prior to 19.1.1 in which incorrect authorization in DAST site p= rofile management could allow a user with Developer role to exfiltrate DAST=
    site profile secrets under certain conditions. 2026-06-25 5.3 CVE-2026-113=
    79 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11379 ] GitLab--GitLab Git= Lab has remediated an issue in GitLab CE/EE affecting all versions from 17.=
    5 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under cer= tain conditions could have allowed an unauthenticated user to view confiden= tial issue references on public projects due to improper authorization chec= ks. 2026-06-25 5.3 CVE-2026-2238 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-2238 ] GitLab--GitLab GitLab has remediated an issue in GitLab EE affec= ting all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 be= fore 19.1.1 that under certain conditions could have allowed an authenticat=
    ed user to read or modify another group's virtual registry cleanup policy s= ettings without authorization. 2026-06-25 5.4 CVE-2026-5309 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-5309 ] GitLab--GitLab GitLab has remediated =
    an issue in GitLab CE/EE affecting all versions from 14.8 before 18.11.6, 1= 9.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions cou=
    ld have allowed an authenticated user to conceal content within a Snippet d=
    ue to improper input validation. 2026-06-25 4.3 CVE-2026-1606 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-1606 ] GitLab--GitLab GitLab has remediate=
    d an issue in GitLab CE/EE affecting all versions from 13.6 before 18.11.6,=
    19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions c= ould have allowed an authenticated user with Reporter-level group permissio=
    ns to view package metadata from projects with the Package Registry disable=
    d due to incorrect authorization checks in the group packages feature. 2026= -06-25 4.3 CVE-2026-5796 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5796=
    ] GitLab--GitLab GitLab has remediated an issue in GitLab CE/EE affecting = all versions from 17.11 before 18.11.6, 19.0 before 19.0.3, and 19.1 before=
    19.1.1 that under certain conditions could have allowed an authenticated u= ser with developer-role permissions to bypass package protection rules and = overwrite protected Maven package metadata due to incorrect authorization c= hecks. 2026-06-25 4.3 CVE-2026-5952 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-5952 ] GitLab--GitLab GitLab has remediated an issue in GitLab CE/EE=
    affecting all versions from 9.3 before 18.11.6, 19.0 before 19.0.3, and 19=
    .1 before 19.1.1 that under certain conditions could have allowed sensitive=
    information to be written to application logs due to insufficient filterin=
    g in a CI/CD API endpoint. 2026-06-25 4.4 CVE-2026-8330 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-8330 ] GNU--libidn GNU libidn before 1.44 is pro=
    ne to out-of-bounds reads of=C2=A0uninitialized memory in the ToUnicode API=
    s because of mishandling in=C2=A0idna_to_unicode_internal. The affected cod=
    e is not present in libidn2. 2026-06-23 4 CVE-2026-57053 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-57053 ] gogs--gogs Gogs is an open source self-= hosted Git service. Prior to 0.14.3, password-reset tokens are generated us= ing conf.Auth.ActivateCodeLives (the account-activation lifetime), not conf= .Auth.ResetPasswordCodeLives. The token lifetime is baked into the token it= self at generation time and is re-extracted from the token at verification = time, making RESET_PASSWORD_CODE_LIVES irrelevant to actual enforcement. Wh=
    en an administrator configures a shorter reset window (e.g., 10 minutes) fo=
    r compliance or security reasons, reset tokens remain exploitable for the f= ull activation lifetime instead, while the reset email falsely advertises t=
    he shorter expiry. This vulnerability is fixed in 0.14.3. 2026-06-24 6.8 CV= E-2026-52809 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52809 ] gogs--go=
    gs Gogs is an open source self-hosted Git service. Prior to 0.14.3, an open=
    redirect vulnerability exists in Gogs where attacker-controlled redirect_t=
    o parameters can bypass validation, allowing redirection to arbitrary exter= nal sites. All redirects in Gogs that are validated via the IsSameSite func= tion are vulnerable. The function only inspects the first two characters of=
    the URL string. This check fails to account for directory traversal sequen= ces followed by backslashes. This vulnerability is fixed in 0.14.3. 2026-06= -24 5.4 CVE-2026-52802 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52802 =
    ] gogs--gogs Gogs is an open source self-hosted Git service. Prior to 0.14.=
    3, a malicious user with rights to create a new file on a repository or wik=
    i page can trigger a denial of service condition in which the pages contain= ing the listing of files will return HTTP error 500 and render the web inte= rface unusable for the repository or wiki. The issue is present in file int= ernal/route/repo/wiki.go and internal/route/repo/view.go where the pages tr=
    y to recover commit information. If errors are returned while recovering co= mmit information, the page will return a 500 error and stop rendering, resu= lting in a denial of service. This vulnerability is fixed in 0.14.3. 2026-0= 6-24 4.9 CVE-2025-64719 [ https://www.cve.org/CVERecord?id=3DCVE-2025-64719=
    ] gogs--gogs Gogs is an open source self-hosted Git service. In 0.14.3 and=
    earlier, any authenticated user can watch a private repository they have n=
    o access to, because the access check in the Watch API handler is inverted.=
    The code checks if repoCtx.ViewerCanRead() (returns 404 when the user CAN = read) instead of if !repoCtx.ViewerCanRead() (return 404 when the user CANN=
    OT read). Once watching, the attacker's dashboard activity feed shows commi=
    t messages, branch names, issue titles, and PR details from the private rep= ository. If email notifications are enabled, the attacker also receives ema= ils containing issue and comment content. 2026-06-24 4.3 CVE-2026-52795 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-52795 ] gophish--gophish Gophish=
    through 0.12.1 contains a denial of service vulnerability that allows auth= enticated users with the User role to exhaust server memory by uploading a = crafted Office document as an email template attachment. The ApplyTemplate(=
    ) function in models/attachment.go processes Office documents as ZIP archiv=
    es and calls ioutil.ReadAll() on each contained file entry without enforcin=
    g size restrictions on uncompressed content, allowing a zip bomb payload to=
    expand to several gigabytes in memory and cause the process to be terminat=
    ed by the operating system. 2026-06-22 6.5 CVE-2026-39904 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-39904 ] gpriday--Page Builder by SiteOrigin Th=
    e Page Builder by SiteOrigin plugin for WordPress is vulnerable to Stored C= ross-Site Scripting via panels_data Parameter in all versions up to, and in= cluding, 2.34.3 due to insufficient input sanitization and output escaping.=
    This makes it possible for authenticated attackers, with Contributor-level=
    access and above, to inject arbitrary web scripts in pages that will execu=
    te whenever a user accesses an injected page. This is possible because the = nonce and edit_post capability checks enforced during save are both satisfi=
    ed by Contributor-level users for their own posts, and the panels_data valu=
    e is stored as post meta - outside the scope of WordPress's unfiltered_html=
    carve-out - meaning no wp_kses fallback prevents the unsanitized WP_Widget= _Custom_HTML content from being persisted and later rendered verbatim on th=
    e frontend. 2026-06-27 6.4 CVE-2026-13295 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-13295 ] Grafana--Grafana OSS The Tempo and Loki datasource plu= gins construct backend HTTP requests by interpolating user-supplied input i= nto URL paths without sanitization, enabling path traversal. A Viewer-role = user can: (1) capture admin-configured datasource credentials (secureJsonDa=
    ta custom headers) by traversing to an attacker-controlled endpoint, (2) in= voke state-changing admin endpoints on Tempo (e.g. /flush, /shutdown), and = (3) exfiltrate internal service data via Loki's CallResource which returns = full HTTP response bodies. 2026-06-22 5.4 CVE-2026-10601 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-10601 ] Grav--Grav Grav before 2.0.0-beta.2 con= tains an XML external entity injection vulnerability in SVG file upload pro= cessing that allows authenticated attackers to read arbitrary files. The ap= plication uses simplexml_load_string without disabling external entity load= ing, enabling attackers to inject XXE payloads via malicious SVG files to e= xfiltrate sensitive data. 2026-06-23 6.5 CVE-2026-56701 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-56701 ] Grav--Grav Grav before 1.6.30 contains a=
    cross-site scripting vulnerability in the Admin plugin page editor default=
    security configuration. Privileged users with page editing capabilities ca=
    n inject malicious scripts to execute arbitrary code and install malicious = plugins for system access. 2026-06-25 5.4 CVE-2020-37256 [ https://www.cve.= org/CVERecord?id=3DCVE-2020-37256 ] GravityKit--GravityView Unauthenticated=
    Insecure Direct Object References (IDOR) in GravityView <=3D 3.0.0 version=
    s. 2026-06-26 5.3 CVE-2026-57665 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-57665 ] GravityMore--Gravity Bookings The Gravity Forms Booking plugin = for WordPress is vulnerable to time-based SQL Injection via the 'staff_id' = parameter in all versions up to, and including, 2.7.1 due to insufficient e= scaping on the user supplied parameter and lack of sufficient preparation o=
    n the existing SQL query. This makes it possible for authenticated attacker=
    s, with Subscriber-level access and above, to append additional SQL queries=
    into already existing queries that can be used to extract sensitive inform= ation from the database. 2026-06-25 6.5 CVE-2026-2508 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-2508 ] grokability--snipe-it Snipe-IT is an IT ass= et/license management system. In versions prior to 8.6.0, a user with only = users.edit can send a PATCH to /api/v1/users/{their_own_id} and grant thems= elves any permission except admin and superuser - for example `assets.view`=
    , `assets.create`, `reports.view`, import, etc. The issue is patched in ver= sion 8.6.0. 2026-06-23 5.5 CVE-2026-48493 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-48493 ] guzzle--guzzle Guzzle is an extensible PHP HTTP client=
    . Prior to 7.12.1, in certain configurations, traffic expected to be protec= ted by TLS on the hop to the proxy is transmitted in cleartext. Proxy authe= ntication credentials (the Proxy-Authorization header, proxy userinfo in th=
    e proxy URL, or CURLOPT_PROXYUSERPWD) are sent without encryption, and the = CONNECT target host and port for tunneled HTTPS requests are exposed. The b= uilt-in cURL handlers (GuzzleHttp\Handler\CurlHandler and GuzzleHttp\Handle= r\CurlMultiHandler, used by default whenever the PHP cURL extension is avai= lable) accept an https:// proxy. libcurl older than 7.50.2 silently treats =
    an https:// proxy as a plaintext http:// proxy. The TLS connection to the p= roxy is never established, and the proxy leg is cleartext with no error or = warning. An application is affected when it sends requests through one of t=
    he built-in cURL handlers, configures an https:// proxy expecting the proxy=
    connection itself to be encrypted, and runs with libcurl older than 7.50.2=
    . This vulnerability is fixed in 7.12.1. 2026-06-23 5.9 CVE-2026-55568 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-55568 ] guzzle--guzzle Guzzle is =
    an extensible PHP HTTP client. Prior to 7.12.1, CookieJar incorrectly accep=
    ts cookies with a dot-only Domain attribute and whitespace-padded variants.=
    SetCookie::matchesDomain() removes leading dots from the cookie domain, no= rmalizing dot-only values to the empty string; SetCookie::validate() only r= ejected a strictly empty domain, so these cookies could be stored and the e= mpty normalized domain was treated as matching any request host. An attacke= r-controlled origin that an application requests with a shared cookie jar c=
    an therefore set a cookie that Guzzle later sends to unrelated hosts using = the same jar. This may allow cookie injection or session fixation against d= ownstream services, depending on how those services interpret the injected = cookie. This vulnerability is fixed in 7.12.1. 2026-06-23 5.8 CVE-2026-5576=
    7 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55767 ] guzzle--psr7 guzzle= http/psr7 is a PSR-7 HTTP message library implementation in PHP. Prior to 2= .12.1, guzzlehttp/psr7 did not reject CR/LF characters in certain first-par=
    ty HTTP start-line fields: the request method, protocol version, and respon=
    se reason phrase. If an application placed attacker-controlled data into on=
    e of those fields and later serialized the PSR-7 message as raw HTTP/1.x, f=
    or example with Message::toString() or an equivalent serializer, the serial= ized message could contain attacker-controlled header lines. The issue can = also be reached through Message::parseRequest() or Message::parseResponse()=
    when malformed raw messages are parsed into first-party PSR-7 objects and = then serialized again. Creating or modifying a Request, Response, or other = PSR-7 object alone is not sufficient. The issue requires the malformed mess= age to be serialized and written to the network, forwarded, replayed, or ot= herwise processed by software that does not independently reject the malfor= med start line. This vulnerability is fixed in 2.12.1. 2026-06-23 4.8 CVE-2= 026-55766 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55766 ] halo-dev--h= alo Halo is an open source website building tool. Prior to 2.24.3, a path t= raversal vulnerability in the backup download endpoint allows authenticated=
    administrators to read arbitrary files from the server filesystem. The bac= kup download endpoint (GET /apis/console.api.migration.halo.run/v1alpha1/ba= ckups/{name}/files/{filename}) in MigrationServiceImpl.download() resolves = the backup filename via Path.resolve() without validating that the resolved=
    path stays within the designated backups directory. Also, the Backup creat= ion endpoint (POST /apis/migration.halo.run/v1alpha1/backups) does not sani= tize the status fields during creation This vulnerability is fixed in 2.24.=
    3. 2026-06-25 5.5 CVE-2026-55439 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-55439 ] harmonic_design--HD Quiz The HD Quiz plugin for WordPress is vu= lnerable to Cross-Site Request Forgery in versions 2.2.0 to 2.2.1. This is = due to missing or incorrect nonce validation on the hdq_validate_nonce func= tion. This makes it possible for unauthenticated attackers to delete or mod= ify quizzes and questions, create new quizzes, and change plugin settings v=
    ia a forged request granted they can trick a site administrator into perfor= ming an action such as clicking on a link. 2026-06-27 4.3 CVE-2026-13422 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-13422 ] HCLSoftware--Traveler f=
    or Microsoft Outlook The HCL Traveler for Microsoft Outlook libraries are b= eing flagged as potentially malicious software or an unrecognized applicati= on. 2026-06-26 6.7 CVE-2024-23581 [ https://www.cve.org/CVERecord?id=3DCVE-= 2024-23581 ] HCLSoftware--Traveler for Microsoft Outlook HCL Traveler for M= icrosoft Outlook (HTMO) is susceptible to a sensitive data exposure vulnera= bility which could allow an attacker to exploit application information to = then attempt additional attacks and cause unknown behavior in the applicati= on. 2026-06-27 5.5 CVE-2025-59868 [ https://www.cve.org/CVERecord?id=3DCVE-= 2025-59868 ] HKUDS--OpenHarness OpenHarness ohmo gateway /resume and /summa=
    ry slash commands default remote_invocable to True, allowing admitted remot=
    e senders to enumerate and load arbitrary session snapshots by ID. Attacker=
    s can exploit this to access victim snapshots containing private prompts, c= redentials, tool output, and file paths via shared gateway channels. 2026-0= 6-23 6.5 CVE-2026-56695 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56695=
    ] HKUDS--OpenHarness OpenHarness /issue and /pr_comments slash commands la=
    ck remote_invocable=3DFalse protection, allowing remote channel senders to = write attacker-controlled Markdown into project context files. Admitted rem= ote attackers can inject malicious content into .openharness/issue.md and .= openharness/pr_comments.md files, which are subsequently injected into runt= ime system prompts, persistently influencing local agent behavior. 2026-06-=
    23 5.4 CVE-2026-56696 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56696 ]=
    Hono--Hono Hono before 4.12.12 does not validate cookie names on the write=
    path in the setCookie(), serialize(), and serializeSigned() functions, all= owing invalid characters such as control characters (e.g. \r or \n) when an=
    application passes a user-controlled cookie name. This can produce malform=
    ed Set-Cookie header values. In modern runtimes such as Node.js and Cloudfl= are Workers, such invalid header values are rejected and cause a runtime er= ror before the response is sent, so header injection or response splitting = could not be reproduced; the issue primarily affects correctness and robust= ness, resulting in runtime errors (availability) rather than confirmed head=
    er injection. 2026-06-23 5.3 CVE-2026-56762 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-56762 ] hono--hono hono before 4.12.14 contains an html inje= ction vulnerability in jsx server-side rendering that allows attackers to i= nject unintended html by using malformed attribute names. Attackers can cra=
    ft specially crafted attribute keys containing characters like quotes or an= gle brackets to break html tag boundaries and inject arbitrary attributes o=
    r elements. 2026-06-24 4.3 CVE-2026-56761 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-56761 ] honojs--hono Hono is a Web application framework that = provides support for any JavaScript runtime. Prior to 4.12.25, the Body Lim=
    it Middleware trusts the request's Content-Length header to decide whether =
    a body is within the limit. On AWS Lambda (API Gateway v1/v2, ALB, VPC Latt= ice, and Lambda@Edge) the body is delivered fully buffered and the adapter = builds the request with the client-declared Content-Length, which need not = match the actual payload. A client can declare a tiny Content-Length while = sending a much larger body, slipping past the limit. This vulnerability is = fixed in 4.12.25. 2026-06-22 6.5 CVE-2026-54288 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-54288 ] honojs--hono Hono is a Web application framework=
    that provides support for any JavaScript runtime. Prior to 4.12.25, on Win= dows hosts, an encoded backslash (%5C) in the request path decodes to \, wh= ich the Windows path resolver treats as a separator. serve-static then reso= lves a single URL segment such as admin\secret.txt into a nested file under=
    the root and serves it, letting an attacker read static files meant to be = protected behind prefix-mounted middleware. This vulnerability is fixed in = 4.12.25. 2026-06-22 5.9 CVE-2026-54286 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54286 ] honojs--hono Hono is a Web application framework that p= rovides support for any JavaScript runtime. Prior to 4.12.25, on AWS Lambda=
    , the ALB single-header response and the VPC Lattice v2 response join multi= ple Set-Cookie headers into one comma-separated value. Because commas also = appear inside cookie attributes (for example Expires dates), clients cannot=
    split the value back into individual cookies and silently drop or misparse=
    them. This vulnerability is fixed in 4.12.25. 2026-06-22 5.3 CVE-2026-5428=
    7 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54287 ] honojs--hono Hono i=
    s a Web application framework that provides support for any JavaScript runt= ime. Prior to 4.12.25, on AWS Lambda@Edge, CloudFront delivers a request he= ader that appears more than once as several separate entries. The adapter w= rites each value with Headers.set instead of Headers.append, so every value=
    overwrites the previous one and only the last reaches the application. Rep= eated request headers such as X-Forwarded-For, Forwarded, and Via are silen= tly truncated to a single value. Request middleware sees only the last valu=
    e of a repeated header instead of the full chain. For applications that bas=
    e access control on the X-Forwarded-For chain, this can weaken or alter tha=
    t decision; for auditing, hop history is lost. This vulnerability is fixed =
    in 4.12.25. 2026-06-22 4.8 CVE-2026-54289 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-54289 ] iamranit--Advanced Contact Form 7 Compact DB The Advan= ced Contact Form 7 - Compact DB plugin for WordPress is vulnerable to unaut= horized deletion of data due to a missing capability check on the cf7cdb_aj= ax_delete_user() function in versions up to, and including, 1.0.0. The hand= ler is registered against both `wp_ajax_cf7cdb_delete` and `wp_ajax_nopriv_= cf7cdb_delete`, and it performs no nonce verification, no capability check,=
    and no ownership check before invoking `$wpdb->delete()` against the `wp_c= f7cdb_data` table with an attacker-supplied integer ID. This makes it possi= ble for unauthenticated attackers to delete arbitrary contact form submissi=
    on entries stored by the plugin by iterating sequential primary-key IDs. 20= 26-06-24 5.3 CVE-2026-12094 [ https://www.cve.org/CVERecord?id=3DCVE-2026-1= 2094 ] IBM--Datacap IBM Datacap 9.1.7, 9.1.8, and 9.1.9 and IBM Datacap Nav= igator 9.1.7, 9.1.8, and 9.1.9 is vulnerable to cross-site scripting. This = vulnerability allows an unauthenticated attacker to embed arbitrary JavaScr= ipt code in the Web UI thus altering the intended functionality potentially=
    leading to credentials disclosure within a trusted session. 2026-06-22 6.1=
    CVE-2026-8059 [ https://www.cve.org/CVERecord?id=3DCVE-2026-8059 ] IBM--Da= tacap IBM Datacap 9.1.7, 9.1.8, and 9.1.9 and IBM Datacap Navigator 9.1.7, = 9.1.8, and 9.1.9 allows an attacker to retrieve user passwords and cryptogr= aphic keys from memory. Attacker can=C2=A0use the same keys to decrypt pass= word, gain access to the application and access sensitive=C2=A0data in the = database. 2026-06-22 5.5 CVE-2026-8636 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-8636 ] IBM--Db2 on Cloud Pak for Data and Db2 Warehouse on Clou=
    d Pak for Data IBM Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak=
    for Data versions 4.8,5.0,5.1,5.2,5.3 could allow an authenticated user to=
    cause a denial of service when creating new databases due to improper allo= cation of resources. 2026-06-22 6.5 CVE-2024-54178 [ https://www.cve.org/CV= ERecord?id=3DCVE-2024-54178 ] IBM--Db2 on Cloud Pak for Data and Db2 Wareho= use on Cloud Pak for Data IBM Db2 on Cloud Pak for Data and Db2 Warehouse o=
    n Cloud Pak for Data versions 4.8, 5.0, 5.1, 5.2, 5.3 could allow a privile= ged user to perform operations and obtain sensitive information outside of = their authority due to improper token validation. 2026-06-22 6 CVE-2025-266=
    9 [ https://www.cve.org/CVERecord?id=3DCVE-2025-2669 ] IBM--Db2 on Cloud Pa=
    k for Data and Db2 Warehouse on Cloud Pak for Data IBM Db2 on Cloud Pak for=
    Data and Db2 Warehouse on Cloud Pak for Data versions 4.8, 5.0, 5.1, 5.2, = and 5.3 could allow an authenticated user to bypass client-side validation = and manipulate input data using man in the middle techniques. 2026-06-22 5.=
    3 CVE-2023-33854 [ https://www.cve.org/CVERecord?id=3DCVE-2023-33854 ] IBM-= -Engineering Workflow Management IBM Engineering Workflow Management 7.0.2 = through 7.0.2 Interim Fix 035, 7.0.3 through 7.0.3 Interim Fix 017, and 7.1=
    through 7.1 Interim Fix 004 is vulnerable to HTTP header injection, caused=
    by improper validation of input by the HOST headers. This could allow an a= ttacker to conduct various attacks against the vulnerable system, including=
    cross-site scripting, cache poisoning or session hijacking. 2026-06-22 6.5=
    CVE-2024-51454 [ https://www.cve.org/CVERecord?id=3DCVE-2024-51454 ] IBM--= Engineering Workflow Management IBM Engineering Workflow Management 7.0.3 t= hrough 7.0.3 Interim Fix 020, and 7.1 through 7.1 Interim Fix 007 is vulner= able to cross-site scripting. This vulnerability allows an authenticated us=
    er to embed arbitrary JavaScript code in the Web UI thus altering the inten= ded functionality potentially leading to credentials disclosure within a tr= usted session. 2026-06-22 5.4 CVE-2025-33128 [ https://www.cve.org/CVERecor= d?id=3DCVE-2025-33128 ] IBM--i IBM WebSphere Application Server and IBM Web= Sphere Application Server Liberty are vulnerable to denial of service in th=
    e WebSphere WebServer Plug-in component when an attacker can pass crafted r= equests to the web server. 2026-06-22 5.9 CVE-2026-10852 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-10852 ] IBM--IBM Watson Speech Services Cartrid=
    ge IBM Watson Speech Services Cartridge is vulnerable to Server-Side Reques=
    t Forgery (SSRF) in Sterling File Gateway, due to a flaw which may allow an=
    authenticated attacker to send unauthorized requests from the system, pote= ntially leading to network enumeration or facilitating other attacks [GHSA-= rr7j-v2q5-chgv] [CVE-2026-7253]. IBM Sterling File Gateway is used in our s= peech runtimes. This vulnerabilitiy has been addressed. Please read the det= ails for remediation below. 2026-06-22 5.3 CVE-2026-7253 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-7253 ] IBM--TRIRIGA Application Platform IBM TR= IRIGA Application Platform 5.0.2 through 5.0.3 is vulnerable to cross-site = scripting. This vulnerability allows an authenticated user to embed arbitra=
    ry JavaScript code in the Web UI thus altering the intended functionality p= otentially leading to credentials disclosure within a trusted session. 2026= -06-22 5.4 CVE-2026-11372 [ https://www.cve.org/CVERecord?id=3DCVE-2026-113=
    72 ] IBM--WebSphere Application Server IBM WebSphere Application Server 9.0=
    , and 8.5 and IBM WebSphere Application Server - Liberty 17.0.0.3 through 2= 6.0.0.6 are vulnerable to a denial of service, caused by sending a speciall= y-crafted request. A remote attacker could exploit this vulnerability to ca= use the server to consume memory resources. 2026-06-22 5.9 CVE-2026-9320 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-9320 ] itsourcecode--Hospital M= anagement System A vulnerability was found in itsourcecode Hospital Managem= ent System 1.0. The affected element is an unknown function of the file /aj= axmedicine.php. The manipulation of the argument medicineid results in sql = injection. It is possible to launch the attack remotely. The exploit has be=
    en made public and could be used. 2026-06-28 6.3 CVE-2026-13496 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-13496 ] itsourcecode--Hospital Managemen=
    t System A vulnerability was determined in itsourcecode Hospital Management=
    System 1.0. The impacted element is an unknown function of the file /appoi= ntment.php. This manipulation of the argument editid causes sql injection. = The attack can be initiated remotely. The exploit has been publicly disclos=
    ed and may be utilized. 2026-06-28 6.3 CVE-2026-13497 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-13497 ] itsourcecode--Hospital Management System A=
    vulnerability has been found in itsourcecode Hospital Management System 1.=
    0. Impacted is an unknown function of the file /adminprofile.php. The manip= ulation of the argument loginid leads to sql injection. It is possible to i= nitiate the attack remotely. The exploit has been disclosed to the public a=
    nd may be used. 2026-06-28 4.7 CVE-2026-13495 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-13495 ] jdx--mise mise manages dev tools like node, python=
    , cmake, and terraform. From 2026.3.15 until 2026.6.4, mise loads github.cr= edential_command from local project config before any trust decision, then = executes that value with sh -c when resolving a GitHub token. An attacker w=
    ho can place a .mise.toml in a repository can execute arbitrary shell comma= nds when the victim runs a GitHub-related mise command and no higher-priori=
    ty GitHub token environment variable is set. This vulnerability is fixed in=
    2026.6.4. 2026-06-26 6.3 CVE-2026-55448 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-55448 ] jdx--mise mise manages dev tools like node, python, cma= ke, and terraform. Prior to 2026.6.1, the mise HTTP backend builds its inst= all symlink destination from the raw resolved version string for non-latest=
    versions. Normal tool install paths use the sanitized version pathname, bu=
    t the HTTP backend's symlink path uses the raw value. On Unix-like systems,=
    if that version is an absolute path, PathBuf::join discards the intended m= ise installs root. A repository-controlled .tool-versions file can therefor=
    e make mise install create a symlink outside the mise install tree. With bi= n_path, the same issue can place an executable symlink under an attacker-se= lected absolute prefix, such as a developer-tool prefix that is later added=
    to PATH. This vulnerability is fixed in 2026.6.1. 2026-06-26 5.5 CVE-2026-= 54557 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54557 ] jegstudio--Gute= nverse WordPress Blocks, Page Builder & Site Editor The Gutenverse - WordPr= ess Blocks, Page Builder & Site Editor plugin for WordPress is vulnerable t=
    o Stored Cross-Site Scripting via admin settings in all versions up to, and=
    including, 3.8.0 due to insufficient input sanitization and output escapin=
    g. This makes it possible for authenticated attackers, with editor-level pe= rmissions and above, to inject arbitrary web scripts in pages that will exe= cute whenever a user accesses an injected page. This only affects multi-sit=
    e installations and installations where unfiltered_html has been disabled. = 2026-06-27 4.4 CVE-2026-12399 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -12399 ] jellyfin--jellyfin Jellyfin is an open source self hosted media se= rver. Prior to 10.11.9, a potential XSS attack exists in Jellyfin which can=
    allow a non-privileged user to execute arbitrary Javascript in the context=
    of a logged-in Administrative user, resulting in numerous potential issues=
    . The Client header during an AuthenticateByName can contain arbitrary HTML=
    and Javascript, which will then be executed by the Administrative user whe=
    n visiting the Access tab of the user in question from within the dashboard=
    . This vulnerability is fixed in 10.11.9. 2026-06-24 5.7 CVE-2026-49220 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-49220 ] JetBrains--Kotlin In Jet= Brains Kotlin before 2.4.20 code execution was possible via unsafe deserial= ization in the build cache metadata 2026-06-26 6.7 CVE-2026-53914 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-53914 ] JetBrains--YouTrack In JetBrai=
    ns YouTrack before 2026.2.16593 improper authorisation in the app configura= tions endpoint allowed modifying project settings 2026-06-26 5.3 CVE-2026-5= 7923 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57923 ] JetBrains--YouTr= ack In JetBrains YouTrack before 2026.2.16593 improper access control allow=
    ed reading users' private data via the comment templates endpoint 2026-06-2=
    6 4.3 CVE-2026-57921 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57921 ] = JetBrains--YouTrack In JetBrains YouTrack before 2026.2.16593 default role = configuration exposed excessive user profile details 2026-06-26 4.3 CVE-202= 6-57924 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57924 ] JetBrains--Yo= uTrack In JetBrains YouTrack before 2026.2.16593 improper access control al= lowed reading saved queries and tags 2026-06-26 4.3 CVE-2026-57925 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-57925 ] jetmonsters--Restaurant Menu =
    by MotoPress Subscriber Broken Access Control in Restaurant Menu by MotoPre=
    ss <=3D 2.4.11 versions. 2026-06-26 4.3 CVE-2025-63078 [ https://www.cve.or= g/CVERecord?id=3DCVE-2025-63078 ] JoomSky--JS Help Desk Unauthenticated Ins= ecure Direct Object References (IDOR) in JS Help Desk <=3D 3.1.0 versions. = 2026-06-26 5.3 CVE-2026-57652 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -57652 ] joomunited--WP Latest Posts The WP Latest Posts plugin for WordPre=
    ss is vulnerable to Stored Cross-Site Scripting via crafted image src attri= butes in post content in versions up to, and including, 5.0.11. This is due=
    to insufficient output escaping in the field() and loop() functions, which=
    extract the raw src attribute value from <img> tags within post_content us= ing a regular expression and then reconstruct new <img> elements or CSS bac= kground-image declarations by directly concatenating the unescaped value - = bypassing WordPress's kses filtering entirely. This makes it possible for a= uthenticated attackers, with author-level access and above, to inject arbit= rary web scripts in pages that will execute whenever a user accesses an inj= ected page. 2026-06-24 6.4 CVE-2026-9620 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-9620 ] joomunited--WP Meta SEO The WP Meta SEO plugin for WordP= ress is vulnerable to Server-Side Request Forgery in all versions up to, an=
    d including, 4.5.18 via the 'new_link' parameter. This makes it possible fo=
    r authenticated attackers, with contributor-level access and above, to make=
    web requests to arbitrary locations originating from the web application a=
    nd can be used to query and modify information from internal services. The = HTTP response status from outbound requests is reflected back in the AJAX J= SON response as status_code, providing an enumeration oracle usable for pro= bing internal hosts and cloud metadata services. 2026-06-24 6.4 CVE-2026-11= 370 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11370 ] jotis--Blue Captc=
    ha The Blue Captcha plugin for WordPress is vulnerable to Cross-Site Reques=
    t Forgery in versions up to and including 2.0.1. This is due to missing or = incorrect nonce validation on the main admin panel (blcap_main_page) and on=
    the Hall of Shame and Log subpages, which accept a 'blcap_action' / 'actio=
    n' parameter from $_REQUEST and perform destructive operations (plugin unin= stall via blcap_uninstall(), log deletion via blcap_delete_logs(), Hall of = Shame deletion via blcap_delete_ip_db(), and adding IPs to the banned list = via update_option('blcap_settings')) with no wp_verify_nonce(), check_admin= _referer(), or check_ajax_referer() calls anywhere in the codebase. This ma= kes it possible for unauthenticated attackers to uninstall the plugin, dele=
    te audit logs, remove Hall of Shame entries, and add arbitrary IP addresses=
    to the block list via a forged request granted they can trick a site admin= istrator into performing an action such as clicking on a link. 2026-06-24 4=
    .3 CVE-2026-10552 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10552 ] k3s= -io--k3s K3s is a fully conformant production-ready Kubernetes distribution=
    . Prior to 1.35.3+k3s1, 1.34.6+k3s1, v1.33.10+k3s1, a path traversal vulner= ability exists in K3s's etcd snapshot decompression functionality. Zip file=
    s containing archive members with maliciously crafted names can be written =
    to arbitrary locations on the filesystem when an administrator restores the=
    archive as a compressed etcd snapshot. This vulnerability is fixed in 1.35= .3+k3s1, 1.34.6+k3s1, v1.33.10+k3s1. 2026-06-25 5.8 CVE-2026-54250 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-54250 ] kanboard--kanboard Kanboard t= hrough 1.2.52, fixed in commit 928c68a, UserViewController::removeSession f= ails to validate the session id parameter before passing it to RememberMeSe= ssionModel::remove, allowing authenticated users to delete other users' Rem= ember Me sessions. Attackers can enumerate sequential session IDs and mass-= invalidate persistent login sessions of any user, including administrators,=
    forcing re-authentication and causing denial of service. 2026-06-25 5.4 CV= E-2026-56774 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56774 ] Kerry--B=
    NE Testimonials Contributor Cross Site Scripting (XSS) in BNE Testimonials = <=3D 2.0.8 versions. 2026-06-26 6.5 CVE-2025-68075 [ https://www.cve.org/CV= ERecord?id=3DCVE-2025-68075 ] kestra-io--kestra Kestra is an open-source, e= vent-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the preview= FileFromExecution endpoint (GET /api/v1/{tenant}/executions/{executionId}/f= ile/preview) contains an access control bypass that allows any authenticate=
    d user to read output files from any other execution within the same tenant=
    , bypassing execution-level and namespace-level isolation. This vulnerabili=
    ty is fixed in 1.0.45 and 1.3.21. 2026-06-26 6.5 CVE-2026-53577 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-53577 ] khoj-ai--khoj A flaw has been fo= und in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function o=
    f the file src/khoj/routers/api_chat.py of the component Conversation Shari=
    ng Handler. This manipulation of the argument conversation.agent causes inc= orrect authorization. Remote exploitation of the attack is possible. The ex= ploit has been published and may be used. The pull request to fix this issu=
    e awaits acceptance. 2026-06-28 5.5 CVE-2026-13508 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-13508 ] Knit Pay--UPI QR Code Payment Gateway for Woo= Commerce Customer Broken Access Control in UPI QR Code Payment Gateway for = WooCommerce <=3D 1.6.2 versions. 2026-06-25 5.4 CVE-2026-56023 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-56023 ] krishaweb--Advance Nav Menu Manag=
    er The Advance Nav Menu Manager plugin for WordPress is vulnerable to autho= rization bypass in all versions up to, and including, 1.3. This is due to t=
    he plugin not properly verifying that a user is authorized to perform an ac= tion. This makes it possible for authenticated attackers, with subscriber-l= evel access and above, to duplicate, copy, move, or publish nav_menu_item p= osts via wp_insert_post(), modifying the site's navigation menus without au= thorization. 2026-06-24 4.3 CVE-2026-8688 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-8688 ] langchain-ai--langchain LangChain is a framework for bu= ilding agents and LLM-powered applications. Prior to 1.3.9, several LangCha=
    in components that resolve filesystem paths or expand search patterns do no=
    t consistently confine the resolved path to the intended root directory. Af= fected behaviors include: a file-search agent middleware that validates a s= tarting directory but not the search pattern or the resolved target of matc= hed files, so glob patterns and symlinks can reach files outside the config= ured root; prompt- and chain/agent-configuration loaders that accept path f= ields and resolve them without confining the result to a trusted base or re= jecting symlink targets; and path-prefix authorization checks that compare =
    by string prefix without a path-segment boundary, so a sibling path sharing=
    the prefix is accepted. When these components receive path values, search = patterns, or workspace contents influenced by an untrusted source - includi=
    ng an LLM acting on untrusted input - the result can be disclosure of files=
    outside the intended boundary. This vulnerability is fixed in 1.3.9. 2026-= 06-22 5.1 CVE-2026-55443 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5544=
    3 ] langflow-ai--langflow Langflow is a tool for building and deploying AI-= powered agents and workflows. Prior to 1.9.0, Langflow is vulnerable to Pat=
    h Traversal in the Knowledge Bases API (POST /api/v1/knowledge_bases). This=
    occurs because user-supplied knowledge base names are used directly to cre= ate file paths without proper sanitization or containment checks. An authen= ticated attacker can exploit this flaw to create directories and write file=
    s anywhere on the server's filesystem. This vulnerability is fixed in 1.9.0=
    . 2026-06-23 6.5 CVE-2026-42867 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-42867 ] langflow-ai--langflow Langflow is a tool for building and deploy= ing AI-powered agents and workflows. Prior to 1.10.0, the "Shareable Playgr= ound" (or "Public Flows" in code) contains a potential arbitrary file-read = vulnerability, depending on the exact flow configuration used. By making a = flow public, public execution of the flow is allowed. The execution request=
    can contain a list of files that gets read by Langflow and fed into the LL=
    M. The files path can be any path supported by the storage - it can be eith=
    er a local file or S3 path if supported by the local configuration This vul= nerability is fixed in 1.10.0. 2026-06-23 6.1 CVE-2026-48520 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-48520 ] langflow-ai--langflow Langflow is a=
    tool for building and deploying AI-powered agents and workflows. Prior to = 1.7.0, the logout button does not clear the session. The previous user stay=
    s logged in unless another user explicitly logs in. This vulnerability is f= ixed in 1.7.0. 2026-06-23 6.1 CVE-2026-55423 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-55423 ] libssh2--libssh2 libssh2 through 1.11.1 grows its p= ublickey list with SSH2_REALLOC but does not zero-initialize new entries be= fore parsing populates them, so a parse failure reaching the cleanup path l= eaves libssh2_publickey_list_free operating on an uninitialized entry. A ma= licious SSH server offering the publickey subsystem can use a malformed res= ponse to make cleanup free an uninitialized, attacker-influenceable attrs p= ointer in a connecting libssh2 client. 2026-06-28 6.5 CVE-2026-58051 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-58051 ] magepeopleteam--Booking and=
    Rental Manager Unauthenticated Broken Access Control in Booking and Rental=
    Manager <=3D 2.7.1 versions. 2026-06-26 5.3 CVE-2026-57660 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-57660 ] Majestic Support--Majestic Support S= ubscriber Insecure Direct Object References (IDOR) in Majestic Support <=3D=
    1.1.7 versions. 2026-06-26 5.4 CVE-2026-57646 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-57646 ] manuelpadillac--MP Customize Login Page The MP Cu= stomize Login Page plugin for WordPress is vulnerable to Cross-Site Request=
    Forgery (CSRF) in all versions up to and including 1.0. This is due to a c= ompletely broken nonce validation in the enter_mpclp_login_options() functi= on, which contains an inverted check (if wp_verify_nonce(...) { return fals=
    e; }) and is missing the required action parameter for wp_verify_nonce(). A=
    s a result, the nonce check is effectively dead code: it never blocks malic= ious requests because a CSRF-supplied empty/invalid nonce always returns fa= lse, satisfying the inverted condition to continue execution. Furthermore, = the settings-update handler is hooked on init without any capability check.=
    This makes it possible for unauthenticated attackers to modify all plugin = setting, including login page background, logo URL, image dimensions, butto=
    n colors, and login message, by tricking a logged-in administrator into sub= mitting a crafted request. 2026-06-24 4.3 CVE-2026-6292 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-6292 ] masteriyo--Masteriyo LMS LMS Course Build= er, Quizzes & Certificates The Masteriyo LMS - LMS Course Builder, Quizzes =
    & Certificates plugin for WordPress is vulnerable to authorization bypass i=
    n all versions up to, and including, 2.2.1. This is due to the plugin not p= roperly verifying that a user is authorized to perform an action. This make=
    s it possible for authenticated attackers, with student-level access and ab= ove, to modify the description (post content) of arbitrary course announcem= ents authored by instructors or administrators. 2026-06-27 4.3 CVE-2026-117=
    73 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11773 ] mastodon--mastodon=
    Mastodon is a free, open-source social network server based on ActivityPub=
    . Prior to 4.5.10, 4.4.17, and 4.3.23, Mastodon's normalization of incoming=
    activities signed with Linked-Data Signatures does not sufficiently protec=
    t the activities from a certain class of spoofing, allowing threat actors t=
    o remove JSON entries from valid signed activities from a third-party actor=
    . This vulnerability is fixed in 4.5.10, 4.4.17, and 4.3.23. 2026-06-24 6.5=
    CVE-2026-48028 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48028 ] masto= don--mastodon Mastodon is a free, open-source social network server based o=
    n ActivityPub. Prior to 4.5.10, 4.4.17, and 4.3.23, Mastodon's normalizatio=
    n of incoming activities signed with Linked-Data Signatures does not suffic= iently protect the activities from a certain class of spoofing, allowing at= tackers to re-arrange a valid signed JSON-LD activity from a third-party ac= tor to have it processed differently. This vulnerability is fixed in 4.5.10=
    , 4.4.17, and 4.3.23. 2026-06-24 5.3 CVE-2026-46349 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-46349 ] mastodon--mastodon Mastodon is a free, open-= source social network server based on ActivityPub. From 4.3.0 until 4.5.11 = and 4.4.18, Mastodon has a feature to let websites credit authors of their = articles. To prevent false attribution claims, Mastodon uses the attributio= nDomains JSON-LD term, however, an error in how it is defined makes Linked = Data Signatures on the toot:attributionDomains property ineffective. An att= acker can arbitrarily modify the attributionDomains value of a legitimately=
    signed Update activity and bypass Mastodon's signature verification. This = vulnerability is fixed in 4.5.11 and 4.4.18. 2026-06-24 5.3 CVE-2026-50128 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-50128 ] Mattermost--github.co= m/mattermost/mattermost/server/public The Mattermost Go module github.com/m= attermost/mattermost/server/public versions < v0.1.22 fail to validate path=
    parameters when constructing API route paths which allows an attacker to r= edirect API calls to unintended endpoints via crafted IDs containing path t= raversal components. Mattermost Advisory ID: MMSA-2025-00532 2026-06-26 5.4=
    CVE-2026-13426 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13426 ] Matte= rmost--Mattermost Mattermost versions 10.11.x <=3D 10.11.18, 11.6.x <=3D 11= .6.3, 11.5.x <=3D 11.5.6 fail to validate attachment URLs against internal =
    or private IP ranges in the Mattermost Agents plugin MCP server which allow=
    s an attacker with access to the MCP server in stdio mode to perform server= -side request forgery (SSRF) and exfiltrate data from internal network serv= ices via supplying internal URLs as file attachments in post creation reque= sts.. Mattermost Advisory ID: MMSA-2026-00635 2026-06-26 6.5 CVE-2026-4339 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-4339 ] Mattermost--Mattermost=
    Mattermost versions 11.7.x <=3D 11.7.0, 11.6.x <=3D 11.6.2, 11.5.x <=3D 11= .5.5, 10.11.x <=3D 10.11.17 Fail to validate channel ownership of an existi=
    ng subscription before applying edits which allows an authenticated attacke=
    r to hijack subscriptions from channels they have no access to via a crafte=
    d PUT request to the subscription edit endpoint.. Mattermost Advisory ID: M= MSA-2026-00650 2026-06-22 6.4 CVE-2026-6062 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-6062 ] Mattermost--Mattermost Mattermost versions 11.7.x <=
    =3D 11.7.0, 11.6.x <=3D 11.6.2, 11.5.x <=3D 11.5.5, 10.11.x <=3D 10.11.17 f= ail to authenticate Atlassian Connect installed callbacks, allowing a remot=
    e unauthenticated attacker to inject a rogue sharedSecret and disrupt the J= ira integration via POST to /ac/installed during the pending-install window=
    .. Mattermost Advisory ID: MMSA-2026-00654 2026-06-22 6.4 CVE-2026-6673 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-6673 ] Mattermost--Mattermost Ma= ttermost Plugins versions <=3D11.6 10.18.11 11.3.6 11.6.5.0 fail to sanitiz=
    e error responses from the OpenAI API before logging, which allows a user w= ith access to server logs or support packets to obtain a valid or partially=
    reconstructable OpenAI API key via inspection of mattermost.log entries ge= nerated during authentication failures. Mattermost Advisory ID: MMSA-2026-0= 0609 2026-06-26 6.8 CVE-2026-9699 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-9699 ] Mattermost--Mattermost Mattermost versions 11.7.x <=3D 11.7.0, = 11.6.x <=3D 11.6.2, 11.5.x <=3D 11.5.5, 10.11.x <=3D 10.11.17 fail to enfor=
    ce administrator authorization on the {{setDefaultInstance}} call within th=
    e {{/gitlab connect}} command handler, which allows any authenticated user =
    to overwrite the global default GitLab instance configuration via the {{/gi= tlab connect <instance-name>}} slash command.. Mattermost Advisory ID: MMSA= -2026-00644 2026-06-22 5.4 CVE-2026-5139 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-5139 ] Mattermost--Mattermost Mattermost versions 11.7.x <=3D 1= 1.7.0, 11.6.x <=3D 11.6.2, 11.5.x <=3D 11.5.5, 10.11.x <=3D 10.11.17 fail t=
    o invalidate cached authentication state for active WebSocket connections d= uring global session revocation, which allows a user with an existing WebSo= cket connection to remain authenticated and continue receiving real-time ev= ents until the cached session expires or the client reconnects.. Mattermost=
    Advisory ID: MMSA-2026-00664 2026-06-22 4.3 CVE-2026-9162 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-9162 ] Mattermost--Mattermost Google Drive Pl= ugin The Mattermost Google Drive plugin before version 1.1.0 fails to valid= ate channel membership in the file creation endpoint, allowing authenticate=
    d users with a connected Google account to share Google Drive files to unau= thorized private channels and disclose private channel membership. 2026-06-=
    25 4.2 CVE-2026-2299 [ https://www.cve.org/CVERecord?id=3DCVE-2026-2299 ] m= axfoundry--MaxButtons Create buttons The MaxButtons - Create buttons plugin=
    for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'vie=
    w' parameter in all versions up to, and including, 9.8.5 due to insufficien=
    t input sanitization and output escaping. This makes it possible for unauth= enticated attackers to inject arbitrary web scripts in pages that execute i=
    f they can successfully trick a user into performing an action such as clic= king on a link. 2026-06-27 6.1 CVE-2026-13245 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-13245 ] Mervin Praison--Featured Image Author Cross Site S= cripting (XSS) in Featured Image <=3D 2.1 versions. 2026-06-26 6.5 CVE-2026= -57431 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57431 ] metagauss--Pro= fileGrid User Profiles, Groups and Communities The ProfileGrid - User Profi= les, Groups and Communities plugin for WordPress is vulnerable to Stored Cr= oss-Site Scripting via the 'pm_author_message' parameter in the pm_send_mes= sage_to_author function in all versions up to, and including, 5.9.9.2 due t=
    o insufficient input sanitization and output escaping. This makes it possib=
    le for authenticated attackers, with Subscriber-level access and above, to = inject arbitrary web scripts in pages that will execute whenever a user acc= esses an injected page. The vulnerability was partially patched in version = 5.9.8.5. 2026-06-23 6.4 CVE-2026-4610 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-4610 ] metagauss--RegistrationMagic Custom Registration Forms, Use=
    r Registration, Payment, and User Login The RegistrationMagic - Custom Regi= stration Forms, User Registration, Payment, and User Login plugin for WordP= ress is vulnerable to Authentication Bypass via Insufficient Verification o=
    f Data Authenticity in all versions up to and including 6.0.8.6. This is du=
    e to the PayPal IPN `callback` handler being registered as a nopriv AJAX ac= tion with no authentication or nonce requirement, and critically because th=
    e handler updates the payment log database row with attacker-controlled POS=
    T data - including `payment_status` and the `custom` field encoding the tar= get `user_id` - before PayPal IPN validation is performed, meaning the data= base remains poisoned even when validation subsequently fails. This makes i=
    t possible for unauthenticated attackers to authenticate as any WordPress u= ser, including administrators, by submitting a forged IPN request that over= writes a payment log entry's `user_id` with that of a target account, then = visiting the success return URL with a legitimately obtained security hash =
    to cause the plugin to issue real WordPress authentication cookies for the = targeted account. 2026-06-27 5.3 CVE-2026-9242 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-9242 ] Mintplex-Labs--anything-llm AnythingLLM is an appl= ication that turns pieces of content into context that any LLM can use as r= eferences during chatting. Prior to 1.13.0, on Windows, the document folder=
    listing route can accept an encoded absolute Windows path that resolves ou= tside the intended documents directory. The shared path containment helper = rejects POSIX-style "../" traversal but does not reject Windows-style paren=
    t paths returned by path.relative(), such as "..". This vulnerability is fi= xed in 1.13.0. 2026-06-24 4.3 CVE-2026-48789 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-48789 ] mirsoftware--MIR blocks and shortcodes The MIR bloc=
    ks and shortcodes plugin for WordPress is vulnerable to Stored Cross-Site S= cripting via the 'title' attribute (and other attributes such as 'ready_ani= mation_text') of the 'msc_stats' shortcode in versions up to, and including=
    , 1.0.0. This is due to insufficient input sanitization and output escaping=
    on user supplied shortcode attributes inside the msc_stats() rendering fun= ction. This makes it possible for authenticated attackers, with contributor= -level access and above, to inject arbitrary web scripts in pages that will=
    execute whenever a user accesses an injected page. 2026-06-24 6.4 CVE-2026= -8896 [ https://www.cve.org/CVERecord?id=3DCVE-2026-8896 ] MLflow--MLflow A=
    vulnerability has been found in MLflow up to 4666cffc7912ea606d592fc38d6a7= 5e2935f65e7. The impacted element is an unknown function of the component E= xperiment-scoped Label Schema CRUD API. Such manipulation leads to missing = authorization. It is possible to launch the attack remotely. A high complex= ity level is associated with this attack. The exploitability is regarded as=
    difficult. The exploit has been disclosed to the public and may be used. A=
    reply to the GitHub issue explains, that "[t]he labeling schema PR has not=
    been merged yet. The auth handlers will be added before the release." 2026= -06-28 5 CVE-2026-13484 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13484=
    ] motioneye-project--motioneye motionEye (mEye) is an online interface for=
    motion software, which is a video surveillance program with motion detecti= on. Versions prior to 0.44.0 are vulnerable to path traversal in the pictur=
    e and movie API endpoints, suhc as /picture/{id}/preview/{filename}. Neithe=
    r the API handlers, nor the mediafiles.py functions such as get_media_previ= ew() check for .. sequences in the filename parameter, except for get_media= _content(). This allows an authenticated user with normal (non-admin) privi= leges to read arbitrary files from the filesystem as the motionEye process = user, such as: /etc/passwd, /etc/shadow, motionEye config files containing = password hashes and plaintext passwords, SSH keys, and other cameras' surve= illance footage. This issue has been fixed in version 0.44.0. 2026-06-24 6.=
    5 CVE-2026-31978 [ https://www.cve.org/CVERecord?id=3DCVE-2026-31978 ] moti= oneye-project--motioneye motionEye (mEye) is an online interface for motion=
    software, a video surveillance program with motion detection. Versions pri=
    or to 0.44.0 create the configuration file /etc/motioneye/motion.conf with = 644 permissions (-rw-r--r--), making it readable by any local user on the s= ystem. This file contains sensitive data including the admin password hash,=
    which can be leveraged by other vulnerabilities to escalate privileges. Ad= ditionally, per-camera configuration files (camera-*.conf) are also created=
    with the same 644 permissions, potentially exposing camera-specific creden= tials and settings. The exposed SHA1 admin password hash can be cracked off= line to recover the plaintext password, used directly to forge authenticate=
    d admin API requests via the signature authentication weakness (GHSA-45h7-4= 99j-7ww3), and chained with the OS command injection flaw (CVE-2025-60787) =
    to escalate a local unprivileged user to the Motion daemon user (often root=
    ), enabling full system compromise. This issue has been fixed in version 0.= 44.0. 2026-06-24 5.5 CVE-2026-32315 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-32315 ] motordesk--MotorDesk The MotorDesk plugin for WordPress is v= ulnerable to Cross-Site Request Forgery in all versions up to, and includin=
    g, 1.1.2. This is due to missing or incorrect nonce validation on the motor= desk_admin_home function. This makes it possible for unauthenticated attack= ers to update the plugin's configuration settings, including the search pag=
    e URI and custom template directory path via a forged request granted they = can trick a site administrator into performing an action such as clicking o=
    n a link. 2026-06-24 4.3 CVE-2026-9724 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-9724 ] myCred--License Manager for WooCommerce Unauthenticated = Insecure Direct Object References (IDOR) in License Manager for WooCommerce=
    <=3D 3.0.15 versions. 2026-06-25 6.5 CVE-2026-56013 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-56013 ] MyScale--MyScaleDB A security flaw has been=
    discovered in MyScale MyScaleDB up to 1.8.0. This vulnerability affects th=
    e function SegmentId::getCacheKey in the library src/VectorIndex/Common/Seg= mentId.h. The manipulation results in insufficient verification of data aut= henticity. It is possible to launch the attack remotely. A high complexity = level is associated with this attack. It is stated that the exploitability =
    is difficult. The exploit has been released to the public and may be used f=
    or attacks. The pull request to fix this issue awaits acceptance. 2026-06-2=
    8 5 CVE-2026-13513 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13513 ] n8= n--n8n n8n before 1.123.25 (1.x) and before 2.11.2 (2.x), with the fix also=
    included in 2.12.0, contains a stored cross-site scripting vulnerability i=
    n the Form Trigger node's CSS sanitization that allows authenticated users =
    to inject malicious scripts. Attackers with workflow creation permissions c=
    an inject XSS payloads that execute persistently for all form visitors, ena= bling form hijacking and phishing attacks. 2026-06-24 5.4 CVE-2026-56358 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-56358 ] n8n--n8n n8n before 1.1= 23.15 and 2.5.0 contains a webhook forgery vulnerability in the GitHub Webh= ook Trigger node that fails to implement HMAC-SHA256 signature verification=
    . Attackers who know the webhook URL can send unsigned POST requests to tri= gger workflows with arbitrary data, spoofing GitHub webhook events. 2026-06= -22 4 CVE-2026-56357 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56357 ] = nanocoai--nanoclaw NanoClaw before 2.1.17 contains a privilege escalation v= ulnerability in the handleApprovalsResponse function that fails to verify r= esponder role authorization. Attackers with a valid questionId can approve =
    or reject privileged actions like package installation by submitting approv=
    al response payloads without proper role validation. 2026-06-23 6.5 CVE-202= 6-56402 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56402 ] nanocoai--nan= oclaw NanoClaw before 2.1.17 contains a symlink following vulnerability in = forwardAttachedFiles that allows container-controlled agents to exfiltrate = host-readable files. The host validates attachment filenames using only isS= afeAttachmentName before copying with fs.copyFileSync, which follows symlin=
    ks without containment checks, allowing malicious agents to disclose arbitr= ary host files. 2026-06-23 5.5 CVE-2026-56692 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-56692 ] nanocoai--nanoclaw NanoClaw before 2.1.17 contains=
    a privilege escalation vulnerability in the create_agent delivery-action h= andler that performs privileged central-database writes without host-side a= uthorization checks. Confined agent containers can invoke create_agent to c= reate arbitrary agent groups, container configurations, and destinations, e= scalating beyond their intended confinement boundary. 2026-06-23 5.5 CVE-20= 26-56693 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56693 ] nanocoai--na= noclaw NanoClaw before 2.1.0 contains a privilege escalation vulnerability =
    in the channel-registration approval flow where handleChannelApprovalRespon=
    se fails to validate admin privileges over target agent groups. Scoped admi=
    ns can submit forged or stale connect callback values to wire messaging cha= nnels into out-of-scope agent groups, exposing unauthorized groups to unapp= roved channels and enabling unauthorized observation or control of restrict=
    ed agent group activity. 2026-06-23 5.4 CVE-2026-56694 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-56694 ] Nelio Software--Nelio Content Contributor=
    Broken Access Control in Nelio Content <=3D 4.3.4 versions. 2026-06-26 4.3=
    CVE-2026-57648 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57648 ] Netwo= rkConfiguration--dhcpcd dhcpcd through 10.3.2, fixed in commit 708b4a5, con= tains a memory leak vulnerability in the IPv6 Router Advertisement route in= formation handling that allows an unauthenticated same-link attacker to cau=
    se denial of service by sending crafted Router Advertisements. Attackers ca=
    n repeatedly send Router Advertisements containing Route Information option=
    s with a lifetime of zero, triggering unfreed allocations in routeinfo_find= alloc() that cause linear memory exhaustion and eventual daemon crash. 2026= -06-23 6.5 CVE-2026-56116 [ https://www.cve.org/CVERecord?id=3DCVE-2026-561=
    16 ] NetworkConfiguration--dhcpcd dhcpcd through 10.3.2, fixed in commit 57= 33d3c, contains a heap use-after-free vulnerability that allows unauthentic= ated same-link attackers to crash the daemon by sending a crafted DHCPv6 RE= NEW reply with RFC6603 OPTION_PD_EXCLUDE and both preferred and valid lifet= imes set to zero. Attackers acting as or impersonating a DHCPv6 server can = trigger dhcp6_deprecatedele() to free a delegated child address while an ou= ter TAILQ_FOREACH_SAFE iterator in dhcp6_deprecateaddrs() still holds the f= reed pointer, causing a use-after-free when TAILQ_REMOVE is reached. 2026-0= 6-23 5.3 CVE-2026-56113 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56113=
    ] NetworkConfiguration--dhcpcd dhcpcd through 10.3.2, fixed in commit 2f00= c7b, contains a one-byte stack out-of-bounds write vulnerability in dhcp6_m= akemessage() in src/dhcp6.c that allows unauthenticated same-link attackers=
    to write beyond a fixed local buffer by serializing an oversized RFC6603 O= PTION_PD_EXCLUDE option body. Attackers can send a crafted DHCPv6 ADVERTISE=
    message containing an IA_PD IAPREFIX /0 with a valid OPTION_PD_EXCLUDE usi=
    ng an exclude prefix length of /121 through /128 to trigger the out-of-boun=
    ds write and potentially corrupt adjacent stack memory. 2026-06-23 5.3 CVE-= 2026-56114 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56114 ] NetworkCon= figuration--dhcpcd dhcpcd through 10.3.2, fixed in commit 78ea09e, contains=
    a heap use-after-free vulnerability in the control socket handling within = src/control.c that allows local unprivileged attackers to trigger memory co= rruption when privilege separation is disabled. Attackers can connect to th=
    e control socket and send a privileged command such as -x, causing control_= recvdata() to free the client object while the same READ+HANGUP event subse= quently reaches control_hangup() with the stale pointer, resulting in a use= -after-free condition exploitable in deployments using --disable-privsep or=
    where privsep initialization has failed with the control socket operating =
    in mode 0666. 2026-06-23 4.7 CVE-2026-56117 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-56117 ] Nexcess--WPComplete Subscriber Broken Access Control=
    in WPComplete <=3D 2.9.5.5 versions. 2026-06-26 5.4 CVE-2026-57661 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-57661 ] nghttp2--nghttp2 nghttp2's n= ghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also = carries a Content-Length header and body onto reusable keep-alive backend c= onnections, re-adding the Upgrade and Connection headers while passing Cont= ent-Length verbatim. A backend that resolves the resulting ambiguous messag=
    e in the attacker's favor enables HTTP request/response smuggling and cross= -client response-queue poisoning. 2026-06-28 5.4 CVE-2026-58055 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-58055 ] nicolargo--glances Glances is an=
    open-source system cross-platform monitoring tool. Prior to 4.5.5, the Gla= nces XML-RPC server (glances -s, implemented in glances/server.py) does not=
    validate the HTTP Host header, leaving it vulnerable to DNS rebinding atta= cks. An attacker can exploit DNS rebinding to exfiltrate the full system mo= nitoring dataset from a victim's browser. This vulnerability is fixed in 4.= 5.5. 2026-06-25 5.3 CVE-2026-46611 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-46611 ] nK--Ghost Kit Contributor Cross Site Scripting (XSS) in Ghost=
    Kit <=3D 3.6.0 versions. 2026-06-26 6.5 CVE-2026-57651 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-57651 ] Nmap--Nmap Nmap through 7.99 does not ke=
    ep the IPv6 extension-header walk within the captured packet in ipv6_get_da= ta_primitive (libnetutil/netutil.cc), so the pointer advances past the buff=
    er and the remaining-length computation underflows to a large value. A scan= ned target or on-path attacker returning a crafted IPv6 response with a tru= ncated extension header can trigger out-of-bounds reads and a crash during = raw IPv6 scans. 2026-06-28 6.5 CVE-2026-58058 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-58058 ] nocodb--nocodb NocoDB is software for building dat= abases as spreadsheets. Prior to 2026.04.1, a reflected XSS vulnerability e= xists in the Page Leaving Warning page. The ncRedirectUrl and ncBackUrl que=
    ry parameters are used in window.location.href and <a> tag bindings without=
    validation, allowing javascript: URI injection. This vulnerability is fixe=
    d in 2026.04.1. 2026-06-23 6.1 CVE-2026-46547 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-46547 ] nocodb--nocodb NocoDB is software for building dat= abases as spreadsheets. Prior to 2026.04.4, the uploadViaURL path in the v1= /v2 attachment API did not enforce NC_ATTACHMENT_FIELD_SIZE against the rem= ote content-length or against the response stream. An authenticated user (E= ditor+) could direct the server to download arbitrarily large files, exhaus= ting disk space and causing denial of service. In packages/nocodb/src/servi= ces/attachments.service.ts, the HEAD probe read content-length but never co= mpared it to NC_ATTACHMENT_FIELD_SIZE; the subsequent storageAdapter.fileCr= eateByUrl() performed the download without maxContentLength. This vulnerabi= lity is fixed in 2026.04.4. 2026-06-23 6.5 CVE-2026-46551 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-46551 ] nocodb--nocodb NocoDB is software for = building databases as spreadsheets. Prior to 2026.04.1, an authenticated us=
    er with columnAdd permission on a Postgres-backed base can inject arbitrary=
    SQL into the formula engine via the optional direction argument of ARRAYSO= RT(...). The value is unrestricted by formula validation and embedded into =
    a knex.raw ORDER BY clause, executing during column creation and on every s= ubsequent record read of the formula column. The vulnerability is specific =
    to the Postgres mapping for ARRAYSORT in packages/nocodb/src/db/functionMap= pings/pg.ts. This vulnerability is fixed in 2026.04.1. 2026-06-23 6 CVE-202= 6-47375 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47375 ] nocodb--nocod=
    b NocoDB is software for building databases as spreadsheets. Prior to 2026.= 04.1, the refresh-token cookie was set with httpOnly: true but missing both=
    the secure flag and the sameSite attribute. Over plain HTTP the cookie cou=
    ld be intercepted on the network; without sameSite, browsers attached it to=
    cross-site POSTs, enabling CSRF against the token-refresh endpoint. This v= ulnerability is fixed in 2026.04.1. 2026-06-23 5.4 CVE-2026-46550 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-46550 ] nocodb--nocodb NocoDB is softw= are for building databases as spreadsheets. Prior to 2026.04.1, shared-base=
    sessions were granted the same base-member capabilities as authenticated v= iewers. Using only the shared-base UUID (xc-shared-base-id), an attacker co= uld enumerate base members and invite an arbitrary email into the base as a=
    real member. The invited user could then redeem the invite via the normal = signup flow and retain authenticated access even after the owner revoked th=
    e shared link. Shared-base sessions were mapped to ProjectRoles.VIEWER in p= ackages/nocodb/src/strategies/base-view.strategy/base-view.strategy.ts, and=
    packages/nocodb/src/utils/acl.ts granted baseUserList and userInvite to th=
    at role. The shared frontend (packages/nc-gui/composables/useApi/intercepto= rs.ts) deliberately removed auth headers in favour of the shared-base heade=
    r, but the ACL middleware did not distinguish shared sessions from genuine = viewers. This vulnerability is fixed in 2026.04.1. 2026-06-23 5.8 CVE-2026-= 46552 [ https://www.cve.org/CVERecord?id=3DCVE-2026-46552 ] nocodb--nocodb = NocoDB is software for building databases as spreadsheets. Prior to 2026.04= .1, the request-filtering-agent SSRF protection was non-functional in the f= our notification webhook plugins (Slack, Discord, Mattermost, Teams) becaus=
    e httpAgent / httpsAgent were passed as part of the request body rather tha=
    n the axios config. An authenticated user with hook-creation permission cou=
    ld direct outbound POST requests to arbitrary internal hosts. This vulnerab= ility is fixed in 2026.04.1. 2026-06-23 4.3 CVE-2026-46548 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-46548 ] nodeca--js-yaml js-yaml is a JavaScri=
    pt YAML parser and dumper. Prior to 4.2.0, a crafted YAML document can trig= ger algorithmic CPU exhaustion in js-yaml merge-key processing (<<) by repe= ating the same alias many times in a merge sequence. This causes quadratic = parse-time behavior relative to input size and can block a Node.js worker/e= vent loop for seconds with a relatively small payload (tens of KB), resulti=
    ng in denial of service. The issue is in merge handling inside lib/loader.j=
    s. This vulnerability is fixed in 4.2.0. 2026-06-22 5.3 CVE-2026-53550 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-53550 ] Noor Alam--Gmail SMTP Una= uthenticated Cross Site Request Forgery (CSRF) in Gmail SMTP <=3D 1.2.3.19 = versions. 2026-06-26 4.3 CVE-2026-57657 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-57657 ] notepad-plus-plus--notepad-plus-plus Notepad++ is a fre=
    e and open-source source code editor. Prior to 8.9.6.1, a local process in = the same interactive Windows session can send a malformed WM_COPYDATA messa=
    ge to Notepad++ using the COPYDATA_FULL_CMDLINE path. The handler appears t=
    o process COPYDATASTRUCT.lpData as an unbounded NUL-terminated wchar_t* ins= tead of enforcing COPYDATASTRUCT.cbData. This vulnerability is fixed in 8.9= .6.1. 2026-06-26 5 CVE-2026-48770 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-48770 ] nrwl--nx Nx is a monorepo solution for TypeScript and polyglot=
    codebases. From 17.0.4 until 22.7.2 and 23.0.0-beta.2, the local HTTP serv=
    er started by nx graph sent Access-Control-Allow-Origin: * on every respons=
    e, letting any website a developer visited read the server's responses cros= s-origin - including the full project graph and the output of the /help end= point, which runs a target's configured help command. The practical impact =
    is typically cross-origin information disclosure, but can be arbitrary comm= and injection in rare cases. This vulnerability is fixed in 22.7.2 and 23.0= .0-beta.2. 2026-06-26 5.9 CVE-2026-54753 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54753 ] Nuxt--Nuxt Nuxt versions 4.0.0 before 4.4.7 and 3.x bef= ore 3.21.7 contain a server-side open redirect vulnerability in navigateTo = that fails to properly validate path-normalized payloads like /..//evil.com=
    and /.//evil.com. Attackers can bypass external-host checks using path-nor= malization techniques to redirect users to attacker-controlled sites via th=
    e Location header or meta-refresh, enabling phishing and OAuth authorizatio= n-code theft. 2026-06-22 6.1 CVE-2026-56326 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-56326 ] Nuxt--Nuxt Nuxt versions 4.0.0 before 4.4.7 and 3.x = before 3.21.7 accept protocol-relative paths such as //evil.com in the relo= adNuxtApp function; these pass the script-protocol check but resolve to a c= ross-origin URL against the current page protocol. Attackers can inject pat=
    hs like //evil.com to redirect users to attacker-controlled hosts, enabling=
    phishing and OAuth authorization-code theft. 2026-06-22 6.1 CVE-2026-56697=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-56697 ] Nuxt--Nuxt Nuxt vers= ions 4.0.0 before 4.4.7 and 3.x before 3.21.7 fail to validate script-capab=
    le URLs in the navigateTo open option, allowing client-side script executio=
    n. Attackers can supply javascript: URLs through the open parameter to exec= ute arbitrary scripts in the application's origin when user-controlled inpu=
    t is passed to navigateTo. 2026-06-22 6.1 CVE-2026-56698 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-56698 ] Nuxt--Nuxt Nuxt 4.0.0 before 4.4.7 and = 3.18.0 before 3.21.7, when running the development server (nuxt dev) on Lin= ux, binds the vite-node IPC server to an abstract-namespace Unix socket wit= hout permission restrictions, allowing local users to enumerate and connect=
    . Unprivileged co-resident users can exploit the unprotected module request=
    handler to read arbitrary files such as .env and SSH keys through the SSR = plugin pipeline. Production builds are unaffected, as the IPC server runs o= nly in development. 2026-06-23 5.5 CVE-2026-56301 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-56301 ] Omnisend--Email Marketing for WooCommerce by O= mnisend Subscriber Broken Access Control in Email Marketing for WooCommerce=
    by Omnisend <=3D 1.19.0 versions. 2026-06-26 5.4 CVE-2026-57632 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-57632 ] Opal_WP--Auros Core Unauthentic= ated Content Injection in Auros Core <=3D 5.3.1 versions. 2026-06-26 5.3 CV= E-2025-64637 [ https://www.cve.org/CVERecord?id=3DCVE-2025-64637 ] open-tel= emetry--opentelemetry-js opentelemetry-js is the OpenTelemetry JavaScript C= lient. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/cor=
    e does not enforce size limits when parsing inbound baggage HTTP headers. T=
    he W3C Baggage specification recommends a maximum of 8,192 bytes and 180 en= tries; these limits were only enforced on the outbound (inject()) path, not=
    on the inbound (extract()) path. Parsing oversized baggage causes memory a= llocation proportional to the header size without any cap. This vulnerabili=
    ty is fixed in 2.8.0. 2026-06-22 5.3 CVE-2026-54285 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-54285 ] open-webui--open-webui Open WebUI is a self-= hosted artificial intelligence platform designed to operate entirely offlin=
    e. Prior to 0.9.6, POST /api/chat/completions accepts an image_url.url valu=
    e that, when it does NOT start with http://, https://, or data:image/, is i= nterpreted as a file id and resolved against the global file table with no = ownership check. an authenticated user can therefore set image_url.url to a= nother user's file id, the server reads that file from disk, base64-encodes=
    it, and injects the data URI into the LLM request. the user then prompts t=
    he LLM to describe / OCR the file and reads the content back. This vulnerab= ility is fixed in 0.9.6. 2026-06-23 6.5 CVE-2026-54009 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-54009 ] open-webui--open-webui Open WebUI is a se= lf-hosted artificial intelligence platform designed to operate entirely off= line. Prior to 0.9.6, Open WebUI's prompt version-history endpoints authori=
    ze the prompt_id in the URL but then act on caller-supplied history IDs wit= hout verifying that the history row belongs to that prompt (history_entry.p= rompt_id =3D=3D prompt.id). This affects /api/v1/prompts/id/{prompt_id}/his= tory/diff, /api/v1/prompts/id/{prompt_id}/update/version, and /api/v1/promp= ts/id/{prompt_id}/history/{history_id}. An authenticated user with access t=
    o any prompt they control, plus a victim prompt_history.id, can read or del= ete another user's private prompt history. This vulnerability is fixed in 0= .9.6. 2026-06-23 6.4 CVE-2026-54015 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-54015 ] open-webui--open-webui Open WebUI is a self-hosted artificia=
    l intelligence platform designed to operate entirely offline. Prior to 0.9.=
    6, Open WebUI added collection-level ACL checks, but the patch can still be=
    bypassed when Milvus multitenancy mode is enabled. The ACL allows unknown = non-KB collection names as legacy/ephemeral collections. In Milvus multiten= ancy mode, that user-controlled collection name becomes a resource_id and i=
    s interpolated into a Milvus expression without escaping. This is caused by=
    an incomplete fix for CVE-2026-44560 This vulnerability is fixed in 0.9.6.=
    2026-06-23 6.5 CVE-2026-54019 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-54019 ] open-webui--open-webui Open WebUI is a self-hosted artificial int= elligence platform designed to operate entirely offline. Prior to 0.9.6, se= veral direct, index-addressed Ollama proxy routes accept a caller-supplied = url_idx path parameter and use it as a raw index into the admin-configured = OLLAMA_BASE_URLS list. Access control on these routes validates only whethe=
    r the user may use the requested model, never which backend the request is = routed to. Any authenticated user can append an arbitrary url_idx to force = their request onto an Ollama backend they were never authorized to reach, i= ncluding internal, higher-privilege, or explicitly admin-disabled backends.=
    This vulnerability is fixed in 0.9.6. 2026-06-23 6.3 CVE-2026-54021 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-54021 ] open-webui--open-webui Open=
    WebUI is a self-hosted artificial intelligence platform designed to operat=
    e entirely offline. Prior to 0.8.11, the ydoc:document:join Socket.IO handl=
    er checks note ownership only when the document_id starts with note: (colon=
    ). However, the YdocManager storage layer normalizes all document IDs by re= placing colons with underscores (document_id.replace(":", "_")). An attacke=
    r can join a document room using note_<id> (underscore) instead of note:<id=
    (colon), bypassing the authorization check entirely while accessing the s=
    ame underlying Yjs document. The server then returns the full document stat=
    e, leaking the victim's private note contents. This vulnerability is fixed =
    in 0.8.11. 2026-06-23 5.3 CVE-2026-54022 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54022 ] open-webui--open-webui Open WebUI is a self-hosted arti= ficial intelligence platform designed to operate entirely offline. Prior to=
    0.9.6, POST /api/v1/calendars/events/{event_id}/update validates that the = caller has write access to the calendar the event currently belongs to, but=
    does not validate the destination calendar_id supplied in the request body=
    . The model layer then persists the new calendar_id unconditionally. A regu= lar user-role account can therefore create an event in their own calendar a=
    nd immediately move it into any other user's calendar whose ID they know - = bypassing the authorization check that create_event correctly performs. Thi=
    s vulnerability is fixed in 0.9.6. 2026-06-23 4.3 CVE-2026-54006 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-54006 ] open-webui--open-webui Open Web=
    UI is a self-hosted artificial intelligence platform designed to operate en= tirely offline. Prior to 0.9.6, a path traversal vulnerability exists in op= en-webui's cache file serving endpoint that allows any authenticated user t=
    o read files from sibling directories outside the intended cache directory,=
    by exploiting an incomplete startswith containment check that lacks a trai= ling path separator. The root cause is that serve_cache_file() in open_webu= i/main.py validates the resolved path with file_path.startswith(os.path.abs= path(CACHE_DIR)) - without appending os.sep. This allows any path resolving=
    to a sibling directory whose name begins with cache (e.g. cache_sibling, c= ache_backup, cached_models) to pass validation. This vulnerability is fixed=
    in 0.9.6. 2026-06-23 4.3 CVE-2026-54014 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54014 ] open-webui--open-webui Open WebUI is a self-hosted arti= ficial intelligence platform designed to operate entirely offline. Prior to=
    0.9.6, Open WebUI has a Broken Object Level Authorization (BOLA) vulnerabi= lity in the builtin search_knowledge_files tool. When native function calli=
    ng is enabled and the selected model has no attached knowledge bases, an au= thenticated user can call search_knowledge_files with an arbitrary knowledg= e_id. The function then returns file metadata from that knowledge base with= out checking whether the user has read access. This allows unauthorized enu= meration of private or restricted knowledge base files. This vulnerability =
    is fixed in 0.9.6. 2026-06-23 4.3 CVE-2026-54016 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-54016 ] opf--openproject OpenProject is open-source, we= b-based project management software. Prior to 17.3.2 and 17.4.0, a Missing = Authorization vulnerability exists in OpenProject's CostReportsController. = The rename and update actions allow any authenticated user to modify the na= me, filters, and grouping of any Public cost report in the system without v= erifying ownership or permission level. An attacker who discovers or guesse=
    s a public report's numeric ID can rename or overwrite its filter configura= tion without any warning to the report's owner. This vulnerability is fixed=
    in 17.3.2 and 17.4.0. 2026-06-26 6.5 CVE-2026-44734 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-44734 ] opf--openproject OpenProject is open-source=
    , web-based project management software. Prior to 17.3.2 and 17.4.0, the GE=
    T /api/v3/shares endpoint returns share details for ALL work packages in a = project to any user with the view_shared_work_packages permission. The auth= orization check operates at the project level only - it does not verify the=
    requesting user can actually view each individual shared work package. Thi=
    s allows a regular project member to discover work package IDs and subjects=
    (including confidential titles), which users have been granted shared acce= ss, what role level was assigned (Editor, Commenter, Viewer). This vulnerab= ility is fixed in 17.3.2 and 17.4.0. 2026-06-26 6.5 CVE-2026-44735 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-44735 ] opf--openproject OpenProject =
    is open-source, web-based project management software. Prior to 17.4.0, the=
    GET /api/v3/relations endpoint allows any authenticated user to retrieve r= elations - and the subject (title) of work packages they have no permission=
    to view - by supplying an arbitrary work package ID in the involved, fromI=
    d, or toId filter. This bypasses the Relation.visible scope due to a flawed=
    performance optimization in RelationQuery. This vulnerability is fixed in = 17.4.0. 2026-06-26 6.5 CVE-2026-44736 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-44736 ] opf--openproject OpenProject is open-source, web-based pro= ject management software. Prior to 17.3.3 and 17.4.1, the HTML sanitizer gr= ants <macro> elements unrestricted data-* attributes via :data wildcard. An=
    attacker injects data-controller=3D"poll-for-changes" into a work package = description, causing Stimulus.js to mount a controller that fetches an atta= cker-uploaded attachment and passes it to renderStreamMessage(). This execu= tes arbitrary Turbo Stream actions - including redirect_to - in every victi= m's authenticated browser session, redirecting them to an attacker-controll=
    ed server. This vulnerability is fixed in 17.3.3 and 17.4.1. 2026-06-26 6.4=
    CVE-2026-52781 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52781 ] opf--= openproject OpenProject is open-source, web-based project management softwa= re. Prior to 17.4.0, OpenProject's rich text (markdown) rendering pipeline = uses Sanitize::Config::RELAXED[:css] for inline style sanitization. This co= nfiguration permits essentially all CSS properties in style attributes on p= ermitted HTML elements (figure, img, table, th, tr, td). This allows any au= thenticated user with write access to formattable text fields (work package=
    descriptions, comments, project descriptions, news) to inject CSS This vul= nerability is fixed in 17.4.0. 2026-06-26 5.7 CVE-2026-44696 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-44696 ] opf--openproject OpenProject is ope= n-source, web-based project management software. Prior to 17.3.2 and 17.4.0=
    , Business Logic Error on OpenProject through PATCH request to /api/v3/user= s/me permits to bypass password requirements. A password validation flaw in=
    the change password behavior allows attackers to change a user's password = only with an active session takeover. This vulnerability is fixed in 17.3.2=
    and 17.4.0. 2026-06-26 5.9 CVE-2026-44733 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-44733 ] opf--openproject OpenProject is open-source, web-base=
    d project management software. Prior to 17.3.3 and 17.4.1, a cross-project = IDOR / authorization context confusion in the Calendar and Team Planner mod= ules allows a user with management permissions in one project to delete pub= lic Calendar or Team Planner Queries from another project where they do not=
    have the corresponding management permissions. Both modules authorize the = request against the project identified by :project_id in the URL, but the a= ctual Query object is loaded later by :id from Query.visible(current_user) = without verifying that the loaded Query belongs to the authorized project. =
    As a result, an attacker can use permissions from Project A to delete share= d/public Calendar or Team Planner views from Project B, causing integrity i= mpact and limited availability impact for users relying on those shared vie= ws. This vulnerability is fixed in 17.3.3 and 17.4.1. 2026-06-26 5.4 CVE-20= 26-52779 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52779 ] opf--openpro= ject OpenProject is open-source, web-based project management software. Pri=
    or to 17.3.2 and 17.4.0, the web application's meetings filter feature leak=
    s whether a given user ID corresponds to a valid account and discloses the = user's full name, allowing an attacker to enumerate all existing user accou= nts by probing user IDs and observing differences in the server response. T= his vulnerability is fixed in 17.3.2 and 17.4.0. 2026-06-26 4.3 CVE-2026-44= 731 [ https://www.cve.org/CVERecord?id=3DCVE-2026-44731 ] opf--openproject = OpenProject is open-source, web-based project management software. Prior to=
    17.3.2 and 17.4.0, OpenProject exposes a document update endpoint used to = modify existing documents. The target document is loaded with visibility ch= ecks and then updated. During update, attacker-controlled attributes are ap= plied to the persisted record before authorization is enforced. As a result=
    , a user without :manage_documents in the source project can move and modif=
    y foreign project documents by setting project_id in a single PATCH request=
    . This vulnerability is fixed in 17.3.2 and 17.4.0. 2026-06-26 4.3 CVE-2026= -44732 [ https://www.cve.org/CVERecord?id=3DCVE-2026-44732 ] opf--openproje=
    ct OpenProject is open-source, web-based project management software. Prior=
    to 17.4.0, `GET /api/v3/meetings/:meeting_id/agenda_items/:agenda_item_id`=
    discloses private work package data from a linked work package that belong=
    s to a private/inaccessible project. This vulnerability is fixed in 17.4.0.=
    2026-06-26 4.3 CVE-2026-49355 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-49355 ] osiris8--Osiris Signature Banner The Osiris Signature Banner plug=
    in for WordPress is vulnerable to Cross-Site Request Forgery in all version=
    s up to, and including, 0.5. This is due to missing or incorrect nonce vali= dation on a function. This makes it possible for unauthenticated attackers =
    to update settings and inject malicious web scripts via a forged request gr= anted they can trick a site administrator into performing an action such as=
    clicking on a link. 2026-06-24 6.1 CVE-2026-8905 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-8905 ] owencutajar--EntreDroppers The EntreDroppers pl= ugin for WordPress is vulnerable to Reflected Cross-Site Scripting via PHP_= SELF Parameter in all versions up to, and including, 1.1.2 due to insuffici= ent input sanitization and output escaping. This makes it possible for unau= thenticated attackers to inject arbitrary web scripts in pages that execute=
    if they can successfully trick a user into performing an action such as cl= icking on a link. The payload is delivered via attacker-controlled path-inf=
    o in the URL (e.g., /wp-admin/admin.php/"><script>alert(0)</script>/?page= =3DEntreDroppers.php), which PHP_SELF reflects directly into the form actio=
    n attribute. 2026-06-24 6.1 CVE-2026-8628 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-8628 ] paradigmatools--Avalon23 Products Filter for WooCommerc=
    e The Avalon23 Products Filter for WooCommerce plugin for WordPress is vuln= erable to Stored Cross-Site Scripting via the 'avalon23_qr' shortcode in al=
    l versions up to, and including, 1.1.6. This is due to insufficient input s= anitization and output escaping on user-supplied shortcode attributes (nota= bly 'title' and 'fixed_link') which are concatenated directly into single-q= uoted HTML attributes by the AVALON23_HELPER::draw_html_item() helper witho=
    ut esc_attr() or any other encoding. This makes it possible for authenticat=
    ed attackers, with Contributor-level access and above, to inject arbitrary = web scripts in pages that will execute whenever a user accesses an injected=
    page. 2026-06-24 6.4 CVE-2026-8865 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-8865 ] peregrinethemes--Hester Core Author Cross Site Scripting (XSS=
    ) in Hester Core <=3D 1.1.8 versions. 2026-06-26 5.9 CVE-2026-57656 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-57656 ] phpseclib--phpseclib phpsecl=
    ib is a PHP secure communications library. From 0.1.1 until 1.0.30, 2.0.55,=
    and 3.0.54, when an application validates an untrusted X.509 certificate w= ith phpseclib, X509::validateSignature() reads a URL out of that certificat= e's Authority Information Access (AIA) extension and connects to it. Attack=
    er who supplies certificate fully controls host, port, and path of that con= nection. URL fetching is enabled by default, and no destination is blocked.=
    An unauthenticated attacker can therefore make a validating server open co= nnections to internal hosts and ports it should never reach, for example lo= opback 127.0.0.1, cloud metadata address 169.254.169.254, and internal-only=
    services. This is a server-side request forgery (SSRF) caused by an insecu=
    re default. This vulnerability is fixed in 1.0.30, 2.0.55, and 3.0.54. 2026= -06-22 5.8 CVE-2026-55599 [ https://www.cve.org/CVERecord?id=3DCVE-2026-555=
    99 ] pixelwelt--Image Sizes on Demand The Image Sizes on Demand plugin for = WordPress is vulnerable to Reflected Cross-Site Scripting via PHP_SELF Serv=
    er Variable in all versions up to, and including, 1.3 due to insufficient i= nput sanitization and output escaping. This makes it possible for unauthent= icated attackers to inject arbitrary web scripts in pages that execute if t= hey can successfully trick a user into performing an action such as clickin=
    g on a link. The injected payload only executes in the context of an admini= strator, as the settings page requires the manage_options capability to ren= der. 2026-06-24 6.1 CVE-2026-8622 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-8622 ] pnpm--pnpm pnpm is a package manager. Prior to 10.34.0 and 11.4= .0, pnpm passes the lockfile-controlled git resolution.commit value to git = fetch without a -- separator or commit-format validation. For git dependenc= ies fetched through the shallow-fetch path, a malicious lockfile can replac=
    e the expected 40-character commit hash with a Git option such as --upload-= pack=3D<command>. For SSH and local transports, --upload-pack can execute t=
    he supplied command. HTTPS transports ignore --upload-pack, so the practica=
    l attack surface is primarily SSH or local git dependencies. This vulnerabi= lity is fixed in 10.34.0 and 11.4.0. 2026-06-25 6.4 CVE-2026-50014 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-50014 ] pnpm--pnpm pnpm is a package = manager. Prior to 10.34.0 and 11.4.0, pnpm's tarball extraction worker skip=
    s integrity verification when the integrity field is absent from the lockfi=
    le resolution. If an attacker can both modify pnpm-lock.yaml to remove the = integrity: field and cause the referenced registry URL to serve altered pac= kage content, pnpm install --frozen-lockfile can install the altered packag=
    e without an integrity error. npm's npm ci enforces integrity by default; p= npm's behavior of silently skipping verification is a pnpm-specific fail-op=
    en gap. This vulnerability is fixed in 10.34.0 and 11.4.0. 2026-06-25 6.8 C= VE-2026-50021 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50021 ] pnpm--p= npm pnpm is a package manager. Prior to 10.34.0 and 11.4.0, `pnpm install` =
    in non-frozen mode can accept new remote package content after detecting th=
    at the downloaded tarball does not match the integrity recorded in pnpm-loc= k.yaml. When a package is already locked with an integrity value, and the r= egistry later serves different metadata and tarball content for the same pa= ckage name and version, pnpm initially reports an integrity mismatch. Howev= er, plain pnpm install then performs a resolution repair, accepts the regis= try's new integrity, updates the lockfile, installs the new content, and ex= its successfully. This means the lockfile integrity check does not act as a=
    hard stop by default. This vulnerability is fixed in 10.34.0 and 11.4.0. 2= 026-06-25 6.8 CVE-2026-50573 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 50573 ] pnpm--pnpm pnpm is a package manager. Prior to 10.34.2 and 11.5.3, = pnpm and pacquet expanded ${ENV_VAR} placeholders from repository-controlle=
    d .npmrc and pnpm-workspace.yaml into registry request destinations and reg= istry credentials. A malicious repository could cause dependency resolution=
    to send victim environment secrets to an attacker-selected registry before=
    lifecycle scripts run. This vulnerability is fixed in 10.34.2 and 11.5.3. = 2026-06-25 6.5 CVE-2026-55180 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -55180 ] pnpm--pnpm pnpm is a package manager. Prior to 10.34.2 and 11.5.3,=
    Manifest bin object keys such as "", ".", and ".." passed pnpm's bin-name = guard. When a malicious package was installed globally, later global remove=
    , update, or add-replacement flows could re-derive those names from the ins= talled manifest and pass path.join(globalBinDir, binName) to removeBin. For=
    "." this targets the global bin directory; for ".." this targets its paren=
    t. This vulnerability is fixed in 10.34.2 and 11.5.3. 2026-06-25 6.5 CVE-20= 26-55699 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55699 ] podman-conta= iner-tools--podman Podman is a tool for managing OCI containers and pods. F= rom 3.0.0 until 5.7.1, running a malicious container image where the WORKDI=
    R path contains a symlink can create a directory or modify ownership on the=
    host filesystem. Modified ownership is less likely to happen as that requi= res help from an untrusted/malicious process that mutates the host filesyst=
    em tree during dereferencing of the WORKDIR path, to trigger a race conditi= on. This vulnerability is fixed in 5.7.1. 2026-06-26 5.3 CVE-2026-55686 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-55686 ] poweradmin--poweradmin P= oweradmin is a web-based DNS administration tool for PowerDNS server. Versi= ons prior to 4.2.4 and 4.3.3 are vulnerable to CSV Injection (Formula Injec= tion) in its log export functionality. User-controlled data - specifically = the username field - is written to exported CSV files without sanitizing fo= rmula trigger characters (=3D, +, -, @). When an administrator exports acti= vity logs and opens the resulting CSV in a spreadsheet application (Microso=
    ft Excel, LibreOffice Calc, Google Sheets), any formula stored in a usernam=
    e is executed by the application. This can be used for phishing attacks aga= inst administrators or data exfiltration. Versions 4.2.4 and 4.3.3 patch th=
    e issue. 2026-06-23 6.9 CVE-2026-47693 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-47693 ] PowerDNS--Authoritative An attacker can send a web requ= est that causes unlimited memory allocation in the internal web server, lea= ding to a denial of service. The internal web server is disabled by default=
    . 2026-06-25 4.3 CVE-2026-42005 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-42005 ] PowerDNS--DNSdist An attacker might be able to cause outgoing TC=
    P connections to backend to be stuck until a timeout occurs instead of bein=
    g released immediately, by sending IXFR queries. This could be used to caus=
    e a denial of service if there is a limit to the number of concurrent conne= ctions to this backend, or if the process runs out of file descriptors. 202= 6-06-25 5.3 CVE-2026-40209 [ https://www.cve.org/CVERecord?id=3DCVE-2026-40= 209 ] PowerDNS--DNSdist An attacker can send crafted DNS over HTTP/3 querie=
    s, triggering an exception that prevents some buffer from being freed right=
    away. The buffer will be freed at the end of the QUIC connection, but on s= ome setups it might be possible to open enough concurrent DoH3 streams to t= rigger an out-of-memory condition, resulting in a denial of service. 2026-0= 6-25 5.3 CVE-2026-40211 [ https://www.cve.org/CVERecord?id=3DCVE-2026-40211=
    ] PowerDNS--DNSdist An out-of-bounds read might happen when SetMacAddrActi=
    on is used, potentially resulting in uninitialized memory being sent over t=
    he network or a crash. 2026-06-25 4.8 CVE-2026-40210 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-40210 ] PowerDNS--Recursor ECS zero scoped answers = are stored in the packet cache while they should not. This impacts only con= figurations that have ECS enabled; 2026-06-25 5.3 CVE-2026-40012 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-40012 ] PowerDNS--Recursor A malicious = authoritative server can send a crafted zone via the ZoneToCache function t= hat leads to a crash of the Recursor due to insuffcient input validation. 2= 026-06-25 5.9 CVE-2026-42387 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 42387 ] PowerDNS--Recursor Incomplete validation of the SOA record present =
    in a catalog zone might lead to a crash. 2026-06-25 5.9 CVE-2026-42388 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-42388 ] PowerDNS--Recursor This f=
    ix provides extra hardening for the 5.4.x branch by doing extra validation =
    of incoming answers from authoritative servers. 2026-06-25 5.3 CVE-2026-423=
    89 [ https://www.cve.org/CVERecord?id=3DCVE-2026-42389 ] PowerDNS--Recursor=
    An invalid zone might pass ZONEMD validation while it should not. This is = only relevant if ZoneToCache is configured with ZONEMD validation. 2026-06-=
    25 5.3 CVE-2026-42390 [ https://www.cve.org/CVERecord?id=3DCVE-2026-42390 ]=
    PowerDNS--Recursor Spoofing replies to Recursor might mark an IP of an aut= horitative server as not supporting EDNS, causing valdiation of DNSSEC reco= rds served by that server to fail. 2026-06-25 5.9 CVE-2026-52690 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-52690 ] protobufjs--protobuf.js protobu= fjs compiles protobuf definitions into JavaScript (JS) functions. Prior to = 8.6.0 and 7.6.3, protobufjs accepted certain schema-derived names that coul=
    d collide with properties used by protobufjs runtime helpers. The known aff= ected names are fields named hasOwnProperty, field or oneof names such as $= type when loaded through protobufjs JSON/reflection descriptors, and servic=
    e methods whose generated helper name is rpcCall. When affected message or = service types were used, protobufjs could read schema-controlled data where=
    it expected an own-property helper, reflected type metadata, or the base R=
    PC helper. This could cause deterministic exceptions or recursive calls in = affected decode post-checks, verification, object conversion, reflected JSO=
    N serialization, or protobufjs RPC helper invocation. This vulnerability is=
    fixed in 8.6.0 and 7.6.3. 2026-06-22 5.3 CVE-2026-54269 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-54269 ] protobufjs--protobuf.js protobufjs comp= iles protobuf definitions into JavaScript (JS) functions. From 8.2.0 to 8.4= .2, protobufjs preserved unknown wire elements in message.$unknowns and did=
    not provide a decode-time option to discard unknown fields before retainin=
    g them. A crafted protobuf payload containing many unknown fields could the= refore cause a decoded message to retain substantially more memory than the=
    input size would suggest, even when unknown-field round-tripping is not ne= eded. protobufjs 8.5.0 added the relevant decode-time options, allowing app= lications that decode untrusted protobuf data to disable unknown-field rete= ntion during decode. protobufjs 8.6.2 flips the default so unknown fields a=
    re discarded unless explicitly opted into. 2026-06-22 5.3 CVE-2026-54270 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-54270 ] Pylons--webob WebOb pro= vides objects for HTTP requests and responses. Prior to 1.8.10, the normali= zation of the HTTP Location header during a redirect is vulnerable to an op=
    en redirect: WebOb joins the redirect target to the request URI using Pytho= n's urljoin, and since Python 3.10 the underlying urlsplit strips ASCII tab=
    , carriage return, and newline characters before parsing, so a redirect tar= get containing such characters can be reinterpreted as a protocol-relative = URL whose authority is an attacker-controlled host. This bypasses the CVE-2= 024-42353 fix that escaped a leading double slash, allowing an attacker who=
    influences the redirect location to send users to an arbitrary external si=
    te instead of the intended one. This vulnerability is fixed in 1.8.10. 2026= -06-22 6.1 CVE-2026-44889 [ https://www.cve.org/CVERecord?id=3DCVE-2026-448=
    89 ] RAGapp--RAGapp A vulnerability has been found in RAGapp up to 0.1.5. A= ffected is the function FileHandler.upload_file/FileHandler.remove_file of = the file src/ragapp/backend/controllers/files.py of the component Knowledge=
    File Handler. Such manipulation leads to path traversal. The attack can be=
    executed remotely. The exploit has been disclosed to the public and may be=
    used. The pull request to fix this issue awaits acceptance. 2026-06-28 6.3=
    CVE-2026-13509 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13509 ] Rapid= 7--InsightConnect Finger Plugin OS Command Injection vulnerability in Rapid=
    7 InsightConnect Finger Plugin on Linux allows authenticated attackers to e= xecute arbitrary OS commands via the user or host parameters due to insuffi= cient input validation in shell command construction. 2026-06-25 6 CVE-2026= -8664 [ https://www.cve.org/CVERecord?id=3DCVE-2026-8664 ] Rapid7--InsightC= onnect Markdown Plugin Server-Side Cross-Site Scripting and Server-Side Req= uest Forgery vulnerability in the markdown_to_pdf action of Rapid7 InsightC= onnect Markdown Plugin version 3.1.4 and earlier on Linux allows remote att= ackers to execute JavaScript server-side and make arbitrary outbound HTTP r= equests via crafted content embedded in Markdown input. The PDF rendering e= ngine does not restrict script execution or outbound network access. 2026-0= 6-26 4.8 CVE-2026-8661 [ https://www.cve.org/CVERecord?id=3DCVE-2026-8661 ]=
    Rapid7--InsightConnect RPM Plugin OS Command Injection vulnerability in Ra= pid7 InsightConnect RPM Plugin on Linux allows authenticated attackers to e= xecute arbitrary OS commands via the repo, key, or name parameters due to i= nsufficient input sanitization in shell command construction. 2026-06-24 6 = CVE-2026-8663 [ https://www.cve.org/CVERecord?id=3DCVE-2026-8663 ] Rapid7--= InsightConnect Sed Plugin Arbitrary File Read vulnerability in Rapid7 Insig= htConnect Sed Plugin on Linux allows authenticated attackers to read arbitr= ary files via the expression parameter due to insufficient input validation=
    . 2026-06-25 6.5 CVE-2026-9153 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-9153 ] Rapid7--InsightConnect SQLmap Plugin OS Command Injection vulnerab= ility in Rapid7 InsightConnect SQLmap Plugin on Linux allows authenticated = attackers to execute arbitrary OS commands via the api_host or api_port par= ameters during connection configuration due to insufficient input validatio=
    n. 2026-06-25 6 CVE-2026-8659 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -8659 ] Rapid7--InsightConnect Tcpdump Plugin OS Command Injection vulnerab= ility in Rapid7 InsightConnect Tcpdump Plugin on Linux allows authenticated=
    attackers to execute arbitrary OS commands via the options or filter param= eters due to insufficient input sanitization in shell command construction.=
    2026-06-25 6 CVE-2026-8658 [ https://www.cve.org/CVERecord?id=3DCVE-2026-8= 658 ] Red Hat--Logging Subsystem for Red Hat OpenShift A missing authorizat= ion flaw was found in the OpenShift Cluster Logging Operator. The operator = creates and forwards ServiceAccount tokens to output destinations without v= erifying that the ClusterLogForwarder creator has permission to use those c= redentials, allowing a delegated editor to exfiltrate SA tokens and escalat=
    e privileges. 2026-06-23 6.8 CVE-2026-10609 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-10609 ] Red Hat--Pen Drive Powered by Red Hat Lightspeed A f= law was found in the Pen Drive report generator. Cluster-sourced data is re= ndered into HTML reports without proper escaping or sanitization. An attack=
    er with cluster administrator privileges can inject a stored cross-site scr= ipting (XSS) payload into cluster objects (such as ClusterVersion spec.chan= nel) that executes in the browser of any user who opens the generated HTML = report. 2026-06-25 6.9 CVE-2026-13083 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-13083 ] Red Hat--Red Hat build of Apicurio Registry 3 A flaw was f= ound in Apicurio Registry. The DocumentBuilderAccessor correctly blocks ext= ernal DTD and schema access but does not disable DOCTYPE declarations or en= able FEATURE_SECURE_PROCESSING. An attacker with artifact-write permission = can upload XML documents with internal entity-expansion payloads (billion-l= aughs variant) that cause CPU and heap exhaustion, partially mitigated by t=
    he JAXP default 64,000 entity-expansion limit. 2026-06-25 6.5 CVE-2026-1299=
    3 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12993 ] Red Hat--Red Hat bu= ild of Keycloak 26.4 A flaw was found in Keycloak's client registration ser= vice. A remote attacker, possessing a previously issued Registration Access=
    Token (RAT), could exploit this vulnerability to re-enable a client that a=
    n administrator had explicitly disabled. This bypasses security controls, a= llowing the attacker to reset the client's secret and potentially regain pr= ivileged API access. The primary impact includes unauthorized information d= isclosure and potential integrity compromise. 2026-06-25 6.5 CVE-2026-9705 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-9705 ] Red Hat--Red Hat build=
    of Keycloak 26.4 A flaw was found in Keycloak. A realm administrator with = the "manage-realm" role can exploit this vulnerability by submitting an arb= itrary filesystem path as a keystore parameter when creating a key provider=
    component. This allows the administrator to probe arbitrary filesystem pat= hs, determining which files exist and are readable by the Keycloak process.=
    This information disclosure could be used to identify high-value targets f=
    or follow-on attacks. 2026-06-25 4.9 CVE-2026-9083 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-9083 ] Red Hat--Red Hat build of Keycloak 26.4 A flaw=
    was found in org.keycloak.authorization. An authenticated user with a gran= ted User-Managed Access (UMA) permission ticket for one resource can exploi=
    t this by using a specific permission request prefix to bypass per-resource=
    access control. This allows the user to gain unauthorized access to all re= sources of that type within the same resource server, even if they do not h= ave a ticket for those specific resources. This vulnerability requires the = resource server to be configured in PERMISSIVE policy enforcement mode and = affects typed resources with ownerManagedAccess enabled, where no explicit = policy protects the resource type. The primary consequence is unauthorized = information disclosure or modification of resources. 2026-06-25 4.6 CVE-202= 6-9799 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9799 ] Red Hat--Red Ha=
    t Enterprise Linux 10 A flaw was found in the community.general Ansible col= lection's nexmo module. The module constructs HTTP requests to the Vonage/N= exmo SMS API by encoding API credentials (api_key and api_secret) into URL = query parameters and sending them via GET requests. This causes credentials=
    to be exposed in web server access logs, proxy logs, HTTP Referer headers,=
    and network monitoring tools, despite the Ansible argument specification m= arking these parameters as no_log. An attacker with access to any of these = logging or monitoring points can obtain the full API credentials and gain u= nauthorized access to the victim's Vonage/Nexmo account. 2026-06-23 6.5 CVE= -2026-11820 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11820 ] Red Hat--= Red Hat Enterprise Linux 10 Module: plugins/modules/keyring_info.py CVSS 3.=
    1: 5.5 MEDIUM - AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Issue: The module retri= eves a passphrase from the OS native keyring (GNOME Keyring, macOS Keychain=
    , Windows Credential Manager) and places it directly into result["passphras= e"] with no output suppression, no no_log protection, and no documentation = warning. Root Cause: Line 105 (protected): keyring_password=3Ddict(type=3D"= str", required=3DTrue, no_log=3DTrue) Line 127 (NOT protected): result["pas= sphrase"] =3D passphrase Observed Output: { "changed": false, "passphrase":=
    "MyMasterP@ssw0rd!SSH_Key_Secret" } Visible via register + debug: { "keyri= ng_result": { "changed": false, "passphrase": "MyMasterP@ssw0rd!SSH_Key_Sec= ret" } } Impact: Master passwords, SSH key passphrases and service credenti= als appear in all Ansible output register: keyring_result followed by debug=
    : var=3Dkeyring_result prints passphrase in full Ansible fact caching backe= nds (Redis, JSON file, memcached) may persist the passphrase AWX/Tower job = logs silently store the live credential Fix: module.exit_json(changed=3DFal= se, passphrase=3Dpassphrase, _ansible_no_log=3DTrue) Also add a documentati=
    on warning requiring callers to use no_log: true at the task level. PoCs Fi=
    g 1: PoC execution showing passphrase in plaintext output Fig 2: Source cod=
    e showing no_log=3DTrue on input (line 105) vs unprotected output (line 127=
    ) 2026-06-23 5.5 CVE-2026-11819 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-11819 ] Red Hat--Red Hat Enterprise Linux 10 A heap-based buffer overflo=
    w was found in dnsmasq. When DNSSEC validation and query logging are both e= nabled, logging of DS or DNSKEY replies containing unsupported algorithm or=
    digest types can cause dnsmasq to write past the end of an internal loggin=
    g buffer. A remote attacker able to supply such a DNS response may crash th=
    e dnsmasq process, resulting in denial of service. 2026-06-22 5.9 CVE-2026-= 12725 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12725 ] Red Hat--Red Ha=
    t Enterprise Linux 10 An out-of-bounds read vulnerability exists in dnsmasq=
    's find_soa() function in src/rfc1035.c. When parsing NS section records, e= xtract_name() is called with extrabytes=3D0, failing to validate that 10 ad= ditional bytes exist for fixed-length DNS record fields. A remote attacker = controlling a DNS zone can exploit this via a crafted NXDOMAIN response to = cause a 10-byte heap out-of-bounds read, potentially accessing stale data f= rom prior transactions. 2026-06-23 5.3 CVE-2026-12969 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-12969 ] Red Hat--Red Hat Enterprise Linux 10 A fla=
    w was found in OpenSSH. A local unprivileged attacker on a Linux client hos=
    t can hijack client-side X11 forwarding connections. This is possible by pr= e-binding the preferred abstract X socket name when X11 forwarding is enabl=
    ed and a local UNIX-domain X socket is used. A successful attack can compro= mise the confidentiality of forwarded X11 traffic, including sensitive wind=
    ow contents and input, and may allow some manipulation of the forwarded ses= sion. 2026-06-23 5 CVE-2026-55655 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-55655 ] Red Hat--Red Hat Enterprise Linux 10 The fix for CVE-2026-2443=
    was regressed by a subsequent rework commit that replaced specific overflo=
    w checks with a general signed comparison. When a client sends a Range requ= est with a suffix length exceeding the content size, the resulting negative=
    start value is not properly clamped, leading to malformed HTTP 206 respons=
    es and log flooding. 2026-06-22 4.8 CVE-2026-12549 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-12549 ] Red Hat--Red Hat Enterprise Linux 10 A flaw w=
    as found in the GStreamer gst-plugins-bad package. When processing a malfor= med H.266/VVC video stream with a crafted aspect ratio indicator value, the=
    H.266 parser performs an out-of-bounds read of up to 8 bytes from adjacent=
    memory. This flaw allows an attacker to craft a malicious H.266 video file=
    or stream that, when processed by a GStreamer-based application, could lea=
    k limited memory contents through video metadata, potentially exposing sens= itive information from the application's address space. 2026-06-23 4.3 CVE-= 2026-12891 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12891 ] Red Hat--R=
    ed Hat Enterprise Linux 10 A flaw was found in GStreamer's gst-plugins-bad = package. When processing a specially crafted H.264 video file containing ma= lformed MVC or SVC extension slice NAL units, a 1-byte heap out-of-bounds r= ead can occur during parsing. This happens when the parser attempts to chec=
    k slice boundary information without first verifying that the NAL unit cont= ains enough data beyond the extension header. An attacker could exploit thi=
    s by tricking a user into opening a malicious H.264 video file, potentially=
    causing the application to crash or leak a single byte of heap memory. 202= 6-06-23 4.4 CVE-2026-12892 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12= 892 ] Red Hat--Red Hat Enterprise Linux 10 A flaw was found in OpenSSH. A m= alicious SSH server can exploit a double free vulnerability in the Diffie-H= ellman Group Exchange (DH-GEX) client path. This occurs during FIPS (Federa=
    l Information Processing Standards) mode known-group validation when the cl= ient processes attacker-controlled DH-GEX group parameters. Successful expl= oitation leads to client-side process termination, resulting in a Denial of=
    Service (DoS). 2026-06-23 4.3 CVE-2026-55653 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-55653 ] Red Hat--Red Hat OpenShift Virtualization 4 A flaw=
    was found in KubeVirt's virt-handler domain notify server. The gRPC handle=
    rs for HandleDomainEvent and HandleK8SEvent derive the VMI identity (namesp= ace/name) solely from the request body without validating it against the co= nnection's origin. Each virt-launcher pod connects through a per-VMI pipe s= ocket, but no identity tag is propagated from the pipe path to the server h= andlers. This allows a compromised virt-launcher process to send forged dom= ain lifecycle events for any other VMI scheduled on the same node, causing = virt-handler to erroneously update that VMI's state and disrupt its lifecyc=
    le management. 2026-06-24 6.5 CVE-2026-13208 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-13208 ] Red Hat--Red Hat OpenShift Virtualization 4 A serve= r-side request forgery (SSRF) flaw was found in KubeVirt's virt-api port-fo= rward handler. When processing a port-forward request to a VirtualMachineIn= stance (VMI), virt-api reads the target IP from vmi.Status.Interfaces[0].IP=
    and passes it directly to net.Dial() without validation. For VMIs using no= n-masquerade network bindings (bridge or secondary-only), this IP is report=
    ed by the QEMU guest agent running inside the VM and is fully controllable =
    by the VM owner. An attacker with kubevirt.io:edit permissions can create a=
    VM with a modified guest agent that reports an arbitrary IP address, then = request port-forward to establish a bidirectional TCP tunnel from virt-api'=
    s cluster-internal network position to any routable destination, bypassing = NetworkPolicy isolation. 2026-06-25 6.4 CVE-2026-13318 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-13318 ] Red Hat--Red Hat OpenShift Virtualization=
    4 A flaw was found in KubeVirt's virt-handler network cache handling. The = WriteToCachedFile function writes data to a launcher-rooted path using os.W= riteFile and os.Chown without symlink protection. A user with access to the=
    virt-launcher container can plant a symlink at the cache file path, causin=
    g virt-handler to follow it and overwrite an arbitrary host file with JSON = content and change its ownership. 2026-06-25 4.2 CVE-2026-13218 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-13218 ] Red Hat--Red Hat OpenShift Virtu= alization 4 A flaw was found in KubeVirt's network annotation generator. Wh=
    en a tenant creates a VirtualMachineInstance with a Multus network configur= ation, the supplied networkName value is written verbatim into the launcher=
    pod's v1.multus-cni.io/default-network annotation without format validatio=
    n or sanitization. The only admission check rejects empty strings; no DNS-1= 123 format validation, JSON detection, or special character rejection is pe= rformed. When the ExternalNetResourceInjection Beta feature gate is enabled=
    (off by default, cluster-admin only), the NAD lookup that would otherwise = catch malformed names is skipped by design. A tenant with kubevirt.io:edit = permissions can inject a JSON-formatted NetworkSelectionElement array speci= fying an arbitrary namespace, NAD name, static IP address, and MAC address.=
    Multus on the node parses this JSON and attaches the launcher pod to the s= pecified network attachment in any namespace, enabling cross-namespace netw= ork access and IP/MAC impersonation on network segments normally segregated=
    from tenant workloads. The ExternalNetResourceInjection feature gate was i= ntroduced in KubeVirt v1.8.0 (first shipped in OpenShift Virtualization 4.2= 1). 2026-06-26 4.9 CVE-2026-13434 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-13434 ] Red Hat--Red Hat Satellite 6.19 A flaw was found in foreman-mc= p-server. This component utilizes two distinct logging mechanisms that can = expose sensitive session and authentication data. One mechanism logs sessio=
    n identifiers, which are treated as authentication credentials, at an infor= mational level. The other, when debug logging is enabled, incompletely sani= tizes HTTP request headers, leading to the cleartext logging of sensitive i= nformation such as authorization tokens and API keys. This vulnerability ca=
    n result in a confidentiality breach, as sensitive authentication data is p= ersisted in plain text within container logs, increasing the risk if logs a=
    re forwarded to a centralized platform. 2026-06-23 6.2 CVE-2026-9073 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-9073 ] reepaydenmark--Frisbii Pay T=
    he Frisbii Pay plugin for WordPress is vulnerable to unauthorized modificat= ion of data due to missing capability checks on the 'upload_csv' and 'proce= ss_batch' functions in all versions up to, and including, 1.8.9. This makes=
    it possible for authenticated attackers, with Subscriber-level access and = above, to upload arbitrary CSV data and overwrite WooCommerce payment token=
    s, postmeta, and order meta records. 2026-06-27 6.5 CVE-2026-3462 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-3462 ] rentmy--RentMy Real-Time Rental=
    Management Plugin The RentMy Real-Time Rental Management Plugin plugin for=
    WordPress is vulnerable to authorization bypass in all versions up to, and=
    including, 4.0.4.1. This is due to the plugin not properly verifying that =
    a user is authorized to perform an action. This makes it possible for unaut= henticated attackers to read, create, update, and delete event records stor=
    ed in the rentmy_events WordPress option, as well as overwrite the rentmy_l= ocationId option. 2026-06-24 5.3 CVE-2026-8690 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-8690 ] rhewlif--Donation Thermometer Unauthenticated Brok=
    en Access Control in Donation Thermometer <=3D 2.2.7 versions. 2026-06-26 5=
    .3 CVE-2025-64636 [ https://www.cve.org/CVERecord?id=3DCVE-2025-64636 ] Roc= ketChat--Rocket.Chat Rocket.Chat is an open-source, secure, fully customiza= ble communications platform. Prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.= 0.6, 7.13.8, and 7.10.12, in the visitors.info endpoint, https://developer.= rocket.chat/apidocs/get-visitor-information-by-id-1, token is returned in t=
    he response. It looks like there's no use case for the token to be present =
    in the response and it would be a good security practice to remove it altog= ether. This vulnerability is fixed in 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.= 0.6, 7.13.8, and 7.10.12. 2026-06-24 6.7 CVE-2026-49278 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-49278 ] RocketChat--Rocket.Chat Rocket.Chat is a=
    n open-source, secure, fully customizable communications platform. Prior to=
    8.5.0, the ImageElement component in packages/gazzodown renders user-contr= olled src values directly into <a href> and <img src> attributes without pr= otocol sanitization. Unlike the analogous LinkSpan component - which uses s= anitizeUrl to block javascript:, data:, and vbscript: protocols - ImageElem= ent passes the raw URL through unchanged. An authenticated user can post a = markdown image with a javascript: URL that, if clicked on an older browser,=
    would execute arbitrary JavaScript in the viewer's session. This vulnerabi= lity is fixed in 8.5.0. 2026-06-24 4.4 CVE-2026-47733 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-47733 ] Roxnor--GetGenie Subscriber Sensitive Data=
    Exposure in GetGenie <=3D 4.4.2 versions. 2026-06-26 6.5 CVE-2026-57316 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-57316 ] rtk-ai--rtk @rtk-ai/rtk= -rewrite transparently rewrites shell commands executed via OpenClaw's exec=
    tool to their RTK equivalents. In 1.0.0, the @rtk-ai/rtk-rewrite OpenClaw = plugin passes attacker-controlled input directly into a shell-backed execSy= nc() template string without shell-safe escaping. JSON.stringify() wraps th=
    e value in double quotes and escapes inner double-quotes and backslashes, b=
    ut leaves $() and backtick shell metacharacters untouched. Because execSync=
    delegates execution to /bin/sh -c, the shell expands $(...) substitutions = even inside double-quoted strings, causing the injected subcommand to execu=
    te before rtk is invoked. An attacker who can influence the exec tool's com= mand parameter (e.g., via an LLM agent prompt or gateway/tool-call input) a= chieves arbitrary OS command execution with the privileges of the plugin/ga= teway process. 2026-06-23 6.3 CVE-2026-55249 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-55249 ] rustfs--rustfs RustFS is a distributed object stora=
    ge system built in Rust. In 1.0.0-beta.7 and earlier, the real-time metrics=
    endpoint at /rustfs/admin/v3/metrics is accessible to any valid IAM user r= egardless of their assigned policy. Every other admin handler in the codeba=
    se calls validate_admin_request to enforce admin-action IAM checks; the Met= ricsHandler skips this call entirely. A restricted IAM user whose policy gr= ants only access to their own bucket can read server-wide operational metri=
    cs including disk I/O statistics, network throughput, scanner cycle timing,=
    and cluster RPC state. 2026-06-26 4.3 CVE-2026-55838 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-55838 ] samuelclay--NewsBlur NewsBlur before 14.5.=
    0 contains a broken access control vulnerability that allows authenticated = users to read private notification feeds by supplying arbitrary user_id val= ues to the GET /social/interactions endpoint without ownership verification=
    . Attackers can enumerate user_id values to access another user's follows, = replies, and social activity without authorization. 2026-06-25 4.3 CVE-2026= -56772 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56772 ] secufor--Secuf= or_OAuth The Secufor_OAuth plugin for WordPress is vulnerable to unauthoriz=
    ed access in all versions up to, and including, 1.0.7. This is due to the p= lugin not properly verifying that a user is authorized to perform an action=
    . This makes it possible for unauthenticated attackers to disconnect the Wo= rdPress site from its linked Secufor account by clearing the plugin's store=
    d login token and user login configuration. 2026-06-24 5.3 CVE-2026-7617 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-7617 ] SeedProd LLC.--SeedProd = Pro Contributor Cross Site Scripting (XSS) in SeedProd Pro < 6.19.5 version=
    s. 2026-06-26 6.5 CVE-2026-57617 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-57617 ] seo_tools--Bulk SEO Image The Bulk SEO Image plugin for WordPre=
    ss is vulnerable to Cross-Site Request Forgery in versions up to and includ= ing 1.1. This is due to missing or incorrect nonce validation on the plugin=
    's settings page handler BulkSeoImage(), which dispatches to launchbulk() /=
    BulkSeoImageGo() whenever the request contains $_POST['bulkseoimage']. No = wp_nonce_field() is emitted in the form and no check_admin_referer()/wp_ver= ify_nonce() is performed before bulk-overwriting the _wp_attachment_image_a=
    lt post meta for every image attached to every published post and/or page. = This makes it possible for unauthenticated attackers to bulk-overwrite imag=
    e ALT-text metadata across the site via a forged request granted they can t= rick a site administrator into performing an action such as clicking on a l= ink. 2026-06-24 4.3 CVE-2026-11997 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-11997 ] SEOPress Free--SEOPress PRO Contributor Broken Access Control=
    in SEOPress PRO <=3D 9.1.1 versions. 2026-06-26 4.3 CVE-2026-57430 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-57430 ] Shenzhen i365-Tech Co. Ltd.-= -Setracker2 Parental Control App (Android) package com.tgelec.setracker Set= racker2 Android Companion App com.tgelec.setracker versions 3.1.5 and prior=
    have a predictable registration ID derived from IMEI. The enrollment syste=
    m lacks additional authentication before assignment. If an attacker is able=
    to obtain the registration ID, they would be able to arbitrarily enroll wa= tches belonging to other users. 2026-06-25 6.5 CVE-2026-9219 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-9219 ] ShortPixel--ShortPixel Adaptive Imag=
    es Unauthenticated Arbitrary File Deletion in ShortPixel Adaptive Images <=
    =3D 3.11.4 versions. 2026-06-26 5.8 CVE-2026-56066 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-56066 ] Significant-Gravitas--AutoGPT AutoGPT is a wo= rkflow automation platform for creating, deploying, and managing continuous=
    artificial intelligence agents. Prior to , the `POST /api/integrations/web= hooks/{webhook_id}/ping` endpoint fetches the target webhook by primary key=
    alone without verifying that the webhook belongs to the authenticated user=
    . Any authenticated user can supply an arbitrary webhook_id to confirm webh= ook existence, leak the webhook's OAuth provider type, and in some cases tr= igger a ping delivery on behalf of another user. This vulnerability is fixe=
    d in . 2026-06-26 5.4 CVE-2026-56823 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-56823 ] SiteGround--SiteGround Email Marketing Unauthenticated Brok=
    en Access Control in SiteGround Email Marketing <=3D 1.7.5 versions. 2026-0= 6-26 5.3 CVE-2026-24547 [ https://www.cve.org/CVERecord?id=3DCVE-2026-24547=
    ] siyuan-note--siyuan SiYuan is an open-source personal knowledge manageme=
    nt system. Prior to 3.7.0, the /api/icon/getDynamicIcon endpoint is explici= tly excluded from authentication in SiYuan's kernel router (router.go, "=C3= =A4=C2=B8=C2=8D=C3=A9=C5=93=E2=82=AC=C3=A8=C2=A6=C2=81=C3=A9=E2=80=B0=C2=B4= =C3=A6=C2=9D=C6=92" -- no auth needed). When called with type=3D8 and a val=
    id block id parameter, this endpoint invokes RenderDynamicIconContentTempla= te, which executes a Go template that includes the querySQL and queryBlocks=
    functions. These functions run arbitrary SELECT statements against the SiY= uan SQLite database. An unauthenticated network-adjacent attacker who knows=
    a valid block ID can exfiltrate all user note content, tags, asset referen= ces, and block attributes from the database. This vulnerability is fixed in=
    3.7.0. 2026-06-24 5.9 CVE-2026-54068 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-54068 ] StatCounter--StatCounter Contributor Cross Site Scripting = (XSS) in StatCounter <=3D 2.1.1 versions. 2026-06-26 6.5 CVE-2026-57629 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-57629 ] studiowombat--Shoppable = Images Lite Subscriber Broken Access Control in Shoppable Images Lite <=3D = 1.3 versions. 2026-06-26 4.3 CVE-2026-57649 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-57649 ] Stylemix--MasterStudy LMS Subscriber Broken Access C= ontrol in MasterStudy LMS <=3D 3.7.30 versions. 2026-06-26 4.3 CVE-2026-576=
    40 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57640 ] surbma--Surbma | I= nfusionsoft Shortcode The Surbma | Infusionsoft Shortcode plugin for WordPr= ess is vulnerable to Stored Cross-Site Scripting via the 'infusionsoft-form=
    ' shortcode in versions up to, and including, 2.0.1. This is due to insuffi= cient input sanitization and output escaping on user-supplied 'account' and=
    'id' shortcode attributes in the surbma_infusionsoft_shortcode_shortcode()=
    function, which are concatenated directly into a <script> tag's src attrib= ute. This makes it possible for authenticated attackers, with contributor-l= evel access and above, to inject arbitrary web scripts in pages that will e= xecute whenever a user accesses an injected page. 2026-06-27 6.4 CVE-2026-1= 1597 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11597 ] SureCart--SureCa=
    rt Subscriber Cross Site Scripting (XSS) in SureCart <=3D 4.2.2 versions. 2= 026-06-26 6.5 CVE-2026-57313 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 57313 ] templatescoderthemes--Spexo The Spexo theme for WordPress is vulner= able to unauthorized access due to a missing capability check on the activa= te_plugin function in all versions up to, and including, 2.0.11. This makes=
    it possible for authenticated attackers, with Subscriber-level access and = above, to activate a limited set of plugins. 2026-06-27 4.3 CVE-2026-12471 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-12471 ] tenable--Nessus A SQL=
    injection vulnerability in Nessus allows a remote, unauthenticated attacke=
    r who controls reverse DNS records for a scanned host to inject malicious S=
    QL into the scan results database, potentially enabling exfiltration of sca= n-result data. 2026-06-25 5.3 CVE-2026-57587 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-57587 ] Themegrill--User Registration Unauthenticated Broke=
    n Access Control in User Registration <=3D 5.2.2 versions. 2026-06-26 6.5 C= VE-2026-52701 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52701 ] Themeis= le--Neve PRO Contributor Cross Site Scripting (XSS) in Neve PRO <=3D 3.1.2 = versions. 2026-06-26 6.5 CVE-2026-57618 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-57618 ] Themeisle--PPOM for WooCommerce Improper Access Control=
    vulnerability in Themeisle PPOM for WooCommerce allows Exploiting Incorrec= tly Configured Access Control Security Levels. This issue affects PPOM for = WooCommerce: from n/a through 33.0.18. 2026-06-25 6.5 CVE-2026-56050 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-56050 ] themeisle--Stripe Payment F= orms by WP Full Pay Accept Credit Card Payments, Donations & Subscriptions = The WP Full Stripe Free plugin for WordPress is vulnerable to Missing Autho= rization in versions up to, and including, 8.4.3 via the wpfs_update_failed= _payment_status AJAX action. The handler is registered through both wp_ajax=
    _ and wp_ajax_nopriv_ hooks and the underlying update_failed_payment_status=
    () function performs no capability check, no nonce verification, and no log= ged-in check before calling $this->db->updatePaymentByEventId() with attack= er-controlled POST parameters. This makes it possible for unauthenticated a= ttackers who can obtain a valid Stripe Payment Intent ID for the target sit=
    e (Payment Intent IDs are exposed to the customer browser during normal Str= ipe.js checkout flows) to manipulate payment records in the site's database=
    , marking previously successful payments as failed and overwriting failure = codes and messages with attacker-supplied values. 2026-06-27 5.3 CVE-2026-1= 2432 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12432 ] Themeum--Kirki S= ubscriber Server Side Request Forgery (SSRF) in Kirki <=3D 6.0.11 versions.=
    2026-06-26 4.9 CVE-2026-57627 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-57627 ] Tim Strifler--Exclusive Addons Elementor Improper Neutralization =
    of Input During Web Page Generation ('Cross-site Scripting') vulnerability =
    in Tim Strifler Exclusive Addons Elementor allows Stored XSS. This issue af= fects Exclusive Addons Elementor: from n/a through 2.7.9.8. 2026-06-26 6.5 = CVE-2026-57620 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57620 ] tomoji= takasu--RTKLIB RTKLIB through 2.4.3 contains an off-by-one out-of-bounds re=
    ad vulnerability in the decode_ssr3 function at src/rtcm3.c:1446 that allow=
    s remote attackers to trigger a global buffer overflow via crafted RTCM3 SS=
    R messages with attacker-controlled signal mode fields. Remote attackers ca=
    n exploit this vulnerability by sending malicious SSR correction streams ov=
    er NTRIP or serial connections to cause denial of service or crash RTKLIB r= overs and CORS servers. 2026-06-25 6.5 CVE-2026-56787 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-56787 ] tomojitakasu--RTKLIB RTKLIB through 2.4.3 = contains a heap buffer overflow vulnerability in the readrnxobsb function i=
    n src/rinex.c that allows attackers to trigger memory corruption by failing=
    to clamp satellite count values from RINEX epoch headers. Attackers can cr= aft malicious RINEX files declaring more than 64 satellites per epoch to ca= use heap buffer overflow writes and out-of-bounds stack reads, crashing RTK= LIB-based applications including rnx2rtkp and RTKPOST. 2026-06-25 6.5 CVE-2= 026-56789 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56789 ] tomojitakas= u--RTKLIB RTKLIB through 2.4.3 contains an out-of-bounds read vulnerability=
    in getcodepri function when processing unrecognized RINEX observation code=
    s, allowing attackers to trigger denial of service. Crafted RINEX files wit=
    h unknown observation types cause negative array indexing into the codepris=
    table, resulting in reliable crashes and potential memory disclosure of ad= jacent global data. 2026-06-25 4.4 CVE-2026-56788 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-56788 ] ToolJet--ToolJet ToolJet is the open-source fo= undation am AI-native platform for building and deploying internal tools, w= orkflows and AI agents. Prior to 3.20.1780-lts, the authenticated endpoint = POST /api/data-sources/decrypt returns the decrypted plaintext for any cred= ential whose credential_id is supplied in the request body. Unlike every ne= ighbouring data-source route, this handler is not protected by ValidateData= SourceGuard, does not receive the calling @User(), and the underlying Crede= ntialsService.getValue() looks the credential up by id only, with no organi= zation scoping. As a result, any authenticated user of any organization can=
    decrypt the data-source secrets of any other organization by supplying tha=
    t organization's credential_id - a cross-tenant confidentiality breach. Thi=
    s vulnerability is fixed in 3.20.1780-lts. 2026-06-25 6.8 CVE-2026-55411 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-55411 ] TortoiseGit team--Torto= iseGit Argument Injection in TortoiseGitBlame via Malicious Git History Fil= enames Leads to Arbitrary File Write in TortoiseGit 2026-06-24 5.5 CVE-2026= -11968 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11968 ] trainingbusine= sspros--Groundhogg CRM, Newsletters, and Marketing Automation The Groundhog=
    g - CRM, Newsletters, and Marketing Automation plugin for WordPress is vuln= erable to generic SQL Injection via the 'after' parameter in all versions u=
    p to, and including, 4.5.4 due to insufficient escaping on the user supplie=
    d parameter and lack of sufficient preparation on the existing SQL query. T= his makes it possible for authenticated attackers, with Sales Manager-level=
    access and above, to append additional SQL queries into already existing q= ueries that can be used to extract sensitive information from the database.=
    The AJAX handler wp_ajax_groundhogg_get_contacts_table has its capability = check commented out and performs no nonce verification, meaning any authent= icated user regardless of role can reach the vulnerable code path. 2026-06-=
    26 6.5 CVE-2026-13226 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13226 ]=
    trainingbusinesspros--Groundhogg CRM, Newsletters, and Marketing Automatio=
    n The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for Wo= rdPress is vulnerable to generic SQL Injection via the 'search' parameter i=
    n all versions up to, and including, 4.5.5 due to insufficient escaping on = the user supplied parameter and lack of sufficient preparation on the exist= ing SQL query. This makes it possible for authenticated attackers, with mar= keter-level access and above, to append additional SQL queries into already=
    existing queries that can be used to extract sensitive information from th=
    e database. 2026-06-27 6.5 CVE-2026-13331 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-13331 ] trainingbusinesspros--Groundhogg CRM, Newsletters, and=
    Marketing Automation The Groundhogg - CRM, Newsletters, and Marketing Auto= mation plugin for WordPress is vulnerable to generic SQL Injection via 'que= ry[select]' Parameter in all versions up to, and including, 4.5.5 due to in= sufficient escaping on the user supplied parameter and lack of sufficient p= reparation on the existing SQL query. This makes it possible for authentica= ted attackers, with Sales Representative-level access and above, to append = additional SQL queries into already existing queries that can be used to ex= tract sensitive information from the database. The sanitized Contact_Query = code path can be bypassed by supplying an invalid filter type (e.g., query[= filters][0][0][type]=3Dinvalid_filter_nonexistent), causing a FilterExcepti=
    on to be caught and execution to fall through to the unsanitized Legacy_Con= tact_Query path. 2026-06-27 6.5 CVE-2026-13333 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-13333 ] TryGhost--Ghost Ghost is a Node.js content manage= ment system. From 6.0.9 until 6.21.1, when making an external request, it i=
    s possible to bypass the IP filter that ensures the request isn't going to =
    an internal service using an IPv6 literal which maps to a private IPv4 addr= ess. This vulnerability is fixed in 6.21.1. 2026-06-24 5.8 CVE-2026-53944 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-53944 ] TryGhost--Ghost Ghost =
    is a Node.js content management system. From 6.19.4 until 6.21.1, when re-r= endering posts, Ghost would refetch missing image dimensions by issuing an = outbound HTTP request to the URL stored on an image card - without restrict= ing that URL to trusted image hosts. An authenticated staff user able to cr= eate or edit posts could therefore point an image card at an attacker-chose=
    n host and cause the Ghost server to request it on their behalf, including = hosts on internal networks or cloud instance metadata endpoints that would = not normally be reachable from the public internet. This vulnerability is f= ixed in 6.21.1. 2026-06-24 5.4 CVE-2026-53946 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-53946 ] TryGhost--Ghost Ghost is a Node.js content managem= ent system. From 5.18.0 until 6.21.1, a discrepancy in responses from the m= embers signin endpoints made it possible for an unauthenticated attacker to=
    determine whether a given email address belongs to a registered member of =
    a Ghost site. This vulnerability is fixed in 6.21.1. 2026-06-24 5.3 CVE-202= 6-53947 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53947 ] TryGhost--Gho=
    st Ghost is a Node.js content management system. From 6.19.4 until 6.21.1, = insufficient validation of the client-supplied Content-Type on Ghost's Admi=
    n API file upload endpoint allowed uploaded files to be served from the sit=
    e with an attacker-chosen content type on S3/GCS storage backends. On insta= llations that serve uploaded files from the same origin as the site, this c= ould have been used to facilitate stored cross-site scripting against site = visitors or staff. This vulnerability is fixed in 6.21.1. 2026-06-24 5.4 CV= E-2026-53948 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53948 ] TryGhost= --Ghost Ghost is a Node.js content management system. From 5.46.1 until 6.2= 1.2, the validation applied to filters on the public API endpoints could be=
    partially bypassed, making it possible to reveal private fields via a brut=
    e force attack. If SQLite was used as the database password hashes were ful=
    ly accessible. If MySQL was used as the database the password hashes' case = (uppercase / lowercase) would have been lost, which would likely have rende= red a further brute force attack on the discovered hashes fruitless. This v= ulnerability is fixed in 6.21.2. 2026-06-24 5.3 CVE-2026-53949 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-53949 ] TryGhost--Ghost Ghost is a Node.j=
    s content management system. From 6.0.9 until 6.21.1, Ghost's private-IP ch= eck for outbound HTTP requests could be bypassed via DNS rebinding, allowin=
    g an attacker to coerce the Ghost server into reaching hosts on internal ne= tworks through features that issue external fetches. This vulnerability is = fixed in 6.21.1. 2026-06-24 4 CVE-2026-53945 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-53945 ] tychesoftwares--Abandoned Cart Lite for WooCommerce=
    Unauthenticated Cross Site Request Forgery (CSRF) in Abandoned Cart Lite f=
    or WooCommerce <=3D 6.8.0 versions. 2026-06-26 4.3 CVE-2026-57637 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-57637 ] tychesoftwares--Payment Gatewa=
    y Based Fees and Discounts for WooCommerce Unauthenticated Insecure Direct = Object References (IDOR) in Payment Gateway Based Fees and Discounts for Wo= oCommerce <=3D 3.0.0 versions. 2026-06-26 6.5 CVE-2026-56048 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-56048 ] ueberdosis--tiptap-php Tiptap for P=
    HP before version 2.1.1 contains an input validation vulnerability that all= ows authenticated attackers to cause a denial of service by submitting Tipt=
    ap JSON with the attrs.href field set to an array instead of a string, caus= ing an unhandled TypeError in the Link::isAllowedUri() function when passed=
    to preg_match(). Attackers can persist malformed JSON records that permane= ntly crash the server-side HTML rendering pipeline for all subsequent viewe=
    rs of that record until the database entry is manually repaired. 2026-06-24=
    6.5 CVE-2026-47110 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47110 ] u= ltrajson--ultrajson UltraJSON is a fast JSON encoder and decoder written in=
    pure C with bindings for Python 3.7+. Prior to 5.13.0, ujson.dumps() (or u= json.dump() or ujson.encode()) have a reject_bytes=3DFalse option. When set=
    , they may accept malformed or truncated UTF-8 byte sequences, silently rew= riting them into different Unicode characters instead of rejecting them. Th=
    is leads to input validation bypass and data integrity issues. This vulnera= bility is fixed in 5.13.0. 2026-06-22 6.5 CVE-2026-54911 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-54911 ] verenigingvanregistrars--Generate Secur= ity.txt The Generate Security.txt plugin for WordPress is vulnerable to aut= horization bypass in all versions up to, and including, 1.0.12. This is due=
    to the plugin not properly verifying that a user is authorized to perform =
    an action. This makes it possible for authenticated attackers, with subscri= ber-level access and above, to delete the site's security.txt file from the=
    server filesystem or create the .well-known directory by directly invoking=
    the delete_securitytxt or create_wellknown_folder AJAX actions. 2026-06-24=
    4.3 CVE-2026-9616 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9616 ] Vil= laTheme--Bopo WooCommerce Product Bundle Builder Unauthenticated Sensitive = Data Exposure in Bopo - WooCommerce Product Bundle Builder <=3D 1.1.6 versi= ons. 2026-06-26 4.3 CVE-2026-57664 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-57664 ] VillaTheme--GIFT4U Unauthenticated Broken Access Control in G= IFT4U <=3D 1.0.10 versions. 2026-06-26 6.5 CVE-2026-57324 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-57324 ] vim--vim Vim is an open source, comman=
    d line text editor. From 9.1.1784 until 9.2.0678, when the bundled zip plug=
    in autoload/zip.vim falls back to PowerShell to browse, read, extract, upda=
    te or delete entries in a zip archive, it builds the PowerShell command by = inserting archive entry names that are quoted only for the shell, not for P= owerShell. A crafted entry name can break out of the intended string contex=
    t and cause PowerShell to execute arbitrary commands with the privileges of=
    the user running Vim, triggered by opening, viewing or extracting the arch= ive. This vulnerability is fixed in 9.2.0678. 2026-06-25 6.5 CVE-2026-57453=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-57453 ] vim--vim Vim is an o= pen source, command line text editor. Prior to 9.2.0662, the dump_prefixes(=
    ) function in src/spell.c walks a spell-file prefix trie iteratively with a=
    depth counter while dumping the prefixes that apply to a word. The counter=
    is bounded only by the trie structure itself; it is never checked against = the size of the fixed MAXWLEN-element stack arrays it indexes (prefix[], ar= ridx[], curi[]). A crafted .spl file, loaded when the user dumps the word l= ist, can drive the descent arbitrarily deep, so the function writes past th=
    e end of those arrays. This is a stack out-of-bounds write that corrupts th=
    e call frame and crashes the editor. This vulnerability is fixed in 9.2.066=
    2. 2026-06-25 5.5 CVE-2026-55892 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-55892 ] vim--vim Vim is an open source, command line text editor. Prior=
    to 9.2.0670, get_text_props() in src/textprop.c reads a uint16 property co= unt stored inline after a line's text and returns it as the number of 32-by=
    te textprop_T entries that follow. The only check is a floor that guarantee=
    s room for a single entry; the count is never checked against the amount of=
    data actually present. A line that declares a large count while carrying l= ittle data causes consumers to read far past the end of the line buffer. Su=
    ch a line can be delivered through a crafted undo file, leading to a crash.=
    This vulnerability is fixed in 9.2.0670. 2026-06-25 5.3 CVE-2026-57451 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-57451 ] vim--vim Vim is an open = source, command line text editor. Prior to 9.2.0671, when Vim opens a file = encrypted with the VimCrypt~04! or VimCrypt~05! method (xchacha20poly1305, = requires the +sodium feature) whose body is shorter than a single libsodium=
    secretstream header, an unsigned length calculation underflows and a subse= quent decryption call reads far past the end of the input buffer, crashing = Vim. This vulnerability is fixed in 9.2.0671. 2026-06-25 5.5 CVE-2026-57452=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-57452 ] vinod-dalvi--Ivory S= earch WordPress Search Plugin The Ivory Search - WordPress Search Plugin pl= ugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'menu_t= itle' and 'menu_magnifier_color' Settings in all versions up to, and includ= ing, 5.5.15 due to insufficient input sanitization and output escaping. Thi=
    s makes it possible for authenticated attackers, with administrator-level a= ccess and above, to inject arbitrary web scripts in pages that will execute=
    whenever a user accesses an injected page. 2026-06-27 4.4 CVE-2026-11356 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-11356 ] vllm-project--vllm vLL=
    M is an inference and serving engine for large language models (LLMs). Prio=
    r to 0.22.0, vLLM's revision pinning controls do not consistently apply to = all artifacts loaded for a model. A deployment that supplies --revision or = --code-revision can still load dynamic code, GGUF files, image processors, = retrieval side weights, or same-repository subfolder weights/config from an=
    unpinned/default revision. This is a supply-chain integrity issue for pinn=
    ed vLLM deployments. Operators can believe they are serving a reviewed mode=
    l revision while vLLM resolves behavior-affecting nested or sibling artifac=
    ts outside that reviewed revision. This vulnerability is fixed in 0.22.0. 2= 026-06-22 6.5 CVE-2026-47155 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 47155 ] vllm-project--vllm vLLM is an inference and serving engine for larg=
    e language models (LLMs). Prior to 0.23.1rc0, vLLM's /v1/audio/transcriptio=
    ns endpoint limits compressed upload size but not decoded PCM output. A 25M=
    B OPUS file expands to ~14.9GB of float32 PCM at decode time. This vulnerab= ility is fixed in 0.23.1rc0. 2026-06-22 6.5 CVE-2026-54233 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-54233 ] vllm-project--vllm vLLM is an inferen=
    ce and serving engine for large language models (LLMs). Prior to 0.23.1rc0,=
    the fix for CVE-2026-22778, which introduced a sanitize_message helper tha=
    t strips object-repr memory addresses from error messages before they reach=
    the client, is incomplete: several response paths echo str(exc) directly t=
    o clients without calling sanitize_message. The unsanitized sites include t=
    he Anthropic API router in vllm/entrypoints/anthropic/api_router.py (the PO=
    ST /v1/messages and POST /v1/messages/count_tokens handlers), the Server-Se=
    nt Events streaming converter in vllm/entrypoints/anthropic/serving.py, and=
    the realtime speech-to-text WebSocket in vllm/entrypoints/speech_to_text/r= ealtime/connection.py. These paths catch the exception inside the route cor= outine and construct the JSONResponse themselves, bypassing the sanitizing = global FastAPI exception handler, and WebSocket frames do not traverse that=
    handler chain at all. Using the same primitive as the parent issue, an una= uthenticated attacker can send malformed image bytes through the Anthropic = Messages API image content parts so that PIL.Image.open raises an Unidentif= iedImageError whose message contains the BytesIO object repr, leaking the h= eap memory address verbatim in the error.message field of the response body=
    . This vulnerability is fixed in 0.23.1rc0. 2026-06-22 5.3 CVE-2026-54236 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-54236 ] volcengine--OpenViking=
    A vulnerability was detected in volcengine OpenViking up to 0.3.21. This a= ffects the function str_to_uint64 of the file openviking/storage/vectordb/u= tils/str_to_uint64.py of the component Local VectorDB Primary-key Label Han= dler. The manipulation of the argument ID results in insufficient verificat= ion of data authenticity. The attack may be launched remotely. Attacks of t= his nature are highly complex. The exploitability is reported as difficult.=
    The pull request to fix this issue awaits acceptance. 2026-06-28 5 CVE-202= 6-13507 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13507 ] warpdotdev--w= arp Warp is an agentic development environment. From 0.2021.04.25.23.05.sta= ble_00 until 0.2026.05.06.15.42.stable_01, Warp accepted certain state-muta= ting terminal lifecycle hooks from the PTY stream without verifying that th=
    e hooks were emitted by Warp's shell integration for the active session. An=
    attacker who could cause a victim to view attacker-controlled terminal out= put in Warp could spoof selected lifecycle metadata, including the current = working directory reported for the active block or SSH session transport me= tadata. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01. 2026-0= 6-24 4.3 CVE-2026-54686 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54686=
    ] WCBoost--WCBoost Products Compare Unauthenticated Sensitive Data Exposur=
    e in WCBoost &#8211; Products Compare <=3D 1.1.0 versions. 2026-06-26 5.3 C= VE-2026-57633 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57633 ] webaway= s--NEX-Forms Ultimate Forms Plugin for WordPress The NEX-Forms - Ultimate F= orms Plugin for WordPress plugin for WordPress is vulnerable to authorizati=
    on bypass in all versions up to, and including, 9.2.2. This is due to the p= lugin not properly verifying that a user is authorized to perform an action=
    . This makes it possible for unauthenticated attackers to enumerate sequent= ial report IDs and download complete form submission data - including names=
    , email addresses, phone numbers, postal addresses, payment details, and up= loaded file paths - for any saved report on the site. 2026-06-27 5.3 CVE-20= 26-12404 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12404 ] wedevs--Doka=
    n Pro The Dokan Pro plugin for WordPress is vulnerable to time-based SQL In= jection via the 'orderby' parameter in all versions up to, and including, 5= .0.4 due to insufficient escaping on the user supplied parameter and lack o=
    f sufficient preparation on the existing SQL query. This makes it possible = for authenticated attackers, with Subscriber-level access and above, to app= end additional SQL queries into already existing queries that can be used t=
    o extract sensitive information from the database. 2026-06-25 6.5 CVE-2026-= 12079 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12079 ] withastro--astr=
    o @astrojs/netlify is an adapter that allows Astro to deploy your hybrid or=
    server rendered site to Netlify. Prior to 7.0.13, @astrojs/netlify convert=
    s Astro image.remotePatterns into Netlify Image CDN images.remote_images re= gular expressions with broader semantics than Astro's canonical matcher. A = single wildcard hostname such as *.example.com is converted to an optional = subdomain regex, so the apex host matches. A single wildcard pathname such =
    as /ok/* is converted without end anchoring, so deeper paths match by prefi=
    x. This vulnerability is fixed in 7.0.13. 2026-06-22 5.3 CVE-2026-54300 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-54300 ] withastro--astro Astro i=
    s a web framework. Prior to 6.4.6, the spreadAttributes function in Astro's=
    server-side rendering pipeline iterates over object keys and passes them d= irectly to addAttribute, which interpolates the key into the HTML output wi= thout escaping. When a developer uses the spread syntax {...props} on an HT=
    ML element and the object keys come from an untrusted source (API, CMS, URL=
    parameters), an attacker can inject arbitrary HTML attributes including ev= ent handlers like onmousemove, onclick, or break out of the attribute conte=
    xt entirely to inject new elements. This vulnerability is fixed in 6.4.6. 2= 026-06-22 4.2 CVE-2026-54298 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 54298 ] WP Folio Team--PPWP Contributor Insecure Direct Object References (= IDOR) in PPWP <=3D 1.9.19 versions. 2026-06-26 4.3 CVE-2026-57634 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-57634 ] wp.insider--Affiliates Manager=
    Affiliate Broken Access Control in Affiliates Manager <=3D 2.9.49 versions=
    . 2026-06-26 6.5 CVE-2026-57654 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-57654 ] wpdevteam--Gutenberg Essential Blocks Page Builder for Gutenberg=
    Blocks & Patterns The Gutenberg Essential Blocks - Page Builder for Gutenb= erg Blocks & Patterns plugin for WordPress is vulnerable to Stored Cross-Si=
    te Scripting via the 'configurablePrefix' Block Attribute in all versions u=
    p to, and including, 6.1.4 due to insufficient input sanitization and outpu=
    t escaping. This makes it possible for authenticated attackers, with Contri= butor-level access and above, to inject arbitrary web scripts in pages that=
    will execute whenever a user accesses an injected page. 2026-06-25 6.4 CVE= -2026-10833 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10833 ] wpeverest= --User Registration & Membership Free & Paid Memberships, Subscriptions, Co= ntent Restriction, User Profile, Custom User Registration & Login Builder T=
    he User Registration & Membership - Free & Paid Memberships, Subscriptions,=
    Content Restriction, User Profile, Custom User Registration & Login Builde=
    r plugin for WordPress is vulnerable to unauthorized modification of data d=
    ue to missing validation checks in the confirm_payment() function in all ve= rsions up to, and including, 5.2.0. This makes it possible for unauthentica= ted attackers to bypass payment processing and activate paid memberships. 2= 026-06-26 6.5 CVE-2026-1869 [ https://www.cve.org/CVERecord?id=3DCVE-2026-1= 869 ] WPManageNinja LLC--Fluent Booking Contributor Cross Site Scripting (X= SS) in Fluent Booking <=3D 2.1.0 versions. 2026-06-26 6.5 CVE-2026-57638 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-57638 ] wummel--patool Patool b= efore 4.0.5 contains a path traversal vulnerability in the safe_extract() f= unction in patoolib/programs/py_tarfile.py when running on Python before 3.= 12, where the is_within_directory() helper uses os.path.commonprefix() for = character-level string comparison instead of path-level comparison, allowin=
    g a crafted archive member path to bypass the containment check. Attackers = can supply a malicious archive with specially crafted member paths to write=
    arbitrary files. 2026-06-26 5.4 CVE-2026-29509 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-29509 ] xpro--Xpro Addons 140+ Widgets for Elementor The=
    Xpro Addons - 140+ Widgets for Elementor plugin for WordPress is vulnerabl=
    e to Stored Cross-Site Scripting via the 'custom_attributes' parameter in a=
    ll versions up to, and including, 1.7.2 due to insufficient input sanitizat= ion and output escaping. This makes it possible for authenticated attackers=
    , with author-level access and above, to inject arbitrary web scripts in pa= ges that will execute whenever a user accesses an injected page. 2026-06-24=
    6.4 CVE-2026-11614 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11614 ] y= apacdev--WhatsOrder Instant Checkout for WooCommerce The WhatsOrder - Insta=
    nt Checkout for WooCommerce plugin for WordPress is vulnerable to Sensitive=
    Information Exposure in all versions up to, and including, 1.0.1 via the y= apacdev_generate_order_pdf. This makes it possible for unauthenticated atta= ckers to extract sensitive customer PII and order details - including full = name, email address, phone number, billing address, ordered items with quan= tities and prices, applied coupons, shipping method, and order total - from=
    any customer's invoice by enumerating sequential order IDs. Invoice HTML f= iles are written to the publicly accessible wp-content/uploads/whatsorder_i= nvoices/ directory, which is created without an .htaccess deny rule or inde= x.php guard, making every invoice directly downloadable over HTTP with no a= uthentication check. 2026-06-24 5.3 CVE-2026-9612 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-9612 ] yashpokharna2555--restaurent-management-system =
    A security flaw has been discovered in yashpokharna2555 restaurent-manageme= nt-system. This impacts an unknown function of the file login_register.php =
    of the component Registration Handler. Performing a manipulation of the arg= ument Username results in cross site scripting. The attack may be initiated=
    remotely. The exploit has been released to the public and may be used for = attacks. This product uses a rolling release model to deliver continuous up= dates. As a result, specific version information for affected or updated re= leases is not available. The project was informed of the problem early thro= ugh an issue report but has not responded yet. 2026-06-28 4.3 CVE-2026-1349=
    9 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13499 ] yt-dlp--yt-dlp yt-d=
    lp is a command-line audio/video downloader. From 2023.09.24 until 2026.06.= 09, if curl is used as an external downloader for yt-dlp, cookies may be le= aked to an unintended host upon HTTP redirect or when the host for download=
    fragments differs from their parent manifest's. At the file download stage=
    , the cookies are passed by yt-dlp to the file downloader via --cookie. How= ever, unless these are loaded from a file, this operation does not activate=
    the cookie engine. As a result, curl will send cookies with requests to do= mains or paths for which the cookies are not scoped. This vulnerability is = fixed in 2026.06.09. 2026-06-23 6.1 CVE-2026-50019 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-50019 ] zephyrproject--zephyr The Zephyr Bluetooth LE=
    Audio Basic Audio Profile (BAP) unicast client mishandles peer-supplied AS=
    E state notifications. In unicast_client_ep_qos_state() (subsys/bluetooth/a= udio/bap_unicast_client.c), the handler writes attacker-controlled QoS fiel=
    ds (interval, framing, phy, sdu, rtn, latency, pd) through the stream-qos p= ointer with only a stream !=3D NULL guard. stream-qos is NULL for any strea=
    m that has been codec-configured via bt_bap_stream_config() but not yet add=
    ed to a unicast group (it is set only by unicast_group_add_stream()). A mal= icious or buggy remote ASCS server, to which the local device is connected =
    as a BAP unicast client, can send a GATT notification announcing the ASE ha=
    s entered the QoS Configured state while the local endpoint is still in the=
    Codec Configured state - a transition the dispatcher explicitly permits - = during that window, causing a write through a NULL pointer and a crash (den= ial of service). The data written is itself remote-controlled. The defect s= hipped in v4.3.0 and v4.4.0 (and earlier). The fix re-points all BAP QoS st= orage to the always-valid embedded ep-qos struct, eliminating the NULL dere= ference. 2026-06-28 6.5 CVE-2026-10593 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-10593 ] zephyrproject--zephyr The Zephyr PL011 UART driver (dri= vers/serial/uart_pl011.c) contains an unbounded software loop in pl011_irq_= tx_enable() that repeatedly invokes the interrupt-driven application callba=
    ck while the TX interrupt mask bit (PL011_IMSC_TXIM) is set, to work around=
    the controller's level-transition TX-interrupt behavior. When CTS hardware=
    flow control is enabled (devicetree hw-flow-control or runtime UART_CFG_FL= OW_CTRL_RTS_CTS) and the wired serial peer de-asserts CTS, the controller s= tops draining the TX FIFO; pl011_fifo_fill() then returns 0 on every call w= hile the application still has pending data and therefore never disables th=
    e TX interrupt. The loop condition never clears, so the thread that called = uart_irq_tx_enable() (e.g. h4_send() in the Bluetooth HCI H4 driver) spins = indefinitely, hanging the executing context and stalling the transport - a = denial of service (CWE-835). An attacker controlling the device attached to=
    the UART's CTS line can trigger the hang by withholding CTS during transmi= ssion. Impact is availability only; there is no memory-safety, confidential= ity, or integrity consequence. The vulnerable loop was introduced in commit=
    b783bc8448ef (Feb 2025) and shipped in releases v4.1.0 through v4.4.0. The=
    fix breaks out of the loop when CTS is blocking and arms the CTS modem-sta= tus interrupt to resume transmission when CTS re-asserts. 2026-06-24 6.5 CV= E-2026-10642 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10642 ] zephyrpr= oject--zephyr The Microchip SERCOM-G1 UART driver (drivers/serial/uart_mchp= _sercom_g1.c), used by the PIC32CM-JH SoC family, contains an out-of-bounds=
    write in its asynchronous (DMA) receive path. When uart_rx_enable() is inv= oked with a one-byte receive buffer (len =3D=3D 1) and CONFIG_UART_MCHP_ASY=
    NC is enabled, the RX-complete ISR starts a single-beat DMA transfer while =
    a received byte is already pending in the SERCOM DATA register. On this SoC=
    the peripheral-triggered DMA start sequencing then writes one byte past th=
    e end of the caller-supplied buffer (CWE-787). The overflowed byte's value =
    is the UART RX data supplied by the connected serial peer (adjacent attacke= r), while its size and location are fixed at one byte immediately after the=
    buffer. Exploitation requires the async UART config (not enabled by defaul=
    t on the in-tree PIC32CM-JH boards) and a consumer that enables RX with a o= ne-byte buffer; impact is limited single-byte memory corruption adjacent to=
    the RX buffer (possible crash / denial of service). The defect shipped in = v4.4.0. The fix reads the first byte with the CPU and, for one-byte buffers=
    , performs no DMA at all; for larger buffers it sizes the DMA for the remai= ning len-1 bytes. 2026-06-28 4.2 CVE-2026-10644 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-10644 ] zephyrproject-rtos--Zephyr Zephyr's ext2 directo= ry-entry parser does not fully validate on-disk directory entry structure b= efore copying the entry name and advancing traversal state. In ext2_fetch_d= irentry() (subsys/fs/ext2/ext2_diskops.c), the code only checks de_name_len=
    <=3D EXT2_MAX_FILE_NAME and then copies the name with memcpy without valid= ating the structural relationship between de_rec_len, de_name_len, and the = directory block boundary (for example that de_rec_len is non-zero, at least=
    the size of the entry header, and that the record fits within the block). = Callers such as find_dir_entry() and ext2_get_direntry() (subsys/fs/ext2/ex= t2_impl.c) then advance traversal using the unvalidated de_rec_len. A craft=
    ed ext2 image can therefore cause an out-of-bounds read from the directory = block buffer when a malformed entry near the end of a block triggers an ove= rsized name copy, or a zero-progress infinite loop when de_rec_len =3D=3D 0=
    . The issue is not reached at mount time but later through directory traver= sal paths such as pathname lookup, stat/open/unlink/rename, and readdir. Th=
    e primary impact is denial of service and out-of-bounds reads under attacke= r-controlled ext2 images mounted from untrusted media. 2026-06-22 4.9 CVE-2= 026-10645 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10645 ]=20

    Back to top [ #top ]

    Low Vulnerabilities

    Primary
    Vendor -- Product Description Published CVSS Score Source Info 7-Zip--7-Zip=
    7-Zip for Windows through 26.02 fails to preserve the Mark-of-the-Web when=
    extracting a crafted RAR5 archive, because its guard that suppresses an ar= chive-supplied Zone.Identifier stream matches the exact name 'Zone.Identifi= er' while a RAR5 STM record named ':Zone.Identifier:$DATA' is not matched a=
    nd NTFS canonicalizes it to the same stream, overwriting the propagated Int= ernet-zone marker with ZoneId=3D0. A second STM record named '::$DATA' over= writes the extracted file's default data stream, letting an attacker defeat=
    SmartScreen/MotW warnings and spoof file content. 2026-06-28 3.3 CVE-2026-= 58052 [ https://www.cve.org/CVERecord?id=3DCVE-2026-58052 ] 78--xiaozhi-esp=
    32 A weakness has been identified in 78 xiaozhi-esp32 up to 2.2.6. Affected=
    by this issue is the function ParseMessage of the file main/mcp_server.cc =
    of the component MCP Response Handler. This manipulation causes improper sy= nchronization. Remote exploitation of the attack is possible. The attack's = complexity is rated as high. The exploitation is known to be difficult. The=
    exploit has been made available to the public and could be used for attack=
    s. The pull request to fix this issue awaits acceptance. 2026-06-28 3.1 CVE= -2026-13489 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13489 ] 78--xiaoz= hi-esp32 A vulnerability was detected in 78 xiaozhi-esp32 up to 2.2.6. This=
    vulnerability affects the function Application::GetInstance of the file ma= in/protocols/mqtt_protocol.cc of the component MQTT Goodbye Handler. Perfor= ming a manipulation of the argument session_id results in denial of service=
    . The attack is possible to be carried out remotely. The complexity of an a= ttack is rather high. It is stated that the exploitability is difficult. Th=
    e exploit is now public and may be used. The patch is named e182471f8c5a224= 34346bd98da34d3b66c8c8b3e. It is recommended to apply a patch to fix this i= ssue. 2026-06-28 3.7 CVE-2026-13491 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-13491 ] AIDC-AI--ComfyUI-Copilot A flaw has been found in AIDC-AI Co= mfyUI-Copilot up to 2.0.28. This issue affects some unknown processing of t=
    he file backend/controller/conversation_api.py of the component Workflow Ch= eckpoint Restore Handler. Executing a manipulation can lead to improper con= trol of resource identifiers. The attack may be performed from remote. A hi=
    gh complexity level is associated with this attack. The exploitability is a= ssessed as difficult. The exploit has been published and may be used. The p= ull request to fix this issue awaits acceptance. 2026-06-28 3.1 CVE-2026-13= 493 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13493 ] arc53--DocsGPT A = flaw has been found in arc53 DocsGPT up to 0.18.0. The affected element is = the function encrypt_credentials of the file application/security/encryptio= n.py of the component Credential Storage. This manipulation causes insuffic= ient verification of data authenticity. It is possible to initiate the atta=
    ck remotely. The complexity of an attack is rather high. The exploitability=
    is described as difficult. The exploit has been published and may be used.=
    The pull request to fix this issue awaits acceptance. 2026-06-28 3.1 CVE-2= 026-13483 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13483 ] babel--babe=
    l Babel is a compiler for writing next generation JavaScript. Prior to 8.0.= 0-rc.6 and 7.29.6, @babel/core affected by an arbitrary file read via a sou= rceMappingURL comment. Using @babel/core to compile maliciously crafted cod=
    e can allow an attacker to read any source map from the system that is runn= ing Babel, if the attacker controls the input source code, can read the out= put source code, and knows the path of the source map file that they want t=
    o read. This vulnerability is fixed in 8.0.0-rc.6 and 7.29.6. 2026-06-22 3.=
    2 CVE-2026-49356 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49356 ] bitw= arden--server Bitwarden Server before 2026.5.0 contains a JSON injection vu= lnerability in IntegrationTemplateProcessor.ReplaceTokens(), which substitu= tes user-controlled values into event-integration templates without JSON en= coding. When an organization has configured an event integration whose temp= late references a user-controlled token (such as #ActingUserName# or #UserN= ame#, populated from a member's display name), an authenticated member can = set their display name to JSON metacharacters and inject arbitrary key-valu=
    e pairs into the rendered payloads delivered to webhook, SIEM, Slack, Teams=
    , or Datadog endpoints, making injected fields indistinguishable from legit= imate template output. 2026-06-25 3.5 CVE-2026-57522 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-57522 ] Cacti--cacti Cacti is an open source perfor= mance and fault management framework. In versions 1.2.30 and below, the loc= ale-dependent decimal formatting in rrdtool_function_update() can corrupt R= RDtool metric values. The rrdtool_function_update() function checks metric = values with is_numeric() and concatenates them into the RRDtool update comm= and via PHP string interpolation. PHP's string cast of floats is locale-sen= sitive: if LC_NUMERIC uses comma as decimal separator (e.g., de_DE), a valu=
    e of 1.5 becomes "1,5". RRDtool expects . as decimal separator, causing met= ric data to shift into wrong columns or be silently dropped. No setlocale()=
    reset is present in the update path. This causes a data integrity issue, b=
    ut is not remotely exploitable; it requires server locale misconfiguration.=
    The issue has been fixed in version 1.2.31. 2026-06-24 2.9 CVE-2026-39894 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-39894 ] Chess--Play and Learn=
    App A weakness has been identified in Chess Play and Learn App up to 4.9.4=
    2 on Android. This issue affects some unknown processing of the file Androi= dManifest.xml of the component com.chess. This manipulation causes exposure=
    of backup file to an unauthorized control sphere. It is feasible to perfor=
    m the attack on the physical device. The exploit has been made available to=
    the public and could be used for attacks. Upgrading the affected component=
    is advised. The vendor was informed early about this issue. They confirmed=
    the existence and that they will address it. Furthermore, they explain tha=
    t their bug bounty "explicitly excludes physical-access attacks". However, = they appreciate the quality of the report and aim at making a goodwill paym= ent to the researcher. 2026-06-28 2.4 CVE-2026-13514 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-13514 ] code-projects--Project Management System A = vulnerability has been found in code-projects Project Management System 1.0=
    . This vulnerability affects unknown code of the file /mail.php of the comp= onent Mail Compose Page. Such manipulation leads to cross site scripting. T=
    he attack may be performed from remote. The exploit has been disclosed to t=
    he public and may be used. 2026-06-28 3.5 CVE-2026-13504 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-13504 ] earendil-works--pi Pi is a minimal term= inal coding harness. From 0.74.0 until 0.78.1, Pi HTML exports render sessi=
    on Markdown into a static HTML file. It did not consistently reject unsafe = Markdown link and image URL schemes. In versions with scheme filtering, C0 = control characters in the URL scheme could bypass the check because browser=
    s normalize those characters before navigation. This vulnerability is fixed=
    in 0.78.1. 2026-06-23 2.5 CVE-2026-54326 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-54326 ] earendil-works--pi Pi is a minimal terminal coding har= ness. From 0.74.0 until 0.78.1, Pi stored API keys and OAuth credentials in=
    auth.json. A race condition in the file write path could briefly create or=
    rewrite this file with permissions derived from the process umask before t= ightening the file to owner-only permissions. This vulnerability is fixed i=
    n 0.78.1. 2026-06-23 2.2 CVE-2026-54327 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54327 ] GitLab--GitLab GitLab has remediated an issue in GitLab=
    EE affecting all versions from 17.9 before 18.11.6, 19.0 before 19.0.3, an=
    d 19.1 before 19.1.1 that under certain conditions could have allowed an au= thenticated user with custom role permissions to view, create, or delete pr= otected environment configurations despite CI/CD visibility being disabled = for the project. 2026-06-25 3.8 CVE-2026-0934 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-0934 ] GitLab--GitLab GitLab has remediated an issue in Gi= tLab EE affecting all versions from 18.6 before 18.11.6, 19.0 before 19.0.3=
    , and 19.1 before 19.1.1 that under certain conditions could have allowed a=
    n authenticated user with limited permissions to access project information=
    due to insufficient authorization checks. 2026-06-25 3.1 CVE-2026-3176 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-3176 ] glpi-project--glpi A secu= rity vulnerability has been detected in glpi-project glpi 11.0.5/11.0.6/11.= 0.7. This affects the function Document::canViewFile of the file front/docu= ment.send.php of the component Document Handler. Such manipulation of the a= rgument docid leads to authorization bypass. The attack can be executed rem= otely. This attack is characterized by high complexity. It is indicated tha=
    t the exploitability is difficult. The vendor was contacted early about thi=
    s disclosure. 2026-06-28 3.7 CVE-2026-13490 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-13490 ] GNU--GNU SASL GNU SASL before 2.2.4 lacks sanitizati=
    on of a short challenge in _gsasl_ntlm_client_step in the NTLM client, whic=
    h could result in memory disclosure via a crafted server. 2026-06-23 3.7 CV= E-2026-56968 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56968 ] GnuPG--G= nuPG CMS (Cryptographic Message Syntax) parsing in gpgsm in GnuPG through 2= .5.20 mishandles the CMS format for AES-GCM because aes-ICVlen is supposed =
    to be 12 bytes but 4 bytes is accepted. NOTE: this is related to CVE-2026-3= 4182. 2026-06-23 2.9 CVE-2026-57062 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-57062 ] gogs--gogs Gogs is an open source self-hosted Git service. P= rior to 0.14.3, specially crafted issue index pattern can cause a panic whe=
    n rendering, resulting in denial of service. In internal/markup/markup.go, = RenderIssueIndexPattern renders the issue index pattern to a link using com= .Expand, which is not safe: when the configured pattern contains an opening=
    brace { but no closing brace }, strings.Index(template, "}") returns -1 an=
    d the subsequent slice template[:-1] triggers a panic. Once such a pattern =
    is set, any page in the affected repository that contains an issue index re= ference such as #1 becomes unavailable. This vulnerability is fixed in 0.14= .3. 2026-06-24 3.5 CVE-2026-52796 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-52796 ] HCLSoftware--Connections HCL Connections contains a broken acc= ess control vulnerability that may allow an unauthorized user to view data =
    in a single specific scenario. 2026-06-23 3.5 CVE-2025-15619 [ https://www.= cve.org/CVERecord?id=3DCVE-2025-15619 ] IBM--Datacap IBM Datacap 9.1.7, 9.1= .8, and 9.1.9 and IBM Datacap Navigator 9.1.7, 9.1.8, and 9.1.9 exposes res= ources or functionality that isn't linked in the UI but is accessible by di= rectly requesting the URL, bypassing intended access controls. 2026-06-22 2=
    .3 CVE-2026-9610 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9610 ] Image= Magick--ImageMagick ImageMagick before 7.1.2-15 contains a memory leak vuln= erability in multiple coders that write raw pixel data where allocated obje= cts are not properly freed. Attackers can trigger this leak by processing s= pecially crafted images, causing memory exhaustion and denial of service. 2= 026-06-24 3.7 CVE-2026-56368 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 56368 ] ImageMagick--ImageMagick ImageMagick before 7.1.2-19 contains an ou= t-of-bounds access vulnerability in ConnectedComponentsImage() when process= ing connected-components artifacts with invalid indices. Attackers can trig= ger access violations by specifying malformed connected-components definiti= ons via CLI, causing denial of service or potential code execution. 2026-06= -24 3.3 CVE-2026-56370 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56370 =
    ] ImageMagick--ImageMagick ImageMagick before 7.1.2-15 and 6.9.13-40 contai=
    ns a heap use-after-free in the meta coder: when memory allocation fails, a=
    single byte is written to a stale pointer. Remote attackers can trigger it=
    by processing specially crafted image files, causing a denial of service. = 2026-06-23 3.7 CVE-2026-56376 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -56376 ] JetBrains--YouTrack In JetBrains YouTrack before 2026.2.16593 proj= ect settings disclosure via the MCP was possible 2026-06-26 3.1 CVE-2026-57= 922 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57922 ] JetBrains--YouTra=
    ck In JetBrains YouTrack before 2026.2.16593 the websandbox bridge was vuln= erable to a prototype pollution attack 2026-06-26 2.6 CVE-2026-57926 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-57926 ] Kludex--python-multipart Py= thon-Multipart is a streaming multipart parser for Python. Prior to 0.0.30,=
    parse_options_header parsed Content-Disposition (and Content-Type) headers=
    with email.message.Message, which transparently applies RFC 2231/5987 deco= ding. The extended parameter syntax (filename*=3Dcharset'lang'value, name*= =3D..., and the filename*0/filename*1 continuation form) is decoded and sur= faced under the bare filename/name key, and overrides the plain parameter w= hen both are present. RFC 7578 =C3=82=C2=A74.2 explicitly forbids the filen= ame* form in multipart/form-data. Components that follow RFC 7578, or that =
    do not implement RFC 2231/5987 decoding for multipart/form-data (WAFs, prox= ies, gateways), may interpret such a header differently. An attacker can ex= ploit that difference to smuggle a different field name or filename past an=
    upstream inspector to the backend. This vulnerability is fixed in 0.0.30. = 2026-06-22 3.7 CVE-2026-53537 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -53537 ] Kludex--python-multipart Python-Multipart is a streaming multipart=
    parser for Python. Prior to 0.0.30, QuerystringParser treated ; as a field=
    separator in application/x-www-form-urlencoded bodies, in addition to &. T=
    he WHATWG URL standard, modern browsers, and Python's urllib.parse (since t=
    he CVE-2021-23336 fix) treat only & as a separator. This creates a parser d= ifferential: the same bytes are tokenized into different fields than a WHAT=
    WG compliant intermediary would produce, allowing an attacker to smuggle ex= tra form fields past an upstream body inspecting component. This vulnerabil= ity is fixed in 0.0.30. 2026-06-22 3.7 CVE-2026-53538 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-53538 ] Kludex--python-multipart Python-Multipart =
    is a streaming multipart parser for Python. Prior to 0.0.31, parse_form() d=
    id not validate the Content-Length header before using it to bound its chun= ked read of the request body. A negative Content-Length turned the bounded = read into a read-until-EOF, so the entire body was loaded into memory in a = single read instead of in fixed-size chunks. This vulnerability is fixed in=
    0.0.31. 2026-06-22 3.7 CVE-2026-53540 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53540 ] Kludex--starlette Starlette is a lightweight ASGI frame= work/toolkit. Prior to 1.3.0, the HTTP request path is not validated before=
    being used to reconstruct request.url. Because request.url is rebuilt by c= oncatenating {scheme}://{host}{path} and re-parsing the result, a path that=
    does not begin with / (for example @google.com) moves the authority bounda=
    ry during re-parsing, so request.url.hostname and request.url.netloc become=
    attacker-controlled. Code that reads request.url.hostname (rather than the=
    Host header or scope) can therefore be misled into trusting an attacker-su= pplied host. This vulnerability is fixed in 1.3.0. 2026-06-22 3.7 CVE-2026-= 54282 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54282 ] Mattermost--Mat= termost Mattermost versions 10.11.x <=3D 10.11.18, 11.6.x <=3D 11.6.3, 11.5=
    .x <=3D 11.5.6 fail to properly apply markdown image rendering restrictions=
    to AI bot tool result posts, which allows an authenticated attacker to exf= iltrate data to an attacker-controlled server via injecting markdown image = syntax into tool result content rendered by a victim's client.. Mattermost = Advisory ID: MMSA-2026-00619 2026-06-26 3.5 CVE-2026-3472 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-3472 ] Mattermost--Mattermost Mattermost versi= ons 11.7.x <=3D 11.7.0, 10.11.x <=3D 10.11.17 fail to enforce bot-specific = permission checks on the user active status endpoint, which allows a User M= anager with user management write access but no Integrations access to deac= tivate bot accounts via the PUT /api/v4/users/{id}/active API endpoint.. Ma= ttermost Advisory ID: MMSA-2026-00667 2026-06-22 3.8 CVE-2026-8074 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-8074 ] Mattermost--Mattermost Matterm= ost versions 11.7.x <=3D 11.7.0, 10.11.x <=3D 10.11.17 fail to validate bot=
    targets when demoting users to guests which allows a lower-privileged admi= nistrator to degrade arbitrary bot accounts via the standard demote-user AP= I.. Mattermost Advisory ID: MMSA-2026-00669 2026-06-22 3.8 CVE-2026-8823 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-8823 ] nocodb--nocodb NocoDB is=
    software for building databases as spreadsheets. Prior to 2026.04.1, the O= Auth token strategy attached oauth_scope and oauth_granted_resources to the=
    request user, but the ACL middleware never consulted either. An OAuth toke=
    n issued with a restricted scope (e.g. MCP-only) therefore inherited the fu=
    ll permissions of the underlying user across all routes; the granted_resour= ces.base_id restriction was bypassed on org-level endpoints that don't popu= late req.context.base_id. This vulnerability is fixed in 2026.04.1. 2026-06= -23 2 CVE-2026-46549 [ https://www.cve.org/CVERecord?id=3DCVE-2026-46549 ] = PowerDNS--DNSdist An attacker sending a large number of crafted DNS queries=
    might be able to trigger a dynamic block being inserted with a value causi=
    ng invalid output to be produced in the prometheus endpoint. The prometheus=
    endpoint will then be rejected by the scraper until the dynamic block expi= res. 2026-06-25 3.7 CVE-2026-40011 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-40011 ] PowerDNS--DNSdist An attacker might be able to delay the proc= essing of DoH3 queries by sending DoH3 GET queries with an invalid DATA fra= me. 2026-06-25 3.7 CVE-2026-40208 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-40208 ] PowerDNS--DNSdist An attacker can send a crafted EDNS OPT reco=
    rd that will be ignored by DNSdist's filtering rules, but will be rewritten=
    as a valid OPT record when EDNS Client Subnet is inserted, causing the bac= kend to see the EDNS option(s) that DNSdist did not filter. 2026-06-25 3.7 = CVE-2026-42004 [ https://www.cve.org/CVERecord?id=3DCVE-2026-42004 ] Rapid7= --InsightConnect Compression Plugin Path Traversal vulnerability in the cre= ate_archive function of Rapid7 InsightConnect Compression Plugin on Linux a= llows authenticated attackers to write to unintended file paths via crafted=
    filename input. The impact is limited to file corruption as content cannot=
    be controlled by the attacker. 2026-06-25 3.3 CVE-2026-8662 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-8662 ] Red Hat--Red Hat Enterprise Linux 10=
    A flaw was found in OpenSSH. This vulnerability, a heap out-of-bounds read=
    , occurs during the cleanup of GSSAPI (Generic Security Service Application=
    Programming Interface) indicators when a trailing NULL termination is miss= ing in the auth-indicators array. A remote attacker, under specific configu= rations involving GSSAPI authentication and a Kerberos environment, could e= xploit this to cause the SSH authentication path to crash or abort. This le= ads to a denial of service (DoS), impacting the availability of the SSH ser= vice. 2026-06-23 3.7 CVE-2026-55654 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-55654 ] Red Hat--Red Hat OpenShift Virtualization 4 A flaw was found=
    in KubeVirt's downward metrics virtio-serial server. The server reads gues=
    t requests using textproto.Reader.ReadLine(), which buffers input indefinit= ely until a newline character is received, with no length limit or read dea= dline. A user with access to a VM guest that has the downward metrics virti= o-serial device configured can write a continuous byte stream to the device=
    , causing unbounded memory allocation in the virt-handler process until it =
    is OOM-killed. 2026-06-26 3.8 CVE-2026-13322 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-13322 ] remix-run--react-router React Router is a router fo=
    r React. From 7.12.0 until 7.15.1, certain CSRF checks in React Router v7 F= ramework Mode were insufficient and run on POST requests, but were bypassed=
    on PUT/PATCH/DELETE requests. This is a low severity vulnerability because=
    modern browser protections (CORS preflight, SameSite cookies) already bloc=
    k the cross-origin attack vectors that this missing CSRF check would otherw= ise gate. This vulnerability is fixed in 7.15.1. 2026-06-22 3.1 CVE-2026-53= 663 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53663 ] SimStudioAI--sim =
    A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this=
    vulnerability is an unknown functionality in the library apps/sim/lib/core= /security/deployment.ts of the component Password Protection Handler. Perfo= rming a manipulation results in use of weak hash. The attack is possible to=
    be carried out remotely. The attack's complexity is rated as high. The exp= loitation appears to be difficult. The exploit has been made public and cou=
    ld be used. The pull request to fix this issue awaits acceptance. 2026-06-2=
    8 3.7 CVE-2026-13510 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13510 ] = skypilot-org--skypilot A vulnerability was detected in skypilot-org skypilo=
    t up to 0.12.0. Impacted is the function username.encode of the file sky/us= ers/server.py of the component User ID Handler. The manipulation results in=
    use of weak hash. The attack may be performed from remote. This attack is = characterized by high complexity. The exploitability is considered difficul=
    t. The exploit is now public and may be used. The vendor was contacted earl=
    y about this disclosure. 2026-06-28 3.7 CVE-2026-13482 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-13482 ] sparklemotion--nokogiri Nokogiri is an op=
    en source XML and HTML library for the Ruby programming language. Prior to = 1.19.4, the NONET parse option, which Nokogiri turns on by default for Noko= giri::XML::Schema (see CVE-2020-26247), was not correctly enforced on the J= Ruby implementation. As a result, a schema parsed with default options coul=
    d still cause external resources to be fetched over the network, potentiall=
    y enabling SSRF or XXE attacks. This vulnerability is fixed in 1.19.4. 2026= -06-25 2.6 CVE-2026-57234 [ https://www.cve.org/CVERecord?id=3DCVE-2026-572=
    34 ] tenable--Nessus A SQL injection vulnerability in Nessus allows an atta= cker to craft a malicious scan result file that, when imported by a privile= ged user, injects malicious SQL into the scan results database, potentially=
    enabling exfiltration of scan-result data. 2026-06-25 3.3 CVE-2026-57588 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-57588 ] VoltAgent--VoltAgent A=
    vulnerability was determined in VoltAgent up to 2.1.17. Affected by this i= ssue is the function handleGetMemoryConversation of the file packages/serve= r-core/src/handlers/memory.handlers.ts of the component Memory REST API. Ex= ecuting a manipulation of the argument conversationId can lead to improper = authorization. The attack may be performed from remote. This attack is char= acterized by high complexity. The exploitation is known to be difficult. Th=
    e exploit has been publicly disclosed and may be utilized. The pull request=
    to fix this issue awaits acceptance. 2026-06-28 3.1 CVE-2026-13511 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-13511 ]=20

    Back to top [ #top ]

    Severity Not Yet Assigned

    Primary
    Vendor -- Product Description Published CVSS Score Source Info AcademySoftw= areFoundation--OpenColorIO OpenColorIO is a color management framework for = visual effects and animation. Prior to version 2.5.2, `FileFormatSpi3D.cpp:= 163` uses `sscanf` with `%s` into 64-byte stack buffers when parsing LUT da=
    ta lines. Input comes from `lineBuffer[4096]`, so a crafted .spi3d file can=
    overflow by ~4000 bytes on non-Windows. Version 2.5.2 fixes the issue. 202= 6-06-24 not yet calculated CVE-2026-42450 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-42450 ] ail project--ail framework A path traversal vulnerabil= ity exists in AIL Framework before the release containing commit 0041456af2= 5da0cdea1c1c4624e46baff2731d8f. An authenticated AIL user can supply crafte=
    d object identifiers through the investigation workflow to cause file paths=
    to resolve outside the intended image, favicon, or screenshot storage dire= ctories. This may allow the attacker to download and read arbitrary files t= hat are accessible to the AIL process. The issue occurs because user-contro= lled path components were joined with application storage paths without ver= ifying that the resolved path remained within the expected directory. The a= ffected download functionality could then include the contents of such file=
    s in a generated archive. 2026-06-22 not yet calculated CVE-2026-56448 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-56448 ] ail project--ail framewor=
    k AIL did not restrict repeated failed attempts to verify a two-factor auth= entication (OTP) code. An attacker who had reached the 2FA verification ste=
    p, such as after successfully completing the password-authentication stage,=
    could submit an unlimited number of OTP guesses. This could enable brute-f= orce guessing of a valid code and bypass the intended second authentication=
    factor, resulting in unauthorized account access. The patch introduces per= -user failed-OTP tracking, blocks verification after 30 failed attempts for=
    one hour, clears the counter after a successful OTP verification, and prov= ides administrator recovery actions to purge affected lockouts. 2026-06-22 = not yet calculated CVE-2026-56450 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-56450 ] aio-libs--aiohttp AIOHTTP is an asynchronous HTTP client/serve=
    r framework for asyncio and Python. Prior to 3.14.0, attacker-controlled in= put included into multipart/payload headers can be used to modify a request=
    to inject additional headers or similar. In the unlikely situation that an=
    application is passing user-controlled strings into MultipartWriter.append= (headers=3D...) or Payload.headers, then an attacker may be able to modify = the request to inject headers or change the contents of the request. This v= ulnerability is fixed in 3.14.0. 2026-06-22 not yet calculated CVE-2026-502=
    69 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50269 ] aio-libs--aiohttp = AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Pyt= hon. Prior to 3.14.1, no limit was present on the number of pipelined reque= sts that could be queued. An attacker may be able to use pipelined requests=
    to use excessive amounts of memory, potentially leading to DoS. This vulne= rability is fixed in 3.14.1. 2026-06-22 not yet calculated CVE-2026-54273 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-54273 ] aio-libs--aiohttp AIOH= TTP is an asynchronous HTTP client/server framework for asyncio and Python.=
    Prior to 3.14.1, if an attacker sends large incomplete websocket frame pay= loads, it may be possible to bypass the usual size limits on memory use. Th=
    is vulnerability is fixed in 3.14.1. 2026-06-22 not yet calculated CVE-2026= -54274 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54274 ] aio-libs--aioh= ttp AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed=
    when an existing connection is reused. If an application makes multiple re= quests to the same domain, but with different per-request server_hostname p= arameters, then the later calls may succeed by reusing the existing connect= ion when they should have been rejected due to the TLS SNI check. This vuln= erability is fixed in 3.14.1. 2026-06-22 not yet calculated CVE-2026-54275 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-54275 ] aio-libs--aiohttp AIO= HTTP is an asynchronous HTTP client/server framework for asyncio and Python=
    . Prior to 3.14.1, DigestAuthMiddleware can send an authentication response=
    after following a cross-origin redirect. This likely requires an open redi= rect vulnerability or similar on the target domain for an attacker to be ab=
    le to execute. Further, the attacker is only receiving the digest, so shoul=
    d only be able to extract the user's credentials if the cryptography is wea=
    k or there is some kind of password reuse. This vulnerability is fixed in 3= .14.1. 2026-06-22 not yet calculated CVE-2026-54276 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-54276 ] aio-libs--aiohttp AIOHTTP is an asynchronous=
    HTTP client/server framework for asyncio and Python. Prior to 3.14.1, it i=
    s possible to bypass the max_line_size check in parts of an HTTP request in=
    the C parser. If using the optimised C parser (the default in pre-built wh= eels), then an attacker may be able to send oversized lines through the HTT=
    P parser and use an excessive amount of memory, potentially leading to DoS.=
    This vulnerability is fixed in 3.14.1. 2026-06-22 not yet calculated CVE-2= 026-54277 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54277 ] aio-libs--a= iohttp AIOHTTP is an asynchronous HTTP client/server framework for asyncio = and Python. Prior to 3.14.1, during cleanup it is possible for a compressed=
    request body to be decompressed into memory in one chunk. An attacker may =
    be able to send a compressed payload in specific situations that could be d= ecompressed into memory, potentially leading to DoS (a zip bomb edge case).=
    This vulnerability is fixed in 3.14.1. 2026-06-22 not yet calculated CVE-2= 026-54278 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54278 ] aio-libs--a= iohttp AIOHTTP is an asynchronous HTTP client/server framework for asyncio = and Python. Prior to 3.14.1, host-only cookies that are saved with CookieJa= r.save() and then restored later with CookieJar.load() lose their host-only=
    status. This vulnerability is fixed in 3.14.1. 2026-06-22 not yet calculat=
    ed CVE-2026-54279 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54279 ] aio= -libs--aiohttp AIOHTTP is an asynchronous HTTP client/server framework for = asyncio and Python. Prior to 3.14.1, payload resources are not closed corre= ctly when a client disconnects in the middle of a write. If a payload is us= ing an open file or similar limited resource, then an attacker may be able =
    to cause resource starvation temporarily until garbage collection or simila=
    r closes the file. This vulnerability is fixed in 3.14.1. 2026-06-22 not ye=
    t calculated CVE-2026-54280 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 4280 ] Akaunting--Akaunting Akaunting 3.1.21 contains an authenticated stor=
    ed cross-site scripting vulnerability in the reusable delete confirmation f= low. A user with permission to create or modify records, such as Items, can=
    store HTML/JavaScript in the record name. 2026-06-22 not yet calculated CV= E-2026-11942 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11942 ] Akauntin= g--Akaunting Akaunting 3.1.21 contains an authenticated stored cross-site s= cripting vulnerability in the document timeline shown on invoice and bill d= etail pages. An authenticated user can store HTML/JavaScript in their own p= rofile name. 2026-06-22 not yet calculated CVE-2026-11943 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-11943 ] Akaunting--Akaunting Akaunting 3.1.21 = contains an authenticated stored Cross-Site Scripting vulnerability in the = report management workflow. A user with permission to create or update repo= rts can store arbitrary HTML/JavaScript in the description field of a repor=
    t. 2026-06-22 not yet calculated CVE-2026-11994 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-11994 ] AMD--AMD Athlon 3000 Series Mobile Processors wi=
    th Radeon Graphics An observable timing discrepancy in the ASP could allow =
    a privileged attacker to perform a brute-force attack against the hash mess= age authentication code, allowing the input of an arbitrary message, potent= ially leading to a loss of data integrity. 2026-06-26 not yet calculated CV= E-2023-20572 [ https://www.cve.org/CVERecord?id=3DCVE-2023-20572 ] AMD--AMD=
    Ryzen 3000 Series Desktop Processors An observable timing discrepancy in t=
    he ASP could allow a privileged attacker to perform a brute-force attack ag= ainst the hash message authentication code, allowing arbitrary message inpu=
    t, potentially leading to a loss of data integrity. 2026-06-26 not yet calc= ulated CVE-2023-20540 [ https://www.cve.org/CVERecord?id=3DCVE-2023-20540 ]=
    angular--angular Angular is a development platform for building mobile and=
    desktop web applications using TypeScript/JavaScript and other languages. = Prior to 22.0.0-next.12, 21.2.13, 20.3.21, and 19.2.22, a Server-Side Reque=
    st Forgery (SSRF) vulnerability exists in @angular/platform-server. The iss=
    ue stems from how the server-side rendering (SSR) engine processes the requ= est URL provided to the rendering entry points. When an absolute-form URL (= e.g., http://evil.com) is passed to the rendering engine, the internal Serv= erPlatformLocation can be manipulated into adopting the attacker-controlled=
    domain as the "current" hostname. Consequently, any relative HttpClient re= quests or PlatformLocation.hostname references are redirected to the attack=
    er controlled server, potentially exposing internal APIs or metadata servic= es. This vulnerability is fixed in 22.0.0-next.12, 21.2.13, 20.3.21, and 19= .2.22. 2026-06-22 not yet calculated CVE-2026-46417 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-46417 ] angular--angular The Angular Language Servic=
    e VS Code Extension provides a rich editing experience for Angular template=
    s. Prior to 21.2.4, the client-side Angular Language Service VS Code extens= ion reads the custom TypeScript SDK paths typescript.tsdk and js/ts.tsdk.pa=
    th directly from workspace configurations (.vscode/settings.json) without v= erifying VS Code Workspace Trust state or asking for user consent (located =
    in client/src/client.ts). The client-side extension then passes the parsed = settings path as a command-line argument (--tsdk) to the background Node.js=
    language server process. During server initialization, the background lang= uage server resolves and dynamically imports (via standard Node.js require(=
    )) the module library tsserverlibrary.js relative to the workspace-specifie=
    d custom directory path. An attacker can exploit this behavior by committin=
    g a repository containing a local malicious tsserverlibrary.js script insid=
    e a custom folder, and a crafted .vscode/settings.json file pointing to tha=
    t folder. When a developer opens the repository folder in VS Code, the exte= nsion automatically attempts to initialize and load the server, which dynam= ically resolves, loads, and executes the malicious script silently in the b= ackground. This vulnerability is fixed in 21.2.4. 2026-06-22 not yet calcul= ated CVE-2026-49241 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49241 ] a= ngular--angular Angular is a development platform for building mobile and d= esktop web applications using TypeScript/JavaScript and other languages. Pr= ior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23, an issue in the @angular= /platform-server package allows remote attackers to bypass host allowlist c= onstraints and direct server-side outgoing requests to arbitrary external e= ndpoints. This occurs due to a parser differential between the strict WHATW=
    G URL parser used for allowlist validation and the lenient Domino URL parse=
    r used to initialize the server emulated DOM. When a server-side request co= ntains a malformed URL with a double port structure (e.g., http://evil.com:= 80:80/path), Node's strict URL.canParse(url) logic returns false and skips = host check validation entirely. However, the same malformed URL is later ac= cepted and parsed leniently by Domino's internal parser, which resolves the=
    origin to http://evil.com:80. The Angular SSR HTTP request interceptor (re= lativeUrlsTransformerInterceptorFn) then resolves all relative backend HTTP=
    requests against this adopted origin, executing the SSRF attack. This vuln= erability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23. 2026-06-2=
    2 not yet calculated CVE-2026-50168 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-50168 ] angular--angular Angular is a development platform for build= ing mobile and desktop web applications using TypeScript/JavaScript and oth=
    er languages. Prior to 22.0.0-rc.2, 21.2.15 20.3.22, and 19.2.23, an issue =
    in the @angular/service-worker package compromises the integrity of request= -policy enforcement during request reconstruction. When the Angular Service=
    Worker intercepts network requests for matched assets, it reconstructs a n=
    ew Request object using an internal helper function. During this reconstruc= tion process, the helper function strips the strict, client-defined request=
    redirect policy configuration (such as redirect: 'error'), falling back to=
    the browser's default 'follow' strategy. If the target web application mak=
    es client-side requests with a strict policy (e.g., expecting a network err=
    or instead of automatically following redirects), the service worker will b= ypass this instruction and automatically follow HTTP 3xx redirects to other=
    destinations. This acts as an unintended proxy/intermediary ("Confused Dep= uty") and can result in cookie/credential exposure or same-origin session-r= estricted data leakage if public dynamic routes redirect to sensitive route=
    s. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.2=
    3. 2026-06-22 not yet calculated CVE-2026-50169 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-50169 ] angular--angular Angular is a development platfo=
    rm for building mobile and desktop web applications using TypeScript/JavaSc= ript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.= 23, a vulnerability was discovered in @angular/common when Server-Side Rend= ering (SSR) and hydration are enabled. The HttpTransferCache utility optimi= zes hydration by caching outgoing HTTP requests performed during SSR and tr= ansferring the cached state to the client-side application via TransferStat=
    e. However, the caching mechanism fails to inspect the withCredentials flag=
    or the Cookie header of outgoing requests. As a result, credentialed, user= -specific responses may be cached by default in the shared TransferState pa= yload. When these responses are serialized into the HTML, any caching layer=
    (such as a CDN, reverse proxy, or shared server cache) that caches the SSR= -rendered HTML page could inadvertently cache and leak one user's private d= ata to other users, leading to a high-severity information disclosure vulne= rability. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and=
    19.2.23. 2026-06-22 not yet calculated CVE-2026-50170 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-50170 ] angular--angular Angular is a development=
    platform for building mobile and desktop web applications using TypeScript= /JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, an=
    d 19.2.23, a Denial of Service (DoS) vulnerability exists in the @angular/c= ommon package of Angular. The formatNumber function, which is also utilized=
    by DecimalPipe, PercentPipe, and CurrencyPipe, does not properly validate = the upper bounds of the digitsInfo parameter. Specifically, the minimum and=
    maximum fraction digits parsed from the digitsInfo string (e.g., 1.2-4) ar=
    e converted to integers and used without limits. When parsing a maliciously=
    crafted digitsInfo string with excessively large fraction digit values (e.= g., 1.200000000-200000000), the internal roundNumber function attempts to p=
    ad the digits array to match the requested fraction size. This results in a=
    n unbounded loop that repeatedly pushes elements into an array. This vulner= ability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23. 2026-06-22 = not yet calculated CVE-2026-50171 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-50171 ] angular--angular The Angular Language Service VS Code Extensio=
    n provides a rich editing experience for Angular templates. the client-side=
    Angular Language Service VS Code extension configures the tooltip Markdown=
    renderer with the isTrusted: true option (located in client/src/client.ts)=
    . This setting instructs VS Code to trust all rendered content it receives,=
    which enables active elements such as command: URIs. However, the backgrou=
    nd Angular Language Server process fails to escape or sanitize brackets, ra=
    w links, and control characters from JSDoc strings before forwarding the ho= ver Markdown content (located in server/src/handlers/hover.ts and server/sr= c/text_render.ts). An attacker can leverage this behavior by crafting a pro= ject TypeScript or JavaScript file (or a third-party npm package dependency=
    ) containing a malicious JSDoc tooltip with an embedded active command link=
    . When a developer hovers over the target symbol to render the tooltip and = clicks the malicious link, the IDE executes the command sequence directly o=
    n the developer's host machine. Prior to 21.2.4, This vulnerability is fixe=
    d in 21.2.4. 2026-06-22 not yet calculated CVE-2026-50178 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-50178 ] angular--angular Angular is a developm= ent platform for building mobile and desktop web applications using TypeScr= ipt/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22,=
    and 19.2.23, an issue in the @angular/service-worker package compromises t=
    he integrity of request-policy enforcement during request reconstruction. W= hen the Angular Service Worker intercepts network requests for matched asse= ts, it reconstructs a new Request object using an internal helper function.=
    During this reconstruction process, the helper function strips explicit cl= ient-defined safety parameters: the credentials configuration (such as cred= entials: 'omit') and the HTTP cache mode configuration (such as cache: 'no-= store'). These are reverted back to standard browser-default parameters (cr= edentials: 'same-origin' and default HTTP cache properties). This causes th=
    e browser to include active credentials (such as cookies or Authorization h= eaders) on outbound requests where the client-side developer explicitly ins= tructed they should be omitted, leading to potential session leaks. Additio= nally, it causes private or non-cacheable resources to be cached by the ser= vice worker's engine, making private page states accessible or persistent i= nside the client's local cache post-logout. This vulnerability is fixed in = 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23. 2026-06-22 not yet calculated C= VE-2026-50184 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50184 ] angular= --angular Angular is a development platform for building mobile and desktop=
    web applications using TypeScript/JavaScript and other languages. Prior to=
    22.0.0-rc.2, 21.2.16, 20.3.24, and 19.2.25, a Cross-Site Scripting (XSS) v= ulnerability exists in @angular/platform-server's DOM emulation dependency = (domino) when serializing the content of raw-text elements (such as <script=
    , <style>, and <iframe>). domino supports escaping raw-text elements durin=
    g serialization to prevent closing-tag breakout. However, a Unicode index a= lignment bug existed in this escaping logic. In JavaScript, string lengths = and character indices are calculated based on UTF-16 code units (where astr=
    al characters-such as emojis-occupy 2 code units / 4 bytes). If the bound d= ynamic text contained astral Unicode characters before the closing tag (e.g=
    . </script>, </style>, or </iframe>), the index offset calculation in domin= o's replacement logic shifted. This misalignment caused domino to fail to r= eplace or escape the closing tag, leaving it raw and unescaped in the outpu=
    t HTML. An attacker who controls the dynamic text can supply a payload cont= aining both an astral Unicode character and a closing tag (e.g., =C3=B0=C5= =B8=CB=9C=E2=82=AC</iframe><script>alert(1)</script>). When serialized on t=
    he server during SSR, the browser parses the unescaped closing tag, exits t=
    he raw-text context early, and executes the subsequent <script> block, lead= ing to same-origin Cross-Site Scripting (XSS). This vulnerability is fixed =
    in 22.0.0-rc.2, 21.2.16, 20.3.24, and 19.2.25. 2026-06-22 not yet calculate=
    d CVE-2026-50555 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50555 ] angu= lar--angular Angular is a development platform for building mobile and desk= top web applications using TypeScript/JavaScript and other languages. Prior=
    to 22.0.0-rc.2, 21.2.16, 20.3.24, and 19.2.25, a Cross-Site Scripting (XSS=
    ) vulnerability exists in @angular/platform-server's DOM emulation dependen=
    cy (domino) when serializing the content of <noscript> elements. When rende= ring dynamic text content inside a <noscript> element via template bindings=
    (such as {{ value }} or [textContent]), the template engine expects the br= owser to render the content safely. Under Server-Side Rendering (SSR), domi=
    no is configured with scripting enabled, meaning <noscript> is treated as a=
    raw-text element. However, domino's serializer completely omitted <noscrip=
    from the list of raw-text elements requiring closing-tag escaping during=
    DOM serialization. As a result, any occurrence of </noscript> in the bound=
    dynamic text was never escaped under any circumstances. The unescaped clos= ing tag was serialized directly into the output HTML (e.g. <noscript></nosc= ript><script>alert(1)</script></noscript>). When parsed by a browser, it cl= oses the <noscript> block early, allowing the injected <script> block to ex= ecute in the user's browser context, causing same-origin Cross-Site Scripti=
    ng (XSS). This vulnerability is fixed in 22.0.0-rc.2, 21.2.16, 20.3.24, and=
    19.2.25. 2026-06-22 not yet calculated CVE-2026-50556 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-50556 ] angular--angular Angular is a development=
    platform for building mobile and desktop web applications using TypeScript= /JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22 and=
    19.2.22, an issue in the @angular/compiler and @angular/core packages allo=
    ws bypassing element and attribute sanitization/validation through specific=
    namespace workarounds. Specifically, namespaced script elements (e.g., <sv= g:script> or <:svg:script>) were not properly identified as script elements=
    by the Angular template preparser, allowing them to pass through template = compilation without being stripped. Furthermore, security context schema ma= ppings for element attributes did not consistently handle attributes within=
    namespaced elements (like SVG and MathML), opening up gaps where malicious=
    namespaced attributes could bypass runtime and compile-time sanitizers. Co= mbined, these flaws enable an attacker who can inject or supply a template/= tag structure with custom namespaces to bypass Angular's script-stripping l= ogic and attribute sanitizers, leading to client-side Cross-Site Scripting = (XSS). This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22 and 19.= 2.22. 2026-06-22 not yet calculated CVE-2026-50557 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-50557 ] angular--angular Angular is a development pla= tform for building mobile and desktop web applications using TypeScript/Jav= aScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19= .2.23, an issue in the @angular/core package allows bypassing script-execut= ion restrictions during dynamic component creation. Specifically, the dynam=
    ic component instantiation mechanism (createComponent) failed to reject mou= nting components directly onto a <script> or namespaced script element (suc=
    h as <svg:script>). This enabled the initialization of custom components on=
    a tag that executes scripts, allowing attackers to hijack or inject script= -executing hosts. This flaw enables an attacker who can control the host el= ement or selector parameter passed to createComponent to initialize or moun=
    t an Angular component directly onto a <script> tag, leading to execution o=
    f untrusted code or client-side Cross-Site Scripting (XSS). This vulnerabil= ity is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23. 2026-06-22 not = yet calculated CVE-2026-52725 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -52725 ] angular--angular Angular is a development platform for building mo= bile and desktop web applications using TypeScript/JavaScript and other lan= guages. Prior to 22.0.1, 21.2.17, and 20.3.25, an information disclosure vu= lnerability exists in the @angular/service-worker package of the Angular fr= amework. When the Service Worker fetches assets, it preserves metadata (suc=
    h as headers) from the original request. However, on cross-origin redirects=
    , the Service Worker fails to strip sensitive headers, violating the Fetch = redirect algorithm. This allows a remote attacker to obtain sensitive crede= ntials (e.g., Authorization tokens, Proxy-Authorization credentials, or ses= sion cookies) by triggering a cross-origin redirect to an untrusted externa=
    l origin. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25. 2026= -06-22 not yet calculated CVE-2026-54264 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54264 ] angular--angular Angular is a development platform for = building mobile and desktop web applications using TypeScript/JavaScript an=
    d other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, an issue in the @= angular/compiler package allows bypassing DOM property sanitization through=
    the use of two-way property bindings. Specifically, when a native DOM prop= erty that requires sanitization (such as innerHTML, srcdoc, src, href, data=
    , or sandbox) is bound using the two-way binding syntax (e.g., [(innerHTML)= ]=3D"value" or bindon-innerHTML=3D"value"), the Angular template compiler f= ailed to apply the appropriate schema-derived sanitizer resolution to the T= woWayProperty operation. As a result, native two-way DOM bindings were emit= ted without the required sanitizer function, whereas equivalent one-way bin= dings would be properly sanitized. This flaw enables an attacker who can co= ntrol the value of a two-way bound sensitive property to bypass Angular's b= uilt-in sanitization logic, potentially leading to client-side Cross-Site S= cripting (XSS). This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25=
    . 2026-06-22 not yet calculated CVE-2026-54265 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-54265 ] angular--angular Angular is a development platfor=
    m for building mobile and desktop web applications using TypeScript/JavaScr= ipt and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, Angular's H= ttpTransferCache caches HTTP requests made during Server-Side Rendering (SS=
    R) so that they can be reused during client-side hydration. This avoids rep= eating the same HTTP requests on the client. The cached responses are store=
    d in TransferState using a cache key generated by hashing request propertie=
    s (method, response type, mapped URL, serialized body, and sorted query par= ameters). The cache keys are generated using a weak 32-bit DJB2-like polyno= mial rolling hash. The 32-bit hash space is extremely small, allowing attac= kers to find hash collisions. An attacker can easily find a query parameter=
    string (e.g., q=3DaaCAZMMM for a search request) that produces the exact s= ame 32-bit hash as a sensitive endpoint (e.g., /api/user/profile). When a v= ictim visits a crafted link containing the colliding parameter, the SSR pro= cess executes both the search request and the profile request. Due to the h= ash collision, the search response overwrites the profile response in the T= ransferState cache. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.= 3.25. 2026-06-22 not yet calculated CVE-2026-54266 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-54266 ] angular--angular Angular is a development pla= tform for building mobile and desktop web applications using TypeScript/Jav= aScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, to opti= mize client-side bootstrap in Server-Side Rendered (SSR) environments, Angu= lar supports Hydration via provideClientHydration(). During SSR, Angular se= rializes the application's runtime state (such as cached HttpClient respons= es) and outputs it into the HTML stream as a <script> tag with a predictabl=
    e identifier. During client bootstrap, Angular recovers this state by looki=
    ng up the element via document.getElementById('ng-state') and parsing its t= ext content. Because the DOM element lookup for the state container is pred= ictable and relies solely on the ID selector (ng-state), it is susceptible =
    to DOM Clobbering. If the application binds untrusted user input or CMS con= tent to element properties such as id (e.g., <div [id]=3D"userInput"> or <a=
    id=3D"ng-state">) before the genuine <script> tag is parsed by the browser=
    , the attacker-controlled element takes precedence in the DOM lookup. Durin=
    g hydration, when Angular calls document.getElementById('ng-state'), the br= owser returns the attacker's clobbered element. Angular then attempts to pa= rse the text content or attributes of this clobbered element as JSON. This = vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25. 2026-06-22 not yet = calculated CVE-2026-54267 [ https://www.cve.org/CVERecord?id=3DCVE-2026-542=
    67 ] angular--angular Angular is a development platform for building mobile=
    and desktop web applications using TypeScript/JavaScript and other languag= es. Prior to 22.0.1, 21.2.17, and 20.3.25, a Denial of Service (DoS) vulner= ability exists in the @angular/common package of the Angular framework. The=
    formatDate function, which is also utilized by the standard Angular DatePi= pe, does not properly limit or validate the length of the format parameter.=
    When parsing a maliciously crafted, excessively long date format string (e= .g., a repeating pattern or very large string), the internal parser splits = the string iteratively using a regular expression loop. This results in unc= ontrolled resource consumption (high CPU utilization and excessive memory a= llocations), leading to a Denial of Service (DoS). This vulnerability is fi= xed in 22.0.1, 21.2.17, and 20.3.25. 2026-06-22 not yet calculated CVE-2026= -54268 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54268 ] anthropics--cl= aude-code Claude Code is an agentic coding tool. From 0.2.54 until 2.1.163,=
    because the hostname huggingface.co was pre-approved as a bare hostname fo=
    r the WebFetch tool, any path on that domain-including attacker-controlled = model repositories-was auto-approved without a permission prompt or being s= ubject to --allowedTools restrictions. An attacker able to inject untrusted=
    content into a Claude Code context could direct it to issue WebFetch reque= sts against attacker-controlled repository files (e.g. /resolve/main/config= .json), which HuggingFace counts as downloads server-side, creating a cover=
    t out-of-band channel for encoding and exfiltrating data Claude can access = such as files, environment variables, or command output. Reliably exploitin=
    g this required the ability to add untrusted content into a Claude Code con= text window. This vulnerability is fixed in 2.1.163. 2026-06-23 not yet cal= culated CVE-2026-54316 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54316 =
    ] Apache Software Foundation--Apache Airflow FTP provider The Apache Airflo=
    w FTP provider's `FTPSHook.get_conn()` created an `ftplib.FTP_TLS` connecti=
    on but never called `prot_p()`, so although the control channel was TLS-pro= tected the data channel was transmitted in cleartext. Any deployment using = `FTPSHook` or `FTPSFileTransmitOperator` to move files over FTPS exposed fi=
    le contents and credentials-in-transit to a network attacker able to observ=
    e the data connection. Upgrade apache-airflow-providers-ftp to `3.15.1` or = later, which issues `PROT P` to encrypt the data channel. 2026-06-26 not ye=
    t calculated CVE-2026-49486 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 9486 ] Apache Software Foundation--Apache Atlas An authenticated user can p= erform XSS. This issue affects Apache Atlas versions 2.4.0 and earlier. Use=
    rs are recommended to upgrade to version 2.5.0, which fixes the issue. 2026= -06-22 not yet calculated CVE-2025-62198 [ https://www.cve.org/CVERecord?id= =3DCVE-2025-62198 ] Apache Software Foundation--Apache Doris MCP Server Apa= che Doris MCP Server contains a SQL injection vulnerability in a metadata q= uery path. A user-controlled database name is directly interpolated into a = SQL query, and the query is executed without passing the caller's authoriza= tion context. This may allow an authenticated attacker, or an anonymous att= acker if authentication is disabled, to bypass SQL security validation and = access metadata outside the intended database scope. Affected users are rec= ommended to upgrade to Doris version 0.6.1 or later, which fixes the issue.=
    2026-06-22 not yet calculated CVE-2025-66336 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2025-66336 ] Apache Software Foundation--Apache IoTDB Improper = Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulne= rability in Apache IoTDB. This issue affects Apache IoTDB: from 2.0.0 befor=
    e 2.0.6, from 1.0.0 before 1.3.6. Users are recommended to upgrade to versi=
    on 1.3.6 and 2.0.6, which fixes the issue. 2026-06-26 not yet calculated CV= E-2025-55017 [ https://www.cve.org/CVERecord?id=3DCVE-2025-55017 ] Apache S= oftware Foundation--Apache IoTDB Improper Limitation of a Pathname to a Res= tricted Directory ('Path Traversal') vulnerability in Apache IoTDB. This is= sue affects Apache IoTDB: from 1.0.0 before 1.3.6, from 2.0.0 before 2.0.7.=
    Users are recommended to upgrade to version 1.3.6 and 2.0.7, which fixes t=
    he issue. 2026-06-26 not yet calculated CVE-2025-64152 [ https://www.cve.or= g/CVERecord?id=3DCVE-2025-64152 ] Apache Software Foundation--Apache Kerby =
    By sending a deeply nested ASN1 structure to a Apache Kerby client or servi= ce, it's possible to trigger a StackOverFlow Exception which can lead to de= nial of service issues. Users are recommended to upgrade to version 2.1.2, = which fixes this issue. 2026-06-26 not yet calculated CVE-2026-57914 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-57914 ] Apache Software Foundation-= -Apache Kerby It is possible to bypass the Kerberos pre-authentication chec=
    k in Apache Kerby by sending a PA-DATA with an unrecognized or unsupported = type. Users are recommended to upgrade to version 2.1.2, which fixes this i= ssue. 2026-06-26 not yet calculated CVE-2026-57915 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-57915 ] Apache Software Foundation--Apache Kvrocks Im= proper Handling of Insufficient Permissions or Privileges vulnerability in = Apache Kvrocks. This issue affects Apache Kvrocks: 2.8.0. Users are recomme= nded to upgrade to version 2.16.0, which fixes the issue. 2026-06-25 not ye=
    t calculated CVE-2026-41566 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 1566 ] Apache Software Foundation--Apache Kvrocks Relative Path Traversal v= ulnerability in Apache Kvrocks. This issue affects Apache Kvrocks: from 1.0=
    .0 through 2.15.0. Users are recommended to upgrade to version 2.16.0, whic=
    h fixes the issue. 2026-06-25 not yet calculated CVE-2026-45188 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-45188 ] Apache Software Foundation--Apac=
    he Kvrocks A vulnerability in Apache Kvrocks. This issue affects Apache Kvr= ocks: from 2.2.0 through 2.15.0. Users are recommended to upgrade to versio=
    n 2.16.0, which fixes the issue. 2026-06-25 not yet calculated CVE-2026-467=
    51 [ https://www.cve.org/CVERecord?id=3DCVE-2026-46751 ] Apache Software Fo= undation--Apache Kvrocks Redis Lua HEAP overflow in cjson library vulnerabi= lity in Apache Kvrocks. This issue affects Apache Kvrocks: from 2.0.4 throu=
    gh 2.15.0. Users are recommended to upgrade to version 2.16.0, which fixes = the issue. 2026-06-25 not yet calculated CVE-2026-46752 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-46752 ] Apache Software Foundation--Apache Kvroc=
    ks A vulnerability in Apache Kvrocks. This issue affects Apache Kvrocks: fr=
    om 2.6.0 through 2.15.0. Users are recommended to upgrade to version 2.16.0=
    , which fixes the issue. 2026-06-25 not yet calculated CVE-2026-54226 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-54226 ] Apache Software Foundation= --Apache NiFi Authorization handling for component configuration verificati=
    on requests in Apache NiFi 1.15.0 through 2.9.0 allows clients with read ac= cess to submit proposed configuration properties. The proposed properties o= verride current configuration, enabling users with read access to invoke pr= edefined verification methods with alternative settings. Apache NiFi instal= lations that do not implement different levels of authorization for viewing=
    and modifying component configuration are not subject to this vulnerabilit=
    y. Upgrading to Apache NiFi 2.10.0 is the recommended mitigation, requiring=
    write access to submit configuration verification requests. 2026-06-22 not=
    yet calculated CVE-2026-44911 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-44911 ] Apache Software Foundation--Apache NiFi Improper escaping of data= base table names in the CaptureChangeMySQL Processor included with Apache N= iFi 1.2.0 through 2.9.0 allows for injecting SQL commands using crafted nam= ing. Manual quoted boundaries added in Apache NiFi 1.8.0 narrowed the scope=
    of potential injection options, but did not cover additional strategies. A= pache NiFi installations that do not use the CaptureChangeMySQL Processor a=
    re not subject to this vulnerability. Upgrading to Apache NiFi 2.10.0 is th=
    e recommended mitigation, which incorporates more robust identifier escapin=
    g. 2026-06-22 not yet calculated CVE-2026-44913 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-44913 ] Apache Software Foundation--Apache NiFi Apache N= iFi 1.12.0 through 2.9.0 are missing authorization when replacing Process G= roups that include extension components with specific Required Permissions = based on the Restricted annotation. The Restricted annotation indicates add= itional privileges required, but framework authorization did not check rest= ricted status when handling requests to replace Process Groups. The missing=
    authorization permits a user with general write access to add components w= ith Restricted status. Apache NiFi installations that do not implement spec= ific authorization for Restricted components are not subject to this vulner= ability because the framework enforces write permissions as the security bo= undary. Upgrading to Apache NiFi 2.9.0 is the recommended mitigation, which=
    removes the implementation of Restricted status authorization from the fra= mework. 2026-06-22 not yet calculated CVE-2026-44914 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-44914 ] Apache Software Foundation--Apache NiFi Apa= che NiFi 0.0.1 through 2.9.0 support building qualified URLs from one of se= veral HTTP request headers that provide an alternative to the standard Host=
    header without validating the values provided. Apache NiFi 1.6.0 introduce=
    d a configurable application property to restrict values provided in the HT=
    TP Host header, but did not apply the validation to alternative Proxy and F= orwarded headers. The absence of proxy host header validation allowed a cli= ent to instruct Apache NiFi web services to construct invalid qualified URL=
    s for redirection or data references. Upgrading to Apache NiFi 2.10.0 is th=
    e recommended mitigation, which implements validation for the X-ProxyHost a=
    nd X-Forwarded-Host HTTP request headers based on the nifi.web.proxy.host p= roperty. Enabling header validation requires configuring the application wi=
    th HTTPS. Reverse proxy servers in front of Apache NiFi are responsible for=
    filtering input request headers and providing allowed values to the applic= ation. 2026-06-22 not yet calculated CVE-2026-54665 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-54665 ] Apache Software Foundation--Apache Shiro Whe=
    n using Apache Shiro with the shiro-guice module in a web servlet context, =
    a specially crafted HTTP request may cause an authentication bypass. This v= ulnerability is similar to https://www.cve.org/CVERecord?id=3DCVE-2020-1957=
    https://www.cve.org/CVERecord , except that it affects the `shiro-guice` m= odule instead of the `shiro-spring` module. This issue affects all Apache S= hiro versions through 2.x, and 3.0.0-alpha-1 only when using `shiro-guice` = module in a web servlet context. Upgrade to version 3.0.0 or later, which f= ixes the issue. 2026-06-25 not yet calculated CVE-2026-56091 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-56091 ] Apache Software Foundation--Apache = Shiro "Remember me" cookie age is not verified on the server. This potentia= lly allows an attacker to intercept a valid cookie and reuse it indefinitel=
    y, even after the configured expiration time has passed. This issue affects=
    all Apache Shiro versions from 1.2.4 through 2.x, and 3.0.0-alpha-1, only = when RememberMe functionality is enabled. Upgrade to version 3.0.0 or later=
    , which fixes the issue. 2026-06-25 not yet calculated CVE-2026-56130 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-56130 ] Apple--Apple M1 GPU Apple =
    M1 GPUs retain register file data between compute shader dispatches from di= fferent processes. A sandboxed Metal attacker app can run a GPU reader shad=
    er that reads stale register values left by a separate sandboxed victim app=
    . In the proof of concept, GPUVictim.app generates a fresh random 128-bit s= ecret using SecRandomCopyBytes and loads it into GPU registers. GPUAttacker= .app, a separate sandboxed app, recovers the exact secret from stale GPU re= gister state. NOTE: The vendor stated that this behavior affects only legac=
    y hardware and has already been addressed at the hardware level in current-= generation Apple Silicon. 2026-06-24 not yet calculated CVE-2026-49269 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-49269 ] Apple--swift-nio-http2 sw= ift-nio-http2's HTTP/2-to-HTTP/1.1 codec did not validate pseudo-header val= ues for control characters before placing them into the translated HTTP/1.1=
    message. swift-nio-http2 1.44.1 adds validation of all pseudo-header value=
    s (:path, :authority, :scheme, :method, and :status) at both the HPACK head=
    er validation layer and the HTTP/2-to-HTTP/1.1 translation layer. Requests =
    or responses containing CR, LF, or NUL bytes in any pseudo-header value are=
    now rejected with a connection error. This issue is fixed in swift-nio-htt=
    p2 1.44.1. 2026-06-25 not yet calculated CVE-2026-28898 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-28898 ] appsmithorg--appsmith Appsmith is a plat= form to build admin panels, internal tools, and dashboards. Prior to 1.99, = the POST /api/v1/admin/send-test-email endpoint accepts attacker-controlled=
    smtpHost and smtpPort values and establishes a raw JavaMail TCP connection=
    without any IP validation. This completely bypasses WebClientUtils.IP_CHEC= K_FILTER, which only applies to Spring WebClient HTTP requests. Additionall=
    y, the raw MailException.getMessage() is returned verbatim in the API error=
    response, enabling error-based internal port scanning and service banner e= numeration. This vulnerability is fixed in 1.99. 2026-06-24 not yet calcula= ted CVE-2026-49979 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49979 ] ap= psmithorg--appsmith Appsmith is a platform to build admin panels, internal = tools, and dashboards. Prior to 2.1, Appsmith's bundled supervisord exposes=
    an XML-RPC interface on port 9001, reachable from outside the container vi=
    a a Caddy reverse-proxy route at /supervisor/* on the public ingress. Combi= ned with the APPSMITH_SUPERVISOR_PASSWORD exposed via GET /api/v1/admin/env=
    , any authenticated administrator can send arbitrary XML-RPC calls to super= visord and execute OS commands inside the Docker container via twiddler.add= ProgramToGroup. This vulnerability is fixed in 2.1. 2026-06-24 not yet calc= ulated CVE-2026-50189 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50189 ]=
    appsmithorg--appsmith Appsmith is a platform to build admin panels, intern=
    al tools, and dashboards. Prior to 2.1, the outbound HTTP host filter appli=
    ed by WebClientUtils (used by the REST API and GraphQL datasource plugins) = validates hosts against an exact-match string denylist. The comprehensive a= ddress-class check (loopback, any-local, link-local, fc00::/7) exists only =
    on a separate code path used by SMTP, not by the HTTP plugin path. As a res= ult, an authenticated user can craft outbound requests that reach loopback-= bound services inside the container. This vulnerability is fixed in 2.1. 20= 26-06-24 not yet calculated CVE-2026-55455 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-55455 ] aquasecurity--trivy Trivy is a security scanner. Prio=
    r to 0.71.0, when Trivy scans a Helm chart archive (.tgz), its custom tar u= npacker reads each entry with io.ReadAll(tr) and no size limit. An attacker=
    who can place a malicious .tgz file in the scanned path can craft a small = compressed archive that decompresses to gigabytes, causing the Trivy proces=
    s to be killed by the OS OOM killer. This vulnerability is fixed in 0.71.0.=
    2026-06-25 not yet calculated CVE-2026-54448 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-54448 ] aquasecurity--trivy Trivy is a security scanner. P= rior to 0.71.1, when Trivy downloads an OCI artifact, it uses the org.openc= ontainers.image.title annotation from the artifact manifest as the destinat= ion filename without validation. An attacker who can make Trivy fetch an at= tacker-controlled artifact can supply a crafted annotation that resolves to=
    a path outside the intended destination, causing Trivy to write the layer = content to an arbitrary location on the host filesystem. This vulnerability=
    is fixed in 0.71.1. 2026-06-25 not yet calculated CVE-2026-55092 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-55092 ] Aruba--ArubaSign Incorrect def= ault permissions in ArubaSign, affecting versions prior to v4.6.6. The vuln= erability is caused by the assignment of inappropriate permissions during t=
    he software's default installation, whereby the main executable and other p= rogramme files located in C:\Program Files have excessive permissions for t=
    he 'Everyone' group. This could allow an unprivileged user to replace the m= ain executable and/or its components with a malicious file, thereby enablin=
    g the execution of arbitrary code. In the worst-case scenario, if the malic= ious code is executed with elevated privileges (such as those of Administra= tor or SYSTEM), the attacker could escalate privileges and gain full contro=
    l of the system, compromising both security and data integrity. 2026-06-22 = not yet calculated CVE-2026-12602 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-12602 ] ash-project--ash Improperly Controlled Modification of Dynamic= ally-Determined Object Attributes vulnerability in ash-project ash allows a=
    user to set the value of a private action argument that is intended to be = controlled only by trusted server-side code. Action arguments declared with=
    public?: false are meant to be set internally (for example via Ash.Changes= et.set_private_argument/3) and must not be settable from end-user input. Wh=
    en a changeset is built from a parameter map, Ash filters out private argum= ents, but the filtering is incomplete. In the regular changeset path (for_c= reate, for_update, for_destroy), private arguments are stripped only when t=
    he parameter key is an atom. When the key is a binary (string), as is the c= ase for user-supplied parameters, the private argument is kept and the user=
    controls its value. In the atomic path (Ash.Changeset.fully_atomic_changes= et/4, also reached through atomic and bulk updates), private arguments are = not stripped at all, regardless of whether the key is an atom or a binary. =
    An attacker who can submit parameters to an action that defines a private a= rgument can therefore inject a value for that argument. Depending on how th=
    e application uses the argument (for example an acting_user_id driving auth= orization or record ownership), this can lead to an integrity violation or = privilege escalation. This issue affects ash: from 3.0.0 before 3.29.3. 202= 6-06-23 not yet calculated CVE-2026-55736 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-55736 ] ASUS--Armoury Crate A permissive list of allowed input=
    s in ASUS Armoury Crate allows a local administrator to perform arbitrary m= emory read/write operations or cause a system crash (BSOD) by bypassing the=
    validation mechanism.Refer to the ' Security Update for Armoury Crate App= =C2=A0' section on the ASUS Security Advisory for more information. 2026-06= -22 not yet calculated CVE-2026-8918 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-8918 ] ATEN--Unizon ATEN Unizon updateLicense Directory Traversal A= rbitrary File Deletion Vulnerability. This vulnerability allows remote atta= ckers to delete arbitrary files on affected installations of ATEN Unizon. A= uthentication is required to exploit this vulnerability. The specific flaw = exists within the updateLicense method. The issue results from the lack of = proper validation of a user-supplied path prior to using it in file operati= ons. An attacker can leverage this vulnerability to delete files or create =
    a denial-of-service condition on the system. Was ZDI-CAN-28502. 2026-06-24 = not yet calculated CVE-2026-9774 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-9774 ] ATEN--Unizon ATEN Unizon uploadSSL Directory Traversal Arbitrary=
    File Deletion Vulnerability. This vulnerability allows remote attackers to=
    delete arbitrary files on affected installations of ATEN Unizon. Authentic= ation is required to exploit this vulnerability. The specific flaw exists w= ithin the uploadSSL method. The issue results from the lack of proper valid= ation of a user-supplied path prior to using it in file operations. An atta= cker can leverage this vulnerability to delete files or create a denial-of-= service condition on the system. Was ZDI-CAN-28503. 2026-06-24 not yet calc= ulated CVE-2026-9775 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9775 ] A= TEN--Unizon ATEN Unizon writeFileToHttpServletResponse Directory Traversal = Information Disclosure Vulnerability. This vulnerability allows remote atta= ckers to disclose sensitive information on affected installations of ATEN U= nizon. Authentication is not required to exploit this vulnerability. The sp= ecific flaw exists within the writeFileToHttpServletResponse method. The is= sue results from the lack of proper validation of a user-supplied path prio=
    r to using it in file operations. An attacker can leverage this vulnerabili=
    ty to disclose information in the context of SYSTEM. Was ZDI-CAN-28505. 202= 6-06-24 not yet calculated CVE-2026-9776 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-9776 ] ATEN--Unizon ATEN Unizon restoreDB Directory Traversal R= emote Code Execution Vulnerability. This vulnerability allows remote attack= ers to execute arbitrary code on affected installations of ATEN Unizon. Aut= hentication is required to exploit this vulnerability. The specific flaw ex= ists within the restoreDB method. The issue results from the lack of proper=
    validation of a user-supplied path prior to using it in file operations. A=
    n attacker can leverage this vulnerability to execute code in the context o=
    f SYSTEM. Was ZDI-CAN-28578. 2026-06-24 not yet calculated CVE-2026-9777 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-9777 ] ATEN--Unizon ATEN Unizon=
    ImportDeviceList Directory Traversal Remote Code Execution Vulnerability. = This vulnerability allows remote attackers to execute arbitrary code on aff= ected installations of ATEN Unizon. Authentication is required to exploit t= his vulnerability. The specific flaw exists within the ImportDeviceList met= hod. The issue results from the lack of proper validation of a user-supplie=
    d path prior to using it in file operations. An attacker can leverage this = vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-28579. = 2026-06-24 not yet calculated CVE-2026-9778 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-9778 ] ATEN--Unizon ATEN Unizon doCryptoHugeFileToFile Impro= per Verification of Cryptographic Signature Remote Code Execution Vulnerabi= lity. This vulnerability allows remote attackers to execute arbitrary code =
    on affected installations of ATEN Unizon. Authentication is required to exp= loit this vulnerability. The specific flaw exists within the updateWar meth= od. The issue results from an incorrect implementation of cryptographic sig= nature verification. An attacker can leverage this vulnerability to execute=
    code in the context of SYSTEM. Was ZDI-CAN-28590. 2026-06-24 not yet calcu= lated CVE-2026-9779 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9779 ] ax= iomatic-systems Bento4 --axiomatic-systems Bento4=C2=A0 A stack overflow in=
    the AP4_StsdAtom::AP4_StsdAtom component of axiomatic-systems Bento4 befor=
    e v1.8.9allows attackers to cause a Denial of Service (DoS) via a crafted M=
    P4 file. 2026-06-26 not yet calculated CVE-2026-36907 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-36907 ] axiomatic-systems Bento4 --axiomatic-syste=
    ms Bento4=C2=A0 A stack overflow in the AP4_Array<AP4_TrunAtom::Entry>::Ens= ureCapacity component of axiomatic-systems Bento4 before v1.8.9allows attac= kers to cause a Denial of Service (DoS) via a crafted MP4 file. 2026-06-26 = not yet calculated CVE-2026-36908 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-36908 ] AzeoTech--DAQFactory In AzeoTech DAQFactory versions 21.1 and = prior, a Use After Free vulnerability can be exploited by an attacker using=
    specially crafted .ctl files which can result in code execution. 2026-06-2=
    5 not yet calculated CVE-2026-12921 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-12921 ] BerriAI--litellm LiteLLM is a proxy server (AI Gateway) to c= all LLM APIs in OpenAI (or native) format. Prior to 1.84.0, This vulnerabil= ity is fixed in 1.84.0. 2026-06-22 not yet calculated CVE-2026-49468 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-49468 ] Budibase--budibase Budibase=
    is an open-source low-code platform. Prior to 3.39.0, an anonymous attacke=
    r who knows or can enumerate a workspace id (app_...) and an S3-source data= source id (ds_...) can call this endpoint with no auth and obtain a 15-minu=
    te pre-signed PUT URL minted on the victim's IAM identity. The endpoint als=
    o returns the publicUrl so the attacker knows exactly where their PUT lands=
    . Because bucket is attacker-controlled, the attacker can write to any buck=
    et those IAM credentials can write to, not only the bucket the datasource w=
    as configured for. The Budibase server route POST /api/attachments/:datasou= rceId/url (packages/server/src/api/routes/static.ts) is registered with onl=
    y the recaptcha middleware. There is no authorized(...) middleware in the c= hain. The controller (packages/server/src/api/controllers/static/index.ts::= getSignedUploadURL) looks the requested datasource up, instantiates an AWS =
    S3 client with the datasource's stored accessKeyId / secretAccessKey, and r= eturns an AWS Signature V4 pre-signed PutObjectCommand URL for the caller-s= upplied bucket and key. The bucket is not pinned to the datasource's config= ured bucket. The workspace context required by sdk.datasources.get is sourc=
    ed by getWorkspaceIdFromCtx (packages/backend-core/src/utils/utils.ts) from=
    any of: the x-budibase-app-id header, the JSON body appId, a path segment = that begins with the workspace prefix, or ?appId=3D. auth.buildAuthMiddlewa= re([], { publicAllowed: true }) runs before any of this and explicitly allo=
    ws anonymous requests. The currentWorkspace middleware's "deny access to de=
    v preview" branch only triggers under isBrowser(ctx) && !isApiKey(ctx); isB= rowser checks the parsed User-Agent for a recognised browser, so any non-br= owser client (curl, the supplied PoC, any tool not setting a browser UA) is=
    neither and reaches dev workspaces too. This vulnerability is fixed in 3.3= 9.0. 2026-06-26 not yet calculated CVE-2026-50137 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-50137 ] Cacti--cacti Cacti is an open source performan=
    ce and fault management framework. Versions 1.2.30 and below contain a Refl= ected XSS vulnerability in the html_auth_footer. This issue has been fixed =
    in version 1.2.31. 2026-06-24 not yet calculated CVE-2026-39897 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-39897 ] Cacti--cacti Cacti is an open so= urce performance and fault management framework. Versions 1.2.30 and prior = are vulnerable to Path Traversal via filename parameter in package_import.p= hp. This issue has been fixed in version 1.2.31. 2026-06-24 not yet calcula= ted CVE-2026-39899 [ https://www.cve.org/CVERecord?id=3DCVE-2026-39899 ] Ca= cti--cacti Cacti is an open source performance and fault management framewo= rk. Versions 1.2.30 and prior are vulnerable to Reflected XSS via tab param= eter in the auth_profile.php JavaScript context. This issue has been fixed =
    in version 1.2.31. 2026-06-24 not yet calculated CVE-2026-39900 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-39900 ] Cacti--cacti Cacti is an open so= urce performance and fault management framework. In versions 1.2.30 and pri= or, the rfilter request parameter is retrieved via the raw accessor grv() (= rather than gfrv() with FILTER_VALIDATE_IS_REGEX validation) and concatenat=
    ed directly into RLIKE SQL clauses in lib/html_graph.php and lib/html_tree.= php, which are reachable pre-authentication through graph_view.php on insta= llations with guest graph viewing enabled. Because the unbalanced-quote pay= load bypasses the regex validation that would otherwise reject it, an unaut= henticated attacker can inject arbitrary SQL to compromise the confidential= ity, integrity, and availability of the database. This advisory is similar =
    to GHSA-69gg-mjfm-jjpc. This issue has been fixed in version 1.2.31. 2026-0= 6-24 not yet calculated CVE-2026-39948 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-39948 ] Cacti--cacti Cacti is an open source performance and fa= ult management framework. Versions 1.2.30 and prior are vulnerable to Comma=
    nd Injection due to lack of sanitization in the escape_command() function. = The escape_command() function at lib/rrd.php is a no-op: it returns $comman=
    d unchanged. The command line built by rrdtool_function_graph() is passed t= hrough this function and then to shell_exec($full_commandline). The risk is=
    in __rrd_execute() where text_format values from graph templates (which ma=
    y contain host variable substitutions) reach shell_exec without adequate es= caping. This issue has been addressed in version 1.2.31. 2026-06-24 not yet=
    calculated CVE-2026-40079 [ https://www.cve.org/CVERecord?id=3DCVE-2026-40= 079 ] Cacti--cacti Cacti is an open source performance and fault management=
    framework. Versions 1.2.30 and prior have a package import signature valid= ation bypass allows which allows self-signed packages. This issue has been = fixed in version 1.2.31. 2026-06-25 not yet calculated CVE-2026-40941 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-40941 ] Caliptra--Core Runtime Fir= mware Incorrect check of function return value in Caliptra Core Runtime Fir= mware (ActivateFirmwareCmd::activate_fw modules) allows bypass of Caliptra = Core's verification of the MCU FW during a hitless update. This issue affec=
    ts Core Runtime Firmware: from 2.0.0 through 2.0.1, 2.1.0. 2026-06-23 not y=
    et calculated CVE-2026-5818 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 818 ] Caliptra--Core Runtime Firmware Missing cryptographic step in Caliptr=
    a Core Firmware (aes_256_gcm_update module) results in an incorrect GCM aut= hentication tag. When the streaming AES-256-GCM API is used with empty AAD,=
    the hardware GHASH accumulator state is not saved after the first update c= all, causing the final tag to exclude the first batch of processed cipherte= xt. Ciphertext produced by that call may be modified without the tag reflec= ting the change. This issue affects Core Runtime Firmware: from 2.0.0 throu=
    gh 2.0.1, 2.1.0. 2026-06-23 not yet calculated CVE-2026-6458 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-6458 ] Cboard--Cboard v0.4.2 SQL Injection = vulnerability in Cboard v.0.4.2 and before allows a remote attacker to exec= ute arbitrary code via the getDimensionsValues component 2026-06-23 not yet=
    calculated CVE-2026-52673 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52= 673 ] chimurai--http-proxy-middleware http-proxy-middleware is node.js http= -proxy middleware. From 0.16.0 until 2.0.10, 3.0.6, and 4.1.0, http-proxy-m= iddleware documents router proxy-table entries as host, path, or host+path = selectors, but the host+path implementation uses unanchored substring match= ing on attacker-controlled request metadata. As a result, a crafted Host he= ader that is only a superstring match for a configured host+path key can st= ill route a request to an unintended backend. This vulnerability is fixed i=
    n 2.0.10, 3.0.6, and 4.1.0. 2026-06-22 not yet calculated CVE-2026-55602 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-55602 ] cursor--cursor Cursor i=
    s a code editor built for programming with AI. Prior to 3.0, Cursor runs ag= ent terminal commands in a sandbox by default, and the sandbox grants write=
    access to the command's working directory. A flaw was identified in how th=
    e agent could modify the working_directory parameter, which could cause the=
    sandbox to include writable paths outside the intended workspace. A malici= ous agent could set working_directory to a sensitive location and write arb= itrary files outside the workspace under the user's privileges. This enable=
    s non-sandboxed Remote Code Execution - for example by overwriting the curs= orsandbox helper so later commands run unsandboxed - with no user interacti=
    on beyond a benign prompt. This vulnerability is fixed in 3.0. 2026-06-25 n=
    ot yet calculated CVE-2026-50548 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-50548 ] cursor--cursor Cursor is a code editor built for programming wi=
    th AI. Prior to 3.0, Cursor runs agent terminal commands in a sandbox by de= fault. Before a Write, the agent canonicalizes the target path to confirm i=
    t stays inside the workspace, but when canonicalization fails it falls back=
    to the original path and writes without approval. A malicious agent can cr= eate an in-workspace symlink that points outside the workspace and force ca= nonicalization to fail - either because the target does not exist or becaus=
    e read permission is removed from the path - so the agent writes through th=
    e symlink to an arbitrary location without approval. A malicious agent coul=
    d write arbitrary files outside the workspace under the user's privileges. = This enables non-sandboxed Remote Code Execution - for example by overwriti=
    ng the cursorsandbox helper so later commands run unsandboxed - with no use=
    r interaction beyond a benign prompt. This vulnerability is fixed in 3.0. 2= 026-06-25 not yet calculated CVE-2026-50549 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-50549 ] danpros--HTMLy HTMLy 3.1.1 contains a Server-Side Re= quest Forgery (SSRF) vulnerability in the RSS feed import functionality. Th=
    e function get_feed() in system/admin/admin.php passes user-supplied $feed_= url directly to file_get_contents() without any validation. An authenticate=
    d attacker with administrative privileges can exploit this by entering a cr= afted URL (e.g., http://dnslog.example.com, file:///etc/passwd, or http://1= 69.254.169.254 in cloud contexts) via Tools -> Import RSS. The server will = then make a request to the attacker-controlled target. 2026-06-26 not yet c= alculated CVE-2026-57940 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5794=
    0 ] DAVIDO--Bytes::Random::Secure Bytes::Random::Secure versions through 0.=
    29 for Perl share internal state across forked processes. When an object is=
    initialised before forking, or when the functional interface is used, then=
    the internal state for the PRNG is shared across processes and identical r= andom streams will be produced. Secrets generated in multiprocess applicati= ons are predictable across processes. 2026-06-26 not yet calculated CVE-202= 6-11625 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11625 ] DAVIDO--Bytes= ::Random::Secure::Tiny Bytes::Random::Secure::Tiny versions through 1.011 f=
    or Perl share internal state across forked processes. When an object is ini= tialised before forking, then the internal state for the PRNG is shared acr= oss processes and identical random streams will be produced. Secrets genera= ted in multiprocess applications are predictable across processes. 2026-06-=
    26 not yet calculated CVE-2026-11702 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-11702 ] Devolutions--Remote Desktop Manager Incorrect link resoluti=
    on by display name in the custom PowerShell VPN editor in Devolutions Remot=
    e Desktop Manager 2026.2.5 through 2026.2.11 allows an authenticated attack=
    er with write access to a shared workspace to execute a PowerShell script i=
    n another user's context via a display name collision with an existing VPN = script link. 2026-06-26 not yet calculated CVE-2026-13372 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-13372 ] Devolutions--Server Improper input val= idation in the PAM AD discovery endpoints in Devolutions Server 2026.2.4.0 = through 2026.2.7.0 allows an authenticated user with the UserGroupsView per= mission to coerce server-side authentication to an attacker-controlled host=
    , exposing PAM provider credentials as a NTLMv2 challenge-response, via a c= rafted DomainName parameter. 2026-06-25 not yet calculated CVE-2026-12755 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-12755 ] dragonflydb--dragonfly=
    Dragonfly is an in-memory data store built for modern application workload=
    s. Prior to 1.39.9, Dragonfly has a RESP Protocol Injection via Lua redis.e= rror_reply() in EvalSerializer. An authenticated user can inject arbitrary = RESP messages into the connection's response stream, potentially causing re= sponse desynchronization in connection-pool clients. This vulnerability is = fixed in 1.39.9. 2026-06-26 not yet calculated CVE-2026-47206 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-47206 ] DRIMO--DRIMO CMS DRIMO CMS is vuln= erable to Reflected XSS via q parameter in searching functionality. An atta= cker can prepare an URL that, when opened, results in arbitrary JavaScript = execution in the victim's browser. Product is in End Of Life phase and will=
    not receive any updates. However, deleting=C2=A0info.php file mitigates th=
    e vulnerability, 2026-06-23 not yet calculated CVE-2026-11772 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-11772 ] DROLSKY--List::SomeUtils::XS List:= :SomeUtils::XS versions before 0.59 for Perl have a heap buffer overflow in=
    the pairwise function. pairwise() collects the values returned by the bloc=
    k into a heap buffer sized to the longer input array, then grows the buffer=
    before each copy with a single quadrupling (alloc <<=3D 2) instead of a lo= op. A block call that returns more than four times the current allocation i=
    n one invocation outgrows that one quadrupling, and the copy writes past th=
    e end of the buffer. Any caller of pairwise() whose block returns, for a si= ngle pair, more than four times the longer input array's length writes past=
    the buffer and corrupts the heap. 2026-06-25 not yet calculated CVE-2026-1= 2844 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12844 ] Edgewall *Genshi= *--Genshi Server side template inject (SSTI) in the expression evaluation c= omponent in Genshi Template Engine version 0.7.9 allows a remote attacker t=
    o achieve remote code execution (RCE) via crafted template expressions. 202= 6-06-26 not yet calculated CVE-2026-0685 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-0685 ] electron--electron Electron is a framework for writing c= ross-platform desktop applications using JavaScript, HTML and CSS. From 42.= 3.1 until 42.3.3, Buffer performs incorrect byte length calculations result= ing in heap buffer under/overflow. Most apps will crash and some may perfor=
    m incorrect buffer allocations in the Node.js Buffer API resulting in unexp= ected truncation or allocation. This vulnerability is fixed in 42.3.3. 2026= -06-23 not yet calculated CVE-2026-54257 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54257 ] elixir-plug--plug Inefficient algorithmic complexity in=
    Plug's nested-parameter decoder allows an unauthenticated remote attacker =
    to cause denial of service. Plug.Conn.Query.decode/4 (and Plug.Conn.Query.d= ecode_each/2) parse query strings and application/x-www-form-urlencoded req= uest bodies. When a key contains many bracketed segments such as a[a][a][a]= =3D1, the decoder walks the brackets and, for each of the N levels, perform=
    s a map operation keyed on an ever-growing binary prefix of the key, hashin=
    g the full byte range at each step. The total decode cost is therefore quad= ratic in the number of nesting levels. With the default Plug.Parsers.URLENC= ODED body limit of 1,000,000 bytes, a single request can carry roughly 333,= 000 nesting levels and saturate a BEAM scheduler for minutes. A small numbe=
    r of concurrent requests can saturate all schedulers and render a Plug-base=
    d server unresponsive. No authentication or knowledge of application routes=
    is required. This vulnerability is associated with program files lib/plug/= conn/query.ex and program routines Plug.Conn.Query.decode/4, Plug.Conn.Quer= y.decode_each/2, Plug.Conn.Query.split_keys/6, Plug.Conn.Query.insert_keys/=
    3, and Plug.Conn.Query.finalize_pointer/2. This issue affects plug from 1.1= 5.0 before 1.15.5, 1.16.4, 1.17.2, 1.18.3, and 1.19.3. 2026-06-23 not yet c= alculated CVE-2026-54892 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5489=
    2 ] FasterXML--jackson-databind jackson-databind contains the general-purpo=
    se data-binding functionality and tree-model for Jackson Data Processor. Fr=
    om 2.13.0 until 2.14.0, a potential Denial-of-Service exists when attacker = sends deeply nested JSON if (and only if) the service reads deeply nested (= 1000s of levels) JSON as JsonNode (ObjectMapper.readTree()) and writes out = same (or modifided) node using JsonNode.toString(). This can consume signif= icant amount of resources with concurrent relatively small requests (1000 n= ested arrays is 2kB). This vulnerability is fixed in 2.14.0. 2026-06-23 not=
    yet calculated CVE-2026-50193 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-50193 ] FastStone--FastStone Image Viewer v8.3 A heap overflow in the FSV= iewer.exe process of FastStone Image Viewer v8.3 allows attackers to cause =
    a execute arbitrary code in the context of the current process via supplyin=
    g a crafted JPEG 2000 (JP2) file. 2026-06-26 not yet calculated CVE-2026-30= 040 [ https://www.cve.org/CVERecord?id=3DCVE-2026-30040 ] FastStone--FastSt= one Image Viewer v8.3 An integer overflow in the PSD parser compnent of Fas= tStone Image Viewer v8.3 allows attackers to execute arbitrary code or caus=
    e a Denial of Service (DoS) via supplying a crafted PSD file. 2026-06-26 no=
    t yet calculated CVE-2026-30041 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-30041 ] filebrowser--filebrowser File Browser is a file managing interfa=
    ce for uploading, deleting, previewing, renaming, and editing files within =
    a specified directory. Prior to 2.63.6, the Hook Authentication feature in = File Browser allows administrators to delegate login verification to an ext= ernal shell command. User-supplied credentials (username and password) are = interpolated into this command string using os.Expand without sanitization.=
    An unauthenticated remote attacker can inject shell metacharacters in the = username or password field at the login screen, causing the server to execu=
    te arbitrary OS commands before any authentication takes place. This is a c= ritical pre-authentication RCE. This vulnerability is fixed in 2.63.6. 2026= -06-25 not yet calculated CVE-2026-54088 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54088 ] filebrowser--filebrowser File Browser is a file managin=
    g interface for uploading, deleting, previewing, renaming, and editing file=
    s within a specified directory. Prior to 2.33.8, when a shell interpreter i=
    s configured (e.g. /bin/sh -c), the command allowlist can be bypassed throu=
    gh shell metacharacters. The allowlist validates only the first token of us=
    er input, but the entire raw string is handed to the shell - semicolons, pi= pes, backticks, and $() all work to chain arbitrary commands after a permit= ted one. This vulnerability is fixed in 2.33.8. 2026-06-25 not yet calculat=
    ed CVE-2026-54090 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54090 ] fil= ebrowser--filebrowser File Browser is a file managing interface for uploadi= ng, deleting, previewing, renaming, and editing files within a specified di= rectory. Prior to 2.63.6, filebrowser builds the download-as-zip / download= -as-tar archive entry names with filepath.ToSlash, which on a Linux host is=
    a no-op for backslashes (\ is only a path separator on Windows). A file wh= ose name contains Windows-style traversal is accepted by the resource handl= ers, stored on the Linux filesystem with a literal backslash name, and then=
    emitted verbatim as the archive entry name. Windows extractors interpret \=
    as a path separator and write the extracted file outside the extraction di= rectory - arbitrary file write on the victim who downloads and extracts the=
    archive. This vulnerability is fixed in 2.63.6. 2026-06-25 not yet calcula= ted CVE-2026-54093 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54093 ] fi= lebrowser--filebrowser File Browser is a file managing interface for upload= ing, deleting, previewing, renaming, and editing files within a specified d= irectory. Prior to 2.63.6, a low-privileged authenticated user of filebrows=
    er (with create + delete permissions in their own isolated scope) can silen= tly destroy share-link records belonging to any other user - including the = administrator - by performing a legitimate DELETE on a file in their own di= rectory whose logical path happens to be a byte-prefix of another user's st= ored share.Link.Path. The file contents of the victim are not exposed, but = the victim's share links are irrevocably wiped. This vulnerability is fixed=
    in 2.63.6. 2026-06-25 not yet calculated CVE-2026-54097 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-54097 ] Flowise--Flowise Flowise through 2.2.4 = contains an unauthenticated arbitrary file upload vulnerability in the /api= /v1/attachments endpoint when storageType is set to local. Attackers can ex= ploit path traversal in the chatId and chatflowId parameters to upload mali= cious files to arbitrary directories, potentially enabling remote code exec= ution and server compromise. 2026-06-25 not yet calculated CVE-2025-71333 [=
    https://www.cve.org/CVERecord?id=3DCVE-2025-71333 ] Flowise--Flowise Flowi=
    se before 3.1.0 contains a server-side request forgery vulnerability in the=
    Execute Flow node that allows attackers to bypass security validation by p= roviding intranet addresses through the base URL field. Attackers can initi= ate HTTP requests to internal network addresses, access cloud metadata, and=
    enumerate internal services by exploiting the missing secureFetch verifica= tion in httpSecurity.ts. 2026-06-23 not yet calculated CVE-2026-56275 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-56275 ] FOSSBilling--FOSSBilling F= OSSBilling is a billing and client management system that automates invoici= ng, payments, and communication for online service businesses. Versions 0.6= .21 through 0.7.2 are vulnerable to IDOR through the support ticket creatio=
    n workflow. By manipulating rel_id when rel_type=3Dorder, an authenticated = client can create a support ticket that references another client's order t= hey do not own. The ticketCreateForClient() method accepted rel_id without = verifying order ownership for non-upgrade tasks, allowing clients to link a=
    new ticket to another client's order by crafting the request. No cron task=
    automatically processes cancel/upgrade requests from ticket relations; sta=
    ff action is required. This affects integrity and confidentiality: staff co= uld be misled into acting on the wrong order (e.g., cancellation or upgrade=
    requests). While there is no client-to-client order data exposure, order I=
    Ds may appear in ticket context. This issue has been fixed in version 0.8.0=
    . 2026-06-23 not yet calculated CVE-2025-64105 [ https://www.cve.org/CVERec= ord?id=3DCVE-2025-64105 ] FOSSBilling--FOSSBilling FOSSBilling is a free, o= pen-source billing and client management system. In versions 0.7.2 and prio=
    r, a query-construction flaw in client list endpoints allowed authenticated=
    clients to bypass tenant scoping and retrieve other clients' data. Details=
    In ServiceTransaction::getSearchQuery() and Order\Service::getSearchQuery(=
    ), OR-based search/action filters were appended without grouping, allowing = SQL operator precedence to evaluate OR clauses independently of the enforce=
    d client_id constraint. Crafted requests could therefore return records and=
    metadata belonging to other clients, including identifiers, amounts, statu=
    s, timestamps, and related fields. This issue was fixed in version 0.8.0. 2= 026-06-23 not yet calculated CVE-2026-23513 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-23513 ] FOSSBilling--FOSSBilling FOSSBilling is a free, open= -source billing and client management system. Starting in version 0.5.4 and=
    prior to version 0.8.0, an authorization bypass in the API role handling a= llows unauthenticated access to privileged `/api/system/*` endpoints. Becau=
    se `system` resolves to the cron admin identity, attackers can invoke admin=
    API methods without valid credentials, session, or CSRF token. Version 0.8=
    .0 patches the issue. Some workarounds are available. Block external access=
    to `/api/system/*` at reverse proxy/WAF, restrict API access by trusted so= urce IPs only (`api.allowed_ips`), rotate all admin/client API tokens immed= iately, invalidate active sessions and reset high-privilege credentials, an= d/or review API request logs for suspicious `/api/system/` access and treat=
    as potential incident. 2026-06-23 not yet calculated CVE-2026-27604 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-27604 ] FOSSBilling--FOSSBilling FO= SSBilling is a free, open-source billing and client management system. In v= ersions 0.7.2 and prior, the Servicecustom Client API's __call method accep=
    ts an order_id parameter and fetches the associated order without verifying=
    the authenticated client owns it, potentially exposing cross-client data t= hrough IDOR. An authenticated client can access any other client's custom s= ervice by guessing sequential order IDs. This can lead to a confidentiality=
    breach - attackers can read client PII (name, email, phone, address, compa=
    ny details, VAT number) and service configuration data belonging to other c= lients. This issue has been fixed in version 0.8.0. 2026-06-24 not yet calc= ulated CVE-2026-27708 [ https://www.cve.org/CVERecord?id=3DCVE-2026-27708 ]=
    FOSSBilling--FOSSBilling FOSSBilling is a free, open-source billing and cl= ient management system. Versions prior to 0.8.0 have a Server-Side Template=
    Injection (SSTI) vulnerability in the template rendering system. Administr= ators with access to features that render Twig templates (email templates, = mass mail campaigns, custom payment adapters, and the `string_render` API e= ndpoint) can inject arbitrary Twig expressions, leading to information disc= losure and remote code execution. The vulnerability exists because Twig tem= plates are rendered without a sandbox, allowing access to the full Twig env= ironment, API context, and the application's dependency injection container=
    . Version 0.8.0 patches the issue. Some workarounds are available. Audit ex= isting email templates for suspicious Twig expressions, rotate all admin an=
    d client API tokens, and/or block external access to /api/system/* at rever=
    se proxy/WAF to mitigate chaining with GHSA-78x5-c8gw-8279. 2026-06-23 not = yet calculated CVE-2026-28496 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -28496 ] FOSSBilling--FOSSBilling FOSSBilling is a free, open-source billin=
    g and client management system. Versions 0.7.2 and prior expose a guest API=
    endpoint, /api/guest/staff/create, intended for initial administrator boot= strap. Due to a flawed admin-existence check, the endpoint remains usable a= fter an administrator already exists. The flawed guard check uses is_counta= ble() on a value that returns a Model_Admin object or null rather than a co= untable type, causing the expression to always evaluate as true and bypass = the intended protection. As a result, an attacker can reach the unprotected=
    endpoint to create a new administrator account and immediately authenticat=
    e, gaining a fully privileged admin session even when an admin already exis= ts. This issue has been fixed in version 0.8.0. 2026-06-24 not yet calculat=
    ed CVE-2026-33543 [ https://www.cve.org/CVERecord?id=3DCVE-2026-33543 ] FOS= SBilling--FOSSBilling FOSSBilling is a free, open-source billing and client=
    management system. In versions 0.5.4 through 0.7.2, the /run-patcher maint= enance endpoint in FOSSBilling was accessible without authentication, which=
    allowed unauthenticated remote users to trigger update patch routines that=
    modify configuration files, execute database schema changes, perform files= ystem mutations, and clear caches. The /run-patcher endpoint executes privi= leged maintenance operations - configuration migrations, database patch exe= cution (including ALTER TABLE, DROP TABLE, UPDATE statements), filesystem d= eletions and renames, and cache clearing - without requiring administrator = authentication, CSRF validation, or CLI context. An unauthenticated remote = attacker can trigger these operations by sending a simple HTTP GET request =
    to /run-patcher, which can be abused for denial-of-service attacks. Certain=
    patches (e.g., batch token regeneration for all admin and client accounts =
    in patch 53, and session invalidation) are disruptive even when re-executed=
    against an already-patched instance. Repeated or concurrent requests may a= lso cause inconsistent database state. This issue has been fixed in version=
    0.8.0. 2026-06-25 not yet calculated CVE-2026-43920 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-43920 ] Frappe--Frappe Framework A Stored Cross-Sit=
    e Scripting (XSS) vulnerability exists in Frappe Framework version 17.0.0-d=
    ev due to improper neutralization of user-controlled input before generatin=
    g HTML output in the Audit Trail component. 2026-06-24 not yet calculated C= VE-2026-50698 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50698 ] Frappe-= -Frappe Framework A Stored Cross-Site Scripting (XSS) vulnerability exists =
    in Frappe Framework version 17.0.0-dev. An authenticated attacker with writ=
    e access to Auto Repeat can persist HTML/JavaScript in reference_document u= sing a whitelisted write path and trigger script execution when users open = the affected Auto Repeat form. 2026-06-24 not yet calculated CVE-2026-50699=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-50699 ] Frappe--Frappe Frame= work A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fra= mework version 17.0.0-dev due to improper neutralization of user-controlled=
    input in the frappe.get_avatar function. 2026-06-24 not yet calculated CVE= -2026-50700 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50700 ] Frappe--F= rappe Framework A Reflected Cross-Site Scripting (XSS) vulnerability exists=
    in Frappe Framework version 17.0.0-dev due to improper neutralization of u= ser-controlled input in the dashboard-view component. 2026-06-24 not yet ca= lculated CVE-2026-50701 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50701=
    ] Frappe--Frappe Framework A Stored Cross-Site Scripting (XSS) vulnerabili=
    ty exists in Frappe Framework version 17.0.0-dev due to improper neutraliza= tion of user-controlled input in the Desk desktop icon renderer. 2026-06-24=
    not yet calculated CVE-2026-50703 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-50703 ] Frappe--Frappe Framework A Stored Cross-Site Scripting (XSS) = vulnerability exists in Frappe Framework version 17.0.0-dev due to improper=
    neutralization of user-controlled input in the File View breadcrumb render= er. 2026-06-24 not yet calculated CVE-2026-50704 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-50704 ] Frappe--Frappe Framework A Cross-Site Scripting=
    (XSS) vulnerability exists in Frappe Framework version 17.0.0-dev due to i= mproper neutralization of untrusted input in the Form Dashboard headline re= nderer. 2026-06-24 not yet calculated CVE-2026-50705 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-50705 ] Frappe--Frappe Framework A Stored Cross-Sit=
    e Scripting (XSS) vulnerability exists in Frappe Framework version 17.0.0-d=
    ev due to improper neutralization of user-controlled input in the MultiSele= ctDialog component. 2026-06-24 not yet calculated CVE-2026-50708 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-50708 ] Frappe--Frappe Framework A Stor=
    ed Cross-Site Scripting (XSS) vulnerability exists in Frappe Framework vers= ion 17.0.0-dev due to improper neutralization of user-controlled input in t=
    he Notifications > Events panel. 2026-06-24 not yet calculated CVE-2026-507=
    09 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50709 ] Frappe--Frappe Fra= mework A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe F= ramework version 17.0.0-dev due to unsafe evaluation of user-controlled dat=
    a in the Number Card component. 2026-06-24 not yet calculated CVE-2026-5071=
    0 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50710 ] Frappe--Frappe Fram= ework A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fr= amework version 17.0.0-dev due to improper neutralization of user-controlle=
    d input in the Number Card component. 2026-06-24 not yet calculated CVE-202= 6-50711 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50711 ] Frappe--Frapp=
    e Framework A Stored Cross-Site Scripting (XSS) vulnerability exists in Fra= ppe Framework version 17.0.0-dev due to improper neutralization of user-con= trolled input in the frappe.ui.Tree component 2026-06-24 not yet calculated=
    CVE-2026-50712 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50712 ] FreeB= SD--FreeBSD When used to deliver a signal to a specific thread, thr_kill2(2=
    ) called p_cansignal() to determine whether the operation was permitted but=
    did not check the result before delivering the signal. The signal was sent=
    even when the permission check failed. The system call returned the result= ing error to the caller, but by then the signal had already been delivered.=
    The missing check allows an unprivileged local user who knows or can guess=
    a target's process and thread IDs to send any signal to a process they wou=
    ld not normally be permitted to signal, including processes owned by other = users or by root. The same check enforces jail boundaries, so a jailed proc= ess can signal processes on the host or in other jails. Thread IDs are allo= cated globally and sequentially, and so can be discovered by brute force wi=
    th no visibility into the target. An attacker can stop or terminate arbitra=
    ry processes, including critical system daemons, resulting in a Denial of S= ervice (DoS). 2026-06-26 not yet calculated CVE-2026-45256 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-45256 ] FreeBSD--FreeBSD The KTLS receive pat=
    h decrypted each record in place, assuming that the mbufs holding received = data were anonymous and safe to modify. This assumption does not hold for d= ata placed on a socket by sendfile(2), which can reference file-backed memo=
    ry directly through non-anonymous M_EXTPG pages or EXT_SFBUF mbufs. When th=
    e sender transmits such data over a loopback connection without enabling KT=
    LS on the transmit side, the file-backed mbufs reach the receiver's decrypt= ion path unchanged. Decrypting a record in place then overwrites the backin=
    g file's page cache instead of a private copy of the data. An unprivileged = local user who can read a file can overwrite its contents with data of thei=
    r choosing by sending the file over a loopback connection on which they hav=
    e enabled KTLS receive. The write modifies the page cache directly, so it b= ypasses file flags such as schg and is written back to disk. By overwriting=
    a setuid binary or other trusted file, a local user can escalate privilege=
    s, potentially gaining full control of the affected system. 2026-06-26 not = yet calculated CVE-2026-45257 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -45257 ] FreeBSD--FreeBSD dsp_mmap_single() validated the requested mapping=
    by checking the sum of the user-supplied offset and length against the buf= fer size. This addition could overflow, so that a large offset and length w= rapped around and passed the check. The offset was then narrowed from 64 to=
    32 bits when converted to a buffer address, yielding a mapping that extend=
    ed past the audio buffer into unrelated kernel memory. The /dev/dsp device = nodes are world-accessible by default. On a system with an audio device, ei= ther issue allows an unprivileged local user to read and write kernel memor=
    y, which can be used to escalate privileges, potentially gaining full contr=
    ol of the affected system. At a minimum, an attacker can crash the kernel, = resulting in a Denial of Service (DoS). 2026-06-27 not yet calculated CVE-2= 026-45258 [ https://www.cve.org/CVERecord?id=3DCVE-2026-45258 ] FreeBSD--Fr= eeBSD sigqueue(2) was marked as permitted in capability mode with the intro= duction of Capsicum in 2011, but the implementation of kern_sigqueue did no=
    t include a capability mode check restricting signal delivery to the callin=
    g process's own PID. A process in capability mode can use sigqueue(2) to se=
    nd signals to any process it could signal following standard Unix permissio= ns, bypassing the Capsicum sandbox restriction. A compromised sandboxed pro= cess could interfere with other processes, for example by sending SIGKILL o=
    r SIGSTOP. This could be any process running as the same user, or any proce= ss, for a superuser sandboxed process. 2026-06-27 not yet calculated CVE-20= 26-45259 [ https://www.cve.org/CVERecord?id=3DCVE-2026-45259 ] FreeBSD--Fre= eBSD The kernel handler for IPV6_MSFILTER dropped a serializing lock in ord=
    er to copy the source-filter list from userspace, then reacquired the lock.=
    During this window another thread could free the multicast filter structur=
    e, leaving the handler with a stale pointer to freed memory. An unprivilege=
    d local user can exploit this use-after-free to escalate privileges. 2026-0= 6-27 not yet calculated CVE-2026-49412 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-49412 ] FreeBSD--FreeBSD The Linuxulator determined whether a b= inary was set-user-ID or set-group-ID by checking the P_SUGID process flag.=
    During execve(2), this flag is not yet set at the point where the auxiliar=
    y vector is constructed, so AT_SECURE was incorrectly set to zero for set-u= ser-ID and set-group-ID executables. An unprivileged local user can inject =
    a shared library via LD_PRELOAD into a set-user-ID or set-group-ID Linux bi= nary, gaining the privileges of that binary. 2026-06-27 not yet calculated = CVE-2026-49413 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49413 ] FreeBS= D--FreeBSD The ELF image activator cleared per-process ASLR preference flag=
    s for setuid binaries after the code that computes the PIE base address, ra= ther than before. As a result, a user-requested ASLR disable was still in e= ffect at the point where the base address was chosen. An unprivileged local=
    user can disable ASLR for a setuid PIE binary by calling procctl(2) before=
    execve(2). This makes exploitation of any separate memory corruption vulne= rability in that binary significantly easier. 2026-06-27 not yet calculated=
    CVE-2026-49414 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49414 ] FreeB= SD--FreeBSD The CONS_HISTORY ioctl handler did not adequately validate the = requested history size. A large value caused an integer overflow in the buf= fer size calculation, resulting in a heap allocation smaller than expected.=
    Subsequent initialization of the buffer wrote beyond the end of the alloca= tion. An unprivileged local user with access to a vt(4) device can trigger =
    an out-of-bounds write in the kernel, potentially escalating privileges. 20= 26-06-27 not yet calculated CVE-2026-49416 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-49416 ] FreeBSD--FreeBSD Second, the audio buffer backing a m= apping could be freed when the device was closed even though the mapping re= mained valid. The freed memory could then be reused elsewhere while still a= ccessible through the stale mapping. The /dev/dsp device nodes are world-ac= cessible by default. On a system with an audio device, either issue allows =
    an unprivileged local user to read and write kernel memory, which can be us=
    ed to escalate privileges, potentially gaining full control of the affected=
    system. At a minimum, an attacker can crash the kernel, resulting in a Den= ial of Service (DoS). 2026-06-27 not yet calculated CVE-2026-49417 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-49417 ] Gaudire--Assassin game The vu= lnerability is present in the '/addJugador' endpoint: * The 'keyJugador' an=
    d 'keyJugadorObjectiu' parameters allow the modification of other users' in= formation without requiring prior authorization validation. This could enab=
    le an authenticated attacker to alter any user's ID and change their inform= ation. * The 'punts' and 'numObjectiusEliminats' fields allow arbitrary dat=
    a to be added because user input is not properly validated. This makes it p= ossible to obtain authentic prizes, awarded by city councils, by falsifying=
    game scores. * In the 'tokens' field, administrative privileges can be sel= f-assigned without server validation or prior authentication. This vulnerab= ility could allow an authenticated attacker to grant themselves administrat=
    or permissions and thus escalate privileges. * Numeric fields allow the ent=
    ry of extremely long values, which can cause the system to crash. Successfu=
    l exploitation of this vulnerability could allow an authenticated attacker =
    to launch a denial-of-service (DoS) attack, preventing created games from b= eing playable. * The 'urlImatge' parameter allows server-side requests to a= rbitrary URLs, enabling the retrieval of users' internal IP addresses, acce=
    ss to internal services, reading of local files, and unauthorized interacti=
    on with third-party APIs. An authenticated attacker could gain access to se= nsitive data. 2026-06-22 not yet calculated CVE-2026-7165 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-7165 ] Gaudire--Assassin game Vulnerability in= volving the exposure of sensitive data provided without adequate protection=
    . The API exposes email and phone number data from the 'email' and 'telefon=
    ' fields. This vulnerability is also present in the local database, as it c= ontains accessible sensitive information such as data on minors and municip=
    al users. Successful exploitation of this vulnerability could allow an unau= thenticated remote attacker to gain access to sensitive information and dat=
    a. 2026-06-22 not yet calculated CVE-2026-7166 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-7166 ] Gaudire--Assassin game The vulnerability arises wh=
    en the system fails to properly validate the 'email' field during the authe= ntication process, allowing unverified or fake email addresses to be accept= ed. This lack of validation enables the creation of user accounts with fake=
    email addresses, facilitating the mass creation of fraudulent accounts. Su= ccessful exploitation of this vulnerability could allow an authenticated at= tacker to carry out various attacks, such as mass spam distribution, system=
    abuse, or bypassing user controls, thereby compromising the security and i= ntegrity of the system. 2026-06-22 not yet calculated CVE-2026-7167 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-7167 ] getk2.org--K2 extension for J= oomla A Joomla user with K2 "create item" rights (Author tier by default) c=
    an submit an article whose `embedVideo` POST field contains a raw `<script>=
    ` tag; K2 stores it verbatim and renders it unescaped to any visitor of the=
    article page. 2026-06-25 not yet calculated CVE-2026-48940 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-48940 ] getk2.org--K2 extension for Joomla T=
    he K2 frontend `item.checkin` task accepts an unauthenticated `sigProFolder=
    ` query parameter and uses it directly to address a `JFolder::delete()` cal=
    l under `/media/k2/galleries/` 2026-06-25 not yet calculated CVE-2026-48941=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-48941 ] getk2.org--K2 extens= ion for Joomla K2 =C3=A2=E2=80=B0=C2=A4 2.26 renders the `#__k2_users.image=
    ` column directly into HTML `src` attributes via two distinct templates, in=
    both cases without HTML escaping. 2026-06-25 not yet calculated CVE-2026-4= 8942 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48942 ] getk2.org--K2 ex= tension for Joomla K2 =C3=A2=E2=80=B0=C2=A4 2.24 contains a mass-assignment=
    defect in the K2 system user plugin `plg_user_k2`. A Registered Joomla use=
    r, by including the field `K2UserForm=3D1` in a standard `com_users` `profi= le.save` POST, can write arbitrary values into the `notes`, `image`, and `p= lugins` columns of their own row in the `#__k2_users` table - none of which=
    are exposed by the K2 frontend profile-edit form. 2026-06-25 not yet calcu= lated CVE-2026-48943 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48943 ] = getk2.org--K2 extension for Joomla The K2 frontend article-save handler acc= epts an `attachment[N][existing]` POST field that is concatenated with `JPA= TH_SITE/` and passed to `JFile::copy()`. `JPath::clean` does NOT strip `..`=
    , and there is no allow-list of source paths. An Author can therefore copy = `configuration.php` (or any other file readable by the web user - including=
    `../../../etc/passwd`) into `/media/k2/attachments/`, then retrieve the co= ntents via the K2 attachment-download endpoint. 2026-06-25 not yet calculat=
    ed CVE-2026-48944 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48944 ] get= k2.org--K2 extension for Joomla The K2 article gallery upload path accepts =
    a zip/tar archive, extracts it under `/media/k2/galleries/<id>/`, and only = renames image files (gif/jpg/jpeg/png/webp) to safe names - non-image files=
    (including `.php`) are extracted as-is and remain executable via direct HT=
    TP access. 2026-06-25 not yet calculated CVE-2026-48945 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-48945 ] getk2.org--K2 extension for Joomla The K=
    2 frontend article-attachment upload path accepts files whose extension is = `.php`, and Apache's standard mod_php matches `\.php$` and executes them un= der the K2 web user. A K2 Author can upload a `shell.php`, then fetch `/med= ia/k2/attachments/shell.php` and execute arbitrary PHP code in the web serv= er's context. 2026-06-25 not yet calculated CVE-2026-48946 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-48946 ] GIMP--GIMP GIMP HDR File Parsing Heap= -based Buffer Overflow Remote Code Execution Vulnerability. This vulnerabil= ity allows remote attackers to execute arbitrary code on affected installat= ions of GIMP. User interaction is required to exploit this vulnerability in=
    that the target must visit a malicious page or open a malicious file. The = specific flaw exists within the parsing of HDR files. The issue results fro=
    m the lack of proper validation of the length of user-supplied data prior t=
    o copying it to a heap-based buffer. An attacker can leverage this vulnerab= ility to execute code in the context of the current process. Was ZDI-CAN-28= 266. 2026-06-24 not yet calculated CVE-2026-2050 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-2050 ] GitHub--GitHub Copilot 1.372.0 GitHub Copilot 1.= 372.0 allows filesystem access outside of a workspace folder (without user = approval) via a file-handler URI parameter to fetch_webpage. Therefore, exf= iltration could occur if there is indirect prompt injection. 2026-06-22 not=
    yet calculated CVE-2025-66389 [ https://www.cve.org/CVERecord?id=3DCVE-202= 5-66389 ] GitLab--GitLab GitLab has remediated an issue in GitLab CE/EE aff= ecting all versions from 8.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 b= efore 19.1.1 that under certain conditions could have allowed an authentica= ted user with maintainer-role permissions to make requests to internal netw= ork resources through mirror synchronization due to improper URL validation=
    . 2026-06-25 not yet calculated CVE-2026-12635 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-12635 ] GNOME--libxml2 Use After Free in libxml2's xmlPar= seInternalSubset from GNOME libxml2 version 2.9.11 to 2.11.0 allows a remot=
    e attacker to cause a denial-of-service via maliciously crafted XML input w= ith improper entity resolution handling. 2026-06-22 not yet calculated CVE-= 2026-6653 [ https://www.cve.org/CVERecord?id=3DCVE-2026-6653 ] gogs--gogs G= ogs is an open source self-hosted Git service. Prior to 0.14.3, when ENABLE= _REVERSE_PROXY_AUTHENTICATION is enabled, Gogs accepts the configured authe= ntication header (default: X-WEBAUTH-USER) directly from client requests wi= thout validating that the request originated from a trusted reverse proxy. = Any remote attacker who can reach the Gogs service can forge this header to=
    impersonate any user or trigger automatic account creation, completely byp= assing authentication. This vulnerability is fixed in 0.14.3. 2026-06-24 no=
    t yet calculated CVE-2026-25119 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-25119 ] gogs--gogs Gogs is an open source self-hosted Git service. Prior=
    to 0.14.3, a repository admin collaborator can escalate their privileges t=
    o owner-level access by exploiting an off-by-one error in the ChangeCollabo= rationAccessMode function. This vulnerability is fixed in 0.14.3. 2026-06-2=
    4 not yet calculated CVE-2026-52804 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-52804 ] gogs--gogs Gogs is an open source self-hosted Git service. P= rior to 0.14.3, in new_form.tmpl, milestone names are rendered with Go's de= fault auto-escaping ({{.Name}}), which converts < to &lt; etc. This prevent=
    s direct HTML injection. However, when the browser renders the DOM, the tex=
    t content of the element contains the decoded original payload. Semantic UI=
    2.4.2's dropdown component has preserveHTML: true as the default setting. = When a user selects a dropdown item, the internal set.text() method calls j= Query's .html() with the item's text content. This re-parses the decoded te=
    xt as HTML, creating the injected element and triggering the JavaScript eve=
    nt handler. An attacker can store an HTML/JavaScript payload in a milestone=
    name, and when any user opens the New Issue page and interacts with the mi= lestone dropdown, the payload executes in their browser via Semantic UI's p= reserveHTML behavior. This vulnerability is fixed in 0.14.3. 2026-06-24 not=
    yet calculated CVE-2026-52807 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-52807 ] gogs--gogs Gogs is an open source self-hosted Git service. Prior =
    to 0.14.3, Git smart HTTP authorizes POST /git-receive-pack using the clien= t-supplied service query string (so ?service=3Dgit-upload-pack is evaluated=
    as read access) while routing still runs git receive-pack, allowing push w= here only read should be allowed. This vulnerability is fixed in 0.14.3. 20= 26-06-24 not yet calculated CVE-2026-52810 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-52810 ] gogs--gogs Gogs is an open source self-hosted Git ser= vice. Prior to 0.14.3, (*Repository).UploadRepoFiles checks for symlinks on=
    ly on the leaf of the upload target (osx.IsSymlink(targetPath)). The siblin=
    gs UpdateRepoFile, DeleteRepoFile, and GetDiffPreview use hasSymlinkInPath,=
    which lstats every component - UploadRepoFiles is the lone outlier. An att= acker with repo-write access plus a multipart upload whose filename contain=
    s a literal backslash (preserved by filepath.Base on Linux, then converted =
    to / by pathx.Clean) redirects the write through a previously-committed dir= ectory symlink. iox.CopyFile opens the destination with os.Create (no O_NOF= OLLOW), so the kernel follows the parent symlink and writes attacker bytes = anywhere the gogs UID can write - ~git/.ssh/authorized_keys =C3=A2=E2=80=A0= =E2=80=99 SSH foothold, or <repo>.git/hooks/post-receive =C3=A2=E2=80=A0=E2= =80=99 next-push RCE. This vulnerability is fixed in 0.14.3. 2026-06-24 not=
    yet calculated CVE-2026-52811 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-52811 ] gogs--gogs Gogs is an open source self-hosted Git service. Prior =
    to 0.14.3, Git LFS storage is content-addressed by OID alone (<LFS-root>/<o= id[0]>/<oid[1]>/<oid>) but per-repo authorization lives in the lfs_object t= able keyed (repo_id, oid). serveUpload skips re-uploading when the OID file=
    already exists on disk and inserts a new (repo_id, oid) row pointing at it=
    without verifying the request body hashes to the OID being claimed. Any us=
    er with write access to one repo can bind their repo to an OID owned by a p= rivate repo and download the original bytes via their own download endpoint=
    . This vulnerability is fixed in 0.14.3. 2026-06-24 not yet calculated CVE-= 2026-52812 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52812 ] gogs--gogs=
    Gogs is an open source self-hosted Git service. Prior to 0.14.3, the Gogs = built-in Go SSH server is vulnerable to an unauthenticated, asymmetric Deni=
    al of Service (DoS) attack. The application accepts inbound TCP connections=
    and passes them to golang.org/x/crypto/ssh.NewServerConn inside a new goro= utine without enforcing any read/write deadlines on the underlying net.Conn=
    . An unauthenticated attacker can open multiple TCP connections to the SSH = port and simply withhold the SSH protocol banner. This forces the server to=
    spawn an unbounded number of goroutines that block indefinitely waiting fo=
    r socket I/O. This leads to complete File Descriptor (FD) exhaustion, preve= nting legitimate users from accessing the Git SSH service, and ultimately d= estabilizing the entire Gogs process (e.g., causing internal log rotation f= ailures). This vulnerability is fixed in 0.14.3. 2026-06-24 not yet calcula= ted CVE-2026-52814 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52814 ] go= gs--gogs Gogs is an open source self-hosted Git service. Prior to 0.14.3, G= ogs has an unauthenticated information disclosure vulnerability. The GET /a= pi/v1/orgs/:orgname/teams endpoint at internal/route/api/v1/org_team.go:8 r= eturns all teams for any organization without requiring authentication. The=
    route group at internal/route/api/v1/api.go:380-385 lacks the reqToken() m= iddleware, and the listTeams() handler performs no authentication check, ex= posing team IDs, names, descriptions, and permission levels to any unauthen= ticated caller. This vulnerability is fixed in 0.14.3. 2026-06-24 not yet c= alculated CVE-2026-52815 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5281=
    5 ] gogs--gogs Gogs is an open source self-hosted Git service. Prior to 0.1= 4.3, the Jupyter Notebook (ipynb) sanitizer endpoint at POST /-/api/sanitiz= e_ipynb allows arbitrary data: URIs without proper restrictions, potentiall=
    y leading to Cross-Site Scripting (XSS). The endpoint uses bluemonday.UGCPo= licy() with p.AllowURLSchemes("data") which permits all data URI schemes in= cluding data:text/html, enabling attackers to inject malicious HTML/JavaScr= ipt. Additionally, the endpoint has no authentication middleware, allowing = any registered user to exploit this vulnerability. This vulnerability is fi= xed in 0.14.3. 2026-06-24 not yet calculated CVE-2026-52816 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-52816 ] golang.org/x/image--golang.org/x/ima= ge/tiff The TIFF decoder does not set a limit on the size of tiles in tiled=
    images, permitting a malicious or corrupt image containing a very large ti=
    le to cause unbounded memory consumption. 2026-06-25 not yet calculated CVE= -2026-46602 [ https://www.cve.org/CVERecord?id=3DCVE-2026-46602 ] golang.or= g/x/image--golang.org/x/image/tiff The TIFF decoder can panic when decoding=
    an invalid image with an out-of-bounds strip offset. 2026-06-26 not yet ca= lculated CVE-2026-46604 [ https://www.cve.org/CVERecord?id=3DCVE-2026-46604=
    ] golang.org/x/image--golang.org/x/image/webp The webp decoder can panic w= hen processing a VP8 chunk with dimensions that do not match the canvas siz=
    e. 2026-06-25 not yet calculated CVE-2026-46601 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-46601 ] Google Cloud--Cloud Console UIs A Missing Author= ization vulnerability in a GraphQL private API operation of the Google App = Engine section of the Cloud Console allows an unauthenticated remote attack=
    er to leak sensitive App Engine request logs from other projects using a sp= ecially crafted request. This vulnerability was patched on 7 April 2026, an=
    d no customer action is needed. 2026-06-22 not yet calculated CVE-2026-8934=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-8934 ] Google Cloud--Gemini = CLI Improper Neutralization used in an OS Command in the container launcher=
    in Google Gemini CLI (versions prior to 0.39.1) and run-gemini-cli GitHub = Action (versions prior to 0.1.22) on headless CI platforms allows an unpriv= ileged attacker to achieve pre-sandbox host-level code execution a maliciou= sly crafted .gemini/.env file. 2026-06-24 not yet calculated CVE-2026-12537=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-12537 ] Google--Chrome Inapp= ropriate implementation in DeviceBoundSessionCredentials in Google Chrome p= rior to 149.0.7827.197 allowed a remote attacker to bypass same origin poli=
    cy via a crafted HTML page. (Chromium security severity: High) 2026-06-24 n=
    ot yet calculated CVE-2026-13021 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-13021 ] Google--Chrome Inappropriate implementation in Autofill in Goog=
    le Chrome prior to 149.0.7827.197 allowed a remote attacker who had comprom= ised the renderer process to leak cross-origin data via a crafted HTML page=
    . (Chromium security severity: High) 2026-06-24 not yet calculated CVE-2026= -13022 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13022 ] Google--Chrome=
    Uninitialized Use in GPU in Google Chrome prior to 149.0.7827.197 allowed =
    a remote attacker who had compromised the renderer process to obtain potent= ially sensitive information from process memory via a crafted HTML page. (C= hromium security severity: High) 2026-06-24 not yet calculated CVE-2026-130=
    23 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13023 ] Google--Chrome Ins= ufficient validation of untrusted input in Navigation in Google Chrome prio=
    r to 149.0.7827.197 allowed a remote attacker who had compromised the rende= rer process to bypass site isolation via a crafted HTML page. (Chromium sec= urity severity: High) 2026-06-24 not yet calculated CVE-2026-13024 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-13024 ] Google--Chrome Race in DevToo=
    ls in Google Chrome prior to 149.0.7827.197 allowed a remote attacker who h=
    ad compromised the renderer process to potentially perform a sandbox escape=
    via a crafted HTML page. (Chromium security severity: High) 2026-06-24 not=
    yet calculated CVE-2026-13025 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-13025 ] Google--Chrome Use after free in Digital Credentials in Google Ch= rome on Mac prior to 149.0.7827.197 allowed a remote attacker to potentiall=
    y exploit heap corruption via a crafted HTML page. (Chromium security sever= ity: High) 2026-06-24 not yet calculated CVE-2026-13026 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-13026 ] Google--Chrome Use after free in FileSys= tem in Google Chrome prior to 149.0.7827.197 allowed a remote attacker to p= otentially exploit heap corruption via a crafted HTML page. (Chromium secur= ity severity: High) 2026-06-24 not yet calculated CVE-2026-13027 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-13027 ] Google--Chrome Use after free i=
    n WebGL in Google Chrome on Android prior to 149.0.7827.197 allowed a remot=
    e attacker to potentially perform a sandbox escape via a crafted HTML page.=
    (Chromium security severity: Critical) 2026-06-24 not yet calculated CVE-2= 026-13028 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13028 ] Google--Chr= ome Use after free in Web Authentication in Google Chrome prior to 149.0.78= 27.197 allowed an attacker who convinced a user to install a malicious exte= nsion to potentially exploit heap corruption via a crafted Chrome Extension=
    . (Chromium security severity: High) 2026-06-24 not yet calculated CVE-2026= -13029 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13029 ] Google--Chrome=
    Uninitialized Use in GPU in Google Chrome on Android prior to 149.0.7827.1=
    97 allowed a remote attacker to obtain potentially sensitive information fr=
    om process memory via a crafted HTML page. (Chromium security severity: Hig=
    h) 2026-06-24 not yet calculated CVE-2026-13030 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-13030 ] Google--Chrome Use after free in Blink in Google=
    Chrome prior to 149.0.7827.197 allowed a remote attacker to execute arbitr= ary code inside a sandbox via a crafted HTML page. (Chromium security sever= ity: High) 2026-06-24 not yet calculated CVE-2026-13031 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-13031 ] Google--Chrome Use after free in WebGL i=
    n Google Chrome on Android prior to 149.0.7827.197 allowed a remote attacke=
    r to potentially perform a sandbox escape via a crafted HTML page. (Chromiu=
    m security severity: Critical) 2026-06-24 not yet calculated CVE-2026-13032=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-13032 ] Google--Chrome Out o=
    f bounds read and write in Blink>InterestGroups in Google Chrome prior to 1= 49.0.7827.197 allowed a remote attacker to execute arbitrary code via a cra= fted HTML page. (Chromium security severity: Critical) 2026-06-24 not yet c= alculated CVE-2026-13033 [ https://www.cve.org/CVERecord?id=3DCVE-2026-1303=
    3 ] Google--Chrome Inappropriate implementation in Passwords in Google Chro=
    me prior to 149.0.7827.197 allowed a remote attacker who had compromised th=
    e renderer process to bypass site isolation via a crafted HTML page. (Chrom= ium security severity: High) 2026-06-24 not yet calculated CVE-2026-13034 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-13034 ] Google--Chrome Use aft=
    er free in Bluetooth in Google Chrome on Mac prior to 149.0.7827.197 allowe=
    d a remote attacker to execute arbitrary code via a malicious peripheral. (= Chromium security severity: High) 2026-06-24 not yet calculated CVE-2026-13= 035 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13035 ] Google--Chrome Us=
    e after free in Blink in Google Chrome prior to 149.0.7827.197 allowed a re= mote attacker to execute arbitrary code inside a sandbox via a crafted HTML=
    page. (Chromium security severity: High) 2026-06-24 not yet calculated CVE= -2026-13036 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13036 ] Google--C= hrome Use after free in WebView in Google Chrome on Android prior to 149.0.= 7827.197 allowed a local attacker to execute arbitrary code inside a sandbo=
    x via a crafted HTML page. (Chromium security severity: High) 2026-06-24 no=
    t yet calculated CVE-2026-13037 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-13037 ] Google--Chrome Use after free in Autofill in Google Chrome on Wi= ndows prior to 149.0.7827.197 allowed a remote attacker to execute arbitrar=
    y code via a crafted HTML page. (Chromium security severity: Critical) 2026= -06-24 not yet calculated CVE-2026-13038 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-13038 ] Google--Chrome Integer overflow in Mojo in Google Chrom=
    e prior to 149.0.7827.201 allowed a remote attacker who had compromised the=
    renderer process to potentially perform a sandbox escape via a malicious f= ile. (Chromium security severity: High) 2026-06-25 not yet calculated CVE-2= 026-13281 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13281 ] Google--Chr= ome Use after free in Payments in Google Chrome on Android prior to 149.0.7= 827.201 allowed a local attacker to potentially exploit heap corruption via=
    physical access to the device. (Chromium security severity: High) 2026-06-=
    25 not yet calculated CVE-2026-13282 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-13282 ] Google--Chrome Use after free in AdFilter in Google Chrome =
    on Android prior to 149.0.7827.201 allowed a remote attacker who convinced =
    a user to engage in specific UI gestures to execute arbitrary code via a cr= afted HTML page. (Chromium security severity: High) 2026-06-25 not yet calc= ulated CVE-2026-13283 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13283 ]=
    Google--go-attestation Improper Validation of Specified Index, Position, o=
    r Offset in Input vulnerability in Google go-attestation. parseEfiSignature= List() does not advance the buffer past vendor bytes before reading entries=
    . For hashSHA256SigGUID lists, this allows attacker-controlled vendor heade=
    r bytes to be appended to the trusted SHA256 hash list. A crafted TPM event=
    log could inject arbitrary SHA256 hashes into the verifier's trusted measu= rement database, enabling a remote attestation verifier to accept a comprom= ised boot state. This issue affects go-attestation: through 0.6.0. 2026-06-=
    24 not yet calculated CVE-2026-12681 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-12681 ] GPAC--MP4Box A use-after-free in the gf_sei_load_from_state= _internal function (/filters/sei_load.c) of GPAC Project/MP4Box before 26.0= 2.0 allows attackers to cause a Denial of Service (DoS) via supplying a cra= fted MPEG-2 TS file. 2026-06-25 not yet calculated CVE-2025-60464 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2025-60464 ] GPAC--MP4Box A use-after-free =
    in the gf_filter_pid_inst_swap function (/filter_core/filter_pid.c) of GPAC=
    Project/MP4Box before 26.02.0 allows attackers to cause a Denial of Servic=
    e (DoS) via supplying a crafted media file. 2026-06-25 not yet calculated C= VE-2025-60465 [ https://www.cve.org/CVERecord?id=3DCVE-2025-60465 ] GPAC--M= P4Box A use-after-free in the gf_filter_pid_get_packet function (/filter_co= re/filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to = cause a Denial of Service (DoS) via supplying a crafted media file. 2026-06= -24 not yet calculated CVE-2025-60466 [ https://www.cve.org/CVERecord?id=3D= CVE-2025-60466 ] GPAC--MP4Box A use-after-free in the gf_filter_pid_inst_sw= ap_delete_task function (/filter_core/filter_pid.c) of GPAC Project/MP4Box = before 26.02.0 allows attackers to cause a Denial of Service (DoS) via supp= lying a crafted media file. 2026-06-24 not yet calculated CVE-2025-60467 [ = https://www.cve.org/CVERecord?id=3DCVE-2025-60467 ] GPAC--MP4Box GPAC Multi= media Open Source Project GPAC Project/MP4Box 2.5-DEV-rev1593-gfe88c3545-ma= ster is affected by: Buffer Overflow. The impact is: cause a denial of serv= ice (local). The component is: filter_core/filter_pid.c (L:574-580): functi=
    on gf_filter_pid_inst_swap_delete_task() improperly accesses freed objects = during PID instance swap/delete cleanup, leading to heap use-after-free. Th=
    e attack vector is: Local (AV:L): a local, authenticated user who processes=
    a specially crafted MPEG-2 TS/MP4 file with MP4Box can trigger the bug dur= ing filter teardown (PID instance swap/delete), causing a crash. =C3=82=C2= =B6=C3=82=C2=B6 In GPAC s MP4Box, gf_filter_pid_inst_swap_delete_task() in = filter_core/filter_pid.c may dereference objects after they have been freed=
    when cleaning up PID instances after a swap/delete operation. Crafted inpu=
    ts (e.g., malformed MPEG-2 TS) can trigger a heap use-after-free and crash;=
    exploitation may be possible. 2026-06-24 not yet calculated CVE-2025-60468=
    [ https://www.cve.org/CVERecord?id=3DCVE-2025-60468 ] GPAC--MP4Box A use-a= fter-free in the gf_filter_pid_reconfigure_task_discard function (/filter_c= ore/filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to=
    cause a Denial of Service (DoS) via supplying a crafted media file. 2026-0= 6-24 not yet calculated CVE-2025-60471 [ https://www.cve.org/CVERecord?id= =3DCVE-2025-60471 ] GPAC--MP4Box A NULL pointer dereference in the gf_filte= r_in_parent_chain function (/filter_core/filter_pid.c) of GPAC Project/MP4B=
    ox before 26.02.0 allows attackers to cause a Denial of Service (DoS) via s= upplying a crafted file. 2026-06-24 not yet calculated CVE-2025-60473 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2025-60473 ] GPAC--MP4Box A buffer over= flow in the gf_media_import function (/media_tools/av_parsers.c) of GPAC Pr= oject/MP4Box before 26.02.0 allows attackers to cause a Denial of Service (= DoS) via supplying a crafted input. 2026-06-24 not yet calculated CVE-2025-= 60474 [ https://www.cve.org/CVERecord?id=3DCVE-2025-60474 ] GPAC--MP4Box v2=
    .4 GPAC MP4Box v2.4 was discovered to contain a NULL pointer dereference in=
    the gf_isom_add_track_kind() function at isomedia/isom_write.c. This vulne= rability allows attackers to cause a Denial of Service (DoS) via a crafted = MP4 file. 2026-06-23 not yet calculated CVE-2025-55639 [ https://www.cve.or= g/CVERecord?id=3DCVE-2025-55639 ] Grocery-Store-Management-System--Grocery-= Store-Management-System GROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL= -PHPMYADMIN v1.0 was discovered to contain a SQL injection vulnerability in=
    the scost parameter in /grocery/search_products.php. This vulnerability al= lows attackers to access sensitive database information via a crafted SQL s= tatement. 2026-06-25 not yet calculated CVE-2026-37149 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-37149 ] HAYAJO--Mojolicious::Plugin::Web::Auth::O= Auth2 Mojolicious::Plugin::Web::Auth::OAuth2 versions through 0.17 for Perl=
    have an insecure default state parameter. When no state generator is speci= fied in the constructor, the module defaults to using a SHA-1 hash of predi= ctable and low-entropy sources, including the epoch time (which is leaked v=
    ia the HTTP Date header) and a call to Perl's built-in rand function. A pre= dictable state allows an attacker to hijack another user's session through = cross site request forgery (CSRF). 2026-06-23 not yet calculated CVE-2026-9= 733 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9733 ] Horner Automation-= -Cscape Horner Automation Cscape versions prior to 10.2 SP3 are vulnerable =
    to an Out-of-Bounds Read vulnerability through parsing CSP files. Successfu=
    l exploitation of this vulnerability could allow an attacker to disclose in= formation and execute arbitrary code. 2026-06-25 not yet calculated CVE-202= 6-12897 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12897 ] HP Inc.--HP D= ock Accessory A potential security vulnerability has been identified in the=
    HP Accessory WMI Provider installer for some HP Docking Stations, which mi= ght allow escalation of privilege and/or arbitrary code execution. HP is re= leasing software updates to mitigate the potential vulnerability. 2026-06-2=
    4 not yet calculated CVE-2026-7539 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-7539 ] HYPR--Passwordless Missing authentication for critical functio=
    n vulnerability in HYPR Passwordless on Windows allows Credentials Intercep= tion. This issue affects HYPR Passwordless: before 11.1.1. 2026-06-25 not y=
    et calculated CVE-2026-4522 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 522 ] IBM--WebSphere Application Server IBM WebSphere Application Server 8.=
    5 and 9.0=C2=A0could allow a remote attacker to bypass authentication and g= ain unauthorized access to JAX-WS applications. 2026-06-22 not yet calculat=
    ed CVE-2026-10845 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10845 ] Ima= geMagick--ImageMagick ImageMagick before 7.1.2-15 and 6.9.13-40 contains a = memory leak in coders/txt.c when processing TXT files with texture attribut= es: the texture object allocated via ReadImage is not released when GetType= Metrics fails, leaking memory each time a crafted TXT file with a texture a= ttribute is processed. 2026-06-23 not yet calculated CVE-2026-56371 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-56371 ] ImageMagick--ImageMagick Ima= geMagick before 7.1.2-15 and 6.9.13-40 contains a command injection vulnera= bility in the SVG decoder that allows attackers to inject arbitrary MVG dra= wing commands. Attackers can craft malicious SVG files with injected Magick=
    Vector Graphics commands that execute during rendering. 2026-06-23 not yet=
    calculated CVE-2026-56379 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56= 379 ] Imagination Technologies--Graphics DDK A web page that contains unusu=
    al GPU shader code is loaded into the GPU compiler process and can trigger =
    a write out-of-bounds write crash in the GPU shader compiler library. On ce= rtain platforms, when the compiler process has system privileges this could=
    enable further exploits on the device. An edge case using a very small val=
    ue in GPU shader code can cause a segmentation fault in the GPU shader comp= iler due to am out-of-bounds write. 2026-06-26 not yet calculated CVE-2026-= 21734 [ https://www.cve.org/CVERecord?id=3DCVE-2026-21734 ] Imagination Tec= hnologies--Graphics DDK Kernel software installed and running inside a Host=
    VM may post improper commands to the GPU Firmware to trigger a memory read=
    or write outside the permitted range of memory for the host kernel. Addres= ses passed to the GPU Firmware can be used by the Firmware for more privile= ged memory accesses than are permitted by the system. 2026-06-26 not yet ca= lculated CVE-2026-45195 [ https://www.cve.org/CVERecord?id=3DCVE-2026-45195=
    ] isaacs--node-tar node-tar is a full-featured Tar for Node.js. Prior to 7= .5.16, tar (node-tar) applies a PAX extended header's size=3D record (and o= ther PAX overrides) to the next header entry of any type, including interme= diary metadata headers such as a GNU long-name (L) or long-link (K) entry. = Per POSIX pax, a PAX extended header (x) describes the next file entry, not=
    the intermediary extension headers that may sit between the x header and t=
    he file it annotates. Because node-tar lets the PAX size override the byte = length of an intervening L/K/x header, an attacker can desynchronize node-t= ar's stream cursor relative to every other mainstream tar implementation (G=
    NU tar, libarchive/bsdtar, Python tarfile, and the now-fixed tar-rs / astra= l-tokio-tar). The result is a tar parser interpretation differential (CWE-4= 36): a single crafted archive yields a different set of members under node-= tar than under the reference tar tools. An attacker can use this to hide a = member from one parser while it is visible to another, which defeats securi=
    ty tooling whose scanner and extractor disagree on archive contents (e.g. a=
    malware/secret scanner that lists entries with one library while a downstr= eam step extracts with another) This vulnerability is fixed in 7.5.16. 2026= -06-22 not yet calculated CVE-2026-53655 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53655 ] JASEI--Net::Statsite::Client Net::Statsite::Client vers= ions through 1.1.0 for Perl allow metric injections. Net::Statsite::Client =
    is a client for the statsite protocol, which is a variant of statsd. Newlin=
    es are not removed from metric names, allowing metric injections. Values ar=
    e not sanitised for newlines or other protocol control characters such as c= olons or pipes, allowing metric injections. 2026-06-22 not yet calculated C= VE-2026-11373 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11373 ] jellyfi= n--jellyfin Jellyfin is an open source self hosted media server. Prior to 1= 0.11.10, a specifically crafted MKV file containing forged filename tags ca=
    n be leveraged to exploit missing path sanitization during playback. Jellyf=
    in treats the MKV file name tag on MKV attachments as trusted and passes it=
    unsanitized into Path.Combine(attachmentFolder, fileName) inside PathManag= er.GetAttachmentPath. Because .NET's Path.Combine neither normalises .. nor=
    rejects a rooted second argument, a crafted MKV can redirect Jellyfin's MK=
    V attachment extraction to any absolute path on disk. This triggers on any = playback action of the affected video on a client which will attempt to bur=
    n in the subtitles by default.g This vulnerability is fixed in 10.11.10. 20= 26-06-24 not yet calculated CVE-2026-49246 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-49246 ] Jenkins Project--Jenkins Active Directory Plugin Jenk= ins Active Directory Plugin 2.41.1 and earlier does not escape the user nam=
    e before building the LDAP search filter in the Windows native (ADSI) authe= ntication path, allowing unauthenticated attackers to inject LDAP wildcard = characters to enumerate directory entries and to authenticate as a matching=
    user whose password they know without knowing their exact user name. 2026-= 06-24 not yet calculated CVE-2026-57288 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-57288 ] Jenkins Project--Jenkins Assembla Plugin Jenkins Assemb=
    la Plugin 1.4 and earlier does not configure its XML parser to prevent XML = external entity (XXE) attacks, allowing attackers able to control the respo= nses of the configured Assembla server to extract secrets from the Jenkins = controller or perform server-side request forgery. 2026-06-24 not yet calcu= lated CVE-2026-57303 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57303 ] = Jenkins Project--Jenkins Assembla Plugin A missing permission check in Jenk= ins Assembla Plugin 1.4 and earlier allows attackers with Overall/Read perm= ission to connect to an attacker-specified URL using an attacker-specified = username and password. 2026-06-24 not yet calculated CVE-2026-57304 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-57304 ] Jenkins Project--Jenkins Ass= embla Plugin A cross-site request forgery (CSRF) vulnerability in Jenkins A= ssembla Plugin 1.4 and earlier allows attackers to connect to an attacker-s= pecified URL using an attacker-specified username and password. 2026-06-24 = not yet calculated CVE-2026-57305 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-57305 ] Jenkins Project--Jenkins Bitbucket Push and Pull Request Plugi=
    n Jenkins Bitbucket Push and Pull Request Plugin 3.3.8 and earlier uncondit= ionally disables SSL/TLS certificate and hostname validation for connection=
    s sending Bearer token authenticated requests to the configured Bitbucket S= erver endpoint, allowing attackers able to intercept network traffic to cap= ture the token. 2026-06-24 not yet calculated CVE-2026-57289 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-57289 ] Jenkins Project--Jenkins Contrast C= ontinuous Application Security Plugin A missing permission check in Jenkins=
    Contrast Continuous Application Security Plugin 3.11 and earlier allows at= tackers with Overall/Read permission to connect to an attacker-specified UR=
    L using an attacker-specified username, API key, and service key. 2026-06-2=
    4 not yet calculated CVE-2026-57297 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-57297 ] Jenkins Project--Jenkins Contrast Continuous Application Sec= urity Plugin A cross-site request forgery (CSRF) vulnerability in Jenkins C= ontrast Continuous Application Security Plugin 3.11 and earlier allows atta= ckers to have Jenkins connect to an attacker-specified URL using an attacke= r-specified username, API key, and service key. 2026-06-24 not yet calculat=
    ed CVE-2026-57298 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57298 ] Jen= kins Project--Jenkins Contrast Continuous Application Security Plugin Missi=
    ng permission checks in Jenkins Contrast Continuous Application Security Pl= ugin 3.11 and earlier allow attackers with Overall/Read permission to enume= rate the names of configured Contrast metadata. 2026-06-24 not yet calculat=
    ed CVE-2026-57299 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57299 ] Jen= kins Project--Jenkins EC2 Fleet Plugin A missing permission check in Jenkin=
    s EC2 Fleet Plugin 4.2.3.539.v8fedff2a_81c3 and earlier allows attackers wi=
    th Overall/Read permission to connect to an attacker-specified URL using at= tacker-specified credentials IDs obtained through another method, capturing=
    AWS credentials stored in Jenkins. 2026-06-24 not yet calculated CVE-2026-= 57294 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57294 ] Jenkins Project= --Jenkins EC2 Fleet Plugin A cross-site request forgery (CSRF) vulnerabilit=
    y in Jenkins EC2 Fleet Plugin 4.2.3.539.v8fedff2a_81c3 and earlier allows a= ttackers to connect to an attacker-specified URL using attacker-specified c= redentials IDs obtained through another method, capturing AWS credentials s= tored in Jenkins. 2026-06-24 not yet calculated CVE-2026-57295 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-57295 ] Jenkins Project--Jenkins External=
    Workspace Manager Plugin Jenkins External Workspace Manager Plugin 1.3.2 a=
    nd earlier does not reject path traversal sequences in the custom workspace=
    path provided to the exwsAllocate Pipeline step, allowing attackers with I= tem/Configure permission to read arbitrary files on the Jenkins controller = file system, which can lead to remote code execution. 2026-06-24 not yet ca= lculated CVE-2026-57296 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57296=
    ] Jenkins Project--Jenkins FitNesse Plugin Jenkins FitNesse Plugin 1.36 an=
    d earlier stores passwords unencrypted in job config.xml files on the Jenki=
    ns controller, where they can be viewed by users with Extended Read permiss= ion or access to the Jenkins controller file system. 2026-06-24 not yet cal= culated CVE-2026-57302 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57302 =
    ] Jenkins Project--Jenkins Git client Plugin Jenkins Git client Plugin 6.6.=
    0 and earlier does not correctly escape the workspace directory name when i=
    t is embedded into a generated SSH wrapper script, allowing attackers able =
    to control the name of a build's working directory to execute arbitrary ope= rating system commands on the agent. 2026-06-24 not yet calculated CVE-2026= -57282 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57282 ] Jenkins Projec= t--Jenkins Git Parameter Plugin A missing permission check in Jenkins Git P= arameter Plugin 462.vdcf3df2ed2ca_ and earlier allows attackers with Item/R= ead permission to obtain information about the SCM repository used by a job=
    , such as branch names, tag names, and revision metadata. 2026-06-24 not ye=
    t calculated CVE-2026-57286 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 7286 ] Jenkins Project--Jenkins Gitee Plugin Missing permission checks in J= enkins Gitee Plugin 1288.v18b_deb_c9069b_ and earlier allow attackers with = Overall/Read permission to connect to an attacker-specified URL using attac= ker-specified credentials IDs obtained through another method. 2026-06-24 n=
    ot yet calculated CVE-2026-57291 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-57291 ] Jenkins Project--Jenkins Gitee Plugin A cross-site request forg= ery (CSRF) vulnerability in Jenkins Gitee Plugin 1288.v18b_deb_c9069b_ and = earlier allows attackers to connect to an attacker-specified URL using atta= cker-specified credentials IDs obtained through another method. 2026-06-24 = not yet calculated CVE-2026-57292 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-57292 ] Jenkins Project--Jenkins Gitee Plugin An incorrect permission = check in Jenkins Gitee Plugin 1288.v18b_deb_c9069b_ and earlier allows atta= ckers with global Item/Configure permission (while lacking Item/Configure p= ermission on any particular job) to enumerate credentials IDs of credential=
    s stored in Jenkins. 2026-06-24 not yet calculated CVE-2026-57293 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-57293 ] Jenkins Project--Jenkins GitHu=
    b Branch Source Plugin A missing permission check in Jenkins GitHub Branch = Source Plugin 1967.1969.v205fd594c821 and earlier allows attackers with Ove= rall/Read permission to obtain the URLs of GitHub Enterprise servers config= ured in the global plugin configuration. 2026-06-24 not yet calculated CVE-= 2026-57285 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57285 ] Jenkins Pr= oject--Jenkins Job Configuration History Plugin Jenkins Job Configuration H= istory Plugin 1356.ve360da_6c523a_ and earlier does not redact the encrypte=
    d values of secrets when displaying historical job and agent configurations=
    , allowing attackers with Extended Read permission to view encrypted secret=
    values that would otherwise be redacted. 2026-06-24 not yet calculated CVE= -2026-57287 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57287 ] Jenkins P= roject--Jenkins MCP Server Plugin A missing permission check in Jenkins MCP=
    Server Plugin 0.177.v629fdb_2557fe and earlier allows attackers with Item/= Read permission to read the Pipeline replay scripts of jobs they can access=
    . 2026-06-24 not yet calculated CVE-2026-57300 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-57300 ] Jenkins Project--Jenkins OWASP ZAP Plugin Jenkins=
    OWASP ZAP Plugin 1.0.7 and earlier performs build operations on the Jenkin=
    s controller rather than the assigned agent, allowing attackers with Item/C= onfigure permission to execute arbitrary code on the Jenkins controller. 20= 26-06-24 not yet calculated CVE-2026-57301 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-57301 ] Jenkins Project--Jenkins Pipeline: Groovy Plugin A cr= oss-site request forgery (CSRF) vulnerability in Jenkins Pipeline: Groovy P= lugin 4331.v9d06ed4658ff and earlier allows attackers to instantiate types = related to job or system configuration other than Pipeline steps through th=
    e Pipeline Snippet Generator. 2026-06-24 not yet calculated CVE-2026-57283 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-57283 ] Jenkins Project--Jenk= ins Pipeline: Groovy Plugin Jenkins Pipeline: Groovy Plugin 4331.v9d06ed465= 8ff and earlier does not restrict the types that can be instantiated throug=
    h the Pipeline Snippet Generator, allowing attackers to instantiate types r= elated to job or system configuration other than Pipeline steps. 2026-06-24=
    not yet calculated CVE-2026-57284 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-57284 ] Jenkins Project--Jenkins Priority Sorter Plugin A cross-site = request forgery (CSRF) vulnerability in Jenkins Priority Sorter Plugin 936.= v2c01c6b_84449 and earlier allows attackers to overwrite the global job pri= ority configuration. 2026-06-24 not yet calculated CVE-2026-57290 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-57290 ] Jenkins Project--Jenkins Scrip=
    t Security Plugin Jenkins Script Security Plugin 1402.v94c9ce464861 and ear= lier does not intercept the implicit type casts applied to the elements of = typed for-each loops in sandboxed Groovy scripts, allowing attackers able t=
    o provide such scripts to invoke arbitrary constructors and bypass the sand= box protection. 2026-06-24 not yet calculated CVE-2026-57280 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-57280 ] Jenkins Project--Jenkins Script Sec= urity Plugin Jenkins Script Security Plugin 1402.v94c9ce464861 and earlier = does not reject Groovy AST transformation annotations carrying an extension=
    s member, allowing attackers able to run sandboxed Groovy scripts to execut=
    e code outside the sandbox if a suitable script is present on the classpath=
    of the component that evaluates the script. 2026-06-24 not yet calculated = CVE-2026-57281 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57281 ] Jenkin=
    s Project--Jenkins Zowe zDevOps Plugin A cross-site request forgery (CSRF) = vulnerability in Jenkins Zowe zDevOps Plugin 1.1.3.50.ve350c9b_450b_1 and e= arlier allows attackers to connect to an attacker-specified URL using attac= ker-specified credentials IDs obtained through another method, capturing cr= edentials stored in Jenkins. 2026-06-24 not yet calculated CVE-2026-57306 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-57306 ] Jenkins Project--Jenki=
    ns Zowe zDevOps Plugin A missing permission check in Jenkins Zowe zDevOps P= lugin 1.1.3.50.ve350c9b_450b_1 and earlier allows attackers with Overall/Re=
    ad permission to connect to an attacker-specified URL using attacker-specif= ied credentials IDs obtained through another method, capturing credentials = stored in Jenkins. 2026-06-24 not yet calculated CVE-2026-57307 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-57307 ] joomcoder.com--JoomCCK extension=
    for Joomla The Joomla extension JoomCCK exposes a front-end controller tas=
    k, that builds two SQL statements by directly concatenating a user-supplied=
    request parameter into the query string without escaping or parameterisati= on. 2026-06-28 not yet calculated CVE-2026-49048 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-49048 ] jqlang--jq jq is a command-line JSON processor.=
    Prior to 1.8.2, comparing two sufficiently deeply nested arrays with the = =3D=3D operator exhausts the C stack on jq's ordinary command-line surface,=
    resulting in denial of service via stack exhaustion (uncontrolled recursio= n). The crash occurs in jq's recursive structural comparison code, with the=
    recursion repeating through jvp_array_equal() and jv_equal() in src/jv.c w= hen comparing deeply nested arrays; a nearby sort comparator path through j= v_cmp() in src/jv_aux.c overflows the stack at a larger nesting depth from = the same missing recursion guard. Anyone running jq comparisons on attacker= -controlled deeply nested JSON values, or embedding jq in a context where u= ntrusted data can reach the =3D=3D comparison path, is affected. This vulne= rability is fixed in 1.8.2. 2026-06-25 not yet calculated CVE-2026-47770 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-47770 ] jqlang--jq jq is a comm= and-line JSON processor. Prior to 1.8.2, on 32bit system, jvp_string_append=
    has a chance of integer/multiple overflowing and then causing a massive bu= ffer overrun. This vulnerability is fixed in 1.8.2. 2026-06-25 not yet calc= ulated CVE-2026-54679 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54679 ]=
    jupyter--jupyter/jupyter A vulnerability in jupyter/nbconvert versions <=
    =3D 7.17.0 allows for Cross-site Scripting (XSS) via unsanitized `text/vnd.= mermaid` output in HTML exports. The `data_mermaid` block in `share/templat= es/lab/base.html.j2` renders `text/vnd.mermaid` cell output directly into H= TML without escaping, enabling attackers to inject arbitrary HTML/JavaScrip=
    t by breaking out of the `<pre>` tag. This vulnerability impacts any server=
    using nbconvert to render notebooks as HTML, allowing attackers to execute=
    arbitrary JavaScript in the context of users viewing the HTML export. 2026= -06-26 not yet calculated CVE-2026-6658 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-6658 ] jupyter-server--jupyter_server Jupyter Server is the bac= kend for Jupyter web applications. Prior to 2.20, the nbconvert HTTP handle=
    rs in jupyter_server render user-authored notebook HTML under the Jupyter o= rigin without a sandbox directive in their Content-Security-Policy. Combine=
    d with nbconvert.HTMLExporter's default non-sanitizing behavior, a notebook=
    carrying an HTML payload in a display_data output triggers stored XSS with=
    cookie access, full /api/* authority, and kernel RCE. This vulnerability i=
    s fixed in 2.20. 2026-06-22 not yet calculated CVE-2026-44727 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-44727 ] keras-team--keras-team/keras A pat=
    h traversal vulnerability exists in keras-team/keras version 3.14.0, specif= ically in the `DiskIOStore.make` method within the Keras 3 model saving and=
    loading library. This vulnerability arises from the improper handling of u= ser-provided layer names, which are used to construct directory paths witho=
    ut sanitizing for parent directory components (`..`). While forward slashes=
    (`/`) are restricted in layer names, directory traversal sequences are not=
    . This allows an attacker to craft a malicious Keras model that, when saved=
    or loaded, can escape the intended temporary working directory and perform=
    unauthorized file system operations, such as creating directories or writi=
    ng files in arbitrary locations. 2026-06-22 not yet calculated CVE-2026-124=
    79 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12479 ] Koha--Library Mana= gement System Cross-Site Scripting (XSS) vulnerability in the patron restri= ction type administration page of Koha Library Management System through 25= .11 allows an authenticated remote attacker with administrator privileges t=
    o inject arbitrary web scripts via the restriction type label (display_text=
    field) 2026-06-26 not yet calculated CVE-2026-50765 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-50765 ] Koha--Library Management System A stored cr= oss-site scripting (XSS) vulnerability in the OPAC item detail page of Koha=
    Library Management System through 25.11 allows an authenticated remote att= acker with edit_items permission to inject arbitrary web scripts via the it=
    em public notes field (items.itemnotes). 2026-06-26 not yet calculated CVE-= 2026-50766 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50766 ] Koha--Libr= ary Management System A stored cross-site scripting (XSS) vulnerability in = the item type administration page of Koha Library Management System through=
    25.11 allows an authenticated remote attacker with administrator privilege=
    s to inject arbitrary web scripts via the item type check-in message field = (checkinmsg) 2026-06-26 not yet calculated CVE-2026-50767 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-50767 ] Lansweeper--lsrunase 2.0/lsencrypt 2.0=
    Lansweeper lsrunase 2.0 and lsencrypt 2.0 use RC4 encryption with a hardco= ded 142-byte static key array to encrypt credentials. An 8-character prefix=
    is stored in cleartext alongside the ciphertext. This allows an attacker w= ith local access to recover any encrypted password to plaintext using a sin= gle SHA-1 hash and RC4 decryption operation, with no brute force required. = 2026-06-26 not yet calculated CVE-2026-39031 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-39031 ] lepture--mistune Mistune is a Python Markdown parse=
    r with renderers and plugins. Prior to 3.3.0, Mistune is vulnerable to a CP=
    U exhaustion DoS due to superlinear (approximately O(n=C3=82=C2=B2)) behavi=
    or in parse_link_text. When parsing Markdown containing many consecutive [ = characters, parse_link_text repeatedly scans the input using a regex search=
    inside a loop. Each iteration re-scans a large portion of the remaining st= ring, resulting in quadratic-time behavior. An attacker-controlled Markdown=
    input can therefore trigger excessive CPU usage with a very small payload.=
    This vulnerability is fixed in 3.3.0. 2026-06-24 not yet calculated CVE-20= 26-49851 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49851 ] Linux--Linux=
    In the Linux kernel, the following vulnerability has been resolved: batman= -adv: v: stop OGMv2 on disabled interface When a batadv_hard_iface is disab= led, its mesh_iface pointer is set to NULL. However, batadv_v_ogm_send_mesh= if() may still dispatch OGMs via batadv_v_ogm_queue_on_if() for interfaces = that have since lost their mesh_iface association. This results in a NULL p= ointer dereference when batadv_v_ogm_queue_on_if() unconditionally calls ne= tdev_priv() on the now NULL hard_iface->mesh_iface to retrieve the batadv_p= riv. It is necessary to ensure that the batadv_v_ogm_queue_on_if() checks t= hat it is using the same mesh_iface for which batadv_v_ogm_send_meshif() wa=
    s called. 2026-06-24 not yet calculated CVE-2026-52913 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-52913 ] Linux--Linux In the Linux kernel, the fol= lowing vulnerability has been resolved: batman-adv: frag: disallow unicast = fragment in fragment batadv_frag_skb_buffer() is called by batadv_batman_sk= b_recv() when a BATADV_UNICAST_FRAG packet is received. Once all fragments = are collected and the packet is reassembled, batadv_recv_frag_packet() call=
    s batadv_batman_skb_recv() again to process the defragmented payload. A mal= icious sender can craft a BATADV_UNICAST_FRAG packet whose reassembled payl= oad is itself a BATADV_UNICAST_FRAG packet (matryoshka-style nesting). Each=
    nesting level recurses through batadv_batman_skb_recv() without bound, gro= wing the kernel stack until it is exhausted. Since refragmentation or fragm= ents in fragments are not actually allowed, discard all packets which are s= till BATADV_UNICAST_FRAG packets after the defragmentation process. 2026-06= -24 not yet calculated CVE-2026-52916 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-52916 ] Linux--Linux In the Linux kernel, the following vulnerabil= ity has been resolved: netfilter: ipset: stop hash:* range iteration at end=
    The following hash set variants: hash:ip,mark hash:ip,port hash:ip,port,ip=
    hash:ip,port,net iterate IPv4 ranges with a 32-bit iterator. The iterator = must stop once the last address in the requested range has been processed. = Advancing it once more can move the traversal state past the end of the req= uest, so a later retry may continue from an unintended position. Handle the=
    iterator increment explicitly at the end of the loop and stop once the upp=
    er bound has been processed. This keeps the existing retry behaviour intact=
    for valid ranges while preventing traversal from continuing past the origi= nal boundary. 2026-06-24 not yet calculated CVE-2026-52921 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-52921 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: vrf: Fix a potential NPD when r= emoving a port from a VRF RCU readers that identified a net device as a VRF=
    port using netif_is_l3_slave() assume that a subsequent call to netdev_mas= ter_upper_dev_get_rcu() will return a VRF device. They then continue to der= eference its l3mdev operations. This assumption is not always correct and c=
    an result in a NPD [1]. There is no RCU synchronization when removing a por=
    t from a VRF, so it is possible for an RCU reader to see a new master devic=
    e (e.g., a bridge) that does not have l3mdev operations. Fix by adding RCU = synchronization after clearing the IFF_L3MDEV_SLAVE flag. Skip this synchro= nization when a net device is removed from a VRF as part of its deletion an=
    d when the VRF device itself is deleted. In the latter case an RCU grace pe= riod will pass by the time RTNL is released. [1] BUG: kernel NULL pointer d= ereference, address: 0000000000000000 [...] RIP: 0010:l3mdev_fib_table_rcu = (net/l3mdev/l3mdev.c:181) [...] Call Trace: <TASK> l3mdev_fib_table_by_inde=
    x (net/l3mdev/l3mdev.c:201 net/l3mdev/l3mdev.c:189) __inet_bind (net/ipv4/a= f_inet.c:499 (discriminator 3)) inet_bind_sk (net/ipv4/af_inet.c:469) __sys= _bind (./include/linux/file.h:62 (discriminator 1) ./include/linux/file.h:8=
    3 (discriminator 1) net/socket.c:1951 (discriminator 1)) __x64_sys_bind (ne= t/socket.c:1969 (discriminator 1) net/socket.c:1967 (discriminator 1) net/s= ocket.c:1967 (discriminator 1)) do_syscall_64 (arch/x86/entry/syscall_64.c:=
    63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1)) entr= y_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) 2026-06-24 not y=
    et calculated CVE-2026-52925 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 52925 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: batman-adv: clear current gateway during teardown batadv_gw_n= ode_free() removes the gateway list entries during mesh teardown, but it do=
    es not clear the currently selected gateway. This leaves stale gateway stat=
    e behind across cleanup and can break a later mesh recreation. Clear bat_pr= iv->gw.curr_gw before walking the gateway list so the selected gateway refe= rence is dropped as part of teardown. 2026-06-24 not yet calculated CVE-202= 6-52926 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52926 ] Linux--Linux =
    In the Linux kernel, the following vulnerability has been resolved: af_unix=
    : Reject SIOCATMARK on non-stream sockets SIOCATMARK reports whether the re= ceive queue is at the urgent mark for MSG_OOB. In AF_UNIX, MSG_OOB is suppo= rted only for SOCK_STREAM sockets. SOCK_DGRAM and SOCK_SEQPACKET reject MSG= _OOB in sendmsg() and recvmsg(), so they should not support SIOCATMARK eith= er. Return -EOPNOTSUPP for non-stream sockets before checking the receive q= ueue. 2026-06-24 not yet calculated CVE-2026-52928 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-52928 ] Linux--Linux In the Linux kernel, the followi=
    ng vulnerability has been resolved: ipc/shm: serialize orphan cleanup with = shm_nattch updates shm_destroy_orphaned() walks the shm idr under shm_ids(n= s).rwsem, but that does not serialize all fields tested by shm_may_destroy(=
    ). In particular, shm_nattch is updated while holding shm_perm.lock, and at= tach paths can do that without holding the rwsem. Do not decide that an orp= haned segment is unused before taking the object lock. Move the shm_may_des= troy() check under shm_perm.lock, matching the other destroy paths, and unl= ock the segment when it no longer qualifies for removal. 2026-06-24 not yet=
    calculated CVE-2026-52930 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52= 930 ] Linux--Linux In the Linux kernel, the following vulnerability has bee=
    n resolved: crypto: jitterentropy - replace long-held spinlock with mutex j= ent_kcapi_random() serializes the shared jitterentropy state, but it curren= tly holds a spinlock across the jent_read_entropy() call. That path perform=
    s expensive jitter collection and SHA3 conditioning, so parallel readers ca=
    n trigger stalls as contending waiters spin for the same lock. To prevent n= on-preemptible lock hold, replace rng->jent_lock with a mutex so contended = readers sleep instead of spinning on a shared lock held across expensive en= tropy generation. 2026-06-24 not yet calculated CVE-2026-52936 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-52936 ] Linux--Linux In the Linux kernel,=
    the following vulnerability has been resolved: tap: fix stack info leak in=
    tap_ioctl() SIOCGIFHWADDR In the SIOCGIFHWADDR path, tap_ioctl() copies 16=
    bytes of an uninitialised on-stack struct sockaddr_storage to userspace vi=
    a ifr_hwaddr, but netif_get_mac_address() only writes sa_family and dev->ad= dr_len (6 for Ethernet) bytes, leaving sa_data[6..13] uninitialised. Those =
    8 trailing bytes leak kernel stack contents; SIOCGIFHWADDR on a macvtap cha= rdev returns kernel .text and direct-map pointers, defeating KASLR. Initial= ise ss at declaration. 2026-06-24 not yet calculated CVE-2026-52937 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-52937 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: bpf: Fix NULL pointer = dereference in bpf_sk_storage_clone and diag paths bpf_selem_unlink_nofail(=
    ) sets SDATA(selem)->smap to NULL before removing the selem from the storag=
    e hlist. A concurrent RCU reader in bpf_sk_storage_clone() can observe the = selem still on the list with smap already NULL, causing a NULL pointer dere= ference. general protection fault, probably for non-canonical address 0xdff= ffc000000000a: KASAN: null-ptr-deref in range [0x0000000000000050-0x0000000= 000000057] RIP: 0010:bpf_sk_storage_clone+0x1cd/0xaa0 net/core/bpf_sk_stora= ge.c:174 Call Trace: <IRQ> sk_clone+0xfed/0x1980 net/core/sock.c:2591 inet_= csk_clone_lock+0x30/0x760 net/ipv4/inet_connection_sock.c:1222 tcp_create_o= penreq_child+0x35/0x2680 net/ipv4/tcp_minisocks.c:571 tcp_v4_syn_recv_sock+= 0x123/0xf90 net/ipv4/tcp_ipv4.c:1729 tcp_check_req+0x8e1/0x2580 include/net= /tcp.h:855 tcp_v4_rcv+0x1845/0x3b80 net/ipv4/tcp_ipv4.c:2347 Add a NULL che=
    ck for smap in bpf_sk_storage_clone(). bpf_sk_storage_diag_put_all() has th=
    e same issue. Add a NULL check and pass the validated smap directly to diag= _get(), which is refactored to take smap as a parameter instead of reading =
    it internally. bpf_sk_storage_diag_put() uses diag->maps[i] which is always=
    valid under its refcount, so diag->maps[i] is passed directly to diag_get(=
    ). 2026-06-24 not yet calculated CVE-2026-52938 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-52938 ] Linux--Linux In the Linux kernel, the following = vulnerability has been resolved: net/rds: fix NULL deref in rds_ib_send_cqe= _handler() on masked atomic completion rds_ib_xmit_atomic() always programs=
    a masked atomic opcode (IB_WR_MASKED_ATOMIC_CMP_AND_SWP or IB_WR_MASKED_AT= OMIC_FETCH_AND_ADD) for every RDS atomic cmsg. But the completion-side swit=
    ch in rds_ib_send_unmap_op() only handles the non-masked opcodes, so a mask=
    ed atomic completion falls through to default and returns rm =3D=3D NULL wh= ile send->s_op is left set. rds_ib_send_cqe_handler() then dereferences the=
    NULL rm via rm->m_final_op, oopsing in softirq context. An unprivileged AF= _RDS sendmsg() of an atomic cmsg over an active RDS/IB connection triggers = it; on hardware that natively accepts masked atomics (mlx4, mlx5) no extra = setup is needed. RDS/IB: rds_ib_send_unmap_op: unexpected opcode 0xd in WR!=
    Oops: general protection fault [#1] SMP KASAN KASAN: null-ptr-deref in ran=
    ge [0x0000000000000190-0x0000000000000197] RIP: rds_ib_send_cqe_handler+0x2= 5c/0xb10 (net/rds/ib_send.c:282) Call Trace: <IRQ> rds_ib_send_cqe_handler = (net/rds/ib_send.c:282) poll_scq (net/rds/ib_cm.c:274) rds_ib_tasklet_fn_se=
    nd (net/rds/ib_cm.c:294) tasklet_action_common (kernel/softirq.c:943) handl= e_softirqs (kernel/softirq.c:573) run_ksoftirqd (kernel/softirq.c:479) </IR=
    Kernel panic - not syncing: Fatal exception in interrupt Handle the mask=
    ed atomic opcodes in the same case as the non-masked ones: they map to the = same struct rds_message.atomic union member, so the existing container_of()= /rds_ib_send_unmap_atomic() body is correct for them. 2026-06-24 not yet ca= lculated CVE-2026-52939 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52939=
    ] Linux--Linux In the Linux kernel, the following vulnerability has been r= esolved: tun: zero the whole vnet header in tun_put_user() tun_put_user() d= eclares an on-stack struct virtio_net_hdr_v1_hash_tunnel without zeroing it=
    . For a non-tunnel skb, virtio_net_hdr_tnl_from_skb() only initializes the = first 10 bytes (sizeof(struct virtio_net_hdr)), leaving bytes 10..23 (num_b= uffers and the hash/tunnel fields) as stack garbage. An unprivileged user c=
    an set the vnet header size to 24 with TUNSETVNETHDRSZ, so __tun_vnet_hdr_p= ut() copies all 24 bytes of the partially-initialized struct to userspace, = leaking 14 bytes of kernel stack on every read of a non-tunnel packet. Fix =
    it the same way tun_get_user() already does by zeroing the whole header rig=
    ht after declaration. 2026-06-24 not yet calculated CVE-2026-52940 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-52940 ] Linux--Linux In the Linux ker= nel, the following vulnerability has been resolved: net/smc: avoid NULL der=
    ef of conn->lnk in smc_msg_event tracepoint The smc_msg_event tracepoint cl= ass, shared by smc_tx_sendmsg and smc_rx_recvmsg, unconditionally dereferen= ces smc->conn.lnk: __string(name, smc->conn.lnk->ibname) conn->lnk is only = set for SMC-R; for SMC-D it is NULL. Other code on these paths already hand= les this (e.g. !conn->lnk in SMC_STAT_RMB_TX_SIZE_SMALL()). With the tracep= oint enabled, the first sendmsg()/recvmsg() on an SMC-D socket crashes: Oop=
    s: general protection fault, probably for non-canonical address KASAN: null= -ptr-deref in range [...] RIP: 0010:strlen+0x1e/0xa0 Call Trace: trace_even= t_raw_event_smc_msg_event (net/smc/smc_tracepoint.h:44) smc_rx_recvmsg (net= /smc/smc_rx.c:515) smc_recvmsg (net/smc/af_smc.c:2859) __sys_recvfrom (net/= socket.c:2315) __x64_sys_recvfrom (net/socket.c:2326) do_syscall_64 The fau= lting address 0x3e0 is offsetof(struct smc_link, ibname), confirming the NU=
    LL ->lnk deref. Enabling the tracepoint requires root, but the trigger itse=
    lf is unprivileged: socket(AF_SMC, ...) has no capability check, and SMC-D = negotiation needs no admin step on s390 or on x86 with the loopback ISM dev= ice loaded. Log an empty device name for SMC-D instead of dereferencing NUL=
    L. 2026-06-24 not yet calculated CVE-2026-52941 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-52941 ] Linux--Linux In the Linux kernel, the following = vulnerability has been resolved: ksmbd: fix FSCTL permission bypass by addi=
    ng a permission check for FSCTL_SET_SPARSE FSCTL_SET_SPARSE in fsctl_set_sp= arse() modifies the file's sparse attribute and saves it through xattr with= out any permission checks. This exposes two issues: 1) A client on a read-o= nly share can change the sparse attribute on files it opened, even though t=
    he share is read-only. Other FSCTL write operations already check test_tree= _conn_flag(work->tcon, KSMBD_TREE_CONN_FLAG_WRITABLE), but FSCTL_SET_SPARSE=
    does not. 2) Even on writable shares, clients without FILE_WRITE_DATA or F= ILE_WRITE_ATTRIBUTES access should not modify the sparse attribute. Similar=
    handle-level checks exist in other functions but are missing here. Add bot=
    h share-level writable check and per-handle access check. Use goto out on e= rror to avoid leaking file references. 2026-06-24 not yet calculated CVE-20= 26-52944 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52944 ] Linux--Linux=
    In the Linux kernel, the following vulnerability has been resolved: i2c: d= ev: prevent integer overflow in I2C_TIMEOUT ioctl While fuzzing with Syzkal= ler, a persistent `schedule_timeout: wrong timeout value` warning was obser= ved, accompanied by SMBus controller state machine corruption. The I2C_TIME= OUT ioctl accepts a user-provided timeout in multiples of 10 ms. The user a= rgument is checked against INT_MAX, but it is subsequently multiplied by 10=
    before being passed to msecs_to_jiffies(). A malicious user can pass a lar=
    ge value (e.g., 429496729) that passes the `arg > INT_MAX` check but overfl= ows when multiplied by 10. This results in a truncated 32-bit unsigned valu=
    e that bypasses the internal `(int)m < 0` check in `msecs_to_jiffies()`. Th=
    e truncated value is then assigned to `client->adapter->timeout` (a signed = 32-bit int), which is reinterpreted as a negative number. When passed to wa= it_for_completion_timeout(), this negative value undergoes sign extension t=
    o a 64-bit unsigned long, triggering the `schedule_timeout` warning and cau= sing premature returns. This leaves the SMBus state machine in an unrecover= able state, constituting a local Denial of Service (DoS). Fix this by bound= ing the user argument to `INT_MAX / 10`. [wsa: move the comment as well] 20= 26-06-24 not yet calculated CVE-2026-52948 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-52948 ] Linux--Linux In the Linux kernel, the following vulne= rability has been resolved: drm/ttm: Fix ttm_bo_shrink() infinite LRU walk =
    on backup failure Apply the same fix as b2ed01e7ad ("drm/ttm: Fix ttm_bo_sw= apout() infinite LRU walk on swapout failure") to the ttm_bo_shrink() path.=
    Move del_bulk_move from before the backup to after success only, using ttm= _resource_del_bulk_move_unevictable() since the resource is now unevictable=
    once fully backed up. 2026-06-24 not yet calculated CVE-2026-52949 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-52949 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: ceph: fix BUG_ON in __= ceph_build_xattrs_blob() due to stale blob size The generic/642 test-case c=
    an reproduce the kernel crash: [40243.605254] ------------[ cut here ]-----= ------- [40243.605956] kernel BUG at fs/ceph/xattr.c:918! [40243.607142] Oo= ps: invalid opcode: 0000 [#1] SMP PTI [40243.608067] CPU: 7 UID: 0 PID: 498= 762 Comm: kworker/7:1 Not tainted 7.0.0-rc7+ #3 PREEMPT(full) [40243.609700=
    ] Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX, + 10.1 machine, 19= 96), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [40243.611820] Workqueue: ceph-= msgr ceph_con_workfn [40243.612715] RIP: 0010:__ceph_build_xattrs_blob+0x1b= 8/0x1e0 [40243.613731] Code: 0f 84 82 fe ff ff e9 cf 8e 56 ff 48 8d 65 e8 3=
    1 c0 5b 41 5c 41 5d 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 c3 cc cc c=
    c cc <0f> 0b 4c 8b 62 08 41 8b 85 24 07 00 00 49 83 c4 04 41 89 44 24 fc [4= 0243.616888] RSP: 0018:ffffcc80c4d4b688 EFLAGS: 00010287 [40243.617773] RAX=
    : 0000000000010026 RBX: 0000000000000001 RCX: 0000000000000000 [40243.61892=
    8] RDX: ffff8a773798dee0 RSI: 0000000000000000 RDI: 0000000000000000 [40243= .620158] RBP: ffffcc80c4d4b6a0 R08: 0000000000000000 R09: 0000000000000000 = [40243.621573] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8a75f3b= 58000 [40243.622907] R13: ffff8a75f3b58000 R14: 0000000000000080 R15: 00000= 0000000bffd [40243.624054] FS: 0000000000000000(0000) GS:ffff8a787d1b4000(0= 000) knlGS:0000000000000000 [40243.625331] CS: 0010 DS: 0000 ES: 0000 CR0: = 0000000080050033 [40243.626269] CR2: 000072f390b623c0 CR3: 000000011c02a003=
    CR4: 0000000000372ef0 [40243.627408] Call Trace: [40243.627839] <TASK> [40= 243.628188] __prep_cap+0x3fd/0x4a0 [40243.628789] ? do_raw_spin_unlock+0x4e= /0xe0 [40243.629474] ceph_check_caps+0x46a/0xc80 [40243.630094] ? __lock_ac= quire+0x4a2/0x2650 [40243.630773] ? find_held_lock+0x31/0x90 [40243.631347]=
    ? handle_cap_grant+0x79f/0x1060 [40243.632068] ? lock_release+0xd9/0x300 [= 40243.632696] ? __mutex_unlock_slowpath+0x3e/0x340 [40243.633429] ? lock_re= lease+0xd9/0x300 [40243.634052] handle_cap_grant+0xcf6/0x1060 [40243.634745=
    ] ceph_handle_caps+0x122b/0x2110 [40243.635415] mds_dispatch+0x5bd/0x2160 [= 40243.636034] ? ceph_con_process_message+0x65/0x190 [40243.636828] ? lock_r= elease+0xd9/0x300 [40243.637431] ceph_con_process_message+0x7a/0x190 [40243= .638184] ? kfree+0x311/0x4f0 [40243.638749] ? kfree+0x311/0x4f0 [40243.6392= 68] process_message+0x16/0x1a0 [40243.639915] ? sg_free_table+0x39/0x90 [40= 243.640572] ceph_con_v2_try_read+0xf58/0x2120 [40243.641255] ? lock_acquire= +0xc8/0x300 [40243.641863] ceph_con_workfn+0x151/0x820 [40243.642493] proce= ss_one_work+0x22f/0x630 [40243.643093] ? process_one_work+0x254/0x630 [4024= 3.643770] worker_thread+0x1e2/0x400 [40243.644332] ? __pfx_worker_thread+0x= 10/0x10 [40243.645020] kthread+0x109/0x140 [40243.645560] ? __pfx_kthread+0= x10/0x10 [40243.646125] ret_from_fork+0x3f8/0x480 [40243.646752] ? __pfx_kt= hread+0x10/0x10 [40243.647316] ? __pfx_kthread+0x10/0x10 [40243.647919] ret= _from_fork_asm+0x1a/0x30 [40243.648556] </TASK> [40243.648902] Modules link=
    ed in: overlay hctr2 libpolyval chacha libchacha adiantum libnh libpoly1305=
    essiv intel_rapl_msr intel_rapl_common intel_uncore_frequency_common skx_e= dac_common nfit kvm_intel kvm irqbypass joydev ghash_clmulni_intel aesni_in= tel rapl input_leds mac_hid psmouse vga16fb serio_raw vgastate floppy i2c_p= iix4 pata_acpi bochs qemu_fw_cfg i2c_smbus sch_fq_codel rbd dm_crypt msr pa= rport_pc ppdev lp parport efi_pstore [40243.654766] ---[ end trace 00000000= 00000000 ]--- Commit d93231a6bc8a ("ceph: prevent a client from exceeding t=
    he MDS maximum xattr size") moved the required_blob_size computation to bef= ore the __build_xattrs() call, introducing a race. __build_xattrs() release=
    s and reacquires i_ceph_lock during execution. In that window, handle_cap_g= rant() may update i_xattrs.blob with a newer MDS-provided blob and bump i_x= attrs.version. When __bui ---truncated--- 2026-06-24 not yet calculated CVE= -2026-52961 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52961 ] Linux--Li= nux In the Linux kernel, the following vulnerability has been resolved: cep=
    h: fix a buffer leak in __ceph_setxattr() The old_blob in __ceph_setxattr()=
    can store ci->i_xattrs.prealloc_blob value during the retry. However, it i=
    s never called the ceph_buffer_put() for the old_blob object. This patch fi= xes the issue of the buffer leak. 2026-06-24 not yet calculated CVE-2026-52= 962 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52962 ] Linux--Linux In t=
    he Linux kernel, the following vulnerability has been resolved: ALSA: usb-a= udio: Bound MIDI endpoint descriptor scans snd_usbmidi_get_ms_info() valida= tes the internal MIDIStreaming endpoint descriptor size before using baAsso= cJackID[], but the descriptor walker can still return a class-specific endp= oint descriptor whose bLength exceeds the remaining bytes in the endpoint-e= xtra scan. That leaves later flexible-array reads bounded by bLength, but n=
    ot by the remaining bytes in the endpoint-extra scan. Stop walking when bLe= ngth is zero or extends past the remaining endpoint-extra scan. 2026-06-24 = not yet calculated CVE-2026-52963 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-52963 ] Linux--Linux In the Linux kernel, the following vulnerability = has been resolved: ALSA: usb-audio: Bound MIDI 2.0 endpoint descriptor scan=
    s The USB MIDI 2.0 endpoint parser has the same descriptor walking pattern =
    as the legacy MIDI parser. It validates bLength against bNumGrpTrmBlock bef= ore reading baAssoGrpTrmBlkID[], but not against the remaining bytes in the=
    endpoint-extra scan. A malformed device can therefore make later baAssoGrp= TrmBlkID[] reads consume bytes past the walked descriptor. Reject zero-leng=
    th and overlong descriptors while walking endpoint extras. 2026-06-24 not y=
    et calculated CVE-2026-52964 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 52964 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout fa= ilure When ttm_tt_swapout() fails, the current code calls ttm_resource_add_= bulk_move() followed by ttm_resource_move_to_lru_tail() to restore the reso= urce's bulk_move membership. However, ttm_resource_move_to_lru_tail() place=
    s the resource at the tail of the LRU list which, relative to the walk curs= or's hitch node (placed immediately after the resource when it was yielded)=
    , puts the resource *in front of the* the hitch. The next list_for_each_ent= ry_continue() from the hitch finds the same resource again, causing an infi= nite loop. Fix by deferring del_bulk_move to the success path only. On the = success path, TTM_TT_FLAG_SWAPPED has just been set by ttm_tt_swapout() but=
    the resource is still tracked in the bulk_move range, so ttm_resource_del_= bulk_move()'s !ttm_resource_unevictable() guard would incorrectly skip the = removal. Introduce ttm_resource_del_bulk_move_unevictable() which bypasses = that guard. 2026-06-24 not yet calculated CVE-2026-52965 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-52965 ] Linux--Linux In the Linux kernel, the f= ollowing vulnerability has been resolved: drm: Replace old pointer to new i=
    dr Commit 5e28b7b94408 introduced a logical error by failing to replace the=
    newly generated IDR pointer to old id's pointer at the correct location wi= thin the "change handle" logic; this resulted in the issue reported by syzb=
    ot [1]. Specifically, the new IDR object pointer is intended to replace the=
    original id's pointer during the normal execution flow. Additionally, an u= nnecessary conditional check for the ret exit path has been removed. [1] !R= B_EMPTY_ROOT(&prime_fpriv->dmabufs) WARNING: drivers/gpu/drm/drm_prime.c:22=
    4 at drm_prime_destroy_file_private+0x48/0x60 drivers/gpu/drm/drm_prime.c:2= 24, CPU#0: syz.0.17/5833 Call Trace: drm_file_free.part.0+0x7e6/0xcc0 drive= rs/gpu/drm/drm_file.c:269 drm_file_free drivers/gpu/drm/drm_file.c:237 [inl= ine] drm_close_helper.isra.0+0x186/0x200 drivers/gpu/drm/drm_file.c:290 drm= _release+0x1ab/0x360 drivers/gpu/drm/drm_file.c:438 2026-06-24 not yet calc= ulated CVE-2026-52966 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52966 ]=
    Linux--Linux In the Linux kernel, the following vulnerability has been res= olved: KVM: s390: pci: fix GAIT table indexing due to double-scaling pointe=
    r arithmetic kvm_s390_pci_aif_enable(), kvm_s390_pci_aif_disable(), and aen= _host_forward() index the GAIT by manually multiplying the index with sizeo= f(struct zpci_gaite). Since aift->gait is already a struct zpci_gaite point= er, this double-scales the offset, accessing element aisb*16 instead of ais=
    b. This causes out-of-bounds accesses when aisb >=3D 32 (with ZPCI_NR_DEVIC= ES=3D512) Fix by removing the erroneous sizeof multiplication. 2026-06-24 n=
    ot yet calculated CVE-2026-52968 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-52968 ] Linux--Linux In the Linux kernel, the following vulnerability h=
    as been resolved: KVM: Reject wrapped offset in kvm_reset_dirty_gfn() kvm_r= eset_dirty_gfn() guards the gfn range with if (!memslot || (offset + __fls(= mask)) >=3D memslot->npages) return; but offset is u64 and the addition is = unchecked. The check can be silently bypassed by a u64 wrap. The dirty ring=
    backing those entries is MAP_SHARED at KVM_DIRTY_LOG_PAGE_OFFSET of the vc=
    pu fd, so the VMM can rewrite the slot and offset fields of any entry betwe=
    en when the kernel pushes them and when KVM_RESET_DIRTY_RINGS consumes them=
    . On reset, kvm_dirty_ring_reset() re-reads the values via READ_ONCE() and = feeds them straight back into this check; only the flags handshake is treat=
    ed as the handover, the slot/offset payload is taken on trust. Crafting two=
    entries entry[i].offset =3D 0xffffffffffffffc1 entry[i+1].offset =3D 0 mak=
    es the coalescing loop in kvm_dirty_ring_reset() compute delta =3D (s64)(0 =
    - 0xffffffffffffffc1) =3D 63 which falls in [0, BITS_PER_LONG), so it folds=
    entry[i+1] into the existing mask by setting bit 63. The trailing kvm_rese= t_dirty_gfn() call then sees offset =3D 0xffffffffffffffc1 and __fls(mask) = =3D 63; the sum is 0 in u64 and the bounds check passes. That offset propag= ates into kvm_arch_mmu_enable_log_dirty_pt_masked() unchanged. On the legac=
    y MMU path -- kvm_memslots_have_rmaps() =3D=3D true, i.e. shadow paging, an=
    y VM that has allocated shadow roots, or a write-tracked slot -- it reaches=
    gfn_to_rmap(), which indexes slot->arch.rmap[0][] with a near-U64_MAX gfn.=
    That is an out-of-bounds load of a kvm_rmap_head, followed by a conditiona=
    l clear of PT_WRITABLE_MASK in whatever the loaded pointer points at. The p= ath is reachable from any process holding /dev/kvm. Range-check offset on i=
    ts own first, so the addition cannot wrap. memslot->npages is bounded well = below U64_MAX, so once offset < npages holds, offset + __fls(mask) (with __= fls(mask) < BITS_PER_LONG) stays in range. 2026-06-24 not yet calculated CV= E-2026-52969 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52969 ] Linux--L= inux In the Linux kernel, the following vulnerability has been resolved: ne= tfilter: nft_ct: fix missing expect put in obj eval nft_ct_expect_obj_eval(=
    ) allocates an expectation and may call nf_ct_expect_related(), but never d= rops its local reference. Add nf_ct_expect_put(exp) before return to balanc=
    e allocation. 2026-06-24 not yet calculated CVE-2026-52970 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-52970 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: crypto: af_alg - Cap AEAD AD le= ngth to 0x80000000 In order to prevent arithmetic overflows when checking t=
    he TX buffer size, cap the associated data length to 0x80000000. 2026-06-24=
    not yet calculated CVE-2026-52972 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-52972 ] Linux--Linux In the Linux kernel, the following vulnerability=
    has been resolved: futex: Prevent lockup in requeue-PI during signal/ time= out wakeup During wait-requeue-pi (task A) and requeue-PI (task B) the foll= owing race can happen: Task A Task B futex_wait_requeue_pi() futex_setup_ti= mer() futex_do_wait() futex_requeue() CLASS(hb, hb1)(&key1); CLASS(hb, hb2)= (&key2); *timeout* futex_requeue_pi_wakeup_sync() requeue_state =3D Q_REQUE= UE_PI_IGNORE *blocks on hb->lock* futex_proxy_trylock_atomic() futex_requeu= e_pi_prepare() Q_REQUEUE_PI_IGNORE =3D> -EAGAIN double_unlock_hb(hb1, hb2) = *retry* Task B acquires both hb locks and attempts to acquire the PI-lock o=
    f the top most waiter (task B). Task A is leaving early due to a signal/ ti= meout and started removing itself from the queue. It updates its requeue_st= ate but can not remove it from the list because this requires the hb lock w= hich is owned by task B. Usually task A is able to swoop the lock after tas=
    k B unlocked it. However if task B is of higher priority then task A may no=
    t be able to wake up in time and acquire the lock before task B gets it aga= in. Especially on a UP system where A is never scheduled. As a result task =
    A blocks on the lock and task B busy loops, trying to make progress but liv=
    e locks the system instead. Tragic. This can be fixed by removing the top m= ost waiter from the list in this case. This allows task B to grab the next = top waiter (if any) in the next iteration and make progress. Remove the top=
    most waiter if futex_requeue_pi_prepare() fails. Let the waiter conditiona= lly remove itself from the list in handle_early_requeue_pi_wakeup(). 2026-0= 6-24 not yet calculated CVE-2026-52977 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-52977 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: net: psp: require admin permission for dev-set an=
    d key-rotate The dev-set and key-rotate netlink operations modify shared de= vice state (PSP version configuration and cryptographic key material, respe= ctively) but do not require CAP_NET_ADMIN. The only access control is psp_d= ev_check_access() which merely verifies netns membership. 2026-06-24 not ye=
    t calculated CVE-2026-52978 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 2978 ] Linux--Linux In the Linux kernel, the following vulnerability has be=
    en resolved: net: psp: check for device unregister when creating assoc psp_= assoc_device_get_locked() obtains a psp_dev reference via psp_dev_get_for_s= ock() (which uses psp_dev_tryget() under RCU); it then acquires psd->lock a=
    nd drops the reference. Before the lock is taken, psp_dev_unregister() can = run to completion: take psd->lock, clear out state, unlock, drop the regist= ration reference. The expectation is that the lock prevents device unregist= ration, but much like with netdevs special care has to be taken when "upgra= ding" a reference to a locked device. Add the missing check if device is st= ill alive. psp_dev_is_registered() exists already but had no callers, which=
    makes me wonder if I either forgot to add this or lost the check during re= factoring... 2026-06-24 not yet calculated CVE-2026-52979 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-52979 ] Linux--Linux In the Linux kernel, the = following vulnerability has been resolved: sched/fair: Clear rel_deadline w= hen initializing forked entities A yield-triggered crash can happen when a = newly forked sched_entity enters the fair class with se->rel_deadline unexp= ectedly set. The failing sequence is: 1. A task is forked while se->rel_dea= dline is still set. 2. __sched_fork() initializes vruntime, vlag and other = sched_entity state, but does not clear rel_deadline. 3. On the first enqueu=
    e, enqueue_entity() calls place_entity(). 4. Because se->rel_deadline is se=
    t, place_entity() treats se->deadline as a relative deadline and converts i=
    t to an absolute deadline by adding the current vruntime. 5. However, the f= orked entity's deadline is not a valid inherited relative deadline for this=
    new scheduling instance, so the conversion produces an abnormally large de= adline. 6. If the task later calls sched_yield(), yield_task_fair() advance=
    s se->vruntime to se->deadline. 7. The inflated vruntime is then used by th=
    e following enqueue path, where the vruntime-derived key can overflow when = multiplied by the entity weight. 8. This corrupts cfs_rq->sum_w_vruntime, b= reaks EEVDF eligibility calculation, and can eventually make all entities a= ppear ineligible. pick_next_entity() may then return NULL unexpectedly, lea= ding to a later NULL dereference. A captured trace shows the effect clearly=
    . Before yield, the entity's vruntime was around: 9834017729983308 After yi= eld_task_fair() executed: se->vruntime =3D se->deadline the vruntime jumped=
    to: 19668035460670230 and the deadline was later advanced further to: 1966= 8035463470230 This shows that the deadline had already become abnormally la= rge before yield_task_fair() copied it into vruntime. rel_deadline is only = meaningful when se->deadline really carries a relative deadline that still = needs to be placed against vruntime. A freshly forked sched_entity should n=
    ot inherit or retain this state. Clear se->rel_deadline in __sched_fork(), = together with the other sched_entity runtime state, so that the first enque=
    ue does not interpret the new entity's deadline as a stale relative deadlin=
    e. 2026-06-24 not yet calculated CVE-2026-52980 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-52980 ] Linux--Linux In the Linux kernel, the following = vulnerability has been resolved: net/sched: netem: fix queue limit check to=
    include reordered packets The queue limit check in netem_enqueue() uses q-= >t_len which only counts packets in the internal tfifo. Packets placed in s= ch->q by the reorder path (__qdisc_enqueue_head) are not counted, allowing = the total queue occupancy to exceed sch->limit under reordering. Include sc= h->q.qlen in the limit check. 2026-06-24 not yet calculated CVE-2026-52984 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-52984 ] Linux--Linux In the L= inux kernel, the following vulnerability has been resolved: netdevsim: zero=
    initialize struct iphdr in dummy sk_buff Syzbot reports a KMSAN uninit-val=
    ue originating from nsim_dev_trap_skb_build, with the allocation also being=
    performed in the same function. Fix this by calling skb_put_zero instead o=
    f skb_put to guarantee zero initialization of the whole IP header. 2026-06-=
    24 not yet calculated CVE-2026-52985 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-52985 ] Linux--Linux In the Linux kernel, the following vulnerabili=
    ty has been resolved: fsnotify: fix inode reference leak in fsnotify_recalc= _mask() fsnotify_recalc_mask() fails to handle the return value of __fsnoti= fy_recalc_mask(), which may return an inode pointer that needs to be releas=
    ed via fsnotify_drop_object() when the connector's HAS_IREF flag transition=
    s from set to cleared. This manifests as a hung task with the following cal=
    l trace: INFO: task umount:1234 blocked for more than 120 seconds. Call Tra= ce: __schedule schedule fsnotify_sb_delete generic_shutdown_super kill_anon= _super cleanup_mnt task_work_run do_exit do_group_exit The race window that=
    triggers the iref leak: Thread A (adding mark) Thread B (removing mark) = =C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3= =A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2= =E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2= =80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80= =9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D= =E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2= =82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82= =AC =C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82= =AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC= =C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3= =A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2= =E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2= =80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80= =9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D= =E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC fsnotify_add_mark= _locked(): fsnotify_add_mark_list(): spin_lock(conn->lock) add mark_B(evict= able) to list spin_unlock(conn->lock) return /* ---- gap: no lock held ----=
    */ fsnotify_detach_mark(mark_A): spin_lock(mark_A->lock) clear ATTACHED fl=
    ag on mark_A spin_unlock(mark_A->lock) fsnotify_put_mark(mark_A) fsnotify_r= ecalc_mask(): spin_lock(conn->lock) __fsnotify_recalc_mask(): /* mark_A ski= pped: ATTACHED cleared */ /* only mark_B(evictable) remains */ want_iref =
    =3D false has_iref =3D true /* not yet cleared */ -> HAS_IREF transitions t= rue -> false -> returns inode pointer spin_unlock(conn->lock) /* BUG: retur=
    n value discarded! * iput() and fsnotify_put_sb_watched_objects() * are nev=
    er called */ Fix this by deferring the transition true -> false of HAS_IREF=
    flag from fsnotify_recalc_mask() (Thread A) to fsnotify_put_mark() (thread=
    B). 2026-06-24 not yet calculated CVE-2026-52990 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-52990 ] Linux--Linux In the Linux kernel, the followin=
    g vulnerability has been resolved: fs/adfs: validate nzones in adfs_validat= e_bblk() Reject ADFS disc records with a zero zone count during boot block = validation, before the disc record is used. When nzones is 0, adfs_read_map=
    () passes it to kmalloc_array(0, ...) which returns ZERO_SIZE_PTR, and adfs= _map_layout() then writes to dm[-1], causing an out-of-bounds write before = the allocated buffer. adfs_validate_dr0() already rejects nzones !=3D 1 for=
    old-format images. Add the equivalent check to adfs_validate_bblk() for ne= w-format images so that a crafted image with nzones =3D=3D 0 is rejected at=
    probe time. Found by syzkaller. 2026-06-24 not yet calculated CVE-2026-529=
    92 [ https://www.cve.org/CVERecord?id=3DCVE-2026-52992 ] Linux--Linux In th=
    e Linux kernel, the following vulnerability has been resolved: vsock/virtio=
    : fix MSG_ZEROCOPY pinned-pages accounting virtio_transport_init_zcopy_skb(=
    ) uses iter->count as the size argument for msg_zerocopy_realloc(), which i=
    n turn passes it to mm_account_pinned_pages() for RLIMIT_MEMLOCK accounting=
    . However, this function is called after virtio_transport_fill_skb() has al= ready consumed the iterator via __zerocopy_sg_from_iter(), so on the last s= kb, iter->count will be 0, skipping the RLIMIT_MEMLOCK enforcement. Pass pk= t_len (the total bytes being sent) as an explicit parameter to virtio_trans= port_init_zcopy_skb() instead of reading the already-consumed iter->count. = This matches TCP and UDP, which both call msg_zerocopy_realloc() with the o= riginal message size. 2026-06-24 not yet calculated CVE-2026-52994 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-52994 ] Linux--Linux In the Linux ker= nel, the following vulnerability has been resolved: net/rds: zero per-item = info buffer before handing it to visitors rds_for_each_conn_info() and rds_= walk_conn_path_info() both hand a caller-allocated on-stack u64 buffer to a=
    per-connection visitor and then copy the full item_len bytes back to user = space via rds_info_copy() regardless of how much of the buffer the visitor = actually wrote. rds_ib_conn_info_visitor() and rds6_ib_conn_info_visitor() = only write a subset of their output struct when the underlying rds_connecti=
    on is not in state RDS_CONN_UP (src/dst addr, tos, sl and the two GIDs via = explicit memsets). Several u32 fields (max_send_wr, max_recv_wr, max_send_s= ge, rdma_mr_max, rdma_mr_size, cache_allocs) and the 2-byte alignment hole = between sl and cache_allocs remain as whatever stack contents preceded the = visitor call and are then memcpy_to_user()'d out to user space. struct rds_= info_rdma_connection and struct rds6_info_rdma_connection are the only rds_= info_* structs in include/uapi/linux/rds.h that are not marked __attribute_= _((packed)), so they have a real alignment hole. The other info visitors (r= ds_conn_info_visitor, rds6_conn_info_visitor, rds_tcp_tc_info, ...) write a=
    ll fields of their packed output struct today and are not known to be vulne= rable, but a future visitor that adds a conditional write-path would have t=
    he same bug. Reproduction on a kernel built without CONFIG_INIT_STACK_ALL_Z= ERO=3Dy: a local unprivileged user opens AF_RDS, sets SO_RDS_TRANSPORT=3DIB=
    , binds to a local address on an RDMA-capable netdev (rxe soft-RoCE on any = netdev is sufficient), sendto()'s any peer on the same subnet (fails cleanl=
    y but installs an rds_connection in the global hash in RDS_CONN_CONNECTING)=
    , then calls getsockopt(SOL_RDS, RDS_INFO_IB_CONNECTIONS). The returned 68-= byte item contains 26 bytes of stack garbage including kernel text/data poi= nters: 0..7 0a 63 00 01 0a 63 00 02 src=3D10.99.0.1 dst=3D10.99.0.2 8..39 0=
    0 ... gids (memset-zeroed) 40..47 e0 92 a3 81 ff ff ff ff kernel pointer (m= ax_send_wr) 48..55 7f 37 b5 81 ff ff ff ff kernel pointer (rdma_mr_max) 56.= .59 01 00 08 00 rdma_mr_size (garbage) 60..61 00 00 tos, sl 62..63 00 00 al= ignment padding 64..67 18 00 00 00 cache_allocs (garbage) Fix by zeroing th=
    e per-item buffer in both rds_for_each_conn_info() and rds_walk_conn_path_i= nfo() before invoking the visitor. This covers the IPv4/IPv6 IB visitors an=
    d hardens all current and future visitors against the same class of bug. No=
    functional change for visitors that fully populate their output. Changes i=
    n v2: - retarget at the net tree (subject prefix "[PATCH net v2]", net/rds:=
    prefix in the title) - pick up Reviewed-by tags from Sharath Srinivasan an=
    d Allison Henderson 2026-06-24 not yet calculated CVE-2026-52995 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-52995 ] Linux--Linux In the Linux kerne=
    l, the following vulnerability has been resolved: ksmbd: fix durable fd lea=
    k on ClientGUID mismatch in durable v2 open ksmbd_lookup_fd_cguid() returns=
    a ksmbd_file with its refcount incremented via ksmbd_fp_get(). parse_durab= le_handle_context() in the DURABLE_REQ_V2 case properly releases this refer= ence on every path inside the ClientGUID-match branch, either by calling ks= mbd_put_durable_fd() or by transferring ownership to dh_info->fp for a succ= essful reconnect. However, when an entry exists in the global file table wi=
    th the same CreateGuid but a different ClientGUID, the code simply falls th= rough to the new-open path without dropping the reference obtained from ksm= bd_lookup_fd_cguid(). Per MS-SMB2 section 3.3.5.9.10 ("Handling the SMB2_CR= EATE_DURABLE_HANDLE_REQUEST_V2 Create Context"), the server MUST locate an = Open whose Open.CreateGuid matches the request's CreateGuid AND whose Open.= ClientGuid matches the ClientGuid of the connection that received the reque= st. If no such Open is found, the server MUST continue with the normal open=
    execution phase. A CreateGuid hit with a ClientGUID mismatch is therefore = the "Open not found" case: proceeding with a new open is correct, but the r= eference obtained purely as a side effect of the lookup must not be leaked.=
    Repeated requests that hit this mismatch pin global_ft entries, prevent __= ksmbd_close_fd() from ever running for the corresponding files, and defeat = the durable scavenger, leading to long-lived resource leaks. Release the re= ference in the mismatch path and clear dh_info->fp so subsequent logic does=
    not mistake a non-matching lookup result for a reconnect target. 2026-06-2=
    4 not yet calculated CVE-2026-52996 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-52996 ] Linux--Linux In the Linux kernel, the following vulnerabilit=
    y has been resolved: net/sched: sch_dualpi2: drain both C-queue and L-queue=
    in dualpi2_change() Fix dualpi2_change() to correctly enforce updated limi=
    t and memlimit values after a configuration change of the dualpi2 qdisc. Be= fore this patch, dualpi2_change() always attempted to dequeue packets via t=
    he root qdisc (C-queue) when reducing backlog or memory usage, and uncondit= ionally assumed that a valid skb will be returned. When traffic classificat= ion results in packets being queued in the L-queue while the C-queue is emp= ty, this leads to a NULL skb dereference during limit or memlimit enforceme= nt. This is fixed by first dequeuing from the C-queue path if it is non-emp= ty. Once the C-queue is empty, packets are dequeued directly from the L-que= ue. Return values from qdisc_dequeue_internal() are checked for both queues=
    . When dequeuing from the L-queue, the parent qdisc qlen and backlog counte=
    rs are updated explicitly to keep overall qdisc statistics consistent. 2026= -06-24 not yet calculated CVE-2026-52997 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-52997 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: netfilter: xtables: restrict several matches to i= net family This is a partial revert of: commit ab4f21e6fb1c ("netfilter: xt= ables: use NFPROTO_UNSPEC in more extensions") to allow ipv4 and ipv6 only.=
    - xt_mac - xt_owner - xt_physdev These extensions are not used by ebtables=
    in userspace. Moreover, xt_realm is only for ipv4, since dst->tclassid is = ipv4 specific. 2026-06-24 not yet calculated CVE-2026-53001 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-53001 ] Linux--Linux In the Linux kernel, th=
    e following vulnerability has been resolved: sctp: fix OOB write to userspa=
    ce in sctp_getsockopt_peer_auth_chunks sctp_getsockopt_peer_auth_chunks() c= hecks that the caller's optval buffer is large enough for the peer AUTH chu=
    nk list with if (len < num_chunks) return -EINVAL; but then writes num_chun=
    ks bytes to p->gauth_chunks, which lives at offset offsetof(struct sctp_aut= hchunks, gauth_chunks) =3D=3D 8 inside optval. The check is missing the siz= eof(struct sctp_authchunks) =3D 8-byte header. When the caller supplies len=
    =3D=3D num_chunks (for any num_chunks > 0) the test passes but copy_to_use= r() writes sizeof(struct sctp_authchunks) =3D 8 bytes past the declared buf= fer. The sibling function sctp_getsockopt_local_auth_chunks() at the next l= ine already has the correct check: if (len < sizeof(struct sctp_authchunks)=
    + num_chunks) return -EINVAL; Align the peer variant with its sibling. Rep= roducer confirms on v7.0-13-generic: an unprivileged userspace caller that = opens a loopback SCTP association with AUTH enabled, queries num_chunks wit=
    h a short optval, then issues the real getsockopt with len =3D=3D num_chunk=
    s and sentinel bytes painted past the buffer observes those sentinel bytes = overwritten with the peer's AUTH chunk type. The bytes written are under th=
    e peer's control but land in the caller's own userspace; this is not a kern=
    el memory corruption, but it is a kernel-side contract violation that can s= ilently corrupt adjacent userspace data. 2026-06-24 not yet calculated CVE-= 2026-53004 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53004 ] Linux--Lin=
    ux In the Linux kernel, the following vulnerability has been resolved: ice:=
    fix potential NULL pointer deref in error path of ice_set_ringparam() ice_= set_ringparam nullifies tstamp_ring of temporary tx_rings, without clearing=
    ICE_TX_RING_FLAGS_TXTIME bit. When ICE_TX_RING_FLAGS_TXTIME is set and the=
    subsequent ice_setup_tx_ring() call fails, a NULL pointer dereference coul=
    d happen in the unwinding sequence: ice_clean_tx_ring() -> ice_is_txtime_cf= g() =3D=3D true (ICE_TX_RING_FLAGS_TXTIME is set) -> ice_free_tx_tstamp_rin= g() -> ice_free_tstamp_ring() -> tstamp_ring->desc (NULL deref) Clear ICE_T= X_RING_FLAGS_TXTIME bit to avoid the potential issue. Note that this potent= ial issue is found by manual code review. Compile test only since unfortuna= tely I don't have E830 devices. 2026-06-24 not yet calculated CVE-2026-5300=
    7 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53007 ] Linux--Linux In the=
    Linux kernel, the following vulnerability has been resolved: ice: fix race=
    condition in TX timestamp ring cleanup Fix a race condition between ice_fr= ee_tx_tstamp_ring() and ice_tx_map() that can cause a NULL pointer derefere= nce. ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag = after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map cal=
    l on another CPU to dereference the tstamp_ring, which could lead to a NULL=
    pointer dereference. CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map() = --------------------------------|--------------------------------- tx_ring-= >tstamp_ring =3D NULL | | ice_is_txtime_cfg() -> true | tstamp_ring =3D tx_= ring->tstamp_ring | tstamp_ring->count // NULL deref! flags &=3D ~ICE_TX_FL= AGS_TXTIME | Fix by: 1. Reordering ice_free_tx_tstamp_ring() to clear the f= lag before NULLing the pointer, with smp_wmb() to ensure proper ordering. 2=
    . Adding smp_rmb() in ice_tx_map() after the flag check to order the flag r= ead before the pointer read, using READ_ONCE() for the pointer, and adding =
    a NULL check as a safety net. 3. Converting tx_ring->flags from u8 to DECLA= RE_BITMAP() and using atomic bitops (set_bit(), clear_bit(), test_bit()) fo=
    r all flag operations throughout the driver: - ICE_TX_RING_FLAGS_XDP - ICE_= TX_RING_FLAGS_VLAN_L2TAG1 - ICE_TX_RING_FLAGS_VLAN_L2TAG2 - ICE_TX_RING_FLA= GS_TXTIME 2026-06-24 not yet calculated CVE-2026-53008 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-53008 ] Linux--Linux In the Linux kernel, the fol= lowing vulnerability has been resolved: nexthop: fix IPv6 route referencing=
    IPv4 nexthop syzbot reported a panic [1] [2]. When an IPv6 nexthop is repl= aced with an IPv4 nexthop, the has_v4 flag of all groups containing this ne= xthop is not updated. This is because nh_group_v4_update is only called whe=
    n replacing AF_INET to AF_INET6, but the reverse direction (AF_INET6 to AF_= INET) is missed. This allows a stale has_v4=3Dfalse to bypass fib6_check_ne= xthop, causing IPv6 routes to be attached to groups that effectively contai=
    n only AF_INET members. Subsequent route lookups then call nexthop_fib6_nh(=
    ) which returns NULL for the AF_INET member, leading to a NULL pointer dere= ference. Fix by calling nh_group_v4_update whenever the family changes, not=
    just AF_INET to AF_INET6. Reproducer: # AF_INET6 blackhole ip -6 nexthop a=
    dd id 1 blackhole # group with has_v4=3Dfalse ip nexthop add id 100 group 1=
    # replace with AF_INET (no -6), has_v4 stays false ip nexthop replace id 1=
    blackhole # pass stale has_v4 check ip -6 route add 2001:db8::/64 nhid 100=
    # panic ping -6 2001:db8::1 [1] https://syzkaller.appspot.com/bug?id=3De17= 283eb2f8dcf3dd9b47fe6f67a95f71faadad0 [2] https://syzkaller.appspot.com/bug= ?id=3D8699b6ae54c9f35837d925686208402949e12ef3 2026-06-24 not yet calculate=
    d CVE-2026-53012 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53012 ] Linu= x--Linux In the Linux kernel, the following vulnerability has been resolved=
    : macvlan: fix macvlan_get_size() not reserving space for IFLA_MACVLAN_BC_C= UTOFF macvlan_get_size() does not account for IFLA_MACVLAN_BC_CUTOFF, but m= acvlan_fill_info() conditionally includes it when port->bc_cutoff !=3D 1. T= his causes nla_put_s32() to fail with -EMSGSIZE when the netlink skb runs o=
    ut of space, triggering a WARN_ON in rtnetlink and preventing the interface=
    from being dumped. The bug can be reproduced with: ip link add macvlan0 li=
    nk eth0 type macvlan mode bridge ip link set macvlan0 type macvlan bc_cutof=
    f 0 ip -d link show macvlan0 # fails with -EMSGSIZE The bc_cutoff feature w=
    as added in commit 954d1fa1ac93 ("macvlan: Add netlink attribute for broadc= ast cutoff"), which added the nla_put_s32() call in macvlan_fill_info() but=
    missed adding the corresponding nla_total_size(4) in macvlan_get_size(). A=
    follow-up commit 55cef78c244d ("macvlan: add forgotten nla_policy for IFLA= _MACVLAN_BC_CUTOFF") fixed the missing nla_policy entry but still did not f=
    ix the size calculation. 2026-06-24 not yet calculated CVE-2026-53013 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-53013 ] Linux--Linux In the Linux = kernel, the following vulnerability has been resolved: net/sched: act_mirre=
    d: fix wrong device for mac_header_xmit check in tcf_blockcast_redir In tcf= _blockcast_redir(), when iterating block ports to redirect packets to multi= ple devices, the mac_header_xmit flag is queried from the wrong device. The=
    loop sends to dev_prev but queries dev_is_mac_header_xmit(dev) - which is = the NEXT device in the iteration, not the one being sent to. This causes tc= f_mirred_to_dev() to make incorrect decisions about whether to push or pull=
    the MAC header. When the block contains mixed device types (e.g., an ether= net veth and a tunnel device), intermediate devices get the wrong mac_heade= r_xmit flag, leading to skb header corruption. In the worst case, skb_push_= rcsum with an incorrect mac_len can exhaust headroom and panic. The last de= vice in the loop is handled correctly (line 365-366 uses dev_is_mac_header_= xmit(dev_prev)), confirming this is a copy-paste oversight for the intermed= iate devices. Fix by using dev_prev instead of dev for the mac_header_xmit = query, consistent with the device actually being sent to. 2026-06-24 not ye=
    t calculated CVE-2026-53014 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 3014 ] Linux--Linux In the Linux kernel, the following vulnerability has be=
    en resolved: erofs: unify lcn as u64 for 32-bit platforms As sashiko report=
    ed [1], `lcn` was typed as `unsigned long` (or `unsigned int` sometimes), w= hich is only 32 bits wide on 32-bit platforms, which causes `(lcn << lclust= erbits)` to be truncated at 4 GiB. In order to consolidate the logic, just = use `u64` consistently around the codebase. [1] https://sashiko.dev/r/20260= 420034612.1899973-1-hsiangkao%40linux.alibaba.com 2026-06-24 not yet calcul= ated CVE-2026-53015 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53015 ] L= inux--Linux In the Linux kernel, the following vulnerability has been resol= ved: f2fs: fix data loss caused by incorrect use of nat_entry flag Data los=
    s can occur when fsync is performed on a newly created file (before any che= ckpoint has been written) concurrently with a checkpoint operation. The sce= nario is as follows: create & write & fsync 'file A' write checkpoint - f2f= s_do_sync_file // inline inode - f2fs_write_inode // inode folio is dirty -=
    f2fs_write_checkpoint - f2fs_flush_merged_writes - f2fs_sync_node_pages - = f2fs_flush_nat_entries - f2fs_fsync_node_pages // no dirty node - f2fs_need= _inode_block_update // return false SPO and lost 'file A' f2fs_flush_nat_en= tries() sets the IS_CHECKPOINTED and HAS_LAST_FSYNC flags for the nat_entry=
    , but this does not mean that the checkpoint has actually completed success= fully. However, f2fs_need_inode_block_update() checks these flags and incor= rectly assumes that the checkpoint has finished. The root cause is that the=
    semantics of IS_CHECKPOINTED and HAS_LAST_FSYNC are only guaranteed after = the checkpoint write fully completes. This patch modifies f2fs_need_inode_b= lock_update() to acquire the sbi->node_write lock before reading the nat_en= try flags, ensuring that once IS_CHECKPOINTED and HAS_LAST_FSYNC are observ=
    ed to be set, the checkpoint operation has already completed. 2026-06-24 no=
    t yet calculated CVE-2026-53017 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-53017 ] Linux--Linux In the Linux kernel, the following vulnerability ha=
    s been resolved: f2fs: avoid reading already updated pages during GC We fou=
    nd the following issue during fuzz testing: page: refcount:3 mapcount:0 map= ping:00000000b6e89c65 index:0x18b2dc pfn:0x161ba9 memcg:f8ffff800e269c00 ao= ps:f2fs_meta_aops ino:2 flags: 0x52880000000080a9(locked|waiters|uptodate|l= ru|private|zone=3D1|kasantag=3D0x4a) raw: 52880000000080a9 fffffffec6e17588=
    fffffffec0ccc088 a7ffff8067063618 raw: 000000000018b2dc 0000000000000009 0= 0000003ffffffff f8ffff800e269c00 page dumped because: VM_BUG_ON_FOLIO(folio= _test_uptodate(folio)) page_owner tracks the page as allocated post_alloc_h= ook+0x58c/0x5ec prep_new_page+0x34/0x284 get_page_from_freelist+0x2dcc/0x2e=
    8c __alloc_pages_noprof+0x280/0x76c __folio_alloc_noprof+0x18/0xac __filema= p_get_folio+0x6bc/0xdc4 pagecache_get_page+0x3c/0x104 do_garbage_collect+0x= 5c78/0x77a4 f2fs_gc+0xd74/0x25f0 gc_thread_func+0xb28/0x2930 kthread+0x464/= 0x5d8 ret_from_fork+0x10/0x20 ------------[ cut here ]------------ kernel B=
    UG at mm/filemap.c:1563! folio_end_read+0x140/0x168 f2fs_finish_read_bio+0x= 5c4/0xb80 f2fs_read_end_io+0x64c/0x708 bio_endio+0x85c/0x8c0 blk_update_req= uest+0x690/0x127c scsi_end_request+0x9c/0xb8c scsi_io_completion+0xf0/0x250=
    scsi_finish_command+0x430/0x45c scsi_complete+0x178/0x6d4 blk_mq_complete_= request+0xcc/0x104 scsi_done_internal+0x214/0x454 scsi_done+0x24/0x34 which=
    is similar to the problem reported by syzbot: https://syzkaller.appspot.co= m/bug?extid=3D3686758660f980b402dc This case is consistent with the descrip= tion in commit 9bf1a3f ("f2fs: avoid GC causing encrypted file corrupted"):=
    Page 1 is moved from blkaddr A to blkaddr B by move_data_block, and after = being written it is marked as uptodate. Then, Page 1 is moved from blkaddr =
    B to blkaddr C, VM_BUG_ON_FOLIO was triggered in the endio initiated by ra_= data_block. There is no need to read Page 1 again from blkaddr B, since it = has already been updated. Therefore, avoid initiating I/O in this case. 202= 6-06-24 not yet calculated CVE-2026-53018 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-53018 ] Linux--Linux In the Linux kernel, the following vulner= ability has been resolved: clk: spacemit: ccu_mix: fix inverted condition i=
    n ccu_mix_trigger_fc() Fix inverted condition that skips frequency change t= rigger, causing kernel panics during cpufreq scaling. 2026-06-24 not yet ca= lculated CVE-2026-53019 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53019=
    ] Linux--Linux In the Linux kernel, the following vulnerability has been r= esolved: scsi: target: core: Fix integer overflow in UNMAP bounds check sbc= _execute_unmap() checks LBA + range does not exceed the device capacity, bu=
    t does not guard against LBA + range wrapping around on 64-bit overflow. Ad=
    d an overflow check matching the pattern already used for WRITE_SAME in the=
    same file. 2026-06-24 not yet calculated CVE-2026-53021 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-53021 ] Linux--Linux In the Linux kernel, the f= ollowing vulnerability has been resolved: platform/x86: dell-wmi-sysman: bo= und enumeration string aggregation populate_enum_data() aggregates firmware= -provided value-modifier and possible-value strings into fixed 512-byte str= uct members. The current code bounds each individual source string but then=
    appends every string and separator with raw strcat() and no remaining-spac=
    e check. Switch the aggregation loops to a bounded append helper and reject=
    enumeration packages whose combined strings do not fit in the destination = buffers. [ij: add include] 2026-06-24 not yet calculated CVE-2026-53022 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-53022 ] Linux--Linux In the Linu=
    x kernel, the following vulnerability has been resolved: fs/ntfs3: terminat=
    e the cached volume label after UTF-8 conversion ntfs_fill_super() loads th=
    e on-disk volume label with utf16s_to_utf8s() and stores the result in sbi-= >volume.label. The converted label is later exposed through ntfs3_label_sho= w() using %s, but utf16s_to_utf8s() only returns the number of bytes writte=
    n and does not add a trailing NUL. If the converted label fills the entire = fixed buffer, ntfs3_label_show() can read past the end of sbi->volume.label=
    while looking for a terminator. Terminate the cached label explicitly afte=
    r a successful conversion and clamp the exact-full case to the last byte of=
    the buffer. 2026-06-24 not yet calculated CVE-2026-53023 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-53023 ] Linux--Linux In the Linux kernel, the = following vulnerability has been resolved: fs/ntfs3: fix missing run load f=
    or vcn0 in attr_data_get_block_locked() When a compressed or sparse attribu=
    te has its clusters frame-aligned, vcn is rounded down to the frame start u= sing cmask, which can result in vcn !=3D vcn0. In this case, vcn and vcn0 m=
    ay reside in different attribute segments. The code already handles the cas=
    e where vcn is in a different segment by loading its runs before allocation=
    . However, it fails to load runs for vcn0 when vcn0 resides in a different = segment than vcn. This causes run_lookup_entry() to return SPARSE_LCN for v= cn0 since its segment was never loaded into the in-memory run list, trigger= ing the WARN_ON(1). Fix this by adding a missing check for vcn0 after the e= xisting vcn segment check. If vcn0 falls outside the current segment range = [svcn, evcn1), find and load the attribute segment containing vcn0 before p= erforming the run lookup. The following scenario triggers the bug: attr_dat= a_get_block_locked() vcn =3D vcn0 & cmask <- vcn !=3D vcn0 after frame alig= nment load runs for vcn segment <- vcn0 segment not loaded! attr_allocate_c= lusters() <- allocation succeeds run_lookup_entry(vcn0) <- vcn0 not in run =
    SPARSE_LCN WARN_ON(1) <- bug fires here! 2026-06-24 not yet calculated C=
    VE-2026-53027 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53027 ] Linux--= Linux In the Linux kernel, the following vulnerability has been resolved: u= sb: typec: Fix error pointer dereference The variable tps->partner is check=
    ed for an error pointer and then if it is, it sends an error message but do=
    es not return and then immediately dereferenced a few lines below: tps->par= tner =3D typec_register_partner(tps->port, &desc); if (IS_ERR(tps->partner)=
    ) dev_warn(tps->dev, "%s: failed to register partnet\n", __func__); if (des= c.identity) { typec_partner_set_identity(tps->partner); cd321x->cur_partner= _identity =3D st.partner_identity; } Add early return and fix spelling mist= ake in error message. Detected by Smatch: drivers/usb/typec/tipd/core.c:827=
    cd321x_update_work() error: 'tps->partner' dereferencing possible ERR_PTR(=
    ) 2026-06-24 not yet calculated CVE-2026-53028 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-53028 ] Linux--Linux In the Linux kernel, the following v= ulnerability has been resolved: fs/ntfs3: prevent uninitialized lcn caused =
    by zero len syzbot reported a uninit-value in ntfs_iomap_begin [1]. Since r= uns was not touched yet, run_lookup_entry() immediately fails and returns f= alse, which makes the value of "*len" 0. Simultaneously, the new value and = err value are also 0, causing the logic in attr_data_get_block_locked() to = jump directly to ok, ultimately resulting in *lcn being triggered before it=
    is set [1]. In ntfs_iomap_begin(), the check for a 0 value in clen is move=
    d forward to before updating lcn to avoid this [1]. [1] BUG: KMSAN: uninit-= value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825 ntfs_iomap_begi= n+0x8c0/0x1460 fs/ntfs3/inode.c:825 iomap_iter+0x9b7/0x1540 fs/iomap/iter.c= :110 Local variable lcn created at: ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/= inode.c:786 2026-06-24 not yet calculated CVE-2026-53029 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-53029 ] Linux--Linux In the Linux kernel, the f= ollowing vulnerability has been resolved: i3c: master: renesas: Fix memory = leak in renesas_i3c_i3c_xfers() The xfer structure allocated by renesas_i3c= _alloc_xfer() was never freed in the renesas_i3c_i3c_xfers() function. Use = the __free(kfree) cleanup attribute to automatically free the memory when t=
    he variable goes out of scope. 2026-06-24 not yet calculated CVE-2026-53030=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-53030 ] Linux--Linux In the = Linux kernel, the following vulnerability has been resolved: bpf: Fix NULL = deref in map_kptr_match_type for scalar regs Commit ab6c637ad027 ("bpf: Fix=
    a bpf_kptr_xchg() issue with local kptr") refactored map_kptr_match_type()=
    to branch on btf_is_kernel() before checking base_type(). A scalar registe=
    r stored into a kptr slot has no btf, so the btf_is_kernel(reg->btf) call d= ereferences NULL. Move the base_type() !=3D PTR_TO_BTF_ID guard before any = reg->btf access. 2026-06-24 not yet calculated CVE-2026-53032 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-53032 ] Linux--Linux In the Linux kernel, = the following vulnerability has been resolved: bpf, sockmap: Fix af_unix nu= ll-ptr-deref in proto update unix_stream_connect() sets sk_state (`WRITE_ON= CE(sk->sk_state, TCP_ESTABLISHED)`) _before_ it assigns a peer (`unix_peer(= sk) =3D newsk`). sk_state =3D=3D TCP_ESTABLISHED makes sock_map_sk_state_al= lowed() believe that socket is properly set up, which would include having =
    a defined peer. IOW, there's a window when unix_stream_bpf_update_proto() c=
    an be called on socket which still has unix_peer(sk) =3D=3D NULL. CPU0 bpf = CPU1 connect -------- ------------ WRITE_ONCE(sk->sk_state, TCP_ESTABLISHED=
    ) sock_map_sk_state_allowed(sk) ... sk_pair =3D unix_peer(sk) sock_hold(sk_= pair) sock_hold(newsk) smp_mb__after_atomic() unix_peer(sk) =3D newsk BUG: = kernel NULL pointer dereference, address: 0000000000000080 RIP: 0010:unix_s= tream_bpf_update_proto+0xa0/0x1b0 Call Trace: sock_map_link+0x564/0x8b0 soc= k_map_update_common+0x6e/0x340 sock_map_update_elem_sys+0x17d/0x240 __sys_b= pf+0x26db/0x3250 __x64_sys_bpf+0x21/0x30 do_syscall_64+0x6b/0x3a0 entry_SYS= CALL_64_after_hwframe+0x76/0x7e Initial idea was to move peer assignment _b= efore_ the sk_state update[1], but that involved an additional memory barri= er, and changing the hot path was rejected. Then a NULL check during proto = update in unix_stream_bpf_update_proto() was considered[2], but the follow-=
    up discussion[3] focused on the root cause, i.e. sockmap update taking a wr= ong lock. Or, more specifically, missing unix_state_lock()[4]. In the end i=
    t was concluded that teaching sockmap about the af_unix locking would be un= necessarily complex[5]. Complexity aside, since BPF_PROG_TYPE_SCHED_CLS and=
    BPF_PROG_TYPE_SCHED_ACT are allowed to update sockmaps, sock_map_update_el= em() taking the unix lock, as it is currently implemented in unix_state_loc= k(): spin_lock(&unix_sk(s)->lock), would be problematic. unix_state_lock() = taken in a process context, followed by a softirq-context TC BPF program at= tempting to take the same spinlock -- deadlock[6]. This way we circled back=
    to the peer check idea[2]. [1]: https://lore.kernel.org/netdev/ba5c50aa-1d= f4-40c2-ab33-a72022c5a32e@rbox.co/ [2]: https://lore.kernel.org/netdev/2024= 0610174906.32921-1-kuniyu@amazon.com/ [3]: https://lore.kernel.org/netdev/7= 603c0e6-cd5b-452b-b710-73b64bd9de26@linux.dev/ [4]: https://lore.kernel.org= /netdev/CAAVpQUA+8GL_j63CaKb8hbxoL21izD58yr1NvhOhU=3Dj+35+3og@mail.gmail.co=
    m/ [5]: https://lore.kernel.org/bpf/CAAVpQUAHijOMext28Gi10dSLuMzGYh+jK61Ujn= +fZ-wvcODR2A@mail.gmail.com/ [6]: https://lore.kernel.org/bpf/dd043c69-4d03= -46fe-8325-8f97101435cf@linux.dev/ Summary of scenarios where af_unix/strea=
    m connect() may race a sockmap update: 1. connect() vs. bpf(BPF_MAP_UPDATE_= ELEM), i.e. sock_map_update_elem_sys() Implemented NULL check is sufficient=
    . Once assigned, socket peer won't be released until socket fd is released.=
    And that's not an issue because sock_map_update_elem_sys() bumps fd refcnf=
    . 2. connect() vs BPF program doing update Update restricted per verifier.c= :may_update_sockmap() to BPF_PROG_TYPE_TRACING/BPF_TRACE_ITER BPF_PROG_TYPE= _SOCK_OPS (bpf_sock_map_update() only) BPF_PROG_TYPE_SOCKET_FILTER BPF_PROG= _TYPE_SCHED_CLS BPF_PROG_TYPE_SCHED_ACT BPF_PROG_TYPE_XDP BPF_PROG_TYPE_SK_= REUSEPORT BPF_PROG_TYPE_FLOW_DISSECTOR BPF_PROG_TYPE_SK_LOOKUP Plus one mor=
    e race to consider: CPU0 bpf CPU1 connect -------- ------------ WRITE_ONCE(= sk->sk_state, TCP_ESTABLISHED) sock_map_sk_state_allowed(sk) sock_hold(news=
    k) smp_mb__after_atomic() ---truncated--- 2026-06-24 not yet calculated CVE= -2026-53034 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53034 ] Linux--Li= nux In the Linux kernel, the following vulnerability has been resolved: bpf=
    , sockmap: Fix af_unix iter deadlock bpf_iter_unix_seq_show() may deadlock = when lock_sock_fast() takes the fast path and the iter prog attempts to upd= ate a sockmap. Which ends up spinning at sock_map_update_elem()'s bh_lock_s= ock(): WARNING: possible recursive locking detected test_progs/1393 is tryi=
    ng to acquire lock: ffff88811ec25f58 (slock-AF_UNIX){+...}-{3:3}, at: sock_= map_update_elem+0xdb/0x1f0 but task is already holding lock: ffff88811ec25f=
    58 (slock-AF_UNIX){+...}-{3:3}, at: __lock_sock_fast+0x37/0xe0 other info t= hat might help us debug this: Possible unsafe locking scenario: CPU0 ---- l= ock(slock-AF_UNIX); lock(slock-AF_UNIX); *** DEADLOCK *** May be due to mis= sing lock nesting notation 4 locks held by test_progs/1393: #0: ffff88814b5= 9c790 (&p->lock){+.+.}-{4:4}, at: bpf_seq_read+0x59/0x10d0 #1: ffff88811ec2= 5fd8 (sk_lock-AF_UNIX){+.+.}-{0:0}, at: bpf_seq_read+0x42c/0x10d0 #2: ffff8= 8811ec25f58 (slock-AF_UNIX){+...}-{3:3}, at: __lock_sock_fast+0x37/0xe0 #3:=
    ffffffff85a6a7c0 (rcu_read_lock){....}-{1:3}, at: bpf_iter_run_prog+0x51d/= 0xb00 Call Trace: dump_stack_lvl+0x5d/0x80 print_deadlock_bug.cold+0xc0/0xc=
    e __lock_acquire+0x130f/0x2590 lock_acquire+0x14e/0x2b0 _raw_spin_lock+0x30= /0x40 sock_map_update_elem+0xdb/0x1f0 bpf_prog_2d0075e5d9b721cd_dump_unix+0= x55/0x4f4 bpf_iter_run_prog+0x5b9/0xb00 bpf_iter_unix_seq_show+0x1f7/0x2e0 = bpf_seq_read+0x42c/0x10d0 vfs_read+0x171/0xb20 ksys_read+0xff/0x200 do_sysc= all_64+0x6b/0x3a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e 2026-06-24 not y=
    et calculated CVE-2026-53035 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 53035 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: HID: usbhid: fix deadlock in hid_post_reset() You can build a=
    USB device that includes a HID component and a storage or UAS component. T=
    he components can be reset only together. That means that hid_pre_reset() a=
    nd hid_post_reset() are in the block IO error handling. Hence no memory all= ocation used in them may do block IO because the IO can deadlock on the mut=
    ex held while resetting a device and calling the interface drivers. Use GFP= _NOIO for all allocations in them. 2026-06-24 not yet calculated CVE-2026-5= 3037 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53037 ] Linux--Linux In = the Linux kernel, the following vulnerability has been resolved: ima_fs: Co= rrectly create securityfs files for unsupported hash algos ima_tpm_chip->al= located_banks[i].crypto_id is initialized to HASH_ALGO__LAST if the TPM alg= orithm is not supported. However there are places relying on the algorithm =
    to be valid because it is accessed by hash_algo_name[]. On 6.12.40 I observ=
    e the following read out-of-bounds in hash_algo_name: =3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D BUG: KASAN: global-out-of-bounds in create_secu= rityfs_measurement_lists+0x396/0x440 Read of size 8 at addr ffffffff83e1813=
    8 by task swapper/0/1 CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12= .40 #3 Call Trace: <TASK> dump_stack_lvl+0x61/0x90 print_report+0xc4/0x580 =
    ? kasan_addr_to_slab+0x26/0x80 ? create_securityfs_measurement_lists+0x396/= 0x440 kasan_report+0xc2/0x100 ? create_securityfs_measurement_lists+0x396/0= x440 create_securityfs_measurement_lists+0x396/0x440 ima_fs_init+0xa3/0x300=
    ima_init+0x7d/0xd0 init_ima+0x28/0x100 do_one_initcall+0xa6/0x3e0 kernel_i= nit_freeable+0x455/0x740 kernel_init+0x24/0x1d0 ret_from_fork+0x38/0x80 ret= _from_fork_asm+0x11/0x20 </TASK> The buggy address belongs to the variable:=
    hash_algo_name+0xb8/0x420 Memory state around the buggy address: ffffffff8= 3e18000: 00 01 f9 f9 f9 f9 f9 f9 00 01 f9 f9 f9 f9 f9 f9 ffffffff83e18080: =
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffffff83e18100: 00 00 00=
    00 00 00 00 f9 f9 f9 f9 f9 00 05 f9 f9 ^ ffffffff83e18180: f9 f9 f9 f9 00 =
    00 00 00 00 00 00 04 f9 f9 f9 f9 ffffffff83e18200: 00 00 00 00 00 00 00 00 =
    04 f9 f9 f9 f9 f9 f9 f9 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Se= ems like the TPM chip supports sha3_256, which isn't yet in tpm_algorithms:=
    tpm tpm0: TPM with unsupported bank algorithm 0x0027 That's TPM_ALG_SHA3_2=
    56 =3D=3D 0x0027 from "Trusted Platform Module 2.0 Library Part 2: Structur= es", page 51 [1]. See also the related U-Boot algorithms update [2]. Thus s= olve the problem by creating a file name with "_tpm_alg_<ID>" postfix if th=
    e crypto algorithm isn't initialized. This is how it looks on the test mach= ine (patch ported to v6.12 release): # ls -1 /sys/kernel/security/ima/ asci= i_runtime_measurements ascii_runtime_measurements_tpm_alg_27 ascii_runtime_= measurements_sha1 ascii_runtime_measurements_sha256 binary_runtime_measurem= ents binary_runtime_measurements_tpm_alg_27 binary_runtime_measurements_sha=
    1 binary_runtime_measurements_sha256 policy runtime_measurements_count viol= ations [1]: https://trustedcomputinggroup.org/wp-content/uploads/Trusted-Pl= atform-Module-2.0-Library-Part-2-Version-184_pub.pdf [2]: https://lists.den= x.de/pipermail/u-boot/2024-July/558835.html 2026-06-24 not yet calculated C= VE-2026-53038 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53038 ] Linux--= Linux In the Linux kernel, the following vulnerability has been resolved: o= cfs2: validate group add input before caching [BUG] OCFS2_IOC_GROUP_ADD can=
    trigger a BUG_ON in ocfs2_set_new_buffer_uptodate(): kernel BUG at fs/ocfs= 2/uptodate.c:509! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010= :ocfs2_set_new_buffer_uptodate+0x194/0x1e0 fs/ocfs2/uptodate.c:509 Code: ff= ffe88f 42b9fe4c 89e64889 dfe8b4df Call Trace: ocfs2_group_add+0x3f1/0x1510 = fs/ocfs2/resize.c:507 ocfs2_ioctl+0x309/0x6e0 fs/ocfs2/ioctl.c:887 vfs_ioct=
    l fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_io= ctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x197/0x1e0 fs/ioctl.c:583 x64_= sys_call+0x1144/0x26a0 arch/x86/include/generated/asm/syscalls_64.h:17 do_s= yscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x93/0xf80=
    arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e RI=
    P: 0033:0x7bbfb55a966d [CAUSE] ocfs2_group_add() calls ocfs2_set_new_buffer= _uptodate() on a user-controlled group block before ocfs2_verify_group_and_= input() validates that block number. That helper is only valid for newly al= located metadata and asserts that the block is not already present in the c= hosen metadata cache. The code also uses INODE_CACHE(inode) even though the=
    group descriptor belongs to main_bm_inode and later journal accesses use t= hat cache context instead. [FIX] Validate the on-disk group descriptor befo=
    re caching it, then add it to the metadata cache tracked by INODE_CACHE(mai= n_bm_inode). Keep the validation failure path separate from the later clean=
    up path so we only remove the buffer from that cache after it has actually = been inserted. This keeps the group buffer lifetime consistent across valid= ation, journaling, and cleanup. 2026-06-24 not yet calculated CVE-2026-5303=
    9 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53039 ] Linux--Linux In the=
    Linux kernel, the following vulnerability has been resolved: fwctl: Fix cl= ass init ordering to avoid NULL pointer dereference on device removal CXL i=
    s linked before fwctl in drivers/Makefile. Both use `module_init, so `cxl_p= ci_driver_init()` runs first. When `cxl_pci_probe()` calls `fwctl_register(=
    )` and then `device_add()`, fwctl_class is not yet registered because fwctl= _init() hasn't run, causing `class_to_subsys()` to return NULL and skip kno= de_class initialization. On device removal, `class_to_subsys()` returns non= -NULL, and `device_del()` calls `klist_del()` on the uninitialized knode, t= riggering a NULL pointer dereference. 2026-06-24 not yet calculated CVE-202= 6-53042 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53042 ] Linux--Linux =
    In the Linux kernel, the following vulnerability has been resolved: efi/cap= sule-loader: fix incorrect sizeof in phys array reallocation The krealloc()=
    call for cap_info->phys in __efi_capsule_setup_info() uses sizeof(phys_add= r_t *) instead of sizeof(phys_addr_t), which might be causing an undersized=
    allocation. The allocation is also inconsistent with the initial array all= ocation in efi_capsule_open() that allocates one entry with sizeof(phys_add= r_t), and the efi_capsule_write() function that stores phys_addr_t values (= not pointers) via page_to_phys(). On 64-bit systems where sizeof(phys_addr_=
    t) =3D=3D sizeof(phys_addr_t *), this goes unnoticed. On 32-bit systems wit=
    h PAE where phys_addr_t is 64-bit but pointers are 32-bit, this allocates h= alf the required space, which might lead to a heap buffer overflow when sto= ring physical addresses. This is similar to the bug fixed in commit fccfa64= 6ef36 ("efi/capsule-loader: fix incorrect allocation size") which fixed the=
    same issue at the initial allocation site. 2026-06-24 not yet calculated C= VE-2026-53047 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53047 ] Linux--= Linux In the Linux kernel, the following vulnerability has been resolved: g= fs2: prevent NULL pointer dereference during unmount When flushing out outs= tanding glock work during an unmount, gfs2_log_flush() can be called when s= dp->sd_jdesc has already been deallocated and sdp->sd_jdesc is NULL. Commit=
    35264909e9d1 ("gfs2: Fix NULL pointer dereference in gfs2_log_flush") adde=
    d a check for that to gfs2_log_flush() itself, but it missed the sdp->sd_jd= esc dereference in gfs2_log_release(). Fix that. 2026-06-24 not yet calcula= ted CVE-2026-53048 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53048 ] Li= nux--Linux In the Linux kernel, the following vulnerability has been resolv= ed: PCI: tegra194: Fix CBB timeout caused by DBI access before core power-o=
    n When PERST# is deasserted twice (assert -> deassert -> assert -> deassert=
    ), a CBB (Control Backbone) timeout occurs at DBI register offset 0x8bc (PC= IE_MISC_CONTROL_1_OFF). This happens because pci_epc_deinit_notify() and dw= _pcie_ep_cleanup() are called before reset_control_deassert() powers on the=
    controller core. The call chain that causes the timeout: pex_ep_event_pex_= rst_deassert() pci_epc_deinit_notify() pci_epf_test_epc_deinit() pci_epf_te= st_clear_bar() pci_epc_clear_bar() dw_pcie_ep_clear_bar() __dw_pcie_ep_rese= t_bar() dw_pcie_dbi_ro_wr_en() <- Accesses 0x8bc DBI register reset_control= _deassert(pcie->core_rst) <- Core powered on HERE The DBI registers, includ= ing PCIE_MISC_CONTROL_1_OFF (0x8bc), are only accessible after the controll=
    er core is powered on via reset_control_deassert(pcie->core_rst). Accessing=
    them before this point results in a CBB timeout because the hardware is no=
    t yet operational. Fix this by moving pci_epc_deinit_notify() and dw_pcie_e= p_cleanup() to after reset_control_deassert(pcie->core_rst), ensuring the c= ontroller is fully powered on before any DBI register accesses occur. 2026-= 06-24 not yet calculated CVE-2026-53051 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53051 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: ASoC: qcom: qdsp6: topology: check widget type be= fore accessing data Check widget type before accessing the private data, as=
    this could a virtual widget which is no associated with a dsp graph, conta= iner and module. Accessing witout check could lead to incorrect memory acce= ss. 2026-06-24 not yet calculated CVE-2026-53052 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-53052 ] Linux--Linux In the Linux kernel, the following=
    vulnerability has been resolved: drm/msm/dpu: fix mismatch between power a=
    nd frequency During DPU runtime suspend, calling dev_pm_opp_set_rate(dev, 0=
    ) drops the MMCX rail to MIN_SVS while the core clock frequency remains at = its original (highest) rate. When runtime resume re-enables the clock, this=
    may result in a mismatch between the rail voltage and the clock rate. For = example, in the DPU bind path, the sequence could be: cpu0: dev_sync_state =
    rpmhpd_sync_state cpu1: dpu_kms_hw_init timeline 0 ---------------------=
    ---------------------------> t After rpmhpd_sync_state, the voltage perform= ance is no longer guaranteed to stay at the highest level. During dpu_kms_h= w_init, calling dev_pm_opp_set_rate(dev, 0) drops the voltage, causing the = MMCX rail to fall to MIN_SVS while the core clock is still at its maximum f= requency. When the power is re-enabled, only the clock is enabled, leading =
    to a situation where the MMCX rail is at MIN_SVS but the core clock is at i=
    ts highest rate. In this state, the rail cannot sustain the clock rate, whi=
    ch may cause instability or system crash. Remove the call to dev_pm_opp_set= _rate(dev, 0) from dpu_runtime_suspend to ensure the correct vote is restor=
    ed when DPU resumes. Patchwork: https://patchwork.freedesktop.org/patch/710= 077/ 2026-06-24 not yet calculated CVE-2026-53056 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-53056 ] Linux--Linux In the Linux kernel, the followin=
    g vulnerability has been resolved: drm/bridge: cadence: cdns-mhdp8546-core:=
    Set the mhdp connector earlier in atomic_enable() In case if we get errors=
    in cdns_mhdp_link_up() or cdns_mhdp_reg_read() in atomic_enable, we will g=
    o to cdns_mhdp_modeset_retry_fn() and will hit NULL pointer while trying to=
    access the mutex. We need the connector to be set before that. Unlike in l= egacy cases with flag !DRM_BRIDGE_ATTACH_NO_CONNECTOR, we do not have conne= ctor initialised in bridge_attach(), so add the mhdp->connector_ptr in devi=
    ce structure to handle both cases with DRM_BRIDGE_ATTACH_NO_CONNECTOR and != DRM_BRIDGE_ATTACH_NO_CONNECTOR, set it in atomic_enable() earlier to avoid = possible NULL pointer dereference in recovery paths like modeset_retry_fn()=
    with the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag set. 2026-06-24 not yet calcu= lated CVE-2026-53058 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53058 ] = Linux--Linux In the Linux kernel, the following vulnerability has been reso= lved: dm log: fix out-of-bounds write due to region_count overflow The loca=
    l variable region_count in create_log_context() is declared as unsigned int=
    (32-bit), but dm_sector_div_up() returns sector_t (64-bit). When a device-= mapper target has a sufficiently large ti->len with a small region_size, th=
    e division result can exceed UINT_MAX. The truncated value is then used to = calculate bitset_size, causing clean_bits, sync_bits, and recovering_bits t=
    o be allocated far smaller than needed for the actual number of regions. Su= bsequent log operations (log_set_bit, log_clear_bit, log_test_bit) use regi=
    on indices derived from the full untruncated region space, causing out-of-b= ounds writes to kernel heap memory allocated by vmalloc. This can be reprod= uced by creating a mirror target whose region_count overflows 32 bits: dmse= tup create bigzero --table '0 8589934594 zero' dmsetup create mymirror --ta= ble '0 8589934594 mirror \ core 2 2 nosync 2 /dev/mapper/bigzero 0 \ /dev/m= apper/bigzero 0' The status output confirms the truncation (sync_count=3D1 = instead of 4294967297, because 0x100000001 was truncated to 1): $ dmsetup s= tatus mymirror 0 8589934594 mirror 2 254:1 254:1 1/4294967297 ... This lead=
    s to a kernel crash in core_in_sync: BUG: scheduling while atomic: (udev-wo= rker)/9150/0x00000000 RIP: 0010:core_in_sync+0x14/0x30 [dm_log] CR2: 000000= 0000000008 Fixing recursive fault but reboot is needed! Fix by widening the=
    local region_count to sector_t and adding an explicit overflow check befor=
    e the value is assigned to lc->region_count. 2026-06-24 not yet calculated = CVE-2026-53059 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53059 ] Linux-= -Linux In the Linux kernel, the following vulnerability has been resolved: =
    dm cache metadata: fix memory leak on metadata abort retry When failing to = acquire the root_lock in dm_cache_metadata_abort because the block_manager =
    is read-only, the temporary block_manager created outside the root_lock is = not properly released, causing a memory leak. Reproduce steps: This can be = reproduced by reloading a new table while the metadata is read-only. While = the second call to dm_cache_metadata_abort is caused by lack of support for=
    table preload in dm-cache, mentioned in commit 9b1cc9f251af ("dm cache: sh= are cache-metadata object across inactive and active DM tables"), it expose=
    s the memory leak in dm_cache_metadata_abort when the function is called mu= ltiple times. Specifically, dm-cache fails to sync the new cache object's m= ode during preresume, creating the reproducer condition. This issue could a= lso occur through concurrent metadata_operation_failed calls due to races i=
    n cache mode updates, but the table preload scenario below provides a relia= ble reproducer. 1. Create a cache device with some faulty trailing metadata=
    blocks dmsetup create cmeta <<EOF 0 200 linear /dev/sdc 0 200 7992 error E=
    OF dmsetup create cdata --table "0 131072 linear /dev/sdc 8192" dmsetup cre= ate corig --table "0 262144 linear /dev/sdc 262144" dd if=3D/dev/zero of=3D= /dev/mapper/cmeta bs=3D4k count=3D1 oflag=3Ddirect dmsetup create cache --t= able "0 131072 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/cori=
    g 128 1 writethrough smq 0" 2. Suspend and resume the cache to start a new = metadata transaction and trigger metadata io errors on the next metadata co= mmit. dmsetup suspend cache dmsetup resume cache 3. Write to the cache devi=
    ce to update metadata fio --filename=3D/dev/mapper/cache --name test --rw= =3Drandwrite --bs=3D4k \ --randrepeat=3D0 --direct=3D1 --size 64k 4. Preloa=
    d the same table dmsetup reload cache --table "$(dmsetup table cache)" 5. R= esume the new table. This triggers the memory leak. dmsetup suspend cache d= msetup resume cache kmemleak logs: <snip> unreferenced object 0xffff8880080= c2010 (size 16): comm "dmsetup", pid 132, jiffies 4294982580 hex dump (firs=
    t 16 bytes): 00 38 b9 07 80 88 ff ff 6a 6b 6b 6b 6b 6b 6b a5 ... backtrace = (crc 3118f31c): kmemleak_alloc+0x28/0x40 __kmalloc_cache_noprof+0x3d9/0x510=
    dm_block_manager_create+0x51/0x140 dm_cache_metadata_abort+0x85/0x320 meta= data_operation_failed+0x103/0x1e0 cache_preresume+0xacd/0xe70 dm_table_resu= me_targets+0xd3/0x320 __dm_resume+0x1b/0xf0 dm_resume+0x127/0x170 <snip> 20= 26-06-24 not yet calculated CVE-2026-53060 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-53060 ] Linux--Linux In the Linux kernel, the following vulne= rability has been resolved: dm cache: fix dirty mapping checking in passthr= ough mode switching As mentioned in commit 9b1cc9f251af ("dm cache: share c= ache-metadata object across inactive and active DM tables"), dm-cache assum=
    ed table reload occurs after suspension, while LVM's table preload breaks t= his assumption. The dirty mapping check for passthrough mode was designed a= round this assumption and is performed during table creation, causing the c= heck to fail with preload while metadata updates are ongoing. This risks lo= ading dirty mappings into passthrough mode, resulting in data loss. Reprodu=
    ce steps: 1. Create a writeback cache with zero migration_threshold to prod= uce dirty mappings dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" = dmsetup create cdata --table "0 131072 linear /dev/sdc 8192" dmsetup create=
    corig --table "0 262144 linear /dev/sdc 262144" dd if=3D/dev/zero of=3D/de= v/mapper/cmeta bs=3D4k count=3D1 oflag=3Ddirect dmsetup create cache --tabl=
    e "0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 1=
    28 2 metadata2 writeback smq \ 2 migration_threshold 0" 2. Preload a table =
    in passthrough mode dmsetup reload cache --table "0 262144 cache /dev/mappe= r/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough s=
    mq 0" 3. Write to the first cache block to make it dirty fio --filename=3D/= dev/mapper/cache --name=3Dpopulate --rw=3Dwrite --bs=3D4k \ --direct=3D1 --= size=3D64k 4. Resume the inactive table. Now it's possible to load the dirt=
    y block into passthrough mode. dmsetup resume cache Fix by moving the check=
    s to the preresume phase to support table preloading. Also remove the unuse=
    d function dm_cache_metadata_all_clean. 2026-06-24 not yet calculated CVE-2= 026-53061 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53061 ] Linux--Linu=
    x In the Linux kernel, the following vulnerability has been resolved: dm ca= che: fix write hang in passthrough mode The invalidate_remove() function ha=
    s incomplete logic for handling write hit bios after cache invalidation. It=
    sets up the remapping for the overwrite_bio but then drops it immediately = without submission, causing write operations to hang. Fix by adding a new i= nvalidate_committed() continuation that submits the remapped writes to the = cache origin after metadata commit completes, while using the overwrite_end=
    io hook to ensure proper completion sequencing. This maintains existing coh= erency. Also improve error handling in invalidate_complete() to preserve th=
    e original error status instead of using bio_io_error() unconditionally. 20= 26-06-24 not yet calculated CVE-2026-53063 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-53063 ] Linux--Linux In the Linux kernel, the following vulne= rability has been resolved: dm cache: fix null-deref with concurrent writes=
    in passthrough mode In passthrough mode, when dm-cache starts to invalidat=
    e a cache entry and bio prison cell lock fails due to concurrent write to t=
    he same cached block, mg->cell remains NULL. The error path in invalidate_c= omplete() attempts to unlock and free the cell unconditionally, causing a N= ULL pointer dereference: KASAN: null-ptr-deref in range [0x0000000000000000= -0x0000000000000007] CPU: 0 UID: 0 PID: 134 Comm: fio Not tainted 6.19.0-rc=
    7 #3 PREEMPT RIP: 0010:dm_cell_unlock_v2+0x3f/0x210 <snip> Call Trace: inva= lidate_complete+0xef/0x430 map_bio+0x130f/0x1a10 cache_map+0x320/0x6b0 __ma= p_bio+0x458/0x510 dm_submit_bio+0x40e/0x16d0 __submit_bio+0x419/0x870 <snip=
    Reproduce steps: 1. Create a cache device dmsetup create cmeta --table "0=
    8192 linear /dev/sdc 0" dmsetup create cdata --table "0 131072 linear /dev= /sdc 8192" dmsetup create corig --table "0 262144 linear /dev/sdc 262144" d=
    d if=3D/dev/zero of=3D/dev/mapper/cmeta bs=3D4k count=3D1 oflag=3Ddirect dm= setup create cache --table "0 262144 cache /dev/mapper/cmeta \ /dev/mapper/= cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" 2. Promote the = first data block into cache fio --filename=3D/dev/mapper/cache --name=3Dpop= ulate --rw=3Dwrite --bs=3D4k \ --direct=3D1 --size=3D64k 3. Reload the cach=
    e into passthrough mode dmsetup suspend cache dmsetup reload cache --table =
    "0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128=
    2 metadata2 passthrough smq 0" dmsetup resume cache 4. Write to the first = cached block concurrently fio --filename=3D/dev/mapper/cache --name test --= rw=3Drandwrite --bs=3D4k \ --randrepeat=3D0 --direct=3D1 --numjobs=3D2 --si=
    ze 64k Fix by checking if mg->cell is valid before attempting to unlock it.=
    2026-06-24 not yet calculated CVE-2026-53064 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-53064 ] Linux--Linux In the Linux kernel, the following vu= lnerability has been resolved: ASoC: sti: use managed regmap_field allocati= ons The regmap_field objects allocated at player init are never freed and m=
    ay leak resources if the driver is removed. Switch to devm_regmap_field_all= oc() to automatically limit the lifetime of the allocations the lifetime of=
    the device. 2026-06-24 not yet calculated CVE-2026-53065 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-53065 ] Linux--Linux In the Linux kernel, the = following vulnerability has been resolved: drm/sun4i: backend: fix error po= inter dereference The function drm_atomic_get_plane_state() can return an e= rror pointer and is not checked for it. Add error pointer check. Detected b=
    y Smatch: drivers/gpu/drm/sun4i/sun4i_backend.c:496 sun4i_backend_atomic_ch= eck() error: 'plane_state' dereferencing possible ERR_PTR() 2026-06-24 not = yet calculated CVE-2026-53066 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -53066 ] Linux--Linux In the Linux kernel, the following vulnerability has = been resolved: PCI: endpoint: pci-ep-msi: Fix error unwind and prevent doub=
    le alloc pci_epf_alloc_doorbell() stores the allocated doorbell message arr=
    ay in epf->db_msg/epf->num_db before requesting MSI vectors. If MSI allocat= ion fails, the array is freed but the EPF state may still point to freed me= mory. Clear epf->db_msg and epf->num_db on the MSI allocation failure path =
    so that later cleanup cannot double-free the array and callers can retry al= location. Also return -EBUSY when doorbells have already been allocated to = prevent leaking or overwriting an existing allocation. 2026-06-24 not yet c= alculated CVE-2026-53067 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5306=
    7 ] Linux--Linux In the Linux kernel, the following vulnerability has been = resolved: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error When hci= _register_dev() fails in hci_uart_register_dev() HCI_UART_PROTO_INIT is not=
    cleared before calling hu->proto->close(hu) and setting hu->hdev to NULL. = This means incoming UART data will reach the protocol-specific recv handler=
    in hci_uart_tty_receive() after resources are freed. Clear HCI_UART_PROTO_= INIT with a write lock before calling hu->proto->close() and setting hu->hd=
    ev to NULL. The write lock ensures all active readers have completed and no=
    new reader can enter the protocol recv path before resources are freed. Th=
    is allows the protocol-specific recv functions to remove the "HCI_UART_REGI= STERED" guard without risking a null pointer dereference if hci_register_de= v() fails. 2026-06-24 not yet calculated CVE-2026-53073 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-53073 ] Linux--Linux In the Linux kernel, the fo= llowing vulnerability has been resolved: bpf: reject short IPv4/IPv6 inputs=
    in bpf_prog_test_run_skb bpf_prog_test_run_skb() calls eth_type_trans() fi= rst and then uses skb->protocol to initialize sk family and address fields = for the test run. For IPv4 and IPv6 packets, it may access ip_hdr(skb) or i= pv6_hdr(skb) even when the provided test input only contains an Ethernet he= ader. Reject the input earlier if the Ethernet frame carries IPv4/IPv6 Ethe= rType but the L3 header is too short. Fold the IPv4/IPv6 header length chec=
    ks into the existing protocol switch and return -EINVAL before accessing th=
    e network headers. 2026-06-24 not yet calculated CVE-2026-53074 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-53074 ] Linux--Linux In the Linux kernel=
    , the following vulnerability has been resolved: net_sched: fix skb memory = leak in deferred qdisc drops When the network stack cleans up the deferred = list via qdisc_run_end(), it operates on the root qdisc. If the root qdisc =
    do not implement the TCQ_F_DEQUEUE_DROPS flag the packets queue to free are=
    never freed and gets stranded on the child's local to_free list. Fix this =
    by making qdisc_dequeue_drop() aware of the root qdisc. It fetches the root=
    qdisc and check for the TCQ_F_DEQUEUE_DROPS flag. If the flag is present, = the packet is appended directly to the root's to_free list. Otherwise, drop=
    it directly as it was done before the optimization was implemented. 2026-0= 6-24 not yet calculated CVE-2026-53079 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53079 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: net/sched: cls_fw: fix NULL dereference of "old" = filters before change() Like pointed out by Sashiko [1], since commit ed76f= 5edccc9 ("net: sched: protect filter_chain list with filter_chain_lock mute= x") TC filters are added to a shared block and published to datapath before=
    their ->change() function is called. This is a problem for cls_fw: an inva= lid filter created with the "old" method can still classify some packets be= fore it is destroyed by the validation logic added by Xiang. Therefore, ins= isting with repeated runs of the following script: # ip link add dev crash0=
    type dummy # ip link set dev crash0 up # mausezahn crash0 -c 100000 -P 10 =
    \ > -A 4.3.2.1 -B 1.2.3.4 -t udp "dp=3D1234" -q & # sleep 1 # tc qdisc add = dev crash0 egress_block 1 clsact # tc filter add block 1 protocol ip prio 1=
    matchall \ > action skbedit mark 65536 continue # tc filter add block 1 pr= otocol ip prio 2 fw # ip link del dev crash0 can still make fw_classify() h=
    it the WARN_ON() in [2]: WARNING: ./include/net/pkt_cls.h:88 at fw_classify= +0x244/0x250 [cls_fw], CPU#18: mausezahn/1399 Modules linked in: cls_fw(E) = act_skbedit(E) CPU: 18 UID: 0 PID: 1399 Comm: mausezahn Tainted: G E 7.0.0-= rc6-virtme #17 PREEMPT(full) Tainted: [E]=3DUNSIGNED_MODULE Hardware name: = Red Hat KVM, BIOS 1.16.3-2.el9 04/01/2014 RIP: 0010:fw_classify+0x244/0x250=
    [cls_fw] Code: 5c 49 c7 45 00 00 00 00 00 41 5d 41 5e 41 5f 5d c3 cc cc cc=
    cc 5b b8 ff ff ff ff 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 90 <0f> 0b =
    90 eb a0 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 RSP: 0018:ffffd= 1b7026bf8a8 EFLAGS: 00010202 RAX: ffff8c5ac9c60800 RBX: ffff8c5ac99322c0 RC=
    X: 0000000000000004 RDX: 0000000000000001 RSI: ffff8c5b74d7a000 RDI: ffff8c= 5ac8284f40 RBP: ffffd1b7026bf8d0 R08: 0000000000000000 R09: ffffd1b7026bf9b=
    0 R10: 00000000ffffffff R11: 0000000000000000 R12: 0000000000010000 R13: ff= ffd1b7026bf930 R14: ffff8c5ac8284f40 R15: 0000000000000000 FS: 00007fca40c3= 7740(0000) GS:ffff8c5b74d7a000(0000) knlGS:0000000000000000 CS: 0010 DS: 00=
    00 ES: 0000 CR0: 0000000080050033 CR2: 00007fca40e822a0 CR3: 0000000005ca00=
    01 CR4: 0000000000172ef0 Call Trace: <TASK> tcf_classify+0x17d/0x5c0 tc_run= +0x9d/0x150 __dev_queue_xmit+0x2ab/0x14d0 ip_finish_output2+0x340/0x8f0 ip_= output+0xa4/0x250 raw_sendmsg+0x147d/0x14b0 __sys_sendto+0x1cc/0x1f0 __x64_= sys_sendto+0x24/0x30 do_syscall_64+0x126/0xf80 entry_SYSCALL_64_after_hwfra= me+0x77/0x7f RIP: 0033:0x7fca40e822ba Code: d8 64 89 02 48 c7 c0 ff ff ff f=
    f eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b=
    8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83=
    ec 30 44 89 RSP: 002b:00007ffc248a42c8 EFLAGS: 00000246 ORIG_RAX: 00000000= 0000002c RAX: ffffffffffffffda RBX: 000055ef233289d0 RCX: 00007fca40e822ba = RDX: 000000000000001e RSI: 000055ef23328c30 RDI: 0000000000000003 RBP: 0000= 55ef233289d0 R08: 00007ffc248a42d0 R09: 0000000000000010 R10: 0000000000000= 000 R11: 0000000000000246 R12: 000000000000001e R13: 00000000000186a0 R14: = 0000000000000000 R15: 00007fca41043000 </TASK> irq event stamp: 1045778 har= dirqs last enabled at (1045784): [<ffffffff864ec042>] __up_console_sem+0x52= /0x60 hardirqs last disabled at (1045789): [<ffffffff864ec027>] __up_consol= e_sem+0x37/0x60 softirqs last enabled at (1045426): [<ffffffff874d48c7>] __= alloc_skb+0x207/0x260 softirqs last disabled at (1045434): [<ffffffff874fe8= f8>] __dev_queue_xmit+0x78/0x14d0 Then, because of the value in the packet'=
    s mark, dereference on 'q->handle' with NULL 'q' occurs: BUG: kernel NULL p= ointer dereference, address: 0000000000000038 [...] RIP: 0010:fw_classify+0= x1fe/0x250 [cls_fw] [...] Skip "old-style" classification on shared blocks,=
    so that the NULL dereference is fixed and WARN_ON() is not hit anymore in = the short lifetime of invalid cls_fw "old-style" filters. [1] https://sashi= ko.dev/#/patchset/2 ---truncated--- 2026-06-24 not yet calculated CVE-2026-= 53080 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53080 ] Linux--Linux In=
    the Linux kernel, the following vulnerability has been resolved: net: hamr= adio: 6pack: fix uninit-value in sixpack_receive_buf sixpack_receive_buf() = does not properly skip bytes with TTY error flags. The while loop iterates = through the flags buffer but never advances the data pointer (cp), and pass=
    es the original count (including error bytes) to sixpack_decode(). This cau= ses sixpack_decode() to process bytes that should have been skipped due to = TTY errors. The TTY layer does not guarantee that cp[i] holds a meaningful = value when fp[i] is set, so passing those positions to sixpack_decode() res= ults in KMSAN reporting an uninit-value read. Fix this by processing bytes = one at a time, advancing cp on each iteration, and only passing valid (non-= error) bytes to sixpack_decode(). This matches the pattern used by slip_rec= eive_buf() and mkiss_receive_buf() for the same purpose. 2026-06-24 not yet=
    calculated CVE-2026-53082 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53= 082 ] Linux--Linux In the Linux kernel, the following vulnerability has bee=
    n resolved: bpf: Fix RCU stall in bpf_fd_array_map_clear() Add a missing co= nd_resched() in bpf_fd_array_map_clear() loop. For PROG_ARRAY maps with man=
    y entries this loop calls prog_array_map_poke_run() per entry which can be = expensive, and without yielding this can cause RCU stalls under load: rcu: = Stack dump where RCU GP kthread last ran: CPU: 0 UID: 0 PID: 30932 Comm: kw= orker/0:2 Not tainted 6.14.0-13195-g967e8def1100 #2 PREEMPT(undef) Workqueu=
    e: events prog_array_map_clear_deferred RIP: 0010:write_comp_data+0x38/0x90=
    kernel/kcov.c:246 Call Trace: <TASK> prog_array_map_poke_run+0x77/0x380 ke= rnel/bpf/arraymap.c:1096 __fd_array_map_delete_elem+0x197/0x310 kernel/bpf/= arraymap.c:925 bpf_fd_array_map_clear kernel/bpf/arraymap.c:1000 [inline] p= rog_array_map_clear_deferred+0x119/0x1b0 kernel/bpf/arraymap.c:1141 process= _one_work+0x898/0x19d0 kernel/workqueue.c:3238 process_scheduled_works kern= el/workqueue.c:3319 [inline] worker_thread+0x770/0x10b0 kernel/workqueue.c:= 3400 kthread+0x465/0x880 kernel/kthread.c:464 ret_from_fork+0x4d/0x80 arch/= x86/kernel/process.c:153 ret_from_fork_asm+0x19/0x30 arch/x86/entry/entry_6= 4.S:245 </TASK> 2026-06-24 not yet calculated CVE-2026-53083 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-53083 ] Linux--Linux In the Linux kernel, t=
    he following vulnerability has been resolved: bpf: return VMA snapshot from=
    task_vma iterator Holding the per-VMA lock across the BPF program body cre= ates a lock ordering problem when helpers acquire locks that depend on mmap= _lock: vm_lock -> i_rwsem -> mmap_lock -> vm_lock Snapshot the VMA under th=
    e per-VMA lock in _next() via memcpy(), then drop the lock before returning=
    . The BPF program accesses only the snapshot. The verifier only trusts vm_m=
    m and vm_file pointers (see BTF_TYPE_SAFE_TRUSTED_OR_NULL in verifier.c). v= m_file is reference- counted with get_file() under the lock and released vi=
    a fput() on the next iteration or in _destroy(). vm_mm is already correct b= ecause lock_vma_under_rcu() verifies vma->vm_mm =3D=3D mm. All other pointe=
    rs are left as-is by memcpy() since the verifier treats them as untrusted. = 2026-06-24 not yet calculated CVE-2026-53084 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-53084 ] Linux--Linux In the Linux kernel, the following vul= nerability has been resolved: bpf: Fix use-after-free in offloaded map/prog=
    info fill When querying info for an offloaded BPF map or program, bpf_map_= offload_info_fill_ns() and bpf_prog_offload_info_fill_ns() obtain the netwo=
    rk namespace with get_net(dev_net(offmap->netdev)). However, the associated=
    netdev's netns may be racing with teardown during netns destruction. If th=
    e netns refcount has already reached 0, get_net() performs a refcount_t inc= rement on 0, triggering: refcount_t: addition on 0; use-after-free. Althoug=
    h rtnl_lock and bpf_devs_lock ensure the netdev pointer remains valid, they=
    cannot prevent the netns refcount from reaching zero. Fix this by using ma= ybe_get_net() instead of get_net(). maybe_get_net() uses refcount_inc_not_z= ero() and returns NULL if the refcount is already zero, which causes ns_get= _path_cb() to fail and the caller to return -ENOENT -- the correct behavior=
    when the netns is being destroyed. 2026-06-24 not yet calculated CVE-2026-= 53089 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53089 ] Linux--Linux In=
    the Linux kernel, the following vulnerability has been resolved: wifi: brc= mfmac: Fix error pointer dereference The function brcmf_chip_add_core() can=
    return an error pointer and is not checked. Add checks for error pointer. = Detected by Smatch: drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c= :1010 brcmf_chip_recognition() error: 'core' dereferencing possible ERR_PTR=
    () drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c:1013 brcmf_chip_= recognition() error: 'core' dereferencing possible ERR_PTR() drivers/net/wi= reless/broadcom/brcm80211/brcmfmac/chip.c:1016 brcmf_chip_recognition() err= or: 'core' dereferencing possible ERR_PTR() drivers/net/wireless/broadcom/b= rcm80211/brcmfmac/chip.c:1019 brcmf_chip_recognition() error: 'core' derefe= rencing possible ERR_PTR() drivers/net/wireless/broadcom/brcm80211/brcmfmac= /chip.c:1022 brcmf_chip_recognition() error: 'core' dereferencing possible = ERR_PTR() [add missing wifi: prefix] 2026-06-24 not yet calculated CVE-2026= -53093 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53093 ] Linux--Linux I=
    n the Linux kernel, the following vulnerability has been resolved: bpf: Fix=
    abuse of kprobe_write_ctx via freplace uprobe programs are allowed to modi=
    fy struct pt_regs. Since the actual program type of uprobe is KPROBE, it ca=
    n be abused to modify struct pt_regs via kprobe+freplace when the kprobe at= taches to kernel functions. For example, SEC("?kprobe") int kprobe(struct p= t_regs *regs) { return 0; } SEC("?freplace") int freplace_kprobe(struct pt_= regs *regs) { regs->di =3D 0; return 0; } freplace_kprobe prog will attach =
    to kprobe prog. kprobe prog will attach to a kernel function. Without this = patch, when the kernel function runs, its first arg will always be set as 0=
    via the freplace_kprobe prog. To fix the abuse of kprobe_write_ctx=3Dtrue = via kprobe+freplace, disallow attaching freplace programs on kprobe program=
    s with different kprobe_write_ctx values. 2026-06-24 not yet calculated CVE= -2026-53095 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53095 ] Linux--Li= nux In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work() When the=
    mt7996 pci chip is detaching, the mt7996_crash_data is released in mt7996_= coredump_unregister(). However, the work item dump_work may still be runnin=
    g or pending, leading to UAF bugs when the already freed crash_data is dere= ferenced again in mt7996_mac_dump_work(). The race condition can occur as f= ollows: CPU 0 (removal path) | CPU 1 (workqueue) mt7996_pci_remove() | mt79= 96_sys_recovery_set() mt7996_unregister_device() | mt7996_reset() mt7996_co= redump_unregister() | queue_work() vfree(dev->coredump.crash_data) | mt7996= _mac_dump_work() | crash_data-> // UAF Fix this by ensuring dump_work is pr= operly canceled before the crash_data is deallocated. Add cancel_work_sync(=
    ) in mt7996_unregister_device() to synchronize with any pending or executin=
    g dump work. 2026-06-24 not yet calculated CVE-2026-53097 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-53097 ] Linux--Linux In the Linux kernel, the = following vulnerability has been resolved: wifi: mt76: mt7915: fix use-afte= r-free bugs in mt7915_mac_dump_work() When the mt7915 pci chip is detaching=
    , the mt7915_crash_data is released in mt7915_coredump_unregister(). Howeve=
    r, the work item dump_work may still be running or pending, leading to UAF = bugs when the already freed crash_data is dereferenced again in mt7915_mac_= dump_work(). The race condition can occur as follows: CPU 0 (removal path) =
    | CPU 1 (workqueue) mt7915_pci_remove() | mt7915_sys_recovery_set() mt7915_= unregister_device() | mt7915_reset() mt7915_coredump_unregister() | queue_w= ork() vfree(dev->coredump.crash_data) | mt7915_mac_dump_work() | crash_data=
    // UAF Fix this by ensuring dump_work is properly canceled before the cr=
    ash_data is deallocated. Add cancel_work_sync() in mt7915_unregister_device=
    () to synchronize with any pending or executing dump work. 2026-06-24 not y=
    et calculated CVE-2026-53098 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 53098 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: bpf: Switch CONFIG_CFI_CLANG to CONFIG_CFI This was renamed i=
    n commit 23ef9d439769 ("kcfi: Rename CONFIG_CFI_CLANG to CONFIG_CFI") as it=
    is now a compiler-agnostic option. Using the wrong name results in the cod=
    e getting compiled out. Meaning the CFI failures for btf_dtor_kfunc_t would=
    still trigger. 2026-06-24 not yet calculated CVE-2026-53099 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-53099 ] Linux--Linux In the Linux kernel, t=
    he following vulnerability has been resolved: wifi: mt76: fix deadlock in r= emain-on-channel mt76_remain_on_channel() and mt76_roc_complete() call mt76= _set_channel() while already holding dev->mutex. Since mt76_set_channel() a= lso acquires dev->mutex, this results in a deadlock. Use __mt76_set_channel=
    () instead of mt76_set_channel(). Add cancel_delayed_work_sync() for mac_wo=
    rk before acquiring the mutex in mt76_remain_on_channel() to prevent a seco= ndary deadlock with the mac_work workqueue. 2026-06-24 not yet calculated C= VE-2026-53100 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53100 ] Linux--= Linux In the Linux kernel, the following vulnerability has been resolved: w= ifi: mt76: mt7921: fix potential deadlock in mt7921_roc_abort_sync roc_abor= t_sync() can deadlock with roc_work(). roc_work() holds dev->mt76.mutex, wh= ile cancel_work_sync() waits for roc_work() to finish. If the caller alread=
    y owns the same mutex, both sides block and no progress is possible. This d= eadlock can occur during station removal when mt76_sta_state() -> mt76_sta_= remove() -> mt7921_mac_sta_remove() -> mt7921_roc_abort_sync() invokes canc= el_work_sync() while roc_work() is still running and holding dev->mt76.mute=
    x. This avoids the mutex deadlock and preserves exactly-once work ownership=
    . 2026-06-24 not yet calculated CVE-2026-53101 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-53101 ] Linux--Linux In the Linux kernel, the following v= ulnerability has been resolved: wifi: mt76: Fix memory leak after mt76_conn= ac_mcu_alloc_sta_req() mt76_connac_mcu_alloc_sta_req() allocates an skb whi=
    ch is expected to be freed eventually by mt76_mcu_skb_send_msg(). However, = currently if an intermediate function fails before sending, the allocated s=
    kb is leaked. Specifically, mt76_connac_mcu_sta_wed_update() and mt76_conna= c_mcu_sta_key_tlv() may fail, leading to an immediate memory leak in the er= ror path. Fix this by explicitly freeing the skb in these error paths. Comm=
    it 7c0f63fe37a5 ("wifi: mt76: mt7996: fix memory leak on mt7996_mcu_sta_key= _tlv error") made a similar change. Compile tested only. Issue found using =
    a prototype static analysis tool and code review. 2026-06-24 not yet calcul= ated CVE-2026-53102 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53102 ] L= inux--Linux In the Linux kernel, the following vulnerability has been resol= ved: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync ro= c_abort_sync() can deadlock with roc_work(). roc_work() holds dev->mt76.mut= ex, while cancel_work_sync() waits for roc_work() to finish. If the caller = already owns the same mutex, both sides block and no progress is possible. = This deadlock can occur during station removal when mt76_sta_state() -> mt7= 6_sta_remove() -> mt7925_mac_sta_remove_link() -> mt7925_mac_link_sta_remov= e() -> mt7925_roc_abort_sync() invokes cancel_work_sync() while roc_work() =
    is still running and holding dev->mt76.mutex. This avoids the mutex deadloc=
    k and preserves exactly-once work ownership. 2026-06-24 not yet calculated = CVE-2026-53103 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53103 ] Linux-= -Linux In the Linux kernel, the following vulnerability has been resolved: = wifi: mt76: Fix memory leak destroying device All MT76 rx queues have an as= sociated page_pool even if the queue is not associated to a NAPI (e.g. WED = RRO queues with WED enabled). Destroy the page_pool running mt76_dma_cleanu=
    p routine during module unload. Moreover returns pages to the page pool if = WED is not enabled for WED RRO queues. 2026-06-24 not yet calculated CVE-20= 26-53104 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53104 ] Linux--Linux=
    In the Linux kernel, the following vulnerability has been resolved: wifi: = mt76: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi Check f=
    or a NULL `vif` before accessing `ieee80211_vif_is_mld(vif)` to avoid a pot= ential kernel panic in scenarios where `vif` might not be initialized. 2026= -06-24 not yet calculated CVE-2026-53105 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53105 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: bpf: Do not allow deleting local storage in NMI C= urrently, local storage may deadlock when deferring freeing selem or local = storage through kfree_rcu(), call_rcu() or call_rcu_tasks_trace() in NMI or=
    reentrant. Since deleting selem in NMI is an unlikely use case, partially = mitigate it by returning error when calling from bpf_xxx_storage_delete() h= elpers in NMI. Note that, it is still possible to deadlock through reentran=
    t. A full mitigation requires returning error when irqs_disabled() is true,=
    which, however is too heavy-handed for bpf_xxx_storage_delete(). The long-= term solution requires _nolock versions of call_rcu. Another possible solut= ion is to defer the free through irq_work [0], but it would grow the size o=
    f selem, which is non-ideal. The check is only needed in bpf_selem_unlink()=
    , which is used by helpers and syscalls. bpf_selem_unlink_nofail() is fine =
    as it is called during map and owner tear down that never run in NMI or ree= ntrant. [0] https://lore.kernel.org/bpf/20260205190233.912-1-alexei.starovo= itov@gmail.com/ 2026-06-24 not yet calculated CVE-2026-53106 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-53106 ] Linux--Linux In the Linux kernel, t=
    he following vulnerability has been resolved: wifi: libertas: don't kill UR=
    Bs in interrupt context Serialization for the TX path was enforced by calli=
    ng usb_kill_urb()/usb_kill_anchored_urbs(), to prevent transmission before =
    a previous URB was completed. usb_tx_block() can be called from interrupt c= ontext (e.g. in the HCD giveback path), so we can't always use it to kill i= n-flight URBs. Prevent sleeping during interrupt context by checking the tx= _submitted anchor for existing URBs. We now return -EBUSY, to indicate ther= e's a pending request. 2026-06-24 not yet calculated CVE-2026-53107 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-53107 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: powerpc/64s: Fix unmap=
    race with PMD migration entries The following race is possible with migrat= ion swap entries or device-private THP entries. e.g. when move_pages is cal= led on a PMD THP page, then there maybe an intermediate state, where PMD en= try acts as a migration swap entry (pmd_present() is true). Then if an munm=
    ap happens at the same time, then this VM_BUG_ON() can happen in pmdp_huge_= get_and_clear_full(). This patch fixes that. Thread A: move_pages() syscall=
    add_folio_for_migration() mmap_read_lock(mm) folio_isolate_lru(folio) mmap= _read_unlock(mm) do_move_pages_to_node() migrate_pages() try_to_migrate_one=
    () spin_lock(ptl) set_pmd_migration_entry() pmdp_invalidate() # PMD: _PAGE_= INVALID | _PAGE_PTE | pfn set_pmd_at() # PMD: migration swap entry (pmd_pre= sent=3D0) spin_unlock(ptl) [page copy phase] # <--- RACE WINDOW --> Thread =
    B: munmap() mmap_write_downgrade(mm) unmap_vmas() -> zap_pmd_range() zap_hu= ge_pmd() __pmd_trans_huge_lock() pmd_is_huge(): # !pmd_present && !pmd_none=
    TRUE (swap entry) pmd_lock() -> # spin_lock(ptl), waits for Thread A to=
    release ptl pmdp_huge_get_and_clear_full() VM_BUG_ON(!pmd_present(*pmdp)) =
    # HITS! [ 287.738700][ T1867] ------------[ cut here ]------------ [ 287.74= 3843][ T1867] kernel BUG at arch/powerpc/mm/book3s64/pgtable.c:187! cpu 0x0=
    : Vector: 700 (Program Check) at [c00000044037f4f0] pc: c000000000094ca4: p= mdp_huge_get_and_clear_full+0x6c/0x23c lr: c000000000645dec: zap_huge_pmd+0= xb0/0x868 sp: c00000044037f790 msr: 800000000282b033 current =3D 0xc0000004= 032c1a00 paca =3D 0xc000000004fe0000 irqmask: 0x03 irq_happened: 0x09 pid =
    =3D 1867, comm =3D a.out kernel BUG at :187! Linux version 6.19.0-12136-g14= 360d4f917c-dirty (powerpc64le-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU =
    ld (GNU Binutils for Debian) 2.40) #27 SMP PREEMPT Sun Feb 22 10:38:56 IST = 2026 enter ? for help [link register ] c000000000645dec zap_huge_pmd+0xb0/0= x868 [c00000044037f790] c00000044037f7d0 (unreliable) [c00000044037f7d0] c0= 00000000645dcc zap_huge_pmd+0x90/0x868 [c00000044037f840] c0000000005724cc = unmap_page_range+0x176c/0x1f40 [c00000044037fa00] c000000000572ea0 unmap_vm= as+0xb0/0x1d8 [c00000044037fa90] c0000000005af254 unmap_region+0xb4/0x128 [= c00000044037fb50] c0000000005af400 vms_complete_munmap_vmas+0x138/0x310 [c0= 0000044037fbe0] c0000000005b0f1c do_vmi_align_munmap+0x1ec/0x238 [c00000044= 037fd30] c0000000005b3688 __vm_munmap+0x170/0x1f8 [c00000044037fdf0] c00000= 0000587f74 sys_munmap+0x2c/0x40 [c00000044037fe10] c000000000032668 system_= call_exception+0x128/0x350 [c00000044037fe50] c00000000000d05c system_call_= vectored_common+0x15c/0x2ec ---- Exception: 3000 (System Call Vectored) at = 0000000010064a2c SP (7fff9b1ee9c0) is in userspace 0:mon> zh commit a30b48b= f1b24 ("mm/migrate_device: implement THP migration of zone device pages"), = enabled migration for device-private PMD entries. Hence this is one other p= ath where this warning could get trigger from. ------------[ cut here ]----= -------- WARNING: arch/powerpc/mm/book3s64/hash_pgtable.c:199 at hash__pmd_= hugepage_update+0x48/0x284, CPU#3: hmm-tests/1905 Modules linked in: test_h=
    mm CPU: 3 UID: 0 PID: 1905 Comm: hmm-tests Tainted: G B W L N 7.0.0-rc1-014= 38-g7e2f0ee7581c #21 PREEMPT Tainted: [B]=3DBAD_PAGE, [W]=3DWARN, [L]=3DSOF= TLOCKUP, [N]=3DTEST Hardware name: IBM pSeries (emulated by qemu) POWER10 (= architected) 0x801200 0xf000006 of:SLOF,git-ee03ae pSeries NIP [c0000000000= 96b70] hash__pmd_hugepage_update+0x48/0x284 LR [c000000000096e7c] hash__pmd= p_huge_get_and_clear+0xd0/0xd4 Call Trace: [c000000604707670] [c000000004e1= 02b8] 0xc000000004e102b8 (unreliable) [c000000604707700] [c00000000064ec3c]=
    set_pmd_migration_entry+0x414/0x498 [c000000604707760] [c00000000063e5a4] = migrate_vma_col ---truncated--- 2026-06-24 not yet calculated CVE-2026-5310=
    8 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53108 ] Linux--Linux In the=
    Linux kernel, the following vulnerability has been resolved: powerpc/pgtab= le-frag: Fix bad page state in pte_frag_destroy powerpc uses pt_frag_refcou=
    nt as a reference counter for tracking it's pte and pmd page table fragment=
    s. For PTE table, in case of Hash with 64K pagesize, we have 16 fragments o=
    f 4K size in one 64K page. Patch series [1] "mm: free retracted page table =
    by RCU" added pte_free_defer() to defer the freeing of PTE tables when retr= act_page_tables() is called for madvise MADV_COLLAPSE on shmem range. [1]: = https://lore.kernel.org/all/7cd843a9-aa80-14f-5eb2-33427363c20@google.com/ = pte_free_defer() sets the active flag on the corresponding fragment's folio=
    & calls pte_fragment_free(), which reduces the pt_frag_refcount. When pt_f= rag_refcount reaches 0 (no active fragment using the folio), it checks if t=
    he folio active flag is set, if set, it calls call_rcu to free the folio, i=
    t the active flag is unset then it calls pte_free_now(). Now, this can lead=
    to following problem in a corner case... [ 265.351553][ T183] BUG: Bad pag=
    e state in process a.out pfn:20d62 [ 265.353555][ T183] page: refcount:0 ma= pcount:0 mapping:0000000000000000 index:0x0 pfn:0x20d62 [ 265.355457][ T183=
    ] flags: 0x3ffff800000100(active|node=3D0|zone=3D0|lastcpupid=3D0x7ffff) [ = 265.358719][ T183] raw: 003ffff800000100 0000000000000000 5deadbeef0000122 = 0000000000000000 [ 265.360177][ T183] raw: 0000000000000000 c0000000119caf5=
    8 00000000ffffffff 0000000000000000 [ 265.361438][ T183] page dumped becaus=
    e: PAGE_FLAGS_CHECK_AT_FREE flag(s) set [ 265.362572][ T183] Modules linked=
    in: [ 265.364622][ T183] CPU: 0 UID: 0 PID: 183 Comm: a.out Not tainted 6.= 18.0-rc3-00141-g1ddeaaace7ff-dirty #53 VOLUNTARY [ 265.364785][ T183] Hardw= are name: IBM pSeries (emulated by qemu) POWER10 (architected) 0x801200 0xf= 000006 of:SLOF,git-ee03ae pSeries [ 265.364908][ T183] Call Trace: [ 265.36= 4955][ T183] [c000000011e6f7c0] [c000000001cfaa18] dump_stack_lvl+0x130/0x1=
    48 (unreliable) [ 265.365202][ T183] [c000000011e6f7f0] [c000000000794758] = bad_page+0xb4/0x1c8 [ 265.365384][ T183] [c000000011e6f890] [c00000000079c0= 20] __free_frozen_pages+0x838/0xd08 [ 265.365554][ T183] [c000000011e6f980]=
    [c0000000000a70ac] pte_frag_destroy+0x298/0x310 [ 265.365729][ T183] [c000= 000011e6fa30] [c0000000000aa764] arch_exit_mmap+0x34/0x218 [ 265.365912][ T= 183] [c000000011e6fa80] [c000000000751698] exit_mmap+0xb8/0x820 [ 265.36608= 0][ T183] [c000000011e6fc30] [c0000000001b1258] __mmput+0x98/0x300 [ 265.36= 6244][ T183] [c000000011e6fc80] [c0000000001c81f8] do_exit+0x470/0x1508 [ 2= 65.366421][ T183] [c000000011e6fd70] [c0000000001c95e4] do_group_exit+0x88/= 0x148 [ 265.366602][ T183] [c000000011e6fdc0] [c0000000001c96ec] pid_child_= should_wake+0x0/0x178 [ 265.366780][ T183] [c000000011e6fdf0] [c00000000003= a270] system_call_exception+0x1b0/0x4e0 [ 265.366958][ T183] [c000000011e6f= e50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec The bad pag=
    e state error occurs when such a folio gets freed (with active flag set), f= rom do_exit() path in parallel. ... this can happen when the pte fragment w=
    as allocated from this folio, but when all the fragments get freed, the pte= _frag_refcount still had some unused fragments. Now, if this process exits,=
    with such folio as it's cached pte_frag in mm->context, then during pte_fr= ag_destroy(), we simply call pagetable_dtor() and pagetable_free(), meaning=
    it doesn't clear the active flag. This, can lead to the above bug. Since w=
    e are anyway in do_exit() path, then if the refcount is 0, then I guess it = should be ok to simply clear the folio active flag before calling pagetable= _dtor() & pagetable_free(). 2026-06-24 not yet calculated CVE-2026-53109 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-53109 ] Linux--Linux In the Lin=
    ux kernel, the following vulnerability has been resolved: bpf: test_run: Fi=
    x the null pointer dereference issue in bpf_lwt_xmit_push_encap The bpf_lwt= _xmit_push_encap helper needs to access skb_dst(skb)->dev to calculate the = needed headroom: err =3D skb_cow_head(skb, len + LL_RESERVED_SPACE(skb_dst(= skb)->dev)); But skb->_skb_refdst may not be initialized when the skb is se=
    t up by bpf_prog_test_run_skb function. Executing bpf_lwt_push_ip_encap fun= ction in this scenario will trigger null pointer dereference, causing a ker= nel crash as Yinhao reported: [ 105.186365] BUG: kernel NULL pointer derefe= rence, address: 0000000000000000 [ 105.186382] #PF: supervisor read access =
    in kernel mode [ 105.186388] #PF: error_code(0x0000) - not-present page [ 1= 05.186393] PGD 121d3d067 P4D 121d3d067 PUD 106c83067 PMD 0 [ 105.186404] Oo= ps: 0000 [#1] PREEMPT SMP NOPTI [ 105.186412] CPU: 3 PID: 3250 Comm: poc Kd= ump: loaded Not tainted 6.19.0-rc5 #1 [ 105.186423] Hardware name: QEMU Sta= ndard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 105.1= 86427] RIP: 0010:bpf_lwt_push_ip_encap+0x1eb/0x520 [ 105.186443] Code: 0f 8=
    4 de 01 00 00 0f b7 4a 04 66 85 c9 0f 85 47 01 00 00 31 c0 5b 5d 41 5c 41 5=
    d 41 5e c3 cc cc cc cc 48 8b 73 58 48 83 e6 fe <48> 8b 36 0f b7 be ec 00 00=
    00 0f b7 b6 e6 00 00 00 01 fe 83 e6 f0 [ 105.186449] RSP: 0018:ffffbb0e038= 7bc50 EFLAGS: 00010246 [ 105.186455] RAX: 000000000000004e RBX: ffff94c74e0= 36500 RCX: ffff94c74874da00 [ 105.186460] RDX: 0000000000000000 RSI: 000000= 0000000000 RDI: ffff94c74e036500 [ 105.186463] RBP: 0000000000000001 R08: 0= 000000000000002 R09: 0000000000000000 [ 105.186467] R10: ffffbb0e0387bd50 R= 11: 0000000000000000 R12: ffffbb0e0387bc98 [ 105.186471] R13: 0000000000000= 014 R14: 0000000000000000 R15: 0000000000000002 [ 105.186484] FS: 00007f166= aa4d680(0000) GS:ffff94c8b7780000(0000) knlGS:0000000000000000 [ 105.186490=
    ] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 105.186494] CR2: 00000= 00000000000 CR3: 000000015eade001 CR4: 0000000000770ee0 [ 105.186499] PKRU:=
    55555554 [ 105.186502] Call Trace: [ 105.186507] <TASK> [ 105.186513] bpf_= lwt_xmit_push_encap+0x2b/0x40 [ 105.186522] bpf_prog_a75eaad51e517912+0x41/= 0x49 [ 105.186536] ? kvm_clock_get_cycles+0x18/0x30 [ 105.186547] ? ktime_g= et+0x3c/0xa0 [ 105.186554] bpf_test_run+0x195/0x320 [ 105.186563] ? bpf_tes= t_run+0x10f/0x320 [ 105.186579] bpf_prog_test_run_skb+0x2f5/0x4f0 [ 105.186= 590] __sys_bpf+0x69c/0xa40 [ 105.186603] __x64_sys_bpf+0x1e/0x30 [ 105.1866= 11] do_syscall_64+0x59/0x110 [ 105.186620] entry_SYSCALL_64_after_hwframe+0= x76/0xe0 [ 105.186649] RIP: 0033:0x7f166a97455d Temporarily add the setting=
    of skb->_skb_refdst before bpf_test_run to resolve the issue. 2026-06-24 n=
    ot yet calculated CVE-2026-53111 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-53111 ] Linux--Linux In the Linux kernel, the following vulnerability h=
    as been resolved: wifi: rtlwifi: pci: fix possible use-after-free caused by=
    unfinished irq_prepare_bcn_tasklet The irq_prepare_bcn_tasklet is initiali= zed in rtl_pci_init() and scheduled when RTL_IMR_BCNINT interrupt is trigge= red by hardware. But it is never killed in rtl_pci_deinit(). When the rtlwi=
    fi card probe fails or is being detached, the ieee80211_hw is deallocated. = However, irq_prepare_bcn_tasklet may still be running or pending, leading t=
    o use-after-free when the freed ieee80211_hw is accessed in _rtl_pci_prepar= e_bcn_tasklet(). Similar to irq_tasklet, add tasklet_kill() in rtl_pci_dein= it() to ensure that irq_prepare_bcn_tasklet is properly terminated before t=
    he ieee80211_hw is released. The issue was identified through static analys= is. 2026-06-24 not yet calculated CVE-2026-53112 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-53112 ] Linux--Linux In the Linux kernel, the following=
    vulnerability has been resolved: wifi: ath11k: fix memory leaks in beacon = template setup The functions ath11k_mac_setup_bcn_tmpl_ema() and ath11k_mac= _setup_bcn_tmpl_mbssid() allocate memory for beacon templates but fail to f= ree it when parameter setup returns an error. Since beacon templates must b=
    e released during normal execution, they must also be released in the error=
    handling paths to prevent memory leaks. Fix this by using unified exit pat=
    hs with proper cleanup in the respective error paths. Compile tested only. = Issue found using a prototype static analysis tool and code review. 2026-06= -24 not yet calculated CVE-2026-53113 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-53113 ] Linux--Linux In the Linux kernel, the following vulnerabil= ity has been resolved: perf/amd/ibs: Avoid calling perf_allow_kernel() from=
    the IBS NMI handler Calling perf_allow_kernel() from the NMI context is un= safe and could be fatal. Capture the permission at event-initialization tim=
    e by storing it in event->hw.flags, and have the NMI handler rely on that c= ached flag instead of making the call directly. 2026-06-24 not yet calculat=
    ed CVE-2026-53114 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53114 ] Lin= ux--Linux In the Linux kernel, the following vulnerability has been resolve=
    d: bus: fsl-mc: use generic driver_override infrastructure When a driver is=
    probed through __driver_attach(), the bus' match() callback is called with= out the device lock held, thus accessing the driver_override field without =
    a lock, which can cause a UAF. Fix this by using the driver-core driver_ove= rride infrastructure taking care of proper locking internally. Note that ca= lling match() from __driver_attach() without the device lock held is intent= ional. [1] 2026-06-24 not yet calculated CVE-2026-53115 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-53115 ] Linux--Linux In the Linux kernel, the fo= llowing vulnerability has been resolved: s390/ap: use generic driver_overri=
    de infrastructure When the AP masks are updated via apmask_store() or aqmas= k_store(), ap_bus_revise_bindings() is called after ap_attr_mutex has been = released. This calls __ap_revise_reserved(), which accesses the driver_over= ride field without holding any lock, racing against a concurrent driver_ove= rride_store() that may free the old string, resulting in a potential UAF. F=
    ix this by using the driver-core driver_override infrastructure, which prot= ects all accesses with an internal spinlock. Note that unlike most other bu= ses, the AP bus does not check driver_override in its match() callback; the=
    override is checked in ap_device_probe() and __ap_revise_reserved() instea=
    d. Also note that we do not enable the driver_override feature of struct bu= s_type, as AP - in contrast to most other buses - passes "" to sysfs_emit()=
    when the driver_override pointer is NULL. Thus, printing "\n" instead of "= (null)\n". Additionally, AP has a custom counter that is modified in the co= rresponding custom driver_override_store(). 2026-06-24 not yet calculated C= VE-2026-53116 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53116 ] Linux--= Linux In the Linux kernel, the following vulnerability has been resolved: s= 390/cio: use generic driver_override infrastructure When a driver is probed=
    through __driver_attach(), the bus' match() callback is called without the=
    device lock held, thus accessing the driver_override field without a lock,=
    which can cause a UAF. Fix this by using the driver-core driver_override i= nfrastructure taking care of proper locking internally. Note that calling m= atch() from __driver_attach() without the device lock held is intentional. = [1] 2026-06-24 not yet calculated CVE-2026-53117 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-53117 ] Linux--Linux In the Linux kernel, the following=
    vulnerability has been resolved: vdpa: use generic driver_override infrast= ructure When a driver is probed through __driver_attach(), the bus' match()=
    callback is called without the device lock held, thus accessing the driver= _override field without a lock, which can cause a UAF. Fix this by using th=
    e driver-core driver_override infrastructure taking care of proper locking = internally. Note that calling match() from __driver_attach() without the de= vice lock held is intentional. [1] 2026-06-24 not yet calculated CVE-2026-5= 3118 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53118 ] Linux--Linux In = the Linux kernel, the following vulnerability has been resolved: platform/w= mi: use generic driver_override infrastructure When a driver is probed thro= ugh __driver_attach(), the bus' match() callback is called without the devi=
    ce lock held, thus accessing the driver_override field without a lock, whic=
    h can cause a UAF. Fix this by using the driver-core driver_override infras= tructure taking care of proper locking internally. Note that calling match(=
    ) from __driver_attach() without the device lock held is intentional. [1] 2= 026-06-24 not yet calculated CVE-2026-53119 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-53119 ] Linux--Linux In the Linux kernel, the following vuln= erability has been resolved: PCI: use generic driver_override infrastructur=
    e When a driver is probed through __driver_attach(), the bus' match() callb= ack is called without the device lock held, thus accessing the driver_overr= ide field without a lock, which can cause a UAF. Fix this by using the driv= er-core driver_override infrastructure taking care of proper locking intern= ally. Note that calling match() from __driver_attach() without the device l= ock held is intentional. [1] 2026-06-24 not yet calculated CVE-2026-53120 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-53120 ] Linux--Linux In the Li= nux kernel, the following vulnerability has been resolved: amd-pstate: Fix = memory leak in amd_pstate_epp_cpu_init() On failure to set the epp, the fun= ction amd_pstate_epp_cpu_init() returns with an error code without freeing = the cpudata object that was allocated at the beginning of the function. Ens= ure that the cpudata object is freed before returning from the function. Th=
    is memory leak was discovered by Claude Opus 4.6 with the aid of Chris Maso= n's AI review-prompts (https://github.com/masoncl/review-prompts/tree/main/= kernel). 2026-06-24 not yet calculated CVE-2026-53121 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-53121 ] Linux--Linux In the Linux kernel, the foll= owing vulnerability has been resolved: btrfs: fix deadlock between reflink = and transaction commit when using flushoncommit When using the flushoncommi=
    t mount option, we can have a deadlock between a transaction commit and a r= eflink operation that copied an inline extent to an offset beyond the curre=
    nt i_size of the destination node. The deadlock happens like this: 1) Task =
    A clones an inline extent from inode X to an offset of inode Y that is beyo=
    nd Y's current i_size. This means we copied the inline extent's data to a f= olio of inode Y that is beyond its EOF, using a call to copy_inline_to_page= (); 2) Task B starts a transaction commit and calls btrfs_start_delalloc_fl= ush() to flush delalloc; 3) The delalloc flushing sees the new dirty folio =
    of inode Y and when it attempts to flush it, it ends up at extent_writepage=
    () and sees that the offset of the folio is beyond the i_size of inode Y, s=
    o it attempts to invalidate the folio by calling folio_invalidate(), which = ends up at btrfs' folio invalidate callback - btrfs_invalidate_folio(). The=
    re it tries to lock the folio's range in inode Y's extent io tree, but it b= locks since it's currently locked by task A - during a reflink we lock the = inodes and the source and destination ranges after flushing all delalloc an=
    d waiting for ordered extent completion - after that we don't expect to hav=
    e dirty folios in the ranges, the exception is if we have to copy an inline=
    extent's data (because the destination offset is not zero); 4) Task A then=
    attempts to start a transaction to update the inode item, and then it's bl= ocked since the current transaction is in the TRANS_STATE_COMMIT_START stat=
    e. Therefore task A has to wait for the current transaction to become unblo= cked (its state >=3D TRANS_STATE_UNBLOCKED). So task A is waiting for the t= ransaction commit done by task B, and the later waiting on the extent lock =
    of inode Y that is currently held by task A. Syzbot recently reported this = with the following stack traces: INFO: task kworker/u8:7:1053 blocked for m= ore than 143 seconds. Not tainted syzkaller #0 "echo 0 > /proc/sys/kernel/h= ung_task_timeout_secs" disables this message. task:kworker/u8:7 state:D sta= ck:23520 pid:1053 tgid:1053 ppid:2 task_flags:0x4208060 flags:0x00080000 Wo= rkqueue: writeback wb_workfn (flush-btrfs-46) Call Trace: <TASK> context_sw= itch kernel/sched/core.c:5298 [inline] __schedule+0x1553/0x5240 kernel/sche= d/core.c:6911 __schedule_loop kernel/sched/core.c:6993 [inline] schedule+0x= 164/0x360 kernel/sched/core.c:7008 wait_extent_bit fs/btrfs/extent-io-tree.= c:811 [inline] btrfs_lock_extent_bits+0x59c/0x700 fs/btrfs/extent-io-tree.c= :1914 btrfs_lock_extent fs/btrfs/extent-io-tree.h:152 [inline] btrfs_invali= date_folio+0x43d/0xc40 fs/btrfs/inode.c:7704 extent_writepage fs/btrfs/exte= nt_io.c:1852 [inline] extent_write_cache_pages fs/btrfs/extent_io.c:2580 [i= nline] btrfs_writepages+0x12ff/0x2440 fs/btrfs/extent_io.c:2713 do_writepag= es+0x32e/0x550 mm/page-writeback.c:2554 __writeback_single_inode+0x133/0x11=
    a0 fs/fs-writeback.c:1750 writeback_sb_inodes+0x995/0x19d0 fs/fs-writeback.= c:2042 wb_writeback+0x456/0xb70 fs/fs-writeback.c:2227 wb_do_writeback fs/f= s-writeback.c:2374 [inline] wb_workfn+0x41a/0xf60 fs/fs-writeback.c:2414 pr= ocess_one_work kernel/workqueue.c:3276 [inline] process_scheduled_works+0xb= 6e/0x18c0 kernel/workqueue.c:3359 worker_thread+0xa53/0xfc0 kernel/workqueu= e.c:3440 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x51e/0xb90=
    arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/e= ntry_64.S:245 </TASK> INFO: task syz.4.64:6910 blocked for more than 143 se= conds. Not tainted syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeou= t_secs" disables this message. task:syz.4.64 state:D stack:22752 pid:6910 t= gid: ---truncated--- 2026-06-24 not yet calculated CVE-2026-53122 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-53122 ] Linux--Linux In the Linux kern= el, the following vulnerability has been resolved: md: wake raid456 reshape=
    waiters before suspend During raid456 reshape, direct IO across the reshap=
    e position can sleep in raid5_make_request() waiting for reshape progress w= hile still holding an active_io reference. If userspace then freezes reshap=
    e and writes md/suspend_lo or md/suspend_hi, mddev_suspend() kills active_i=
    o and waits for all in-flight IO to drain. This can deadlock: the IO needs = reshape progress to continue, but the reshape thread is already frozen, so = the active_io reference is never dropped and suspend never completes. raid5= _prepare_suspend() already wakes wait_for_reshape for dm-raid. Do the same = for normal md suspend when reshape is already interrupted, so waiting raid4=
    56 IO can abort, drop its reference, and let suspend finish. The mdadm test=
    tests/25raid456-reshape-deadlock reproduces the hang. 2026-06-24 not yet c= alculated CVE-2026-53123 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5312=
    3 ] Linux--Linux In the Linux kernel, the following vulnerability has been = resolved: ublk: reset per-IO canceled flag on each fetch If a ublk server s= tarts recovering devices but dies before issuing fetch commands for all IOs=
    , cancellation of the fetch commands that were successfully issued may neve=
    r complete. This is because the per-IO canceled flag can remain set even af= ter the fetch for that IO has been submitted - the per-IO canceled flags fo=
    r all IOs in a queue are reset together only once all IOs for that queue ha=
    ve been fetched. So if a nonempty proper subset of the IOs for a queue are = fetched when the ublk server dies, the IOs in that subset will never succes= sfully be canceled, as their canceled flags remain set, and this prevents u= blk_cancel_cmd from actually calling io_uring_cmd_done on the commands, des= pite the fact that they are outstanding. Fix this by resetting the per-IO c= ancel flags immediately when each IO is fetched instead of waiting for all = IOs for the queue (which may never happen). 2026-06-24 not yet calculated C= VE-2026-53124 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53124 ] Linux--= Linux In the Linux kernel, the following vulnerability has been resolved: m=
    d: fix array_state=3Dclear sysfs deadlock When "clear" is written to array_= state, md_attr_store() breaks sysfs active protection so the array can dele=
    te itself from its own sysfs store method. However, md_attr_store() current=
    ly drops the mddev reference before calling sysfs_unbreak_active_protection= (). Once do_md_stop(..., 0) has made the mddev eligible for delayed deletio=
    n, the temporary kobject reference taken by sysfs_break_active_protection()=
    can become the last kobject reference protecting the md kobject. That allo=
    ws sysfs_unbreak_active_protection() to drop the last kobject reference fro=
    m the current sysfs writer context. kobject teardown then recurses into ker= nfs removal while the current sysfs node is still being unwound, and lockde=
    p reports recursive locking on kn->active with kernfs_drain() in the call c= hain. Reproducer on an existing level: 1. Create an md0 linear array and ac= tivate it: mknod /dev/md0 b 9 0 echo none > /sys/block/md0/md/metadata_vers= ion echo linear > /sys/block/md0/md/level echo 1 > /sys/block/md0/md/raid_d= isks echo "$(cat /sys/class/block/sdb/dev)" > /sys/block/md0/md/new_dev ech=
    o "$(($(cat /sys/class/block/sdb/size) / 2))" > \ /sys/block/md0/md/dev-sdb= /size echo 0 > /sys/block/md0/md/dev-sdb/slot echo active > /sys/block/md0/= md/array_state 2. Wait briefly for the array to settle, then clear it: slee=
    p 2 echo clear > /sys/block/md0/md/array_state The warning looks like: WARN= ING: possible recursive locking detected bash/588 is trying to acquire lock=
    : (kn->active#65) at __kernfs_remove+0x157/0x1d0 but task is already holdin=
    g lock: (kn->active#65) at sysfs_unbreak_active_protection+0x1f/0x40 ... Ca=
    ll Trace: kernfs_drain __kernfs_remove kernfs_remove_by_name_ns sysfs_remov= e_group sysfs_remove_groups __kobject_del kobject_put md_attr_store kernfs_= fop_write_iter vfs_write ksys_write Restore active protection before mddev_= put() so the extra sysfs kobject reference is dropped while the mddev is st= ill held alive. The actual md kobject deletion is then deferred until after=
    the sysfs write path has fully returned. 2026-06-24 not yet calculated CVE= -2026-53125 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53125 ] Linux--Li= nux In the Linux kernel, the following vulnerability has been resolved: blk= -cgroup: fix disk reference leak in blkcg_maybe_throttle_current() Add the = missing put_disk() on the error path in blkcg_maybe_throttle_current(). Whe=
    n blkcg lookup, blkg lookup, or blkg_tryget() fails, the function jumps to = the out label which only calls rcu_read_unlock() but does not release the d= isk reference acquired by blkcg_schedule_throttle() via get_device(). Since=
    current->throttle_disk is already set to NULL before the lookup, blkcg_exi= t() cannot release this reference either, causing the disk to never be free=
    d. Restore the reference release that was present as blk_put_queue() in the=
    original code but was inadvertently dropped during the conversion from req= uest_queue to gendisk. 2026-06-24 not yet calculated CVE-2026-53126 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-53126 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: block: fix zones_cond = memory leak on zone revalidation error paths When blk_revalidate_disk_zones=
    () fails after disk_revalidate_zone_resources() has allocated args.zones_co= nd, the memory is leaked because no error path frees it. 2026-06-24 not yet=
    calculated CVE-2026-53127 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53= 127 ] Linux--Linux In the Linux kernel, the following vulnerability has bee=
    n resolved: drbd: Balance RCU calls in drbd_adm_dump_devices() Make drbd_ad= m_dump_devices() call rcu_read_lock() before rcu_read_unlock() is called. T= his has been detected by the Clang thread-safety analyzer. 2026-06-24 not y=
    et calculated CVE-2026-53128 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 53128 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: fs/mbcache: cancel shrink work before destroying the cache mb= _cache_destroy() calls shrinker_free() and then frees all cache entries and=
    the cache itself, but it does not cancel the pending c_shrink_work work it=
    em first. If mb_cache_entry_create() schedules c_shrink_work via schedule_w= ork() and the work item is still pending or running when mb_cache_destroy()=
    runs, mb_cache_shrink_worker() will access the cache after its memory has = been freed, causing a use-after-free. This is only reachable by a privilege=
    d user (root or CAP_SYS_ADMIN) who can trigger the last put of a mounted ex= t2/ext4/ocfs2 filesystem. Cancel the work item with cancel_work_sync() befo=
    re calling shrinker_free(), ensuring the worker has finished and will not b=
    e rescheduled before the cache is torn down. 2026-06-24 not yet calculated = CVE-2026-53129 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53129 ] Linux-= -Linux In the Linux kernel, the following vulnerability has been resolved: = netfilter: nft_fib: fix stale stack leak via the OIFNAME register For NFT_F= IB_RESULT_OIFNAME the destination register is declared with len =3D IFNAMSI=
    Z (four 32-bit registers), but on the lookup-fail, RTN_LOCAL and oif-mismat=
    ch paths nft_fib{4,6}_eval() only writes one register via "*dest =3D 0". Th=
    e remaining three registers are left as whatever was on the stack in nft_do= _chain()'s struct nft_regs, and a downstream expression that loads the regi= ster span can leak that uninitialised kernel stack to userspace. The NFTA_F= IB_F_PRESENT existence check has the same shape: it is only meaningful for = NFT_FIB_RESULT_OIF, yet it was accepted for any result type while the eval = stores a single byte via nft_reg_store8(), leaving the rest of the declared=
    span stale. Fix both: - replace the bare "*dest =3D 0" in the eval with nf= t_fib_store_result(), which strscpy_pad()s the whole IFNAMSIZ for OIFNAME (= and is already used on the other early-return path), and - restrict NFTA_FI= B_F_PRESENT to NFT_FIB_RESULT_OIF and declare its destination as a single u=
    8, so the marked span matches the one byte the eval writes. 2026-06-25 not = yet calculated CVE-2026-53134 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -53134 ] Linux--Linux In the Linux kernel, the following vulnerability has = been resolved: drm/amd/display: Fix NULL deref and buffer over-read in SDP = debugfs [Why & How] dp_sdp_message_debugfs_write() dereferences connector->= base.state->crtc without checking for NULL. A connector can be connected bu=
    t not bound to any CRTC (e.g. after hot-plug before the next atomic commit)=
    , causing a kernel crash when writing to the sdp_message debugfs node. The = function also ignores the user-provided size argument and always passes 36 = bytes to copy_from_user(), reading past the user buffer when size < 36. Fix=
    both issues by: - Returning -ENODEV when connector->base.state or state->c= rtc is NULL - Clamping write_size to min(size, sizeof(data)) (cherry picked=
    from commit 6ab4c36a522842ff70474a1c0af2e40e50fc8300) 2026-06-25 not yet c= alculated CVE-2026-53135 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5313=
    5 ] Linux--Linux In the Linux kernel, the following vulnerability has been = resolved: drm/amd/display: Clamp VBIOS HDMI retimer register count to array=
    size [Why & How] The VBIOS integrated info tables (v1_11 and v2_1) contain=
    HdmiRegNum and Hdmi6GRegNum fields that are used as loop bounds when copyi=
    ng retimer I2C register settings into fixed-size arrays (dp*_ext_hdmi_reg_s= ettings[9] and dp*_ext_hdmi_6g_reg_settings[3]). These u8 fields are not va= lidated before use, so a malformed VBIOS can specify values up to 255, caus= ing an out-of-bounds heap write during driver probe. Clamp each register co= unt to the destination array size using min_t() before the copy loops, in b= oth get_integrated_info_v11() and get_integrated_info_v2_1(). (cherry picke=
    d from commit 5a7f0ef90195940c54b0f5bb85b87da55f038c69) 2026-06-25 not yet = calculated CVE-2026-53136 [ https://www.cve.org/CVERecord?id=3DCVE-2026-531=
    36 ] Linux--Linux In the Linux kernel, the following vulnerability has been=
    resolved: drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size=
    [Why & How] During HDCP 2.x repeater authentication over HDMI, the driver = reads the sink's RxStatus register and extracts a 10-bit message size field=
    (max value 1023). This value is used as the read length for the ReceiverID=
    list without being clamped to the size of the destination buffer rx_id_lis= t[177]. A malicious HDMI repeater could advertise a message size larger tha=
    n the buffer, causing an out-of-bounds write during the I2C read. Clamp the=
    read length in mod_hdcp_read_rx_id_list() to the size of the rx_id_list bu= ffer, matching the approach already used in the DP branch. (cherry picked f= rom commit 229212219e4247d9486f8ba41ef087358490be09) 2026-06-25 not yet cal= culated CVE-2026-53137 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53137 =
    ] Linux--Linux In the Linux kernel, the following vulnerability has been re= solved: drm/amd/display: Bound VBIOS record-chain walk loops [Why & How] Al=
    l record-chain walk loops in bios_parser.c and bios_parser2.c use for(;;) a=
    nd only terminate on a 0xFF record_type sentinel or zero record_size. A mal= formed VBIOS image missing the terminator record causes unbounded iteration=
    at probe time, potentially hundreds of thousands of iterations with record= _size=3D1. In the final iterations near the BIOS image boundary, struct cas=
    ts beyond the 2-byte header validated by GET_IMAGE can also read out of bou= nds. Cap all 14 record-chain walk loops to BIOS_MAX_NUM_RECORD (256) iterat= ions. The atombios.h defines up to 22 distinct record types and atomfirmwar= e.h has 13. Assuming an average of less than 10 records per type (which is = reasonable since most are connector- based) 256 is a generous upper bound. = (cherry picked from commit 95700a3d660287ed657d6892f7be9ffc0e294a93) 2026-0= 6-25 not yet calculated CVE-2026-53138 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53138 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: drm/v3d: Skip CSD when it has zeroed workgroups A=
    compute shader dispatch encodes its workgroup counts in the CFG0..CFG2 reg= isters. Kicking off a dispatch with a zero count in any of the three dimens= ions is invalid. First, the hardware will process 0 as 65536, while the use= r-space driver exposes a maximum of 65535. Over that, a submission with a z= eroed workgroup dimension should be a no-op. These zeroed counts can reach = the dispatch path through an indirect CSD job, whose workgroup counts are o= nly known once the indirect buffer is read and may legitimately be zero, bu=
    t such scenario should only result in a no-op. Overwrite the indirect CSD j=
    ob workgroup counts with the indirect BO ones, even if they are zeroed, and=
    don't submit the job to the hardware when any of the workgroup counts is z= ero, so the job completes immediately instead of running the shader. 2026-0= 6-25 not yet calculated CVE-2026-53139 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53139 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: drm/v3d: Fix vaddr leak when indirect CSD has zer= oed workgroups v3d_rewrite_csd_job_wg_counts_from_indirect() maps both the = indirect buffer and the workgroup buffer and is expected to release them be= fore returning. When any of the workgroup counts read from the buffer is ze= ro, the function bailed out early and skipped the cleanup, leaking the vadd=
    r mappings of both BOs. Jump to the cleanup path instead of returning direc= tly, so the mappings are always dropped. 2026-06-25 not yet calculated CVE-= 2026-53140 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53140 ] Linux--Lin=
    ux In the Linux kernel, the following vulnerability has been resolved: drm/= v3d: Fix global performance monitor reference counting In the SET_GLOBAL io= ctl, v3d_perfmon_find() bumps the reference count on the perfmon it returns=
    , but v3d_perfmon_set_global_ioctl() and v3d_perfmon_delete() fail to relea=
    se that reference on several paths: 1. v3d_perfmon_set_global_ioctl() leaks=
    the reference on its error paths. 2. CLEAR_GLOBAL leaks both the find refe= rence and the reference previously stashed in v3d->global_perfmon by the SE= T_GLOBAL ioctl that configured it. 3. Destroying a perfmon that is the curr= ent global perfmon leaks the reference stashed by the SET_GLOBAL ioctl. Rel= ease each of these references explicitly. 2026-06-25 not yet calculated CVE= -2026-53141 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53141 ] Linux--Li= nux In the Linux kernel, the following vulnerability has been resolved: drm= /xe/display: fix oops in suspend/shutdown without display The xe driver kee=
    ps track of whether to probe display, and whether display hardware is there=
    , using xe->info.probe_display. It gets set to false if there's no display = after intel_display_device_probe(). However, the display may also be disabl=
    ed via fuses, detected at a later time in intel_display_device_info_runtime= _init(). In this case, the xe driver does for_each_intel_crtc() on uninitia= lized mode config in xe_display_flush_cleanup_work(), leading to a NULL poi= nter dereference, and generally calls display code with display info cleare=
    d. Check for intel_display_device_present() after intel_display_device_info= _runtime_init(), and reset xe->info.probe_display as necessary. Also do uns= et_display_features() for completeness, although display runtime init has a= lready done that. This will need to be unified across all cases later. Move=
    intel_display_device_info_runtime_init() call slightly earlier, similar to=
    i915, to avoid a bunch of unnecessary setup for no display cases. Note #1:=
    The xe driver has no business doing low level display plumbing like for_ea= ch_intel_crtc() to begin with. It all needs to happen in display code. Note=
    #2: The actual bug is present already in commit 44e694958b95 ("drm/xe/disp= lay: Implement display support"), but the oops was likely introduced later =
    at commit ddf6492e0e50 ("drm/xe/display: Make display suspend/resume work o=
    n discrete"). (cherry picked from commit 7c3eb9f47533220888a67266448185fd07= 75d4da) 2026-06-25 not yet calculated CVE-2026-53142 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-53142 ] Linux--Linux In the Linux kernel, the follo= wing vulnerability has been resolved: drm/amdkfd: Fix buffer overflow in SD=
    MA queue checkpoint/restore on GFX11 The v11 MQD manager incorrectly assign=
    ed the CP-compute variants of checkpoint_mqd/restore_mqd for KFD_MQD_TYPE_S= DMA queues. These functions use sizeof(struct v11_compute_mqd) (2048 bytes)=
    instead of sizeof(struct v11_sdma_mqd) (512 bytes), causing a 1536-byte ov= erflow. During CRIU checkpoint of an SDMA queue on Navi3x: - checkpoint_mqd=
    () reads 2048 bytes from a 512-byte SDMA MQD buffer, leaking 1536 bytes of = adjacent GTT memory to userspace During CRIU restore: - restore_mqd() write=
    s 2048 bytes into a 512-byte SDMA MQD buffer, corrupting 1536 bytes of adja= cent GTT memory (often the ring buffer or neighboring MQDs) This is a copy-= paste regression unique to v11. All other ASIC backends (cik, vi, v9, v10, = v12) correctly use the SDMA-specific variants. Add checkpoint_mqd_sdma() an=
    d restore_mqd_sdma() functions that properly handle the smaller v11_sdma_mq=
    d structure, matching the pattern used in other MQD managers. (cherry picke=
    d from commit 6fa41db7ffdec97d62433adf03b7b9b759af8c2c) 2026-06-25 not yet = calculated CVE-2026-53143 [ https://www.cve.org/CVERecord?id=3DCVE-2026-531=
    43 ] Linux--Linux In the Linux kernel, the following vulnerability has been=
    resolved: drm/amdkfd: fix NULL dereference in get_queue_ids() When usr_que= ue_id_array is NULL and num_queues is non-zero, get_queue_ids() returns NUL=
    L. The callers check only IS_ERR() on the return value; since IS_ERR(NULL) = =3D=3D false the check passes, and suspend_queues() calls q_array_invalidat= e() which immediately dereferences NULL while iterating num_queues times. U= serspace can trigger this via kfd_ioctl_set_debug_trap() by supplying num_q= ueues > 0 with a zero queue_array_ptr, causing a kernel panic. A NULL usr_q= ueue_id_array with num_queues =3D=3D 0 is a legitimate no-op (q_array_inval= idate never executes, and resume_queues already guards all queue_ids derefe= rences behind a NULL check). Return ERR_PTR(-EINVAL) only when num_queues i=
    s non-zero and the pointer is absent; both callers already propagate IS_ERR=
    () returns correctly to userspace. (cherry picked from commit f165a82cdf503= 884bb1797771c61b2fcc72113d4) 2026-06-25 not yet calculated CVE-2026-53144 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-53144 ] Linux--Linux In the Li= nux kernel, the following vulnerability has been resolved: thunderbolt: Cla=
    mp XDomain response data copy to allocation size tb_xdp_properties_request(=
    ) derives the per-packet copy length from the response header without check= ing that it fits in the previously allocated data buffer. A malicious peer = can set its length field larger than the declared data_length, causing memc=
    py to write past the kcalloc allocation. Clamp the per-packet copy length s=
    o that the cumulative offset never exceeds data_len. 2026-06-25 not yet cal= culated CVE-2026-53148 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53148 =
    ] Linux--Linux In the Linux kernel, the following vulnerability has been re= solved: thunderbolt: Bound root directory content to block size __tb_proper= ty_parse_dir() does not check that content_offset + content_len fits within=
    block_len for the root directory case. When rootdir->length equals or exce= eds block_len - 2, the entry loop reads past the allocated property block. = Add a bounds check after computing content_offset and content_len to reject=
    directories whose content extends past the block. 2026-06-25 not yet calcu= lated CVE-2026-53149 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53149 ] = Linux--Linux In the Linux kernel, the following vulnerability has been reso= lved: thunderbolt: Reject zero-length property entries in validator tb_prop= erty_entry_valid() accepts entries with length =3D=3D 0 for DIRECTORY, DATA=
    , and TEXT types. A zero-length TEXT entry passes validation but causes an = underflow in the null-termination logic: property->value.text[property->len= gth * 4 - 1] =3D ' '; When property->length is 0 this writes to offset -1 r= elative to the allocation. Reject zero-length entries early in the validato=
    r since they have no valid representation in the XDomain property protocol.=
    2026-06-25 not yet calculated CVE-2026-53150 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-53150 ] Linux--Linux In the Linux kernel, the following vu= lnerability has been resolved: mmc: dw_mmc-rockchip: Add missing private da=
    ta for very old controllers The really old controllers (rk2928, rk3066, rk3= 188) do not support UHS speeds at all, and thus never handled phase data. F=
    or that reason it never had a parse_dt callback and no driver private data =
    at all. Commit ff6f0286c896 ("mmc: dw_mmc-rockchip: Add memory clock auto-g= ating support") makes the private data sort of mandatory, because the init = function checks whether phases are configured internally or through the clo=
    ck controller. This results in the old SoCs then experiencing NULL-pointer = dereferences when they try to access that private-data struct. While we cou=
    ld have if (priv) conditionals in all places, it's way less cluttery to jus=
    t give the old types their private-data struct. 2026-06-25 not yet calculat=
    ed CVE-2026-53152 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53152 ] Lin= ux--Linux In the Linux kernel, the following vulnerability has been resolve=
    d: mm/hugetlb: restore reservation on error in hugetlb folio copy paths Two=
    sites in mm/hugetlb.c allocate a hugetlb folio via alloc_hugetlb_folio() (= consuming a VMA reservation) and then call copy_user_large_folio(), which b= ecame int-returning in commit 1cb9dc4b475c ("mm: hwpoison: support recovery=
    from HugePage copy-on-write faults") and can now fail (e.g. -EHWPOISON on =
    a hwpoisoned source page). On the failure path, folio_put() restores the gl= obal hugetlb pool count through free_huge_folio(), but the per-VMA reservat= ion map entry is left marked consumed: - hugetlb_mfill_atomic_pte() resubmi= ssion path (UFFDIO_COPY) - copy_hugetlb_page_range() fork-time CoW path whe=
    n hugetlb_try_dup_anon_rmap() fails (rare: pinned hugetlb anon folio under = fork) User-visible effect: on UFFDIO_COPY into a private hugetlb VMA where = the resubmission copy fails, the reservation for that address is leaked fro=
    m the VMA's reserve map. A subsequent fault at the same address takes the n= o-reservation path, and under hugetlb pool pressure the task is SIGBUSed at=
    an address it had previously reserved. The fork-time CoW path leaks the sa=
    me way in the child VMA's reserve map, though it requires the much rarer co= mbination of pinned hugetlb anon page + hwpoisoned source. Add the missing = restore_reserve_on_error() call before folio_put() on both error paths. 202= 6-06-25 not yet calculated CVE-2026-53154 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-53154 ] Linux--Linux In the Linux kernel, the following vulner= ability has been resolved: mm/huge_memory: use correct flags for device pri= vate PMD entry Commit 65edfda6f3f2 ("mm/rmap: extend rmap and migration sup= port device-private entries") updated set_pmd_migration_entry() to use pmdp= _huge_get_and_clear() in the softleaf case, but made no further adjustments=
    to the function itself. Therefore this function continues to incorrectly u=
    se pmd_write(), pmd_soft_dirty() and pmd_uffd_wp() to determine whether the=
    installed migration entry should be marked writable, softdirty or uffd-wp = respectively. Whilst all are incorrect, the most problematic of these is pm= d_write(), as this can lead to corrupted rmap state. On x86-64 _PAGE_SWP_SO= FT_DIRTY is aliased to _PAGE_RW. So calling pmd_write() on a softleaf will = return the softdirty state encoded in the entry, assuming CONFIG_MEM_SOFT_D= IRTY was enabled. This was observed when running the hmm.hmm_device_private= .anon_write_child selftest: 1. The test faults in a range then migrates it = such that a device-private THP range is established. 2. The parent then mig= rates it to a device-private writable PMD entry whose folio is entirely Ano= nExclusive with entire_mapcount=3D1, softdirty set (accidentally correct wr= ite state). 3. The parent forks and the PMD entries are set to device-priva=
    te read only entries, entire_mapcount=3D2, softdirty still set. 4. [BUG] Th=
    e child writes to the range then migrates to RAM - intending to install non= -writable migration entries - but replacing parent and child PMD mappings w= ith WRITABLE entries due to misinterpreting the softdirty bit. 5. In remove= _migration_pmd(), if !softleaf_is_migration_read(entry) we set the RMAP_EXC= LUSIVE flag when calling folio_add_anon_rmap_pmd() for both parent and chil=
    d, which are therefore AnonExclusive. 6. [SPLAT] Child sets migrated folio = entire_mapcount=3D1, parent sets entire_mapcount=3D2 and we end up with an = AnonExclusive folio with entire_mapcount=3D2! Assert fires in __folio_add_a= non_rmap(): VM_WARN_ON_FOLIO(folio_test_large(folio) && folio_entire_mapcou= nt(folio) > 1 && PageAnonExclusive(cur_page), folio) This patch fixes the i= ssue by correctly referencing the softleaf entry fields for writable, softd= irty and uffd-wp in set_pmd_migration_entry(). It also only updates A/D fla=
    gs if the entry is present as these are otherwise not meaningful for a soft= leaf entry. This patch also flips the if (!present) { ... } else { ... } lo= gic in set_pmd_migration_entry() so it is easier to understand, and adds so=
    me comments to make things clearer. I was able to bisect this to commit 775= 465fd26a3 ("lib/test_hmm: add zone device private THP test infrastructure")=
    which first exposes this bug as it was the commit that permitted test_hmm =
    to generate the test. However commit 65edfda6f3f2 ("mm/rmap: extend rmap an=
    d migration support device-private entries") is the commit that actually en= abled this behaviour. 2026-06-25 not yet calculated CVE-2026-53155 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-53155 ] Linux--Linux In the Linux ker= nel, the following vulnerability has been resolved: nvmem: core: fix use-af= ter-free bugs in error paths Fix several instances of error paths in which =
    we call __nvmem_device_put() - which may end up freeing the underlying memo=
    ry and other resources - and then keep on using the nvmem structure. Always=
    put the reference to the nvmem device as the last step before returning th=
    e error code. 2026-06-25 not yet calculated CVE-2026-53156 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-53156 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: net: phonet: free phonet_device=
    after RCU grace period phonet_device_destroy() removes a phonet_device fro=
    m the per-net device list with list_del_rcu(), but frees it immediately. RC=
    U readers walking the same list can still hold a pointer to the object afte=
    r it has been removed, leading to a slab-use-after-free. Use kfree_rcu(), m= atching the lifetime rule already used by phonet_address_del() for the same=
    object type. 2026-06-25 not yet calculated CVE-2026-53157 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-53157 ] Linux--Linux In the Linux kernel, the=
    following vulnerability has been resolved: misc: fastrpc: Fix NULL pointer=
    dereference in rpmsg callback A NULL pointer dereference was observed on H= awi at boot when the DSP sends a glink message before fastrpc_rpmsg_probe()=
    has completed initialization: Unable to handle kernel NULL pointer derefer= ence at virtual address 0000000000000178 pc : _raw_spin_lock_irqsave+0x34/0= x8c lr : fastrpc_rpmsg_callback+0x3c/0xcc [fastrpc] ... Call trace: _raw_sp= in_lock_irqsave+0x34/0x8c (P) fastrpc_rpmsg_callback+0x3c/0xcc [fastrpc] qc= om_glink_native_rx+0x538/0x6a4 qcom_glink_smem_intr+0x14/0x24 [qcom_glink_s= mem] The faulting address 0x178 corresponds to the lock variable inside str= uct fastrpc_channel_ctx, confirming that cctx is NULL when fastrpc_rpmsg_ca= llback() attempts to take the spinlock. There are two issues here. First, d= ev_set_drvdata() is called before spin_lock_init() and idr_init(), leaving =
    a window where the callback can retrieve a valid cctx pointer but operate o=
    n an uninitialized spinlock. Second, the rpmsg channel becomes live as soon=
    as the driver is bound, so fastrpc_rpmsg_callback() can fire before dev_se= t_drvdata() is called at all, resulting in dev_get_drvdata() returning NULL=
    . Fix both issues by moving all cctx initialization ahead of dev_set_drvdat= a() so the structure is fully initialized before it becomes visible to the = callback, and add a NULL check in fastrpc_rpmsg_callback() as a guard again=
    st any remaining window. 2026-06-25 not yet calculated CVE-2026-53158 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-53158 ] Linux--Linux In the Linux = kernel, the following vulnerability has been resolved: misc: fastrpc: fix D=
    MA address corruption due to find_vma misuse fastrpc_get_args() uses find_v= ma() to look up the VMA for a user-provided pointer and compute a DMA addre=
    ss offset. When the address falls in a gap before the returned VMA, (ptr & = PAGE_MASK) - vma->vm_start underflows, corrupting the DMA address sent to t=
    he DSP. Replace find_vma() with vma_lookup(), which returns NULL when the a= ddress is not contained within any VMA. 2026-06-25 not yet calculated CVE-2= 026-53159 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53159 ] Linux--Linu=
    x In the Linux kernel, the following vulnerability has been resolved: locki= ng/rtmutex: Skip remove_waiter() when waiter is not enqueued syzbot trigger=
    ed the following splat in remove_waiter() via FUTEX_CMP_REQUEUE_PI: KASAN: = null-ptr-deref in range [0x0000000000000a88-0x0000000000000a8f] class_raw_s= pinlock_constructor remove_waiter+0x159/0x1200 kernel/locking/rtmutex.c:156=
    1 rt_mutex_start_proxy_lock+0x103/0x120 futex_requeue+0x10e4/0x20d0 __x64_s= ys_futex+0x34f/0x4d0 task_blocks_on_rt_mutex() does not arm the waiter upon=
    deadlock detection, leaving waiter->task nil, where 3bfdc63936dd ("rtmutex=
    : Use waiter::task instead of current in remove_waiter()") made this fatal.=
    Furthermore, rt_mutex_start_proxy_lock() should not be calling into remove= _waiter() upon a successfully grabbing the rtmutex. 1a1fb985f2e2 ("futex: H= andle early deadlock return correctly"), moved the remove_waiter() out of _= _rt_mutex_start_proxy_lock() (where 'ret' was only ever 0 or < 0) into the = wrapper. Tighten this check to account for try_to_take_rt_mutex(). 2026-06-=
    25 not yet calculated CVE-2026-53163 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-53163 ] Linux--Linux In the Linux kernel, the following vulnerabili=
    ty has been resolved: iommu/dma: Do not try to iommu_map a 0 length region =
    in swiotlb iommu_dma_iova_link_swiotlb() processes a mapping that is unalig= ned in three parts, the head, middle and trailer. If the middle is empty be= cause there are no aligned pages it will call down to iommu_map() with a 0 = size which the iommupt implementation will fail as illegal. It then tries t=
    o do an error unwind and starts from the wrong spot corrupting the mapping =
    so the eventual destruction triggers a WARN_ON. Check for 0 length and avoi=
    d mapping and use offset not 0 as the starting point to unlink. This is fre= quently triggered by using some kinds of thunderbolt NVMe drives that trigg=
    er forced SWIOTLB for unaligned memory. NVMe seems to pass in oddly aligned=
    buffers for the passthrough commands from smartctl that hit this condition=
    . 2026-06-25 not yet calculated CVE-2026-53164 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-53164 ] Linux--Linux In the Linux kernel, the following v= ulnerability has been resolved: futex/requeue: Prevent NULL pointer derefer= ence in remove_waiter() on self-deadlock When FUTEX_CMP_REQUEUE_PI requeues=
    a non-top waiter that already owns the target PI futex, task_blocks_on_rt_= mutex() returns -EDEADLK before setting waiter->task. The subsequent remove= _waiter() in rt_mutex_start_proxy_lock() dereferences the NULL waiter->task=
    , causing a kernel crash. Add a self-deadlock check for non-top waiters bef= ore calling rt_mutex_start_proxy_lock(), analogous to the top-waiter check =
    in futex_lock_pi_atomic(). 2026-06-25 not yet calculated CVE-2026-53166 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-53166 ] Linux--Linux In the Linu=
    x kernel, the following vulnerability has been resolved: fuse: limit FUSE_N= OTIFY_RETRIEVE to uptodate folios FUSE_NOTIFY_RETRIEVE must be limited to u= ptodate folios; !uptodate folios can contain uninitialized data. Since FUSE= _NOTIFY_RETRIEVE is intended to only return data that is already in the pag=
    e cache and not wait for data from the FUSE daemon, treat !uptodate folios =
    as if they weren't present. This only has security impact on systems that d= on't enable automatic zero-initialization of all page allocations via CONFI= G_INIT_ON_ALLOC_DEFAULT_ON or init_on_alloc=3D1. 2026-06-25 not yet calcula= ted CVE-2026-53167 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53167 ] Li= nux--Linux In the Linux kernel, the following vulnerability has been resolv= ed: fuse: reject fuse_notify() pagecache ops on directories The operations = FUSE_NOTIFY_STORE and FUSE_NOTIFY_RETRIEVE allow the FUSE daemon to activel=
    y write/read pagecache contents. For directories with FOPEN_CACHE_DIR, the = pagecache is used as kernel-internal cache storage, and userspace is not su= pposed to have direct access to this cache - in particular, fuse_parse_cach= e() will hit WARN_ON() if the cache contains bogus data. Reject FUSE_NOTIFY= _STORE and FUSE_NOTIFY_RETRIEVE on anything other than regular files with -= EINVAL. 2026-06-25 not yet calculated CVE-2026-53168 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-53168 ] Linux--Linux In the Linux kernel, the follo= wing vulnerability has been resolved: accel/ethosu: reject NPU_OP_RESIZE co= mmands from userspace NPU_OP_RESIZE is a U85-only command that the driver d= oes not yet implement. The existing WARN_ON(1) placeholder fires unconditio= nally whenever userspace submits this command via DRM_IOCTL_ETHOSU_GEM_CREA= TE, causing unbounded kernel log spam. If panic_on_warn is set the kernel p= anics, giving any unprivileged user with access to the DRM device a trivial=
    denial-of-service primitive. Replace the WARN_ON(1) with an explicit -EINV=
    AL return so the ioctl rejects the command before it reaches hardware. 2026= -06-25 not yet calculated CVE-2026-53169 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53169 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: bnxt_en: Fix NULL pointer dereference PCIe errors=
    detected by a Root Port or Downstream Port cause error recovery services t=
    o run on all subordinate devices regardless of administrative state. The .e= rror_detected() callback, bnxt_io_error_detected(), disables and synchroniz=
    es IRQs via bnxt_disable_int_sync(), which calls bnxt_cp_num_to_irq_num() t=
    o map completion rings to IRQs using bp->bnapi. Since bp->bnapi is allocate=
    d on NIC open and freed on NIC close, PCIe error recovery on a closed NIC c=
    an dereference a NULL pointer. Check if bp->bnapi is NULL before disabling = and synchronizing IRQs. 2026-06-25 not yet calculated CVE-2026-53177 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-53177 ] Linux--Linux In the Linux k= ernel, the following vulnerability has been resolved: staging: rtl8723bs: f=
    ix buffer over-read in rtw_update_protection rtw_update_protection() is cal= led with a pointer offset into the ies buffer but the full ie_length is pas= sed, causing a potential buffer over-read. 2026-06-25 not yet calculated CV= E-2026-53179 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53179 ] Linux--L= inux In the Linux kernel, the following vulnerability has been resolved: vs= ock/vmci: fix sk_ack_backlog leak on failed handshake When vmci_transport_r= ecv_connecting_server() returns an error, vmci_transport_recv_listen() call=
    s vsock_remove_pending() but never calls sk_acceptq_removed(). This leaves = sk_ack_backlog incremented permanently. Repeated handshake failures (malfor= med packets, queue pair alloc failure, event subscribe failure) cause sk_ac= k_backlog to climb toward sk_max_ack_backlog. Once it reaches the limit the=
    listener permanently refuses all new connections with -ECONNREFUSED, a sil= ent denial of service requiring a process restart to recover. The two exist= ing sk_acceptq_removed() calls in af_vsock.c do not cover this path: line 7=
    64 checks vsock_is_pending() which returns false after vsock_remove_pending= (), and line 1889 is only reached on successful accept(). Fix by balancing = sk_acceptq_added() with sk_acceptq_removed() on the error path. 2026-06-25 = not yet calculated CVE-2026-53181 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-53181 ] Linux--Linux In the Linux kernel, the following vulnerability = has been resolved: drm/virtio: fix dma_fence refcount leak on error in virt= io_gpu_dma_fence_wait() dma_fence_unwrap_for_each() internally calls dma_fe= nce_unwrap_first() which does cursor->chain =3D dma_fence_get(head), taking=
    an extra reference. On normal loop completion, dma_fence_unwrap_next() rel= eases this via dma_fence_chain_walk() -> dma_fence_put(). When virtio_gpu_d= o_fence_wait() fails and the function returns early from inside the loop, t=
    he cursor->chain reference is never released. This is the only caller in th=
    e entire kernel that does an early return inside dma_fence_unwrap_for_each.=
    Add dma_fence_put(itr.chain) before the early return. 2026-06-25 not yet c= alculated CVE-2026-53190 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5319=
    0 ] Linux--Linux In the Linux kernel, the following vulnerability has been = resolved: USB: serial: io_ti: fix heap overflow in build_i2c_fw_hdr() build= _i2c_fw_hdr() allocates a fixed-size buffer of (16*1024 - 512) + sizeof(str= uct ti_i2c_firmware_rec) bytes, then copies le16_to_cpu(img_header->Length)=
    bytes into it without validating that Length fits within the available spa=
    ce after the firmware record header. img_header->Length is a __le16 from th=
    e firmware file and can be up to 65535. check_fw_sanity() validates the tot=
    al firmware size but not img_header->Length specifically. Fix by rejecting = images where img_header->Length exceeds the available destination space. 20= 26-06-25 not yet calculated CVE-2026-53195 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-53195 ] Linux--Linux In the Linux kernel, the following vulne= rability has been resolved: USB: serial: io_ti: fix heap overflow in get_ma= nuf_info() get_manuf_info() reads le16_to_cpu(rom_desc->Size) bytes from th=
    e device I2C EEPROM into a buffer allocated with kmalloc_obj(), which is si= zeof(struct edge_ti_manuf_descriptor) =3D 10 bytes. The Size field comes fr=
    om the device and is only validated (in check_i2c_image()) to make sure the=
    descriptor fits within TI_MAX_I2C_SIZE (16384 bytes), not against the dest= ination buffer size. A malicious USB device can therefore set Size to any v= alue up to 16377, causing a heap overflow of up to 16367 bytes when plugged=
    into a host running this driver. valid_csum() is called after read_rom() a=
    nd also iterates buffer[0..Size-1], compounding the out-of-bounds access. F=
    ix by rejecting descriptors with unexpected length before calling read_rom(=
    ). [ johan: amend commit message; also check for short descriptors ] 2026-0= 6-25 not yet calculated CVE-2026-53196 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53196 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: xfrm: iptfs: fix ABBA deadlock in iptfs_destroy_s= tate() iptfs_destroy_state() calls hrtimer_cancel() while holding a spinloc=
    k that the timer callback also acquires, leading to an ABBA deadlock on SMP=
    systems. For the output timer (iptfs_timer): - iptfs_destroy_state() holds=
    lock, calls hrtimer_cancel() - iptfs_delay_timer() callback takes x->lo=
    ck For the drop timer (drop_timer): - iptfs_destroy_state() holds drop_lock=
    , calls hrtimer_cancel() - iptfs_drop_timer() callback takes drop_lock Both=
    timers use HRTIMER_MODE_REL_SOFT, so their callbacks run in softirq contex=
    t. When hrtimer_cancel() is called for a soft timer that is currently execu= ting on another CPU, hrtimer_cancel_wait_running() spins on softirq_expiry_= lock -- the same lock held by the softirq running the callback. If the call= back is blocked waiting for the spinlock held by the caller of hrtimer_canc= el(), a circular dependency forms: CPU 0: holds lock_A -> waits for softirq= _expiry_lock CPU 1: holds softirq_expiry_lock -> waits for lock_A Fix by ca= lling hrtimer_cancel() before acquiring the respective locks. hrtimer_cance= l() is safe to call without holding any lock and will wait for any in-progr= ess callback to complete. For the output timer, the lock is still acquired = afterwards to drain the packet queue. For the drop timer, the lock/unlock p= air is removed entirely since it only existed to serialize with the timer c= allback, which hrtimer_cancel() already guarantees. Found by source code au= dit. 2026-06-25 not yet calculated CVE-2026-53197 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-53197 ] Linux--Linux In the Linux kernel, the followin=
    g vulnerability has been resolved: firmware: stratix10-rsu: Fix NULL deref =
    on rsu_send_msg() timeout in probe rsu_send_msg() can return -ETIMEDOUT whe=
    n wait_for_completion_interruptible_timeout() fires while the SMC call is s= till pending. In stratix10_rsu_probe(), the error paths for COMMAND_RSU_DCM= F_VERSION, COMMAND_RSU_DCMF_STATUS, COMMAND_RSU_MAX_RETRY and COMMAND_RSU_G= ET_SPT_TABLE call stratix10_svc_free_channel() - which sets chan->scl to NU=
    LL - but then fall through and queue the next request on the same channel. = The next svc kthread that runs will dereference pdata->chan->scl in its rec= eive callback path, triggering a NULL pointer dereference identical to the = one fixed by commit c45f7263100c ("firmware: stratix10-rsu: Fix NULL pointe=
    r dereference when RSU is disabled") for the COMMAND_RSU_STATUS path. Apply=
    the same cleanup pattern to the remaining failure paths: remove the async = client, free the channel, and return early so no further messages are queue=
    d on a channel whose scl has been cleared. While at it, clean up stratix10_= rsu_probe() in two ways without changing behavior: - Drop redundant zero-in= itialization of fields already cleared by devm_kzalloc(): client.receive_cb=
    , status.* and spt0/1_address (INVALID_SPT_ADDRESS is 0x0). - Replace five = identical 3-line error-cleanup blocks (stratix10_svc_remove_async_client() =
    + stratix10_svc_free_channel() + return ret) with goto labels (remove_async= _client, free_channel), matching the standard kernel resource-unwinding pat= tern and making it easier to extend the probe sequence without forgetting m= atching cleanup. Also move init_completion() next to mutex_init() so sync-p= rimitive initialization is grouped before anything that could trigger a cal= lback. --- v2: Add a minor clean-up of the function stratix10_rsu_probe() t=
    o have a centralize exit for all the rsu_send_async_msg() and rsu_send_msg(=
    ). 2026-06-25 not yet calculated CVE-2026-53204 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-53204 ] Linux--Linux In the Linux kernel, the following = vulnerability has been resolved: accel/ivpu: Add bounds check for firmware = runtime memory Validate that the firmware runtime memory specified in the i= mage header is properly aligned and sized to hold the firmware image. This = prevents errors during memory allocation and image transfer. 2026-06-25 not=
    yet calculated CVE-2026-53206 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-53206 ] Linux--Linux In the Linux kernel, the following vulnerability has=
    been resolved: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge= _page_for_hwpoison Two concurrent madvise(MADV_HWPOISON) calls on the same = hugetlb page can trigger a recursive spinlock self-deadlock (AA deadlock) o=
    n hugetlb_lock when racing with a concurrent unmap: thread#0 thread#1 -----= --- -------- madvise(folio, MADV_HWPOISON) -> poisons the folio successfull=
    y madvise(folio, MADV_HWPOISON) unmap(folio) try_memory_failure_hugetlb get= _huge_page_for_hwpoison spin_lock_irq(&hugetlb_lock) <- held __get_huge_pag= e_for_hwpoison hugetlb_update_hwpoison() -> MF_HUGETLB_FOLIO_PRE_POISONED g= oto out: folio_put() refcount: 1 -> 0 free_huge_folio() spin_lock_irqsave(&= hugetlb_lock) -> AA DEADLOCK! The out: path in __get_huge_page_for_hwpoison=
    () calls folio_put() to drop the GUP reference while the hugetlb_lock is st= ill held by the hugetlb.c wrapper get_huge_page_for_hwpoison(). If concurre=
    nt unmap has released the page table mapping reference, folio_put() drops t=
    he folio refcount to zero, triggering free_huge_folio() which attempts to r= e-acquire the non-recursive hugetlb_lock. Fix this by moving hugetlb_lock a= cquisition from the hugetlb.c wrapper into get_huge_page_for_hwpoison(). Pl= ace spin_unlock_irq() before the folio_put() at the out: label so the folio=
    is always released outside the lock. [akpm@linux-foundation.org: fix race,=
    rename label per Miaohe] 2026-06-25 not yet calculated CVE-2026-53207 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-53207 ] Linux--Linux In the Linux=
    kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: r= eject BR/EDR signaling packets over MTUsig net/bluetooth/l2cap_core.c:l2cap= _sig_channel() accepts BR/EDR signaling packets up to the channel MTU and d= ispatches each command without enforcing the signaling MTU (MTUsig). A Blue= tooth BR/EDR peer within radio range can send a fixed-channel CID 0x0001 pa= cket that is larger than MTUsig and contains many L2CAP_ECHO_REQ commands b= efore pairing. In a real-radio stock-kernel run, one 681-byte signaling pac= ket containing 168 zero-length ECHO_REQ commands made the target transmit 1=
    68 ECHO_RSP frames over about 220 ms. Impact: a Bluetooth BR/EDR peer withi=
    n radio range, before pairing, can force 168 ECHO_RSP frames from one 681-b= yte fixed-channel signaling packet containing packed ECHO_REQ commands. Def= ine Linux's BR/EDR signaling MTU as the spec minimum of 48 bytes and reject=
    any larger signaling packet with one L2CAP_COMMAND_REJECT_RSP carrying L2C= AP_REJ_MTU_EXCEEDED before any command is dispatched. The Bluetooth Core sp=
    ec wording for MTUExceeded says the reject identifier shall match the first=
    request command in the packet, and that packets containing only responses = shall be silently discarded. Linux intentionally deviates from that prescri= ption: silently discarding desynchronizes the peer because the remote stack=
    never learns its responses were dropped, and locating the first request co= mmand requires walking command headers past MTUsig, i.e. processing bytes f= rom a packet we have already decided is too large to process. We therefore = always emit one reject and use the identifier from the first command header=
    , a single fixed-offset byte read. The unrestricted BR/EDR signaling parser=
    and ECHO_REQ response path both trace to the initial git import; no later = introducing commit is available for a Fixes tag. 2026-06-25 not yet calcula= ted CVE-2026-53208 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53208 ] Li= nux--Linux In the Linux kernel, the following vulnerability has been resolv= ed: tee: shm: fix shm leak in register_shm_helper() register_shm_helper() a= llocates shm before calling iov_iter_npages(). If iov_iter_npages() returns=
    0, the function jumps to err_ctx_put and leaks shm. This can be triggered =
    by TEE_IOC_SHM_REGISTER with struct tee_ioctl_shm_register_data where lengt=
    h is 0. Jump to err_free_shm instead. 2026-06-25 not yet calculated CVE-202= 6-53210 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53210 ] Linux--Linux =
    In the Linux kernel, the following vulnerability has been resolved: netfilt= er: nft_meta_bridge: fix stale stack leak via IIFHWADDR register NFT_META_B= RI_IIFHWADDR declares its destination register with len =3D ETH_ALEN (6 byt= es), which the register-init tracking rounds up to two 32-bit registers (8 = bytes). nft_meta_bridge_get_eval() then does memcpy(dest, br_dev->dev_addr,=
    ETH_ALEN), writing only 6 bytes and leaving the upper 2 bytes of the secon=
    d register as uninitialised nft_do_chain() stack. A downstream load of that=
    register span leaks those stale bytes to userspace. Zero the second regist=
    er before the memcpy so the full declared span is written. 2026-06-25 not y=
    et calculated CVE-2026-53211 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 53211 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: drm/vc4: fix krealloc() memory leak Don't just overwrite the = original pointer passed to krealloc() with its return value without checkin=
    g latter: MEM =3D krealloc(MEM, SZ, GFP); If krealloc() returns NULL, that = erases the pointer to the still allocated memory, hence leaks this memory. = Instead, use a temporary variable, check it's not NULL and only then assign=
    it to the original pointer: TMP =3D krealloc(MEM, SZ, GFP); if (!TMP) retu= rn; MEM =3D TMP; While on it, use krealloc_array(). 2026-06-25 not yet calc= ulated CVE-2026-53213 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53213 ]=
    Linux--Linux In the Linux kernel, the following vulnerability has been res= olved: ipv6: Fix a potential NPD in cleanup_prefix_route() addrconf_get_pre= fix_route() can return the fib6_null_entry sentinel entry which has a NULL = fib6_table pointer. Therefore, before setting the route's expiration time, = check that we are not working with this entry, as otherwise a NPD will be t= riggered [1]. Note that the other callers of addrconf_get_prefix_route() ar=
    e not susceptible to this bug: 1. addrconf_prefix_rcv(): Requests a route w= ith the 'RTF_ADDRCONF | RTF_PREFIX_RT' flags which are not set on fib6_null= _entry. 2. modify_prefix_route(): Fixed by commit a747e02430df ("ipv6: avoi=
    d possible NULL deref in modify_prefix_route()"). 3. __ipv6_ifa_notify(): C= alls ip6_del_rt() which specifically checks for fib6_null_entry and returns=
    an error. [1] Oops: general protection fault, probably for non-canonical a= ddress 0xdffffc0000000006: 0000 [#1] SMP KASAN KASAN: null-ptr-deref in ran=
    ge [0x0000000000000030-0x0000000000000037] [...] Call Trace: <TASK> __kasan= _check_byte (mm/kasan/common.c:573) lock_acquire.part.0 (kernel/locking/loc= kdep.c:5842 (discriminator 1)) _raw_spin_lock_bh (kernel/locking/spinlock.c= :182 (discriminator 1)) cleanup_prefix_route (net/ipv6/addrconf.c:1280) ipv= 6_del_addr (net/ipv6/addrconf.c:1342) inet6_addr_del.isra.0 (net/ipv6/addrc= onf.c:3119) inet6_rtm_deladdr (net/ipv6/addrconf.c:4812) rtnetlink_rcv_msg = (net/core/rtnetlink.c:6997) netlink_rcv_skb (net/netlink/af_netlink.c:2555)=
    netlink_unicast (net/netlink/af_netlink.c:1344) netlink_sendmsg (net/netli= nk/af_netlink.c:1899) __sock_sendmsg (net/socket.c:802 (discriminator 4)) _= ___sys_sendmsg (net/socket.c:2698) ___sys_sendmsg (net/socket.c:2752) __sys= _sendmsg (net/socket.c:2784) do_syscall_64 (arch/x86/entry/syscall_64.c:63 = arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/en= try/entry_64.S:121) 2026-06-25 not yet calculated CVE-2026-53214 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-53214 ] Linux--Linux In the Linux kerne=
    l, the following vulnerability has been resolved: netfilter: nft_exthdr: fi=
    x register tracking for F_PRESENT flag nft_exthdr_init() passes user-contro= lled priv->len to nft_parse_register_store(), which marks that many bytes i=
    n the register bitmap as initialized. However, when NFT_EXTHDR_F_PRESENT is=
    set, the eval paths write only 1 byte (nft_reg_store8) or 4 bytes (*dest =
    =3D 0 on TCP/DCCP error path). When len > 4, registers beyond the first are=
    never written, retaining uninitialized stack data from nft_regs. Bail out =
    if userspace requests too much data when F_PRESENT is set. 2026-06-25 not y=
    et calculated CVE-2026-53218 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 53218 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: netfilter: x_tables: avoid leaking percpu counter pointers Th=
    e native and compat get-entries paths copy the fixed rule entry header from=
    the kernelized rule blob to userspace before overwriting the entry's count=
    er fields with a sanitized counter snapshot. On SMP kernels, entry->counter= s.pcnt contains the percpu allocation address used by x_tables rule counter=
    s. A caller can provide a userspace buffer that faults during the initial f= ixed-header copy after pcnt has been copied but before the later sanitized = counter copy runs. The syscall then returns -EFAULT while leaving the raw p= ercpu pointer in userspace. Copy only the fixed entry prefix before counter=
    s from the kernelized rule blob, then copy the sanitized counter snapshot i= nto the counter field. Apply this ordering to the IPv4, IPv6, and ARP nativ=
    e and compat get-entries implementations so a fault cannot expose the inter= nal percpu counter pointer. 2026-06-25 not yet calculated CVE-2026-53219 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-53219 ] Linux--Linux In the Lin=
    ux kernel, the following vulnerability has been resolved: netfilter: revali= date bridge ports ebt_redirect_tg() dereferences br_port_get_rcu() return w= ithout a NULL check, causing a kernel panic when the bridge port has been r= emoved between the original hook invocation and an NFQUEUE reinject. A mere=
    NULL check isn't sufficient, however. As sashiko review points out userspa=
    ce can not only remove the port from the bridge, it could also place the de= vice in a different virtual device, e.g. macvlan. If this happens, we must = drop the packet, there is no way for us to reinject it into the bridge path=
    . Switch to _upper API, we don't need the bridge port structure. Also, this=
    fix keeps another bug intact: Both nfnetlink_log and nfnetlink_queue use C= ONFIG_BRIDGE_NETFILTER too aggressive, which prevents certain logging featu= res when queueing in bridge family: NETFILTER_FAMILY_BRIDGE can be enabled = while the old CONFIG_BRIDGE_NETFILTER cruft is off. Fixes tag is a common a= ncestor, this was always broken. 2026-06-25 not yet calculated CVE-2026-532=
    20 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53220 ] Linux--Linux In th=
    e Linux kernel, the following vulnerability has been resolved: ptp: ocp: fi=
    x resource freeing order Commit a60fc3294a37 ("ptp: rework ptp_clock_unregi= ster() to disable events") added a call to ptp_disable_all_events() which c= hanges the configuration of pins if they support EXTTS events. In ptp_ocp_d= etach() pins resources are freed before ptp_clock_unregister() and it leads=
    to use-after-free during driver removal. Fix it by changing the order of f= ree/unregister calls. To avoid irq handler running on the other core while = ptp device unregistering, call synchronize_irq() after HW is configured to = stop producing irqs and no irqs are in-flight. 2026-06-25 not yet calculate=
    d CVE-2026-53222 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53222 ] Linu= x--Linux In the Linux kernel, the following vulnerability has been resolved=
    : gpio: rockchip: fix generic IRQ chip leak on remove The driver allocates = domain generic chips using irq_alloc_domain_generic_chips() during probe. H= owever, on driver remove/teardown, the generic chips are not automatically = freed when the IRQ domain is removed because the domain flags do not includ=
    e IRQ_DOMAIN_FLAG_DESTROY_GC. This causes both the domain generic chips str= ucture and the associated generic chips to be leaked. Additionally, the gen= eric chips remain on the global gc_list and may later be visited by generic=
    IRQ chip suspend, resume, or shutdown callbacks after the GPIO bank has be=
    en removed, potentially resulting in a use-after-free and kernel crash. Fix=
    the resource leak by explicitly calling irq_domain_remove_generic_chips() = before removing the IRQ domain in rockchip_gpio_remove(). 2026-06-25 not ye=
    t calculated CVE-2026-53226 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 3226 ] Linux--Linux In the Linux kernel, the following vulnerability has be=
    en resolved: net: openvswitch: fix possible kfree_skb of ERR_PTR After the = patch in the "Fixes" tag, the allocation of the "reply" skb can happen eith=
    er before or after locking the ovs_mutex. However, error cleanups still fol= low the classical reversed order, assuming "reply" is allocated before lock= ing: it is freed after unlocking. If "reply" allocation happens after locki=
    ng the mutex and it fails, "reply" is left with an ERR_PTR, and execution j= umps to the correspondent cleanup stage which will try to free an invalid p= ointer. Fix this by setting the pointer to NULL after having saved its erro=
    r value. 2026-06-25 not yet calculated CVE-2026-53227 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-53227 ] Linux--Linux In the Linux kernel, the foll= owing vulnerability has been resolved: net: phy: don't try to setup PHY-dri= ven SFP cages when using genphy We don't have support for PHY-driver SFP ca= ges with the genphy code. On top of that, it was found by sashiko that runn= ing sfp_bus_add_upstream() for genphy deadlocks, as for genphy the PHY prob= ing runs under RTNL, which isn't the case for non-genphy drivers. This prob= lem was reproduced, and does lead to a deadlock on RTNL. Before the blamed = commit, the phy_sfp_probe() call was made by individual PHY drivers, so the=
    re was no way to get to the SFP probing path when using genphy. Let's there= fore only run phy_sfp_probe when not using genphy. 2026-06-25 not yet calcu= lated CVE-2026-53231 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53231 ] = Linux--Linux In the Linux kernel, the following vulnerability has been reso= lved: netdev: fix double-free in netdev_nl_bind_rx_doit() Sashiko flags tha=
    t genlmsg_reply() always consumes the skb. The error path calls nlmsg_free(= rsp) so we can't jump directly to it. Let's not unbind, just propagate the = error to the user. This is the typical way of handling genlmsg_reply() fail= ures. They shouldn't happen unless user does something silly like calling t=
    he kernel with an already-full rcvbuf. 2026-06-25 not yet calculated CVE-20= 26-53233 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53233 ] Linux--Linux=
    In the Linux kernel, the following vulnerability has been resolved: net: i= bm: emac: Fix use-after-free during device removal The driver was using dev= m_register_netdev() which causes unregister_netdev() to be deferred until t=
    he devres cleanup phase, which runs after emac_remove() returns. This creat=
    es a use-after-free window where: 1. emac_remove() is called, which tears d= own hardware (cancels work, detaches modules, unregisters from MAL) 2. emac= _remove() returns 3. devres cleanup runs and finally calls unregister_netde= v() During step 3, the network stack might still process packets, triggerin=
    g emac_irq(), emac_poll(), or other handlers that access now-freed hardware=
    resources (dev->emacp, dev->mal, etc.). Fix this by replacing devm_registe= r_netdev() with manual register_netdev() and calling unregister_netdev() at=
    the beginning of emac_remove(), before any hardware teardown. This ensures=
    the network device is fully stopped and unregistered before hardware resou= rces are released. The change is safe because: - dev->ndev is assigned very=
    early in probe (before any error paths that could bypass emac_remove) - pl= atform_set_drvdata() is only called after successful registration, so emac_= remove() only runs for fully registered devices - unregister_netdev() is id= empotent and safe to call on any registered device 2026-06-25 not yet calcu= lated CVE-2026-53234 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53234 ] = Linux--Linux In the Linux kernel, the following vulnerability has been reso= lved: tcp: restrict SO_ATTACH_FILTER to priv users This patch restricts the=
    use of SO_ATTACH_FILTER (cBPF) on TCP sockets to users with CAP_NET_ADMIN = capability. This blocks potential side-channel attack where an unprivileged=
    application attaches a filter to leak TCP sequence/acknowledgment numbers.=
    2026-06-25 not yet calculated CVE-2026-53236 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-53236 ] Linux--Linux In the Linux kernel, the following vu= lnerability has been resolved: gpio: mvebu: fix NULL pointer dereference in=
    suspend/resume mvebu_pwm_suspend() and mvebu_pwm_resume() are called for a=
    ll GPIO banks during suspend/resume, but not all banks have PWM functionali= ty. GPIO banks without PWM have mvchip->mvpwm set to NULL. Calling mvebu_pw= m_suspend() with mvpwm =3D=3D NULL causes a NULL pointer dereference when i=
    t tries to access mvpwm->blink_select. Unable to handle kernel NULL pointer=
    dereference at virtual address 00000020 when write [00000020] *pgd=3D00000= 000 Internal error: Oops: 815 [#1] PREEMPT ARM Modules linked in: CPU: 0 UI=
    D: 0 PID: 406 Comm: sh Not tainted 6.12.74-rt12-yocto-standard-g4e96f98fb7d= b-dirty #353 Hardware name: Marvell Armada 370/XP (Device Tree) PC is at re= gmap_mmio_read+0x38/0x54 LR is at regmap_mmio_read+0x38/0x54 pc : [<c05fd2a= c>] lr : [<c05fd2ac>] psr: 200f0013 sp : f0c11d10 ip : 00000000 fp : c100d2=
    f0 r10: c14fb854 r9 : 00000000 r8 : 00000000 r7 : c1799c00 r6 : 00000020 r5=
    : 00000020 r4 : c179c7c0 r3 : f0a231a0 r2 : 00000020 r1 : 00000020 r0 : 00= 000000 Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none Control=
    : 10c5387d Table: 135ec059 DAC: 00000051 Call trace: regmap_mmio_read from = _regmap_bus_reg_read+0x78/0xac _regmap_bus_reg_read from _regmap_read+0x60/= 0x154 _regmap_read from regmap_read+0x3c/0x60 regmap_read from mvebu_gpio_s= uspend+0xa4/0x14c mvebu_gpio_suspend from dpm_run_callback+0x54/0x180 dpm_r= un_callback from device_suspend+0x124/0x630 device_suspend from dpm_suspend= +0x124/0x270 dpm_suspend from dpm_suspend_start+0x64/0x6c dpm_suspend_start=
    from suspend_devices_and_enter+0x140/0x8e8 suspend_devices_and_enter from = pm_suspend+0x2fc/0x308 pm_suspend from state_store+0x6c/0xc8 state_store fr=
    om kernfs_fop_write_iter+0x10c/0x1f8 kernfs_fop_write_iter from vfs_write+0= x270/0x468 vfs_write from ksys_write+0x70/0xf0 ksys_write from ret_fast_sys= call+0x0/0x54 Add a NULL check for mvchip->mvpwm before calling the PWM sus= pend/resume functions. 2026-06-25 not yet calculated CVE-2026-53237 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-53237 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: netlabel: validate unl= abeled address and mask attribute lengths netlbl_unlabel_addrinfo_get() use=
    d the address attribute length to determine whether the attribute data coul=
    d be read as an IPv4 or IPv6 address, but did not independently validate th=
    e corresponding mask attribute length. A crafted Generic Netlink request co= uld therefore provide a valid IPv4/IPv6 address attribute with a shorter ma=
    sk attribute, which would later be read as a full struct in_addr or struct = in6_addr. NLA_BINARY policy lengths are maximum lengths by default, so use = NLA_POLICY_EXACT_LEN() for the unlabeled IPv4/IPv6 address and mask attribu= tes. This rejects short attributes during policy validation and also expose=
    s the exact length requirements through policy introspection. 2026-06-25 no=
    t yet calculated CVE-2026-53238 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-53238 ] Linux--Linux In the Linux kernel, the following vulnerability ha=
    s been resolved: ALSA: seq: dummy: fix UMP event stack overread The dummy s= equencer port forwards events by copying an incoming struct snd_seq_event i= nto a stack temporary, rewriting source and destination, and dispatching th=
    e temporary to subscribers. That legacy event storage is smaller than struc=
    t snd_seq_ump_event. When a UMP event reaches the dummy client, the copy le= aves the UMP flag set but only provides legacy-sized stack storage. The sub= scriber delivery path then uses snd_seq_event_packet_size() and copies a UM= P-sized packet from that stack object, reading past the end of the temporar=
    y. Use the existing union __snd_seq_event storage and copy the packet size = reported for the incoming event before rewriting the common routing fields.=
    This preserves the full UMP packet for UMP events while keeping legacy eve=
    nt handling unchanged. 2026-06-25 not yet calculated CVE-2026-53241 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-53241 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: rseq: Fix using an uni= nitialized stack variable in rseq_exit_user_update() There is an bug in whi=
    ch an uninitialized stack variable is used in rseq_exit_user_update() as re= ported by syzbot: BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr in= clude/linux/rseq_entry.h:502 [inline] The local variable: struct rseq_ids i=
    ds =3D { .cpu_id =3D task_cpu(t), .mm_cid =3D task_mm_cid(t), .node_id =3D = cpu_to_node(ids.cpu_id), }; According to the C standard, the evaluation ord=
    er of expressions in an initializer list is indeterminately sequenced. The = compiler (Clang, in this KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *= before* `ids.cpu_id` is initialized with `task_cpu(t)`. This is fixed by mo= ving the assignment of ids.node_id outside the structure initialization. 20= 26-06-25 not yet calculated CVE-2026-53243 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-53243 ] Linux--Linux In the Linux kernel, the following vulne= rability has been resolved: net/802/mrp: fix vector attribute parsing in mr= p_pdu_parse_vecattr In mrp_pdu_parse_vecattr(), vector attribute events are=
    encoded three per byte and valen tracks the number of events left to proce= ss. The parser decrements valen after processing the first and second event=
    s from each event byte, but not after processing the third one. When valen =
    is exactly a multiple of three, the loop continues after the last valid eve=
    nt and consumes the next byte as a new event byte, applying a spurious even=
    t to the MRP applicant state. Additionally, when valen is zero the parser u= nconditionally consumes attrlen bytes as FirstValue and advances the offset=
    , even though per IEEE 802.1ak a VectorAttribute with only a LeaveAllEvent = has valen of zero and no FirstValue or Vector fields. This corrupts the off= set for subsequent PDU parsing. Also, when valen exceeds three the loop cro= sses byte boundaries but the attribute value is not incremented between the=
    last event of one byte and the first event of the next. This causes the fi= rst event of the next byte to use the same attribute value as the third eve=
    nt rather than the next consecutive value. Decrement valen after processing=
    the third event, skip FirstValue consumption when valen is zero, and incre= ment the attribute value at the end of each loop iteration. 2026-06-25 not = yet calculated CVE-2026-53245 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -53245 ] Linux--Linux In the Linux kernel, the following vulnerability has = been resolved: ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options This patch = restricts setting Loose Source and Record Route (LSRR) and Strict Source an=
    d Record Route (SSRR) IP options to users with CAP_NET_RAW capability. This=
    prevents unprivileged applications from forcing packets to route through a= ttacker-controlled nodes to leak TCP ISN and possibly other protocol inform= ation. While LSRR and SSRR are commonly filtered in many network environmen= ts, they may still be supported and forwarded along some network paths. RFC=
    7126 (Recommendations on Filtering of IPv4 Packets Containing IPv4 Options=
    ) recommend to drop these options in 4.3 and 4.4. 2026-06-25 not yet calcul= ated CVE-2026-53249 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53249 ] L= inux--Linux In the Linux kernel, the following vulnerability has been resol= ved: Bluetooth: ISO: Fix not releasing hdev reference on iso_conn_big_sync = hci_get_route() returns a reference-counted hci_dev pointer via hci_dev_hol= d(). The function exits normally or with an error without ever releasing it=
    . 2026-06-25 not yet calculated CVE-2026-53251 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-53251 ] Linux--Linux In the Linux kernel, the following v= ulnerability has been resolved: Bluetooth: fix memory leak in error path of=
    hci_alloc_dev() Early failures in Bluetooth HCI UART configuration leak SR=
    CU percpu memory. When device initialization fails before hci_register_dev(=
    ) completes, the HCI_UNREGISTER flag is never set. As a result, when the de= vice reference count reaches zero, bt_host_release() evaluates this flag as=
    false and falls back to a direct kfree(hdev). Because hci_release_dev() is=
    bypassed, the SRCU struct initialized early in hci_alloc_dev() is never cl= eaned up, resulting in a leak of percpu memory. Fix the leak by explicitly = calling cleanup_srcu_struct() in the fallback (unregistered) branch of bt_h= ost_release() before freeing the device. 2026-06-25 not yet calculated CVE-= 2026-53252 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53252 ] Linux--Lin=
    ux In the Linux kernel, the following vulnerability has been resolved: Blue= tooth: MGMT: validate advertising TLV before type checks tlv_data_is_valid(=
    ) reads each advertising data field length from data[i], then inspects data=
    [i + 1] for managed EIR types before checking that the current field still = fits inside the supplied buffer. A malformed field whose length byte is the=
    last byte of the buffer can therefore make the parser read one byte past t=
    he advertising data. KASAN reported the following when a malformed MGMT_OP_= ADD_ADVERTISING request reached that path: BUG: KASAN: vmalloc-out-of-bound=
    s in tlv_data_is_valid() Read of size 1 Call trace: tlv_data_is_valid() add= _advertising() hci_mgmt_cmd() hci_sock_sendmsg() Move the existing element-= length check before any type-octet inspection so each non-empty element is = proven to contain its type byte before the parser looks at data[i + 1]. 202= 6-06-25 not yet calculated CVE-2026-53255 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-53255 ] Linux--Linux In the Linux kernel, the following vulner= ability has been resolved: wifi: cfg80211: enforce HE/EHT cap/oper consiste= ncy Xiang Mei reports that mac80211 could crash if eht_cap is set but eht_o= per isn't. Rather than fixing that for the individual user(s), enforce that=
    both HE/EHT have consistent elements. 2026-06-25 not yet calculated CVE-20= 26-53257 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53257 ] Linux--Linux=
    In the Linux kernel, the following vulnerability has been resolved: wifi: = fix leak if split 6 GHz scanning fails rdev->int_scan_req is leaked if cfg8= 0211_scan() fails. Note that it's supposed to be released at ___cfg80211_sc= an_done() but this doesn't happen as rdev->scan_req is NULL at that point, = too, leading to the early return from the freeing function. unreferenced ob= ject 0xffff8881161d0800 (size 512): comm "wpa_supplicant", pid 379, jiffies=
    4294749765 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 =
    00 00 00 00 ................ 00 00 00 00 00 00 00 00 f0 81 13 16 81 88 ff f=
    f ................ backtrace (crc c867fdb6): kmemleak_alloc+0x89/0x90 __kma= lloc_noprof+0x2fd/0x410 cfg80211_scan+0x133/0x730 nl80211_trigger_scan+0xc6= 9/0x1cc0 genl_family_rcv_msg_doit+0x204/0x2f0 genl_rcv_msg+0x431/0x6b0 netl= ink_rcv_skb+0x143/0x3f0 genl_rcv+0x27/0x40 netlink_unicast+0x4f6/0x820 netl= ink_sendmsg+0x797/0xce0 __sock_sendmsg+0xc4/0x160 ____sys_sendmsg+0x5e4/0x8=
    90 ___sys_sendmsg+0xf8/0x180 __sys_sendmsg+0x136/0x1e0 __x64_sys_sendmsg+0x= 76/0xc0 x64_sys_call+0x13f0/0x17d0 Found by Linux Verification Center (linu= xtesting.org). 2026-06-25 not yet calculated CVE-2026-53258 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-53258 ] Linux--Linux In the Linux kernel, th=
    e following vulnerability has been resolved: devlink: Release nested relati=
    on on devlink free devlink relation state is normally released from devl_un= register(), which calls devlink_rel_put(). This misses devlink instances th=
    at get a nested relation before registration and then fail probe before dev= l_register() is reached. That flow can happen for SFs. The child devlink ge=
    ts linked to its parent before registration, then a later probe error calls=
    devlink_free() directly. Since the instance was never registered, devl_unr= egister() is not called and devlink->rel is leaked. Release any pending rel= ation from devlink_free() as well. The registered path is unchanged because=
    devl_unregister() already clears devlink->rel before devlink_free() runs. = 2026-06-25 not yet calculated CVE-2026-53261 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-53261 ] Linux--Linux In the Linux kernel, the following vul= nerability has been resolved: 6lowpan: fix off-by-one in multicast context = address compression The second memcpy in lowpan_iphc_mcast_ctx_addr_compres= s() uses &data[1] as destination and &ipaddr->s6_addr[11] as source, but bo=
    th should be offset by one: &data[2] and &ipaddr->s6_addr[12] respectively.=
    This off-by-one has two consequences: 1. data[1] is overwritten with s6_ad= dr[11], corrupting the RIID field in the compressed multicast address 2. da= ta[5] is never written, so uninitialized kernel stack memory is transmitted=
    over the network via lowpan_push_hc_data(), leaking kernel stack contents = The correct inline data layout must match what the decompression function l= owpan_uncompress_multicast_ctx_daddr() expects: data[0..1] =3D s6_addr[1..2=
    ] (flags/scope + RIID) data[2..5] =3D s6_addr[12..15] (group ID) Also zero-= initialize the data array as a defensive measure against similar bugs in th=
    e future. 2026-06-25 not yet calculated CVE-2026-53263 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-53263 ] Linux--Linux In the Linux kernel, the fol= lowing vulnerability has been resolved: netfilter: synproxy: add mutex to g= uard hook reference counting As the synproxy infrastructure register netfil= ter hooks on-demand when a user adds the first iptables target or nftables = expression, if done concurrently they can race each other. Introduce a mute=
    x to serialize the refcount control blocks access from both frontends. Whil=
    e a per namespace mutex might be more efficient, it is not needed for targe= t/expression like SYNPROXY. 2026-06-25 not yet calculated CVE-2026-53269 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-53269 ] Linux--Linux In the Lin=
    ux kernel, the following vulnerability has been resolved: ksmbd: fix NULL-d= eref of opinfo->conn in oplock/lease break notifiers smb2_oplock_break_noti=
    () and smb2_lease_break_noti() read opinfo->conn into a local with neither = READ_ONCE() nor a NULL check. Both run from oplock_break() after opinfo_get= _list() has dropped ci->m_lock, so a concurrent SMB2 LOGOFF (session_fd_che= ck()) can set op->conn =3D NULL under ci->m_lock within that window. ksmbd_= conn_r_count_inc(conn) then writes through NULL at offset 0xc4 -- a remotel=
    y triggerable oops. Guard both reads the way compare_guid_key() already doe=
    s: read opinfo->conn with READ_ONCE() and return early if it is NULL, befor=
    e allocating the work struct so nothing leaks. A NULL conn means the client=
    is gone and the break is moot, so return 0; oplock_break() treats that as = success and runs the normal teardown. 2026-06-25 not yet calculated CVE-202= 6-53271 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53271 ] Linux--Linux =
    In the Linux kernel, the following vulnerability has been resolved: erofs: = fix use-after-free on sbi->sync_decompress z_erofs_decompress_kickoff() can=
    race with filesystem unmount, causing a use-after-free on sbi->sync_decomp= ress. When I/O completes, z_erofs_endio() calls z_erofs_decompress_kickoff(=
    ) to queue z_erofs_decompressqueue_work() asynchronously. Then, after all f= olios are unlocked, unmount workflow can proceed and sbi will be freed befo=
    re accessing to sbi->sync_decompress. Thread (unmount) I/O completion kwork=
    er queue_work z_erofs_decompressqueue_work (all folios are unlocked) cleanu= p_mnt .. erofs_kill_sb erofs_sb_free kfree(sbi) access sbi->sync_decompress=
    // UAF!! 2026-06-25 not yet calculated CVE-2026-53272 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-53272 ] Linux--Linux In the Linux kernel, the fol= lowing vulnerability has been resolved: net/smc: fix sleep-inside-lock in _= _smc_setsockopt() causing local DoS A logic flaw in __smc_setsockopt() allo=
    ws a local unprivileged user to cause a Denial of Service (DoS) by holding = the socket lock indefinitely. The function __smc_setsockopt() calls copy_fr= om_sockptr() while holding lock_sock(sk). By passing a userfaultfd-monitore=
    d memory page (or FUSE-backed memory on systems where unprivileged userfaul= tfd is disabled) as the optval, an attacker can halt execution during the c= opy operation, keeping the lock held. Combined with asynchronous tear-down = operations like shutdown(), this exhausts the kernel wq (kworkers) and trig= gers the hung task watchdog. [ 240.123456] INFO: task kworker/u8:2 blocked = for more than 120 seconds. [ 240.123489] Call Trace: [ 240.123501] smc_shut= down+... [ 240.123512] lock_sock_nested+... This patch moves the user-space=
    copy outside the lock_sock() critical section to prevent the issue. 2026-0= 6-25 not yet calculated CVE-2026-53274 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53274 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: arm_mpam: Check whether the config array is alloc= ated before destroying it __destroy_component_cfg() is called to free the c= onfiguration array. It uses the embedded 'garbage' structure, which means t=
    he array has to be allocated. If __destroy_component_cfg() is called from m= pam_disable() before the configuration was ever allocated, then a NULL poin= ter is dereferenced. Check for this case and return early if the configurat= ion is not allocated. __destroy_component_cfg() also frees the mbwu_state a=
    s this is allocated by __allocate_component_cfg(). As the mbwu_state is all= ocated after comp->cfg is set, and is also under mpam_list_lock, only the f= irst pointer needs checking. 2026-06-26 not yet calculated CVE-2026-53278 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-53278 ] Linux--Linux In the Li= nux kernel, the following vulnerability has been resolved: drm/gma500/oaktr= ail_lvds: fix hang on init failure The LVDS init code looks up an I2C adapt=
    er using i2c_get_adapter() and tries to read the EDID before falling back t=
    o allocating and registering its own adapter. The error handling does not s= eparate these cases so on a late init failure it will try to deregister and=
    free also an adapter that had previously been registered. Since i2c_get_ad= apter() takes another reference to the adapter, deregistration hangs indefi= nitely while waiting for the reference to be released. Fix this by only des= troying adapters allocated during LVDS init on errors. 2026-06-26 not yet c= alculated CVE-2026-53279 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5327=
    9 ] Linux--Linux In the Linux kernel, the following vulnerability has been = resolved: iommu: Fix NULL group->domain dereference in pci_dev_reset_iommu_= done() Local sashiko review pointed it out that group->domain could be NULL=
    when a default domain fails to allocate during the first probe, which can = crash at domain->ops->attach_dev dereference in __iommu_attach_device() inv= oked by pci_dev_reset_iommu_done(). pci_dev_reset_iommu_prepare() is fine a=
    s an old_domain pointer can be NULL. Skip the re-attach in pci_dev_reset_io= mmu_done() to fix the bug. 2026-06-26 not yet calculated CVE-2026-53280 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-53280 ] Linux--Linux In the Linu=
    x kernel, the following vulnerability has been resolved: x86/kexec: Push kj= ump return address even for non-kjump kexec The version of purgatory code s= hipped by kexec-tools attempts to look above the top of its stack to find a=
    return address for a kjump, even in a non-kjump kexec. After the commit in=
    Fixes: the word above the stack might not be there, leading to a fault (wh= ich is at least now caught by my exception-handling code in kexec). That co= mmit fixed things for the actual kjump path, but no longer "gratuitously" p= ushes the unused return address to the stack in the non-kjump path. Put tha=
    t *back* in the non-kjump path, to prevent purgatory from crashing when try= ing to access it. 2026-06-26 not yet calculated CVE-2026-53282 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-53282 ] Linux--Linux In the Linux kernel,=
    the following vulnerability has been resolved: iommu/amd: Bounds-check dev=
    id in __rlookup_amd_iommu() iommu_device_register() walks every device on t=
    he PCI bus via bus_for_each_dev() and calls amd_iommu_probe_device() for ea= ch. The inlined check_device() path computes the device's sbdf, calls rlook= up_amd_iommu() to find the owning IOMMU, and only afterwards verifies devid=
    <=3D pci_seg->last_bdf. __rlookup_amd_iommu() indexes rlookup_table[devid]=
    with no bounds check of its own, so for a PCI device whose BDF is not desc= ribed by the IVRS, the lookup reads past the end of the allocation before t=
    he caller's bounds check can run. This was harmless before commit e874c666b= 15b ("iommu/amd: Change rlookup, irq_lookup, and alias to use kvalloc()"): = the table was a zeroed page-order allocation, so the over-read returned NUL=
    L and the caller's NULL check skipped the device. After that commit the tab=
    le is a tight kvcalloc() and the over-read returns adjacent slab contents, = which check_device() then dereferences as a struct amd_iommu *, causing a b= oot-time GPF. Seen on Google Compute Engine ct6e VMs, where the virtualized=
    IVRS describes only the four TPU endpoints 00:04.0-07.0; the gVNIC at 00:0= 8.0 (devid 0x40) indexes 56 bytes past the 456-byte allocation, into the ad= jacent kmalloc-512 slab object: pci 0000:00:04.0: Adding to iommu group 0 p=
    ci 0000:00:05.0: Adding to iommu group 1 pci 0000:00:06.0: Adding to iommu = group 2 pci 0000:00:07.0: Adding to iommu group 3 Oops: general protection = fault, probably for non-canonical address 0x3a64695f78746382: 0000 [#1] SMP=
    NOPTI CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.22 #1 Hardware=
    name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/0= 6/2025 RIP: 0010:amd_iommu_probe_device+0x54/0x3a0 Call Trace: __iommu_prob= e_device+0x107/0x520 probe_iommu_group+0x29/0x50 bus_for_each_dev+0x7e/0xe0=
    iommu_device_register+0xc9/0x240 iommu_go_to_state+0x9c0/0x1c60 amd_iommu_= init+0x14/0x40 pci_iommu_init+0x16/0x60 do_one_initcall+0x47/0x2f0 Guard th=
    e array access in __rlookup_amd_iommu(). With the fix applied on 6.18.22, t=
    he gVNIC at 00:08.0 is skipped cleanly and the VM boots. 2026-06-26 not yet=
    calculated CVE-2026-53283 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53= 283 ] Linux--Linux In the Linux kernel, the following vulnerability has bee=
    n resolved: drm/amd/display: Wrap DCN32 phantom-plane allocation in DC_RUN_= WITH_PREEMPTION_ENABLED [Why] dcn32_validate_bandwidth() wraps dcn32_intern= al_validate_bw() with DC_FP_START()/DC_FP_END(). In x86 non-RT, DC_FP_START=
    takes fpregs_lock(), which disables local softirqs. The DML1 path through = dcn32_enable_phantom_plane() calls kvzalloc() to allocate ~335 KiB for dc_p= lane_state. This triggers the vmalloc path, which calls BUG_ON(in_interrupt= ()) because it's invoked within the FPU-enabled (softirq disabled) region, = leading to a kernel crash. [How] Wrap the dc_state_create_phantom_plane() c= all with the DC_RUN_WITH_PREEMPTION_ENABLED() macro to allow preemption dur= ing this memory allocation. (cherry picked from commit 885ccbef7b94a8b38f69= c4211c679021aa27ad11) 2026-06-26 not yet calculated CVE-2026-53285 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-53285 ] Linux--Linux In the Linux ker= nel, the following vulnerability has been resolved: idpf: fix double free a=
    nd use-after-free in aux device error paths When auxiliary_device_add() fai=
    ls in idpf_plug_vport_aux_dev() or idpf_plug_core_aux_dev(), the err_aux_de= v_add label calls auxiliary_device_uninit() and falls through to err_aux_de= v_init. The uninit call will trigger put_device(), which invokes the releas=
    e callback (idpf_vport_adev_release / idpf_core_adev_release) that frees ia= dev. The fall-through then reads adev->id from the freed iadev for ida_free=
    () and double-frees iadev with kfree(). Free the IDA slot and clear the bac= k-pointer before uninit, while adev is still valid, then return immediately=
    . Commit 65637c3a1811 ("idpf: fix UAF in RDMA core aux dev deinitialization=
    ") fixed the same use-after-free in the matching unplug path in this file b=
    ut missed both probe error paths. 2026-06-26 not yet calculated CVE-2026-53= 286 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53286 ] Linux--Linux In t=
    he Linux kernel, the following vulnerability has been resolved: audit: fix = incorrect inheritable capability in CAPSET records __audit_log_capset() rec= ords the effective capability set into the inheritable field due to a copy-= paste error. Every CAPSET audit record therefore reports cap_pi (process in= heritable) with the value of cap_effective instead of cap_inheritable. This=
    silently corrupts audit data used for compliance and forensic analysis: an=
    attacker who modifies inheritable capabilities to prepare for a privilege-= escalating exec would have the change masked in the audit trail. The bug ha=
    s been present since the original introduction of CAPSET audit records in 2= 008. 2026-06-26 not yet calculated CVE-2026-53287 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-53287 ] Linux--Linux In the Linux kernel, the followin=
    g vulnerability has been resolved: arm64: Reserve an extra page for early k= ernel mapping The final part of [data, end) segment may overflow into the n= ext page of init_pg_end[1] which is the gap page before early_init_stack[2]=
    : [1] crash_arm64_v9.0.1> vtop ffffffed00601000 VIRTUAL PHYSICAL ffffffed00= 601000 83401000 PAGE DIRECTORY: ffffffecffd62000 PGD: ffffffecffd62da0 =3D>=
    10000000833fb003 PMD: ffffff80033fb018 =3D> 10000000833fe003 PTE: ffffff80= 033fe008 =3D> 68000083401f03 PAGE: 83401000 PTE PHYSICAL FLAGS 68000083401f=
    03 83401000 (VALID|SHARED|AF|NG|PXN|UXN) PAGE PHYSICAL MAPPING INDEX CNT FL= AGS fffffffec00d0040 83401000 0 0 1 4000 reserved [2] ffffffed002c8000 (r) = __pi__data ffffffed0054e000 (d) __pi___bss_start ffffffed005f5000 (b) __pi_= init_pg_dir ffffffed005fe000 (b) __pi_init_pg_end ffffffed005ff000 (B) earl= y_init_stack ffffffed00608000 (b) __pi__end For 4K pages, the early kernel = mapping may use 2MB block entries but the kernel segments are only 64KB ali= gned. Segment boundaries that fall within a 2MB block therefore require a P=
    TE table so that different attributes can be applied on either side of the = boundary. KERNEL_SEGMENT_COUNT still correctly counts the five permanent ke= rnel VMAs registered by declare_kernel_vmas(). However, since commit 5973a6= 2efa34 ("arm64: map [_text, _stext) virtual address range non-executable+re= ad-only"), the early mapper also maps [_text, _stext) separately from [_ste= xt, _etext). This adds one more early-only split and can require one more p= age-table page than the existing EARLY_SEGMENT_EXTRA_PAGES allowance reserv= es. Increase the 4K-page early mapping allowance by one page to cover that = additional split. [catalin.marinas@arm.com: rewrote part of the commit log]=
    [catalin.marinas@arm.com: expanded the code comment] 2026-06-26 not yet ca= lculated CVE-2026-53288 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53288=
    ] Linux--Linux In the Linux kernel, the following vulnerability has been r= esolved: ice: fix NULL pointer dereference in ice_reset_all_vfs() ice_reset= _all_vfs() ignores the return value of ice_vf_rebuild_vsi(). When the VSI r= ebuild fails (e.g. during NVM firmware update via nvmupdate64e), ice_vsi_re= build() tears down the VSI on its error path, leaving txq_map and rxq_map a=
    s NULL. The subsequent unconditional call to ice_vf_post_vsi_rebuild() lead=
    s to a NULL pointer dereference in ice_ena_vf_q_mappings() when it accesses=
    vsi->txq_map[0]. The single-VF reset path in ice_reset_vf() already handle=
    s this correctly by checking the return value of ice_vf_reconfig_vsi() and = skipping ice_vf_post_vsi_rebuild() on failure. Apply the same pattern to ic= e_reset_all_vfs(): check the return value of ice_vf_rebuild_vsi() and skip = ice_vf_post_vsi_rebuild() and ice_eswitch_attach_vf() on failure. The VF is=
    left safely disabled (ICE_VF_STATE_INIT not set, VFGEN_RSTAT not set to VF= ACTIVE) and can be recovered via a VFLR triggered by a PCI reset of the VF = (sysfs reset or driver rebind). Note that this patch does not prevent the V=
    F VSI rebuild from failing during NVM update - the underlying cause is firm= ware being in a transitional state while the EMP reset is processed, which = can cause Admin Queue commands (ice_add_vsi, ice_cfg_vsi_lan) to fail. This=
    patch only prevents the subsequent NULL pointer dereference that crashes t=
    he kernel when the rebuild does fail. crash> bt PID: 50795 TASK: ff34c9ee70= 8dc680 CPU: 1 COMMAND: "kworker/u512:5" #0 [ff72159bcfe5bb50] machine_kexec=
    at ffffffffaa8850ee #1 [ff72159bcfe5bba8] __crash_kexec at ffffffffaaa15fb=
    a #2 [ff72159bcfe5bc68] crash_kexec at ffffffffaaa16540 #3 [ff72159bcfe5bc7=
    0] oops_end at ffffffffaa837eda #4 [ff72159bcfe5bc90] page_fault_oops at ff= ffffffaa893997 #5 [ff72159bcfe5bce8] exc_page_fault at ffffffffab528595 #6 = [ff72159bcfe5bd10] asm_exc_page_fault at ffffffffab600bb2 [exception RIP: i= ce_ena_vf_q_mappings+0x79] RIP: ffffffffc0a85b29 RSP: ff72159bcfe5bdc8 RFLA= GS: 00010206 RAX: 00000000000f0000 RBX: ff34c9efc9c00000 RCX: 0000000000000= 000 RDX: 0000000000000000 RSI: 0000000000000010 RDI: ff34c9efc9c00000 RBP: = ff34c9efc27d4828 R8: 0000000000000093 R9: 0000000000000040 R10: ff34c9efc27= d4828 R11: 0000000000000040 R12: 0000000000100000 R13: 0000000000000010 R14=
    : R15: ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ff72159bcfe5bdf8] i= ce_sriov_post_vsi_rebuild at ffffffffc0a85e2e [ice] #8 [ff72159bcfe5be08] i= ce_reset_all_vfs at ffffffffc0a920b4 [ice] #9 [ff72159bcfe5be48] ice_servic= e_task at ffffffffc0a31519 [ice] #10 [ff72159bcfe5be88] process_one_work at=
    ffffffffaa93dca4 #11 [ff72159bcfe5bec8] worker_thread at ffffffffaa93e9de = #12 [ff72159bcfe5bf18] kthread at ffffffffaa946663 #13 [ff72159bcfe5bf50] r= et_from_fork at ffffffffaa8086b9 The panic occurs attempting to dereference=
    the NULL pointer in RDX at ice_sriov.c:294, which loads vsi->txq_map (offs=
    et 0x4b8 in ice_vsi). The faulting VSI is an allocated slab object but not = fully initialized after a failed ice_vsi_rebuild(): crash> struct ice_vsi 0= xff34c9efc27d4828 netdev =3D 0x0, rx_rings =3D 0x0, tx_rings =3D 0x0, q_vec= tors =3D 0x0, txq_map =3D 0x0, rxq_map =3D 0x0, alloc_txq =3D 0x10, num_txq=
    =3D 0x10, alloc_rxq =3D 0x10, num_rxq =3D 0x10, The nvmupdate64e process w=
    as performing NVM firmware update: crash> bt 0xff34c9edd1a30000 PID: 49858 = TASK: ff34c9edd1a30000 CPU: 1 COMMAND: "nvmupdate64e" #0 [ff72159bcd617618]=
    __schedule at ffffffffab5333f8 #4 [ff72159bcd617750] ice_sq_send_cmd at ff= ffffffc0a35347 [ice] #5 [ff72159bcd6177a8] ice_sq_send_cmd_retry at fffffff= fc0a35b47 [ice] #6 [ff72159bcd617810] ice_aq_send_cmd at ffffffffc0a38018 [= ice] #7 [ff72159bcd617848] ice_aq_read_nvm at ffffffffc0a40254 [ice] #8 ---= truncated--- 2026-06-26 not yet calculated CVE-2026-53289 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-53289 ] Linux--Linux In the Linux kernel, the = following vulnerability has been resolved: ALSA: hda/conexant: Fix missing = error check for jack detection In cx_probe(), the return value of snd_hda_j= ack_detect_enable_callback() is ignored. This function returns a pointer, a=
    nd if it fails (e.g., due to memory allocation failure), it returns an erro=
    r pointer which must be checked using IS_ERR(). If the registration fails, = the driver continues to probe, but the jack detection callback will not be = registered. This can lead to a kernel crash later when the driver attempts =
    to handle jack events or accesses the uninitialized structure. Check the re= turn value using IS_ERR() and propagate the error via PTR_ERR() to the prob=
    e caller. 2026-06-26 not yet calculated CVE-2026-53291 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-53291 ] Linux--Linux In the Linux kernel, the fol= lowing vulnerability has been resolved: net: phonet: do not BUG_ON() in pn_= socket_autobind() on failed bind syzbot reported a kernel BUG triggered fro=
    m pn_socket_sendmsg() via pn_socket_autobind(): kernel BUG at net/phonet/so= cket.c:213! RIP: 0010:pn_socket_autobind net/phonet/socket.c:213 [inline] R= IP: 0010:pn_socket_sendmsg+0x240/0x250 net/phonet/socket.c:421 Call Trace: = sock_sendmsg_nosec+0x112/0x150 net/socket.c:797 __sock_sendmsg net/socket.c= :812 [inline] __sys_sendto+0x402/0x590 net/socket.c:2280 ... pn_socket_auto= bind() calls pn_socket_bind() with port 0 and, on -EINVAL, assumes the sock=
    et was already bound and asserts that the port is non-zero: err =3D pn_sock= et_bind(sock, ..., sizeof(struct sockaddr_pn)); if (err !=3D -EINVAL) retur=
    n err; BUG_ON(!pn_port(pn_sk(sock->sk)->sobject)); return 0; /* socket was = already bound */ However pn_socket_bind() also returns -EINVAL when sk->sk_= state is not TCP_CLOSE, even when the socket has never been bound and pn_po= rt() is still 0. In that case the BUG_ON() fires and panics the kernel from=
    a user-triggerable path. Treat the "bind returned -EINVAL but pn_port() is=
    still 0" case as a regular error and propagate -EINVAL to the caller inste=
    ad of crashing. Existing callers already translate a non-zero return from p= n_socket_autobind() into -ENOBUFS/-EAGAIN, so returning -EINVAL here only c= hanges behaviour from panic to a normal errno. 2026-06-26 not yet calculate=
    d CVE-2026-53292 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53292 ] Linu= x--Linux In the Linux kernel, the following vulnerability has been resolved=
    : drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG There were multiple issues in th=
    at code. First of all the order between the reset semaphore and the mm_lock=
    was wrong (e.g. copy_to_user) was called while holding the lock. Then we a= llocated memory while holding the reset semaphore which is also a pretty bi=
    g bug and can deadlock. Then we used down_read_trylock() instead of waiting=
    for the reset to finish. (cherry picked from commit 361b6e6b303d4b691f6c59= 74d3eaab67ca6dd90e) 2026-06-26 not yet calculated CVE-2026-53293 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-53293 ] Linux--Linux In the Linux kerne=
    l, the following vulnerability has been resolved: mailbox: mailbox-test: do= n't free the reused channel The RX channel can be aliased to the TX channel=
    if it has a different MMIO. This special case needs to be handled when fre= eing the channels otherwise a double-free occurs. 2026-06-26 not yet calcul= ated CVE-2026-53294 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53294 ] L= inux--Linux In the Linux kernel, the following vulnerability has been resol= ved: mailbox: add sanity check for channel array Fail gracefully if there i=
    s no channel array attached to the mailbox controller. Otherwise the later = dereference will cause an OOPS which might not be seen because mailbox cont= rollers might instantiate very early. Remove the comment explaining the obv= ious while here. 2026-06-26 not yet calculated CVE-2026-53295 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-53295 ] Linux--Linux In the Linux kernel, = the following vulnerability has been resolved: mailbox: mailbox-test: free = channels on probe error On probe error, free the previously obtained channe= ls. This not only prevents a leak, but also UAF scenarios because the clien=
    t structure will be removed nonetheless because it was allocated with devm.=
    2026-06-26 not yet calculated CVE-2026-53296 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-53296 ] Linux--Linux In the Linux kernel, the following vu= lnerability has been resolved: net: mana: Guard mana_remove against double = invocation If PM resume fails (e.g., mana_attach() returns an error), mana_= probe() calls mana_remove(), which tears down the device and sets gd->gdma_= context =3D NULL and gd->driver_data =3D NULL. However, a failed resume cal= lback does not automatically unbind the driver. When the device is eventual=
    ly unbound, mana_remove() is invoked a second time. Without a NULL check, i=
    t dereferences gc->dev with gc =3D=3D NULL, causing a kernel panic. Add an = early return if gdma_context or driver_data is NULL so the second invocatio=
    n is harmless. Move the dev =3D gc->dev assignment after the guard so it ca= nnot dereference NULL. 2026-06-26 not yet calculated CVE-2026-53297 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-53297 ] Linux--Linux In the Linux ke= rnel, the following vulnerability has been resolved: net: airoha: Move ndes=
    c initialization at end of airoha_qdma_init_rx_queue() If queue entry or DM=
    A descriptor list allocation fails in airoha_qdma_init_rx_queue routine, ai= roha_qdma_cleanup() will trigger a NULL pointer dereference running netif_n= api_del() for RX queue NAPIs since netif_napi_add() has never been executed=
    to this particular RX NAPI. The issue is due to the early ndesc initializa= tion in airoha_qdma_init_rx_queue() since airoha_qdma_cleanup() relies on n= desc value to check if the queue is properly initialized. Fix the issue mov= ing ndesc initialization at end of airoha_qdma_init_tx routine. Move page_p= ool allocation after descriptor list allocation in order to avoid memory le= aks if desc allocation fails. 2026-06-26 not yet calculated CVE-2026-53298 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-53298 ] Linux--Linux In the L= inux kernel, the following vulnerability has been resolved: net: airoha: Mo=
    ve ndesc initialization at end of airoha_qdma_init_tx() If queue entry list=
    allocation fails in airoha_qdma_init_tx_queue routine, airoha_qdma_cleanup= _tx_queue() will trigger a NULL pointer dereference accessing the queue ent=
    ry array. The issue is due to the early ndesc initialization in airoha_qdma= _init_tx_queue(). Fix the issue moving ndesc initialization at end of airoh= a_qdma_init_tx routine. 2026-06-26 not yet calculated CVE-2026-53299 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-53299 ] Linux--Linux In the Linux k= ernel, the following vulnerability has been resolved: reset: amlogic: t7: F=
    ix null reset ops Fix missing reset ops causing kernel null pointer derefer= ence. This SOC's reset is currently not used yet. 2026-06-26 not yet calcul= ated CVE-2026-53301 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53301 ] L= inux--Linux In the Linux kernel, the following vulnerability has been resol= ved: crypto: eip93 - fix hmac setkey algo selection eip93_hmac_setkey() all= ocates a temporary ahash transform for computing HMAC ipad/opad key materia=
    l. The allocation uses the driver-specific cra_driver_name (e.g. "sha256-ei= p93") but passes CRYPTO_ALG_ASYNC as the mask, which excludes async algorit= hms. Since the EIP93 hash algorithms are the only ones registered under tho=
    se driver names and they are inherently async, the lookup is self-contradic= tory and always fails with -ENOENT. When called from the AEAD setkey path, = this failure leaves the SA record partially initialized with zeroed digest = fields. A subsequent crypto operation then dereferences a NULL pointer in t=
    he request context, resulting in a kernel panic: ``` pc : eip93_aead_handle= _result+0xc8c/0x1240 [crypto_hw_eip93] lr : eip93_aead_handle_result+0xbec/= 0x1240 [crypto_hw_eip93] sp : ffffffc082feb820 x29: ffffffc082feb820 x28: f= fffff8011043980 x27: 0000000000000000 x26: 0000000000000000 x25: ffffffc078= da0bc8 x24: 0000000091043980 x23: ffffff8004d59e50 x22: ffffff8004d59410 x2=
    1: ffffff8004d593c0 x20: ffffff8004d593c0 x19: ffffff8004d4f300 x18: 000000= 0000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000007fda7aa49=
    8 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: 00= 00000000000000 x10: fffffffff8127a80 x9 : 0000000000000000 x8 : ffffff8004d= 4f380 x7 : 0000000000000000 x6 : 000000000000003f x5 : 0000000000000040 x4 =
    : 0000000000000008 x3 : 0000000000000009 x2 : 0000000000000008 x1 : 0000000= 028000003 x0 : ffffff8004d388c0 Code: 910142b6 f94012e0 f9002aa0 f90006d3 (= f9400740) ``` The reported symbol eip93_aead_handle_result+0xc8c is a resol= ution artifact from static functions being merged under the nearest exporte=
    d symbol. Decoding the faulting sequence: ``` 910142b6 ADD X22, X21, #0x50 = f94012e0 LDR X0, [X23, #0x20] f9002aa0 STR X0, [X21, #0x50] f90006d3 STR X1=
    9, [X22, #0x8] f9400740 LDR X0, [X26, #0x8] ``` The faulting LDR at [X26, #= 0x8] is loading ctx->flags (offset 8 in eip93_hash_ctx), where ctx has been=
    resolved to NULL from a partially initialized or unreachable transform con= text following the failed setkey. Fix this by dropping the CRYPTO_ALG_ASYNC=
    mask from the crypto_alloc_ahash() call. The code already handles async co= mpletion correctly via crypto_wait_req(), so there is no requirement to res= trict the lookup to synchronous algorithms. Note that hashing a single 64-b= yte block through the hardware is likely slower than doing it in software d=
    ue to the DMA round-trip overhead, but offloading it may still spare CPU cy= cles on the slower embedded cores where this IP is found. [Detailed investi= gation report of this bug] 2026-06-26 not yet calculated CVE-2026-53302 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-53302 ] Linux--Linux In the Linu=
    x kernel, the following vulnerability has been resolved: f2fs: protect exte= nsion_list reading with sb_lock in f2fs_sbi_show() In f2fs_sbi_show(), the = extension_list, extension_count and hot_ext_count are read without holding = sbi->sb_lock. If a concurrent sysfs store modifies the extension list via f= 2fs_update_extension_list(), the show path may read inconsistent count and = array contents, potentially leading to out-of-bounds access or displaying s= tale data. Fix this by holding sb_lock around the entire extension list rea=
    d and format operation. 2026-06-26 not yet calculated CVE-2026-53303 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-53303 ] Linux--Linux In the Linux k= ernel, the following vulnerability has been resolved: scsi: sg: Resolve sof=
    t lockup issue when opening /dev/sgX The parameter def_reserved_size define=
    s the default buffer size reserved for each Sg_fd and should be restricted =
    to a range between 0 and 1,048,576 (see https://tldp.org/HOWTO/SCSI-Generic= -HOWTO/proc.html). Although the function sg_proc_write_dressz enforces this=
    limit, it is possible to bypass it by directly modifying the module parame= ter as shown below, which then causes a soft lockup: echo -1 > /sys/module/= sg/parameters/def_reserved_size exec 4<> /dev/sg0 watchdog: BUG: soft locku=
    p - CPU#5 stuck for 26 seconds! [bash:537] Modules loaded: CPU: 5 UID: 0 PI=
    D: 537 Command: bash, kernel version 6.19.0-rc3+ #134, PREEMPT disabled Har= dware: QEMU Standard PC (i440FX + PIIX, 1996), BIOS version 1.16.1-2.fc37 d= ated 04/01/2014 ... Call Trace: sg_build_reserve+0x5c/0xa0 sg_add_sfp+0x168= /0x270 sg_open+0x16e/0x340 chrdev_open+0xbe/0x230 do_dentry_open+0x175/0x48=
    0 vfs_open+0x34/0xf0 do_open+0x265/0x3d0 path_openat+0x110/0x290 do_filp_op= en+0xc3/0x170 do_sys_openat2+0x71/0xe0 __x64_sys_openat+0x6d/0xa0 do_syscal= l_64+0x62/0x310 entry_SYSCALL_64_after_hwframe+0x76/0x7e The fix is to use = module_param_cb to validate and reject invalid values assigned to def_reser= ved_size. 2026-06-26 not yet calculated CVE-2026-53304 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-53304 ] Linux--Linux In the Linux kernel, the fol= lowing vulnerability has been resolved: usb: typec: ps883x: Fix Oops at unb= ind When trying to unbind a device in order to bind to it vfio-platform as:=
    echo bc0000.geniqup > /sys/bus/platform/devices/bc0000.geniqup/driver/unbi=
    nd I get the following Oops: [ 436.478639] Unable to handle kernel NULL poi= nter dereference at virtual address 0000000000000020 [ 436.487762] Mem abor=
    t info: [ 436.490716] ESR =3D 0x0000000096000004 [ 436.494595] EC =3D 0x25:=
    DABT (current EL), IL =3D 32 bits [ 436.500071] SET =3D 0, FnV =3D 0 [ 436= .503250] EA =3D 0, S1PTW =3D 0 [ 436.506505] FSC =3D 0x04: level 0 translat= ion fault [ 436.511533] Data abort info: [ 436.514558] ISV =3D 0, ISS =3D 0= x00000004, ISS2 =3D 0x00000000 [ 436.520215] CM =3D 0, WnR =3D 0, TnD =3D 0=
    , TagAccess =3D 0 [ 436.525436] GCS =3D 0, Overlay =3D 0, DirtyBit =3D 0, X=
    s =3D 0 [ 436.530918] user pgtable: 4k pages, 48-bit VAs, pgdp=3D0000000886= 1a9000 [ 436.537554] [0000000000000020] pgd=3D0000000000000000, p4d=3D00000= 00000000000 [ 436.544548] Internal error: Oops: 0000000096000004 [#1] SMP [=
    436.550374] Modules linked in: [ 436.553542] CPU: 2 UID: 0 PID: 671 Comm: = bash Tainted: G W 7.0.0-rc3-g56fcdd0911a5-dirty #2 PREEMPT [ 436.564440] Ta= inted: [W]=3DWARN [ 436.567515] Hardware name: LENOVO 91B6CTO1WW/3796, BIOS=
    O6NKT3BA 05/02/2025 [ 436.574675] pstate: 21400005 (nzCv daif +PAN -UAO -T=
    CO +DIT -SSBS BTYPE=3D--) [ 436.581841] pc : ps883x_retimer_remove+0x14/0x9=
    4 [ 436.586605] lr : i2c_device_remove+0x28/0x84 [ 436.591017] sp : ffff800= 0847137c0 That's because the ps883x_retimer_remove() retrieves the driver d= ata from i2c_get_clientdata() which was never set at probe. So, add i2c_set= _clientdata() at the end of the probe. 2026-06-26 not yet calculated CVE-20= 26-53305 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53305 ] Linux--Linux=
    In the Linux kernel, the following vulnerability has been resolved: tty: h= vc_iucv: fix off-by-one in number of supported devices MAX_HVC_IUCV_LINES = =3D=3D HVC_ALLOC_TTY_ADAPTERS =3D=3D 8. This is the number of entries in: s= tatic struct hvc_iucv_private *hvc_iucv_table[MAX_HVC_IUCV_LINES]; Sometime=
    s hvc_iucv_table[] is limited by: (a) if (num > hvc_iucv_devices) // for er= ror detection or (b) for (i =3D 0; i < hvc_iucv_devices; i++) // in 2 place=
    s (so these 2 don't agree; second one appears to be correct to me.) hvc_iuc= v_devices can be 0..8. This is a counter. (c) if (hvc_iucv_devices > MAX_HV= C_IUCV_LINES) If hvc_iucv_devices =3D=3D 8, (a) allows the code to access h= vc_iucv_table[8]. Oops. 2026-06-26 not yet calculated CVE-2026-53306 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-53306 ] Linux--Linux In the Linux k= ernel, the following vulnerability has been resolved: pinctrl: pinconf-gene= ric: Fully validate 'pinmux' property The pinconf_generic_parse_dt_pinmux()=
    assumes that the 'pinmux' property is not empty when present. This might b=
    e not true. With that, the allocator will give a special value in return an=
    d not NULL which lead to the crash when trying to access that (invalid) mem= ory. Fix that by fully validating 'pinmux' value, including its length. 202= 6-06-26 not yet calculated CVE-2026-53307 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-53307 ] Linux--Linux In the Linux kernel, the following vulner= ability has been resolved: power: supply: max77705: Free allocated workqueu=
    e and fix removal order Use devm interface for allocating workqueue to fix = two bugs at the same time: 1. Driver leaks the memory on remove(), because = the workqueue is not destroyed. 2. Driver allocates workqueue and then regi= sters interrupt handlers with devm interface. This means that probe error p= aths will not use a reversed order, but first destroy the workqueue and the=
    n, via devm release handlers, free the interrupt. The interrupt handler sch= edules work on this exact workqueue, thus if interrupt is hit in this short=
    time window - after destroying workqueue, but before devm() frees the inte= rrupt - the schedulled work will lead to use of freed memory. Change is not=
    equivalent in the workqueue itself: use non-legacy API which does not set = (__WQ_LEGACY | WQ_MEM_RECLAIM). The workqueue is used to update power suppl=
    y (power_supply_changed()) status, thus there is no point to run it for mem= ory reclaim. Note that dev_name() is not directly used in second argument t=
    o prevent possible unlikely parsing any "%" character in device name as for= mat. 2026-06-26 not yet calculated CVE-2026-53308 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-53308 ] Linux--Linux In the Linux kernel, the followin=
    g vulnerability has been resolved: soc/tegra: cbb: Fix cross-fabric target = timeout lookup When a fabric receives an error interrupt, the error may hav=
    e occurred on a different fabric. The target timeout lookup was using the w= rong base address (cbb->regs) with offsets from a different fabric's target=
    map, causing a kernel page fault. Unable to handle kernel paging request a=
    t virtual address ffff80000954cc00 pc : tegra234_cbb_get_tmo_slv+0xc/0x28 C= all trace: tegra234_cbb_get_tmo_slv+0xc/0x28 print_err_notifier+0x6c0/0x7d0=
    tegra234_cbb_isr+0xe4/0x1b4 Add tegra234_cbb_get_fabric() to look up the c= orrect fabric device using fab_id, and use its base address for accessing t= arget timeout registers. 2026-06-26 not yet calculated CVE-2026-53310 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-53310 ] Linux--Linux In the Linux = kernel, the following vulnerability has been resolved: fuse: fix uninit-val=
    ue in fuse_dentry_revalidate() fuse_dentry_revalidate() may be called with =
    a dentry that didn't had ->d_time initialised. The issue was found with KMS= AN, where lookup_open() calls __d_alloc(), followed by d_revalidate(), as s= hown below: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D BUG: KMSAN: uninit-value in fuse_dentry_revalidate+0x= 150/0x13d0 fs/fuse/dir.c:394 fuse_dentry_revalidate+0x150/0x13d0 fs/fuse/di= r.c:394 d_revalidate fs/namei.c:1030 [inline] lookup_open fs/namei.c:4405 [= inline] open_last_lookups fs/namei.c:4583 [inline] path_openat+0x1614/0x64c=
    0 fs/namei.c:4827 do_file_open+0x2aa/0x680 fs/namei.c:4859 [...] Uninit was=
    created at: slab_post_alloc_hook mm/slub.c:4466 [inline] slab_alloc_node m= m/slub.c:4788 [inline] kmem_cache_alloc_lru_noprof+0x382/0x1280 mm/slub.c:4= 807 __d_alloc+0x55/0xa00 fs/dcache.c:1740 d_alloc_parallel+0x99/0x2740 fs/d= cache.c:2604 lookup_open fs/namei.c:4398 [inline] open_last_lookups fs/name= i.c:4583 [inline] path_openat+0x135f/0x64c0 fs/namei.c:4827 do_file_open+0x= 2aa/0x680 fs/namei.c:4859 [...] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 2026-06-26 not yet calculated CV= E-2026-53311 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53311 ] Linux--L= inux In the Linux kernel, the following vulnerability has been resolved: io= mmu/riscv: Remove overflows on the invalidation path Since RISC-V supports =
    a sign extended page table it should support a gather->end of ULONG_MAX, bu=
    t if this happens it will infinite loop because of the overflow. Also avoid=
    overflow computing the length by moving the +1 to the other side of the < = 2026-06-26 not yet calculated CVE-2026-53312 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-53312 ] Linux--Linux In the Linux kernel, the following vul= nerability has been resolved: drm/amd/display: Avoid NULL dereference in dc= _dmub_srv error paths In dc_dmub_srv_log_diagnostic_data() and dc_dmub_srv_= enable_dpia_trace(). Both functions check: if (!dc_dmub_srv || !dc_dmub_srv= ->dmub) and then call DC_LOG_ERROR() inside that block. DC_LOG_ERROR() uses=
    dc_dmub_srv->ctx internally. So if dc_dmub_srv is NULL, the logging itself=
    can dereference a NULL pointer and cause a crash. Fix this by splitting th=
    e checks. First check if dc_dmub_srv is NULL and return immediately. Then c= heck dc_dmub_srv->dmub and log the error only when dc_dmub_srv is valid. Fi= xes the below: ../display/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_d= ata() error: we previously assumed 'dc_dmub_srv' could be null (see line 96=
    1) ../display/dc/dc_dmub_srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: =
    we previously assumed 'dc_dmub_srv' could be null (see line 1166) 2026-06-2=
    6 not yet calculated CVE-2026-53313 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-53313 ] Linux--Linux In the Linux kernel, the following vulnerabilit=
    y has been resolved: padata: Put CPU offline callback in ONLINE section to = allow failure syzbot reported the following warning: DEAD callback error fo=
    r CPU1 WARNING: kernel/cpu.c:1463 at _cpu_down+0x759/0x1020 kernel/cpu.c:14= 63, CPU#0: syz.0.1960/14614 at commit 4ae12d8bd9a8 ("Merge tag 'kbuild-fixe= s-7.0-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux") wh= ich tglx traced to padata_cpu_dead() given it's the only sub-CPUHP_TEARDOWN= _CPU callback that returns an error. Failure isn't allowed in hotplug state=
    s before CPUHP_TEARDOWN_CPU so move the CPU offline callback to the ONLINE = section where failure is possible. 2026-06-26 not yet calculated CVE-2026-5= 3314 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53314 ] Linux--Linux In = the Linux kernel, the following vulnerability has been resolved: drm/amd/ra=
    s: Fix NULL deref in ras_core_get_utc_second_timestamp() ras_core_get_utc_s= econd_timestamp() retrieves the current UTC timestamp (in seconds since the=
    Unix epoch) through a platform-specific RAS system callback and is used fo=
    r timestamping RAS error events. The function checks ras_core in the condit= ional statement before calling the sys_fn callback. However, when the condi= tion fails, the function prints an error message using ras_core->dev. If ra= s_core is NULL, this can lead to a potential NULL pointer dereference when = accessing ras_core->dev. Add an early NULL check for ras_core at the beginn= ing of the function and return 0 when the pointer is not valid. This preven=
    ts the dereference and makes the control flow clearer. 2026-06-26 not yet c= alculated CVE-2026-53315 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5331=
    5 ] Linux--Linux In the Linux kernel, the following vulnerability has been = resolved: drm/amd/ras: Fix NULL deref in ras_core_ras_interrupt_detected() = Fixes a NULL pointer dereference when ras_core is NULL and ras_core->dev is=
    accessed in the error path. Reported by: Dan Carpenter <dan.carpenter@lina= ro.org> 2026-06-26 not yet calculated CVE-2026-53316 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-53316 ] Linux--Linux In the Linux kernel, the follo= wing vulnerability has been resolved: wifi: mt76: mt7921: Place upper limit=
    on station AID Any station configured with an AID over 20 causes a firmwar=
    e crash. This situation occurred in our testing using an AP interface on 79=
    22 hardware, with a modified hostapd, sourced from Mediatek's OpenWRT feeds=
    . In stock hostapd, station AIDs begin counting at 1, and this configuratio=
    n is prevented with an upper limit on associated stations. However, the mod= ified hostapd began allocation at 65, which caused the firmware to crash. T= his fix does not allow these AIDs to work, but will prevent the firmware cr= ash. This crash was only seen on IFTYPE_AP interfaces, and the fix does not=
    appear to have an effect on IFTYPE_STATION behavior. 2026-06-26 not yet ca= lculated CVE-2026-53317 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53317=
    ] Linux--Linux In the Linux kernel, the following vulnerability has been r= esolved: wifi: mt76: mt7925: prevent NULL pointer dereference in mt7925_tx_= check_aggr() Move the NULL check for 'sta' before dereferencing it to preve=
    nt a possible crash. 2026-06-26 not yet calculated CVE-2026-53318 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-53318 ] Linux--Linux In the Linux kern= el, the following vulnerability has been resolved: blk-wbt: remove WARN_ON_= ONCE from wbt_init_enable_default() wbt_init_enable_default() uses WARN_ON_= ONCE to check for failures from wbt_alloc() and wbt_init(). However, both a=
    re expected failure paths: - wbt_alloc() can return NULL under memory press= ure (-ENOMEM) - wbt_init() can fail with -EBUSY if wbt is already registere=
    d syzbot triggers this by injecting memory allocation failures during MTD p= artition creation via ioctl(BLKPG), causing a spurious warning. wbt_init_en= able_default() is a best-effort initialization called from blk_register_que= ue() with a void return type. Failure simply means the disk operates withou=
    t writeback throttling, which is harmless. Replace WARN_ON_ONCE with plain = if-checks, consistent with how wbt_set_lat() in the same file already handl=
    es these failures. Add a pr_warn() for the wbt_init() failure to retain dia= gnostic information without triggering a full stack trace. 2026-06-26 not y=
    et calculated CVE-2026-53319 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 53319 ] Linux--Linux In the Linux kernel, the following vulnerability has b= een resolved: nilfs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_di= rty() nilfs_ioctl_mark_blocks_dirty() uses bd_oblocknr to detect dead block=
    s by comparing it with the current block number bd_blocknr. If they differ,=
    the block is considered dead and skipped. However, bd_oblocknr should neve=
    r be 0 since block 0 typically stores the primary superblock and is never a=
    valid GC target block. A corrupted ioctl request with bd_oblocknr set to 0=
    causes the comparison to incorrectly match when the lookup returns -ENOENT=
    and sets bd_blocknr to 0, bypassing the dead block check and calling nilfs= _bmap_mark() on a non-existent block. This causes nilfs_btree_do_lookup() t=
    o return -ENOENT, triggering the WARN_ON(ret =3D=3D -ENOENT). Fix this by r= ejecting ioctl requests with bd_oblocknr set to 0 at the beginning of each = iteration. [ryusuke: slightly modified the commit message and comments for = accuracy] 2026-06-26 not yet calculated CVE-2026-53320 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-53320 ] Linux--Linux In the Linux kernel, the fol= lowing vulnerability has been resolved: io_uring/napi: cap busy_poll_to 10 = msec Currently there's no cap on the maximum amount of time that napi is al= lowed to poll if no events are found, which can lead to kernel complaints o=
    n a task being stuck as there's no conditional rescheduling done within tha=
    t loop. Just cap it to 10 msec in total, that's already way above any kind =
    of sane value that will reap any benefits, yet low enough that it's nowhere=
    near being able to trigger preemption complaints. 2026-06-26 not yet calcu= lated CVE-2026-53321 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53321 ] = Linux--Linux In the Linux kernel, the following vulnerability has been reso= lved: net: dsa: remove redundant netdev_lock_ops() from conduit ethtool ops=
    DSA replaces the conduit (master) device's ethtool_ops with its own wrappe=
    rs that aggregate stats from both the conduit and DSA switch ports. Taking = the lock again inside the DSA wrappers causes a deadlock. Stumbled upon thi=
    s when booting qemu with fbnic and CONFIG_NET_DSA_LOOP=3Dy (which looks lik=
    e some kind of testing device that auto-populates the ports of eth0). `etht= ool -i` is enough to deadlock. This means we have basically zero coverage f=
    or DSA stuff with real ops locked devs. Remove the redundant netdev_lock_op= s()/netdev_unlock_ops() calls from the DSA conduit ethtool wrappers. 2026-0= 6-26 not yet calculated CVE-2026-53323 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-53323 ] Linux--Linux In the Linux kernel, the following vulnera= bility has been resolved: net: mana: Use pci_name() for debugfs directory n= aming Use pci_name(pdev) for the per-device debugfs directory instead of ha= rdcoded "0" for PFs and pci_slot_name(pdev->slot) for VFs. The previous app= roach had two issues: 1. pci_slot_name() dereferences pdev->slot, which can=
    be NULL for VFs in environments like generic VFIO passthrough or nested KV=
    M, causing a NULL pointer dereference. 2. Multiple PFs would all use "0", a=
    nd VFs across different PCI domains or buses could share the same slot name=
    , leading to -EEXIST errors from debugfs_create_dir(). pci_name(pdev) retur=
    ns the unique BDF address, is always valid, and is unique across the system=
    . 2026-06-26 not yet calculated CVE-2026-53324 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-53324 ] LY Corporation--Central Dogma A vulnerability has=
    been identified in centraldogma-server-mirror-git versions prior to 0.84.0=
    , where the Git mirror SSH client does not verify remote host keys for git+= ssh:// connections, allowing an on-path attacker to perform man-in-the-midd=
    le attacks and compromise mirrored repositories. 2026-06-22 not yet calcula= ted CVE-2026-11745 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11745 ] LY=
    Corporation--Central Dogma A vulnerability has been identified in centrald= ogma-server versions prior to 0.84.0, where enabling ZooKeeper replication = without setting replication.secret causes the server to silently fall back =
    to a hard-coded, publicly known secret. This default credential authenticat=
    es the embedded ZooKeeper ensemble, allowing an attacker with network acces=
    s to read the full replication log or join the quorum and execute arbitrary=
    replicated commands across the cluster. 2026-06-22 not yet calculated CVE-= 2026-11746 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11746 ] LY Corpora= tion--Central Dogma A vulnerability has been identified in centraldogma-ser= ver-auth-shiro versions prior to 0.84.0, where the SearchFirstActiveDirecto= ryRealm substitutes the login username into an LDAP search filter without n= eutralizing LDAP filter metacharacters, allowing an unauthenticated attacke=
    r to manipulate the filter to cause authentication confusion and enumerate = the directory structure. 2026-06-22 not yet calculated CVE-2026-11748 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-11748 ] Mailerup--Mailerup Open re= direct vulnerability (CWE-601) in the _safe_redirect function of the click-= tracking endpoint (/c/<token>/) in Mailerup <1.0.0=C2=A0on all platforms al= lows remote unauthenticated attackers to redirect victims to arbitrary exte= rnal sites and conduct phishing attacks via a crafted u=C2=A0query paramete=
    r, because the URL scheme is validated (blocking javascript: and data:) but=
    the destination host is not restricted to an allowlist, and a signing.BadS= ignature exception is silently caught so a valid signed token is not requir= ed. 2026-06-24 not yet calculated CVE-2026-13163 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-13163 ] Mailerup--Mailerup Missing Authentication for C= ritical Function (CWE-306) in the RegisterView (apps/accounts/views.py), ex= posed at POST /api/auth/register/, in MailerUp <1.0.1 allows a remote, unau= thenticated attacker to self-register a working account on instances where = registration is intended to be restricted, because the endpoint applies the=
    AllowAny permission with no email verification, CAPTCHA, or administrator = approval. Any account created this way can read all email stored by the ins= tance, resulting in full disclosure of stored messages to an arbitrary unau= thenticated attacker 2026-06-24 not yet calculated CVE-2026-13164 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-13164 ] mastodon--mastodon Mastodon is=
    a free, open-source social network server based on ActivityPub. Prior to 4= .5.10, 4.4.17, and 4.3.23, the list of disallowed IP address ranges was lac= king an IP address range that can be used to reach local IP addresses. An a= ttacker can use an IP address in the affected range to make Mastodon perfor=
    m HTTP requests against loopback interfaces, potentially allowing access to=
    otherwise private resources and services. This vulnerability is fixed in 4= .5.10, 4.4.17, and 4.3.23. 2026-06-24 not yet calculated CVE-2026-46348 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-46348 ] MessagePack-CSharp--Mess= agePack-CSharp MessagePack for C# is a MessagePack serializer for C#. Prior=
    to 2.5.301 and 3.1.7, MessagePackReader.ReadDateTime() can allocate stack = memory based on an attacker-controlled MessagePack extension length. In the=
    slow path for timestamp extension parsing, the computed tokenSize includes=
    the extension body length from the wire and is used in a stackalloc operat= ion before the extension length is validated as one of the valid timestamp = sizes. A very small payload can claim a large timestamp extension body and = cause a stack allocation large enough to trigger an uncatchable StackOverfl= owException, terminating the host process. This vulnerability is fixed in 2= .5.301 and 3.1.7. 2026-06-22 not yet calculated CVE-2026-48502 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-48502 ] MessagePack-CSharp--MessagePack-C= Sharp MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.3=
    01 and 3.1.7, the parameterless MessagePackInputFormatter() constructor use=
    s default serializer options, which resolve to MessagePackSerializerOptions= .Standard with MessagePackSecurity.TrustedData. The formatter is designed f=
    or ASP.NET Core MVC request bodies, which commonly cross an HTTP trust boun= dary. This insecure default can expose applications to denial-of-service at= tacks that MessagePackSecurity.UntrustedData is intended to mitigate, such =
    as hash-collision attacks against dictionary-like model properties. This vu= lnerability is fixed in 2.5.301 and 3.1.7. 2026-06-22 not yet calculated CV= E-2026-48509 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48509 ] MessageP= ack-CSharp--MessagePack-CSharp MessagePack for C# is a MessagePack serializ=
    er for C#. Prior to 2.5.301 and 3.1.7, when MessagePack-CSharp decompresses=
    Lz4Block or Lz4BlockArray payloads, it reads declared uncompressed lengths=
    from the wire and allocates output buffers based on those lengths before v= alidating that the compressed data is valid or that the declared expansion =
    is reasonable. A small payload can claim a very large uncompressed length a=
    nd force a large allocation before LZ4 decoding begins. This vulnerability =
    is fixed in 2.5.301 and 3.1.7. 2026-06-22 not yet calculated CVE-2026-48510=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-48510 ] MessagePack-CSharp--= MessagePack-CSharp MessagePack for C# is a MessagePack serializer for C#. P= rior to 2.5.301 and 3.1.7, ExpandoObjectFormatter.Deserialize populates Sys= tem.Dynamic.ExpandoObject by calling IDictionary<string, object>.Add for ea=
    ch map entry. ExpandoObject internally maintains member names in array-like=
    structures, so inserting many distinct keys can require repeated linear sc= ans and array copies. For large attacker-controlled maps, this produces qua= dratic CPU and allocation behavior. The issue is especially surprising beca= use ExpandoObjectResolver.Options is configured with MessagePackSecurity.Un= trustedData, but collision-resistant dictionary comparers cannot protect Ex= pandoObject insertion internals. This vulnerability is fixed in 2.5.301 and=
    3.1.7. 2026-06-22 not yet calculated CVE-2026-48511 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-48511 ] MessagePack-CSharp--MessagePack-CSharp Mess= agePack for C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1= .7, MessagePack-CSharp's JSON conversion helpers contain multiple recursion=
    paths that do not consistently enforce a depth limit. These paths are in t=
    he JSON conversion component rather than normal typed MessagePack deseriali= zation. MessagePackSerializer.ConvertFromJson recursively processes nested = JSON arrays and objects in FromJsonCore() without consulting MessagePackSec= urity.MaximumObjectGraphDepth. TinyJsonReader.ReadNextToken() recursively c= onsumes comma and colon separator characters, allowing even malformed JSON = with long separator runs to consume one stack frame per character. MessageP= ackSerializer.ConvertToJson applies depth checks to arrays and maps, but th=
    e typeless extension branch for ext-100 recursively calls ToJsonCore() with= out applying MessagePackSecurity.DepthStep(ref reader). Each path can allow=
    attacker-controlled input to exhaust the process stack and trigger an unca= tchable StackOverflowException instead of failing with a catchable parse or=
    serialization exception. This vulnerability is fixed in 2.5.301 and 3.1.7.=
    2026-06-22 not yet calculated CVE-2026-48512 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-48512 ] MessagePack-CSharp--MessagePack-CSharp MessagePack=
    for C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1.7, run= time-generated union deserializers emitted by DynamicUnionResolver do not c= all MessagePackSecurity.DepthStep(ref reader) and do not decrement reader.D= epth around recursive deserialization and skip paths. This means union dese= rialization does not consistently participate in the maximum object graph d= epth enforcement that protects other recursive formatter paths. For unknown=
    union keys, the emitted deserializer calls reader.Skip() on attacker-contr= olled data without an enclosing depth step. This vulnerability is fixed in = 2.5.301 and 3.1.7. 2026-06-22 not yet calculated CVE-2026-48513 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-48513 ] MessagePack-CSharp--MessagePack-= CSharp MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.= 301 and 3.1.7, UnsafeBlitFormatterBase<T>.Deserialize reads an attacker-con= trolled byteLength from an extension payload and allocates an array based o=
    n that value before validating it against the extension header length or re= maining payload bytes. The outer extension header is bounded by available i= nput, but that bound is not used to constrain the inner byteLength before a= llocation. A very small payload can therefore request a very large T[] allo= cation. This vulnerability is fixed in 2.5.301 and 3.1.7. 2026-06-22 not ye=
    t calculated CVE-2026-48514 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 8514 ] MessagePack-CSharp--MessagePack-CSharp MessagePack for C# is a Messa= gePack serializer for C#. Prior to 2.5.301 and 3.1.7, MessagePack-CSharp's = multi-dimensional array formatters read dimension lengths directly from the=
    payload and allocate T[,], T[,,], or T[,,,] before validating that the dim= ension product matches the encoded element count. The formatter reads a gua= rded element array header, but allocation of the target multi-dimensional a= rray happens before the dimensions are checked against that element count. =
    A small payload can therefore declare large dimensions, provide an empty or=
    tiny inner array, and cause a large heap allocation before element data is=
    validated. This vulnerability is fixed in 2.5.301 and 3.1.7. 2026-06-22 no=
    t yet calculated CVE-2026-48515 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-48515 ] MessagePack-CSharp--MessagePack-CSharp MessagePack for C# is a M= essagePack serializer for C#. Prior to 2.5.301 and 3.1.7, InterfaceLookupFo= rmatter<TKey,TElement> constructs an internal Dictionary<TKey, IGrouping<TK= ey,TElement>> with the default equality comparer instead of the security-aw= are comparer supplied by options.Security.GetEqualityComparer<TKey>(). This=
    formatter omission allows hash-collision CPU denial of service against ILo= okup<TKey,TElement> even when the application has opted into the untrusted-= data security posture This vulnerability is fixed in 2.5.301 and 3.1.7. 202= 6-06-22 not yet calculated CVE-2026-48516 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-48516 ] MessagePack-CSharp--MessagePack-CSharp MessagePack for=
    C# is a MessagePack serializer for C#. Prior to 2.5.301 and 3.1.7, Message= Pack-CSharp's typeless deserialization includes MessagePackSerializerOption= s.ThrowIfDeserializingTypeIsDisallowed(Type) as a safety check for dangerou=
    s types. The default implementation checks the outer type name, but it does=
    not recursively inspect array element types or generic type arguments. As =
    a result, a type that would be blocked directly can be wrapped inside an ar= ray or constructed generic type and pass the outer type check. The formatte=
    r machinery can then materialize formatters for the inner blocked type. Thi=
    s vulnerability is fixed in 2.5.301 and 3.1.7. 2026-06-22 not yet calculate=
    d CVE-2026-48517 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48517 ] Mint= plex-Labs--anything-llm AnythingLLM is an application that turns pieces of = content into context that any LLM can use as references during chatting. Fr=
    om 1.11.1 until 1.14.1, userId/workspaceId scoping to the parsed-files read= /delete paths was added. However, the POST /api/workspace/:slug/embed-parse= d-file/:fileId flow still deletes the target file by primary key only, with=
    no ownership check, inside two finally{} blocks that run even when the own= ership-checked read fails. As a result a manager or admin (multi-user mode)=
    can delete any other user's parsed file in any workspace - including works= paces they are not a member of - by enumerating integer fileIds. The server=
    even returns "File not found" while still deleting the file. This vulnerab= ility is fixed in 1.14.1. 2026-06-24 not yet calculated CVE-2026-55611 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-55611 ] misp--misp Multiple MISP = core controllers and model capture paths accepted client-controlled request=
    fields such as primary keys (id) and ownership/scope foreign keys (event_i=
    d, org_id, user_id, sharing_group_id, galaxy_cluster_uuid, organisation_uui=
    d, and related nested object identifiers) without consistently stripping, p= inning, or revalidating them against the server-authorized object. In affec= ted paths, an authenticated user with access to one authorized object could=
    submit crafted REST or form payloads that caused MISP to save data against=
    a different object than the one checked by the authorization logic. Depend= ing on the endpoint, this could allow object overwrite, object re-parenting=
    , ownership transfer, unauthorized sharing-group scoping, event/object inje= ction, proposal retargeting, or stored attacker-controlled content appearin=
    g in another user's context. The fixes harden affected create/edit/import f= lows by stripping client-supplied primary keys on create-only saves, re-pin= ning route- or database-authorized identifiers before save operations, vali= dating effective sharing-group scope, and adding field whitelists where own= ership fields must never be editable. The initial broad fix also added a ce= ntral CRUDComponent::edit()=C2=A0primary-key re-pin so payload-supplied IDs=
    cannot redirect saves away from the already-authorized row. GitHub's patch=
    for 7acf8220c=C2=A0describes this central issue as CRUDComponent::edit()= =C2=A0copying supplied fields, including a payload primary key, onto the lo= aded record, allowing CakePHP save()=C2=A0to update an arbitrary row unless=
    the loaded ID is re-pinned. 2026-06-22 not yet calculated CVE-2026-56422 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-56422 ] misp--misp MISP Core c= ontained broken access-control checks in the bulk deletion flows for Event = Reports=C2=A0and Sharing Groups. The affected deleteSelection=C2=A0handlers=
    authorized deletion using broad role-level permissions instead of validati=
    ng authorization for each selected object. For Event Reports, EventReportsC= ontroller::deleteSelection=C2=A0relied on the global perm_add=C2=A0capabili=
    ty rather than a per-report ownership/authorization check. As a result, a c= ontributor-level user could submit report IDs or UUIDs for reports belongin=
    g to other organisations and hard-delete them instance-wide. The fix change=
    d the callback to call EventReport::fetchIfAuthorized($user, $itemId, 'dele= te')=C2=A0for each selected report before deletion. For Sharing Groups, Sha= ringGroupsController::deleteSelection=C2=A0relied on the global perm_sharin= g_group=C2=A0capability rather than verifying ownership of each selected sh= aring group. This allowed a sharing-group-capable user to hard-delete shari=
    ng groups owned by other organisations, bypassing the per-object ownership = gate used by the single-object delete action. The fix changed the callback =
    to call SharingGroup::checkIfOwner($user, $itemId)=C2=A0for each selected s= haring group. An authenticated attacker with the relevant broad role permis= sion could abuse the affected bulk deletion endpoints to delete objects out= side their organisation's authorization scope, causing loss of event-report=
    content or sharing-group configuration across the instance. 2026-06-22 not=
    yet calculated CVE-2026-56423 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-56423 ] misp--misp MISP core contained multiple broken access-control fla=
    ws where authorization checks were performed against the wrong entity, or w= here ownership/editability checks were missing on write paths. In affected = subsystems, a lower-privileged authenticated user with the relevant feature=
    permission could cause the application to authorize one object but mutate = another, or could modify objects that were merely visible rather than edita= ble by the user's organization. The affected paths included: * Event Report=
    s tag removal: the route-authorized report could differ from the report ID = used for tag detachment, enabling cross-organization tag removal from anoth=
    er event report * Collection Elements bulk deletion: bulk deletion authoriz=
    ed against a collection whose ID matched the collection-element row ID, rat= her than the element's actual parent collection, enabling deletion of eleme= nts from collections the user did not own. * Analyst Data capture/update: n= ested analyst data updates could overwrite an existing record without apply= ing the normal canEditAnalystData=C2=A0ownership check, enabling cross-orga= nization overwrite of analyst data records. * Template Elements editing: ed= iting authorized against a template whose ID matched the template-element I=
    D, rather than the element's actual parent template, enabling unauthorized = edits to another organization's template elements. * Decaying Model editing=
    and mappings: write paths loaded models using view-scope access but did no=
    t verify edit ownership, enabling users to edit or remap visible models own=
    ed by another organization.=C2=A0 Successful exploitation could allow an au= thenticated user with subsystem-specific permissions to perform unauthorize=
    d cross-organization modifications or deletions of MISP data, resulting in = integrity loss, unauthorized tampering with shared intelligence, and disrup= tion of analyst workflows. 2026-06-22 not yet calculated CVE-2026-56424 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-56424 ] misp--misp The Azure Act= ive Directory (AAD) authentication implementation contained multiple weakne= sses in its OAuth 2.0 authorization flow that could allow attackers to bypa=
    ss important security guarantees provided by the protocol. The application = used the PHP session identifier (session_id()) as the OAuth state parameter=
    . Because session identifiers are long-lived authentication credentials, ex= posing them in OAuth redirect URLs could leak valid session tokens through = browser history, HTTP Referer headers, reverse proxies, access logs, or thi= rd-party infrastructure involved in the authentication flow. If obtained by=
    an attacker, the leaked session identifier could potentially be used for s= ession hijacking. Additionally, the implementation did not regenerate the s= ession identifier after successful authentication, leaving authenticated se= ssions susceptible to session fixation attacks where an attacker forces a v= ictim to use a known session identifier before login and later reuses that = identifier after authentication. The OAuth state value was also not impleme= nted as a dedicated, single-use nonce. This weakened CSRF protections and i= ncreased the risk of replay attacks against the OAuth callback process. The=
    authentication flow further failed to enforce HTTPS for the configured OAu=
    th redirect URI. If a non-HTTPS redirect URI was used, OAuth authorization = codes and access tokens could traverse the network in plaintext, exposing s= ensitive credentials to network attackers. Finally, OAuth error responses c= ontaining attacker-controlled GET parameters were logged verbatim. An attac= ker could inject control characters or crafted log content, leading to log = forging, log injection, or corruption of audit records. The fix introduces:=
    * A dedicated cryptographically random OAuth state value. * Single-use sta=
    te validation and invalidation. * Constant-time state comparison using hash= _equals(). * Session identifier rotation after successful authentication. *=
    Enforcement of HTTPS-only redirect URIs. * Sanitized and length-limited lo= gging of OAuth error parameters. AAD Authentication Plugin (OAuth 2.0 / Azu=
    re Active Directory integration) 2026-06-22 not yet calculated CVE-2026-564=
    25 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56425 ] misp--misp MISP al= lowed a site administrator to configure an arbitrary filesystem path for th=
    e NDJSON error log used by JsonLogTool. Because log entries can include att= acker-controlled content, an authenticated attacker with site administrator=
    privileges could direct log output to a PHP file in a web-accessible direc= tory and inject PHP code through logged data. Accessing the resulting file = could lead to remote code execution with the privileges of the web server p= rocess. The fix restricts log destinations to existing directories beneath = APP/tmp/logs or /var/log, requires absolute paths, rejects stream wrappers = and traversal-related input, and limits filenames to .log or .ndjson extens= ions while disallowing executable extension segments. 2026-06-22 not yet ca= lculated CVE-2026-56446 [ https://www.cve.org/CVERecord?id=3DCVE-2026-56446=
    ] misp--misp MISP allowed an authenticated site administrator to set the K= afka_rdkafka_config setting to an arbitrary filesystem path. MISP subsequen= tly parsed the referenced INI file and passed its options to rdkafka. A cra= fted attacker-controlled configuration file could use rdkafka options such =
    as plugin.library.paths to load an external library, resulting in arbitrary=
    code execution with the privileges of the MISP process. An attacker could = leverage a MISP-writable location, such as an uploaded file or administrati=
    ve image, to host the malicious configuration file. The issue is fixed by r= estricting the setting to absolute .ini files located only in approved conf= iguration directories outside the webroot and MISP upload targets. 2026-06-=
    22 not yet calculated CVE-2026-56447 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-56447 ] MosaicML--Composer MosaicML Composer Deserialization of Unt= rusted Data Remote Code Execution Vulnerability. This vulnerability allows = remote attackers to execute arbitrary code on affected installations of Mos= aicML Composer. User interaction is required to exploit this vulnerability =
    in that the target must visit a malicious page or open a malicious file. Th=
    e specific flaw exists within the parsing of checkpoints. The issue results=
    from the lack of proper validation of user-supplied data, which can result=
    in deserialization of untrusted data. An attacker can leverage this vulner= ability to execute code in the context of the current process. Was ZDI-CAN-= 27990. 2026-06-24 not yet calculated CVE-2026-10043 [ https://www.cve.org/C= VERecord?id=3DCVE-2026-10043 ] motioneye-project--motioneye motionEye (mEye=
    ) is an online interface for a piece of software called "motion," which is =
    a video surveillance program with motion detection. Versions prior to 0.44.=
    0 contain an absolute path traversal vulnerability in multiple media file h= andlers that allows an attacker to read arbitrary files from the filesystem=
    . The affected handlers accept a user-controlled filename parameter and con= struct filesystem paths using `os.path.join()`. When an absolute path is su= pplied, Python discards the configured media directory and returns the atta= cker-supplied path directly. The application then bypasses Tornado's built-=
    in path validation by overriding the relevant safety checks. As a result, a=
    n attacker can access files outside of the configured camera media director=
    y, subject to the permissions of the motionEye process. Version 0.44.0 fixe=
    s the issue. 2026-06-24 not yet calculated CVE-2026-55488 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-55488 ] MSI--NBFoundation Service Insecure Per= missions vulnerability in MSI NBFoundation Service v.2.0.2506.1201 allows a=
    remote attacker to obtain sensitive information via the MSIAPService.exe c= omponent 2026-06-25 not yet calculated CVE-2026-37452 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-37452 ] MSI--NBFoundation Service Insecure Permiss= ions vulnerability in MSI NBFoundation Service v.2.0.2506.1201 allows a rem= ote attacker to obtain sensitive information via the MSI_SERVICE_2 pipe 202= 6-06-25 not yet calculated CVE-2026-37453 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-37453 ] MSI--NBFoundation Service Insecure Permissions vulnera= bility in MSI NBFoundation Service v.2.0.2506.1201 allows a remote attacker=
    to obtain sensitive information via the 3DES-ECB encryption 2026-06-25 not=
    yet calculated CVE-2026-37454 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-37454 ] n8n-io--n8n n8n is an open source workflow automation platform. P= rior to 1.123.43, 2.22.1, and 2.20.7, an authenticated user with permission=
    to create or modify workflows could achieve global prototype pollution via=
    an unvalidated pagination parameter in the HTTP Request node. Combined wit=
    h other techniques this could lead to RCE on the instance. This vulnerabili=
    ty is fixed in 1.123.43, 2.22.1, and 2.20.7. 2026-06-23 not yet calculated = CVE-2026-44789 [ https://www.cve.org/CVERecord?id=3DCVE-2026-44789 ] n8n-io= --n8n n8n is an open source workflow automation platform. Prior to 1.123.43=
    , 2.22.1, and 2.20.7, an authenticated user with permission to create or mo= dify workflows could inject CLI flags on the Git node's Push operation allo= wing an attacker to read arbitrary files from the n8n server potentially le= ading to full compromise. This vulnerability is fixed in 1.123.43, 2.22.1, = and 2.20.7. 2026-06-23 not yet calculated CVE-2026-44790 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-44790 ] n8n-io--n8n n8n is an open source workf= low automation platform. Prior to 1.123.43, 2.22.1, and 2.20.7, an authenti= cated user with permission to create or modify workflows could bypass the p= atch for CVE-2026-42232 in the XML node. When combined with other nodes, th=
    is could lead to RCE on the n8n host. This vulnerability is fixed in 1.123.= 43, 2.22.1, and 2.20.7. 2026-06-23 not yet calculated CVE-2026-44791 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-44791 ] n8n-io--n8n n8n is an open = source workflow automation platform. Prior to 1.123.43, 2.22.1, and 2.20.7,=
    an attacker with write access to the git repository connected to an n8n So= urce Control configuration could commit a malicious Data Table JSON file co= ntaining a crafted column name. When an administrator performed a Source Co= ntrol Pull, n8n imported the file and could lead to SQL injection on the in= ternal PostgreSQL instance. Exploitation requires the n8n instance uses Pos= tgreSQL as its database backend, the Source Control feature is enabled and = connected to a repository the attacker can write to, and an administrator t= riggers a Source Control Pull. This vulnerability is fixed in 1.123.43, 2.2= 2.1, and 2.20.7. 2026-06-23 not yet calculated CVE-2026-44792 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-44792 ] n8n-io--n8n n8n is an open source = workflow automation platform. Prior to 1.123.43, 2.22.1, and 2.20.7, the OA= uth1 and OAuth2 credential reconnect endpoints authorized access using cred= ential:read rather than credential:update. An authenticated user with read-= only access to a shared credential could initiate an OAuth reconnect flow a=
    nd overwrite the stored token material for that credential with tokens boun=
    d to an external account they control. Workflows relying on the affected cr= edential would subsequently execute under the attacker's OAuth identity, en= abling data exfiltration to attacker-controlled external services and persi= stent takeover of shared integrations. This vulnerability is fixed in 1.123= .43, 2.22.1, and 2.20.7. 2026-06-23 not yet calculated CVE-2026-45732 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-45732 ] n8n-io--n8n n8n is an open=
    source workflow automation platform. Prior to 1.123.48, 2.21.8, and 2.22.4=
    , an authenticated user with permission to create or modify workflows conta= ining a Python Code Node could escape the sandbox and achieve arbitrary cod=
    e execution on the task runner container. This vulnerability is fixed in 1.= 123.48, 2.21.8, and 2.22.4. 2026-06-23 not yet calculated CVE-2026-49444 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-49444 ] n8n-io--n8n n8n is an o= pen source workflow automation platform. Prior to 1.123.48, 2.21.8, and 2.2= 2.4, an authenticated user with permission to create or modify workflows co= uld supply a local filesystem path as the source repository in the Git node=
    's Clone operation, or as the target repository in the Push operation, bypa= ssing the N8N_RESTRICT_FILE_ACCESS_TO file sandbox. This allowed the conten=
    ts of any local git repository accessible to the n8n process to be cloned i= nto an allowed path and read, circumventing the access restrictions that co= rrectly blocked direct file reads to the same paths. This vulnerability is = fixed in 1.123.48, 2.21.8, and 2.22.4. 2026-06-23 not yet calculated CVE-20= 26-49465 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49465 ] n8n-io--n8n = n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25= .7, and 2.26.2, an authenticated user with workflow edit access could confi= gure a Respond to Webhook node to serve binary content with an attacker-con= trolled Content-Type. The binary response path bypassed the central Content= -Security-Policy sandbox header, allowing a public webhook to execute JavaS= cript in the n8n origin when visited by an authenticated user, with access =
    to that user's session. This vulnerability is fixed in 1.123.55, 2.25.7, an=
    d 2.26.2. 2026-06-23 not yet calculated CVE-2026-54301 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-54301 ] n8n-io--n8n n8n is an open source workflo=
    w automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, an authentica= ted user with workflow edit access could inject arbitrary JavaScript into t=
    he Chat Trigger's generated page by setting a malicious webhookId. When a l= ogged-in user visited the chat URL, the injected code executed in the n8n o= rigin with that user's session privileges. This vulnerability is fixed in 1= .123.55, 2.25.7, and 2.26.2. 2026-06-23 not yet calculated CVE-2026-54302 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-54302 ] n8n-io--n8n n8n is an = open source workflow automation platform. Prior to 2.24.0, an endpoint in t=
    he Meta and Microsoft Teams trigger nodes reflects a query parameter into t=
    he HTTP response without sanitization or Content-Security-Policy headers, e= nabling reflected XSS in the n8n origin when a logged-in user visits a craf= ted URL. This vulnerability is fixed in 2.24.0. 2026-06-23 not yet calculat=
    ed CVE-2026-54303 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54303 ] n8n= -io--n8n n8n is an open source workflow automation platform. Prior to 1.123= .55, 2.25.7, and 2.26.1, an authenticated user with permission to create or=
    modify workflows and access to a SecurityScorecard credential with limited=
    allowed domains could configure the SecurityScorecard node's report downlo=
    ad operation to target an attacker-controlled URL. The node attached the Se= curityScorecard API token to the outbound request, causing the credential t=
    o be sent to the attacker-controlled host bypassing credential configured l= imitations and exfiltrating. This vulnerability is fixed in 1.123.55, 2.25.=
    7, and 2.26.1. 2026-06-23 not yet calculated CVE-2026-54304 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-54304 ] n8n-io--n8n n8n is an open source wo= rkflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, three EE=
    endpoints used by the Dynamic Credentials feature accepted any authenticat=
    ed n8n session without performing per-resource ownership or scope checks on=
    the target workflow or credential. An authenticated user with no project m= embership or credential sharing relationship could enumerate credential ide= ntifiers, names, and types referenced by any private workflow in the instan= ce, initiate an OAuth authorization flow against another user's credential =
    to overwrite its stored tokens with tokens bound to an account they control=
    , or revoke another user's stored credential tokens entirely. Workflows rel= ying on a hijacked credential would subsequently execute under the attacker=
    's OAuth identity, enabling data exfiltration to attacker-controlled extern=
    al services and persistent takeover of integrations. Token revocation would=
    break affected workflows. This vulnerability is fixed in 1.123.55, 2.25.7,=
    and 2.26.2. 2026-06-23 not yet calculated CVE-2026-54305 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-54305 ] n8n-io--n8n n8n is an open source work= flow automation platform. Prior to 2.25.7 and 2.26.2, a prototype pollution=
    vulnerability allowed a crafted public webhook payload to inject attacker-= controlled fields into workflow data during internal object copying. These = fields could be surfaced and consumed as normal values by downstream built-=
    in nodes. Where a workflow combines a public webhook with action nodes that=
    consume the resulting fields, an attacker could cause the workflow to act =
    as a confused deputy - targeting unintended records or issuing outbound req= uests using the workflow owner's configured credentials. This vulnerability=
    is fixed in 2.25.7 and 2.26.2. 2026-06-23 not yet calculated CVE-2026-5430=
    6 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54306 ] n8n-io--n8n n8n is =
    an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and=
    2.26.2, a member-level user with editor access to a shared workflow could = reference credentials they do not own via specific public API endpoints. Cr= edential ownership checks were only enforced partially leading to cross-use=
    r credential access. This issue affects instances where workflow sharing is=
    enabled and at least one workflow has been shared with a member-level user=
    as an Editor. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.=
    2026-06-23 not yet calculated CVE-2026-54307 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-54307 ] n8n-io--n8n n8n is an open source workflow automat= ion platform. Prior to 2.25.7 and 2.26.2, the MicrosoftAgent365Trigger and = StripeTrigger node did not validate that inbound requests. As a result, an = unauthenticated attacker who knows the webhook URL could submit a forged pa= yload and cause the workflow to execute with attacker-controlled data. This=
    vulnerability is fixed in 2.25.7 and 2.26.2. 2026-06-23 not yet calculated=
    CVE-2026-54308 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54308 ] n8n-i= o--n8n n8n is an open source workflow automation platform. Prior to 2.25.7 = and 2.26.2, when @n8n/mcp-browser is run in HTTP transport mode, the MCP en= dpoint accepts session initialization and tool invocation requests without = any authentication. Any network-reachable client, or any website visited by=
    the user, can establish an MCP session and invoke browser-control tools. W= here the n8n AI Browser Bridge extension is installed and a browser connect= ion is active, an unauthenticated caller can access browser-control capabil= ities including navigation, JavaScript evaluation, and cookie and storage a= ccess against the user's real browser profile. This issue only affects inst= ances where @n8n/mcp-browser is run with the HTTP transport (--transport ht= tp). This vulnerability is fixed in 2.25.7 and 2.26.2. 2026-06-23 not yet c= alculated CVE-2026-54309 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5430=
    9 ] n8n-io--n8n n8n is an open source workflow automation platform. Prior t=
    o 2.25.7 and 2.26.2, an authenticated user with permission to create or mod= ify workflows could supply a crafted parameters to the TimescaleDB and/or l= egacy Postgres v1 node's allowing arbitrary SQL to be injected and executed=
    against the connected database within the privileges of the configured dat= abase account. This vulnerability is fixed in 2.25.7 and 2.26.2. 2026-06-23=
    not yet calculated CVE-2026-54310 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-54310 ] n8n-io--n8n n8n is an open source workflow automation platfor=
    m. Prior to 2.25.7 and 2.26.2, an authenticated user with permission to cre= ate or modify workflows could pollute the sandbox used by the Merge node's = SQL Query mode. Because the sandbox context was cached and reused across al=
    l workflow executions on the instance, prototype mutations introduced by on=
    e user's workflow persist into subsequent Merge SQL executions belonging to=
    other users or projects. This allowed a low-privileged attacker to interce=
    pt workflow data processed by other users on the same instance. This issue = only affects multi-user n8n instances where more than one user has permissi=
    on to create and execute workflows containing the Merge node in SQL Query m= ode. This vulnerability is fixed in 2.25.7 and 2.26.2. 2026-06-23 not yet c= alculated CVE-2026-54311 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5431=
    1 ] n8n-io--n8n n8n is an open source workflow automation platform. Prior t=
    o 2.24.0, an authenticated user with permission to create or modify workflo=
    ws could achieve global prototype pollution via the Microsoft SQL node by s= upplying a crafted value as the table parameter. This pollutes Object.proto= type process-wide for the lifetime of the n8n server process, causing appli= cation-wide validation failures and rendering the n8n instance completely n= on-functional until restarted. This vulnerability is fixed in 2.24.0. 2026-= 06-23 not yet calculated CVE-2026-54312 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-54312 ] n8n-io--n8n n8n is an open source workflow automation p= latform. Prior to 2.24.0, an authenticated user with workflow edit access c= ould supply a malicious filter value in the MongoDB node's Find And Replace=
    operation. The value was not validated before being passed to MongoDB as a=
    query filter, allowing unintended documents to be matched and overwritten = with attacker-controlled content. This vulnerability is fixed in 2.24.0. 20= 26-06-23 not yet calculated CVE-2026-54313 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-54313 ] n8n-io--n8n n8n is an open source workflow automation=
    platform. Prior to 2.24.0, the Compression node's Decompress operation exp= anded attacker-controlled archives into memory without enforcing limits on = decompressed output size. An unauthenticated attacker could send a small co= mpressed archive to a public webhook workflow using this node, causing the = n8n process to terminate due to memory exhaustion and disrupting all workfl= ows in the same instance. This vulnerability is fixed in 2.24.0. 2026-06-23=
    not yet calculated CVE-2026-54314 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-54314 ] NEC Corporation--ExpressUpdate Agent for Windows An access co= ntrol deficiency vulnerability exists in ExpressUpdate Agent for Windows. I=
    f a malicious user gains access to the product, arbitrary code could be exe= cuted with SYSTEM privileges. 2026-06-26 not yet calculated CVE-2026-8797 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-8797 ] nestjs--nest Nest is a = framework for building scalable Node.js server-side applications. Prior to = 11.1.24, an authentication bypass vulnerability exists in @nestjs/platform-= fastify. When middleware is registered through NestJS's MiddlewareConsumer.= forRoutes() API on the Fastify adapter, an unauthenticated client can bypas=
    s the Nest middleware registered for that route by simply appending a trail= ing slash (/) to the request URL. This bypass works on the default Fastify = adapter configuration. This vulnerability is fixed in 11.1.24. 2026-06-22 n=
    ot yet calculated CVE-2026-54281 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-54281 ] NLnet Labs--NSD If NSD is configured as secondary for a zone, t=
    he primary of that zone can crash NSD with an AXFR containing a DNS message=
    with a special crafted SVCB RR with an rdata size of 65512, that let's an = (uint16_t) variable that is used to allocate space needed for the RR wrap (= because total size > 65535), causing a heap overflow. The attacker can perf= orm a controlled (RCE class) head write of up to 65509 bytes 2026-06-25 not=
    yet calculated CVE-2026-12244 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-12244 ] NLnet Labs--NSD NSD from version 4.13.0 has a heap use-after-free=
    bug in logging errors on TLS connections, causing a crash of the server pr= ocess, which can be triggered trivially by sending a DNS query over a DoT c= onnection, and closing the connection without reading the response. 2026-06= -25 not yet calculated CVE-2026-12245 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-12245 ] NLnet Labs--NSD NSD version 4.14.0 introduced a bug where =
    a specially crafted APL RR, with an adflength larger than permitted for the=
    address family will overwrite the stack when the zone is written to disk, = with a maximum of 111 attacker controlled bytes. 2026-06-25 not yet calcula= ted CVE-2026-12246 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12246 ] NL= net Labs--NSD When a provide-xfr is given with a tls-auth-name, a secondary=
    requesting a transfer should provide a client certificate with that name. = However, no client certificate is needed when the request comes in over TLS=
    over the regular tls-port (and not the tls-auth-port) or over over TCP ove=
    r the regular port, when the other conditions of the provide-xfr rule match=
    . 2026-06-25 not yet calculated CVE-2026-12490 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-12490 ] nocodb--nocodb NocoDB is software for building da= tabases as spreadsheets. Prior to 2026.04.1, the upload-by-URL path did not=
    enforce NC_ATTACHMENT_FIELD_SIZE against either the remote file's advertis=
    ed Content-Length or the decoded length of a data: URI, allowing an authent= icated user to bypass the configured per-file size limit. This vulnerabilit=
    y is fixed in 2026.04.1. 2026-06-23 not yet calculated CVE-2026-46553 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-46553 ] nocodb--nocodb NocoDB is s= oftware for building databases as spreadsheets. Prior to 2026.04.4, deleted=
    API tokens continued to authenticate requests until their cache entry expi= red, because the auth cache was not invalidated by token value at deletion = time. The API token deletion path removed the database row but did not evic=
    t the token-value keyed entry from the auth cache. The auth middleware ther= efore continued to accept the deleted token until the cache entry aged out,=
    leaving a deletion-to-revocation window of up to three days. This vulnerab= ility is fixed in 2026.04.4. 2026-06-23 not yet calculated CVE-2026-46554 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-46554 ] nocodb--nocodb NocoDB =
    is software for building databases as spreadsheets. Prior to 2026.05.1, the=
    public shared-view relation endpoints accepted a caller-supplied column ID=
    without verifying that the column was visible in the shared view, so anyon=
    e holding a share UUID could read links from any LTAR column on the view's = table - including columns the view owner had hidden. publicMmList, publicHm= List, and relDataList already ensured that the requested column belonged to=
    the view's model, but did not check the view-column entry's show flag. Thi=
    s vulnerability is fixed in 2026.05.1. 2026-06-23 not yet calculated CVE-20= 26-47279 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47279 ] nocodb--noco=
    db NocoDB is software for building databases as spreadsheets. Prior to 2026= .04.1, the password-reset page rendered the URL token directly into a JavaS= cript string literal in a server-rendered EJS template. EJS <%=3D %> HTML-e= ntity-encodes a fixed set of characters but does not escape single quotes o=
    r backslashes, so a crafted token could break out of the JS string context = and execute attacker-controlled script in the NocoDB origin. Triggering req= uired only that a victim follow a malicious password-reset link. This vulne= rability is fixed in 2026.04.1. 2026-06-23 not yet calculated CVE-2026-4737=
    6 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47376 ] nocodb--nocodb Noco=
    DB is software for building databases as spreadsheets. Prior to 2026.04.1, = the client-side hashRedirect plugin called window.location.replace() on a p= ath extracted from the URL hash fragment after only checking hashPath.start= sWith('/'). Protocol-relative URLs (//attacker.com/) also satisfy that chec=
    k, so a crafted link silently redirected visitors to an attacker-controlled=
    origin. This vulnerability is fixed in 2026.04.1. 2026-06-23 not yet calcu= lated CVE-2026-47377 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47377 ] = nocodb--nocodb NocoDB is software for building databases as spreadsheets. P= rior to 2026.04.1, Public shared-view endpoints exposed values from columns=
    that the view owner had hidden, via three independent paths: groupBy retur= ned raw values for any column named in the request, filter and sort arrays = operated on hidden columns enabling boolean-blind extraction, and the relat= ed-data list accepted arbitrary link-column IDs from other tables in the sa=
    me base. This vulnerability is fixed in 2026.04.1. 2026-06-23 not yet calcu= lated CVE-2026-47378 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47378 ] = nocodb--nocodb NocoDB is software for building databases as spreadsheets. P= rior to 2026.05.1, the shared-view password check fell back to strict-equal= ity (=3D=3D=3D) comparison for legacy plaintext passwords, leaking the pass= word's length and per-character prefix through response timing. This vulner= ability is fixed in 2026.05.1. 2026-06-23 not yet calculated CVE-2026-47379=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-47379 ] nocodb--nocodb NocoD=
    B is software for building databases as spreadsheets. Prior to 2026.04.1, s= ign-in response timing differed between known and unknown email addresses b= ecause the unknown-user branch returned without performing a password hash = comparison. This vulnerability is fixed in 2026.04.1. 2026-06-23 not yet ca= lculated CVE-2026-47380 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47380=
    ] nocodb--nocodb NocoDB is software for building databases as spreadsheets=
    . Prior to 2026.05.1, a user in one workspace could exercise another worksp= ace's integration through the testConnection endpoint by supplying its ID, = because the integration was fetched in a bypass scope and the caller's perm= ission check matched any base in any workspace. This vulnerability is fixed=
    in 2026.05.1. 2026-06-23 not yet calculated CVE-2026-47381 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-47381 ] nocodb--nocodb NocoDB is software fo=
    r building databases as spreadsheets. Prior to 2026.05.1, the connection-te=
    st endpoint opened a raw TCP socket to the user-supplied database host with= out resolving and range-checking the destination, so private and link-local=
    addresses (including IPv4-mapped IPv6 forms and localhost) reached the dri= ver. This vulnerability is fixed in 2026.05.1. 2026-06-23 not yet calculate=
    d CVE-2026-47382 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47382 ] noco= db--nocodb NocoDB is software for building databases as spreadsheets. Prior=
    to 2026.05.1, an authenticated commenter could store HTML in row comments = that executed as script when other users hovered over the comment in the ex= panded form view. The comment write paths persisted the raw comment body wi=
    th no server-side sanitisation; the expanded-form sidebar then rendered the=
    stored body and fed its data-tooltip attribute to Tippy with allowHTML: tr= ue. Even when the editor stripped script tags at write time, attribute-leve=
    l payloads re-entered the DOM as live HTML on hover. This vulnerability is = fixed in 2026.05.1. 2026-06-23 not yet calculated CVE-2026-47383 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-47383 ] nocodb--nocodb NocoDB is softwa=
    re for building databases as spreadsheets. Prior to 2026.05.1, an authentic= ated user with column-create permission can inject SQL into the bulk groupB=
    y endpoint by setting a column's title to a SQL fragment. The bulk groupBy = path in group-by.ts builds three database-specific knex.raw() aggregations = that interpolate the request's column_name directly into the SQL string. Co= lumn lookup in data-table.service.ts matches on both the sanitized column_n= ame field and the free-text title, so a title containing a SQL fragment byp= asses the public endpoint's existing column allowlist and reaches the query=
    builder unescaped. This vulnerability is fixed in 2026.05.1. 2026-06-23 no=
    t yet calculated CVE-2026-47384 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-47384 ] nocodb--nocodb NocoDB is software for building databases as spre= adsheets. Prior to 2026.05.1, an authenticated user with base-create permis= sion can attach a SQLite source pointing at an arbitrary file on the NocoDB=
    host, including NocoDB's own internal databases. The SQLite client and the=
    base/integration create services accepted a caller-supplied filename and p= assed it to fs.exists and fs.open('w') without restricting the location. A = user could point a source at noco.db, at a tenant database under nc_minimal= _dbs/, or at any writable path the NocoDB process can reach, and then read =
    or overwrite its contents through the regular table APIs.This vulnerability=
    is fixed in 2026.05.1. 2026-06-23 not yet calculated CVE-2026-47385 [ http= s://www.cve.org/CVERecord?id=3DCVE-2026-47385 ] nocodb--nocodb NocoDB is so= ftware for building databases as spreadsheets. Prior to 2026.05.1, two conc= urrent token-exchange requests using the same OAuth authorization code coul=
    d each mint a distinct valid (access_token, refresh_token) pair, breaking t=
    he single-use guarantee that PKCE relies on. This vulnerability is fixed in=
    2026.05.1. 2026-06-23 not yet calculated CVE-2026-47386 [ https://www.cve.= org/CVERecord?id=3DCVE-2026-47386 ] nocodb--nocodb NocoDB is software for b= uilding databases as spreadsheets. Prior to 2026.05.1, the shared form-view=
    submit handler (packages/nc-gui/composables/useSharedFormViewStore.ts) in = NocoDB writes the form's redirect_url to window.location.href after a same-= host check that does not validate the URL scheme. A user with editor role (=
    or above) on any base can plant a javascript: URL in the form's redirect_ur=
    l; when an authenticated viewer opens the share-link and submits the form, = the payload executes in the NocoDB origin and can read the session token fr=
    om localStorage["nocodb-gui-v2"]. This vulnerability is fixed in 2026.05.1.=
    2026-06-23 not yet calculated CVE-2026-47387 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-47387 ] nocodb--nocodb NocoDB is software for building dat= abases as spreadsheets. Prior to 2026.05.1, a low-privilege MCP token holde=
    r with knowledge of an attachment path could read any file in shared storag=
    e, including attachments belonging to other bases and workspaces, because t=
    he MCP readAttachment tool did not verify the file's ownership. This vulner= ability is fixed in 2026.05.1. 2026-06-23 not yet calculated CVE-2026-47388=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-47388 ] nocodb--nocodb NocoD=
    B is software for building databases as spreadsheets. Prior to 2026.05.1, r= evokeAllOAuthTokensByUser in the users service is an empty stub being calle=
    d from passwordChange, passwordForgot, and passwordReset. OAuth access and = refresh tokens were not revoked when the user changed, reset, or recovered = their password, leaving an attacker-issued OAuth grant valid after the user=
    believed they had locked the attacker out. This vulnerability is fixed in = 2026.05.1. 2026-06-23 not yet calculated CVE-2026-53926 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-53926 ] nocodb--nocodb NocoDB is software for bu= ilding databases as spreadsheets. Prior to 2026.05.1, the spreadsheet-fetch=
    endpoint (axiosRequestMake) accepted URLs whose path contained a permitted=
    extension anywhere in the string, and applied a hand-rolled regex blocklis=
    t that omitted 127.0.0.0/8 and 169.254.0.0/16, allowing the cloud-metadata = endpoint to be reached with a crafted URL This vulnerability is fixed in 20= 26.05.1. 2026-06-23 not yet calculated CVE-2026-53927 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-53927 ] nocodb--nocodb NocoDB is software for buil= ding databases as spreadsheets. Prior to 2026.05.1, a stolen refresh token = survived a password-forgot flow and could be used to mint fresh JWTs even a= fter the user reset their password. passwordChange and passwordReset delete=
    d the user's refresh tokens, but passwordForgot only rotated token_version = and revoked OAuth tokens - it did not call UserRefreshToken.deleteAllUserTo= ken(user.id). An attacker holding a captured refresh cookie could still exc= hange it for a new access token after the victim triggered the recovery flo=
    w. This vulnerability is fixed in 2026.05.1. 2026-06-23 not yet calculated = CVE-2026-53928 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53928 ] nocodb= --nocodb NocoDB is software for building databases as spreadsheets. Prior t=
    o 2026.05.1, with NC_SECURE_ATTACHMENTS=3Dtrue, an authenticated uploader c= ould deliver .html or .svg attachments that the browser rendered inline fro=
    m the NocoDB origin instead of forcing a download. The signed attachment ha= ndler stored response-header overrides under PascalCase keys (ResponseConte= ntDisposition, ResponseContentType) while the controller that served the fi=
    le read them under lowercase-hyphen names (response-content-disposition). T=
    he mismatch dropped the Content-Disposition: attachment header, leaving Exp= ress to auto-render .html, .svg, and similar inline. This vulnerability is = fixed in 2026.05.1. 2026-06-23 not yet calculated CVE-2026-53929 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-53929 ] nocodb--nocodb NocoDB is softwa=
    re for building databases as spreadsheets. Prior to 2026.05.1, the base-mig= ration endpoint accepted a caller-supplied URL that the migration worker de= referenced without enforcing protocol or destination, allowing scheme abuse=
    (file:, ftp:, etc.) and probing of internal HTTP destinations. This vulner= ability is fixed in 2026.05.1. 2026-06-23 not yet calculated CVE-2026-53930=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-53930 ] nocodb--nocodb NocoD=
    B is software for building databases as spreadsheets. Prior to 2026.05.1, t=
    he spreadsheet-import endpoint axiosRequestMake could be used as a generic = HTTP proxy. Before the fix it was reachable unauthenticated, and its URL-ex= tension allowlist was a regex tested against the full URL string, so URLs w= hose query string ended in .csv satisfies the gate even though the underlyi=
    ng request is for another file. This vulnerability is fixed in 2026.05.1. 2= 026-06-23 not yet calculated CVE-2026-53931 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-53931 ] nodejs--node A flaw in Node.js proxy tunnel error ha= ndling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages.=
    When proxy credentials are embedded in the proxy URL, they may be exposed = through error handling paths and captured by logs, diagnostics, or other er= ror consumers. This vulnerability affects all supported release lines: **No= de.js 22**, **Node.js 24**, and **Node.js 26**. 2026-06-26 not yet calculat=
    ed CVE-2026-48615 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48615 ] nod= ejs--node A flaw in Node.js TLS hostname handling can cause Node.js unicode=
    dot separator handling can lead to tls wildcard-depth authentication bypas=
    s due to resolver and verifier hostname normalization mismat. This can lead=
    to confidentiality impact or bypass of the intended security boundary unde=
    r affected configurations. This vulnerability affects all supported release=
    lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**. 2026-06-26 not = yet calculated CVE-2026-48618 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -48618 ] nodejs--node A flaw in Node.js HTTP/2 client allows a server to se=
    nd an unlimited number of ORIGIN frames, which could lead to an Out of Memo=
    ry error on the client. This vulnerability affects all supported release li= nes: **Node.js 22**, **Node.js 24**, and **Node.js 26**. 2026-06-26 not yet=
    calculated CVE-2026-48619 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48= 619 ] nodejs--node A inconsistency in Node.js hostname matching can cause a=
    trust-policy bypass in multi-context mTLS setups. This vulnerability affec=
    ts all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.=
    js 26**. 2026-06-26 not yet calculated CVE-2026-48928 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-48928 ] nodejs--node A flaw in Node.js TLS hostnam=
    e handling can cause Embedded-nul hostnames can lead to silent authority re= binding due to c-string truncation in resolver bindings. This vulnerability=
    affects all supported release lines: **Node.js 22**, **Node.js 24**, and *= *Node.js 26**. 2026-06-26 not yet calculated CVE-2026-48930 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-48930 ] nodejs--node A flaw in Node.js HTTP = Agent can cause a client to accept as valid a response that is send before = the client has sent the request. This vulnerability affects all supported r= elease lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**. 2026-06-2=
    2 not yet calculated CVE-2026-48931 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-48931 ] nodejs--node A flaw in Node.js WebCrypto implementation can = crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB.=
    This vulnerability affects all supported release lines: **Node.js 22**, **= Node.js 24**, and **Node.js 26**. 2026-06-26 not yet calculated CVE-2026-48= 933 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48933 ] nodejs--node A fl=
    aw in Node.js TLS host verification can cause an attacker to bypass certifi= cation validation. This vulnerability affects all supported release lines: = **Node.js 22**, **Node.js 24**, and **Node.js 26**. 2026-06-26 not yet calc= ulated CVE-2026-48934 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48934 ]=
    nodejs--node A flaw in Node.js Permission API can cause a file metadata to=
    be modified even on a path that was set as read-only with e.g. `--allow-fs= -read`. This vulnerability affects all supported release lines: **Node.js 2= 2**, **Node.js 24**, and **Node.js 26**. 2026-06-26 not yet calculated CVE-= 2026-48935 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48935 ] nodejs--no=
    de A flaw in Node.js Permission API can cause a local server to be started = (via a Unix domain socket), even without the `--allow-net` permission. This=
    vulnerability affects one supported release line: **Node.js 26**. 2026-06-=
    26 not yet calculated CVE-2026-48936 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-48936 ] notepad-plus-plus--notepad-plus-plus Notepad++ is a free an=
    d open-source source code editor. From 8.9.4 until 8.9.6, Notepad++ contain=
    s a local privilege escalation vulnerability in the installer. During insta= llation, the installer invokes powershell.exe without using an absolute pat=
    h after setting the working directory to the installation contextMenu direc= tory. If an attacker can pre-place a malicious powershell.exe in a user-wri= table custom installation directory, and a privileged user later runs the i= nstaller and selects that directory, the attacker-controlled executable is = launched with the elevated privileges of the installer. This vulnerability =
    is fixed in 8.9.6. 2026-06-26 not yet calculated CVE-2026-46710 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-46710 ] notepad-plus-plus--notepad-plus-= plus Notepad++ is a free and open-source source code editor. Prior to 8.9.6= .4, NppCommands.cpp checks the HMAC of the on-disk shortcuts.xml at the mom= ent a user command fires (Time-of-Check). However, the command payload is t= aken from the in-memory _userCommands vector, which is populated at applica= tion startup and never re-synchronized with the on-disk file (Time-of-Use).=
    Swapping shortcuts.xml between startup and command execution causes the HM=
    AC check to validate a clean file while a malicious command runs. An attack=
    er with write access to shortcuts.xml places a malicious version on disk be= fore launch, then immediately restores the legitimate file. The HMAC check =
    at execution time validates the restored legitimate file (check passes), wh= ile the malicious payload executes from memory. This vulnerability is fixed=
    in 8.9.6.4. 2026-06-26 not yet calculated CVE-2026-52885 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-52885 ] Ollama AI--Ollama Unauthenticated remo=
    te information disclosure vulnerability in Ollama's model quantization engi=
    ne allows an attacker to read and exfiltrate the server's heap memory, pote= ntially leading to sensitive data exposure, further compromise, and stealth=
    y persistence. 2026-06-26 not yet calculated CVE-2026-5757 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-5757 ] open-webui--open-webui Open WebUI is a=
    self-hosted artificial intelligence platform designed to operate entirely = offline. Prior to 0.9.6, the chat message listener allows non-same-origin i= nput:prompt and action:submit messages, so an external site can set prompt = text and trigger submitPrompt() in an authenticated victim session. I valid= ated this with a cross-origin attacker page that auto-posted messages and c= aused unauthorized POST /api/v1/chats/new and POST /api/chat/completions re= quests containing attacker-controlled prompts. This enables cross-site forc=
    ed actions and model/tool execution under victim privileges without consent=
    . This vulnerability is fixed in 0.9.6. 2026-06-23 not yet calculated CVE-2= 026-54007 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54007 ] openlink vi= rtuoso-opensource--openlink virtuoso-opensource v7.2.11 An issue in the sql= o_place_dt_set component of openlink virtuoso-opensource v7.2.11 allows att= ackers to cause a Denial of Service (DoS) via crafted SQL statements. 2026-= 06-23 not yet calculated CVE-2025-61018 [ https://www.cve.org/CVERecord?id= =3DCVE-2025-61018 ] openlink virtuoso-opensource--openlink virtuoso-opensou= rce v7.2.11 An issue in the sqlo_key_part_best component of openlink virtuo= so-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) v=
    ia crafted SQL statements. 2026-06-23 not yet calculated CVE-2025-61019 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2025-61019 ] openlink virtuoso-openso= urce--openlink virtuoso-opensource v7.2.11 An issue in the sqlo_strip_in_jo=
    in component of openlink virtuoso-opensource v7.2.11 allows attackers to ca= use a Denial of Service (DoS) via crafted SQL statements. 2026-06-23 not ye=
    t calculated CVE-2025-61020 [ https://www.cve.org/CVERecord?id=3DCVE-2025-6= 1020 ] openlink virtuoso-opensource--openlink virtuoso-opensource v7.2.11 A=
    n issue in the sqlo_natural_join_cond component of openlink virtuoso-openso= urce v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafte=
    d SQL statements. 2026-06-23 not yet calculated CVE-2025-61021 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2025-61021 ] openlink virtuoso-opensource--ope= nlink virtuoso-opensource v7.2.11 An issue in the sqlo_tb_col_preds compone=
    nt of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Deni=
    al of Service (DoS) via crafted SQL statements. 2026-06-23 not yet calculat=
    ed CVE-2025-61022 [ https://www.cve.org/CVERecord?id=3DCVE-2025-61022 ] ope= nlink virtuoso-opensource--openlink virtuoso-opensource v7.2.11 An issue in=
    the st_compare component of openlink virtuoso-opensource v7.2.11 allows at= tackers to cause a Denial of Service (DoS) via crafted SQL statements. 2026= -06-23 not yet calculated CVE-2025-61023 [ https://www.cve.org/CVERecord?id= =3DCVE-2025-61023 ] openlink virtuoso-opensource--openlink virtuoso-opensou= rce v7.2.11 An issue in the sqlo_try_in_loop component of openlink virtuoso= -opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via=
    crafted SQL statements. 2026-06-23 not yet calculated CVE-2025-61024 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2025-61024 ] openlink virtuoso-opensour= ce--openlink virtuoso-opensource v7.2.11 An issue in the sslr_qst_get compo= nent of openlink virtuoso-opensource v7.2.11 allows attackers to cause a De= nial of Service (DoS) via crafted SQL statements. 2026-06-23 not yet calcul= ated CVE-2025-61025 [ https://www.cve.org/CVERecord?id=3DCVE-2025-61025 ] o= penlink virtuoso-opensource--openlink virtuoso-opensource v7.2.11 An issue =
    in the t_set_push component of openlink virtuoso-opensource v7.2.11 allows = attackers to cause a Denial of Service (DoS) via crafted SQL statements. 20= 26-06-23 not yet calculated CVE-2025-61027 [ https://www.cve.org/CVERecord?= id=3DCVE-2025-61027 ] openlink virtuoso-opensource--openlink virtuoso-opens= ource v7.2.11 An issue in the time_t_to_dt component of openlink virtuoso-o= pensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via c= rafted SQL statements. 2026-06-23 not yet calculated CVE-2025-61028 [ https= ://www.cve.org/CVERecord?id=3DCVE-2025-61028 ] openlink virtuoso-opensource= --openlink virtuoso-opensource v7.2.11 An issue in the sqlo_untry component=
    of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial=
    of Service (DoS) via crafted SQL statements. 2026-06-23 not yet calculated=
    CVE-2025-61029 [ https://www.cve.org/CVERecord?id=3DCVE-2025-61029 ] OpenS= tack--Swift In OpenStack Swift before 2.37.2, proxy-server does not strip i= nternal update headers (X-Container-Host, X-Container-Device, X-Delete-At-H= ost, X-Delete-At-Device) from client requests before forwarding them to obj= ect-servers. An authenticated user with write access can inject these heade=
    rs to redirect container update requests to an attacker-controlled server, = enabling server-side request forgery. The SSRF requests expose internal clu= ster metadata including storage policy indexes, partition mappings, device = names, and when at rest encryption is enabled, cipher text and initializati=
    on vectors for the container-level encryption key. The attacker can also ca= use "ghost listings" in arbitrary containers via the shard-range redirect m= echanism. 2026-06-23 not yet calculated CVE-2026-50221 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-50221 ] OpenText--Access Manager An unauthorized = user can modify configuration through API calls that affects the OpenText A= ccess Manager.=C2=A0This issue affects Access Manager before 5.1.3. 2026-06= -24 not yet calculated CVE-2026-11877 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-11877 ] OpenText--Access Manager Improper neutralization of input = during web page generation ('cross-site scripting') vulnerability in OpenTe=
    xt Access Manager allows Cross-Site Scripting (XSS). This issue affects Acc= ess Manager: from 5.1 through 5.1.2. 2026-06-24 not yet calculated CVE-2026= -11878 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11878 ] outline--outli=
    ne Outline is a service that allows for collaborative documentation. Prior =
    to 1.8.0, the AuthenticationHelper.canAccess function uses ctx.originalUrl =
    to verify if an API key or OAuth token has the required scopes for a reques=
    t. It extracts the resource by splitting the URL by / and taking the last s= egment. However, it fails to strip the URL fragment (#). Because Koa's rout=
    er uses ctx.path (which strips the fragment) for routing, an attacker can a= ppend a fragment containing a permitted path (e.g., #foo/api/documents.info=
    ) to a restricted endpoint (e.g., /api/documents.create). The router will r= oute the request to the restricted endpoint, but canAccess will evaluate th=
    e permitted path in the fragment, bypassing the API key scope restrictions = and allowing privilege escalation. This vulnerability is fixed in 1.8.0. 20= 26-06-25 not yet calculated CVE-2026-54573 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-54573 ] PaperCut--Print Deploy An insecure process execution = vulnerability exists in the pc-printer-updater.exe component of the PaperCu=
    t Print Deploy Client for Windows. The application, which typically operate=
    s with high-level system privileges, attempts to perform an internal valida= tion check by invoking a secondary system utility using an unqualified file=
    reference. Because the application does not specify an absolute path to th=
    is utility, it relies on the operating system's default search order to loc= ate the executable. Under specific conditions, a local attacker with the ab= ility to modify directories within the system's search path could plant a m= alicious binary that mimics the expected utility. This could result in the = malicious code being executed with SYSTEM privileges, leading to a full com= promise of the affected host. 2026-06-22 not yet calculated CVE-2026-6645 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-6645 ] Payara--Payara Server A=
    critical vulnerability in Admin GUI in Payara Server Full 4.x, 5.x, 6.x, 7= .x, 7.2026.x, 6.2025.x, 6.2024.x on All platforms that allows the attacker =
    to leak the admin gfresttoken to an attacker-controlled host that can resul=
    t in a full unauthenticated takeover of Payara admin domain. A Server-Side = Request Forgery (SSRF) vulnerability in the DownloadServlet of the Admin GU=
    I in Payara Server allows a remote attacker to exfiltrate the administrator=
    's REST session token (gfresttoken) to an attacker-controlled host via a cr= afted request URL. Combined with the absence of CSRF protection on Download= Servlet, an unauthenticated attacker can trick a logged-in administrator in=
    to triggering the token leak, then replay the stolen token to gain full adm= inistrative access to the Payara domain, leading to arbitrary code executio=
    n via WAR deployment. The vulnerability exists in the=C2=A0DownloadServlet= =C2=A0and associated=C2=A0ContentSource=C2=A0implementations (LogViewerCont= entSource,=C2=A0LogFilesContentSource,=C2=A0LBConfigContentSource,=C2=A0Cli= entStubsContentSource) within the=C2=A0admingui:console-common=C2=A0module.=
    2026-06-24 not yet calculated CVE-2026-12986 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-12986 ] PayloadCMS--PayloadCMS An Improper Authorization v= ulnerability exists in PayloadCMS version 3.84.1 due to insufficient access=
    control on the account unlock operation. 2026-06-26 not yet calculated CVE= -2026-11779 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11779 ] Pegasyste= ms--Pega Infinity Pega Platform versions 8.3.0 through Infinity 25.1.2 are = affected by an authorization weakness that may allow authenticated users to=
    access certain additional data via crafted URLs. 2026-06-23 not yet calcul= ated CVE-2025-62180 [ https://www.cve.org/CVERecord?id=3DCVE-2025-62180 ] P= entestify--Pentestify Server-Side Request Forgery (SSRF) (CWE-918) in the P=
    DF generation endpoint GET /api/reports/{id}/pdf (backend/main.py) in ccyl1=
    3 Pentestify 1.0.0 and lower allows remote attackers to make the server iss=
    ue requests to arbitrary internal or external URLs, including cloud metadat=
    a services, and return the rendered content in the resulting PDF via a craf= ted Host header, because the target URL is built from request.base_url with= out validation. 2026-06-24 not yet calculated CVE-2026-13150 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-13150 ] PHPOffice--PhpSpreadsheet PhpSpread= sheet is a pure PHP library for reading and writing spreadsheet files. Prio=
    r to 1.30.5, CVE-2026-34084 was patched by the helper File::prohibitWrapper=
    s. The helper calls parse_url($filename, PHP_URL_SCHEME) and then checks is= _string($scheme) && strlen($scheme) > 1 to reject stream wrappers such as p= har://, php://, data:// or expect://. The check is not equivalent to "does = the path contain a wrapper". When the input has the form phar:///path/file.= phar/inner with three or more slashes after the scheme, parse_url returns b= oolean false instead of returning the scheme string. The is_string($scheme)=
    branch is therefore skipped, the helper returns without throwing, and the = caller proceeds. PHP's stream layer, however, still treats phar:///... as a=
    valid phar wrapper and opens the underlying phar file. The result is that = IOFactory::load($attackerPath) walks past the patch and still touches the p= har wrapper. On PHP 7.x, simply reaching the phar wrapper via is_file is en= ough for PHP to automatically deserialize the phar metadata, which in turn = invokes the magic methods __wakeup and __destruct of an attacker controlled=
    object and gives full RCE. On PHP 8.x, automatic metadata deserialization = for plain file ops was removed, so the chain at the PhpSpreadsheet layer re= duces to a phar wrapper file read primitive, and RCE only resurfaces if the=
    downstream consumer ever calls Phar::getMetadata. This vulnerability is fi= xed in 1.30.5. 2026-06-22 not yet calculated CVE-2026-45034 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-45034 ] Pivotal-- Pivotal CRM An issue in Pi= votal CRM v.6.6.04.08 allows a remote attacker to execute arbitrary code vi=
    a the Pivotal.Core.Common.dll and Pivotal.Engine.Client.Services.Conversion= .dll components. 2026-06-23 not yet calculated CVE-2026-39253 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-39253 ] pnpm--pnpm pnpm is a package manag= er. Prior to 10.33.4 and 11.0.7, a malicious codeload.github.com server can=
    serve whatever tarball it wants and pnpm will install it regardless of the=
    lockfile. The lockfile does not store the hash of the dependencies from ht= tps://codeload.github.com. This means that if this server was compromised o=
    r a person's machine configuration was compromised, pnpm would download and=
    install these dependencies. This vulnerability is fixed in 10.33.4 and 11.= 0.7. 2026-06-25 not yet calculated CVE-2026-48995 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-48995 ] pnpm--pnpm pnpm is a package manager. Prior to=
    10.34.0 and 11.4.0, pnpm can send user-level unscoped npm authentication c= redentials to a registry chosen by a repository-local .npmrc file. In the r= eproduced case, the user's npm config contains a default registry and an un= scoped _authToken. The repository does not provide a token-bearing auth lin=
    e. It only sets registry=3D to a different registry URL. During normal pnpm=
    metadata/install workflows, pnpm binds the user-origin unscoped credential=
    to the repository-selected registry and sends it as an Authorization heade=
    r. This vulnerability is fixed in 10.34.0 and 11.4.0. 2026-06-25 not yet ca= lculated CVE-2026-50017 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50017=
    ] presire--qSnapper Lack of authentication when using the "snapshot diff" = functions in qSnapper before version 1.3.3 allowed a local attacker to see = otherwise read protected information. 2026-06-22 not yet calculated CVE-202= 6-41047 [ https://www.cve.org/CVERecord?id=3DCVE-2026-41047 ] presire--qSna= pper Incorrect caching of authentication between different polkit methods i=
    n qSnapper before version 1.3.3 allowed a local attacker to use functions l= ike "restore from snapshot" even if only allowed to do "delete snapshot". 2= 026-06-22 not yet calculated CVE-2026-41048 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-41048 ] presire--qSnapper Incorrect caching of authenticatio=
    n between different users of the=C2=A0 qSnapper dbus service before version=
    1.3.3 allowed any local attacker to use dbus functions after a privileged = users has authenticated for them. 2026-06-22 not yet calculated CVE-2026-41= 049 [ https://www.cve.org/CVERecord?id=3DCVE-2026-41049 ] pretix--pretix Ma= licious HTML content could be injected into the email address of an order, = which pretix showed without sanitization on the confirmation page for indiv= idual tickets in that order. 2026-06-25 not yet calculated CVE-2026-13225 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-13225 ] pretix--pretix Malicio=
    us HTML content contained in the layout specification of a PDF ticket or ba= dge layout was executed when the PDF editor is opened in the browser. This = could allow one backend user to inject JavaScript into the browser context =
    of another backend user. Due to requirements of the PDF rendering and editi=
    ng libraries used, this is one of the few pages in our backend that do not = have a strong Content-Security-Policy that would render this capability use= less for most scenarios. 2026-06-25 not yet calculated CVE-2026-57532 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-57532 ] pretix--pretix Malicious H= TML content could be injected into the page pretix shows when redirection t=
    o an untrusted page occurs. Since this page has a Content-Security-Policy, = this can mainly be used for phishing purposes. 2026-06-25 not yet calculate=
    d CVE-2026-57533 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57533 ] pret= ix--pretix Content injected to PDF rendering contexts could, in many places=
    , include HTML content including <img> tags. If the src attribute of these = images pointed to an URL, the PDF rendering engine would download the image=
    from that place and display it, thereby leaking information about the rend= ering server and possibly creating an SSRF vector in the local network. 202= 6-06-25 not yet calculated CVE-2026-57535 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-57535 ] pretix--pretix-computop Our payment integration with C= omputop-based payment methods did not properly validate payment status resp= onses. An attacker could use a successful payment status response from one = payment and supply it to the system for a different payment, gaining access=
    to multiple valid tickets with only one payment. 2026-06-25 not yet calcul= ated CVE-2026-13223 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13223 ] p= retix--pretix-digital Malicious HTML content could be injected into the con= tent rendered by the pretix-digital plugin. 2026-06-25 not yet calculated C= VE-2026-13314 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13314 ] pretix-= -pretix-mollie Our payment integration with Mollie did not properly validat=
    e payment status responses. An attacker could use a successful payment stat=
    us response from one payment and supply it to the system for a different pa= yment, gaining access to multiple valid tickets with only one payment. 2026= -06-25 not yet calculated CVE-2026-57536 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-57536 ] pretix--pretix-oppwa Our payment integration with Oppwa= -based payment methods did not properly validate payment status responses. =
    An attacker could use a successful payment status response from one payment=
    and supply it to the system for a different payment, gaining access to mul= tiple valid tickets with only one payment. 2026-06-25 not yet calculated CV= E-2026-13222 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13222 ] pretix--= pretix-pages Malicious HTML content could be injected into the content of a=
    page in the pretix-pages plugin. 2026-06-25 not yet calculated CVE-2026-57= 534 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57534 ] pretix--Venueless=
    Untrusted user data was passed verbatim to Excel exports for administrator=
    s. This allowed formula injection which can be used to compromise the envir= onment of the user loading the file or other data in the file. 2026-06-22 n=
    ot yet calculated CVE-2026-12862 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-12862 ] pretix--Venueless An unvalidated redirect was contained in Venu= eless' social login functionality and could be exploited for phishing using=
    trusted domains. 2026-06-22 not yet calculated CVE-2026-12863 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-12863 ] pretix--Venueless Permissions whe=
    re checked incorrectly during room creation, allowing attackers to create r= ooms of types they shouldn't be allowed to create. 2026-06-25 not yet calcu= lated CVE-2026-13350 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13350 ] = py-pdf--pypdf pypdf is a free and open-source pure-python PDF library. Prio=
    r to 6.12.2, an attacker who uses this vulnerability can craft a PDF which = leads to long runtimes. This requires accessing a stream which uses the /Fl= ateDecode filter with a PNG predictor. This vulnerability is fixed in 6.12.=
    2. 2026-06-22 not yet calculated CVE-2026-49460 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-49460 ] py-pdf--pypdf pypdf is a free and open-source pu= re-python PDF library. Prior to 6.12.2, an attacker who uses this vulnerabi= lity can craft a PDF which leads to large memory usage. This requires extra= cting the text of a page which contains a form XObject with self-references=
    . This vulnerability is fixed in 6.12.2. 2026-06-22 not yet calculated CVE-= 2026-49461 [ https://www.cve.org/CVERecord?id=3DCVE-2026-49461 ] py-pdf--py= pdf pypdf is a free and open-source pure-python PDF library. Prior to 6.13.=
    0, an attacker who uses this vulnerability can craft a PDF which leads to a=
    n infinite loop. This requires extracting the text in layout mode. This vul= nerability is fixed in 6.13.0. 2026-06-22 not yet calculated CVE-2026-54530=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-54530 ] py-pdf--pypdf pypdf =
    is a free and open-source pure-python PDF library. Prior to 6.13.0, an atta= cker who uses this vulnerability can craft a PDF which leads to an infinite=
    loop. This requires merging a file with outlines into a writer. This vulne= rability is fixed in 6.13.0. 2026-06-22 not yet calculated CVE-2026-54531 [=
    https://www.cve.org/CVERecord?id=3DCVE-2026-54531 ] py-pdf--pypdf pypdf is=
    a free and open-source pure-python PDF library. Prior to 6.13.1, an attack=
    er who uses this vulnerability can craft a PDF which leads to an infinite l= oop. This requires merging a file with threads/articles into a writer. This=
    vulnerability is fixed in 6.13.1. 2026-06-22 not yet calculated CVE-2026-5= 4651 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54651 ] Python Software = Foundation--CPython When using the "configparser" module to write configura= tion files containing multi-line text values with carriage return character=
    s (\r) the resulting file could be injected with unexpected keys and values=
    if the attacker controls the written value. 2026-06-23 not yet calculated = CVE-2026-0864 [ https://www.cve.org/CVERecord?id=3DCVE-2026-0864 ] Python S= oftware Foundation--CPython tarfile.extractall() with the 'data' or 'tar' f= ilter could be bypassed by a crafted archive where a hardlink references a = symlink stored at a deeper name than the hardlink itself.=C2=A0 The extract= ion fallback validated the symlink at it's archived location but recreated =
    it at the hardlink's shallower path, letting a relative target the filter j= udged contained escape the destination directory.=C2=A0 This allowed a mali= cious tar archive to create a symlink pointing outside the destination, ena= bling out-of-destination file reads or writes. This was an incomplete fix o=
    f CVE-2025-4330. 2026-06-23 not yet calculated CVE-2026-11940 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-11940 ] Python Software Foundation--CPytho=
    n When using the "tarfile" module with a file opened in "streaming mode" (m= ode=3D"r|") the tarfile module did not properly handle EOF, making archive = parsing take exponentially longer. 2026-06-23 not yet calculated CVE-2026-1= 1972 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11972 ] QOS.CH Sarl--Log= back-core ACE vulnerability in conditional configuration file processing by=
    QOS.CH logback-core up to and including version 1.5.35 in Java application=
    s, allows an attacker to execute arbitrary code circumventing existing prot= ections against CVE-2025-11226 by=C2=A0compromising an existing logback con= figuration file or by injecting an environment variable before program exec= ution. A successful attack requires the presence of Janino library to be pr= esent on the user's class path. In addition, the attacker must=C2=A0 have w= rite access to a configuration file. Alternatively, the attacker could inje=
    ct a malicious environment variable pointing to a malicious configuration f= ile. In both cases, the attack requires existing privilege. 2026-06-24 not = yet calculated CVE-2026-13006 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -13006 ] Quest--NetVault Backup Quest NetVault Backup viewclient Cross-Site=
    Scripting Authentication Bypass Vulnerability. This vulnerability allows r= emote attackers to bypass authentication on affected installations of Quest=
    NetVault Backup. User interaction is required to exploit this vulnerabilit=
    y in that the target must visit a malicious page or open a malicious file. = The specific flaw exists within the viewclient webpage. The issue results f= rom the lack of proper validation of user-supplied data, which can lead to = the injection of an arbitrary script. An attacker can leverage this in conj= unction with other vulnerabilities to execute arbitrary code in the context=
    of SYSTEM. Was ZDI-CAN-28202. 2026-06-24 not yet calculated CVE-2026-7569 =
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-7569 ] Quest--NetVault Backup=
    Quest NetVault Backup NVBUDashboard SQL Injection Remote Code Execution Vu= lnerability. This vulnerability allows remote attackers to execute arbitrar=
    y code on affected installations of Quest NetVault Backup. Although authent= ication is required to exploit this vulnerability, the existing authenticat= ion mechanism can be bypassed. The specific flaw exists within the processi=
    ng of NVBUDashboard JSON-RPC messages. The issue results from the lack of p= roper validation of a user-supplied string before using it to construct SQL=
    queries. An attacker can leverage this vulnerability to execute code in th=
    e context of NETWORK SERVICE. Was ZDI-CAN-27809. 2026-06-24 not yet calcula= ted CVE-2026-7570 [ https://www.cve.org/CVERecord?id=3DCVE-2026-7570 ] Ques= t--NetVault Backup Quest NetVault Backup addclient3 Cross-Site Scripting Au= thentication Bypass Vulnerability. This vulnerability allows remote attacke=
    rs to bypass authentication on affected installations of Quest NetVault Bac= kup. User interaction is required to exploit this vulnerability in that the=
    target must visit a malicious page or open a malicious file. The specific = flaw exists within the addclient3 webpage. The issue results from the lack =
    of proper validation of user-supplied data, which can lead to the injection=
    of an arbitrary script. An attacker can leverage this in conjunction with = other vulnerabilities to execute arbitrary code in the context of SYSTEM. W=
    as ZDI-CAN-27666. 2026-06-24 not yet calculated CVE-2026-9780 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-9780 ] Quest--NetVault Backup Quest NetVau=
    lt Backup NVBURASDevice SQL Injection Remote Code Execution Vulnerability. = This vulnerability allows remote attackers to execute arbitrary code on aff= ected installations of Quest NetVault Backup. Although authentication is re= quired to exploit this vulnerability, the existing authentication mechanism=
    can be bypassed. The specific flaw exists within the processing of NVBURAS= Device JSON-RPC messages. The issue results from the lack of proper validat= ion of a user-supplied string before using it to construct SQL queries. An = attacker can leverage this vulnerability to execute code in the context of = NETWORK SERVICE. Was ZDI-CAN-27648. 2026-06-24 not yet calculated CVE-2026-= 9781 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9781 ] Quest--NetVault B= ackup Quest NetVault Backup NVBUDeviceDrive SQL Injection Remote Code Execu= tion Vulnerability. This vulnerability allows remote attackers to execute a= rbitrary code on affected installations of Quest NetVault Backup. Although = authentication is required to exploit this vulnerability, the existing auth= entication mechanism can be bypassed. The specific flaw exists within the p= rocessing of NVBUDeviceDrive JSON-RPC messages. The issue results from the = lack of proper validation of a user-supplied string before using it to cons= truct SQL queries. An attacker can leverage this vulnerability to execute c= ode in the context of NETWORK SERVICE. Was ZDI-CAN-27633. 2026-06-24 not ye=
    t calculated CVE-2026-9782 [ https://www.cve.org/CVERecord?id=3DCVE-2026-97=
    82 ] Quest--NetVault Backup Quest NetVault Backup NVBURemovableMedia SQL In= jection Remote Code Execution Vulnerability. This vulnerability allows remo=
    te attackers to execute arbitrary code on affected installations of Quest N= etVault Backup. Although authentication is required to exploit this vulnera= bility, the existing authentication mechanism can be bypassed. The specific=
    flaw exists within the processing of NVBURemovableMedia JSON-RPC messages.=
    The issue results from the lack of proper validation of a user-supplied st= ring before using it to construct SQL queries. An attacker can leverage thi=
    s vulnerability to execute code in the context of NETWORK SERVICE. Was ZDI-= CAN-27632. 2026-06-24 not yet calculated CVE-2026-9783 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-9783 ] Quest--NetVault Backup Quest NetVault Back=
    up NVBULibraryPort SQL Injection Remote Code Execution Vulnerability. This = vulnerability allows remote attackers to execute arbitrary code on affected=
    installations of Quest NetVault Backup. Although authentication is require=
    d to exploit this vulnerability, the existing authentication mechanism can =
    be bypassed. The specific flaw exists within the processing of NVBULibraryP= ort JSON-RPC messages. The issue results from the lack of proper validation=
    of a user-supplied string before using it to construct SQL queries. An att= acker can leverage this vulnerability to execute code in the context of NET= WORK SERVICE. Was ZDI-CAN-27631. 2026-06-24 not yet calculated CVE-2026-978=
    4 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9784 ] Quest--NetVault Back=
    up Quest NetVault Backup NVBULibrarySlot SQL Injection Remote Code Executio=
    n Vulnerability. This vulnerability allows remote attackers to execute arbi= trary code on affected installations of Quest NetVault Backup. Although aut= hentication is required to exploit this vulnerability, the existing authent= ication mechanism can be bypassed. The specific flaw exists within the proc= essing of NVBULibrarySlot JSON-RPC messages. The issue results from the lac=
    k of proper validation of a user-supplied string before using it to constru=
    ct SQL queries. An attacker can leverage this vulnerability to execute code=
    in the context of NETWORK SERVICE. Was ZDI-CAN-27630. 2026-06-24 not yet c= alculated CVE-2026-9785 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9785 =
    ] Quest--NetVault Backup Quest NetVault Backup NVBUDashboard SQL Injection = Remote Code Execution Vulnerability. This vulnerability allows remote attac= kers to execute arbitrary code on affected installations of Quest NetVault = Backup. Although authentication is required to exploit this vulnerability, = the existing authentication mechanism can be bypassed. The specific flaw ex= ists within the processing of NVBUDashboard JSON-RPC messages. The issue re= sults from the lack of proper validation of a user-supplied string before u= sing it to construct SQL queries. An attacker can leverage this vulnerabili=
    ty to execute code in the context of NETWORK SERVICE. Was ZDI-CAN-27626. 20= 26-06-24 not yet calculated CVE-2026-9786 [ https://www.cve.org/CVERecord?i= d=3DCVE-2026-9786 ] Quest--NetVault Backup Quest NetVault Backup NVBULogDae= mon Command Injection Remote Code Execution Vulnerability. This vulnerabili=
    ty allows remote attackers to execute arbitrary code on affected installati= ons of Quest NetVault Backup. Although authentication is required to exploi=
    t this vulnerability, the existing authentication mechanism can be bypassed=
    . The specific flaw exists within the processing of NVBULogDaemon JSON-RPC = messages. The issue results from the lack of proper validation of a user-su= pplied string before using it to execute a system call. An attacker can lev= erage this vulnerability to execute code in the context of SYSTEM. Was ZDI-= CAN-27625. 2026-06-24 not yet calculated CVE-2026-9787 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-9787 ] Redox--Relibc An issue in the pthread_rwlo= ckattr_setpshared() function of relibc commit 61f42d allows attackers to ca= use a Denial of Service (DoS) via a crafted input. 2026-06-25 not yet calcu= lated CVE-2026-38637 [ https://www.cve.org/CVERecord?id=3DCVE-2026-38637 ] = Redox--Relibc An issue in the parse_month function (/time/strptime.rs) of r= elibc commit ab6a2e allows attackers to cause a Denial of Service (DoS) via=
    parsing a crafted input. 2026-06-26 not yet calculated CVE-2026-38639 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-38639 ] Redox--Relibc A reachable=
    unwrap in the __assert_fail function (/assert/mod.rs) of relibc commit 61f= 42d allows attackers to cause a Denial of Service (DoS) via a crafted strin=
    g. 2026-06-25 not yet calculated CVE-2026-38640 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-38640 ] Redox--Relibc An issue in the DSO::mmap_and_copy=
    function of relibc commit 61f42d allows attackers to cause a Denial of Ser= vice (DoS) via loading a crafted shared library. 2026-06-26 not yet calcula= ted CVE-2026-38641 [ https://www.cve.org/CVERecord?id=3DCVE-2026-38641 ] Re= olink--Home Hub A vulnerability exists in the netclient and factory service=
    s of Reolink Home Hub (versions prior to v3.3.0.456_26031911) due to the po= ssibility of brute-force cracking the credentials. This issue could allow a= ttackers on the same local network to intercept traffic between the Hub and=
    associated cameras and compromise the credentials of connected cameras. 20= 26-06-26 not yet calculated CVE-2026-57473 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-57473 ] Revive Adserver--Revive Adserver A missing validation=
    of user input when saving delivery limitations in Revive Adserver 6.0.6 an=
    d earlier could allow a low-privileged user to use the logical parameter to=
    inject malicious PHP code into the compiledlimitations field on the databa=
    se and have it executed during banner delivery. Input sanitisation has been=
    improved to ensure that the parameter is properly validated. 2026-06-23 no=
    t yet calculated CVE-2026-34916 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-34916 ] Revive--Adserver A missing access control check when linking ban= ners or campaigns to a zone through the zone-include.php script of Revive A= dserver 6.0.6 and earlier, or via its API allows a low-privileged user coul=
    d link their zones to banners or campaigns owned by other managers on the s= ame instance, resulting in inconsistent ownership relationships. Ownership = validation has been added to ensure that banners and campaigns can only be = linked to zones managed by the same account. 2026-06-23 not yet calculated = CVE-2026-34912 [ https://www.cve.org/CVERecord?id=3DCVE-2026-34912 ] Revive= --Adserver A missing access control check when linking trackers to campaign=
    s through the campaign-trackers.php script of Revive Adserver 6.0.6 and ear= lier could allow a low-privileged user to link their trackers to campaigns = owned by other managers on the same instance, resulting in inconsistent own= ership relationships. Ownership validation has been added to ensure that ca= mpaigns can only be linked to trackers owned by the same advertiser. 2026-0= 6-23 not yet calculated CVE-2026-34913 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-34913 ] Revive--Adserver A missing sanitisation of user input i=
    n the zone-include.php script of Revive Adserver 6.0.6 and earlier. A low-p= rivileged user could exploit the clientid parameter to perform blind SQL in= jection attacks. Input sanitisation has been improved to ensure that all pa= rameters processed by the script are properly validated. 2026-06-23 not yet=
    calculated CVE-2026-34914 [ https://www.cve.org/CVERecord?id=3DCVE-2026-34= 914 ] Revive--Adserver A missing sanitisation of user input in the zone-inc= lude.php script of Revive Adserver 6.0.6 and earlier could allow a low-priv= ileged user to exploit the clientid parameter to perform blind SQL injectio=
    n attacks. Input sanitisation has been improved to ensure that all paramete=
    rs processed by the script are properly validated. 2026-06-23 not yet calcu= lated CVE-2026-34915 [ https://www.cve.org/CVERecord?id=3DCVE-2026-34915 ] = Revive--Adserver Low-privileged session IDs generated for the web admin con= sole could be reused in the XML RPC API, whose authentication is normally r= estricted to admin users. An attacker could leverage this to gain unauthori= sed access and exploit API level vulnerabilities. The session context (web/= API) is now recorded along with other session data, preventing session IDs = from being used interchangeably. 2026-06-23 not yet calculated CVE-2026-349=
    17 [ https://www.cve.org/CVERecord?id=3DCVE-2026-34917 ] Revive--Adserver L= ow-privileged users could use their Full Name as a vector for a stored XSS = attack. The name is included in system generated emails, whose content is s= tored in the details field of the userlog table. An admin user viewing the = email content through userlog-details.php would have any malicious JavaScri=
    pt payload executed due to missing output sanitisation. Proper escaping has=
    been added to the userlog details output. 2026-06-23 not yet calculated CV= E-2026-44956 [ https://www.cve.org/CVERecord?id=3DCVE-2026-44956 ] Revive--= Adserver A missing access control check when invoking various modify method=
    s in the XML RPC API of Revive Adserver 6.0.6 and earlier. The API allowed = entities to be reassigned to different parent entities, leading to inconsis= tent ownership relationships. This issue was exploitable only in combinatio=
    n with CVE-2026-34917 or with third-party API extensions that expose API fu= nctionality to low-privileged users. Access control checks have been added =
    to validate access to parent entities in the API modify methods. 2026-06-23=
    not yet calculated CVE-2026-44957 [ https://www.cve.org/CVERecord?id=3DCVE= -2026-44957 ] Revive--Adserver An access control bypass allows an advertise= r-level user to activate or deactivate a banner in Revive Adserver 6.0.6 an=
    d earlier, even when such permissions were not granted. The banner-edit.php=
    script allowed the banner status to be overwritten solely based on banner = edit permissions. The status field has been removed from the hidden form fi= elds in the banner edit screen. 2026-06-23 not yet calculated CVE-2026-4495=
    8 [ https://www.cve.org/CVERecord?id=3DCVE-2026-44958 ] Revive--Adserver A = missing validation of user input exists when saving delivery limitations in=
    Revive Adserver 6.0.6 and earlier. A low-privileged user could add an unex= pected component parameter and inject malicious PHP code into the compiledl= imitations field, which would then be executed during banner delivery. Inpu=
    t sanitisation has been improved to ensure that unexpected parameters are f= iltered out. 2026-06-23 not yet calculated CVE-2026-44959 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-44959 ] Revive--Adserver A stored XSS can be e= xploited by leveraging the usernames as an attack vector. When an admin use=
    r viewed the audit log details for affected entries, any malicious JavaScri=
    pt payload embedded in the username would be executed due to missing output=
    sanitisation. Proper escaping has been added to the audit log details outp= ut. 2026-06-23 not yet calculated CVE-2026-44960 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-44960 ] Revive--Adserver The XML-RPC API addUser method=
    has a validation bypass introduced in the fix for CVE-2025-55129. As a res= ult, API users could create usernames that enabled impersonation or stored = XSS attacks. Proper validation has been added where it was missing. 2026-06= -23 not yet calculated CVE-2026-44961 [ https://www.cve.org/CVERecord?id=3D= CVE-2026-44961 ] Revive--Adserver A bypass for CVE-2026-34913 exists with p= roper ownership validation that had not been applied to the reverse operati=
    on of linking campaigns and trackers through the `tracker-campaigns.php` sc= ript in Revive Adserver 6.0.7 and earlier. As a result, a low-privileged us=
    er could link their trackers to campaigns owned by other managers on the sa=
    me instance, leading to inconsistent ownership relationships. 2026-06-26 no=
    t yet calculated CVE-2026-50739 [ https://www.cve.org/CVERecord?id=3DCVE-20= 26-50739 ] Revive--Adserver A missing sanitisation vulnerability of user in= put in the zone-include.php script exists in Revive Adserver 6.0.7 and earl= ier. A low-privileged user could exploit the refresh parameter of the iFram=
    e invocation tag to perform reflected XSS attacks. 2026-06-26 not yet calcu= lated CVE-2026-50740 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50740 ] = Revive--Adserver Bypass to the fix for CVE-2026-34916. Variants of such vec= tors have been also reported by phucrio and offsetmd. The fix can be bypass=
    ed either by sending a disallowed but otherwise valid plugin identifier as = `type`, or using the `ox.setChannelTargeting` XML-RPC API method. 2026-06-2=
    6 not yet calculated CVE-2026-50741 [ https://www.cve.org/CVERecord?id=3DCV= E-2026-50741 ] Revive--Adserver A stored XSS vulnerabilities exists in the = `maintenance-acl-check.php` and `maintenance-banners-check.php` tools of Re= vive Adserver 6.0.7. The issue was caused by entity names being displayed w= ithout proper escaping when inconsistencies were detected. Whether the XSS = payload is executed when an administrator uses the affected maintenance too=
    ls is not entirely under the attacker's control. 2026-06-26 not yet calcula= ted CVE-2026-50742 [ https://www.cve.org/CVERecord?id=3DCVE-2026-50742 ] Re= vive--Adserver A bypass to the admin-only restriction of the XML-RPC API in=
    Revive Adserver 6.0.7. The API response for the ox.login method returned a=
    session ID cookie in the HTTP headers, and although the method correctly r= eturned an error, the associated session was not invalidated. As a result, = the leaked session ID could be used to perform subsequent API calls without=
    restrictions. 2026-06-26 not yet calculated CVE-2026-50744 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-50744 ] Revive--Adserver A missing sanitisat= ion vulnerability exists with user input in the stats-video.php script. The=
    way URLs to this script were constructed did not follow best practices, an=
    d the output of the Smarty custom helper function url was neither properly = encoded nor sanitised, allowing user-supplied input to be reflected without=
    escaping. 2026-06-26 not yet calculated CVE-2026-50745 [ https://www.cve.o= rg/CVERecord?id=3DCVE-2026-50745 ] RocketChat--Rocket.Chat Rocket.Chat is a=
    n open-source, secure, fully customizable communications platform. Prior to=
    8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11, Rocket.Chat=
    's SAML integration does not verify the signature on inbound LogoutRequest = messages. An unauthenticated remote attacker who knows a target user's SAML=
    NameID - which major identity providers (Okta, Google Workspace, Microsoft=
    Entra ID, JumpCloud) expose as the user's email address - can craft a vali= d-looking unsigned LogoutRequest and submit it to the SP logout endpoint. T=
    he server processes it as legitimate, immediately destroying the victim's s= ession. Because the attack requires no authentication and no interaction fr=
    om the victim, it can be repeated in a loop against individual users or scr= ipted across many accounts, effectively rendering the Rocket.Chat instance = unusable for SAML-authenticated users. This vulnerability is fixed in 8.5.0=
    , 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11. 2026-06-24 not ye=
    t calculated CVE-2026-45677 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 5677 ] RocketChat--Rocket.Chat Rocket.Chat is an open-source, secure, fully=
    customizable communications platform. Prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4,=
    8.1.5, 8.0.6, 7.13.8, and 7.10.12, Rocket.Chat allows users deactivated th= rough users.deactivateIdle to keep using already-issued login tokens. A use=
    r that an administrator has marked inactive for idleness can still access a= uthenticated REST endpoints with the old token. This vulnerability is fixed=
    in 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12. 2026-06-=
    24 not yet calculated CVE-2026-45757 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-45757 ] RocketChat--Rocket.Chat Rocket.Chat is an open-source, secu= re, fully customizable communications platform. Prior to 8.5.0, 8.4.1, 8.3.=
    3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11, Rocket.Chat's SAML service pro= vider implementation silently skips both SAML Response and Assertion signat= ure validation when the configured IdP certificate field is empty. The veri= fySignatures routine performs an early return when serviceProviderOptions.c= ert is falsy, which is the default state of the setting. Because provider r= egistration only gates on the SAML "enabled" toggle and not on the presence=
    of a certificate, an administrator who enables SAML without pasting an IdP=
    certificate obtains a fully wired, publicly reachable SAML login endpoint = that accepts unsigned or attacker-supplied assertions. This is a default-co= nfiguration authentication-bypass class: the fail-open branch is reached wi=
    th no misconfiguration beyond leaving a field at its shipped default. This = vulnerability is fixed in 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7,=
    and 7.10.11. 2026-06-24 not yet calculated CVE-2026-46423 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-46423 ] RocketChat--Rocket.Chat Rocket.Chat i=
    s an open-source, secure, fully customizable communications platform. Prior=
    to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12, Rocket.C= hat does not revoke OAuth bearer or refresh tokens when a user is deactivat= ed. A deactivated user can continue using an existing OAuth access token, a=
    nd can also mint a fresh access token from an existing refresh token. This = vulnerability is fixed in 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8,=
    and 7.10.12. 2026-06-24 not yet calculated CVE-2026-49277 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-49277 ] RocketChat--Rocket.Chat Rocket.Chat i=
    s an open-source, secure, fully customizable communications platform. Prior=
    to 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13, in apps/meteor/a= pp/apple/server/loginHandler.ts, handleIdentityToken parses a JWT issued by=
    Apple during the OAuth flow. The try block checks for an email parameter. =
    If the JWT does not contain an email address, the application falls back to=
    accepting an arbitrary email value supplied directly in the request. Attac= kers are able to forge Apple JWTs that do not contain an email address and = leverage this vulnerability to carry out account takeover attacks. This vul= nerability is fixed in 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.1=
    3. 2026-06-24 not yet calculated CVE-2026-55666 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-55666 ] rtk-ai--rtk rtk filters and compresses command o= utputs before they reach your LLM context. Prior to 0.32.0, RTK (Rust Token=
    Killer) improperly trusts project-local configuration files. RTK automatic= ally loads .rtk/filters.toml from the working directory with highest priori=
    ty and without user notification. An attacker can place a malicious filter = file in a repository to apply regex-based modifications (e.g., strip_lines_= matching) to shell command output before it is shown to the LLM, without an=
    y indication that the output has been modified. This allows attackers to se= lectively suppress or alter command output (including file contents, diffs,=
    and security scan results) without detection, potentially concealing malic= ious code during AI-assisted development or review. This vulnerability is f= ixed in 0.32.0. 2026-06-23 not yet calculated CVE-2026-45792 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-45792 ] ruby--net-imap Net::IMAP implements=
    Internet Message Access Protocol (IMAP) client functionality in Ruby. Prio=
    r to 0.6.5 and 0.5.15, several Net::IMAP commands accept a "raw data" argum= ent that is sent verbatim after validation to prevent command injection. Ho= wever, if a server does not support non-synchronizing literals, it may stil=
    l be possible to inject arbitrary IMAP commands inside non-synchronizing li= terals. A server without support for non-synchronizing literals may interpr=
    et the "+}\r\n" as the end of a malformed command line and respond with a t= agged BAD. In that case, the contents of the literal will be interpreted as=
    one or more new pipelined commands, allowing a CRLF command injection atta=
    ck to succeed. This affects criteria for #search and #uid_search; search_ke=
    ys for #sort, #thread, #uid_sort, and #uid_thread; and attr for #fetch and = #uid_fetch. This vulnerability is fixed in 0.6.5 and 0.5.15. 2026-06-22 not=
    yet calculated CVE-2026-47240 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-47240 ] ruby--net-imap Net::IMAP implements Internet Message Access Proto= col (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, several=
    Net::IMAP commands accept a raw string argument which is only validated to=
    prevent CRLF injection and then sent verbatim. If this string is derived f= rom user-controlled input, an attacker can force the next command to be abs= orbed as a continuation of the first command. This will cause the first com= mand to eventually fail, but also prevents it from returning until another = command is sent (from another thread). That other command will not return u= ntil the connection is closed. This vulnerability is fixed in 0.6.5 and 0.5= .15. 2026-06-22 not yet calculated CVE-2026-47241 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-47241 ] ruby--net-imap Net::IMAP implements Internet M= essage Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 = and 0.5.15, when Net::IMAP#id is called with a hash argument, although the =
    ID field value strings are correctly quoted (escaping quoted specials), the=
    y were not validated to prohibit CRLF sequences. While Net::IMAP#enable doe=
    s process its arguments for aliases, it does not validate them as valid ato=
    ms (or as a list of valid atoms). The #to_s value is sent verbatim. Argumen=
    ts to either command could be used by an attacker to inject arbitrary IMAP = commands. This vulnerability is fixed in 0.6.5 and 0.5.15. 2026-06-22 not y=
    et calculated CVE-2026-47242 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 47242 ] ruby-concurrency--concurrent-ruby concurrent-ruby is a modern concu= rrency tools for Ruby. Prior to 1.3.7, Concurrent::AtomicReference#update c=
    an enter a permanent busy retry loop when the current value is Float::NAN. = The issue is caused by the interaction between AtomicReference#update, whic=
    h retries until compare_and_set(old_value, new_value) succeeds; Numeric com= pare_and_set, which checks old =3D=3D old_value before attempting the under= lying atomic swap.; and Ruby NaN semantics, where Float::NAN =3D=3D Float::= NAN is always false. As a result, once an AtomicReference contains Float::N= AN, calling #update repeatedly evaluates the caller's block and never retur= ns. In services that store externally derived numeric values in an AtomicRe= ference, this can cause CPU exhaustion or permanent request/job hangs. This=
    vulnerability is fixed in 1.3.7. 2026-06-24 not yet calculated CVE-2026-54= 904 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54904 ] ruby-concurrency-= -concurrent-ruby concurrent-ruby is a modern concurrency tools for Ruby. Pr= ior to 1.3.7, Concurrent::ReentrantReadWriteLock can incorrectly grant a wr= ite lock after one thread acquires the read lock 32,768 times. The lock sto= res a thread's local read and write hold counts in one integer. The low 15 = bits are used for the read hold count, and bit 15 is used as WRITE_LOCK_HEL=
    D. After 32,768 reentrant read acquisitions, the local read count crosses i= nto the write-lock bit. try_write_lock then treats the thread as already ho= lding a write lock and returns true without setting the global RUNNING_WRIT=
    ER bit. This breaks the core mutual-exclusion guarantee: the caller is told=
    it has a write lock, but other threads can still hold or acquire read lock=
    s at the same time. This vulnerability is fixed in 1.3.7. 2026-06-24 not ye=
    t calculated CVE-2026-54905 [ https://www.cve.org/CVERecord?id=3DCVE-2026-5= 4905 ] ruby-concurrency--concurrent-ruby concurrent-ruby is a modern concur= rency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLock#release_wri= te_lock does not verify that the calling thread acquired the write lock. An=
    y thread with access to the lock object can release an active write lock he=
    ld by another thread. A second writer can then enter its critical section w= hile the first writer is still running. Concurrent::ReadWriteLock#release_r= ead_lock also decrements the shared counter even when no read lock is held.=
    Calling it on a fresh lock changes the counter from 0 to -1, after which n= ormal read acquisition raises Concurrent::ResourceLimitError. This is a syn= chronization correctness issue in the public Concurrent::ReadWriteLock API.=
    This vulnerability is fixed in 1.3.7. 2026-06-24 not yet calculated CVE-20= 26-54906 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54906 ] SafeLine--Sa= feLine SL6/SL6+ The SafeLine SL6 and SL6+ devices integrated into elevator = emergency intercom systems are vulnerable to an authentication bypass. This=
    vulnerability allows attackers to bypass authentication requirements and a= ccess the device's configuration service via the Bluetooth Low Energy (BLE)=
    interface. Consequently, an attacker within wireless range can gain unauth= orized administrative access to the device configuration. 2026-06-22 not ye=
    t calculated CVE-2025-4994 [ https://www.cve.org/CVERecord?id=3DCVE-2025-49=
    94 ] Safetica--Endpoint Client Kernel driver ProcessMonitorDriver.sys in Sa= fetica's endpoint client x64 , versions 10.5.75.0 and 11.11.4.0, allows unp= rivileged user to abuse IOCTL path and terminate protected system processes=
    . 2026-06-26 not yet calculated CVE-2026-0828 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-0828 ] Schneider Electric--EasyLogic T150 (formerly Saitel=
    DR) Remote Terminal Unit & Controller CWE-522 Insufficiently Protected Cre= dentials vulnerability that could cause unauthorized access and exposure of=
    sensitive information when unauthenticated attacker accesses credentials s= tored within firmware or system files. With this credential an attacker cou=
    ld subsequently compromise the device if they have physical access to the d= evice. 2026-06-25 not yet calculated CVE-2026-9650 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-9650 ] Schneider Electric--EasyLogic T150 (formerly S= aitel DR) Remote Terminal Unit & Controller CWE-732 Incorrect Permission As= signment for Critical Resource vulnerability that could cause unauthorized = disclosure of password hashes and potential account compromise when an atta= cker with privileged local access reads improperly protected system files. = 2026-06-25 not yet calculated CVE-2026-9651 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-9651 ] Schneider Electric--PowerLogic P7 CWE-476 NULL Pointe=
    r Dereference vulnerability exists that could cause a denial-of-service con= dition, rendering the device's HMI and configuration functionality unavaila= ble when malformed requests are received over exposed network interfaces. 2= 026-06-25 not yet calculated CVE-2026-9716 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-9716 ] Schneider Electric--PowerLogic P7 CWE-78 Neutralizatio=
    n of Special Elements used in an OS Command ('OS Command Injection') vulner= ability exists that could allow unauthorized execution of commands with ele= vated privileges, impacting system integrity, confidentiality, and availabi= lity when a privileged authenticated user interacts with a vulnerable netwo= rk-exposed service. 2026-06-25 not yet calculated CVE-2026-9717 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-9717 ] Schneider Electric--PowerLogic P7=
    CWE-617 Reachable Assertion vulnerability exists that could allow an authe= nticated attacker to trigger a denial-of-service condition, impacting syste=
    m availability when a specially crafted request is sent to a vulnerable net= work-exposed service. 2026-06-25 not yet calculated CVE-2026-9718 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-9718 ] seaweedfs--seaweedfs SeaweedFS =
    is a distributed storage system for object storage (S3), file systems, and = Iceberg tables. Prior to 4.30, the S3 API gateway and the Iceberg REST cata= log gateway construct their routers with mux.NewRouter().SkipClean(true). W= ith path cleaning disabled, a .. segment inside the URL survives routing, s=
    o a request such as `GET /bucket-A/../evil-bucket/key`, is matched as bucke= t=3Dbucket-A, object=3D../evil-bucket/key. The captured object key is then = joined into a filer path with util.JoinPath (S3) / path.Join (Iceberg), whi=
    ch collapse the .. server-side, so the actual read or write lands in evil-b= ucket. This vulnerability is fixed in 4.30. 2026-06-25 not yet calculated C= VE-2026-54917 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54917 ] Signifi= cant-Gravitas--AutoGPT AutoGPT is a workflow automation platform for creati= ng, deploying, and managing continuous artificial intelligence agents. Prio=
    r to 0.6.32, there is a DoS vulnerability in AITextSummarizerBlock. Malicio=
    us users can amplify their input. For example, if a malicious user inputs 1=
    0K of content, the server will consume 50G of memory, eventually causing me= mory resources to be exhausted, resulting in DoS. This vulnerability is fix=
    ed in 0.6.32. 2026-06-26 not yet calculated CVE-2025-32394 [ https://www.cv= e.org/CVERecord?id=3DCVE-2025-32394 ] Significant-Gravitas--AutoGPT AutoGPT=
    is a workflow automation platform for creating, deploying, and managing co= ntinuous artificial intelligence agents. Prior to 0.6.32, there is a DoS vu= lnerability in ExtractTextInformationBlock. Malicious users can amplify the=
    ir input. For example, if a malicious user inputs 10K of content, the serve=
    r will consume 50G of memory, eventually causing memory resources to be exh= austed, resulting in DoS. This vulnerability is fixed in 0.6.32. 2026-06-26=
    not yet calculated CVE-2025-32423 [ https://www.cve.org/CVERecord?id=3DCVE= -2025-32423 ] silabs.com--Simplicity SDK SYMCRYPTO is the SiXG301's host si=
    de hardware engine accessed by PSA crypto library that accelerates symmetri=
    c cryptographic operations (AES encryption/decryption and hashing). DPA Cou= ntermeasures on SYMCRYPTO can be weakened (reduced entropy) by forcing cert= ain seed values if an attacker gains code execution capability on the impac= ted device. * Therefore, the keys loaded on SYMCRYPTO may be more vulnerabl=
    e to extraction through DPA attacks than intended 2026-06-25 not yet calcul= ated CVE-2026-4930 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4930 ] Sil= icon Labs--EmberZNet In EmberZNet v9.0.2 and earlier, malformed global ZCL = messages can trigger out-of-bounds reads in framework parsing logic and ter= minate the process. These messages must come from a device that has already=
    joined the network, and no information leakage back to the sender was obse= rved. 2026-06-25 not yet calculated CVE-2026-4526 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-4526 ] Silicon Labs--EmberZNet In EmberZNet v9.0.2 and=
    earlier, malformed Color Control messages can lead to asserts that termina=
    te the process. These messages must come from a device that has already joi= ned the network. Only devices supporting the Color Control cluster may be i= mpacted. 2026-06-25 not yet calculated CVE-2026-47145 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-47145 ] Silicon Labs--EmberZNet In EmberZNet v9.0.=
    2 and earlier, malformed Color Control messages can lead to asserts that te= rminate the process. These messages must come from a device that has alread=
    y joined the network. Only devices supporting the Color Control cluster may=
    be impacted. 2026-06-25 not yet calculated CVE-2026-47146 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-47146 ] Silicon Labs--EmberZNet In EmberZNet = v9.0.2 and earlier, malformed OTA requests can drive the OTA server parser = into out-of-bounds reads. A limited amount of data from RAM is read back to=
    the requester. The size and location of this data is limited. These reques=
    ts must come from a device that has already joined the network. Only device=
    s supporting the OTA Server cluster may be impacted. 2026-06-25 not yet cal= culated CVE-2026-47147 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47147 =
    ] Silicon Labs--EmberZNet In EmberZNet v9.0.2 and earlier, malformed GetGro= upMembership commands can trigger repeated reads past the end of the messag=
    e payload and terminate the process. These messages must come from a device=
    that has already joined the network, and no information leakage back to th=
    e sender was observed. Only devices supporting the Groups cluster may be im= pacted. 2026-06-25 not yet calculated CVE-2026-47148 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-47148 ] Silicon Labs--EmberZNet In EmberZNet v9.0.2=
    and earlier, malformed or out-of-range Door Lock user identifiers can trig= ger out-of-bounds table reads and terminate the process. These messages mus=
    t come from a device that has already joined the network, and no informatio=
    n leakage back to the sender was observed. Only devices supporting the Door=
    Lock cluster may be impacted. 2026-06-25 not yet calculated CVE-2026-47149=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-47149 ] Silicon Labs--EmberZ= Net In EmberZNet v9.0.2 and earlier, malformed IAS Zone enrollment messages=
    can trigger an out-of-bounds state-table write and terminate the process. = The size and location of this write is limited. These messages must come fr=
    om a device that has already joined the network. Only devices supporting th=
    e IAS Zone cluster may be impacted. 2026-06-25 not yet calculated CVE-2026-= 47150 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47150 ] Silicon Labs--E= mberZNet In EmberZNet v9.0.2 and earlier, malformed ClearWeekdaySchedule me= ssages can trigger out-of-bounds writes into Door Lock schedule state. The = size and location of this data is limited. These messages must come from a = device that has already joined the network. Only devices supporting the Doo=
    r Lock cluster may be impacted. 2026-06-25 not yet calculated CVE-2026-4715=
    1 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47151 ] Silicon Labs--Ember= ZNet In EmberZNet v9.0.2 and earlier, a malformed Level Control Move comman=
    d can terminate the process through a divide-by-zero fault. This command mu=
    st come from a device that has already joined the network. Only devices sup= porting the Level Control cluster may be impacted. 2026-06-25 not yet calcu= lated CVE-2026-47152 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47152 ] = Silicon Labs--EmberZNet In EmberZNet v9.0.2 and earlier, a malformed Level = Control Step command can terminate the process through a divide-by-zero fau= lt. This command must come from a device that has already joined the networ=
    k. Only devices supporting the Level Control cluster may be impacted. 2026-= 06-25 not yet calculated CVE-2026-47153 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-47153 ] Silicon Labs--EmberZNet In EmberZNet v9.0.2 and earlier=
    , a malformed GetProfileResponse message can trigger out-of-bounds reads wh= ile iterating interval entries and terminate the process. These messages mu=
    st come from a device that has already joined the network, and no informati=
    on leakage back to the sender was observed. Only devices supporting the Sim= ple Metering cluster may be impacted. 2026-06-25 not yet calculated CVE-202= 6-47154 [ https://www.cve.org/CVERecord?id=3DCVE-2026-47154 ] Silicon Labs-= -SiSDK Incorrect use of the PUF key for user key generation in EFR32xG27 re= sults in predictable keys 2026-06-25 not yet calculated CVE-2026-2815 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-2815 ] Silicon Labs--SiSDK Imprope=
    r bounds validation in EmberZNet SDK versions 9.0.2 and earlier may result =
    in crashes or dynamic memory leakage. 2026-06-25 not yet calculated CVE-202= 6-6432 [ https://www.cve.org/CVERecord?id=3DCVE-2026-6432 ] siyuan-note--si= yuan SiYuan is an open-source personal knowledge management system. Prior t=
    o 3.7.0, SiYuan Note's kernel HTTP server unconditionally trusts all chrome= -extension:// origins, granting RoleAdministrator access to every installed=
    browser extension without any authentication. Combined with the default em= pty AccessAuthCode on desktop installs, any Chrome/Chromium extension -- in= cluding a compromised legitimate extension via supply chain attack -- can m= ake fully authenticated admin API calls to the SiYuan kernel at 127.0.0.1:6= 806, enabling data exfiltration, stored XSS injection, and configuration ta= mpering. This vulnerability is fixed in 3.7.0. 2026-06-24 not yet calculate=
    d CVE-2026-54069 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54069 ] siyu= an-note--siyuan SiYuan is an open-source personal knowledge management syst= em. Prior to 3.7.0, Lute's HTML sanitizer does not remove <iframe> elements=
    . Combined with the SiYuan Electron client's permissive security configurat= ion, an attacker can include a malicious <iframe> in a Bazaar package READM=
    E that executes arbitrary commands on the victim's machine when the package=
    details are viewed. No package installation is required. This vulnerabilit=
    y is fixed in 3.7.0. 2026-06-24 not yet calculated CVE-2026-54759 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-54759 ] sparklemotion--nokogiri Nokogi=
    ri is an open source XML and HTML library for the Ruby programming language=
    . Prior to 1.19.4, Nokogiri::XML::NodeSet#[] (and its alias #slice) checked=
    the requested index against the node set's bounds using a 32-bit-truncated=
    copy of the index. A large negative index could pass the check and then be=
    used at full width, reading outside the node set's storage. On CRuby this =
    is an out-of-bounds read that typically crashes the process; on JRuby it is=
    not memory-unsafe but returns an incorrect node. This vulnerability is fix=
    ed in 1.19.4. 2026-06-25 not yet calculated CVE-2026-57235 [ https://www.cv= e.org/CVERecord?id=3DCVE-2026-57235 ] sparklemotion--nokogiri Nokogiri is a=
    n open source XML and HTML library for the Ruby programming language. Prior=
    to 1.19.4, calling Document#encoding=3D with an invalid encoding (e.g., a = non-string, or a string containing a null byte) raises an exception, but on=
    ly after freeing the document's current encoding string without replacing i=
    t. The document is left referencing freed memory, so the next call to Docum= ent#encoding reads invalid memory, which can cause a segfault or leak freed=
    bytes into a Ruby String. Affects the CRuby (libxml2) implementation only;=
    JRuby is not affected. This vulnerability is fixed in 1.19.4. 2026-06-25 n=
    ot yet calculated CVE-2026-57236 [ https://www.cve.org/CVERecord?id=3DCVE-2= 026-57236 ] sparklemotion--nokogiri Nokogiri is an open source XML and HTML=
    library for the Ruby programming language. Prior to 1.19.4, Nokogiri conta= ins a bug when calling certain methods on allocated-but-uninitialized nativ=
    e wrapper classes that inherit from Nokogiri::XML::Node. This caused a NULL=
    pointer dereference that could crash the process. This vulnerability is fi= xed in 1.19.4. 2026-06-25 not yet calculated CVE-2026-57434 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-57434 ] sparklemotion--nokogiri Nokogiri is =
    an open source XML and HTML library for the Ruby programming language. Prio=
    r to 1.19.4, Nokogiri's CRuby native extension could leave a Ruby wrapper p= ointing to freed memory when replacing the value of an XML attribute. If Ru=
    by code had already accessed an attribute child node, Nokogiri::XML::Attr#v= alue=3D could free the underlying native child node while the wrapper remai= ned reachable through the document node cache. A later use of the freed chi=
    ld node or a Ruby GC mark could dereference an invalid pointer, causing an = invalid read and a possible segfault. This vulnerability is fixed in 1.19.4=
    . 2026-06-25 not yet calculated CVE-2026-57435 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-57435 ] sparklemotion--nokogiri Nokogiri is an open sourc=
    e XML and HTML library for the Ruby programming language. Prior to 1.19.4, = Nokogiri::XML::Document#root=3D validated only that the new root was a Noko= giri::XML::Node, allowing a DTD node to be set as the document root. The re= sult is a heap use-after-free during garbage collection or finalization, le= ading to an invalid memory read or potentially a segfault. This vulnerabili=
    ty is fixed in 1.19.4. 2026-06-25 not yet calculated CVE-2026-57436 [ https= ://www.cve.org/CVERecord?id=3DCVE-2026-57436 ] sparklemotion--nokogiri Noko= giri is an open source XML and HTML library for the Ruby programming langua= ge. Prior to 1.19.4, Nokogiri::XML::XPathContext did not keep its source do= cument alive for garbage collection. If an XPathContext outlived its docume=
    nt and the document was collected, evaluating an XPath expression could rea=
    d invalid memory and potentially segfault. This is only reachable when appl= ication code constructs an XPathContext directly and lets the document beco=
    me unreachable while continuing to use the context. The normal Document#xpa= th, #css, and related search methods are not affected, and it is not trigge= rable by malicious document input. This vulnerability is fixed in 1.19.4. 2= 026-06-25 not yet calculated CVE-2026-57437 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-57437 ] sparklemotion--nokogiri Nokogiri is an open source X=
    ML and HTML library for the Ruby programming language. Prior to 1.19.4, XIn= clude substitution performed by Nokogiri::XML::Node#do_xinclude replaced ea=
    ch <xi:include> in place, freeing the include node along with its children = (such as <xi:fallback> and its descendants) and any namespaces declared on = them. If an application had already exposed one of those nodes or namespace=
    s to Ruby, the corresponding Ruby object was left pointing at freed memory.=
    Using the object could result in invalid reads or writes to memory. This v= ulnerability is fixed in 1.19.4. 2026-06-25 not yet calculated CVE-2026-574=
    38 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57438 ] Technitium --Techn= itium DNS Server v.14.3 An issue in Technitium DNS Server v.14.3 and before=
    allows a remote attacker to cause a denial of service via the DnsServerApp= .exe, DnsServerApp.dll, TechnitiumLibrary.Net/Dns/DnsClient.cs components 2= 026-06-26 not yet calculated CVE-2026-36478 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-36478 ] Tenda--N300 F3 Cleartext storage and exposure of WPA=
    2 credentials, and missing authentication on the rr/wr memory read/write co= mmands, in the unauthenticated UART debug console of the Tenda N300 F3 (V60=
    3) allow a physically proximate attacker to obtain stored WPA2 credentials =
    in cleartext and to read or write arbitrary memory via the serial console. = 2026-06-26 not yet calculated CVE-2026-38571 [ https://www.cve.org/CVERecor= d?id=3DCVE-2026-38571 ] Thinkst Applied Research--Canarytokens An HTML inje= ction vulnerability exists in the Google Chat webhook notification=C2=A0 se=
    nt by Thinkst Applied Research Canarytokens, enabling Interface Manipulatio=
    n in Google Chat. An attacker can insert limited HTML content including lin= ks. This issue affects Canarytokens: from Docker tag sha-4aef1db90 before s= ha-8ab4dccd, from Git commit 4aef1db90 before 8ab4dccd. 2026-06-22 not yet = calculated CVE-2026-12888 [ https://www.cve.org/CVERecord?id=3DCVE-2026-128=
    88 ] Thinkst Applied Research--Canarytokens Stored Cross-Site Scripting in = the exposed AWS API key store of=C2=A0Thinkst Applied Research Canarytokens=
    . Anonymous exploitation requires knowledge of a random identifier. This is= sue affects Canarytokens: from Docker tag sha-4116b92cb before sha-f5aa5c4e=
    , from Git commit 4116b92cb before f5aa5c4e. 2026-06-24 not yet calculated = CVE-2026-13140 [ https://www.cve.org/CVERecord?id=3DCVE-2026-13140 ] ToolJe= t--ToolJet ToolJet is the open-source foundation am AI-native platform for = building and deploying internal tools, workflows and AI agents. Prior to 3.= 20.178-lts, any authenticated user with builder role (free tier) can overwr= ite a globally-shared marketplace plugin with arbitrary JavaScript that exe= cutes server-side with full Node.js access (require, process). The maliciou=
    s code runs whenever any user on the instance triggers a query using that p= lugin - achieving both RCE and supply-chain compromise of the entire ToolJe=
    t deployment. This vulnerability is fixed in 3.20.178-lts. 2026-06-25 not y=
    et calculated CVE-2026-55413 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 55413 ] Totolink--EX1200L Totolink=C2=A0EX1200L router is vulnerable to Buf= fer Overflow in the login functionality in=C2=A0cgi-bin/cstecgi.cgi endpoin= t.=C2=A0This vulnerability could be exploited to cause the program to crash=
    and to execute code remotely. This allows the attacker to perform actions =
    as root including reading and editing data, as well as bricking the router.=
    Because vendor contact attempts were unsuccessful, the vulnerability has o= nly been confirmed in version 9.3.5u.6146_B20201023 but may also affect oth=
    er versions. 2026-06-23 not yet calculated CVE-2026-44089 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-44089 ] TP-Link Systems Inc.--Archer MR200 v07=
    A command injection vulnerability has been identified in the DHCP option p= rocessing logic in multiple TP-Link router models, due to insufficient vali= dation of externally supplied DHCP option data.=C2=A0An adjacent attacker m=
    ay exploit this vulnerability by supplying crafted DHCP responses, potentia= lly resulting in unauthorized command execution during device initializatio=
    n or provisioning workflows. This typically occurs when the device is in a = factory-default or unconfigured state. Successful exploitation may allow an=
    adjacent, unauthenticated attacker to execute arbitrary commands with elev= ated privileges, potentially leading to full compromise of the affected dev= ice and unauthorized administrative control. 2026-06-22 not yet calculated = CVE-2026-11834 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11834 ] TP-Lin=
    k Systems Inc.--Tapo C200 v3 A denial-of-service (DoS) vulnerability has be=
    en identified in Tapo C200 v3 in the network packet handling logic due to i= mproper handling of IPv4 fragmented packets.=C2=A0 An unauthenticated adjac= ent attacker can send crafted packets to cause excessive resource consumpti= on, leading to instability of the device.Successful exploitation can remote=
    ly trigger a temporary denial-of-service condition,=C2=A0causing the camera=
    to become unresponsive and resulting in intermittent loss of video monitor= ing and recording. 2026-06-24 not yet calculated CVE-2026-12760 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-12760 ] traefik--traefik Traefik is an H= TTP reverse proxy and load balancer. Prior to 2.11.48, 3.6.19, and 3.7.3, t= here is a high severity vulnerability in Traefik's StripPrefix middleware t= hat allows an unauthenticated attacker to bypass route-level authentication=
    and authorization. When a public router matches on a PathPrefix rule and a= pplies the StripPrefix middleware, a request path containing .. or its perc= ent-encoded form %2e%2e can match the public route at routing time and then=
    , after the prefix is stripped and the path is normalized, resolve to a pat=
    h served by a separate, authenticated router. As a result, an attacker can = reach protected backend paths - such as admin or internal configuration end= points - without satisfying the authentication middleware attached to the p= rotected router. This vulnerability is fixed in 2.11.48, 3.6.19, and 3.7.3.=
    2026-06-23 not yet calculated CVE-2026-48020 [ https://www.cve.org/CVEReco= rd?id=3DCVE-2026-48020 ] traefik--traefik Traefik is an HTTP reverse proxy = and load balancer. From 3.7.0 until 3.7.3, there is a high severity vulnera= bility in Traefik's domain-fronting protection (SNICheck) that allows an un= authenticated client to bypass mutual TLS enforced through wildcard router = TLSOptions. When a router uses a wildcard host rule such as Host(*.example.= com) with stricter TLS options (for example RequireAndVerifyClientCert), SN= ICheck resolves the TLS options for the HTTP Host header using exact map lo= okups only and never applies wildcard matching. If another permissive SNI i=
    s served on the same entrypoint, an attacker can complete the TLS handshake=
    under the permissive options and then send an HTTP Host header targeting t=
    he wildcard-protected backend, reaching it without presenting a client cert= ificate. This affects the regular HTTPS / HTTP-2 path and does not require = HTTP/3. This vulnerability is fixed in 3.7.3. 2026-06-23 not yet calculated=
    CVE-2026-48491 [ https://www.cve.org/CVERecord?id=3DCVE-2026-48491 ] traef= ik--traefik Traefik is an HTTP reverse proxy and load balancer. Prior to 3.= 7.3, there is a critical vulnerability in Traefik's HTTP/3 (QUIC) TLS confi= guration selection that allows unauthenticated clients to bypass router-spe= cific mTLS enforcement. When HTTP/3 is enabled on an entrypoint, the TLS ha= ndshake selects the applicable TLS configuration through an exact, case-sen= sitive lookup on the SNI value, which fails to match wildcard host patterns=
    (e.g., *.example.com) or case variants of the configured hostname. Because=
    the handshake falls back to the default TLS configuration - which may not = require client certificates - a client can complete the QUIC handshake with= out presenting a certificate, while the subsequent HTTP routing layer still=
    dispatches the request to a backend protected by a router-specific mTLS po= licy. The issue affects deployments where HTTP/3 is enabled, a router uses =
    a wildcard Host rule or case-insensitive hostname matching, a router-specif=
    ic TLSOptions enforces client certificate authentication, and UDP access to=
    the entrypoint is reachable by an attacker. This vulnerability is fixed in=
    3.7.3. 2026-06-23 not yet calculated CVE-2026-53622 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-53622 ] traefik--traefik Traefik is an HTTP reverse=
    proxy and load balancer. Prior to 3.6.21 and 3.7.5, there is a high severi=
    ty vulnerability in Traefik's Kubernetes Gateway provider affecting the cro= ssProviderNamespaces allowlist. For HTTPRoute rules that declare multiple (= WRR) backendRefs, Traefik evaluates the allowlist against the target backen= dRef.namespace instead of the route's own namespace. As a result, an HTTPRo= ute created in a namespace that is not allow-listed can reference a cross-p= rovider TraefikService such as api@internal, dashboard@internal or rest@int= ernal by pointing backendRef.namespace at an allow-listed namespace covered=
    by a Gateway API ReferenceGrant, exposing internal Traefik services on the=
    data plane. Exploitation requires the ability to create an accepted HTTPRo= ute and a matching ReferenceGrant from an allow-listed namespace; it does n=
    ot require any change to Traefik static configuration, RBAC, or the deploym= ent itself. This vulnerability is fixed in 3.6.21 and 3.7.5. 2026-06-23 not=
    yet calculated CVE-2026-54761 [ https://www.cve.org/CVERecord?id=3DCVE-202= 6-54761 ] traefik--traefik Traefik is an HTTP reverse proxy and load balanc= er. From 3.7.0-ea.1 until 3.7.5, there is a medium severity vulnerability i=
    n Traefik's Kubernetes Ingress NGINX provider that causes affected routes t=
    o fail open. When an Ingress explicitly enables BasicAuth or DigestAuth thr= ough the supported nginx.ingress.kubernetes.io/auth-type and auth-secret an= notations, but the referenced auth Secret cannot be resolved or parsed, Tra= efik logs the resolution error, skips installing the authentication middlew= are, and still emits a router to the backend service. A route that operator=
    s intended to protect is therefore published to the data plane without its = authentication control, allowing unauthenticated access to the backend. The=
    trigger is an invalid or unresolved auth dependency - a missing, malformed=
    , unreadable, or policy-denied Secret - rather than an intentionally unprot= ected route. This vulnerability is fixed in 3.7.5. 2026-06-23 not yet calcu= lated CVE-2026-54762 [ https://www.cve.org/CVERecord?id=3DCVE-2026-54762 ] = Trellix--Trellix Network Security NX, EX, FX, AX, and CMS A Code Injection = vulnerability existed in Trellix Network Security CM and NX. A locally auth= enticated admin user can execute arbitrary code using the web interface and=
    Alert artifact details. 2026-06-26 not yet calculated CVE-2025-7958 [ http= s://www.cve.org/CVERecord?id=3DCVE-2025-7958 ] Unknown--AI Share & Summariz=
    e The AI Share & Summarize WordPress plugin before 2.0.4 does not sanitise = and escape some of its shortcode attributes before outputting them in a pag=
    e, allowing users with the Contributor role and above to perform Stored Cro= ss-Site Scripting attacks. 2026-06-24 not yet calculated CVE-2026-10531 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-10531 ] Unknown--Cornerstone The=
    Cornerstone WordPress plugin before 7.8.9 does not enforce capability chec=
    ks on one of its REST API routes, allowing any authenticated user to disclo=
    se the metadata of any other user, including roles, session token previews = and stored billing/shipping fields. This affects the premium co Cornerstone=
    page builder distributed bundled with the X , not the unrelated free `corn= erstone` Cornerstone WordPress plugin before 7.8.9 (v0.8.x) on the .org rep= ository. 2026-06-24 not yet calculated CVE-2026-9709 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-9709 ] Unknown--Cornerstone The Cornerstone WordPre=
    ss plugin before 7.8.8 does not enforce capability checks on one of its CSS= -preview request handlers, and exposes the nonce needed to call it to every=
    logged-in user on any wp-admin page, allowing any authenticated user to ev= aluate dynamic content tokens against arbitrary users and disclose their se= nsitive metadata including raw password hashes. This affects the premium co=
    Cornerstone page builder distributed bundled with the X , not the unrelate=
    d free `cornerstone` Cornerstone WordPress plugin before 7.8.8 (v0.8.x) on = the .org repository. 2026-06-24 not yet calculated CVE-2026-9710 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-9710 ] Unknown--Email Address Encoder T=
    he Email Address Encoder WordPress plugin before 1.0.25, email-encoder-prem= ium WordPress plugin before 0.3.12 does not properly handle email replaceme= nt, which could allow unauthenticated users to perform Stored XSS attacks 2= 026-06-25 not yet calculated CVE-2026-5305 [ https://www.cve.org/CVERecord?= id=3DCVE-2026-5305 ] Unknown--Frontend File Manager Plugin The Frontend Fil=
    e Manager Plugin WordPress plugin through 23.6 does not sanitise nor escape=
    a filename submitted to the frontend file-rename endpoint before storing i=
    t as post meta and rendering it back on the admin File Manager listing, lea= ding to a Stored Cross-Site Scripting vulnerability exploitable by users wi=
    th Subscriber-level access and above against an administrator viewing the f= ile management interface. 2026-06-23 not yet calculated CVE-2026-8378 [ htt= ps://www.cve.org/CVERecord?id=3DCVE-2026-8378 ] Unknown--Frontend File Mana= ger Plugin The Frontend File Manager Plugin WordPress plugin through 23.6 d= oes not properly enforce its nonce check on the file download handler, allo= wing unauthenticated attackers to download files uploaded by any user throu=
    gh the Frontend File Manager Plugin WordPress plugin through 23.6 by iterat= ing identifiers. 2026-06-23 not yet calculated CVE-2026-8379 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-8379 ] Unknown--Frontend File Manager Plugi=
    n The Frontend File Manager Plugin WordPress plugin through 23.6 does not p= roperly verify ownership of every targeted post before permanent deletion, = allowing authenticated users with author-level access and above to permanen= tly delete arbitrary posts and pages. When the Frontend File Manager Plugin=
    WordPress plugin through 23.6's "Allow guest uploads" setting is enabled b=
    y an administrator, the same deletion primitive becomes reachable by unauth= enticated users. 2026-06-26 not yet calculated CVE-2026-8380 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-8380 ] Unknown--Infility Global The Infilit=
    y Global Infility Global WordPress plugin before 2.15.20 for WordPress does=
    not sanitize or validate the orderby and order parameters in the import_li= st(), url_detail(), and file_detail() admin page callbacks before using the=
    m in SQL queries, allowing authenticated attackers with Editor-level access=
    or higher to perform time-based blind SQL injection and extract sensitive = data from the database. The ImportData module must be enabled via the Infil= ity Global WordPress plugin before 2.15.20's module toggle page. 2026-06-23=
    not yet calculated CVE-2026-7842 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-7842 ] Unknown--Infility Global The Infility Global WordPress plugin b= efore 2.15.19 does not properly sanitize and escape some parameters before = using them in SQL statements, leading to a SQL Injection vulnerability expl= oitable by authenticated users with Subscriber-level access and above. 2026= -06-23 not yet calculated CVE-2026-8163 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-8163 ] Unknown--InPost PL The InPost PL WordPress plugin before=
    1.9.1 does not verify that the request originates from the legitimate buye=
    r before allowing the WooCommerce order parcel-locker destination to be upd= ated, allowing unauthenticated attackers to silently redirect the shipping = destination of any pending or processing order on the site. 2026-06-25 not = yet calculated CVE-2026-9702 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 9702 ] Unknown--Masteriyo LMS The Masteriyo LMS WordPress plugin before 2.2=
    .1 does not perform authorization checks in a course-progress REST API cont= roller, allowing unauthenticated users to read and permanently delete any u= ser's course-progress records. 2026-06-25 not yet calculated CVE-2026-10824=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-10824 ] Unknown--Motors The = Motors WordPress plugin before 1.4.110 does not have proper authorisation a=
    nd CSRF checks on one of its AJAX actions, allowing unauthenticated attacke=
    rs to modify arbitrary post metadata, such as the gallery, featured image a= nd, on WooCommerce sites, product prices. 2026-06-22 not yet calculated CVE= -2026-7859 [ https://www.cve.org/CVERecord?id=3DCVE-2026-7859 ] Unknown--Pa=
    id Membership Plugin, Ecommerce, User Registration Form, Login Form, User P= rofile & Restrict Content The Paid Membership Plugin, Ecommerce, User Regis= tration Form, Login Form, User Profile & Restrict Content WordPress plugin = before 4.16.17 does not verify that the user performing a subscription acti=
    on owns the targeted subscription, allowing any authenticated user (Subscri= ber+) to cancel other users' active subscriptions via an Insecure Direct Ob= ject Reference. 2026-06-27 not yet calculated CVE-2026-10820 [ https://www.= cve.org/CVERecord?id=3DCVE-2026-10820 ] Unknown--Pie Register The Pie Regis= ter WordPress plugin before 3.8.4.10 does not use sufficiently random value=
    s when generating its account verification tokens, allowing unauthenticated=
    attackers to predict a valid token and activate an account without access =
    to the associated email inbox. 2026-06-22 not yet calculated CVE-2026-10530=
    [ https://www.cve.org/CVERecord?id=3DCVE-2026-10530 ] Unknown--Post Duplic= ator The Post Duplicator WordPress plugin before 3.0.15 does not safely han= dle custom meta-data during post duplication, storing attacker-supplied ser= ialized values without the WordPress meta API's double-serialization protec= tion, allowing users with Contributor-level access and above to inject a PH=
    P Object. 2026-06-24 not yet calculated CVE-2026-10749 [ https://www.cve.or= g/CVERecord?id=3DCVE-2026-10749 ] Unknown--Printcart Web to Print Product D= esigner for WooCommerce The Printcart Web to Print Product Designer for Woo= Commerce WordPress plugin through 2.4.8 is vulnerable to path traversal whi=
    ch makes it possible for the attacker to retrieve the directory listing for=
    arbitrary directories on the server. 2026-06-26 not yet calculated CVE-202= 5-10268 [ https://www.cve.org/CVERecord?id=3DCVE-2025-10268 ] Unknown--SALE= Smanago & Leadoo The SALESmanago & Leadoo WordPress plugin before 3.11.3 do=
    es not properly sanitise and escape a parameter passed to one of its AJAX a= ctions before using it in a SQL statement, and fails to enforce authorisati=
    on on that action, allowing authenticated users with minimal permissions, s= uch as subscribers, to perform SQL injection attacks. 2026-06-26 not yet ca= lculated CVE-2026-10835 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10835=
    ] Unknown--Shariff for WordPress The Shariff for WordPress Shariff for Wor= dPress plugin through 1.0.11 does not sanitize or escape the shariff_infour=
    l setting before outputting it in the frontend HTML via the generateshariff=
    () function, which could allow high privilege users such as admin to perfor=
    m Stored Cross-Site Scripting attacks even when the unfiltered_html capabil= ity is disallowed (for example in multisite setup). 2026-06-27 not yet calc= ulated CVE-2026-9677 [ https://www.cve.org/CVERecord?id=3DCVE-2026-9677 ] U= nknown--Simple Basic Contact Form The Simple Basic Contact Form WordPress p= lugin through 20250114 does not escape user-supplied input before reflectin=
    g it into the contact form output on validation errors, leading to a Reflec= ted Cross-Site Scripting vulnerability that unauthenticated attackers can e= xploit against site visitors via a crafted link or cross-site form submissi= on. 2026-06-23 not yet calculated CVE-2026-8172 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-8172 ] Unknown--Site Kit by Google The Site Kit by Googl=
    e WordPress plugin before 1.176.0 does not properly restrict a REST API wri=
    te endpoint to administrators, allowing lower-privileged users who have bee=
    n granted dashboard sharing access (such as Editors) to modify a site-wide = Site Kit by Google WordPress plugin before 1.176.0 setting that should only=
    be modifiable by administrators. 2026-06-24 not yet calculated CVE-2026-10= 753 [ https://www.cve.org/CVERecord?id=3DCVE-2026-10753 ] Unknown--smart-po= st-show-pro Multiple Shapedsmart-post-show-pro WordPress plugin before 4.0.=
    2, Real Testimonials Pro WordPress plugin before 3.2.5, Product Slider for = WooCommerce Pro WordPress plugin before 3.5.3 Pro smart-post-show-pro WordP= ress plugin before 4.0.2, Real Testimonials Pro WordPress plugin before 3.2= .5, Product Slider for WooCommerce Pro WordPress plugin before 3.5.3 were d= istributed with malicious code through the vendor's compromised update serv= er, allowing unauthenticated attackers to deploy a second-stage payload tha=
    t exfiltrates credentials and other sensitive data and grants full control =
    of affected sites. 2026-06-24 not yet calculated CVE-2026-10735 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-10735 ] Unknown--Transbank Webpay The Tr= ansbank Webpay WordPress plugin before 1.14.0 does not sanitize and escape = logs to be displayed, allowing unauthenticated users to perform Stored XSS = attacks against logged in administrator 2026-06-22 not yet calculated CVE-2= 026-6858 [ https://www.cve.org/CVERecord?id=3DCVE-2026-6858 ] Unknown--ulti= mate-woocommerce-auction-pro The ultimate-woocommerce-auction-pro WordPress=
    plugin through 2.4.5 does not sanitise and escape a parameter before outpu= tting it back in the page, leading to a Reflected Cross-Site Scripting whic=
    h could be used against high privilege users such as admin 2026-06-22 not y=
    et calculated CVE-2026-4110 [ https://www.cve.org/CVERecord?id=3DCVE-2026-4= 110 ] Unknown--ultimate-woocommerce-auction-pro The ultimate-woocommerce-au= ction-pro WordPress plugin through 2.4.5 does not sanitise and escape a par= ameter before outputting it back in the page, leading to a Reflected Cross-= Site Scripting which could be used against high privilege users such as adm=
    in 2026-06-22 not yet calculated CVE-2026-4259 [ https://www.cve.org/CVERec= ord?id=3DCVE-2026-4259 ] Unknown--Vitepos The Vitepos WordPress plugin befo=
    re 3.4.2 does not properly restrict the roles that can be assigned when cre= ating new users via one of its REST API endpoints, allowing authenticated u= sers with a custom Vitepos WordPress plugin before 3.4.2 role to escalate p= rivileges to administrator. 2026-06-22 not yet calculated CVE-2026-8157 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-8157 ] Unknown--YMC Filter The Y=
    MC Filter WordPress plugin before 3.11.3 does not properly authorize access=
    to one of its REST API endpoints and does not validate a user-supplied que=
    ry parameter, allowing unauthenticated attackers to retrieve the titles and=
    content of private, draft, and other non-public posts. 2026-06-26 not yet = calculated CVE-2026-10823 [ https://www.cve.org/CVERecord?id=3DCVE-2026-108=
    23 ] Unraid--Unraid Unraid Web Server FileUpload Command Injection Remote C= ode Execution Vulnerability. This vulnerability allows remote attackers to = execute arbitrary code on affected installations of Unraid. Authentication =
    is required to exploit this vulnerability. The specific flaw exists within = FileUpload.php. The issue results from the lack of proper validation of a u= ser-supplied string before using it to execute a system call. An attacker c=
    an leverage this vulnerability to execute code in the context of the www-da=
    ta user. Was ZDI-CAN-30116. 2026-06-24 not yet calculated CVE-2026-9772 [ h= ttps://www.cve.org/CVERecord?id=3DCVE-2026-9772 ] Unraid--Unraid Unraid Web=
    Server ToggleState Command Injection Remote Code Execution Vulnerability. = This vulnerability allows remote attackers to execute arbitrary code on aff= ected installations of Unraid. Authentication is required to exploit this v= ulnerability. The specific flaw exists within ToggleState.php. The issue re= sults from the lack of proper validation of a user-supplied string before u= sing it to execute a system call. An attacker can leverage this vulnerabili=
    ty to execute code in the context of the www-data user. Was ZDI-CAN-30134. = 2026-06-24 not yet calculated CVE-2026-9773 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-9773 ] upKeeper Solutions--upKeeper Instant Privilege Access=
    Improper output neutralization for logs vulnerability in upKeeper Solution=
    s upKeeper Instant Privilege Access on Windows allows Log Injection-Tamperi= ng-Forging. This issue affects upKeeper Instant Privilege Access: through 1= .6.1. 2026-06-24 not yet calculated CVE-2026-10745 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-10745 ] vim--vim Vim is an open source, command line = text editor. Prior to 9.2.0653, the tree_count_words() function in src/spel= lfile.c fills in the word-count fields of a spell-file word trie by walking=
    it iteratively with a depth counter. The counter is bounded only by the tr=
    ie structure itself; it is never checked against the size of the fixed MAXW= LEN-element stack arrays it indexes (arridx[], curi[], wordcount[]). A craf= ted .spl/.sug file pair, loaded when the user invokes spell suggestion, can=
    drive the descent arbitrarily deep, so the function writes past the end of=
    those arrays. This is a stack out-of-bounds write that corrupts the call f= rame and crashes the editor. This vulnerability is fixed in 9.2.0653. 2026-= 06-25 not yet calculated CVE-2026-55693 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-55693 ] vim--vim Vim is an open source, command line text edito=
    r. Prior to 9.2.0663, a Vimscript code injection vulnerability exists in s:= NetrwLocalRmFile() in the netrw plugin (runtime/pack/dist/opt/netrw/autoloa= d/netrw.vim) when deleting a local file from the browser. A filename derive=
    d from the buffer's directory listing is interpolated into an Ex command li=
    ne passed to :execute with only the backslash character escaped, allowing a=
    crafted filename containing a bar (|) to terminate the intended command an=
    d execute arbitrary Vimscript, including shell commands via :call system() = and :!. This vulnerability is fixed in 9.2.0663. 2026-06-25 not yet calcula= ted CVE-2026-55895 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55895 ] vi= m--vim Vim is an open source, command line text editor. From 9.2.0320 until=
    9.2.0679, a crafted undo or swap file can store a virtual-text property wh= ose offset and length point outside the line's property data. When Vim rest= ores or displays such a line it converts the offset into a pointer and read=
    s the virtual text without bounds checking, causing an out-of-bounds read t= hat can crash Vim or disclose adjacent heap memory. This vulnerability is f= ixed in 9.2.0679. 2026-06-25 not yet calculated CVE-2026-57454 [ https://ww= w.cve.org/CVERecord?id=3DCVE-2026-57454 ] vim--vim Vim is an open source, c= ommand line text editor. Prior to 9.2.0698, the single-byte branch of spell= _soundfold_sofo() in src/spell.c translates a word through a spell file's S= OFO (sound-folding) byte map into a caller-owned result buffer. Its copy lo=
    op advances the output index ri with no upper bound and terminates only on = the input NUL, writing one byte per input byte into the MAXWLEN-element sta=
    ck buffer the caller provides. A word longer than MAXWLEN, passed to soundf= old() (or reached via sound-based spell suggestion) while a SOFO-based spel=
    l language is active, therefore writes past the end of that buffer. This is=
    a stack out-of-bounds write that corrupts the call frame and crashes the e= ditor. This vulnerability is fixed in 9.2.0698. 2026-06-25 not yet calculat=
    ed CVE-2026-57455 [ https://www.cve.org/CVERecord?id=3DCVE-2026-57455 ] vim= --vim Vim is an open source, command line text editor. Prior to 9.2.0699, V= im's Python omni-completion (runtime/autoload/python3complete.vim and the l= egacy pythoncomplete.vim) executes reconstructed function and class definit= ions from the current buffer with exec() as part of populating the completi=
    on dictionary. When reconstructing that source, each scope's docstring is i= nserted verbatim between triple quotes with no escaping, so a hostile buffe=
    r can break out of the triple-quoted literal and execute attacker-controlle=
    d Python during omni-completion. This vulnerability is fixed in 9.2.0699. 2= 026-06-25 not yet calculated CVE-2026-57456 [ https://www.cve.org/CVERecord= ?id=3DCVE-2026-57456 ] vitejs--launch-editor launch-editor allows users to = open files with line numbers in editor from Node.js. Prior to 2.14.1, the l= aunch-editor NPM package accesses arbitrary paths including Windows UNC pat= hs. When a UNC path is opened, Windows automatically attempts NTLM authenti= cation to the remote host, causing the user's NTLMv2 password hash to be le= aked to an attacker-controlled SMB server. This can result in credential co= mpromise through offline hash cracking. This vulnerability is fixed in 2.14= .1. 2026-06-22 not yet calculated CVE-2026-53632 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-53632 ] vitejs--vite Vite is a frontend tooling framewo=
    rk for JavaScript. Prior to 8.0.16, 7.3.5, and 6.4.3, the contents of files=
    that are specified by server.fs.deny can be returned to the browser on Win= dows. Vite's dev server denies direct access to sensitive files through ser= ver.fs.deny, including entries such as .env, .env.*, and *.{crt,pem}. Howev= er, on Windows, the deny logic does not correctly normalize NTFS ADS path f= orms before access checks are applied. Because of this, requests such as /.= env::$DATA?raw are treated as allowed paths, while Windows resolves them to=
    the original file's default data stream. Similar to that, Windows allows a= ccessing a file using a different name with the 8.3 short name compatibilit=
    y feature. Vite did not reject accessing files via them. This vulnerability=
    is fixed in 8.0.16, 7.3.5, and 6.4.3. 2026-06-22 not yet calculated CVE-20= 26-53571 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53571 ] vllm-project= --vllm vLLM is an inference and serving engine for large language models (L= LMs). From 0.5.5 until 0.23.1rc0, integer truncation of tensor dimensions i=
    n vLLM's GGUF dequantize kernels (csrc/quantization/gguf/gguf_kernel.cu) ca= uses partial tensor processing. The output tensor is allocated at full size=
    via torch::empty (uninitialized memory), but the dequantize CUDA kernel pr= ocesses only a truncated number of elements. The unfilled portion of the ou= tput tensor retains whatever was previously in GPU memory. In multi-tenant = inference deployments, this residual GPU memory may contain tensor data fro=
    m other users' inference requests, constituting information disclosure. Thi=
    s vulnerability is fixed in 0.23.1rc0. 2026-06-22 not yet calculated CVE-20= 26-53923 [ https://www.cve.org/CVERecord?id=3DCVE-2026-53923 ] vllm-project= --vllm vLLM is an inference and serving engine for large language models (L= LMs). Prior to 0.23.1rc0, ll temperature validation gates use comparison op= erators (<, >), which silently evaluate to False for NaN and for positive I= nfinity in Python's IEEE 754 float semantics. Both values pass every guard = and propagate to GPU sampling kernels, where they produce undefined behavio=
    r or CUDA errors that can crash the inference worker. This vulnerability is=
    fixed in 0.23.1rc0. 2026-06-22 not yet calculated CVE-2026-54235 [ https:/= /www.cve.org/CVERecord?id=3DCVE-2026-54235 ] Wolfram Research Inc.--Cloud T=
    he default JVM can access files and directories under `/tmp/` including the=
    `$TemporaryDirectory` of other users on the same cloud instance (`/tmp/Use= rTemporaryFiles/`). The `-init` file for the the JVM initialization exists =
    in the vulnerable directory during the startup of the JVM. An attacker with=
    access to the shared `/tmp/` space can preemptively create or replace `.ja=
    r` files or directories (via the `-init` file) that the victim JVM will res= olve first in its classpath. By strategically placing a malicious version o=
    f a commonly used library (e.g., `commons-io`) in a location that is includ=
    ed in the classpath before the legitimate version, an attacker can cause th=
    e JVM to load the malicious class during startup, thereby executing the att= acker's code. 2026-06-26 not yet calculated CVE-2025-11919 [ https://www.cv= e.org/CVERecord?id=3DCVE-2025-11919 ] wolfSSL--wolfSSL wolfSSL's AVX2-optim= ized ML-KEM implementation (mlkem_cmp_avx2) compares only 1536 of the 1568 = ciphertext bytes during the Fujisaki-Okamoto re-encryption check in ML-KEM-= 1024 decapsulation. Ciphertexts that differ from the expected re-encryption=
    solely in bytes 1536-1567 bypass implicit rejection and are accepted as va= lid, breaking IND-CCA2 security. An attacker able to submit chosen cipherte= xts to a decapsulation oracle that uses a static ML-KEM-1024 key, and to ob= serve whether the genuine shared secret or the implicit-rejection secret wa=
    s produced, can use this as a plaintext-checking oracle to recover the priv= ate key. A proof of concept recovered a full ML-KEM-1024 private key with a= pproximately 98% success using roughly 350 chosen ciphertexts. The flaw is =
    a deterministic logic error and does not rely on timing measurements. 2026-= 06-25 not yet calculated CVE-2026-10097 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-10097 ] wolfSSL--wolfSSL OCSP CertID serial-number length-confu= sion in wolfSSL_OCSP_resp_find_status allows a same-issuer SingleResponse w= hose serial is a prefix of the target serial to be reported as the revocati=
    on status of a different certificate. The lookup compared serial-number byt=
    es without first requiring the two serial numbers to be of equal length, so=
    a SingleResponse for one certificate (same issuer) whose serial is a prefi=
    x of the target's serial would match, returning the wrong certificate's sta= tus. The fix requires the serial lengths to be equal before comparing the s= erial bytes. 2026-06-25 not yet calculated CVE-2026-10098 [ https://www.cve= .org/CVERecord?id=3DCVE-2026-10098 ] wolfSSL--wolfSSL The X25519 x86_64 ass= embly implementation fails to clear the most significant bit during the fin=
    al modular reduction, so the computed result may not be fully reduced modul=
    o the field prime 2^255 - 19. This can leave the field element in a non-can= onical form, producing an incorrect result from the scalar multiplication a=
    nd potentially a wrong shared secret. The final carry-propagation chains in=
    the x64 and AVX2 reduction routines could overflow into the top bit, and t=
    he high limb was not masked afterward, so the 255-bit field element was lef=
    t non-canonical. 2026-06-25 not yet calculated CVE-2026-10512 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-10512 ] wolfSSL--wolfSSL Certificates with=
    wildcard DNS SANs (e.g. *.example.com) bypassed CA name-constraint checks.=
    A certificate with a wildcard DNS SAN that should be rejected by the issui=
    ng CA's permitted/excluded DNS name constraints could be accepted. 2026-06-=
    25 not yet calculated CVE-2026-10592 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-10592 ] wolfSSL--wolfSSL X.509 trust-chain bypass in the OpenSSL co= mpatibility certificate verifier (wolfSSL_X509_verify_cert()). This affects=
    only builds with --enable-opensslextra (OPENSSL_EXTRA) and whose applicati=
    on validates certificates by calling X509_verify_cert() with caller-supplie=
    d untrusted intermediate certificates; for those users it is critical, othe= rwise the library is unaffected. In particular, native wolfSSL TLS/DTLS usa=
    ge is not impacted. wolfSSL's X509_verify_cert() temporarily loads each cal= ler-supplied untrusted intermediate into the certificate manager but failed=
    to drop them before the trusted-store check, so an untrusted intermediate = could anchor the path itself. An attacker can present a chain that never re= aches a configured trust anchor and have it accepted, resulting in acceptan=
    ce of an attacker-controlled certificate. This is certificate verification = independent of TLS (e.g. S/MIME/CMS, code/firmware signing, JWT/JWS x5c), i=
    s not specific to any key type or algorithm, and a single untrusted interme= diate suffices. The default wolfSSL TLS handshake (WOLFSSL_VERIFY_PEER) is = not affected; only TLS applications doing manual or deferred peer verificat= ion through this API are, which also requires --enable-sessioncerts. 2026-0= 6-25 not yet calculated CVE-2026-11310 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-11310 ] wolfSSL--wolfSSL Missing SNI/ALPN binding on stateful (= session-ID) resumption, which previously skipped the binding check performe=
    d for ticket-based resumption. A cached session could be resumed under a di= fferent SNI/ALPN than originally negotiated and, where client-authenticatio=
    n policy differs across virtual hosts, carry the cached peer-authentication=
    state into a context it was not established for. Resumption now verifies t=
    he SNI/ALPN binding for all paths and declines (falling back to a full hand= shake) on mismatch. 2026-06-25 not yet calculated CVE-2026-11703 [ https://= www.cve.org/CVERecord?id=3DCVE-2026-11703 ] wolfSSL--wolfSSL X.509 trust-ch= ain bypass (path-depth exhaustion) in the OpenSSL compatibility certificate=
    verifier (wolfSSL_X509_verify_cert()). This affects only builds with --ena= ble-opensslextra whose application calls X509_verify_cert() with caller-sup= plied untrusted intermediates; for those users it is critical, otherwise th=
    e library is unaffected. Native wolfSSL TLS/DTLS usage is not impacted. X50= 9_verify_cert() returned success based only on the last verified link rathe=
    r than on reaching a trust anchor: when the supplied chain is deeper than t=
    he verifier's maximum path depth (default 100), path building runs out of d= epth while still walking untrusted intermediates and the chain is accepted = even though it never reaches a configured trust anchor, allowing acceptance=
    of an attacker-controlled certificate. The default TLS handshake (WOLFSSL_= VERIFY_PEER) is not affected; only applications doing manual or deferred ve= rification through this API are. 2026-06-25 not yet calculated CVE-2026-119=
    99 [ https://www.cve.org/CVERecord?id=3DCVE-2026-11999 ] wolfSSL--wolfSSL O= ut-of-bounds heap read during SM2/SM3 certificate signature verification. W= hen parsing a certificate with an SM3wSM2 signature, the Subject Key Identi= fier computation reads the trailing 65 bytes of the public key without chec= king that the key is at least that long. A public key shorter than 65 bytes=
    results in an out-of-bounds heap read, leading to a potential crash (denia=
    l of service); there is no out-of-bounds write. Note this only affects buil=
    ds with SM2 support (--enable-sm2 or --enable-all). 2026-06-25 not yet calc= ulated CVE-2026-12340 [ https://www.cve.org/CVERecord?id=3DCVE-2026-12340 ]=
    wolfSSL--wolfSSL Out-of-bounds write in the Renesas TSIP TLS 1.3 transcrip=
    t buffer. In tsip_StoreMessage() the capacity check guarding the fixed mess= age bag (MSGBAG_SIZE) sets an error code but fails to return, so execution = falls through to an XMEMCPY that writes past the end of the buffer once the=
    accumulated TLS 1.3 handshake transcript exceeds MSGBAG_SIZE (8 KB), corru= pting adjacent heap state and potentially causing a remote denial of servic=
    e crash. The bag is sized to hold a normal handshake, so this is reached on=
    ly by an unusually large but valid certificate chain, or by a malicious or = man-in-the-middle server sending an oversized handshake message to a client=
    that does not strictly verify the chain. This only affects builds using th=
    e Renesas TSIP TLS port (WOLFSSL_RENESAS_TSIP_TLS) as a TLS 1.3 client on R= enesas MCUs with TSIP hardware enabled, and is rated High within those buil= ds. All other configurations are unaffected. 2026-06-25 not yet calculated = CVE-2026-55958 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55958 ] wolfSS= L--wolfSSL Un-negotiated Raw Public Key (RFC 7250) accepted in place of an = X.509 certificate, bypassing chain validation. A raw public key has no chai=
    n, so ParseCertRelative() accepts it without performing any trust verificat= ion; it must therefore only be accepted when RPK was actually negotiated fo=
    r that peer. The check now defaults the expected type to X.509 (per RFC 725= 0/8446) when no type was negotiated, comparing against the received server = certificate type on the client and the selected client certificate type on = the server, and rejects any mismatch, including an un-negotiated raw public=
    key, with UNSUPPORTED_CERTIFICATE. Only affects builds with Raw Public Key=
    support (HAVE_RPK) enabled - disabled by default in a standalone build, bu=
    t included in --enable-all. 2026-06-25 not yet calculated CVE-2026-55960 [ = https://www.cve.org/CVERecord?id=3DCVE-2026-55960 ] wolfSSL--wolfSSL wolfSS= L_PKCS7_verify() returning success for a degenerate (certs-only) PKCS#7 obj= ect that contains no signer. Such an object has empty signerInfos, so the u= nderlying signed-data verification succeeds without authenticating any cont= ent. The compatibility-layer verify path now rejects the object when no sig= ner signature has actually been verified, so a PKCS#7 carrying no valid sig= nature is no longer reported as verified. This is enforced regardless of th=
    e PKCS7_NOVERIFY flag, which only suppresses signer certificate chain valid= ation and was never intended to waive the requirement that a signature exis=
    t. Only affects OpenSSL compatibility builds that call the PKCS7_verify() c= ompatibility API on potentially degenerate PKCS#7 bundles. 2026-06-25 not y=
    et calculated CVE-2026-55961 [ https://www.cve.org/CVERecord?id=3DCVE-2026-= 55961 ] wolfSSL--wolfSSL TLS 1.3 post-handshake authentication (PHA) issue = where a server could accept a client's Finished message without the client = having sent a Certificate and CertificateVerify. The post-handshake-auth ex= emption that allows an empty/absent peer certificate was only intended for = the initial handshake, but it was also being applied while a post-handshake=
    CertificateRequest was still outstanding. The check is now scoped to the i= nitial handshake only: on the server, once a post-handshake CertificateRequ= est has been sent (certReqCtx is set), a peer certificate and a valid Certi= ficateVerify are required again before the Finished is accepted, with empty= -certificate handling following the configured verify mode (FAIL_IF_NO_PEER= _CERT) just as during first-handshake client authentication. Only affects T=
    LS 1.3 servers built with post-handshake authentication support (WOLFSSL_PO= ST_HANDSHAKE_AUTH / --enable-postauth, included in --enable-all) that enabl=
    e WOLFSSL_VERIFY_POST_HANDSHAKE and request a client certificate after the = handshake via wolfSSL_request_certificate(). Clients, and servers that do n=
    ot use post-handshake authentication, are unaffected. 2026-06-25 not yet ca= lculated CVE-2026-55962 [ https://www.cve.org/CVERecord?id=3DCVE-2026-55962=
    ] wolfSSL--wolfSSL Chain intermediate CA:TRUE without keyCertSign accepted=
    as a signing CA. Intermediate CA certificates are required to have the key= CertSign key usage when a Key Usage extension is present, but chain-supplie=
    d temporary CAs (WOLFSSL_TEMP_CA) added while building a certificate path w= ere previously exempted from this check, so an intermediate asserting CA:TR=
    UE but lacking keyCertSign was accepted as a signing CA. The check now appl= ies to chain-supplied temporary CAs as well; only operator-loaded root cert= ificates (WOLFSSL_USER_CA) and self-signed roots remain exempt. Per RFC 528=
    0 an absent Key Usage extension implies all usages, so the requirement is e= nforced only when the extension is actually present (extKeyUsageSet). Affec=
    ts the OpenSSL-compatibility certificate-path-building path (X509_verify_ce=
    rt / X509_STORE, OPENSSL_EXTRA/OPENSSL_ALL), where untrusted chain intermed= iates are added as temporary CAs; native (non-OpenSSL-compat) certificate v= erification does not create temporary CAs and is unaffected. Within those b= uilds, the check applies unless ALLOW_INVALID_CERTSIGN is defined. 2026-06-=
    25 not yet calculated CVE-2026-55964 [ https://www.cve.org/CVERecord?id=3DC= VE-2026-55964 ] wolfSSL--wolfSSL AES-GCM encryption/decryption with extreme=
    ly large cumulative single message sizes (>64 GiB) were not properly reject=
    ed by the streaming APIs, allowing counter wrap, keystream reuse, and conse= quent plaintext recovery. 2026-06-25 not yet calculated CVE-2026-55967 [ ht= tps://www.cve.org/CVERecord?id=3DCVE-2026-55967 ] wolfSSL--wolfSSL Partial-= chain certificate verification may accept chains that terminate at a peer-s= upplied, untrusted intermediate certificate rather than a trusted anchor. A=
    n attacker could present a chain that ends at an intermediate they control = and have it accepted as valid. This affects the OpenSSL compatibility certi= ficate-path-building path (wolfSSL_X509_verify_cert / X509_STORE, OPENSSL_E= XTRA) when the X509_V_FLAG_PARTIAL_CHAIN verify flag is enabled. 2026-06-25=
    not yet calculated CVE-2026-6091 [ https://www.cve.org/CVERecord?id=3DCVE-= 2026-6091 ] wolfSSL--wolfSSL When HAVE_ENCRYPT_THEN_MAC is configured, the = implementation could fall back to MAC-then-Encrypt rather than enforcing En= crypt-then-MAC. 2026-06-25 not yet calculated CVE-2026-6092 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-6092 ] wolfSSL--wolfSSL Heap buffer overread=
    in wc_PKCS7_DecodeEnvelopedData when parsing crafted PKCS7 EnvelopedData. = This could theoretically be triggered by attacker-supplied data delivered v=
    ia S/MIME or CMS. 2026-06-25 not yet calculated CVE-2026-6094 [ https://www= .cve.org/CVERecord?id=3DCVE-2026-6094 ] wolfSSL--wolfSSL Bleichenbacher pad= ding oracle in PKCS#7 KTRI decryption. When decrypting PKCS#7 EnvelopedData=
    using RSA PKCS#1 v1.5 key transport, wolfSSL returned distinguishable erro=
    r codes depending on whether RSA padding validation failed versus whether t=
    he decrypted content was malformed. An attacker able to submit crafted Enve= lopedData messages and observe error responses could use this as a padding = oracle to incrementally recover the encrypted Content Encryption Key (CEK).=
    The fix generates a deterministic pseudo-random fake CEK on padding failur=
    e (via HMAC-SHA256) and proceeds with decryption identically, using constan= t-time operations throughout, so that all failure paths produce the same er= ror regardless of padding validity. 2026-06-25 not yet calculated CVE-2026-= 6291 [ https://www.cve.org/CVERecord?id=3DCVE-2026-6291 ] wolfSSL--wolfSSL = Out-of-bounds write in SetSuitesHashSigAlgo when processing an oversized si= gnature algorithms list, allowing a write past the bounds of the destinatio=
    n buffer. 2026-06-25 not yet calculated CVE-2026-6325 [ https://www.cve.org= /CVERecord?id=3DCVE-2026-6325 ] wolfSSL--wolfSSL PKCS#12 MAC verification u= ses an attacker-controlled comparison length, weakening the integrity check=
    on the MAC and allowing a mismatched MAC to be accepted. The PKCS#12 verif=
    y path compared the locally computed HMAC against the MAC parsed from the P= KCS#12 structure using a length taken directly from the attacker-supplied i= nput, without first verifying that it equals the length of the digest actua= lly produced by the configured algorithm. A truncated or zero-length stored=
    MAC could therefore be accepted, defeating the integrity protection of the=
    MAC. 2026-06-25 not yet calculated CVE-2026-6329 [ https://www.cve.org/CVE= Record?id=3DCVE-2026-6329 ] wolfSSL--wolfSSL The ML-KEM ARM64 NEON cipherte=
    xt comparison only compares half of the input, breaking the Fujisaki-Okamot=
    o transform's implicit rejection and weakening IND-CCA2 security on that co=
    de path. The constant-time comparison effectively ignored part of the re-en= crypted ciphertext, so a decapsulating party could fail to detect a manipul= ated ciphertext and proceed without the standard's required implicit reject= ion. 2026-06-25 not yet calculated CVE-2026-6330 [ https://www.cve.org/CVER= ecord?id=3DCVE-2026-6330 ] wolfSSL--wolfSSL HMAC zero-length tag forgery in=
    EVP_DigestVerifyFinal, where a zero-length tag could be accepted as valid = during HMAC verification. In the OpenSSL-compatibility HMAC verify path the=
    supplied signature length was only checked as not exceeding the MAC length=
    , so a zero-length or otherwise truncated tag could pass verification. The = fix requires the supplied tag length to exactly equal the MAC length and re= jects a zero-length MAC, so a forged short or empty tag is no longer accept= ed. 2026-06-25 not yet calculated CVE-2026-6331 [ https://www.cve.org/CVERe= cord?id=3DCVE-2026-6331 ] wolfSSL--wolfSSL Certificate policy and RFC 8446 = compliance concerns regarding the continued acceptance of SHA-1/MD5 in cert= ificate processing. 2026-06-25 not yet calculated CVE-2026-6412 [ https://w= ww.cve.org/CVERecord?id=3DCVE-2026-6412 ] wolfSSL--wolfSSL A CRL critical e= xtension bypass exists in ParseCRL_Extensions where critical extensions are=
    not properly enforced, allowing a crafted CRL with an unhandled critical e= xtension to be accepted. This only affects builds with CRL support enabled = and where a crafted CRL had a trusted signature when parsed. 2026-06-25 not=
    yet calculated CVE-2026-6450 [ https://www.cve.org/CVERecord?id=3DCVE-2026= -6450 ] wolfSSL--wolfSSL Integer underflow in wc_PKCS7_DecryptOri when hand= ling crafted Other Recipient Info, leading to incorrect length handling dur= ing decryption. 2026-06-25 not yet calculated CVE-2026-6678 [ https://www.c= ve.org/CVERecord?id=3DCVE-2026-6678 ] wolfSSL--wolfSSL A heap buffer overfl=
    ow could occur in the DTLS 1.3 ACK serialization path before the connecting=
    peer is authenticated. The buffer overflow was due to an integer truncatio=
    n when computing the length of the ACK record-number list, causing an under= sized buffer to be allocated and then overrun. This affects builds using DT=
    LS 1.3 and wolfSSL version 5.9.0 and earlier. A fix was added to the 5.9.1 = release. 2026-06-25 not yet calculated CVE-2026-6679 [ https://www.cve.org/= CVERecord?id=3DCVE-2026-6679 ] wolfSSL--wolfSSL The PKCS#7 decode path igno= res the caller-supplied output buffer size (outputSz), allowing decoded con= tent to be written past the bounds of the provided buffer. This affects wol= fSSL 5.9.0 and earlier and was fixed in the 5.9.1 release. 2026-06-25 not y=
    et calculated CVE-2026-6681 [ https://www.cve.org/CVERecord?id=3DCVE-2026-6= 681 ] wolfSSL--wolfSSL X.509 name constraint bypass via the Subject Common = Name when treated as a DNS-type name. A certificate whose Subject CN violat=
    es an issuing CA's DNS name constraints could be accepted. 2026-06-25 not y=
    et calculated CVE-2026-6731 [ https://www.cve.org/CVERecord?id=3DCVE-2026-6= 731 ] wolfSSL--wolfSSL PKCS7_verify signer confusion allows forged signatur= es, where the signer associated with a signature is not correctly bound, pe= rmitting a forged signature to be accepted. 2026-06-25 not yet calculated C= VE-2026-7511 [ https://www.cve.org/CVERecord?id=3DCVE-2026-7511 ] wolfSSL--= wolfSSL Use-after-free in PQC hybrid key-share handling. This is an incompl= ete-fix follow-up to CVE-2026-5460 (released in 5.9.1): a malicious TLS 1.3=
    server sending a truncated PQC hybrid KeyShare can still trigger the error=
    cleanup path to operate on freed memory. 2026-06-25 not yet calculated CVE= -2026-7531 [ https://www.cve.org/CVERecord?id=3DCVE-2026-7531 ] wolfSSL--wo= lfSSL iPAddress name constraints bypass when WOLFSSL_IP_ALT_NAME is not def= ined. IP address name constraints are not enforced in that configuration, a= llowing a certificate to bypass an issuing CA's IP address constraints. 202= 6-06-25 not yet calculated CVE-2026-7532 [ https://www.cve.org/CVERecord?id= =3DCVE-2026-7532 ] wolfSSL--wolfSSL wc_Blake2bHmacFinal and wc_Blake2sHmacF= inal discard the message when the key length exceeds the block size, produc= ing a MAC that is independent of the input. When the supplied key is longer=
    than the BLAKE2 block size the key-hashing branch reinitialized the runnin=
    g hash state, discarding the accumulated message data, so the resulting MAC=
    depended only on the key and not on the message being authenticated. This = bug is specific to the HMAC-BLAKE2 APIs that were added in wolfSSL version = 5.9.0. 2026-06-25 not yet calculated CVE-2026-8720 [ https://www.cve.org/CV= ERecord?id=3DCVE-2026-8720 ] Yokogawa Electric Corporation--FAST/TOOLS Over= view: A vulnerability has been found in FAST/TOOLS and CI Server. The web s= erver may return a response containing the CI Server setting information. T= his information could be exploited by an attacker for other attacks. The af= fected products and versions are as follows: FAST/TOOLS (Packages: RVSVRN, = UNSVRN, HMIWEB, FTEES, HMIMOB) R9.01 to R10.04 CI Server=C2=A0(All packages= )=C2=A0R1.01 to R1.04 2026-06-23 not yet calculated CVE-2026-11833 [ https:= //www.cve.org/CVERecord?id=3DCVE-2026-11833 ]=20

    Back to top [ #top ]

    body { font-size: 1em; font-family: Arial, Verdana, sans-serif; font-weight=
    : normal; font-style: normal; color: #333333; }=20

    Having trouble viewing this message?=C2=A0View it as a webpage [ https://co= ntent.govdelivery.com/accounts/USDHSCISA/bulletins/41e3aa5 ].=C2=A0 [ https= ://content.govdelivery.com/accounts/USDHS/bulletins/292141e ]

    You are subscribed to updates from the Cybersecurity and Infrastructure Sec= urity Agency [ https://www.cisa.gov ] (CISA)
    Manage Subscriptions [ https://public.govdelivery.com/accounts/USDHSCISA/su= bscriber/edit?preferences=3Dtrue#tab1 ]=C2=A0=C2=A0|=C2=A0=C2=A0Privacy Pol= icy [ https://www.cisa.gov/privacy-policy ]=C2=A0=C2=A0|=C2=A0 Help [ https= ://subscriberhelp.granicus.com/s/article/Subscriber-Help-Center ] [ https:/= /insights.govdelivery.com/Communications/Subscriber_Help_Center ]

    Connect with CISA:=20
    Facebook [ https://www.facebook.com/CISA ]=C2=A0 |=C2=A0 Twitter [ https://= twitter.com/CISAgov ]=C2=A0 |=C2=A0 Instagram [ https://Instagram.com/cisag=
    ov ]=C2=A0 |=C2=A0 LinkedIn [ https://www.linkedin.com/company/cybersecurit= y-and-infrastructure-security-agency ]=C2=A0 |=C2=A0=C2=A0 YouTube [ https:= //www.youtube.com/channel/UCxyq9roe-npgzrVwbpoAy0A ]

    ________________________________________________________________________

    This email was sent to cisa@toolazy.synchro.net using GovDelivery Communica= tions Cloud, on behalf of: Cybersecurity and Infrastructure Security Agency=
    =C2=B7 707 17th St, Suite 4000 =C2=B7 Denver, CO 80202 GovDelivery logo [ = https://subscriberhelp.granicus.com/ ]=20
    body .abe-column-block { min-height: 5px; } table.gd_combo_table img {margi= n-left:10px; margin-right:10px;} table.gd_combo_table div.govd_image_displa=
    y img, table.gd_combo_table td.gd_combo_image_cell img {margin-left:0px; ma= rgin-right:0px;}

    --===============4830605103477052940==
    Content-Type: text/html; charset="utf-8"
    MIME-Version: 1.0
    Content-Transfer-Encoding: quoted-printable

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns=3D"http://www.w3.org/1999/xhtml" xml:lang=3D"en" lang=3D"en"> <head>
    <title> Vulnerability Summary for the Week of June 22, 2026
    </title>


    </head>
    <body style=3D"">

    <table width=3D"700" border=3D"0" cellspacing=3D"0" cellpadding=3D"0"=
    align=3D"center">
    <tr>
    <td>

    <!--[if (gte mso 9)|(IE)]>
    <table style=3D"display:none"><tr><td><a name=3D"gd_top" id=3D"gd_top"></= a></td></tr></table>
    <![endif]-->
    <a name=3D"gd_top" id=3D"gd_top"></a>

    =20



    <p><img src=3D"https://content.govdelivery.com/attachments/fancy_images/U= SDHSCISA/2020/06/3486054/05152023-gov-delivery-banner-copy_original.png" al= t=3D"Cybersecurity and Infrastructure Security Agency (CISA)" title=3D"" wi= dth=3D"600" height=3D"100"></p>
    <p>You are subscribed to Vulnerability Bulletins for Cybersecurity and In= frastructure Security Agency. This information has recently been updated an=
    d is now available.</p>
    <p>The CISA Vulnerability Bulletin provides a summary of new vulnerabilitie=
    s that have been recorded in the past week. In some cases, the vulnerabilit= ies in the bulletin may not yet have assigned CVSS scores.</p> <p>Vulnerabilities are based on the=C2=A0<a href=3D"https://www.cve.org/" t= arget=3D"_blank" class=3D"ext" data-extlink=3D"" rel=3D"noopener">Common Vu= lnerabilities and Exposures</a>=C2=A0(CVE) vulnerability naming standard an=
    d are organized according to severity, determined by the=C2=A0<a href=3D"ht= tps://www.cve.org/about/relatedefforts" target=3D"_blank" rel=3D"noopener">= Common Vulnerability Scoring System</a>=C2=A0(CVSS) standard. The division =
    of high, medium, and low severities correspond to the following scores:</p>


    <strong>High</strong>: vulnerabilities with a CVSS base score of 7.0=E2=80= =9310.0</li>

    <strong>Medium</strong>: vulnerabilities with a CVSS base score of 4.0=E2= =80=936.9</li>

    <strong>Low</strong>: vulnerabilities with a CVSS base score of 0.0=E2=80= =933.9</li>
    </ul>
    <p>Entries may include additional information provided by organizations and=
    efforts sponsored by CISA. This information may include identifying inform= ation, values, definitions, and related links. Patch information is provide=
    d when available. Please note that some of the information in the bulletin =
    is compiled from external, open-source reports and is not a direct result o=
    f CISA analysis.</p>
    <p>=C2=A0</p>
    <div class=3D"rss_item" style=3D"margin-bottom: 2em;">
    <div class=3D"rss_title" style=3D"font-weight: bold; font-size: 120%; margi=
    n: 0 0 0.3em; padding: 0;"><a href=3D"https://www.cisa.gov/news-events/bull= etins/sb26-180">Vulnerability Summary for the Week of June 22, 2026</a></di=

    <div class=3D"rss_pub_date" style=3D"font-size: 90%; font-style: italic; co= lor: #666666; margin: 0 0 0.3em; padding: 0;">06/29/2026 2:30 PM EDT</div>

    <div class=3D"rss_description" style=3D"margin: 0 0 0.3em; padding: 0;">
    <div id=3D"high_v">
    <h2 id=3D"high_v_title">High Vulnerabilities</h2>
    <table class=3D"table no-tablesaw" style=3D"table-layout: fixed; width: 100= %;" border=3D"1" summary=3D"High Vulnerabilities">
    <thead>

    <th class=3D"vendor-product" style=3D"width: 24%;" scope=3D"col">
    <span class=3D"primary-vendor">Primary</span><br><span class=3D"primary-ven= dor">Vendor</span> -- Product</th>
    <th style=3D"width: 44%;" scope=3D"col">Description</th>
    <th style=3D"width: 10%;" scope=3D"col">Published</th>
    <th style=3D"width: 8%;" scope=3D"col">CVSS Score</th>
    <th style=3D"width: 7%;" scope=3D"col">Source Info</th>
    </tr>
    </thead>
    <tbody>

    <td class=3D"vendor-product">abhisheksaha11--URL Preview</td>
    <td>The URL Preview plugin for WordPress is vulnerable to Server-Side Reque=
    st Forgery in all versions up to, and including, 1.0 via the 'url' paramete=
    r. This makes it possible for unauthenticated attackers to make web request=
    s to arbitrary locations originating from the web application and can be us=
    ed to query and modify information from internal services.</td> <td>2026-06-24</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12100" target=3D= "_blank" rel=3D"noopener">CVE-2026-12100</a></td>
    </tr>

    <td class=3D"vendor-product">adegans--AdRotate Banner Manager</td>
    <td>The AdRotate Banner Manager plugin for WordPress is vulnerable to PHP C= ode Injection in all versions up to, and including, 5.17.7 via the 'banner'=
    attribute of the adrotate shortcode. This is due to insufficient input val= idation and sanitization of the banner shortcode attribute before concatena= tion into a PHP code string wrapped in W3 Total Cache mfunc or Borlabs Cach=
    e fragment markers. This makes it possible for authenticated attackers, wit=
    h Contributor-level access and above, to execute arbitrary PHP code on the = server. This vulnerability requires W3 Total Cache or Borlabs Cache support=
    to be enabled in AdRotate settings.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12242" target=3D= "_blank" rel=3D"noopener">CVE-2026-12242</a></td>
    </tr>

    <td class=3D"vendor-product">Adenion--Blog2Social</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in Blog2Social &lt;=3D 8.9.2=
    versions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56044" target=3D= "_blank" rel=3D"noopener">CVE-2026-56044</a></td>
    </tr>

    <td class=3D"vendor-product">Adobe--Acrobat Reader</td>
    <td>Acrobat Reader versions 2020.009.20074, 2020.001.30002, 2017.011.30171,=
    2015.006.30523 and earlier are affected by an out-of-bounds write vulnerab= ility that could result in arbitrary code execution in the context of the c= urrent user. Exploitation of this issue requires user interaction in that a=
    victim must open a malicious file.</td>
    <td>2026-06-23</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2020-9695" target=3D"= _blank" rel=3D"noopener">CVE-2020-9695</a></td>
    </tr>

    <td class=3D"vendor-product">Adrian Tobey--Groundhogg</td>
    <td>Sales Representative SQL Injection in Groundhogg &lt;=3D 4.5 versions.<=

    <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57667" target=3D= "_blank" rel=3D"noopener">CVE-2026-57667</a></td>
    </tr>

    <td class=3D"vendor-product">Ads WPQuads--Ads by WPQuads</td> <td>Unauthenticated Sensitive Data Exposure in Ads by WPQuads &lt;=3D 3.0.3=
    versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54824" target=3D= "_blank" rel=3D"noopener">CVE-2026-54824</a></td>
    </tr>

    <td class=3D"vendor-product">AF themes--WP Post Author</td>
    <td>Contributor SQL Injection in WP Post Author &lt;=3D 3.9.1 versions.</td=

    <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57643" target=3D= "_blank" rel=3D"noopener">CVE-2026-57643</a></td>
    </tr>

    <td class=3D"vendor-product">Ahmad--JS Help Desk</td>
    <td>Subscriber Arbitrary File Deletion in JS Help Desk &lt;=3D 3.1.1 versio= ns.</td>
    <td>2026-06-25</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56054" target=3D= "_blank" rel=3D"noopener">CVE-2026-56054</a></td>
    </tr>

    <td class=3D"vendor-product">AKIN Software Computer Import Export Industry = and Trade Ltd.--CafePlus</td>
    <td>Missing authentication for critical function vulnerability in AKIN Soft= ware Computer Import Export Industry and Trade Ltd. CafePlus allows Accessi=
    ng Functionality Not Properly Constrained by ACLs. This issue affects CafeP= lus: from 12.05.03 before 12.05.04.</td>
    <td>2026-06-23</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10711" target=3D= "_blank" rel=3D"noopener">CVE-2026-10711</a></td>
    </tr>

    <td class=3D"vendor-product">akosglys--Syncee Premium Dropshipping &amp; Wh= olesale</td>
    <td>Unauthenticated Broken Access Control in Syncee Premium Dropshipping &a= mp;amp; Wholesale &lt;=3D 1.0.27 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54846" target=3D= "_blank" rel=3D"noopener">CVE-2026-54846</a></td>
    </tr>

    <td class=3D"vendor-product">Algolplus--Advanced Order Export For WooCommer= ce</td>
    <td>Customer Cross Site Scripting (XSS) in Advanced Order Export For WooCom= merce &lt;=3D 4.0.9 versions.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56042" target=3D= "_blank" rel=3D"noopener">CVE-2026-56042</a></td>
    </tr>

    <td class=3D"vendor-product">Amazon Web Services--Language Servers for AWS<=

    <td>Improper trust boundary enforcement in Language Servers for AWS before = version 1.65.0 on all supported platforms may allow a for arbitrary code ex= ecution. If a local user opens a maliciously crafted workspace, any command=
    s within the project configuration files may be automatically executed. Thi=
    s issue requires the user to trust the workspace when prompted. To remediat=
    e this issue, users should upgrade to Language Servers for AWS version 1.65=
    .0 or higher.</td>
    <td>2026-06-23</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12957" target=3D= "_blank" rel=3D"noopener">CVE-2026-12957</a></td>
    </tr>

    <td class=3D"vendor-product">Amazon Web Services--Language Servers for AWS<=

    <td>Missing symlink validation in Language Servers for AWS may allow an arb= itrary file write outside of the workspace trust boundary. This may occur w= hen a local user opens a workspace with a maliciously crafted symlink that = resolves to a file path outside the workspace trust boundary. To remediate = this issue, users should upgrade to version 1.69.0 or higher.</td> <td>2026-06-23</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12958" target=3D= "_blank" rel=3D"noopener">CVE-2026-12958</a></td>
    </tr>

    <td class=3D"vendor-product">Anthropic--Claude Desktop Cowork</td> <td>Anthropic Claude Desktop Cowork VM image handling (confirmed across v1.= 1348.0 through v1.2278.0, including v1.1348.0, v1.1617.0, and v1.2278.0) va= lidates only file presence and a version marker string before booting rootf= s.img, but does not verify image content integrity at time-of-use. A local = attacker with unprivileged code execution as the victim macOS user can modi=
    fy the VM root filesystem image and have it trusted on subsequent Cowork VM=
    boots, enabling persistent arbitrary code execution in the VM and access t=
    o host-mounted directories. The estimated CWE mapping is CWE-353 (Missing S= upport for Integrity Check).</td>
    <td>2026-06-23</td>
    <td>8.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7574" target=3D"= _blank" rel=3D"noopener">CVE-2026-7574</a></td>
    </tr>

    <td class=3D"vendor-product">antlr--ANTLR4</td>
    <td>A weakness has been identified in antlr ANTLR4 up to 4.13.2. Affected i=
    s an unknown function of the file tool/src/org/antlr/v4/codegen/model/Outpu= tFile.java of the component Grammar Action Block Handler. Executing a manip= ulation can lead to code injection. The attack may be launched remotely. Th=
    e exploit has been made available to the public and could be used for attac= ks. The vendor was contacted early about this disclosure but did not respon=
    d in any way.</td>
    <td>2026-06-28</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13500" target=3D= "_blank" rel=3D"noopener">CVE-2026-13500</a></td>
    </tr>

    <td class=3D"vendor-product">Appsbd--Vitepos</td>
    <td>Unauthenticated Sensitive Data Exposure in Vitepos &lt;=3D 3.4.2 versio= ns.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54841" target=3D= "_blank" rel=3D"noopener">CVE-2026-54841</a></td>
    </tr>

    <td class=3D"vendor-product">appsmithorg--appsmith</td>
    <td>Appsmith is a platform to build admin panels, internal tools, and dashb= oards. Prior to 2.1, the bundled Caddy reverse-proxy's admin API - which ha=
    s no authentication by default - is bound on 0.0.0.0:2019 inside the contai= ner. While this listener is not directly published to the host by docker-co= mpose.yml, it is reachable from the Appsmith server process itself or a SSR=
    F vulnerability. An authenticated low-privileged user can therefore drive t=
    he SSRF to issue POST /load (or any other admin-API call) against http://0.= 0.0.0:2019/, fully replacing the live Caddy configuration and taking over t=
    he reverse proxy. This vulnerability is fixed in 2.1.</td>
    <td>2026-06-24</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55454" target=3D= "_blank" rel=3D"noopener">CVE-2026-55454</a></td>
    </tr>

    <td class=3D"vendor-product">ARforms--ARforms</td>
    <td>The ARForms plugin for WordPress is vulnerable to Stored Cross-Site Scr= ipting via the `value` parameter of the `arf_save_incomplete_form_data` AJA=
    X action in all versions up to, and including, 7.1.3 due to insufficient in= put sanitization and output escaping. This makes it possible for unauthenti= cated attackers to inject arbitrary web scripts that will execute whenever =
    an administrator views the "Partial Filled Form Entries" page in the ARForm=
    s dashboard.</td>
    <td>2026-06-24</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-3652" target=3D"= _blank" rel=3D"noopener">CVE-2026-3652</a></td>
    </tr>

    <td class=3D"vendor-product">Autodesk--Fusion</td>
    <td>A maliciously crafted webpage, when visited by a user with Autodesk Fus= ion Desktop running and the MCP extension enabled, can trigger a vulnerabil= ity in the MCP extension that could allow arbitrary code execution. A succe= ssful exploit may allow code to execute with the privileges of the current = user.</td>
    <td>2026-06-22</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10789" target=3D= "_blank" rel=3D"noopener">CVE-2026-10789</a></td>
    </tr>

    <td class=3D"vendor-product">Averta--Master Slider</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in Master Slider &lt;=3D 3.1= 1.2 versions.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56014" target=3D= "_blank" rel=3D"noopener">CVE-2026-56014</a></td>
    </tr>

    <td class=3D"vendor-product">Ays Pro--Popup box</td>
    <td>Administrator SQL Injection in Popup box &lt;=3D 6.0.1 versions.</td> <td>2026-06-26</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57631" target=3D= "_blank" rel=3D"noopener">CVE-2026-57631</a></td>
    </tr>

    <td class=3D"vendor-product">bestwebsoft--Gallery</td>
    <td>Contributor SQL Injection in Gallery &lt;=3D 4.7.8 versions.</td> <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57642" target=3D= "_blank" rel=3D"noopener">CVE-2026-57642</a></td>
    </tr>

    <td class=3D"vendor-product">bitwarden--server</td>
    <td>Bitwarden Server before 2026.5.0 contains a privilege escalation vulner= ability that allows authenticated Custom users with ManageUsers permission =
    to remove Admin accounts from an organization by exploiting a missing role = hierarchy check in the bulk user-remove endpoint. Attackers can supply Admi=
    n organization-user IDs in a bulk DELETE request to bypass the guard enforc=
    ed on the single-user removal path, effectively removing one or more Admin = accounts from an organization.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57520" target=3D= "_blank" rel=3D"noopener">CVE-2026-57520</a></td>
    </tr>

    <td class=3D"vendor-product">Bootstrapped Ventures--Visual Link Preview</td=

    <td>Subscriber Sensitive Data Exposure in Visual Link Preview &lt;=3D 2.3.1=
    versions.</td>
    <td>2026-06-25</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54821" target=3D= "_blank" rel=3D"noopener">CVE-2026-54821</a></td>
    </tr>

    <td class=3D"vendor-product">bPlugins--MailChimp Block</td>
    <td>Unauthenticated Broken Access Control in MailChimp Block &lt;=3D 1.1.15=
    versions.</td>
    <td>2026-06-26</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56063" target=3D= "_blank" rel=3D"noopener">CVE-2026-56063</a></td>
    </tr>

    <td class=3D"vendor-product">bPlugins--Panorama Viewer 360 Degree Image + V= ideo Viewer</td>
    <td>Contributor Local File Inclusion in Panorama Viewer - 360 Degree Image =
    + Video Viewer &lt;=3D 1.6.1 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57647" target=3D= "_blank" rel=3D"noopener">CVE-2026-57647</a></td>
    </tr>

    <td class=3D"vendor-product">BuddyBoss--Buddyboss Platform</td>
    <td>Subscriber PHP Object Injection in Buddyboss Platform &lt;=3D 3.0.4 ver= sions.</td>
    <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56032" target=3D= "_blank" rel=3D"noopener">CVE-2026-56032</a></td>
    </tr>

    <td class=3D"vendor-product">Budibase--budibase</td>
    <td>Budibase is an open-source low-code platform. Prior to 3.39.12, an unau= thenticated visitor of any published Budibase app reads every document of t=
    he backing MongoDB, CouchDB, Elasticsearch, DynamoDB-PartiQL, or REST-with-= JSON-body collection and, where the builder has published a PUBLIC write qu= ery, modifies every document of that collection with one HTTP request. enri= chContext at packages/server/src/sdk/workspace/queries/queries.ts:121-138 s= ubstitutes parameter values into the raw JSON body of a query, then JSON.pa= rses the result. The validator validateQueryInputs at packages/server/src/a= pi/controllers/query/index.ts:61-71 rejects only Handlebars markers ({{, }}=
    ) in user input and does not escape JSON metacharacters (", \, }). A parame= ter value containing a closing quote and additional keys lifts attacker-con= trolled fields into the parsed filter object. For Mongo find, the parsed fi= lter passes directly to collection.find() (packages/server/src/integrations= /mongodb.ts:506-510). Duplicate-key JSON parsing overrides the builder's {n= ame: "..."} with {name: {$exists: true}} and returns every document. The sa=
    me primitive against an updateMany query (mongodb.ts:577-585) widens the fi= lter scope to the full collection while the builder-controlled $set body ru=
    ns against every matched document. The authorized middleware at packages/se= rver/src/middleware/authorized.ts:141-148 short-circuits when the query's r= ole is PUBLIC. CSRF is not enforced on this path. POST /api/v2/queries/:que= ryId (packages/server/src/api/routes/query.ts:63) accepts the call with no = session, only an x-budibase-app-id header that is public from the published= -app URL. This vulnerability is fixed in 3.39.12.</td>
    <td>2026-06-26</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54350" target=3D= "_blank" rel=3D"noopener">CVE-2026-54350</a></td>
    </tr>

    <td class=3D"vendor-product">Budibase--budibase</td>
    <td>Budibase is an open-source low-code platform. Prior to 3.39.9, `POST /a= pi/pwa/process-zip` at packages/server/src/api/routes/static.ts:24 accepts =
    a builder-uploaded .zip, extracts it with extract-zip@2.0.1 into a temp dir= ectory, then for each entry listed in icons.json validates the icon path, o= pens it, and streams the bytes into MinIO. The resulting object is served b= ack via GET /api/assets/{appId}/pwa/{uuid}.png. extract-zip@2.0.1 preserves=
    absolute symlink targets when restoring symlink entries. The icon-source v= alidator at packages/server/src/api/controllers/static/index.ts:259-268 res= olves the icon source string against baseDir (path.resolve), checks resolve= dSrc.startsWith(baseDir + path.sep) against that string, and calls fs.exist= sSync(resolvedSrc) which follows symbolic links to confirm the target exist=
    s. None of the three calls reject symbolic-link entries. packages/backend-c= ore/src/objectStore/objectStore.ts:302 then calls (await fsp.open(path)).cr= eateReadStream() on the resolved path. fsp.open follows the symlink, the ta= rget file's bytes stream into MinIO, and the response of the asset-fetch en= dpoint returns those bytes verbatim. Result: a workspace-level builder read=
    s any file the server process can open. This vulnerability is fixed in 3.39= .9.</td>
    <td>2026-06-26</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54352" target=3D= "_blank" rel=3D"noopener">CVE-2026-54352</a></td>
    </tr>

    <td class=3D"vendor-product">Budibase--budibase</td>
    <td>Budibase is an open-source low-code platform. Prior to 3.39.9, the webh= ook trigger endpoint in Budibase is publicly accessible and passes the full=
    HTTP request body into automation execution parameters. A mass assignment = vulnerability in externalTrigger() allows an attacker to overwrite the inte= rnal appId property by including it in the webhook POST body. When the auto= mation is processed asynchronously (the default path for webhooks without a=
    collect step), the worker executes the attacker-defined automation in the = context of the victim's workspace, granting full read/write access to the v= ictim's database. This vulnerability is fixed in 3.39.9.</td> <td>2026-06-26</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54351" target=3D= "_blank" rel=3D"noopener">CVE-2026-54351</a></td>
    </tr>

    <td class=3D"vendor-product">Budibase--budibase</td>
    <td>Budibase is an open-source low-code platform. Prior to 3.39.9, authenti= cated users with automation permissions can bypass Budibase's SSRF blacklis=
    t through DNS rebinding. The outbound fetch flow validates a hostname again=
    st the blacklist before the request is sent, but the actual socket connecti=
    on later performs a separate DNS lookup through node-fetch. Since the valid= ated IPs are never pinned to the connection, an attacker-controlled hostnam=
    e can return a public IP during validation and a private/internal IP during=
    the real connection. This results in a non-blind SSRF primitive against in= ternal services reachable from the Budibase host, including loopback, RFC19=
    18 ranges, and cloud metadata endpoints. This vulnerability is fixed in 3.3= 9.9.</td>
    <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54353" target=3D= "_blank" rel=3D"noopener">CVE-2026-54353</a></td>
    </tr>

    <td class=3D"vendor-product">Budibase--budibase</td>
    <td>Budibase is an open-source low-code platform. Prior to 3.39.0, `GET /ap= i/chat-links/:instance/:token/handoff` is a public endpoint (no auth requir= ed) that performs a permanent, state-changing operation: it binds an extern=
    al chat identity (Slack/Discord/MS Teams) to an authenticated Budibase user=
    account, with no consent UI and no CSRF protection. The session token in t=
    he URL is created by the attacker (from their own /link slash command) and = embeds the attacker's externalUserId. When an authenticated Budibase victim=
    visits the URL, their account is silently and permanently linked to the at= tacker's Slack/Discord identity. The server responds with "Authentication s= ucceeded." - no indication of what was linked. This vulnerability is fixed =
    in 3.39.0.</td>
    <td>2026-06-26</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50132" target=3D= "_blank" rel=3D"noopener">CVE-2026-50132</a></td>
    </tr>

    <td class=3D"vendor-product">Budibase--budibase</td>
    <td>Budibase is an open-source low-code platform. Prior to 3.39.3, the appl= ication server exposes an unauthenticated endpoint that generates S3 PutObj= ect presigned URLs using credentials stored in a workspace datasource. The = route is protected only by the recaptcha middleware and does not require au= thentication, table permission, datasource permission, or builder access. A=
    public caller who knows a workspace ID and S3 datasource ID can request a = signed upload URL for attacker-controlled bucket and key values. This vulne= rability is fixed in 3.39.3.</td>
    <td>2026-06-26</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50136" target=3D= "_blank" rel=3D"noopener">CVE-2026-50136</a></td>
    </tr>

    <td class=3D"vendor-product">bytuncay--Kargo Takip</td>
    <td>The Kargo Takip plugin for WordPress is vulnerable to Server-Side Reque=
    st Forgery in all versions up to, and including, 1.2 via the 'api_url' para= meter. This makes it possible for unauthenticated attackers to make web req= uests to arbitrary locations originating from the web application and can b=
    e used to query and modify information from internal services. The script e= choes internal API response data (specifically the value of any 'auth' key =
    in a JSON response body) verbatim back to the attacker's browser, enabling = direct exfiltration of responses from internal services such as cloud insta= nce metadata endpoints.</td>
    <td>2026-06-24</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12095" target=3D= "_blank" rel=3D"noopener">CVE-2026-12095</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. In = versions 1.2.30 and prior, the rfilter request variable was concatenated in=
    to a RLIKE SQL clause without sanitization. The endpoint does not require a= uthentication (graph viewing supports guest access via the configured guest=
    user), so the SQLi was reachable pre-auth on installs with guest viewing e= nabled. This issue was fixed in version 1.2.31.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39893" target=3D= "_blank" rel=3D"noopener">CVE-2026-39893</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior have unauthenticated LFI through graph_theme and rrd= tool IPC serialization hardening. This issue has been resolved in version 1= .2.31.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39938" target=3D= "_blank" rel=3D"noopener">CVE-2026-39938</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior have pre-authentication SQL Injection via unanchored=
    FILTER_VALIDATE_REGEXP in graph_view.php. This issue has been fixed in ver= sion 1.2.31.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39955" target=3D= "_blank" rel=3D"noopener">CVE-2026-39955</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior have a Stored SQL Injection vulnerability through gr= aph_name_regexp in the Reports feature. This issue has been fixed in versio=
    n 1.2.31.</td>
    <td>2026-06-24</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39951" target=3D= "_blank" rel=3D"noopener">CVE-2026-39951</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior have SQL Injection through unsanitized unserialize+i= mplode in managers.php. At line 756 of managers.php, the application assign=
    s $selected_items by calling cacti_unserialize(stripslashes(gnrv('selected_= graphs_array'))). The cacti_unserialize() function calls unserialize() with=
    allowed_classes set to false, which prevents object injection but still al= lows arbitrary string arrays to be deserialized. Then, at lines 760 to 766,=
    the deserialized array values are passed directly into db_execute('DELETE = FROM snmpagent_managers WHERE id IN (' . implode(',', $selected_items) . ')= '), where they are imploded into the SQL statement without any integer vali= dation, resulting in SQL Injection when using SNMP agent management permiss= ions. This issue has been fixed in version 1.2.31.</td>
    <td>2026-06-25</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40083" target=3D= "_blank" rel=3D"noopener">CVE-2026-40083</a></td>
    </tr>

    <td class=3D"vendor-product">caddyserver--caddy</td>
    <td>Caddy is an extensible server platform that uses TLS by default. From 2= .7.0 until 2.11.3, the FastCGI transport's splitPos() in modules/caddyhttp/= reverseproxy/fastcgi/fastcgi.go misuses golang.org/x/text/search with searc= h.IgnoreCase when the request path contains a non-ASCII byte. Two distinct = flaws in that fallback let an attacker mislead Caddy's FastCGI splitting in=
    to treating a non-.php (or other configured split_path extension) file as a=
    script. In any deployment where the attacker can place content into a file=
    served via FastCGI (uploads, file storage, etc.), this can be escalated to=
    remote code execution by crafting a URL whose path triggers either flaw. T= his vulnerability is fixed in 2.11.3.</td>
    <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45135" target=3D= "_blank" rel=3D"noopener">CVE-2026-45135</a></td>
    </tr>

    <td class=3D"vendor-product">caddyserver--caddy</td>
    <td>Caddy is an extensible server platform that uses TLS by default. Prior =
    to 2.11.4, forward_auth copy_headers deletes the exact client-supplied iden= tity header before copying the trusted value from the auth gateway. But whe=
    n the request later goes through php_fastcgi, Caddy normalizes HTTP headers=
    into CGI variables by replacing - with _. This lets a client send an under= score alias that survives the forward_auth delete step but becomes the same=
    PHP/FastCGI variable. Result: a remote client can inject or sometimes over= ride identity/group headers trusted by PHP/FastCGI applications behind Cadd=
    y. This vulnerability is fixed in 2.11.4.</td>
    <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52845" target=3D= "_blank" rel=3D"noopener">CVE-2026-52845</a></td>
    </tr>

    <td class=3D"vendor-product">caddyserver--caddy</td>
    <td>Caddy is an extensible server platform that uses TLS by default. Prior =
    to 2.11.4, on Windows, Caddy path matchers treat /private\secret.txt as out= side /private/*, but file_server later resolves the same request path as pr= ivate\secret.txt on disk. An unauthenticated remote client can bypass Caddy=
    path-scoped auth/deny routes protecting /private/*. This vulnerability is = fixed in 2.11.4.</td>
    <td>2026-06-23</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52844" target=3D= "_blank" rel=3D"noopener">CVE-2026-52844</a></td>
    </tr>

    <td class=3D"vendor-product">canboat--canboat</td>
    <td>CANBoat through 6.22, fixed in commit a5a22b7, contains an off-by-one g= lobal buffer overflow in the searchForPgn() function in analyzer/pgn.c that=
    allows remote attackers to crash the application. Attackers can deliver a = crafted NMEA-2000 message with an out-of-range PGN value over CAN bus or N2= K-over-IP to trigger an out-of-bounds array access and denial of service.</=

    <td>2026-06-25</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56790" target=3D= "_blank" rel=3D"noopener">CVE-2026-56790</a></td>
    </tr>

    <td class=3D"vendor-product">Canonical--LXD</td>
    <td>A privilege escalation vulnerability exists in LXD from 6.0 before 6.9,=
    5.21.0 before 5.21.5, and 5.0.0 before 5.0.7 regarding the handling of pro= ject-restriction policies during snapshot restoration.. An authenticated pr= oject operator in a restricted multi-tenant environment can bypass policy r= estrictions by importing a maliciously crafted instance backup containing r= estricted configuration keys within a snapshot. When the snapshot is restor= ed, these restricted keys are applied to the live instance without policy v= alidation. Starting the modified instance grants the operator unauthorized = host root access.</td>
    <td>2026-06-26</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9640" target=3D"= _blank" rel=3D"noopener">CVE-2026-9640</a></td>
    </tr>

    <td class=3D"vendor-product">Canonical--lxd</td>
    <td>Broken Access Control in the devLXDInstancePatchHandler component of Ca= nonical LXD allows an untrusted guest to mount, read, and overwrite another=
    guest's custom storage volume via a crafted device PATCH request over /dev= /lxd when security.devlxd.management.volumes is enabled.</td> <td>2026-06-26</td>
    <td>8.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12411" target=3D= "_blank" rel=3D"noopener">CVE-2026-12411</a></td>
    </tr>

    <td class=3D"vendor-product">Cap-go--capgo</td>
    <td>Supabase Capgo before 12.128.2 contains an authorization bypass vulnera= bility in the SECURITY DEFINER record_build_time RPC function that allows u= nauthenticated attackers to insert arbitrary build-time records. Attackers = can exploit this by calling POST /rest/v1/rpc/record_build_time with a publ=
    ic API key to poison billing and quota data for any organization, enabling = resource exhaustion and cross-tenant billing manipulation.</td> <td>2026-06-24</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56245" target=3D= "_blank" rel=3D"noopener">CVE-2026-56245</a></td>
    </tr>

    <td class=3D"vendor-product">Cap-go--capgo</td>
    <td>Cap-go capgo (capgo-backend) before 12.128.12 contains an unauthenticat=
    ed denial-of-service vulnerability arising from the audit_logs table's Row-= Level Security (RLS) policy when accessed via the Supabase PostgREST API. B= ecause the PostgreSQL query planner executes costly logic before RLS reject= ion, unfiltered queries to the public.audit_logs endpoint using the public = anon key consistently trigger statement timeouts (PostgREST error 57014). U= nder concurrency, this exhausts database resources and causes cascading HTT=
    P 500 failures on unrelated endpoints (e.g. /orgs), resulting in an applica= tion-layer denial of service.</td>
    <td>2026-06-23</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56248" target=3D= "_blank" rel=3D"noopener">CVE-2026-56248</a></td>
    </tr>

    <td class=3D"vendor-product">Cap-go--capgo</td>
    <td>Cap-go before 12.128.2 contains a privilege inversion vulnerability in = GET /build/logs/:jobId that allows read-only API key holders to cancel runn= ing native builds. The endpoint registers an abort listener on the SSE stre=
    am that unconditionally invokes cancelBuildOnDisconnect() using the privile= ged server-side BUILDER_API_KEY when clients disconnect, bypassing the app.= build_native permission check required by the explicit POST /build/cancel/:= jobId endpoint. Attackers with read-only API keys can repeatedly disrupt na= tive build operations and CI/CD workflows by opening the log stream and dro= pping the connection.</td>
    <td>2026-06-22</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56280" target=3D= "_blank" rel=3D"noopener">CVE-2026-56280</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains a broken authentication vulnerability in=
    its API key generation mechanism. API keys are exposed in frontend request=
    s, and the backend fails to validate that keys are securely generated and b= ound to the authenticated user. An attacker can tamper with the API key par= ameter in the generation request and supply arbitrary values, generating cu= stom API keys without proper authorization, which can lead to unauthorized = access to protected endpoints.</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56237" target=3D= "_blank" rel=3D"noopener">CVE-2026-56237</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains a cross-domain SSO account takeover vuln= erability in the provision-user endpoint that allows attackers to merge arb= itrary victim accounts based on email match without validating SSO provider=
    domain authorization. An attacker with enterprise org admin access and a m= alicious IdP can forge SAML assertions containing victim email addresses to=
    trigger account merge and gain full access to victim accounts, organizatio= ns, and data.</td>
    <td>2026-06-24</td>
    <td>8.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56223" target=3D= "_blank" rel=3D"noopener">CVE-2026-56223</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains an authorization bypass vulnerability in=
    its public API key management handlers (get/put/delete/post). API keys cre= ated with mode=3Dall but restricted to a single app via limited_to_apps are=
    only checked for limited_to_orgs and not for limited_to_apps, so an app-sc= oped key can enumerate, update, and delete sibling API keys belonging to th=
    e same account that are outside its declared app scope, enabling tampering = with account-level credentials.</td>
    <td>2026-06-23</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56225" target=3D= "_blank" rel=3D"noopener">CVE-2026-56225</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 fails to enforce limited_to_orgs and limited_to_a= pps constraints on subkeys provided via x-limited-key-id header in middlewa= reKey function. Attackers can bypass subkey scope restrictions by referenci=
    ng their own subkeys, causing all downstream route handlers to use the unre= stricted parent key instead of the scoped subkey.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56232" target=3D= "_blank" rel=3D"noopener">CVE-2026-56232</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains a security control bypass vulnerability = where the PostgREST/RLS plane accepts plaintext API keys through the capgke=
    y header despite enforce_hashed_api_keys being enabled. Attackers can bypas=
    s org-level hashed-key enforcement by sending plaintext API keys directly t=
    o the PostgREST/RLS plane to access protected resources.</td> <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56243" target=3D= "_blank" rel=3D"noopener">CVE-2026-56243</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains a rate limit bypass vulnerability in the=
    channel_self endpoint that allows attackers to circumvent rate limiting by=
    rotating the user-controlled device_id parameter. Attackers can send multi= ple requests per second by changing device_id values to flood the channel_d= evices table and cause database exhaustion.</td>
    <td>2026-06-22</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56324" target=3D= "_blank" rel=3D"noopener">CVE-2026-56324</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains an authorization bypass vulnerability in=
    POST /private/role_bindings that fails to verify app_id ownership during a= pp-scoped role binding creation. An attacker with administrative privileges=
    in one organization can create role bindings targeting applications owned =
    by other organizations, enabling unauthorized read and modification of vict=
    im applications.</td>
    <td>2026-06-23</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56222" target=3D= "_blank" rel=3D"noopener">CVE-2026-56222</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains a broken object level authorization (BOL=
    A) vulnerability in the POST /build/start/:jobId and POST /build/cancel/:jo= bId endpoints. The handlers authorize the request based only on the attacke= r-controlled app_id supplied in the request body and never verify that the = jobId in the URL belongs to that app_id (or the same tenant/org) before iss= uing privileged builder commands with the server-held builder API key. An a= uthenticated user with the app.build_native permission for any app they con= trol can start or cancel arbitrary builder jobs belonging to other tenants =
    by supplying a victim jobId, resulting in cross-tenant build sabotage (deni=
    al of service), unauthorized compute actions, and potential billing impact.= </td>
    <td>2026-06-24</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56231" target=3D= "_blank" rel=3D"noopener">CVE-2026-56231</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 allows non-admin API keys to read webhook signing=
    secrets via Supabase REST due to insufficient row-level security policies =
    on the webhooks table. Attackers can retrieve the webhook secret and forge = valid X-Capgo-Signature headers to send authenticated webhook events to con= figured receivers, breaking webhook authenticity and integrity.</td> <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56244" target=3D= "_blank" rel=3D"noopener">CVE-2026-56244</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 enforces mandatory two-factor authentication only=
    at the UI level. Sensitive Organization (ORG) management API endpoints (e.= g., editing organization details, inviting users) do not validate 2FA compl= etion on the backend. An authenticated Admin user who has not enabled 2FA c=
    an replay or modify a previously captured ORG API request to perform privil= eged organization actions, bypassing the globally enforced 2FA requirement.= </td>
    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56256" target=3D= "_blank" rel=3D"noopener">CVE-2026-56256</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 allows direct patching of public.apps.owner_org t= hrough PostgREST, bypassing the transfer_app() workflow and creating split-= brain ownership. Attackers can directly update apps.owner_org while leaving=
    app_versions.owner_org unchanged, enabling old-org keys to retain access t=
    o version data while new-org keys control the app record.</td> <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56257" target=3D= "_blank" rel=3D"noopener">CVE-2026-56257</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.12 fails to filter deleted app versions when joinin=
    g channels during /updates resolution, allowing deleted bundles to remain s= electable. Attackers can continue deploying deleted bundles to devices by e= xploiting the missing app_versions.deleted filter in channel version joins.= </td>
    <td>2026-06-22</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56314" target=3D= "_blank" rel=3D"noopener">CVE-2026-56314</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains an information disclosure vulnerability =
    in the unauthenticated /updates endpoint that resolves the defaultChannel p= arameter before enforcing privacy restrictions, allowing attackers to enume= rate private channels and leak version/config state. Unauthenticated attack= ers can probe private channel names and distinguish valid channels from non= existent ones based on response differences, revealing assigned bundle vers= ions and platform-specific configuration details.</td>
    <td>2026-06-23</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56322" target=3D= "_blank" rel=3D"noopener">CVE-2026-56322</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains an information disclosure vulnerability =
    in the /functions/v1/channel_self endpoint that allows unauthenticated atta= ckers to enumerate non-public channel names and determine app existence and=
    subscription status. Remote attackers can send GET requests with arbitrary=
    app_id parameters to disclose internal rollout channels, enumerate valid a= pplications across tenants, and leak billing status without authentication =
    or device binding.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56323" target=3D= "_blank" rel=3D"noopener">CVE-2026-56323</a></td>
    </tr>

    <td class=3D"vendor-product">cgarvey--Email JavaScript Cloak</td>
    <td>The Email JavaScript Cloak plugin for WordPress is vulnerable to Stored=
    Cross-Site Scripting via the plugin's 'email' shortcode in all versions up=
    to, and including, 1.03 due to insufficient input sanitization and output = escaping on user supplied attributes. This makes it possible for authentica= ted attackers, with contributor-level access and above, to inject arbitrary=
    web scripts in pages that will execute whenever a user accesses an injecte=
    d page.</td>
    <td>2026-06-24</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10091" target=3D= "_blank" rel=3D"noopener">CVE-2026-10091</a></td>
    </tr>

    <td class=3D"vendor-product">Chainlit--chainlit</td>
    <td>Chainlit before 2.10.1 contains a session hijacking vulnerability that = allows unauthenticated attackers to restore and inherit authenticated user = sessions by presenting a valid sessionId during WebSocket session restorati=
    on without ownership verification. Attackers can exploit the restore_existi= ng_session path to assume a victim's permissions and roles, enabling unauth= orized invocation of tools and access to data restricted to the authenticat=
    ed victim.</td>
    <td>2026-06-22</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56104" target=3D= "_blank" rel=3D"noopener">CVE-2026-56104</a></td>
    </tr>

    <td class=3D"vendor-product">CheckView--CheckView Automated Testing</td> <td>Unauthenticated Broken Access Control in CheckView Automated Testing &l= t;=3D 2.1.0 versions.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54844" target=3D= "_blank" rel=3D"noopener">CVE-2026-54844</a></td>
    </tr>

    <td class=3D"vendor-product">chimurai--http-proxy-middleware</td> <td>http-proxy-middleware is node.js http-proxy middleware. From 3.0.4 unti=
    l 3.0.7 and 4.1.1, fixRequestBody() is the library's documented helper for = re-emitting a request body that was already consumed by a body parser. When=
    the outgoing Content-Type is multipart/form-data, it rebuilds the body wit=
    h handlerFormDataBodyData(), which interpolates each req.body key and value=
    directly into the multipart wire format without neutralizing CR/LF. A \r\n=
    inside a value (or key) lets an attacker close the current part and inject=
    an entirely new form part. Because the proxy's own body parser saw a singl=
    e opaque value, any gateway-side policy or validation performed on req.body=
    is evaluated against a different set of fields than the upstream backend u= ltimately parses a request/parameter desynchronization across the trust bou= ndary. This vulnerability is fixed in 3.0.7 and 4.1.1.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55603" target=3D= "_blank" rel=3D"noopener">CVE-2026-55603</a></td>
    </tr>

    <td class=3D"vendor-product">chrisvrichardson--MapPress Maps for WordPress<=

    <td>Unauthenticated Cross Site Scripting (XSS) in MapPress Maps for WordPre=
    ss &lt;=3D 2.97.3 versions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56011" target=3D= "_blank" rel=3D"noopener">CVE-2026-56011</a></td>
    </tr>

    <td class=3D"vendor-product">clearsale--ClearSale Total</td>
    <td>The ClearSale Total plugin for WordPress is vulnerable to SQL Injection=
    via the `pagseguro[metodo]` POST parameter of the `clearsale_total_push` A= JAX action in all versions up to, and including, 3.4.2. The handler is regi= stered for unauthenticated users (`wp_ajax_nopriv_clearsale_total_push`), a=
    nd although a `wp_verify_nonce()` check exists, the failing branch's `die()=
    ` is commented out so execution continues regardless of nonce validity. On = PHP &lt; 8.0 the attacker-supplied `$metodo` value bypasses the `switch ($m= etodo) { case 4: ... }` guard via loose type juggling (the string `"4 AND S= LEEP(5)"` compares equal to integer `4`), reaching an unquoted `UPDATE wp_c= s_total_dadosextras SET metodo=3D$metodo, ...` query. This makes it possibl=
    e for unauthenticated attackers to append additional SQL queries into alrea=
    dy existing queries that can be used to extract sensitive information from = the database. Exploitation requires the target server to be running PHP &lt=
    ; 8.0.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8705" target=3D"= _blank" rel=3D"noopener">CVE-2026-8705</a></td>
    </tr>

    <td class=3D"vendor-product">codemstory--</td>
    <td>Unauthenticated SQL Injection in =C3=AC=E2=80=BA=C5=92=C3=AB=E2=80=9C= =C5=93=C3=AD=E2=80=9D=E2=80=9E=C3=AB=C2=A0=CB=86=C3=AC=C5=A0=C2=A4 =C3=AA= =C2=B2=C2=B0=C3=AC=C2=A0=C5=93 =C3=AC=E2=80=B9=C2=AC=C3=AD=E2=80=9D=C5=92= =C3=AD=C5=BD=CB=9C=C3=AC=C2=9D=C2=B4 &lt;=3D 5.5.6 versions.</td> <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56036" target=3D= "_blank" rel=3D"noopener">CVE-2026-56036</a></td>
    </tr>

    <td class=3D"vendor-product">contempoinc--Real Estate 7</td> <td>Unauthenticated SQL Injection in Real Estate 7 &lt;=3D 3.5.9 versions.<=

    <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54827" target=3D= "_blank" rel=3D"noopener">CVE-2026-54827</a></td>
    </tr>

    <td class=3D"vendor-product">corvuspay--CorvusPay WooCommerce Payment Gatew= ay</td>
    <td>Unauthenticated Broken Authentication in CorvusPay WooCommerce Payment = Gateway &lt;=3D 2.7.4 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56029" target=3D= "_blank" rel=3D"noopener">CVE-2026-56029</a></td>
    </tr>

    <td class=3D"vendor-product">Cory Marsh--BitFire Security</td> <td>Unauthenticated Multiple Vulnerabilities in BitFire Security &lt;=3D 5.= 0.3 versions.</td>
    <td>2026-06-26</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56035" target=3D= "_blank" rel=3D"noopener">CVE-2026-56035</a></td>
    </tr>

    <td class=3D"vendor-product">Crawl4AI--Crawl4AI</td>
    <td>Crawl4AI before 0.8.8 contains an arbitrary file write vulnerability in=
    the screenshot and PDF endpoints that allows unauthenticated attackers to = write files outside the intended directory via symlink and time-of-check-ti= me-of-use (TOCTOU) attacks on the output_path parameter. Remote attackers c=
    an exploit insufficient path validation and symlink following to achieve ar= bitrary file write and potential code execution on systems where the runtim=
    e user has write access to executable or cron locations.</td> <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56258" target=3D= "_blank" rel=3D"noopener">CVE-2026-56258</a></td>
    </tr>

    <td class=3D"vendor-product">Crawl4AI--Crawl4AI</td>
    <td>Crawl4AI before 0.8.7 contains a server-side request forgery vulnerabil= ity in the /crawl, /crawl/stream, /md, and /llm endpoints that fetch arbitr= ary user-supplied URLs without validation. Unauthenticated attackers can by= pass the internal-address blocklist using IPv6-mapped IPv4 addresses to rea=
    ch internal services and cloud metadata endpoints.</td>
    <td>2026-06-22</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56266" target=3D= "_blank" rel=3D"noopener">CVE-2026-56266</a></td>
    </tr>

    <td class=3D"vendor-product">Creative Themes--Blocksy Companion Pro</td> <td>Contributor Remote Code Execution (RCE) in Blocksy Companion Pro &lt;=
    =3D 2.1.45 versions.</td>
    <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57315" target=3D= "_blank" rel=3D"noopener">CVE-2026-57315</a></td>
    </tr>

    <td class=3D"vendor-product">Crocoblock. Jetimpex Inc.--JetBooking</td> <td>Unauthenticated SQL Injection in JetBooking &lt;=3D 4.0.4.1 versions.</=

    <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54820" target=3D= "_blank" rel=3D"noopener">CVE-2026-54820</a></td>
    </tr>

    <td class=3D"vendor-product">Crocoblock. Jetimpex Inc.--JetEngine</td> <td>Unauthenticated SQL Injection in JetEngine &lt;=3D 3.8.10.2 versions.</=

    <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56068" target=3D= "_blank" rel=3D"noopener">CVE-2026-56068</a></td>
    </tr>

    <td class=3D"vendor-product">Crocoblock. Jetimpex Inc.--JetSmartFilters</td=

    <td>Unauthenticated SQL Injection in JetSmartFilters &lt;=3D 3.8.3 versions= .</td>
    <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56067" target=3D= "_blank" rel=3D"noopener">CVE-2026-56067</a></td>
    </tr>

    <td class=3D"vendor-product">CusRev--Customer Reviews for WooCommerce</td> <td>Unauthenticated Cross Site Scripting (XSS) in Customer Reviews for WooC= ommerce &lt;=3D 5.110.1 versions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56043" target=3D= "_blank" rel=3D"noopener">CVE-2026-56043</a></td>
    </tr>

    <td class=3D"vendor-product">Daan.dev--OMGF Pro</td>
    <td>Unrestricted Upload of File with Dangerous Type vulnerability in Daan.D=
    ev OMGF Pro allows Using Malicious Files. This issue affects OMGF Pro: from=
    n/a through 5.2.6.</td>
    <td>2026-06-25</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57700" target=3D= "_blank" rel=3D"noopener">CVE-2026-57700</a></td>
    </tr>

    <td class=3D"vendor-product">Daktronics--VFC-DMP-5000</td>
    <td>Various versions of Daktronics Controller Firmware could allow authenti= cated and unauthenticated remote users to escape the intended directory and=
    enumerate arbitrary file system paths.</td>
    <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-28701" target=3D= "_blank" rel=3D"noopener">CVE-2026-28701</a></td>
    </tr>

    <td class=3D"vendor-product">Daktronics--VFC-DMP-5000</td>
    <td>The DMP-5000 devices are shipped with a default administrative web acco= unt with weak authentication controls, which are not required to be changed=
    during initial configuration or operation. Using these accounts provides f= ull system access.</td>
    <td>2026-06-26</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-31928" target=3D= "_blank" rel=3D"noopener">CVE-2026-31928</a></td>
    </tr>

    <td class=3D"vendor-product">Daktronics--VFC-DMP-5000</td>
    <td>The DMP-5000 file service exposes authenticated arbitrary file upload f= unctionality. There are exposed endpoints which allows authenticated users =
    to upload files of any type without validation. No file extension filtering=
    or content inspection is enforced which allows executable binaries and scr= ipts to be accepted and written directly to the server.</td> <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-33560" target=3D= "_blank" rel=3D"noopener">CVE-2026-33560</a></td>
    </tr>

    <td class=3D"vendor-product">danny-avila--LibreChat</td>
    <td>LibreChat is an enhanced ChatGPT clone that supports multiple AI provid= ers. Prior to 0.8.5, LibreChat's MCP OAuth implementation does not validate=
    that the resource parameter from OAuth Protected Resource metadata (RFC 97= 28) matches the configured MCP server URL, allowing a malicious MCP server =
    to steal access tokens intended for a legitimate server. This vulnerability=
    is fixed in 0.8.5.</td>
    <td>2026-06-25</td>
    <td>8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54030" target=3D= "_blank" rel=3D"noopener">CVE-2026-54030</a></td>
    </tr>

    <td class=3D"vendor-product">danny-avila--LibreChat</td>
    <td>LibreChat is an enhanced ChatGPT clone that supports multiple AI provid= ers. Prior to 0.8.4-rc1, LibreChat allows users to configure custom OpenAI-= compatible API endpoints by setting a baseURL. This URL is used to construc=
    t HTTP requests without any SSRF validation - no private IP check, no schem=
    e restriction, no DNS pinning. An authenticated user can set baseURL to int= ernal network addresses. This vulnerability is fixed in 0.8.4-rc1.</td> <td>2026-06-25</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54033" target=3D= "_blank" rel=3D"noopener">CVE-2026-54033</a></td>
    </tr>

    <td class=3D"vendor-product">danpros--htmly</td>
    <td>HTMLy CMS through 3.1.1 contains a path traversal vulnerability that al= lows low-privileged authenticated attackers to relocate arbitrary files by = supplying directory traversal sequences in the oldfile parameter at the adm=
    in autosave endpoint. Attackers can pass unsanitized traversal sequences di= rectly to file_exists() and rename() functions in admin.php without canonic= alization or directory boundary enforcement to cause unintended relocation =
    of any file writable by the web server process to an attacker-specified dra=
    ft location.</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45233" target=3D= "_blank" rel=3D"noopener">CVE-2026-45233</a></td>
    </tr>

    <td class=3D"vendor-product">daytonaio--daytona</td>
    <td>Daytona is a secure and elastic infrastructure runtime for AI-generated=
    code execution and agent workflows. Prior to 0.184.0, organization invitat= ions could be accepted (and declined) by a user whose email matched the inv= itation but had not been verified. Daytona authenticates users via OIDC and=
    matches an invitation's target email against the email in the caller's tok= en, but the invitation accept and decline paths did not require that email =
    to be verified, unlike organization creation, which already enforced verifi= cation. On identity providers that allow self-service signup and issue a se= ssion before the email is verified, an actor could register an address matc= hing a pending invitation, leave it unverified, and accept the invitation, = joining the target organization with the role the invitation carried (up to=
    Owner). This vulnerability is fixed in 0.184.0.</td>
    <td>2026-06-23</td>
    <td>8.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54320" target=3D= "_blank" rel=3D"noopener">CVE-2026-54320</a></td>
    </tr>

    <td class=3D"vendor-product">daytonaio--daytona</td>
    <td>Daytona is a secure and elastic infrastructure runtime for AI-generated=
    code execution and agent workflows. From 0.101.0 until 0.184.0, sandbox pr= eviews that were switched from public to private could remain reachable wit= hout authentication for a short period after the change, due to a cached vi= sibility state that was not invalidated when the sandbox's visibility chang= ed. This vulnerability is fixed in 0.184.0.</td>
    <td>2026-06-23</td>
    <td>7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54321" target=3D= "_blank" rel=3D"noopener">CVE-2026-54321</a></td>
    </tr>

    <td class=3D"vendor-product">daytonaio--daytona</td>
    <td>Daytona is a secure and elastic infrastructure runtime for AI-generated=
    code execution and agent workflows. Prior to 0.185.0, Daytona's organizati=
    on role update and delete endpoints authorized the caller as an owner of th=
    e organization named in the request path, but resolved and mutated the targ=
    et role by its identifier alone, without verifying the role belonged to tha=
    t organization. An authenticated user who owns any organization (organizati= ons are self-service) could therefore modify the permissions of, or delete,=
    a role belonging to a different organization, given that role's identifier=
    . This vulnerability is fixed in 0.185.0.</td>
    <td>2026-06-23</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54322" target=3D= "_blank" rel=3D"noopener">CVE-2026-54322</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Container Storage Modules</td>
    <td>Dell Dell Container Storage Modules, version(s) csi-powerstore v2.16.0,=
    csi-unity v2.16.0, csi-powerflex v2.16.0, csi-powermax v2.16.0, contain(s)=
    an Improper Neutralization of Special Elements used in an OS Command ('OS = Command Injection') vulnerability. A high privileged attacker with remote a= ccess could potentially exploit this vulnerability, leading to Command exec= ution.</td>
    <td>2026-06-26</td>
    <td>8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40711" target=3D= "_blank" rel=3D"noopener">CVE-2026-40711</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Display and Peripheral Manager</td>
    <td>Dell Display and Peripheral Manager (DDPM Windows), versions prior to 2= .3, contain an Improper Access Control vulnerability. A low-privileged atta= cker with local access could potentially exploit this vulnerability, leadin=
    g to Code execution.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46733" target=3D= "_blank" rel=3D"noopener">CVE-2026-46733</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Display and Peripheral Manager</td>
    <td>Dell Display and Peripheral Manager (DDPM Mac), versions prior to 2.3, = contain an Improper Certificate Validation vulnerability. A low-privileged = attacker with local access could potentially exploit this vulnerability, le= ading to Protection mechanism bypass.</td>
    <td>2026-06-25</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46734" target=3D= "_blank" rel=3D"noopener">CVE-2026-46734</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Display and Peripheral Manager</td>
    <td>Dell Display and Peripheral Manager (DDPM Mac), versions prior to 2.3, = contain an Improper Neutralization of Special Elements used in an OS Comman=
    d ('OS Command Injection') vulnerability. A low-privileged attacker with lo= cal access could potentially exploit this vulnerability, leading to Command=
    execution.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46735" target=3D= "_blank" rel=3D"noopener">CVE-2026-46735</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Wyse Management Suite</td>
    <td>Dell Wyse Management Suite, versions prior to WMS 5.5 HF1, contain an A= cceptance of Extraneous Untrusted Data With Trusted Data vulnerability. A l= ow-privileged attacker with remote access could potentially exploit this vu= lnerability, leading to Remote Code Execution.</td>
    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41120" target=3D= "_blank" rel=3D"noopener">CVE-2026-41120</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Wyse Management Suite</td>
    <td>Dell Wyse Management Suite, versions prior to WMS 5.5 HF1, contain an I= mproper Limitation of a Pathname to a Restricted Directory ('Path Traversal=
    ') vulnerability. A high privileged attacker with remote access could poten= tially exploit this vulnerability, leading to Remote Code Execution.</td> <td>2026-06-25</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49506" target=3D= "_blank" rel=3D"noopener">CVE-2026-49506</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Wyse Management Suite (WMS)</td>
    <td>Dell Wyse Management Suite (WMS), versions prior to WMS 2605, contain a=
    n Improper Neutralization of Special Elements used in an SQL Command ('SQL = Injection') vulnerability. A low-privileged attacker with remote access cou=
    ld potentially exploit this vulnerability, leading to Unauthorized access.<=

    <td>2026-06-22</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44271" target=3D= "_blank" rel=3D"noopener">CVE-2026-44271</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Wyse Management Suite (WMS)</td>
    <td>Dell Wyse Management Suite (WMS), versions prior to WMS 2605, contain a=
    n Improper Neutralization of Special Elements used in an SQL Command ('SQL = Injection') vulnerability. A low-privileged attacker with remote access cou=
    ld potentially exploit this vulnerability, leading to Unauthorized access.<=

    <td>2026-06-22</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44272" target=3D= "_blank" rel=3D"noopener">CVE-2026-44272</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Wyse Management Suite (WMS)</td>
    <td>Dell Wyse Management Suite (WMS), versions prior to WMS 2605, contain a=
    n Improper Link Resolution Before File Access vulnerability. A low-privileg=
    ed attacker with local access could potentially exploit this vulnerability,=
    leading to Unauthorized access.</td>
    <td>2026-06-22</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44274" target=3D= "_blank" rel=3D"noopener">CVE-2026-44274</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7= .10, Deno's node:child_process implementation provided an escapeShellArg() = helper used when callers passed shell: true to spawn / spawnSync / exec and=
    friends. On Windows, the helper failed to quote arguments that contained c= md.exe metacharacters and did not neutralize % (which cmd.exe expands even = inside double-quoted strings). An attacker who controlled any portion of an=
    argument passed to such a call could inject arbitrary additional commands = into the spawned cmd.exe invocation. This vulnerability is fixed in 2.7.10.= </td>
    <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49402" target=3D= "_blank" rel=3D"noopener">CVE-2026-49402</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. From 2.0.0 u= ntil 2.7.8, a flaw in Deno's Node.js tls compatibility layer could cause a = TLS client to transmit application data in plaintext after a connection ret= ry. When `autoSelectFamily was enabled and the first address-family attempt=
    failed, the socket reinitialization path reused a stale TLS upgrade hook t= hat was bound to the original, failed handle. As a result, the replacement = TCP connection was never upgraded to TLS, and any data the application wrot=
    e before the secureConnect event travelled over the network unencrypted. A = network attacker positioned to cause the initial connection attempt to fail=
    (for example, by dropping IPv6 traffic on a dual-stack host) could determi= nistically trigger the fallback path and observe or tamper with traffic tha=
    t the application believed was TLS-protected. This vulnerability is fixed i=
    n 2.7.8.</td>
    <td>2026-06-23</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44726" target=3D= "_blank" rel=3D"noopener">CVE-2026-44726</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7= .14, Deno's permission system enforces filesystem and execution restriction=
    s by comparing the requested path against the path supplied to --deny-read,=
    --deny-write, --deny-run, or --deny-ffi. On macOS, that comparison was don=
    e at the raw-byte level while the APFS filesystem treats different Unicode = spellings of the same name as the same file. That means a program could rea=
    ch a denied path by spelling it differently than the deny rule. This vulner= ability is fixed in 2.7.14.</td>
    <td>2026-06-23</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49401" target=3D= "_blank" rel=3D"noopener">CVE-2026-49401</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8= .1, node:crypto.checkPrime(candidate[, options][, callback]) and crypto.che= ckPrimeSync(candidate[, options]) ran no Miller-Rabin rounds at all when th=
    e caller left options.checks at its default of 0. In that mode, the only te=
    st applied to the candidate was trial division by the primes up to 17,863. = Any composite whose smallest prime factor exceeds that bound - for example = the product of two primes just above it, such as 17,881 =C3=83=E2=80=94 17,= 891 - was reported as true ("probably prime"). The same divergence affected=
    the lower-level op_node_check_prime / op_node_check_prime_bytes paths that=
    the polyfill calls into. This vulnerability is fixed in 2.8.1.</td> <td>2026-06-23</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49440" target=3D= "_blank" rel=3D"noopener">CVE-2026-49440</a></td>
    </tr>

    <td class=3D"vendor-product">Design--Stylish Cost Calculator</td> <td>Unauthenticated Broken Access Control in Stylish Cost Calculator &lt;=
    =3D 8.3.9 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54847" target=3D= "_blank" rel=3D"noopener">CVE-2026-54847</a></td>
    </tr>

    <td class=3D"vendor-product">Dev Kabir--Enable CORS</td>
    <td>Unauthenticated Backdoor in Enable CORS &lt;=3D 2.0.3 versions.</td> <td>2026-06-26</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54833" target=3D= "_blank" rel=3D"noopener">CVE-2026-54833</a></td>
    </tr>

    <td class=3D"vendor-product">dFactory--Responsive Lightbox</td> <td>Unauthenticated Cross Site Scripting (XSS) in Responsive Lightbox &lt;=
    =3D 2.7.6 versions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56041" target=3D= "_blank" rel=3D"noopener">CVE-2026-56041</a></td>
    </tr>

    <td class=3D"vendor-product">Digiwin--EasyFlow .NET</td>
    <td>EasyFlow .NET developed by Digiwin has a Session Fixation vulnerability=
    . If unauthenticated remote attackers replace a specific session ID for a u= ser, they can gain the user's privilege once the user logs in.</td> <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12581" target=3D= "_blank" rel=3D"noopener">CVE-2026-12581</a></td>
    </tr>

    <td class=3D"vendor-product">docling-project--docling</td>
    <td>Docling simplifies document processing by parsing diverse formats and p= roviding integrations with the generative AI ecosystem. FIn versions &gt;=
    =3D 2.82.0, &lt; 2.91.0, if the HTML backend was explicitly configured for = rendering (rendering option by default deactivated), then the Playwright-ba= sed rendering feature could allow JavaScript execution and unrestricted net= work access when processing untrusted HTML documents. An attacker could cra=
    ft malicious HTML that executes arbitrary JavaScript in the rendering conte=
    xt or makes unauthorized network requests to internal services, potentially=
    leading to SSRF attacks, data exfiltration, or remote code execution in th=
    e rendering environment. This vulnerability is fixed in 2.91.0.</td> <td>2026-06-24</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44016" target=3D= "_blank" rel=3D"noopener">CVE-2026-44016</a></td>
    </tr>

    <td class=3D"vendor-product">docling-project--docling</td>
    <td>Docling simplifies document processing by parsing diverse formats and p= roviding integrations with the generative AI ecosystem. Prior to 2.91.0, th=
    e EasyOCR model download functionality extracted ZIP archives without valid= ating member paths, enabling Zip Slip attacks. If an attacker could comprom= ise the model download source (via supply chain attack, DNS spoofing, or MI= TM), they could write arbitrary files to any location writable by the proce= ss, potentially achieving remote code execution by overwriting Python files=
    or system binaries, persistent backdoors by modifying startup scripts or S=
    SH keys, and data corruption or system compromise. This vulnerability is fi= xed in 2.91.0.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44017" target=3D= "_blank" rel=3D"noopener">CVE-2026-44017</a></td>
    </tr>

    <td class=3D"vendor-product">docling-project--docling</td>
    <td>Docling simplifies document processing by parsing diverse formats and p= roviding integrations with the generative AI ecosystem. From 2.13.0 until 2= .74.0, the USPTO patent XML parser used the standard xml.sax.parseString() = without protection against XML External Entity (XXE) attacks. An attacker c= ould craft malicious USPTO patent XML files with external entity references=
    that could read arbitrary files from the server filesystem, perform Server= -Side Request Forgery (SSRF) attacks, or cause denial of service through en= tity expansion (Billion Laughs attack). The vulnerability affects three USP=
    TO patent format parsers: ICE (v4.x), Grant v2.5, and Application v1.x. Thi=
    s vulnerability is fixed in 2.74.0.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44020" target=3D= "_blank" rel=3D"noopener">CVE-2026-44020</a></td>
    </tr>

    <td class=3D"vendor-product">docling-project--docling</td>
    <td>Docling simplifies document processing by parsing diverse formats and p= roviding integrations with the generative AI ecosystem. Prior to 2.94.0, th=
    e HTML backend has unsafe URI and path handling. This vulnerability is fixe=
    d in 2.94.0.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47214" target=3D= "_blank" rel=3D"noopener">CVE-2026-47214</a></td>
    </tr>

    <td class=3D"vendor-product">Dokan Multivendor Plugin--Dokan Pro</td> <td>Unauthenticated Privilege Escalation in Dokan Pro &lt;=3D 5.0.4 version= s.</td>
    <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56033" target=3D= "_blank" rel=3D"noopener">CVE-2026-56033</a></td>
    </tr>

    <td class=3D"vendor-product">dokku--dokku</td>
    <td>Dokku is a docker-powered PaaS. Prior to 0.38.2, the git:from-archive a=
    nd certs:add commands extract user-supplied tar/zip archives into temporary=
    directories without sanitizing member paths or preventing symlink traversa=
    l. GNU tar creates symlinks during extraction and follows them for subseque=
    nt entries, allowing an attacker to write arbitrary files anywhere writable=
    by the dokku user - including overwriting ~/.ssh/authorized_keys to gain u= nrestricted shell access. This vulnerability is fixed in 0.38.2.</td> <td>2026-06-26</td>
    <td>9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45405" target=3D= "_blank" rel=3D"noopener">CVE-2026-45405</a></td>
    </tr>

    <td class=3D"vendor-product">dokku--dokku</td>
    <td>Dokku is a docker-powered PaaS. Prior to 0.38.2, the openresty-vhosts p= lugin copies files from an app's openresty/http-includes/ git repository di= rectory to the host and then interpolates their filenames, unescaped, into =
    a single-quoted shell string that is later parsed by eval. A filename conta= ining a single quote breaks the quoting and allows command substitution to = execute arbitrary commands on the host as the dokku user during the app's n= ext deploy. This vulnerability is fixed in 0.38.2.</td>
    <td>2026-06-26</td>
    <td>9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45406" target=3D= "_blank" rel=3D"noopener">CVE-2026-45406</a></td>
    </tr>

    <td class=3D"vendor-product">dokku--dokku</td>
    <td>Dokku is a docker-powered PaaS. Prior to 0.38.2, the app name validatio=
    n regex (^[a-z0-9][^/:_A-Z]*$) permits shell metacharacters. When an authen= ticated user pushes to a git remote with a crafted app name, the name is em= bedded unquoted into a bash pre-receive hook script via an unquoted heredoc=
    (&lt;&lt;EOF instead of &lt;&lt;'EOF') in fn-git-create-hook() at plugins/= git/internal-functions:378. On git push, bash interprets the semicolon as a=
    command separator, executing arbitrary commands as the dokku user. This vu= lnerability is fixed in 0.38.2.</td>
    <td>2026-06-26</td>
    <td>9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45408" target=3D= "_blank" rel=3D"noopener">CVE-2026-45408</a></td>
    </tr>

    <td class=3D"vendor-product">dokku--dokku</td>
    <td>Dokku is a docker-powered PaaS. Prior to 0.38.7, the cron plugin utiliz=
    es commands in the app.json file to manage system cron running as the Dokku=
    user. An app.json cron command utilizing special shell characters - includ= ing, but not limited to, &gt; or ; - can break out of the Docker container = and execute commands on the host as the Dokku user. This vulnerability is f= ixed in 0.38.7.</td>
    <td>2026-06-26</td>
    <td>9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54636" target=3D= "_blank" rel=3D"noopener">CVE-2026-54636</a></td>
    </tr>

    <td class=3D"vendor-product">dragonflydb--dragonfly</td>
    <td>Dragonfly is an in-memory data store built for modern application workl= oads. Prior to 1.39.0, a crafted RESTORE payload triggers an out-of-bounds = read in DragonflyDB's listpack collection loaders, crashing the entire serv=
    er process (SIGSEGV). Because DragonflyDB requires no authentication by def= ault and RESTORE is a normal keyspace command, an unauthenticated remote at= tacker can crash the server with a single ~24-byte command - a remote, repe= atable denial of service. This vulnerability is fixed in 1.39.0.</td> <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54341" target=3D= "_blank" rel=3D"noopener">CVE-2026-54341</a></td>
    </tr>

    <td class=3D"vendor-product">Eagle-Themes--Eagle Booking</td> <td>Unauthenticated Cross Site Request Forgery (CSRF) in Eagle Booking &lt;= =3D 1.3.4.3 versions.</td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-68052" target=3D= "_blank" rel=3D"noopener">CVE-2025-68052</a></td>
    </tr>

    <td class=3D"vendor-product">earendil-works--pi</td>
    <td>Pi is a minimal terminal coding harness. From 0.74.0 until 0.78.1, Pi v= ersions with temporary npm or git extension package installs used predictab=
    le paths under the operating system temporary directory. On Linux-based mul= ti-user systems, a local attacker who can write to the shared temporary dir= ectory could prepare the expected package location before another user runs=
    pi with a temporary extension package source. Pi could then load attacker-= controlled extension code in the victim user's process. This vulnerability =
    is fixed in 0.78.1.</td>
    <td>2026-06-23</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54328" target=3D= "_blank" rel=3D"noopener">CVE-2026-54328</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. From 1.37.0 until 1.37.5 and 1.38.3, when the %REQUESTED_SE= RVER_NAME(X:Y)% is used in log format and host related options is specified=
    , like HOST_FIRST, SNI_FIRST, it's possible to crash Envoy when the specifi=
    ed host header is missing in the request headers. This vulnerability is fix=
    ed in 1.37.5 and 1.38.3.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47220" target=3D= "_blank" rel=3D"noopener">CVE-2026-47220</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, destructor of=
    JSON Object results in stack overflow when deeply O(100K) nested objects a=
    re present. This vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, and 1.3= 8.1.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48042" target=3D= "_blank" rel=3D"noopener">CVE-2026-48042</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. From 1.23.0 until 1.35.11, 1.36.7, 1.37.3, and 1.38.1, a vu= lnerability has been identified in Envoy's zstd decompressor implementation=
    (ZstdDecompressorImpl). When zstd decompression is enabled, processing a s= pecially crafted, highly compressed zstd payload can lead to massive memory=
    allocation. An attacker can exploit this to cause severe memory exhaustion=
    , potentially resulting in an Out-Of-Memory (OOM) kill and Denial of Servic=
    e (DoS) for the Envoy proxy. This vulnerability is fixed in 1.35.11, 1.36.7=
    , 1.37.3, and 1.38.1.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48044" target=3D= "_blank" rel=3D"noopener">CVE-2026-48044</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, Envoy can tra= nslate a downstream HTTP/3 request that is complete at the transport layer = (HEADERS with FIN / headers-only close) but still carries a nonzero Content= -Length into a complete upstream HTTP/1 request with unresolved body debt. =
    In an HTTP/1 upstream deployment where the origin replies before reading th=
    e declared body and keeps the connection reusable, the beginning of the nex=
    t Envoy-generated upstream request can be consumed as the first request's b= ody. The remaining bytes are then parsed by the origin as a new HTTP/1 requ= est. This was reproduced as a route-bypass/desync: direct /pwn was denied b=
    y Envoy, but the second downstream H3 stream received the response for back= end-parsed GET /pwn HTTP/1.1. This vulnerability is fixed in 1.35.11, 1.36.=
    7, 1.37.3, and 1.38.1.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48743" target=3D= "_blank" rel=3D"noopener">CVE-2026-48743</a></td>
    </tr>

    <td class=3D"vendor-product">Etoile Web Design Incorporated--Five Star Rest= aurant Reservations</td>
    <td>Unauthenticated Broken Access Control in Five Star Restaurant Reservati= ons &lt;=3D 2.7.19 versions.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54830" target=3D= "_blank" rel=3D"noopener">CVE-2026-54830</a></td>
    </tr>

    <td class=3D"vendor-product">EventPrime--EventPrime</td>
    <td>Subscriber PHP Object Injection in EventPrime &lt;=3D 4.3.4.1 versions.= </td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56053" target=3D= "_blank" rel=3D"noopener">CVE-2026-56053</a></td>
    </tr>

    <td class=3D"vendor-product">Everthemess--Goya Core</td>
    <td>Contributor Local File Inclusion in Goya Core &lt; 1.0.9.4 versions.</t=

    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-68064" target=3D= "_blank" rel=3D"noopener">CVE-2025-68064</a></td>
    </tr>

    <td class=3D"vendor-product">EVoke--EVoke CSMS</td>
    <td>WebSocket endpoints lack proper authentication mechanisms, enabling att= ackers to impersonate charging stations. As a result, attackers can exploit=
    this weakness to gain unauthorized access to sensitive data or perform una= uthorized actions. Given that no authentication is required, this can lead =
    to privilege escalation and potentially compromise the security of the enti=
    re system.</td>
    <td>2026-06-25</td>
    <td>9.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40702" target=3D= "_blank" rel=3D"noopener">CVE-2026-40702</a></td>
    </tr>

    <td class=3D"vendor-product">EVoke--EVoke CSMS</td>
    <td>The WebSocket Application Programming Interface lacks restrictions on t=
    he number of authentication requests. This absence of rate limiting may all=
    ow an attacker to conduct denial-of-service attacks or brute-force attacks =
    to gain unauthorized access.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50176" target=3D= "_blank" rel=3D"noopener">CVE-2026-50176</a></td>
    </tr>

    <td class=3D"vendor-product">EVoke--EVoke CSMS</td>
    <td>The WebSocket backend uses charging station identifiers to uniquely ass= ociate sessions but allows multiple endpoints to connect using the same ses= sion identifier. This implementation results in predictable session identif= iers. This vulnerability may allow unauthorized users to authenticate as ot= her users or enable a malicious actor to cause a denial-of-service conditio=
    n by overwhelming the backend with valid session requests.</td> <td>2026-06-25</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54479" target=3D= "_blank" rel=3D"noopener">CVE-2026-54479</a></td>
    </tr>

    <td class=3D"vendor-product">expr-eval--expr-eval</td>
    <td>All versions of the package expr-eval are vulnerable to Code Execution = via the toJSFunction() API. An attacker can execute arbitrary JavaScript by=
    supplying crafted expressions that are compiled into native code using new=
    Function(). Because user-controlled expressions are transformed directly i= nto executable JavaScript, attackers can escape the intended expression san= dbox and run arbitrary code within the application's context.</td> <td>2026-06-23</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12866" target=3D= "_blank" rel=3D"noopener">CVE-2026-12866</a></td>
    </tr>

    <td class=3D"vendor-product">FasterXML--jackson-databind</td> <td>jackson-databind contains the general-purpose data-binding functionalit=
    y and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21= .4, and 3.1.4, jackson-databind's PolymorphicTypeValidator (PTV) is the pri= mary safety mechanism guarding polymorphic deserialization. When polymorphi=
    c typing is enabled and a type identifier contains generic parameters (i.e.=
    the type ID string contains &lt;), DatabindContext._resolveAndValidateGene= ric() validates only the raw container class name (the substring before &lt=
    ;) against the configured PTV. If the container type is approved, the metho=
    d parses the full canonical type string via TypeFactory.constructFromCanoni= cal() and returns the fully parameterized type without ever validating the = nested type arguments against the PTV. The nested type arguments are then r= esolved, instantiated, and populated as beans during deserialization. An at= tacker who controls the type ID can therefore place a denied class as a gen= eric type parameter of an allowed container - for example java.util.ArrayLi= st&lt;com.evil.Gadget&gt; when only java.util.ArrayList is allow-listed. Th=
    e container passes the PTV check; com.evil.Gadget is loaded via Class.forNa= me(name, true, loader), instantiated, and its properties are set from attac= ker-controlled JSON. This completely bypasses an explicitly configured PTV = allow-list. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.</td> <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54512" target=3D= "_blank" rel=3D"noopener">CVE-2026-54512</a></td>
    </tr>

    <td class=3D"vendor-product">FasterXML--jackson-databind</td> <td>jackson-databind contains the general-purpose data-binding functionalit=
    y and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21= .4, and 3.1.4, BasicPolymorphicTypeValidator.Builder.allowIfSubTypeIsArray(=
    ) allowlists any array type based only on clazz.isArray(), without validati=
    ng the array's component (element) type against the configured allowlist. A=
    PTV built with allowIfSubTypeIsArray() plus an explicit concrete-type allo= wlist therefore still permits EvilType[] even though EvilType is not allowl= isted. When Jackson deserializes the elements and no per-element type IDs a=
    re present, it instantiates the component type directly with no further PTV=
    check, bypassing the allowlist. This vulnerability is fixed in 2.18.8, 2.2= 1.4, and 3.1.4.</td>
    <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54513" target=3D= "_blank" rel=3D"noopener">CVE-2026-54513</a></td>
    </tr>

    <td class=3D"vendor-product">feast-dev--feast</td>
    <td>Feast before 0.63.0 contains an unsafe deserialization vulnerability th=
    at allows unauthenticated or unauthorized attackers to achieve remote code = execution by sending a crafted gRPC request to the registry server. The use= r_defined_function.body field of an OnDemandFeatureView spec is decoded fro=
    m base64 and passed to dill.loads() before any authorization check is perfo= rmed, enabling attackers to embed a malicious serialized Python object with=
    an arbitrary __reduce__ method to execute OS commands as the feast service=
    account.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56121" target=3D= "_blank" rel=3D"noopener">CVE-2026-56121</a></td>
    </tr>

    <td class=3D"vendor-product">FFmpeg--FFmpeg</td>
    <td>FFmpeg's RASC video decoder (decode_dlta in libavcodec/rasc.c) performs=
    32-bit reads and writes at the row cursor before the NEXT_LINE row-boundar=
    y check and validates the DLTA region in pixel rather than byte units, so a=
    DLTA run on a PAL8 frame can access several bytes past the row allocation.=
    A crafted media stream using the RASC FourCC, decoded by libavcodec, trigg= ers a bitstream-controlled out-of-bounds heap write and adjacent out-of-bou= nds read, leading to memory corruption.</td>
    <td>2026-06-28</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58049" target=3D= "_blank" rel=3D"noopener">CVE-2026-58049</a></td>
    </tr>

    <td class=3D"vendor-product">filamentphp--filament</td>
    <td>Filament is a collection of full-stack components for accelerated Larav=
    el development. From 4.0.0 until 4.11.5 and 5.6.5, a flaw in the handling o=
    f recovery codes for app-based multi-factor authentication allows the same = recovery code to be reused via concurrent submission. This issue does not a= ffect email-based MFA. It also only applies when recovery codes are enabled=
    . If an attacker gains access to both the user's password and their recover=
    y codes, they get two authenticated sessions per recovery code burned inste=
    ad of one, or more if they batch the parallel submissions wider, materially=
    extending the attacker's window of access compared to what the single-use = guarantee implies. This vulnerability is fixed in 4.11.5 and 5.6.5.</td> <td>2026-06-22</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48505" target=3D= "_blank" rel=3D"noopener">CVE-2026-48505</a></td>
    </tr>

    <td class=3D"vendor-product">filamentphp--filament</td>
    <td>Filament is a collection of full-stack components for accelerated Larav=
    el development. From 3.0.0 until 3.3.53, a disabled RichEditor field render=
    ed its raw state without sanitizing HTML. Where the data stored in this fie= ld's state isn't sanitized already when the form state was filled, an attac= ker could plant malicious HTML or JavaScript and achieve XSS that executes = for users who view the form. This vulnerability is fixed in 3.3.53.</td> <td>2026-06-22</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55409" target=3D= "_blank" rel=3D"noopener">CVE-2026-55409</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Starting = with 2.0.0-rc.1, when FileBrowser is configured with proxy authentication (= auth.method=3Dproxy), any unauthenticated attacker who can reach the server=
    directly can impersonate any user - including admin - by sending a single = forged HTTP header. No credentials are required. Additionally, specifying a=
    non-existent username causes the server to automatically create a new user=
    account, providing an account creation primitive with no authorization. Th=
    is is an already known issue that has been documented in the documentation = for several years, but has not been documented as a vulnerability before.</=

    <td>2026-06-25</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54089" target=3D= "_blank" rel=3D"noopener">CVE-2026-54089</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Prior to = 2.63.7, `POST /api/share/&lt;path&gt;` accepts an authenticated request for=
    an arbitrary path and stores a public share record without checking whethe=
    r the target file currently exists. Later, when a file is created at that s= ame path, the previously created public share immediately becomes valid and=
    exposes the new file through `GET /api/public/dl/&lt;hash&gt;`. This vulne= rability is fixed in 2.63.7.</td>
    <td>2026-06-25</td>
    <td>8.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54096" target=3D= "_blank" rel=3D"noopener">CVE-2026-54096</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Prior to = 2.63.16, a scoped, non-admin File Browser user holding only the Create perm= ission can delete arbitrary files outside their scope (other tenants' data,=
    and the application's own database) via the upload failure-cleanup path. S= copedFs.RemoveAll is the one dereferencing operation that skips the symlink=
    guard every other method enforces. The direct-upload handler runs RemoveAl=
    l on the user-controlled path during failed-upload cleanup, gated only by P= erm.Create. If an escaping directory symlink already exists inside the user=
    's scope, an authenticated create-only user can delete an out-of-scope targ= et, bypassing both the ScopedFs boundary and the Perm.Delete gate. This vul= nerability is fixed in 2.63.16.</td>
    <td>2026-06-25</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55667" target=3D= "_blank" rel=3D"noopener">CVE-2026-55667</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Prior to = 2.63.6, File Browser's public share handlers rebase the share owner's files= ystem root to the shared directory and then evaluate descendant paths again=
    st the owner's global and per-user rules using the rebased relative path in= stead of the original path relative to the owner's scope. As a result, an a= ttacker who knows a public directory share URL can access files and subdire= ctories that the owner explicitly blocked with rules, as long as those bloc= ked paths are located underneath the shared directory. In the simplest case=
    this is an unauthenticated information disclosure through `GET /api/public= /share/*` and `GET /api/public/dl/*`. This vulnerability is fixed in 2.63.6= .</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54091" target=3D= "_blank" rel=3D"noopener">CVE-2026-54091</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Prior to = 2.63.14, it does not stop the HTTP file handlers from following symbolic li= nks before they open, serve, write, share, or list a file. As a result, a s= coped user - and in some cases an unauthenticated public-share recipient - = can cross the intended scope boundary by following a symlink whose path is = lexically inside their scope but whose target is outside it. This vulnerabi= lity is fixed in 2.63.14.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54094" target=3D= "_blank" rel=3D"noopener">CVE-2026-54094</a></td>
    </tr>

    <td class=3D"vendor-product">FlatPress--FlatPress</td>
    <td>FlatPress contains a stored cross-site scripting vulnerability in comme=
    nt and contact forms where name, URL, and email fields are rendered without=
    proper output encoding in Smarty templates. Attackers can inject arbitrary=
    HTML and JavaScript through these fields to execute malicious scripts in b= rowsers of viewers including administrators, or bypass URL scheme validatio=
    n to inject javascript: or data: URIs.</td>
    <td>2026-06-23</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56785" target=3D= "_blank" rel=3D"noopener">CVE-2026-56785</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise contains a path traversal vulnerability in the /api/v1/document= -store/loader/process endpoint that allows unauthenticated attackers to wri=
    te arbitrary files to the filesystem. Attackers can exploit unsanitized fil= eName parameters with ../ sequences to overwrite critical files like packag= e.json and achieve remote code execution when the application restarts.</td=

    <td>2026-06-25</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71338" target=3D= "_blank" rel=3D"noopener">CVE-2025-71338</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise contains an authentication bypass vulnerability in the unprotec= ted /api/v1/account/register endpoint that allows unauthenticated attackers=
    to create user accounts. Remote attackers can exploit this endpoint to reg= ister arbitrary accounts and authenticate to the system, gaining full API a= ccess without credentials.</td>
    <td>2026-06-25</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71327" target=3D= "_blank" rel=3D"noopener">CVE-2025-71327</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.0.6 (affected versions 2.2.8 and earlier) contains an = arbitrary file access vulnerability due to missing validation that the chat= flowId and chatId parameters are UUIDs or numbers in file handling operatio= ns. By supplying a path-traversal value (e.g., '../../../../../tmp') as the=
    chatflow id, an unauthenticated attacker can use the /api/v1/chatflows end= point (via addBase64FilesToStorage) to write arbitrary files, and the /api/= v1/get-upload-file and /api/v1/openai-assistants-file/download endpoints (v=
    ia streamStorageFile) to read arbitrary files. Arbitrary file write may lea=
    d to remote code execution.</td>
    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71334" target=3D= "_blank" rel=3D"noopener">CVE-2025-71334</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.0.6 (affected versions 2.2.7-patch.1 and earlier) cont= ains an unsandboxed remote code execution vulnerability in the Custom MCP f= eature, which is designed to execute OS commands such as launching local MC=
    P servers. Because Flowise's authentication and authorization model is mini= mal and lacks role-based access control, and the default installation runs = without authentication unless FLOWISE_USERNAME and FLOWISE_PASSWORD are set=
    , an attacker can send a crafted JSON payload with the header 'x-request-fr= om: internal' to the /api/v1/node-load-method/customMCP endpoint to execute=
    arbitrary OS commands, resulting in complete compromise of the platform co= ntainer or server.</td>
    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71336" target=3D= "_blank" rel=3D"noopener">CVE-2025-71336</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.1.2 contains multiple OS command injection vulnerabili= ties in the Custom MCP Server feature due to incomplete command-flag valida= tion and a regex bypass in local file access restrictions. An attacker with=
    a Flowise account of any role, or API access with view/update permissions = for chatflows, can configure a malicious MCP server to bypass the validateC= ommandFlags blocklist (for example, 'docker build' is not blocked, and 'npx=
    --yes' is not blocked while only '-y' is) and the validateArgsForLocalFile= Access checks, resulting in execution of arbitrary commands on the Flowise = host.</td>
    <td>2026-06-23</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56274" target=3D= "_blank" rel=3D"noopener">CVE-2026-56274</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.0.10 contains an unverified password change vulnerabil= ity. An authenticated user can change their account password through the ac= count settings (Security) section without supplying the current password or=
    any additional verification, as the application does not enforce a current= -password check on the credential change. This can lead to full account tak= eover, particularly if an attacker can hijack or coerce an authenticated se= ssion.</td>
    <td>2026-06-25</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71328" target=3D= "_blank" rel=3D"noopener">CVE-2025-71328</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.0.10 (affected versions 3.0.7 and earlier) fails to in= validate existing sessions and session tokens after a user changes their pa= ssword. An attacker who already holds an active session, for example via a = stolen session token or a device left logged in, remains authenticated as t=
    he legitimate user even after the user rotates their credentials, undermini=
    ng the security purpose of the password change.</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71335" target=3D= "_blank" rel=3D"noopener">CVE-2025-71335</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.0.10 (affected versions 3.0.7 and earlier) contains an=
    unverified email change vulnerability. An authenticated user can change th=
    e account email address, used as a login identifier and password-recovery c= hannel, via the account profile endpoint without confirming the change to t=
    he original email address or re-entering the current password. By changing = the recovery email, an attacker can take over the account and abuse passwor=
    d reset mechanisms.</td>
    <td>2026-06-23</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71337" target=3D= "_blank" rel=3D"noopener">CVE-2025-71337</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.0.6 contains an arbitrary file read vulnerability in t=
    he chatId parameter of the /api/v1/get-upload-file and /api/v1/openai-assis= tants-file/download endpoints. The chatId value is not validated and is pas= sed to streamStorageFile(), where a fallback file-lookup path constructed w= ithout the orgId is evaluated after the storage-directory containment check=
    , allowing path traversal beyond the intended storage directory. Unauthenti= cated attackers can read sensitive files such as /root/.flowise/database.sq= lite, exposing all database content in the default configuration.</td> <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71324" target=3D= "_blank" rel=3D"noopener">CVE-2025-71324</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.1.2 contains an information disclosure vulnerability i=
    n the /api/v1/chatflows/apikey/:apikey endpoint. When the keyonly query par= ameter is omitted (the default), the endpoint returns not only the chatflow=
    s bound to the supplied API key but also all chatflows across every workspa=
    ce that have no API key assigned, because the underlying query lacks any wo= rkspace filter. An attacker with a valid API key for one workspace can ther= efore retrieve the full ChatFlow configuration (including flowData with sys= tem prompts and node configurations, chatbotConfig, apiConfig, and credenti=
    al IDs) of unprotected chatflows belonging to other workspaces.</td> <td>2026-06-22</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56268" target=3D= "_blank" rel=3D"noopener">CVE-2026-56268</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.1.0 (versions 3.0.13 and earlier) contains a missing a= uthentication vulnerability in the /api/v1/loginmethod endpoint that allows=
    unauthenticated users to retrieve an organization's complete SSO configura= tion, including OAuth client secrets in cleartext, by providing an organiza= tionId parameter. Remote attackers can send a GET request to harvest sensit= ive API credentials for Google, Microsoft/Azure, GitHub, and Auth0 integrat= ions. This affects FlowiseAI Cloud and self-hosted instances where the endp= oint is exposed.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56270" target=3D= "_blank" rel=3D"noopener">CVE-2026-56270</a></td>
    </tr>

    <td class=3D"vendor-product">fpuenteonline--Object Cache 4 everyone</td> <td>Unauthenticated Sensitive Data Exposure in Object Cache 4 everyone &lt;= =3D 2.3.2 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54834" target=3D= "_blank" rel=3D"noopener">CVE-2026-54834</a></td>
    </tr>

    <td class=3D"vendor-product">Frisbii--Frisbii Pay</td>
    <td>Contributor Privilege Escalation in Frisbii Pay &lt;=3D 1.8.2 versions.= </td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56038" target=3D= "_blank" rel=3D"noopener">CVE-2026-56038</a></td>
    </tr>

    <td class=3D"vendor-product">FunnelKit--Funnel Builder by FunnelKit</td> <td>Improper Neutralization of Special Elements used in an SQL Command ('SQ=
    L Injection') vulnerability in FunnelKit Funnel Builder by FunnelKit allows=
    Blind SQL Injection. This issue affects Funnel Builder by FunnelKit: from = n/a through 3.15.0.5.</td>
    <td>2026-06-24</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56052" target=3D= "_blank" rel=3D"noopener">CVE-2026-56052</a></td>
    </tr>

    <td class=3D"vendor-product">garybowers--bootimus</td>
    <td>Bootimus through 0.1.70 contains a broken access control vulnerability = that allows authenticated low-privileged users to perform administrative ac= tions by exploiting missing role enforcement in the JWTMiddleware function =
    in internal/auth/auth.go, which validates JWT tokens and account status but=
    fails to inspect the is_admin flag. Attackers can send requests to any end= point under the /api/users path to create new administrator accounts or res=
    et administrator passwords, thereby gaining full control of the server and = the ability to modify boot menus and installation scripts served to PXE cli= ents.</td>
    <td>2026-06-23</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56115" target=3D= "_blank" rel=3D"noopener">CVE-2026-56115</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-I/O Box 4E</td>
    <td>GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays outp=
    ut that can be controlled over Ethernet and RS-485. DVRSearch is a service = running by default on the IOBox listening for UDP messages on port 10001. A=
    ny user on the network can send messages to this service and interact with = it. Upon receiving a UDP message, the server reads at most 1460 bytes into =
    a local buffer and a pointer to the buffer is stored in a global variable: = #### IP field stack overflow The following code is vulnerable to a stack ov= erflow that is attacker-controlled: v3 =3D strlen(g_network_config-&gt;ip_a= ddr); memcpy(&amp;reply_buf[36], g_network_config-&gt;ip_addr, v3);</td> <td>2026-06-24</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12485" target=3D= "_blank" rel=3D"noopener">CVE-2026-12485</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-I/O Box 4E</td>
    <td>GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays outp=
    ut that can be controlled over Ethernet and RS-485. DVRSearch is a service = running by default on the IOBox listening for UDP messages on port 10001. A=
    ny user on the network can send messages to this service and interact with = it. Upon receiving a UDP message, the server reads at most 1460 bytes into =
    a local buffer and a pointer to the buffer is stored in a global variable: = #### Net Mask field stack overflow The following code is vulnerable to a st= ack overflow that is attacker-controlled: v6 =3D strlen(g_network_config-&g= t;net_mask); memcpy(&amp;reply_buf[184], g_network_config-&gt;net_mask, v6)= ;</td>
    <td>2026-06-24</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12846" target=3D= "_blank" rel=3D"noopener">CVE-2026-12846</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-I/O Box 4E</td>
    <td>GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays outp=
    ut that can be controlled over Ethernet and RS-485. DVRSearch is a service = running by default on the IOBox listening for UDP messages on port 10001. A=
    ny user on the network can send messages to this service and interact with = it. Upon receiving a UDP message, the server reads at most 1460 bytes into =
    a local buffer and a pointer to the buffer is stored in a global variable: = #### Gateway field stack overflow The following code is vulnerable to a sta=
    ck overflow that is attacker-controlled: v7 =3D strlen(g_network_config-&gt= ;gateway); memcpy(&amp;reply_buf[216], g_network_config-&gt;gateway, v7);</=

    <td>2026-06-24</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12847" target=3D= "_blank" rel=3D"noopener">CVE-2026-12847</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-I/O Box 4E</td>
    <td>GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays outp=
    ut that can be controlled over Ethernet and RS-485. DVRSearch is a service = running by default on the IOBox listening for UDP messages on port 10001. A=
    ny user on the network can send messages to this service and interact with = it. Upon receiving a UDP message, the server reads at most 1460 bytes into =
    a local buffer and a pointer to the buffer is stored in a global variable: = #### DNS field stack overflow The following code is vulnerable to a stack o= verflow that is attacker-controlled: v8 =3D strlen(g_network_config-&gt;dns= _addr); memcpy(&amp;reply_buf[248], g_network_config-&gt;dns_addr, v8);</td=

    <td>2026-06-24</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12848" target=3D= "_blank" rel=3D"noopener">CVE-2026-12848</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-I/O Box 4E</td>
    <td>Multiple OS command injection vulnerabilities exist in the libNetSetObj= .so functionality of GeoVision GV-I/O Box 4E 2.09. A specially crafted netw= ork packet can lead to command execution. An attacker can send a network re= quest to trigger this vulnerability. `libNetSetObj.so` is an internal libra=
    ry used by various binaries on the device to configure the network stack (s= tart and stop various services, configure IP, Netmask, gateway, dns, etc.) = #### CNetSetObj::m_F_n_Set_IP_Addr command injection The following function=
    takes a string as an ip address, performs no sanitization and calls `syste= m`. This is a classic command injection vulnerability. The function is reac= hable from both the network-exposed `DVRSearch` service and the `Network.cg=
    i` endpoint. int __fastcall CNetSetObj::m_F_n_Set_IP_Addr(const char **this=
    , char *ip_addr) { bool v2; // zf char v4[72]; // [sp+0h] [bp-48h] BYREF v2=
    =3D *this =3D=3D 0; if ( *this ) v2 =3D ip_addr =3D=3D 0; if ( v2 ) return=
    0; sprintf(v4, "/sbin/ifconfig %s %s", *this, ip_addr); // attacker contro= lled ip address system(v4); return 1; }</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12486" target=3D= "_blank" rel=3D"noopener">CVE-2026-12486</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-I/O Box 4E</td>
    <td>Multiple OS command injection vulnerabilities exist in the libNetSetObj= .so functionality of GeoVision GV-I/O Box 4E 2.09. A specially crafted netw= ork packet can lead to command execution. An attacker can send a network re= quest to trigger this vulnerability. `libNetSetObj.so` is an internal libra=
    ry used by various binaries on the device to configure the network stack (s= tart and stop various services, configure IP, Netmask, gateway, dns, etc.) = #### CNetSetObj::m_F_n_Set_Net_Mask command injection The following functio=
    n takes a string as a net mask address, performs no sanitization on it and = calls `system`. This is a classic command injection vulnerability. The func= tion is reachable from both the network-exposed `DVRSearch` service and the=
    `Network.cgi` endpoint. int __fastcall CNetSetObj::m_F_n_Set_Net_Mask(cons=
    t char **this, char *netmask_addr) { bool v2; // zf char v4[72]; // [sp+0h]=
    [bp-48h] BYREF v2 =3D *this =3D=3D 0; if ( *this ) v2 =3D netmask_addr =3D= =3D 0; if ( v2 ) return 0; sprintf(v4, "/sbin/ifconfig %s netmask %s", *thi=
    s, netmask_addr); // attacker controlled netmask_addr system(v4); return 1;=
    }</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12849" target=3D= "_blank" rel=3D"noopener">CVE-2026-12849</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-I/O Box 4E</td>
    <td>Multiple OS command injection vulnerabilities exist in the libNetSetObj= .so functionality of GeoVision GV-I/O Box 4E 2.09. A specially crafted netw= ork packet can lead to command execution. An attacker can send a network re= quest to trigger this vulnerability. `libNetSetObj.so` is an internal libra=
    ry used by various binaries on the device to configure the network stack (s= tart and stop various services, configure IP, Netmask, gateway, dns, etc.) = #### CNetSetObj::m_F_n_Set_Gate_way command injection The following functio=
    n takes a string as a gatewy address, performs no sanitization on it and ca= lls `system`. This is a classic command injection vulnerability. The functi=
    on is reachable from both the network-exposed `DVRSearch` service and the `= Network.cgi` endpoint. int __fastcall CNetSetObj::m_F_n_Set_Gate_way(const = char **this, char *gw, char *dev) { char s[324]; // [sp+4h] [bp-144h] BYREF=
    if ( !dev &amp;&amp; !*this || !gw ) return 0; system("/sbin/route del -ne=
    t 224.0.0.0 netmask 224.0.0.0"); system("/sbin/route del default "); if ( d=
    ev ) sprintf(s, "/sbin/route add default gw %s dev %s", gw, dev); //attacke=
    r controlled gw string else sprintf(s, "/sbin/route add default gw %s dev %= s", gw, *this); //attacker controlled gw string system(s); sprintf(s, "/sbi= n/route add -net 224.0.0.0 netmask 224.0.0.0 gw %s dev %s", gw, *this); //a= ttacker controlled gw string system(s); return 1; }</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12850" target=3D= "_blank" rel=3D"noopener">CVE-2026-12850</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-I/O Box 4E</td>
    <td>Multiple OS command injection vulnerabilities exist in the libNetSetObj= .so functionality of GeoVision GV-I/O Box 4E 2.09. A specially crafted netw= ork packet can lead to command execution. An attacker can send a network re= quest to trigger this vulnerability. `libNetSetObj.so` is an internal libra=
    ry used by various binaries on the device to configure the network stack (s= tart and stop various services, configure IP, Netmask, gateway, dns, etc.) = #### CNetSetObj::m_F_n_Set_DNS_Addr command injection The following functio=
    n can take up to two addresses, performs no sanitization and then calls `sy= stem`. This is a classic command injection vulnerability. The function is r= eachable from both the network-exposed `DVRSearch` service and the `Network= .cgi` endpoint. int __fastcall CNetSetObj::m_F_n_Set_DNS_Addr(CNetSetObj *t= his, char *dns1, char *dns2) { int result; // r0 char v5[80]; // [sp+0h] [b= p-50h] BYREF if ( !dns1 ) result =3D 0; if ( dns1 ) { sprintf(v5, "/bin/ech=
    o nameserver %s &gt; /etc/resolv.conf", dns1); // attacker controlled dns1 = field system(v5); if ( dns2 ) { sprintf(v5, "/bin/echo nameserver %s &gt;&g=
    t; /etc/resolv.conf", dns2); system(v5); } return 1; } return result;</td> <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12851" target=3D= "_blank" rel=3D"noopener">CVE-2026-12851</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated stack-based buffer overflow vulnerability exists in = thttpd in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulner= ability is caused by insufficient bounds checking when processing web reque=
    st parameters in a specific request path. A remote attacker may exploit thi=
    s vulnerability by sending a crafted HTTP request with overly long input, r= esulting in memory corruption, denial of service, or potentially arbitrary = code execution.</td>
    <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57878" target=3D= "_blank" rel=3D"noopener">CVE-2026-57878</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated stack-based buffer overflow vulnerability exists in = ssvr in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerab= ility is caused by insufficient bounds checking when processing RTSP custom=
    authentication data. A remote attacker may exploit this vulnerability by s= ending a crafted RTSP request, resulting in memory corruption, denial of se= rvice, or potentially arbitrary code execution.</td>
    <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57879" target=3D= "_blank" rel=3D"noopener">CVE-2026-57879</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated stack-based buffer overflow vulnerability exists in = ssvr in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerab= ility is caused by insufficient bounds checking when parsing RTSP Digest au= thentication fields. A remote attacker may exploit this vulnerability by se= nding a crafted RTSP request containing overly long authentication data, re= sulting in memory corruption, denial of service, or potentially arbitrary c= ode execution.</td>
    <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57880" target=3D= "_blank" rel=3D"noopener">CVE-2026-57880</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated stack-based buffer overflow vulnerability exists in = vlsvr in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnera= bility is caused by insufficient length validation when processing remote l= ogin data. A remote attacker may exploit this vulnerability by sending craf= ted login data with overly long input, resulting in memory corruption, deni=
    al of service, or potentially arbitrary code execution.</td> <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57881" target=3D= "_blank" rel=3D"noopener">CVE-2026-57881</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated format string vulnerability exists in vlsvr in GeoVi= sion GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caus=
    ed by improper handling of externally controlled input during log message f= ormatting in the login processing path. A remote attacker may exploit this = vulnerability by sending crafted login data, potentially causing informatio=
    n disclosure, memory corruption, or a denial of service.</td> <td>2026-06-26</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57877" target=3D= "_blank" rel=3D"noopener">CVE-2026-57877</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated directory traversal vulnerability exists in get_fcon= t.cgi in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnera= bility is caused by insufficient validation of user-supplied file path inpu=
    t before the requested file is accessed by the CGI component. A remote atta= cker may exploit this vulnerability by sending a crafted request to read ar= bitrary files accessible to the affected process, resulting in information = disclosure.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57872" target=3D= "_blank" rel=3D"noopener">CVE-2026-57872</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated NULL pointer dereference vulnerability exists in IEE= E8021x_upload.cgi in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier.=
    The vulnerability is caused by improper validation of multipart upload hea= ders when processing certificate-related upload fields. A remote attacker m=
    ay exploit this vulnerability by sending a malformed multipart request, cau= sing the affected CGI process to crash and resulting in a denial of service= .</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57873" target=3D= "_blank" rel=3D"noopener">CVE-2026-57873</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated buffer overflow vulnerability exists in IEEE8021x_up= load.cgi in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vuln= erability is caused by insufficient bounds checking when parsing filename v= alues in multipart upload data. A remote attacker may exploit this vulnerab= ility by sending a crafted upload request with overly long input, causing m= emory corruption and resulting in a denial of service.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57874" target=3D= "_blank" rel=3D"noopener">CVE-2026-57874</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated NULL pointer dereference vulnerability exists in the=
    HTTP request parsing logic of multiple CGI components in GeoVision GV-LPC2= 011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by improp=
    er validation of required HTTP request metadata before it is used by the af= fected components. A remote attacker may exploit this vulnerability by send= ing a specially crafted HTTP request, causing the affected process to crash=
    and resulting in a denial of service.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57875" target=3D= "_blank" rel=3D"noopener">CVE-2026-57875</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GV-LPCLPC2011/2211</td>
    <td>An unauthenticated out-of-bounds write vulnerability exists in onvif.cg=
    i in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerabili=
    ty is caused by insufficient bounds checking when processing HTTP request b= ody data. A remote attacker may exploit this vulnerability by sending a cra= fted request with excessive input, causing memory corruption and resulting =
    in a denial of service.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57876" target=3D= "_blank" rel=3D"noopener">CVE-2026-57876</a></td>
    </tr>

    <td class=3D"vendor-product">getmaxun--maxun</td>
    <td>Maxun before 0.0.42 contains a cross-tenant insecure direct object refe= rence vulnerability in storage and webhook API handlers that allows authent= icated users to access other users' robots and OAuth tokens. Attackers can = read plaintext Google and Airtable access tokens, modify, delete, or execut=
    e other users' robots by bypassing ownership checks in API endpoints.</td> <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56767" target=3D= "_blank" rel=3D"noopener">CVE-2026-56767</a></td>
    </tr>

    <td class=3D"vendor-product">getsentry--sentry</td>
    <td>Sentry is an error tracking and performance monitoring tool. From 24.4.=
    0 until 26.5.2, a Regular Expression Denial of Service (ReDoS) vulnerabilit=
    y exists in Sentry's event ingestion pipeline, where a regex applied to att= acker-controlled fields on incoming events can be made to consume dispropor= tionate CPU time. This vulnerability is fixed in 26.5.2.</td> <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52794" target=3D= "_blank" rel=3D"noopener">CVE-2026-52794</a></td>
    </tr>

    <td class=3D"vendor-product">Gitea--act_runner</td>
    <td>Gitea act_runner with the Docker backend (through act 0.262.0) passes a=
    workflow's container.options string to the Docker job container's HostConf=
    ig and, when configured with privileged: false, forces only the Privileged = flag off while merging options such as --pid=3Dhost, --cap-add, and --secur= ity-opt unchanged. A user who can run a workflow on a Docker-backed runner = can create a job container with host namespaces and broad capabilities and = escape to the host as root despite privileged mode being disabled.</td> <td>2026-06-28</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58053" target=3D= "_blank" rel=3D"noopener">CVE-2026-58053</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab EE affecting all versions from=
    16.4 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under=
    certain conditions could have allowed an authenticated user with developer= -role permissions to execute arbitrary client-side code in the context of a= nother user's session, due to improper sanitization of user-supplied input.= </td>
    <td>2026-06-25</td>
    <td>8.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10086" target=3D= "_blank" rel=3D"noopener">CVE-2026-10086</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab CE/EE affecting all versions f= rom 18.10 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that u= nder certain conditions could have allowed an unauthenticated user to execu=
    te arbitrary JavaScript in a user's browser session due to improper path va= lidation under certain conditions.</td>
    <td>2026-06-25</td>
    <td>8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10712" target=3D= "_blank" rel=3D"noopener">CVE-2026-10712</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab EE affecting all versions from=
    19.1 before 19.1.1 that under certain conditions could have allowed a user=
    to access sensitive information that had already been committed to a proje= ct, due to insufficient output filtering in Duo Workflows.</td> <td>2026-06-25</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12053" target=3D= "_blank" rel=3D"noopener">CVE-2026-12053</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, organi= zation names containing path traversal sequences (../) are accepted by Gogs=
    , and repositories under them are written to paths following these path tra= versals. This allows storing/retrieving data for repositories at arbitrary = locations on the filesystem. By creating nested structure of Git repositori= es, one can overwrite the other's hooks configuration to result in Remote C= ode Execution (RCE). This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52813" target=3D= "_blank" rel=3D"noopener">CVE-2026-52813</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, Gogs a= llows authenticated users to achieve Remote Code Execution (RCE) on the ser= ver by creating a pull request with a specially crafted branch name that in= jects the --exec flag into the git rebase command during the "Rebase before=
    merging" merge operation. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52806" target=3D= "_blank" rel=3D"noopener">CVE-2026-52806</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, the fi=
    x for CVE-2022-1285 prevents adding webooks or running webhooks with URLs w= ith a hostname that resolves in localCIDRs. However, webhooks still follow = redirects allowing to access hostname inside localCIDRs. This vulnerability=
    is fixed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47267" target=3D= "_blank" rel=3D"noopener">CVE-2026-47267</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.0, as an = authorized user, an intruder can dictate the value which is passed to the g=
    it diff command which, together with bypassing the filtering of the passed = value, allows the user to bypass the target directory and write the result =
    of the comparison to any arbitrary path. This vulnerability is fixed in 0.1= 4.0.</td>
    <td>2026-06-24</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52797" target=3D= "_blank" rel=3D"noopener">CVE-2026-52797</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, althou=
    gh .ipynb previews are sanitized on the server side via /-/api/sanitize_ipy= nb, the inserted content is re-rendered on the client side without sanitiza= tion using marked() on elements with the .nb-markdown-cell class. During th=
    is process, links containing schemes such as javascript: can be regenerated=
    . As a result, when a victim views an attacker-crafted .ipynb file and clic=
    ks the link, arbitrary JavaScript is executed in the Gogs origin, leading t=
    o a click-based Stored XSS. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>8.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52798" target=3D= "_blank" rel=3D"noopener">CVE-2026-52798</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, organi= zation team member management can be performed via GET requests without CSR=
    F protection. If a victim who is an organization owner is logged in and is = tricked into visiting a crafted link, an attacker-controlled user can be ad= ded to the Owners team. As a result, the attacker gains organization owner-= equivalent privileges. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52800" target=3D= "_blank" rel=3D"noopener">CVE-2026-52800</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, the Go=
    gs Mirror Settings functionality provide an alternative way from the well p= rotected New Migration functionality for any authenticated users to import = local repositories. This issue stems from a lack of validation of SaveAddre=
    ss function. This vulnerability is fixed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52801" target=3D= "_blank" rel=3D"noopener">CVE-2026-52801</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, a Serv= er-Side Request Forgery (SSRF) vulnerability exists in the repository migra= tion functionality. The application validates only the initially submitted = URL hostname, but git clone --mirror follows HTTP redirects. An authenticat=
    ed user can submit a public URL that redirects to a blocked internal endpoi=
    nt (e.g., 127.0.0.1), importing the internal repository's contents into an = attacker-controlled repository. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>8.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52805" target=3D= "_blank" rel=3D"noopener">CVE-2026-52805</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, GET /a= ttachments/:uuid returns the raw attachment file without verifying whether = the requester has view permission for the associated Issue/Comment/Release =
    or the repository. In a test environment with REQUIRE_SIGNIN_VIEW =3D false=
    , we confirmed that an unauthenticated user can download attachments belong= ing to a private repository. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52799" target=3D= "_blank" rel=3D"noopener">CVE-2026-52799</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, three = API endpoints - PATCH /api/v1/repos/:owner/:repo/issue-tracker, PATCH /api/= v1/repos/:owner/:repo/wiki, and POST /api/v1/repos/:owner/:repo/mirror-sync=
    - are gated by reqRepoWriter() rather than reqRepoAdmin(). The equivalent = operations in the web UI sit behind reqRepoAdmin, which requires AccessMode=
    &gt;=3D AccessModeAdmin. A write-level collaborator (who has AccessMode = =3D=3D AccessModeWrite &lt; AccessModeAdmin) can therefore call these API e= ndpoints directly to disable the native issue tracker or wiki, inject attac= ker-controlled external tracker/wiki URLs that redirect all repository visi= tors, or trigger mirror sync - none of which they are authorized to do. Thi=
    s vulnerability is fixed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52808" target=3D= "_blank" rel=3D"noopener">CVE-2026-52808</a></td>
    </tr>

    <td class=3D"vendor-product">Google--AngularJS</td>
    <td>A flaw in AngularJS' Strict Contextual Escaping (SCE) logic allows bypa= ssing certain SCE policies for resource URLs and can lead to arbitrary Java= Script execution within the context of the victim's browser session. SCE's = purpose is to ensure that only trusted or safe values are used in certain s= ecurity-sensitive contexts, such as resource URLs, including URLs that defi=
    ne executable JavaScript scripts, '&lt;iframe&gt;' documents, route templat= es, etc. A flaw in the logic that tries to match entire URLs against regula=
    r expression matchers can result in partial matches for certain types of re= gular expressions, effectively bypassing the policies and allowing the use =
    of unsafe values as resource URLs. This issue affects AngularJS versions gr= eater than or equal to 1.2.0-rc.3. Note: The AngularJS project was already = End-of-Life when this CVE was published and will not receive any updates to=
    address this issue. For more information see the=C2=A0 End-of-Life announc= ement https://docs.angularjs.org/misc/version-support-status .</td> <td>2026-06-24</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11998" target=3D= "_blank" rel=3D"noopener">CVE-2026-11998</a></td>
    </tr>

    <td class=3D"vendor-product">Grafana--Grafana Enterprise</td>
    <td>The public dashboard query endpoint does not limit request body size be= fore processing, allowing unauthenticated attackers to trigger excessive me= mory allocation by sending arbitrarily large JSON payloads. This can lead t=
    o denial of service through memory exhaustion. No valid dashboard access to= ken or authentication is required to exploit this vulnerability.</td> <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42127" target=3D= "_blank" rel=3D"noopener">CVE-2026-42127</a></td>
    </tr>

    <td class=3D"vendor-product">Grafana--Grafana OSS</td>
    <td>The Loki datasource plugin's callResource handler contains a path trave= rsal vulnerability. An authenticated Viewer-role user can escape the plugin=
    's resource sandbox and access administrative Loki endpoints (e.g. /config,=
    /services, /ready) to extract sensitive backend configuration and internal=
    service information.</td>
    <td>2026-06-22</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42129" target=3D= "_blank" rel=3D"noopener">CVE-2026-42129</a></td>
    </tr>

    <td class=3D"vendor-product">Grafana--Grafana OSS</td>
    <td>The geomap panel's XYZ tile layer has a sanitize-then-interpolate order= ing bug. sanitizeTextPanelContent() runs on the raw template string before = getTemplateSrv().replace() substitutes the variable value, which uses the g= lob format with no HTML escaping. The result is passed to OpenLayers via el= ement.innerHTML. An Editor can set a textbox variable's default value to an=
    XSS payload that executes for every user who opens the dashboard. This is =
    a bypass of the CVE-2023-0507 fix</td>
    <td>2026-06-22</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9029" target=3D"= _blank" rel=3D"noopener">CVE-2026-9029</a></td>
    </tr>

    <td class=3D"vendor-product">Grafana--Snowflake Datasource</td>
    <td>The Snowflake datasource allows for GET/PUT commands, which can allow a=
    ny user with access to run queries against the data source to read/write fi= les between the local grafana server and the connected Snowflake host.</td> <td>2026-06-22</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-28381" target=3D= "_blank" rel=3D"noopener">CVE-2026-28381</a></td>
    </tr>

    <td class=3D"vendor-product">H.VIEW--HV-500S6 IP Camera</td>
    <td>A vulnerability exists in H.View IP cameras that could allow an authent= icated user to supply unsanitized XML fields to the device's certificate ge= neration interface, which are incorporated into a backend certificate creat= ion command without proper input validation. This may allow for command exe= cution with elevated privileges during certificate generation.</td> <td>2026-06-26</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55975" target=3D= "_blank" rel=3D"noopener">CVE-2026-55975</a></td>
    </tr>

    <td class=3D"vendor-product">H.VIEW--HV-500S6 IP Camera</td>
    <td>A vulnerability exists in H.View IP cameras certificate-related upload = interfaces allow authenticated users to store arbitrary file content to fix= ed, persistent filesystem locations without validating file type, structure=
    , or size. This design omission enables the placement of unexpected or malf= ormed data in locations intended for trusted certificate material, which co= uld affect system integrity or behavior even after reboot.</td> <td>2026-06-26</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56414" target=3D= "_blank" rel=3D"noopener">CVE-2026-56414</a></td>
    </tr>

    <td class=3D"vendor-product">H5P--H5P</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in H5P &lt;=3D 1.17.6 versio= ns.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56006" target=3D= "_blank" rel=3D"noopener">CVE-2026-56006</a></td>
    </tr>

    <td class=3D"vendor-product">haiwen--seahub</td>
    <td>Seahub before 13.0.23 does not enforce SHARE_LINK_LOGIN_REQUIRED on GET=
    /api/v2.1/share-link-zip-task/, allowing unauthenticated users to bypass a= uthentication. Attackers with a folder share-link token can call the GET en= dpoint to obtain a fileserver zip token and download entire shared director=
    y trees.</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56768" target=3D= "_blank" rel=3D"noopener">CVE-2026-56768</a></td>
    </tr>

    <td class=3D"vendor-product">hancock11--WP Forms Connector</td>
    <td>The WP Forms Connector plugin for WordPress is vulnerable to Informatio=
    n Exposure in all versions up to, and including, 1.8. The plugin registers = the REST route wp/v3/user/list/&lt;id&gt; (callback userDetail()) with perm= ission_callback set to '__return_true', and the function's home-grown authe= ntication only verifies that the supplied 'Username' HTTP header maps to an=
    administrator account and that a 'Password' HTTP header is non-empty. It n= ever validates the password with wp_check_password() (unlike the sibling de= lete_wc_user() function which does). This makes it possible for unauthentic= ated attackers to retrieve sensitive information for any registered user ID=
    - including the WordPress password hash (user_pass) and email address - by=
    sending a request with a valid administrator login name (commonly the defa= ult 'admin') and any arbitrary password value.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9178" target=3D"= _blank" rel=3D"noopener">CVE-2026-9178</a></td>
    </tr>

    <td class=3D"vendor-product">hancock11--WP Forms Connector</td>
    <td>The WP Forms Connector plugin for WordPress is vulnerable to SQL Inject= ion via the 'order' parameter of the /wp-json/wp/v3/post/list REST endpoint=
    in versions up to and including 1.8. This is due to insufficient escaping =
    on the user-supplied 'order' parameter (read directly from $_GET['order'] i= nto $shorting) and the lack of sufficient preparation on the existing SQL q= uery in the listPost() function, where the value is concatenated unquoted i= nto the ORDER BY clause and executed via $wpdb-&gt;get_results() without $w= pdb-&gt;prepare(). The endpoint is registered with permission_callback '__r= eturn_true' and performs only a broken header-based check that validates th=
    e supplied 'Username' corresponds to an administrator account while never v= erifying the 'Password'. This makes it possible for unauthenticated attacke=
    rs to append additional SQL queries into already existing queries that can =
    be used to extract sensitive information from the database.</td> <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9179" target=3D"= _blank" rel=3D"noopener">CVE-2026-9179</a></td>
    </tr>

    <td class=3D"vendor-product">hcengineering--platform</td>
    <td>Huly Platform through 0.7.423, fixed in commit 68cbf8a contains an auth= enticated server-side request forgery vulnerability in the /import endpoint=
    of front pod that allows workspace users to make arbitrary server requests=
    . Attackers can exploit this by supplying malicious URLs to fetch internal = services, exfiltrate responses, and replay credentials against backend syst= ems.</td>
    <td>2026-06-25</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56769" target=3D= "_blank" rel=3D"noopener">CVE-2026-56769</a></td>
    </tr>

    <td class=3D"vendor-product">HCLSoftware--Traveler for Microsoft Outlook</t=

    <td>HCL Traveler for Microsoft Outlook (HTMO) is susceptible to vulnerabili= ties due to .NET Framework 4.5 being out of service. =C2=A0Since .NET Frame= work 4.5 has reached end-of-life and no longer receives security updates, i=
    t may expose the application to publicly known security weaknesses through = vulnerable third-party components.</td>
    <td>2026-06-27</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2023-37524" target=3D= "_blank" rel=3D"noopener">CVE-2023-37524</a></td>
    </tr>

    <td class=3D"vendor-product">home-assistant--core</td>
    <td>Home Assistant is open source home automation software that puts local = control and privacy first. Prior to 2026.6.0, the Konnected integration reg= isters an HTTP endpoint, KonnectedView (homeassistant/components/konnected/= __init__.py), that is marked as not requiring authentication (requires_auth=
    =3D False). A comment next to that line says auth is instead handled "via = the access token from configuration." That promise is only half true. Write=
    requests (POST and PUT) are handled by update_sensor(), which does check t=
    he request's Authorization: Bearer &lt;token&gt; header against the integra= tion's stored access tokens (using hmac.compare_digest). Read requests (GET=
    ) are handled by a separate get() method that has no authentication check a=
    t all. This vulnerability is fixed in 2026.6.0.</td>
    <td>2026-06-23</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54317" target=3D= "_blank" rel=3D"noopener">CVE-2026-54317</a></td>
    </tr>

    <td class=3D"vendor-product">home-assistant--core</td>
    <td>Home Assistant is open source home automation software that puts local = control and privacy first. Prior to 2026.5.3, the LocationSensorManager Bro= adcastReceiver is exported with no permission. Any installed app, with zero=
    runtime permissions, can broadcast a forged Google Play Services LocationR= esult 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 A= ndroid's developer-mode "Mock Location" gate and allows a local malicious a=
    pp to drive zone-based automations (unlock door / disarm alarm / open garag=
    e) by faking the user's GPS position. This vulnerability is fixed in 2026.5= .3.</td>
    <td>2026-06-23</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54318" target=3D= "_blank" rel=3D"noopener">CVE-2026-54318</a></td>
    </tr>

    <td class=3D"vendor-product">honojs--hono</td>
    <td>Hono is a Web application framework that provides support for any JavaS= cript runtime. Prior to 4.12.25, with credentials: true and no explicit ori= gin (the default wildcard), the CORS Middleware reflects the request's Orig=
    in and sends Access-Control-Allow-Credentials: true. Any site can then make=
    credentialed cross-origin requests and read the responses, exposing cookie= -authenticated endpoints to arbitrary origins. This vulnerability is fixed =
    in 4.12.25.</td>
    <td>2026-06-22</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54290" target=3D= "_blank" rel=3D"noopener">CVE-2026-54290</a></td>
    </tr>

    <td class=3D"vendor-product">Hubbell--Aclara Metrum Cellular Web Interface<=

    <td>The Aclara Metrum Cellular Web Interface is vulnerable to unauthorized = access due to the absence of authentication controls on critical system fun= ctions. This weakness exposes essential configuration settings, allowing at= tackers to alter operational parameters and trigger system restarts without=
    restriction. Such unauthorized changes can disrupt normal functionality an=
    d, if performed repeatedly, may lead to a loss of communications to the dev= ice.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-1840" target=3D"= _blank" rel=3D"noopener">CVE-2026-1840</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--i</td>
    <td>IBM WebSphere Application Server and IBM WebSphere Application Server L= iberty - when using Intelligent Management with the WebSphere WebServer Plu= g-in component - are vulnerable to remote code execution and denial of serv= ice. This vulnerability can be exploited when an attacker impersonates back= end servers and sends crafted responses to the plug-in.</td> <td>2026-06-22</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9072" target=3D"= _blank" rel=3D"noopener">CVE-2026-9072</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--i</td>
    <td>IBM WebSphere Application Server and IBM WebSphere Application Server L= iberty are vulnerable to remote code execution and denial of service in the=
    WebSphere Web Server Plug-in component. This vulnerability can be exploite=
    d when an attacker impersonates the application server and sends crafted re= sponses to the plug-in.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8858" target=3D"= _blank" rel=3D"noopener">CVE-2026-8858</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Langflow OSS</td>
    <td>IBM Langflow OSS 1.0.0 through 1.9.3 has an vulnerability due to an imp= roper isolation of Python execution combined with an authentication bypass = that allows an unauthenticated attacker to execute arbitrary code on the ho=
    st system, resulting in complete compromise</td>
    <td>2026-06-22</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10561" target=3D= "_blank" rel=3D"noopener">CVE-2026-10561</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Langflow OSS</td>
    <td>IBM Langflow OSS 1.0.0 through 1.8.4 could allow unauthenticated attack= ers to access protected MCP project resources and execute MCP operations du=
    e to improper authorization enforcement in the Streamable MCP transport end= point.</td>
    <td>2026-06-22</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7664" target=3D"= _blank" rel=3D"noopener">CVE-2026-7664</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Storage Protect Client</td>
    <td>IBM Storage Protect Client 8.1.0.0 through 8.2.1.0 and IBM Storage Prot= ect Snapshot For Windows 8.1.0.0 through 8.2.1.0 could allow a remote attac= ker to bypass authentication due to the use of a hardcoded credential in th=
    e FlashCopy Manager (FCM) authentication mechanism. The application contain=
    s a static credential embedded in multiple authentication code paths, and d= oes not properly validate authentication responses, which may allow an unau= thenticated attacker to establish a trusted session and access protected se= rvices. This vulnerability affects client components across multiple versio=
    ns and may allow an attacker to impersonate legitimate clients, potentially=
    leading to unauthorized access to system resources.</td>
    <td>2026-06-22</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12628" target=3D= "_blank" rel=3D"noopener">CVE-2026-12628</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--WebSphere Application Server</td>
    <td>IBM WebSphere Application Server 9.0 and 8.5 and IBM WebSphere Applicat= ion Server - Liberty 17.0.0.3 through 26.0.0.6 are vulnerable to HTTP reque=
    st smuggling. A remote attacker could smuggle a specially crafted request t=
    o the application server thereby allowing the attacker to bypass security c= ontrols, spoof identity, escalate privilege, and expose sensitive informati= on.</td>
    <td>2026-06-22</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8646" target=3D"= _blank" rel=3D"noopener">CVE-2026-8646</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--WebSphere Application Server</td>
    <td>IBM WebSphere Application Server 9.0, and 8.5 is vulnerable to server-s= ide request forgery (SSRF) with the Ajax Proxy configured. This may allow a=
    n attacker to send unauthorized requests from the system, resulting in a se= curity bypass or information disclosure.</td>
    <td>2026-06-22</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9006" target=3D"= _blank" rel=3D"noopener">CVE-2026-9006</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--WebSphere Application Server</td>
    <td>IBM WebSphere Application Server 9.0, and 8.5 and IBM WebSphere Applica= tion Server - Liberty 17.0.0.3 through 26.0.0.6 are vulnerable to a denial =
    of service, caused by sending a specially-crafted request. A remote attacke=
    r could exploit this vulnerability to cause the server to consume memory re= sources.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9071" target=3D"= _blank" rel=3D"noopener">CVE-2026-9071</a></td>
    </tr>

    <td class=3D"vendor-product">icc0rz--H5P</td>
    <td>Contributor Arbitrary File Deletion in H5P &lt;=3D 1.17.7 versions.</td=

    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57321" target=3D= "_blank" rel=3D"noopener">CVE-2026-57321</a></td>
    </tr>

    <td class=3D"vendor-product">Igor Benic--Recipe Maker For Your Food Blog fr=
    om Zip Recipes</td>
    <td>Contributor SQL Injection in Recipe Maker For Your Food Blog from Zip R= ecipes &lt;=3D 8.2.7 versions.</td>
    <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57663" target=3D= "_blank" rel=3D"noopener">CVE-2026-57663</a></td>
    </tr>

    <td class=3D"vendor-product">immich-app--immich</td>
    <td>immich is a high performance self-hosted photo and video management sol= ution. From commit 4ffa26c9 until 4eb1003, a reflected cross-site scripting=
    (XSS) vulnerability on the /auth/login page allows an attacker to fully co= mpromise any authenticated user's account with a single link click. The con= tinue query parameter is read from the URL and passed to SvelteKit's redire= ct() without any scheme or origin validation, allowing attacker-controlled = JavaScript to execute inside Immich's origin. The payload then uses the vic= tim's existing session to mint an all-permission API key on their account, = leading to persistent account takeover. This vulnerability is fixed in comm=
    it 4eb1003.</td>
    <td>2026-06-23</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53662" target=3D= "_blank" rel=3D"noopener">CVE-2026-53662</a></td>
    </tr>

    <td class=3D"vendor-product">InspiryThemes--RealHomes</td>
    <td>Subscriber PHP Object Injection in RealHomes &lt;=3D 4.5.3 versions.</t=

    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56055" target=3D= "_blank" rel=3D"noopener">CVE-2026-56055</a></td>
    </tr>

    <td class=3D"vendor-product">Jacob N. Breetvelt--WP Photo Album Plus</td> <td>Improper Neutralization of Special Elements used in an SQL Command ('SQ=
    L Injection') vulnerability in Jacob N. Breetvelt WP Photo Album Plus allow=
    s Blind SQL Injection. This issue affects WP Photo Album Plus: from n/a thr= ough 9.1.13.005.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54829" target=3D= "_blank" rel=3D"noopener">CVE-2026-54829</a></td>
    </tr>

    <td class=3D"vendor-product">Jay Versluis--Child Theme Wizard</td> <td>Unauthenticated Cross Site Request Forgery (CSRF) in Child Theme Wizard=
    &lt;=3D 1.4 versions.</td>
    <td>2026-06-26</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57655" target=3D= "_blank" rel=3D"noopener">CVE-2026-57655</a></td>
    </tr>

    <td class=3D"vendor-product">jdx--mise</td>
    <td>mise manages dev tools like node, python, cmake, and terraform. Prior t=
    o 2026.3.10, mise processes .tool-versions files through the Tera template = engine during parsing, with the exec() function registered, enabling arbitr= ary command execution. Unlike .mise.toml files, .tool-versions files are no=
    t subject to trust verification in non-paranoid mode. This means an attacke=
    r can place a malicious .tool-versions file in a git repository, and when a=
    victim with mise activated cds into the directory, arbitrary commands exec= ute without any trust prompt. This vulnerability is fixed in 2026.3.10.</td=

    <td>2026-06-26</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-33646" target=3D= "_blank" rel=3D"noopener">CVE-2026-33646</a></td>
    </tr>

    <td class=3D"vendor-product">jdx--mise</td>
    <td>mise manages dev tools like node, python, cmake, and terraform. Prior t=
    o 2026.6.4, mise's trust feature gates config files (mise.toml, .tool-versi= ons) through trust_check, but task-include files are loaded on a path that = never reaches it. When a directory has a task-include dir (mise-tasks/, .mi= se/tasks/,=C2=A6) but no config file, mise falls back to the default includ=
    es and renders each task's tera fields - and that tera environment has exec=
    () registered. A {{ exec(command=3D=C2=A6') }} in any rendered field runs a= rbitrary commands the moment the tasks are merely listed. There's no config=
    file to gate on, so no trust prompt ever appears. Read-only commands trigg=
    er it: mise tasks, mise task ls, mise run, mise tasks --usage (the query sh= ell completion runs on Tab). The victim only has to cd into a cloned repo a=
    nd list or tab-complete a task. This vulnerability is fixed in 2026.6.4.</t=

    <td>2026-06-26</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55441" target=3D= "_blank" rel=3D"noopener">CVE-2026-55441</a></td>
    </tr>

    <td class=3D"vendor-product">Jegstudio--Gutenverse Companion</td> <td>Unauthenticated Broken Access Control in Gutenverse Companion &lt;=3D 2= .5.0 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54832" target=3D= "_blank" rel=3D"noopener">CVE-2026-54832</a></td>
    </tr>

    <td class=3D"vendor-product">jellyfin--jellyfin</td>
    <td>Jellyfin is an open source self hosted media server. Prior to 10.11.10,=
    a potential FFmpeg argument injection vulnerability exists in the subtitle=
    conversion code path. SubtitleEncoder.ConvertTextSubtitleToSrtInternal (Su= btitleEncoder.cs, line 382) interpolates the subtitle file path into FFmpeg=
    command-line arguments without calling EncodingUtils.NormalizePath(). On L= inux, filenames can contain double-quote characters, which break the argume=
    nt quoting and allow injection of arbitrary FFmpeg arguments. The vulnerabi= lity is reachable without authentication via SubtitleController.GetSubtitle=
    , which has no [Authorize] attribute. An attacker who can place a file in a=
    Jellyfin media library directory (shared NAS, Samba share, guest upload) c=
    an achieve arbitrary file write on the server and information disclosure. T= his vulnerability is fixed in 10.11.10.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48793" target=3D= "_blank" rel=3D"noopener">CVE-2026-48793</a></td>
    </tr>

    <td class=3D"vendor-product">jellyfin--jellyfin</td>
    <td>Jellyfin is an open source self hosted media server. From 10.9.0 until = 10.11.10, the POST /ClientLog/Document endpoint accepts the Authorization h= eader's Client and Version fields and uses them unsanitized as components o=
    f the on-disk filename when persisting client-uploaded log documents. As a = result, any authenticated non-admin user can include ../ sequences in the C= lient field to cause Jellyfin to write attacker-controlled content to arbit= rary paths reachable by the Jellyfin service user, with a forced .log suffi=
    x. This vulnerability is fixed in 10.11.10.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49247" target=3D= "_blank" rel=3D"noopener">CVE-2026-49247</a></td>
    </tr>

    <td class=3D"vendor-product">Jellywp--NanoMag</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in NanoMag &lt;=3D 1.8 versi= ons.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57325" target=3D= "_blank" rel=3D"noopener">CVE-2026-57325</a></td>
    </tr>

    <td class=3D"vendor-product">jetmonsters--Restaurant Menu by MotoPress</td> <td>Contributor SQL Injection in Restaurant Menu by MotoPress &lt;=3D 2.4.1=
    0 versions.</td>
    <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57644" target=3D= "_blank" rel=3D"noopener">CVE-2026-57644</a></td>
    </tr>

    <td class=3D"vendor-product">Johnson &amp; Johnson--Audit Tracking Manageme=
    nt System</td>
    <td>Johnson &amp; Johnson Audit Tracking Management System (ATMS) before 20= 26-04-21 allows viewing of meeting minutes and transcripts.</td> <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57913" target=3D= "_blank" rel=3D"noopener">CVE-2026-57913</a></td>
    </tr>

    <td class=3D"vendor-product">Johnson &amp; Johnson--Campus Recruiting</td> <td>Johnson &amp; Johnson Campus Recruiting before 2025-10-31 allows viewin=
    g of data provided by recruited students, and notes entered about students =
    by interviewers.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57912" target=3D= "_blank" rel=3D"noopener">CVE-2026-57912</a></td>
    </tr>

    <td class=3D"vendor-product">joomunited--WP Meta SEO</td>
    <td>The WP Meta SEO plugin for WordPress is vulnerable to Unauthenticated S= tored Cross-Site Scripting via the REQUEST_URI server variable in all versi= ons up to, and including, 4.5.18. When the plugin's `wpmsTemplateRedirect()=
    ` hook detects a 404, it concatenates `$_SERVER['HTTP_HOST']` with the raw = `$_SERVER['REQUEST_URI']` and inserts that value verbatim into the `wp_wpms= _links.link_url` column via `$wpdb-&gt;insert()`. This makes it possible fo=
    r unauthenticated attackers to inject arbitrary web scripts that execute wh= enever an administrator views the plugin's 404 &amp; Redirects admin page (= `/wp-admin/admin.php?page=3Dmetaseo_broken_link`).</td>
    <td>2026-06-24</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9643" target=3D"= _blank" rel=3D"noopener">CVE-2026-9643</a></td>
    </tr>

    <td class=3D"vendor-product">jqlang--jq</td>
    <td>jq is a command-line JSON processor. Prior to 1.8.2,` jq --rawfile` can=
    turn a handled oversized-string error into invalid-state reuse and a real = heap out-of-bounds write in assertion-disabled builds. When jv_load_file(ra= w=3D1) reads an attacker-controlled file, it repeatedly appends file chunks=
    to the same jv string accumulator. Once jv_string_append_buf() returns jv_= invalid_with_msg("String too long"), the raw-file loop does not stop. If th=
    e file contains at least one more byte, the next loop iteration appends a n=
    ew chunk to an object that is already invalid. With assertions enabled this=
    aborts in jvp_string_ptr(). With assertions disabled, the invalid object i=
    s interpreted as a string object and ASan reports heap-buffer-overflow. Thi=
    s vulnerability is fixed in 1.8.2.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49839" target=3D= "_blank" rel=3D"noopener">CVE-2026-49839</a></td>
    </tr>

    <td class=3D"vendor-product">kestra-io--kestra</td>
    <td>Kestra is an open-source, event-driven orchestration platform. Prior to=
    1.0.45 and 1.3.21, AuthenticationFilter in Kestra OSS uses request.getPath= ().endsWith("/configs") to whitelist the public configuration endpoint from=
    Basic Auth. Because the check is a suffix match rather than an exact path = match, any API path whose last segment is configs bypasses authentication e= ntirely. An unauthenticated remote attacker can exploit this to create and = execute arbitrary workflows without credentials. Because Kestra ships with = script execution plugins (plugin-script-shell, plugin-script-python, etc.) = enabled by default, this directly results in unauthenticated Remote Code Ex= ecution as root inside the Kestra worker container. This vulnerability is f= ixed in 1.0.45 and 1.3.21.</td>
    <td>2026-06-26</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49869" target=3D= "_blank" rel=3D"noopener">CVE-2026-49869</a></td>
    </tr>

    <td class=3D"vendor-product">kestra-io--kestra</td>
    <td>Kestra is an open-source, event-driven orchestration platform. Prior to=
    1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/a= pi/v1/**")) treats any request whose path ends in /configs as the public in= stance-config endpoint and forwards it without a credential check. kestra a= ddresses its resources by URL path segments that the caller chooses (/api/v= 1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id},=
    /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller pic=
    ks the literal configs as the final segment, and the request bypasses Basic= -Auth entirely. Because the bypass reaches the flow-create and execution-tr= igger routes, an unauthenticated caller creates a flow containing a Shell o=
    r Process task and runs it. The task executes as root inside the kestra con= tainer. The official docker-compose.yml mounts /var/run/docker.sock, so roo=
    t in the container reaches the host Docker daemon. This vulnerability is fi= xed in 1.0.45 and 1.3.21.</td>
    <td>2026-06-26</td>
    <td>10</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53576" target=3D= "_blank" rel=3D"noopener">CVE-2026-53576</a></td>
    </tr>

    <td class=3D"vendor-product">kestra-io--kestra</td>
    <td>Kestra is an open-source, event-driven orchestration platform. Prior to=
    1.3.24, this vulnerability exists in the BasicAuth authentication componen=
    t of the Kestra OSS workflow orchestration platform. An attacker who gains = read access to the PostgreSQL database can exploit SHA-512's high computati=
    on speed to recover the administrator password offline. In Kubernetes deplo= yments, a successful crack further enables reading of the cluster ServiceAc= count Token and all K8s Secrets, achieving vertical privilege escalation. T= his vulnerability is fixed in 1.3.24.</td>
    <td>2026-06-26</td>
    <td>8.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55069" target=3D= "_blank" rel=3D"noopener">CVE-2026-55069</a></td>
    </tr>

    <td class=3D"vendor-product">kestra-io--kestra</td>
    <td>Kestra is an open-source, event-driven orchestration platform. Prior to=
    1.0.43 and 1.3.19, several Kestra API endpoints accept a kestra:// URI fro=
    m the client and pass it through StorageInterface.parentTraversalGuard befo=
    re reading the underlying file from the local storage backend. The guard on=
    ly inspects the literal URI.toString(), so a URL-encoded .. written as %2E%=
    2E slips through. The downstream code then calls URI.getPath(), which decod=
    es %2E%2E back to .., and the resulting path is handed to Paths.get(...) wi= thout normalization. The OS resolves the .. segments at open(2) time, so an=
    authenticated user with a single execution can read any file the Kestra pr= ocess has access to on the host filesystem (/etc/passwd, mounted secrets, o= ther tenants' execution outputs, etc.). This vulnerability is fixed in 1.0.=
    43 and 1.3.19.</td>
    <td>2026-06-26</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45807" target=3D= "_blank" rel=3D"noopener">CVE-2026-45807</a></td>
    </tr>

    <td class=3D"vendor-product">kestra-io--kestra</td>
    <td>Kestra is an open-source, event-driven orchestration platform. Prior to=
    1.0.45 and 1.3.23, the local internal-storage backend validates user-suppl= ied paths for .. traversal before it converts Windows-style backslashes to = forward slashes. An attacker can therefore smuggle a traversal sequence pas=
    t the guard using backslashes (..\..\..\); the guard sees a harmless string=
    , and the path is only rewritten to ../../../ after validation, immediately=
    before the file is opened. Any authenticated user who can view an executio=
    n (the lowest-privilege role) can call GET /api/v1/{tenant}/executions/{exe= cutionId}/file?path=3D=C2=A6 and read any file on the server filesystem rea= dable by the Kestra process, outside the storage sandbox and across every t= enant and namespace. This includes the embedded H2 database (all flows, all=
    users, all stored secrets), internal storage of every other tenant/namespa= ce, mounted secret files, and the process environment (/proc/self/environ) = which contains configured database and secret-backend credentials. It is a = complete breach of Kestra's storage isolation and multi-tenancy boundary. T= his vulnerability is fixed in 1.0.45 and 1.3.23.</td>
    <td>2026-06-26</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49984" target=3D= "_blank" rel=3D"noopener">CVE-2026-49984</a></td>
    </tr>

    <td class=3D"vendor-product">kingaddons--Trinity Backup =E2=80=9C Backup, M= igrate, Restore, Clone &amp; Schedule Backups</td>
    <td>Unauthenticated Sensitive Data Exposure in Trinity Backup &amp;#8211; B= ackup, Migrate, Restore, Clone &amp;amp; Schedule Backups &lt;=3D 2.0.9 ver= sions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54839" target=3D= "_blank" rel=3D"noopener">CVE-2026-54839</a></td>
    </tr>

    <td class=3D"vendor-product">Kludex--python-multipart</td>
    <td>Python-Multipart is a streaming multipart parser for Python. Prior to 0= .0.30, when parsing application/x-www-form-urlencoded bodies, QuerystringPa= rser located the field separator with a two step lookup: it first scanned t=
    he entire remaining buffer for &amp;, and only when no &amp; existed anywhe=
    re ahead did it fall back to scanning for ;. For a body that uses ; as the = separator and contains no &amp;, every field iteration performed a full fai= led &amp; scan over the entire remaining buffer before locating the nearby =
    ;. With N semicolon separated fields in a chunk of size B, this yields O(B^=
    2) byte comparisons per chunk. An attacker can submit a small crafted body =
    of the form a;a;a;... and cause the parser to spend seconds of CPU per requ= est. A handful of concurrent requests can exhaust worker processes. This vu= lnerability is fixed in 0.0.30.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53539" target=3D= "_blank" rel=3D"noopener">CVE-2026-53539</a></td>
    </tr>

    <td class=3D"vendor-product">Kludex--starlette</td>
    <td>Starlette is a lightweight ASGI framework/toolkit. From 0.4.1 until 1.3= .1, request.form() accepts max_fields and max_part_size to bound resource c= onsumption while parsing form data. These limits are enforced for multipart= /form-data, but silently ignored for application/x-www-form-urlencoded. An = unauthenticated attacker can therefore send a urlencoded body with an arbit= rarily large number of fields or an arbitrarily large field, even when the = application configured limits it believed would apply. This vulnerability i=
    s fixed in 1.3.1.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54283" target=3D= "_blank" rel=3D"noopener">CVE-2026-54283</a></td>
    </tr>

    <td class=3D"vendor-product">labstack--echo</td>
    <td>Echo is a Go web framework. Prior to 4.15.3 and 5.2.0, Echo's router an=
    d static file handler disagree on URL path decoding. The router matches rou= tes using the raw encoded path (preserving %2F as-is), while StaticDirector= yHandler unescapes %2F to / before resolving filesystem paths. This allows =
    an attacker to bypass route-level access controls and read static files wit= hout authorization. This vulnerability is fixed in 4.15.3 and 5.2.0.</td> <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55677" target=3D= "_blank" rel=3D"noopener">CVE-2026-55677</a></td>
    </tr>

    <td class=3D"vendor-product">langflow-ai--langflow</td>
    <td>Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.9.2, the "Shareable Playground" (or "Public Flows" in co= de) contains a critical RCE vulnerability. Shareable Playground feature wor=
    ks by enabling the execution of workflows by unauthenticated users, by acce= ssing a link. Specifically, it enables the route /api/v1/build_public_tmp t=
    o execute any public flow, given a public flow ID. When the route executes = the flow, it allows for providing arbitrary custom Python code as the nodes=
    code, inside the JSON payload. The vulnerable field is data.nodes[X].data.= node.template.code.value. This vulnerability is fixed in 1.9.2.</td> <td>2026-06-23</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48519" target=3D= "_blank" rel=3D"noopener">CVE-2026-48519</a></td>
    </tr>

    <td class=3D"vendor-product">langflow-ai--langflow</td>
    <td>Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.9.2, an Insecure Direct Object Reference (IDOR) vulnerab= ility in /api/v1/responses endpoint allows an authenticated attacker to exe= cute any flow belonging to another user by specifying the victim's flow ID =
    in the request. This vulnerability is fixed in 1.9.2.</td>
    <td>2026-06-23</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55255" target=3D= "_blank" rel=3D"noopener">CVE-2026-55255</a></td>
    </tr>

    <td class=3D"vendor-product">langflow-ai--langflow</td>
    <td>Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.9.2, by controlling a files that are digested into the R= AG, an attacker can direct the node to read any file on the file-system by = absolute path. All components based on BaseFileComponent are vulnerable to = the vulnerability. This includes Docling (DoclingInlineComponent), Docling = Serve, DoclingRemoteComponent), Read File (FileComponent), NVIDIA Retriever=
    Extraction (NvidiaIngestComponent), Video File (VideoFileComponent), and U= nstructured API (UnstructuredComponent). This vulnerability is fixed in 1.9= .2.</td>
    <td>2026-06-23</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55447" target=3D= "_blank" rel=3D"noopener">CVE-2026-55447</a></td>
    </tr>

    <td class=3D"vendor-product">langflow-ai--langflow</td>
    <td>Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.9.1, unauthenticated users can upload any amount of data=
    to the server without any limitations. No need for any prior knowledge, on=
    ly network access to Langflow. This can lead to space exhaustion on the ser= ver. In addition, in the response, the absolute path of the uploaded file i=
    s reported to the attacker, which is an information leak that can assist in=
    chaining other primitives. This vulnerability is fixed in 1.9.1.</td> <td>2026-06-23</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55450" target=3D= "_blank" rel=3D"noopener">CVE-2026-55450</a></td>
    </tr>

    <td class=3D"vendor-product">langflow-ai--langflow</td>
    <td>Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.9.0, Langflow's /api/v1/monitor router exposes 7 endpoin=
    ts that perform read, write, and delete operations on user-owned resources =
    - messages, sessions, build artifacts, and LLM transaction logs - without v= erifying that the authenticated requester owns the targeted resource. Any a= uthenticated user can read, modify, rename, or permanently delete another u= ser's data by supplying the target's resource ID or flow_id. This is a clas= sic IDOR/BOLA vulnerability. Notably, the same source file (monitor.py) con= tains one correctly-implemented endpoint that uses an ownership check, demo= nstrating the correct pattern was known but inconsistently applied. This vu= lnerability is fixed in 1.9.0.</td>
    <td>2026-06-23</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-33760" target=3D= "_blank" rel=3D"noopener">CVE-2026-33760</a></td>
    </tr>

    <td class=3D"vendor-product">langflow-ai--langflow</td>
    <td>Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.0.19, an attacker can send a /api/v1/files/upload/ reque=
    st without any authentication token/cookies and abuse a very long multipart=
    form boundary to make the langflow app unusable for all users for an indef= inite amount of time. This vulnerability is fixed in 1.0.19.</td> <td>2026-06-23</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55446" target=3D= "_blank" rel=3D"noopener">CVE-2026-55446</a></td>
    </tr>

    <td class=3D"vendor-product">libssh2--libssh2</td>
    <td>libssh2 through 1.11.1 reads an attacker-controlled 32-bit attribute co= unt from a publickey-subsystem response and uses it in the allocation num_a= ttrs * sizeof(libssh2_publickey_attribute) without bounds checking, so on 3= 2-bit platforms the multiplication overflows to an undersized buffer. A mal= icious SSH server can then drive the attribute-parsing loop to write past t=
    he allocation, causing a heap buffer overflow in a connecting libssh2 clien= t.</td>
    <td>2026-06-28</td>
    <td>7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58050" target=3D= "_blank" rel=3D"noopener">CVE-2026-58050</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bat= man-adv: fix fragment reassembly length accounting batman-adv keeps a runni=
    ng payload length for queued fragments and uses it to validate a fragment c= hain before reassembly. That accounting currently allows the accumulated fr= agment length to be truncated during updates. As a result, malformed fragme=
    nt chains can bypass the intended validation and drive reassembly with inco= nsistent length state, leading to a local denial of service. Fix the accoun= ting by storing the accumulated length in a length-typed field and rejectin=
    g update overflows before the existing validation logic runs. The fix was v= erified against the original reproducer and against valid fragment reassemb=
    ly paths.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52914" target=3D= "_blank" rel=3D"noopener">CVE-2026-52914</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sct=
    p: purge outqueue on stale COOKIE-ECHO handling sctp_stream_update() is onl=
    y invoked when the association is moved into COOKIE_WAIT during association=
    setup/reconfiguration. In this path, the outbound stream scheduler state (= stream-&gt;out_curr) is expected to be clean, since no user data should hav=
    e been transmitted yet unless the state machine has already partially progr= essed. However, a corner case exists in sctp_sf_do_5_2_6_stale(): when a St= ale Cookie ERROR is received, the association is rolled back from COOKIE_EC= HOED to COOKIE_WAIT. In this scenario, user data may already have been queu=
    ed and even bundled with the COOKIE-ECHO chunk. During the rollback, sctp_s= tream_update() frees the old stream table and installs a new one, but it do=
    es not invalidate stream-&gt;out_curr. As a result, out_curr may still poin=
    t to a freed sctp_stream_out entry from the previous stream state. Later, S= CTP scheduler dequeue paths (FCFS, RR, PRIO, etc.) rely on stream-&gt;out_c= urr-&gt;ext, which can lead to use-after-free once the old stream state has=
    been released via sctp_stream_free(). This results in crashes such as (rep= orted by Yuqi): BUG: KASAN: slab-use-after-free in sctp_sched_fcfs_dequeue+= 0x13a/0x140 Read of size 8 at addr ff1100004d4d3208 by task mini_poc/9312 C= PU: 1 UID: 1001 PID: 9312 Comm: mini_poc Not tainted 7.1.0-rc1-00305-gbd3a4= 795d574 #5 PREEMPT(full) sctp_sched_fcfs_dequeue+0x13a/0x140 sctp_outq_flus= h+0x1603/0x33e0 sctp_do_sm+0x31c9/0x5d30 sctp_assoc_bh_rcv+0x392/0x6f0 sctp= _inq_push+0x1db/0x270 sctp_rcv+0x138d/0x3c10 Fix this by fully purging the = association outqueue when handling the Stale Cookie case. This ensures all = pending transmit and retransmit state is dropped, and any scheduler cached = pointers are invalidated, making it safe to rebuild stream state during COO= KIE_WAIT restart. Updating only stream-&gt;out_curr would be insufficient, = since queued and retransmittable data would still reference the old stream = state and trigger later use-after-free in dequeue paths.</td> <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52924" target=3D= "_blank" rel=3D"noopener">CVE-2026-52924</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bat= man-adv: tp_meter: avoid use of uninit sender vars batadv_tp_recv_ack() and=
    batadv_tp_stop() are only valid for tp_vars in the BATADV_TP_SENDER role. = When called with a BATADV_TP_RECEIVER role, it proceeds to read sender-only=
    members that were never initialized, leading to undefined behavior. This c=
    an be triggered when a node that is currently acting as a receiver in an on= going tp_meter session receives a malicious ACK packet. Guard against this =
    by checking tp_vars-&gt;role immediately after the lookup and bailing out i=
    f it is not BATADV_TP_SENDER, before any of those members are accessed.</td=

    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52931" target=3D= "_blank" rel=3D"noopener">CVE-2026-52931</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: lib= ceph: Fix potential out-of-bounds access in crush_decode() A message of typ=
    e CEPH_MSG_OSD_MAP containing a crush map with at least one bucket has two = fields holding the bucket algorithm. If the values in these two fields diff= er, an out-of-bounds access can occur. This is the case because the first a= lgorithm field (alg) is used to allocate the correct amount of memory for a=
    bucket of this type, while the second algorithm field inside the bucket (b= -&gt;alg) is used in the subsequent processing. This patch fixes the issue =
    by adding a check that compares alg and b-&gt;alg and aborts the processing=
    in case they differ. Furthermore, b-&gt;alg is set to 0 in this case, beca= use the destruction of the crush map also uses this field to determine the = bucket type, which can again result in an out-of-bounds access when trying =
    to free the memory pointed to by the fields of the bucket. To correctly fre=
    e the memory allocated for the bucket in such a case, the corresponding cal=
    l to kfree is moved from the algorithm-specific crush_destroy_bucket functi= ons to the generic crush_destroy_bucket().</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52955" target=3D= "_blank" rel=3D"noopener">CVE-2026-52955</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: lib= ceph: Fix potential out-of-bounds access in osdmap_decode() When decoding o= sd_state and osd_weight from an incoming osdmap in osdmap_decode(), both ar=
    e decoded for each osd, i.e., map-&gt;max_osd times. The ceph_decode_need()=
    check only accounts for sizeof(*map-&gt;osd_weight) once. This can potenti= ally result in an out-of-bounds memory access if the incoming message is co= rrupted such that the max_osd value exceeds the actual content of the osdma=
    p message. This patch fixes the issue by changing the corresponding part in=
    the ceph_decode_need() check to account for map-&gt;max_osd*sizeof(*map-&g= t;osd_weight).</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52958" target=3D= "_blank" rel=3D"noopener">CVE-2026-52958</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : usb: rtl8150: fix use-after-free in rtl8150_start_xmit() syzbot reported =
    a KASAN slab-use-after-free read in rtl8150_start_xmit() when accessing skb= -&gt;len for tx statistics after usb_submit_urb() has been called: BUG: KAS= AN: slab-use-after-free in rtl8150_start_xmit+0x71f/0x760 drivers/net/usb/r= tl8150.c:712 Read of size 4 at addr ffff88810eb7a930 by task kworker/0:4/52=
    26 The URB completion handler write_bulk_callback() frees the skb via dev_k= free_skb_irq(dev-&gt;tx_skb). The URB may complete on another CPU in softir=
    q context before usb_submit_urb() returns in the submitter, so by the time = the submitter reads skb-&gt;len the skb has already been queued to the per-= CPU completion_queue and freed by net_tx_action(): CPU A (xmit) CPU B (USB = completion softirq) ------------ ------------------------------ dev-&gt;tx_= skb =3D skb; usb_submit_urb() --+ |-------&gt; write_bulk_callback() | dev_= kfree_skb_irq(dev-&gt;tx_skb) | net_tx_action() | napi_skb_cache_put() &lt;=
    -- free netdev-&gt;stats.tx_bytes | +=3D skb-&gt;len; &lt;-- UAF read Fix i=
    t by caching skb-&gt;len before submitting the URB and using the cached val=
    ue when updating the tx_bytes counter. The pre-existing tx_bytes semantics = are preserved: the counter tracks the original frame length (skb-&gt;len), = not the ETH_ZLEN/USB-alignment padded "count" value that is handed to the d= evice. Changing that would be a user-visible accounting change and is out o=
    f scope for this UAF fix.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52982" target=3D= "_blank" rel=3D"noopener">CVE-2026-52982</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nf_conntrack_sip: don't use simple_strtoul Replace unsafe port pars= ing in epaddr_len(), ct_sip_parse_header_uri(), and ct_sip_parse_request() = with a new sip_parse_port() helper that validates each digit against the bu= ffer limit, eliminating the use of simple_strtoul() which assumes NUL-termi= nated strings. The previous code dereferenced pointers without bounds check=
    s after sip_parse_addr() and relied on simple_strtoul() on non-NUL-terminat=
    ed skb data. A port that reaches the buffer limit without a trailing charac= ter is also rejected as malformed. Also get rid of all simple_strtoul() usa=
    ge in conntrack, prefer a stricter version instead. There are intentional c= hanges: - Bail out if number is &gt; UINT_MAX and indicate a failure, same = for too long sequences. While we do accept 05535 as port 5535, we will not = accept e.g. 'sip:10.0.0.1:005060'. While its syntactically valid under RFC = 3261, we should restrict this to not waste cycles when presented with malfo= rmed packets with 64k '0' characters. - Force base 10 in ct_sip_parse_numer= ical_param(). This is used to fetch 'expire=3D' and 'rports=3D'; both are e= xpected to use base-10. - In nf_nat_sip.c, only accept the parsed value if = its within the 1k-64k range. - epaddr_len now returns 0 if the port is inva= lid, as it already does for invalid ip addresses. This is intentional. nf_c= onntrack_sip performs lots of guesswork to find the right parts of the mess= age to parse. Being stricter could break existing setups. Connection tracki=
    ng helpers are designed to allow traffic to pass, not to block it. Based on=
    an earlier patch from Jenny Guanni Qu &lt;qguanni@gmail.com&gt;.</td> <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52986" target=3D= "_blank" rel=3D"noopener">CVE-2026-52986</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: nvm= et-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers Current= ly, when nvmet_tcp_build_pdu_iovec() detects an out-of-bounds PDU length or=
    offset, it triggers nvmet_tcp_fatal_error(cmd-&gt;queue) and returns early=
    . However, because the function returns void, the callers are entirely unaw= are that a fatal error has occurred and that the cmd-&gt;recv_msg.msg_iter = was left uninitialized. Callers such as nvmet_tcp_handle_h2c_data_pdu() pro= ceed to blindly overwrite the queue state with queue-&gt;rcv_state =3D NVME= T_TCP_RECV_DATA Consequently, the socket receiving loop may attempt to read=
    incoming network data into the uninitialized iterator. Fix this by shiftin=
    g the error handling responsibility to the callers.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52989" target=3D= "_blank" rel=3D"noopener">CVE-2026-52989</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: tip=
    c: fix double-free in tipc_buf_append() tipc_msg_validate() can potentially=
    reallocate the skb it is validating, freeing the old one. In tipc_buf_appe= nd(), it was being called with a pointer to a local variable which was a co=
    py of the caller's skb pointer. If the skb was reallocated and validation s= ubsequently failed, the error handling path would free the original skb poi= nter, which had already been freed, leading to double-free. Fix this by che= cking if head now points to a newly allocated reassembled skb. If it does, = reassign *headbuf for later freeing operations.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52993" target=3D= "_blank" rel=3D"noopener">CVE-2026-52993</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nfnetlink_osf: fix out-of-bounds read on option matching In nf_osf_= match(), the nf_osf_hdr_ctx structure is initialized once and passed by ref= erence to nf_osf_match_one() for each fingerprint checked. During TCP optio=
    n parsing, nf_osf_match_one() advances the shared ctx-&gt;optp pointer. If =
    a fingerprint perfectly matches, the function returns early without restori=
    ng ctx-&gt;optp to its initial state. If the user has configured NF_OSF_LOG= LEVEL_ALL, the loop continues to the next fingerprint. However, because ctx= -&gt;optp was not restored, the next call to nf_osf_match_one() starts pars= ing from the end of the options buffer. This causes subsequent matches to r= ead garbage data and fail immediately, making it impossible to log more tha=
    n one match or logging incorrect matches. Instead of using a shared ctx-&gt= ;optp pointer, pass the context as a constant pointer and use a local point=
    er (optp) for TCP option traversal. This makes nf_osf_match_one() strictly = stateless from the caller's perspective, ensuring every fingerprint check s= tarts at the correct option offset.</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52999" target=3D= "_blank" rel=3D"noopener">CVE-2026-52999</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: conntrack: remove sprintf usage Replace it with scnprintf, the buff=
    er sizes are expected to be large enough to hold the result, no need for sn= printf+overflow check. Increase buffer size in mangle_content_len() while a=
    t it. BUG: KASAN: stack-out-of-bounds in vsnprintf+0xea5/0x1270 Write of si=
    ze 1 at addr [..] vsnprintf+0xea5/0x1270 sprintf+0xb1/0xe0 mangle_content_l= en+0x1ac/0x280 nf_nat_sdp_session+0x1cc/0x240 process_sdp+0x8f8/0xb80 proce= ss_invite_request+0x108/0x2b0 process_sip_msg+0x5da/0xf50 sip_help_tcp+0x45= e/0x780 nf_confirm+0x34d/0x990 [..]</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53002" target=3D= "_blank" rel=3D"noopener">CVE-2026-53002</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ipv=
    6: fix possible UAF in icmpv6_rcv() Caching saddr and daddr before pskb_pul= l() is problematic since skb-&gt;head can change. Remove these temporary va= riables: - We only access &amp;ipv6_hdr(skb)-&gt;saddr and &amp;ipv6_hdr(sk= b)-&gt;daddr when net_dbg_ratelimited() is called in the slow path. - Avoid=
    potential future misuse after pskb_pull() call.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53006" target=3D= "_blank" rel=3D"noopener">CVE-2026-53006</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ksm= bd: fix use-after-free in smb2_open during durable reconnect In smb2_open, = the call to ksmbd_put_durable_fd(fp) drops the reference to the durable fil=
    e descriptor early during the durable reconnect process. If an error occurs=
    subsequently (eg, ksmbd_iov_pin_rsp fails) or a scavenger accesses the fil=
    e, it leads to a use-after-free when accessing fp properties (eg fp-&gt;cre= ate_time). Move the single put to the end of the function below err_out2 so=
    fp stays valid until smb2_open returns.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53010" target=3D= "_blank" rel=3D"noopener">CVE-2026-53010</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ocf= s2/dlm: validate qr_numregions in dlm_match_regions() Patch series "ocfs2/d= lm: fix two bugs in dlm_match_regions()". In dlm_match_regions(), the qr_nu= mregions field from a DLM_QUERY_REGION network message is used to drive loo=
    ps over the qr_regions buffer without sufficient validation. This series fi= xes two issues: - Patch 1 adds a bounds check to reject messages where qr_n= umregions exceeds O2NM_MAX_REGIONS. The o2net layer only validates message = byte length; it does not constrain field values, so a crafted message can s=
    et qr_numregions up to 255 and trigger out-of-bounds reads past the 1024-by=
    te qr_regions buffer. - Patch 2 fixes an off-by-one in the local-vs-remote = comparison loop, which uses '&lt;=3D' instead of '&lt;', reading one entry = past the valid range even when qr_numregions is within bounds. This patch (=
    of 2): The qr_numregions field from a DLM_QUERY_REGION network message is u= sed directly as loop bounds in dlm_match_regions() without checking against=
    O2NM_MAX_REGIONS. Since qr_regions is sized for at most O2NM_MAX_REGIONS (= 32) entries, a crafted message with qr_numregions &gt; 32 causes out-of-bou= nds reads past the qr_regions buffer. Add a bounds check for qr_numregions = before entering the loops.</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53043" target=3D= "_blank" rel=3D"noopener">CVE-2026-53043</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mem= ory: tegra124-emc: Fix dll_change check The code checking whether the speci= fied memory timing enables DLL in the EMRS register was reversed. DLL is en= abled if bit A0 is low. Fix the check.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53045" target=3D= "_blank" rel=3D"noopener">CVE-2026-53045</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ksm= bd: fix use-after-free from async crypto on Qualcomm crypto engine ksmbd_cr= ypt_message() sets a NULL completion callback on AEAD requests and does not=
    handle the -EINPROGRESS return code from async hardware crypto engines lik=
    e the Qualcomm Crypto Engine (QCE). When QCE returns -EINPROGRESS, ksmbd tr= eats it as an error and immediately frees the request while the hardware DM=
    A operation is still in flight. The DMA completion callback then dereferenc=
    es freed memory, causing a NULL pointer crash: pc : qce_skcipher_done+0x24/= 0x174 lr : vchan_complete+0x230/0x27c ... el1h_64_irq+0x68/0x6c ksmbd_free_= work_struct+0x20/0x118 [ksmbd] ksmbd_exit_file_cache+0x694/0xa4c [ksmbd] Us=
    e the standard crypto_wait_req() pattern with crypto_req_done() as the comp= letion callback, matching the approach used by the SMB client in fs/smb/cli= ent/smb2ops.c. This properly handles both synchronous engines (immediate re= turn) and async engines (-EINPROGRESS followed by callback notification).</=

    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53046" target=3D= "_blank" rel=3D"noopener">CVE-2026-53046</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: gfs=
    2: add some missing log locking Function gfs2_logd() calls the log flushing=
    functions gfs2_ail1_start(), gfs2_ail1_wait(), and gfs2_ail1_empty() witho=
    ut holding sdp-&gt;sd_log_flush_lock, but these functions require exclusion=
    against concurrent transactions. To fix that, add a non-locking __gfs2_log= _flush() function. Then, in gfs2_logd(), take sdp-&gt;sd_log_flush_lock bef= ore calling the above mentioned log flushing functions and __gfs2_log_flush= ().</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53049" target=3D= "_blank" rel=3D"noopener">CVE-2026-53049</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: cry= pto: hisilicon/sec2 - prevent req used-after-free for sec During packet tra= nsmission, if the system is under heavy load, the hardware might complete p= rocessing the packet and free the request memory (req) before the transmiss= ion function finishes. If the software subsequently accesses this req, a us= e-after-free error will occur. The qp_ctx memory exists throughout the pack=
    et sending process, so replace the req with the qp_ctx.</td> <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53055" target=3D= "_blank" rel=3D"noopener">CVE-2026-53055</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : bcmgenet: fix racing timeout handler The bcmgenet_timeout handler tries t=
    o take down all tx queues when a single queue times out. This is over zealo=
    us and causes many race conditions with queues that are still chugging alon=
    g. Instead lets only restart the timed out queue.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53086" target=3D= "_blank" rel=3D"noopener">CVE-2026-53086</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : bcmgenet: fix off-by-one in bcmgenet_put_txcb The write_ptr points to the=
    next open tx_cb. We want to return the tx_cb that gets rewinded, so we mus=
    t rewind the pointer first then return the tx_cb that it points to. That wa=
    y the txcb can be correctly cleaned up.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53088" target=3D= "_blank" rel=3D"noopener">CVE-2026-53088</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: require Ethernet MAC header before using eth_hdr() `ip6t_eui64`, `x= t_mac`, the `bitmap:ip,mac`, `hash:ip,mac`, and `hash:mac` ipset types, and=
    `nf_log_syslog` access `eth_hdr(skb)` after either assuming that the skb i=
    s associated with an Ethernet device or checking only that the `ETH_HLEN` b= ytes at `skb_mac_header(skb)` lie between `skb-&gt;head` and `skb-&gt;data`=
    . Make these paths first verify that the skb is associated with an Ethernet=
    device, that the MAC header was set, and that it spans at least a full Eth= ernet header before accessing `eth_hdr(skb)`.</td>
    <td>2026-06-25</td>
    <td>9.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53131" target=3D= "_blank" rel=3D"noopener">CVE-2026-53131</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: rxr= pc: Fix the ACK parser to extract the SACK table for parsing Fix modificati=
    on of the received skbuff in rxrpc_input_soft_acks() and a potential incorr= ect access of the buffer in a fragmented UDP packet (the packet would proba= bly have to be deliberately pre-generated as fragmented) when AF_RXRPC trie=
    s to extract the contents of the SACK table by copying out the contents of = the SACK table into a buffer before attempting to parse AF_RXRPC assumes th=
    at it can just call skb_condense() and then validly access the SACK table f= rom skb-&gt;data and that it will be a flat buffer - but skb_condense() can=
    silently fail to do anything under some circumstances. Note that whilst rx= rpc_input_soft_acks() should be able to parse extended ACKs, the rest of AF= _RXRPC doesn't currently support that. Further, there's then no need to cal=
    l skb_condense() in rxrpc_input_ack(), so don't.</td>
    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53151" target=3D= "_blank" rel=3D"noopener">CVE-2026-53151</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ine=
    t: frags: fix use-after-free caused by the fqdir_pre_exit() flush On netns = teardown, fqdir_pre_exit() walks the fqdir rhashtable and flushes every fra= gment queue that is not yet complete using inet_frag_queue_flush(). That he= lper frees all the skbs queued on the fragment queue but does not set INET_= FRAG_COMPLETE, and leaves q-&gt;fragments_tail and q-&gt;last_run_head poin= ting at the freed skbs. The queue itself stays in the rhashtable. fqdir_pre= _exit() first lowers high_thresh to 0 to stop new queue lookups, but it can= not stop a fragment that already obtained the queue through inet_frag_find(=
    ) earlier and stalled just before taking the queue lock. Once that fragment=
    resumes after the flush and takes the queue lock, it passes the INET_FRAG_= COMPLETE check and then dereferences the freed fragments_tail. inet_frag_qu= eue_insert() reads FRAG_CB() and -&gt;len of that pointer and, on the appen=
    d path, writes -&gt;next_frag, causing a slab use-after-free. IPv6, nf_conn= track_reasm6 and 6lowpan reassembly share the same flush path and are affec= ted as well. Reset rb_fragments, fragments_tail and last_run_head in inet_f= rag_queue_flush() so a flushed queue no longer points at the freed skbs. A = fragment that resumes after the flush and takes the queue lock then finds a=
    n empty queue and starts a new run instead of dereferencing the freed fragm= ents_tail. ip_frag_reinit() already performed this reset after its own flus=
    h, so drop the now duplicate code there.</td>
    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53175" target=3D= "_blank" rel=3D"noopener">CVE-2026-53175</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: IB/= isert: Reject login PDUs shorter than ISER_HEADERS_LEN In drivers/infiniban= d/ulp/isert/ib_isert.c, isert_login_recv_done() computes the login request = payload length as wc-&gt;byte_len minus ISER_HEADERS_LEN with no lower boun=
    d, and login_req_len is a signed int. A remote iSER initiator can post a lo= gin Send work request carrying fewer than ISER_HEADERS_LEN (76) bytes, so t=
    he subtraction underflows and login_req_len becomes negative. isert_rx_logi= n_req() then reads that negative length back into a signed int, takes size = =3D min(rx_buflen, MAX_KEY_VALUE_PAIRS), and because the min() is signed it=
    keeps the negative value; the value is then passed as the memcpy() length = and sign-extended to a multi-gigabyte size_t. The copy into the 8192-byte l= ogin-&gt;req_buf runs far out of bounds and faults, crashing the target nod=
    e. The login phase precedes iSCSI authentication, so no credentials are req= uired to reach this path. Reject any login PDU shorter than ISER_HEADERS_LE=
    N before the subtraction, mirroring the existing early return on a failed w= ork completion, so login_req_len can never go negative. The upper bound was=
    already safe: a posted login buffer cannot deliver more than ISER_RX_PAYLO= AD_SIZE, so the difference stays at or below MAX_KEY_VALUE_PAIRS and the ex= isting min() clamps it; only the missing lower bound needs to be added.</td=

    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53176" target=3D= "_blank" rel=3D"noopener">CVE-2026-53176</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: RDM= A/srp: bound SRP_RSP sense copy by the received length srp_process_rsp() co= pies sense data from rsp-&gt;data + resp_data_len, where resp_data_len is t=
    he full 32-bit value supplied by the SRP target and is never checked agains=
    t the number of bytes actually received (wc-&gt;byte_len). The copy length =
    is bounded to SCSI_SENSE_BUFFERSIZE, so at most 96 bytes are copied, but th=
    e source offset is not bounded. A malicious or compromised SRP target on th=
    e InfiniBand/RoCE fabric that the initiator has logged into can return an S= RP_RSP with SRP_RSP_FLAG_SNSVALID set and a large resp_data_len. The receiv=
    e buffer is allocated at the target-chosen max_ti_iu_len, so the source of = the sense copy lands past the bytes actually received; with resp_data_len n= ear 0xFFFFFFFF it is gigabytes past the buffer and the read faults. Copy th=
    e sense data only if it has not been truncated, that is, only if the respon=
    se header, the response data, and the sense region fit within the bytes act= ually received; otherwise drop the sense and log. The in-tree iSER and NVMe= -RDMA receive paths already bound their parse by wc-&gt;byte_len; this brin=
    gs ib_srp into line with them.</td>
    <td>2026-06-25</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53186" target=3D= "_blank" rel=3D"noopener">CVE-2026-53186</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : mvpp2: refill RX buffers before XDP or skb use The RX error path returns = the current descriptor buffer to the hardware BM pool. That is only valid w= hile the driver still owns the buffer. mvpp2_rx_refill() can fail after the=
    current buffer has been handed to XDP or attached to an skb. In those case=
    s mvpp2_run_xdp() may have recycled, redirected, or queued the page for XDP= _TX, and an skb free also retires the data buffer. Returning such a buffer =
    to BM lets hardware DMA into memory that is no longer owned by the RX ring.=
    Refill the BM pool before handing the current buffer to XDP or to the skb.=
    If the allocation fails there, drop the packet and return the still-owned = current buffer to BM, preserving the pool depth. Once the refill succeeds, = later local drops retire/free the current buffer instead of returning it to=
    BM.</td>
    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53215" target=3D= "_blank" rel=3D"noopener">CVE-2026-53215</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : mvpp2: limit XDP frame size to the RX buffer mvpp2 has short and long BM = pools, and short pool buffers can be smaller than PAGE_SIZE. The XDP path n= evertheless initializes every xdp_buff with PAGE_SIZE as frame size. XDP he= lpers use frame_sz to validate tail growth and to derive the hard end of th=
    e data area. Advertising PAGE_SIZE for short buffers can let bpf_xdp_adjust= _tail() grow a packet past the real allocation, corrupting memory or later = tripping skb tailroom checks. Initialize the XDP buffer with bm_pool-&gt;fr= ag_size so XDP tailroom matches the actual buffer backing the packet.</td> <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53216" target=3D= "_blank" rel=3D"noopener">CVE-2026-53216</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ip6= _vti: fix incorrect tunnel matching in vti6_tnl_lookup() In vti6_tnl_lookup= (), when an exact match for a tunnel fails, the code falls back to searchin=
    g for wildcard tunnels: - Tunnels matching the packet's local address, with=
    any remote address wildcard remote). - Tunnels matching the packet's remot=
    e address, with any local address (wildcard local). However, vti6 stores al=
    l these different types of tunnels in the same hash table (ip6n-&gt;tnls_r_=
    l) prone to hash collisions. The bug is that the fallback search loops in v= ti6_tnl_lookup() were missing checks to ensure that the candidate tunnel ac= tually has a wildcard address.</td>
    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53221" target=3D= "_blank" rel=3D"noopener">CVE-2026-53221</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sct=
    p: validate embedded INIT chunk and address list lengths in cookie sctp_unp= ack_cookie() only checked that the embedded INIT chunk length did not excee=
    d the remaining cookie payload, but did not ensure that the INIT chunk is l= arge enough to contain a complete INIT header. A malformed COOKIE_ECHO can = therefore carry a truncated INIT chunk whose length field is smaller than s= izeof(struct sctp_init_chunk). Later, sctp_process_init() accesses INIT par= ameters unconditionally, which may lead to out-of-bounds reads. In addition=
    , raw_addr_list_len is not fully validated against the remaining cookie pay= load. When cookie authentication is disabled, an attacker can supply an ove= rsized raw_addr_list_len and cause sctp_raw_to_bind_addrs() to read beyond = the end of the cookie. The address parser also lacks sufficient bounds chec=
    ks for parameter headers and lengths, allowing malformed address parameters=
    to trigger out-of-bounds reads. Fix this by: - requiring the embedded INIT=
    chunk length to be at least sizeof(struct sctp_init_chunk); - validating t= hat the INIT chunk and raw address list together fit within the cookie payl= oad; - verifying sufficient data exists for each address parameter header a=
    nd payload before parsing it. Note that sctp_verify_init() must be called a= fter sctp_unpack_cookie() and before sctp_process_init() when cookie authen= tication is disabled. This will be addressed in a separate patch.</td> <td>2026-06-25</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53224" target=3D= "_blank" rel=3D"noopener">CVE-2026-53224</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sct=
    p: fix uninit-value in __sctp_rcv_asconf_lookup() __sctp_rcv_asconf_lookup(=
    ) in net/sctp/input.c only checks that the ASCONF chunk can hold the ADDIP = header and a parameter header, then calls af-&gt;from_addr_param(), which r= eads the full address (16 bytes for IPv6) trusting the parameter's declared=
    length. An unauthenticated peer can send a truncated trailing ASCONF chunk=
    that declares an IPv6 address parameter but stops after the 4-byte paramet=
    er header; reached from the no-association lookup path, from_addr_param() t= hen reads uninitialized bytes past the parameter. Impact: an unauthenticate=
    d SCTP peer makes the receive path read up to 16 bytes of uninitialized mem= ory past a truncated ASCONF address parameter. The sibling __sctp_rcv_init_= lookup() bounds parameters with sctp_walk_params(); this path open-codes th=
    e fetch and omits the bound. Verify the whole address parameter lies within=
    the chunk before from_addr_param() reads it, the same class of fix as comm=
    it 51e5ad549c43 ("net: sctp: fix KMSAN uninit-value in sctp_inq_pop").</td> <td>2026-06-25</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53225" target=3D= "_blank" rel=3D"noopener">CVE-2026-53225</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ipv=
    6: sit: reload inner IPv6 header after GSO offloads ipip6_tunnel_xmit() cac= hes the inner IPv6 header pointer at function entry and continues using it = after iptunnel_handle_offloads(). For GSO skbs, iptunnel_handle_offloads() = calls skb_header_unclone(). When the skb header is cloned, skb_header_unclo= ne() can call pskb_expand_head(), which may move the skb head. The pskb_exp= and_head() contract requires pointers into the skb header to be reloaded af= ter the call. If the later skb_realloc_headroom() branch is not taken, SIT = uses the stale iph6 pointer to read the inner hop limit and DS field. That = can read from a freed skb head after the old head's remaining clone is rele= ased. Reload iph6 after the offload helper succeeds and before subsequent r= eads from the inner IPv6 header. Keep the existing reload after skb_realloc= _headroom(), since that branch can also replace the skb.</td> <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53228" target=3D= "_blank" rel=3D"noopener">CVE-2026-53228</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sct=
    p: validate cached peer INIT chunk length in COOKIE_ECHO processing When a = listening SCTP server processes a COOKIE_ECHO chunk, the cached peer INIT c= hunk embedded after the cookie is parsed and its parameters are later walke=
    d by sctp_process_init() using sctp_walk_params(). However, the chunk heade=
    r length of this cached INIT chunk was not validated against the remaining = buffer in the COOKIE_ECHO payload. If the length field is inflated, the par= ameter walk can run beyond the actual received data, leading to out-of-boun=
    ds reads and potential memory corruption during later parameter handling (e= .g. STATE_COOKIE processing and kmemdup() copies). Add a bounds check in sc= tp_unpack_cookie() to ensure the cached INIT chunk length does not exceed t=
    he available data in the COOKIE_ECHO buffer before it is used.</td> <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53246" target=3D= "_blank" rel=3D"noopener">CVE-2026-53246</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : ethernet: mtk_eth_soc: Fix use-after-free in metadata dst teardown mtk_fr= ee_dev() calls metadata_dst_free() which frees the metadata_dst with kfree(=
    ) immediately, bypassing the RCU grace period. In the RX path, skb_dst_set_= noref() sets a non-refcounted pointer from the skb to the metadata_dst. Thi=
    s function requires RCU read-side protection and the dst must remain valid = until all RCU readers complete. Since metadata_dst_free() calls kfree() dir= ectly, a use-after-free can occur if any skb still holds a noref pointer to=
    the dst when the driver tears it down. Replace metadata_dst_free() with ds= t_release() which properly goes through the refcount path: when the refcoun=
    t drops to zero, it schedules the actual free via call_rcu_hurry(), ensurin=
    g all RCU readers have completed before the memory is freed.</td> <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53247" target=3D= "_blank" rel=3D"noopener">CVE-2026-53247</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: tcp=
    : Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req(). syzbot r= eported a weird reqsk-&gt;rsk_refcnt underflow in __inet_csk_reqsk_queue_dr= op(). The captured reqsk_put() in __inet_csk_reqsk_queue_drop() is called o= nly when it successfully removes reqsk from ehash. Moreover, reqsk_timer_ha= ndler() calls another reqsk_put() after that. This indicates that the reqsk=
    was missing both refcnts for ehash and the timer itself. Since all the syz= bot reports had PREEMPT_RT enabled, the only possible scenario is that reqs= k_queue_hash_req() is preempted after mod_timer() and before refcount_set()=
    , and then the timer triggered after 1s aborts the reqsk due to its listene= r's close(). Let's wrap mod_timer() and refcount_set() with preempt_disable= _nested() and preempt_enable_nested(). Note that inet_ehash_insert() holds = the normal spin_lock() (mutex in PREEMPT_RT), so it must be called outside =
    of preempt_disable_nested(), but this is fine. The lookup path just ignores=
    0 sk_refcnt entries in ehash and tries to create another reqsk, but this w= ill fail at inet_ehash_insert(). [0]: refcount_t: underflow; use-after-free=
    . WARNING: lib/refcount.c:28 at refcount_warn_saturate+0xb2/0x110 lib/refco= unt.c:28, CPU#0: ktimers/0/16 Modules linked in: CPU: 0 UID: 0 PID: 16 Comm=
    : ktimers/0 Tainted: G L syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=3DSO= FTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine,=
    BIOS Google 04/18/2026 RIP: 0010:refcount_warn_saturate+0xb2/0x110 lib/ref= count.c:28 Code: e4 7d d1 0a 67 48 0f b9 3a eb 4a e8 38 3d 23 fd 48 8d 3d e=
    1 7d d1 0a 67 48 0f b9 3a eb 37 e8 25 3d 23 fd 48 8d 3d de 7d d1 0a &lt;67&= gt; 48 0f b9 3a eb 24 e8 12 3d 23 fd 48 8d 3d db 7d d1 0a 67 48 0f RSP: 000= 0:ffffc90000157948 EFLAGS: 00010246 RAX: ffffffff84a1301b RBX: 000000000000= 0003 RCX: ffff88801ca98000 RDX: 0000000000000100 RSI: 0000000000000000 RDI:=
    ffffffff8f72ae00 RBP: ffffffff99ae3b01 R08: ffff88801ca98000 R09: 00000000= 00000005 R10: 0000000000000100 R11: 0000000000000004 R12: ffff8880425ef568 = R13: ffff8880425ef4f8 R14: ffff8880425ef578 R15: 0000000000000000 FS: 00000= 00000000000(0000) GS:ffff888126386000(0000) knlGS:0000000000000000 CS: 0010=
    DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7b46710e9c CR3: 0000000= 00dbb6000 CR4: 00000000003526f0 Call Trace: &lt;TASK&gt; __refcount_sub_and= _test include/linux/refcount.h:400 [inline] __refcount_dec_and_test include= /linux/refcount.h:432 [inline] refcount_dec_and_test include/linux/refcount= .h:450 [inline] reqsk_put include/net/request_sock.h:136 [inline] __inet_cs= k_reqsk_queue_drop+0x3ce/0x440 net/ipv4/inet_connection_sock.c:1007 reqsk_t= imer_handler+0x651/0xdf0 net/ipv4/inet_connection_sock.c:1137 call_timer_fn= +0x192/0x5e0 kernel/time/timer.c:1748 expire_timers kernel/time/timer.c:179=
    9 [inline] __run_timers kernel/time/timer.c:2374 [inline] __run_timer_base+= 0x6a3/0x9f0 kernel/time/timer.c:2386 run_timer_base kernel/time/timer.c:239=
    5 [inline] run_timer_softirq+0x67/0x170 kernel/time/timer.c:2403 handle_sof= tirqs+0x1de/0x6d0 kernel/softirq.c:622 __do_softirq kernel/softirq.c:656 [i= nline] run_ktimerd+0x69/0x100 kernel/softirq.c:1151 smpboot_thread_fn+0x541= /0xa50 kernel/smpboot.c:160 kthread+0x388/0x470 kernel/kthread.c:436 ret_fr= om_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x=
    30 arch/x86/entry/entry_64.S:245 &lt;/TASK&gt;</td>
    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53260" target=3D= "_blank" rel=3D"noopener">CVE-2026-53260</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ocf= s2/dlm: fix off-by-one in dlm_match_regions() region comparison The local-v= s-remote region comparison loop uses '&lt;=3D' instead of '&lt;', causing i=
    t to read one entry past the valid range of qr_regions. The other loops in = the same function correctly use '&lt;'. Fix the loop condition to use '&lt;=
    ' for consistency and correctness.</td>
    <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53309" target=3D= "_blank" rel=3D"noopener">CVE-2026-53309</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: serialize accept_q access bt_sock_poll() walks the accept queue wit= hout synchronization, while child teardown can unlink the same socket and d= rop its last reference. The unsynchronized accept queue walk has existed si= nce the initial Bluetooth import. Protect accept_q with a dedicated lock fo=
    r queue updates and polling. Also rework bt_accept_dequeue() to take tempor= ary child references under the queue lock before dropping it and locking th=
    e child socket.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52918" target=3D= "_blank" rel=3D"noopener">CVE-2026-52918</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: xt_policy: fix strict mode inbound policy matching match_policy_in(=
    ) walks sec_path entries from the last transform to the first one, but stri=
    ct policy matching needs to consume info-&gt;pol[] in the same forward orde=
    r as the rule layout. Derive the strict-match policy position from the numb=
    er of transforms already consumed so that multi-element inbound rules are m= atched consistently.</td>
    <td>2026-06-24</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52920" target=3D= "_blank" rel=3D"noopener">CVE-2026-52920</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bat= man-adv: tvlv: reject oversized TVLV packets batadv_tvlv_container_ogm_appe= nd() builds a TVLV packet section from the tvlv.container_list. The total s= ize of this section is computed by batadv_tvlv_container_list_size(), which=
    sums the sizes of all registered containers. The return type and accumulat=
    or in batadv_tvlv_container_list_size() were u16. If the accumulated size e= xceeds U16_MAX, the value wraps around, causing the subsequent allocation i=
    n batadv_tvlv_container_ogm_append() to be undersized. The memcpy-style cop=
    y that follows would then write beyond the end of the allocated buffer, cor= rupting kernel memory. Fix this by widening the return type of batadv_tvlv_= container_list_size() to size_t. In batadv_tvlv_container_ogm_append(), che=
    ck the computed length against U16_MAX before proceeding, and bail out as i=
    f the allocation had failed when the limit is exceeded.</td> <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52934" target=3D= "_blank" rel=3D"noopener">CVE-2026-52934</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= mu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset In __iomm= u_group_set_domain_internal(), concurrent domain attachments are rejected w= hen any device in the group is recovering. This is necessary to fence concu= rrent attachments to a multi-device group where devices might share the sam=
    e RID due to PCI DMA alias quirks, but triggers the WARN_ON in __iommu_grou= p_set_domain_nofail(). Other IOMMU_SET_DOMAIN_MUST_SUCCEED callers in detac= h/teardown paths, such as __iommu_group_set_core_domain and __iommu_release= _dma_ownership, should not be rejected, as the domain would be freed anyway=
    in these nofail paths while group-&gt;domain is still pointing to it. So p= ci_dev_reset_iommu_done() could trigger a UAF when re-attaching group-&gt;d= omain. Honor the IOMMU_SET_DOMAIN_MUST_SUCCEED flag, allowing the callers t= hrough the group-&gt;recovery_cnt fence, so as to update the group-&gt;doma=
    in pointer. Instead add a gdev-&gt;blocked check in the device iteration lo= op, to prevent any concurrent per-device detachment.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52952" target=3D= "_blank" rel=3D"noopener">CVE-2026-52952</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: smb= /client: fix possible infinite loop and oob read in symlink_data() On 32-bi=
    t architectures, the infinite loop is as follows: len =3D p-&gt;ErrorDataLe= ngth =3D=3D 0xfffffff8 u8 *next =3D p-&gt;ErrorContextData + len next =3D=
    =3D p On 32-bit architectures, the out-of-bounds read is as follows: len =
    =3D p-&gt;ErrorDataLength =3D=3D 0xfffffff0 u8 *next =3D p-&gt;ErrorContext= Data + len next =3D=3D (u8 *)p - 8</td>
    <td>2026-06-24</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52967" target=3D= "_blank" rel=3D"noopener">CVE-2026-52967</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= mu/amd: Fix clone_alias() to use the original device's devid Currently clon= e_alias() assumes first argument (pdev) is always the original device point= er. This function is called by pci_for_each_dma_alias() which based on topo= logy decides to send original or alias device details in first argument. Th=
    is meant that the source devid used to look up and copy the DTE may be inco= rrect, leading to wrong or stale DTE entries being propagated to alias devi= ce. Fix this by passing the original pdev as the opaque data argument to bo=
    th the direct clone_alias() call and pci_for_each_dma_alias(). Inside clone= _alias(), retrieve the original device from data and compute devid from it.= </td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53053" target=3D= "_blank" rel=3D"noopener">CVE-2026-53053</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= mu/riscv: Add IOTINVAL after updating DDT/PDT entries Add riscv_iommu_iodir= _iotinval() to perform required TLB and context cache invalidations after u= pdating DDT or PDT entries, as mandated by the RISC-V IOMMU specification (= Section 6.3.1 and 6.3.2).</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53057" target=3D= "_blank" rel=3D"noopener">CVE-2026-53057</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp l2cap_ecred_= reconf_rsp() calls l2cap_chan_del() without holding l2cap_chan_lock(). Ever=
    y other l2cap_chan_del() caller in the file acquires the lock first. A remo=
    te BLE device can send a crafted L2CAP ECRED reconfiguration response to co= rrupt the channel list while another thread is iterating it. Add l2cap_chan= _hold() and l2cap_chan_lock() before l2cap_chan_del(), and l2cap_chan_unloc= k() and l2cap_chan_put() after, matching the pattern used in l2cap_ecred_co= nn_rsp() and l2cap_conn_del().</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53071" target=3D= "_blank" rel=3D"noopener">CVE-2026-53071</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER When pro= tocol sets HCI_PROTO_DEFER, hci_conn_request_evt() calls hci_connect_cfm(co= nn) without hdev-&gt;lock. Generally hci_connect_cfm() assumes it is held, = and if conn is deleted concurrently -&gt; UAF. Only SCO and ISO set HCI_PRO= TO_DEFER and only for defer setup listen, and HCI_EV_CONN_REQUEST is not ge= nerated for ISO. In the non-deferred listening socket code paths, hci_conne= ct_cfm(conn) is called with hdev-&gt;lock held. Fix by holding the lock.</t=

    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53072" target=3D= "_blank" rel=3D"noopener">CVE-2026-53072</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ppp=
    : require CAP_NET_ADMIN in target netns for unattached ioctls /dev/ppp open=
    is currently authorized against file-&gt;f_cred-&gt;user_ns, while unattac= hed administrative ioctls operate on current-&gt;nsproxy-&gt;net_ns. As a r= esult, a local unprivileged user can create a new user namespace with CLONE= _NEWUSER, gain CAP_NET_ADMIN only in that new user namespace, and still iss=
    ue PPPIOCNEWUNIT, PPPIOCATTACH, or PPPIOCATTCHAN against an inherited netwo=
    rk namespace. Require CAP_NET_ADMIN in the user namespace that owns the tar= get network namespace before handling unattached PPP administrative ioctls.=
    This preserves normal pppd operation in the network namespace it is actual=
    ly privileged in, while rejecting the userns-only inherited-netns case.</td=

    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53075" target=3D= "_blank" rel=3D"noopener">CVE-2026-53075</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : pull headers in qdisc_pkt_len_segs_init() Most ndo_start_xmit() methods e= xpects headers of gso packets to be already in skb-&gt;head. net/core/tso.c=
    users are particularly at risk, because tso_build_hdr() does a memcpy(hdr,=
    skb-&gt;data, hdr_len); qdisc_pkt_len_segs_init() already does a dissectio=
    n of gso packets. Use pskb_may_pull() instead of skb_header_pointer() to ma=
    ke sure drivers do not have to reimplement this. Some malicious packets cou=
    ld be fed, detect them so that we can drop them sooner with a new SKB_DROP_= REASON_SKB_BAD_GSO drop_reason.</td>
    <td>2026-06-24</td>
    <td>8.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53091" target=3D= "_blank" rel=3D"noopener">CVE-2026-53091</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: thu= nderbolt: Validate XDomain request packet size before type cast tb_xdp_hand= le_request() casts the received packet buffer to protocol-specific structs = without verifying that the allocation is large enough for the target type. =
    A peer can send a minimal XDomain packet that passes the generic header len= gth check but is shorter than the struct accessed after the cast, causing o= ut-of- bounds reads from the kmemdup allocation. Plumb the packet length th= rough xdomain_request_work and validate it against the expected struct size=
    before each cast.</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53147" target=3D= "_blank" rel=3D"noopener">CVE-2026-53147</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: acc= el/ethosu: reject DMA commands with uninitialized length cmd_state_init() i= nitializes the command state with memset(0xff), leaving dma-&gt;len at U64_= MAX to signal missing setup. The only setter is NPU_SET_DMA0_LEN; if usersp= ace omits this command and issues NPU_OP_DMA_START, dma-&gt;len remains U64= _MAX. In dma_length(), a positive stride added to U64_MAX wraps to a small = value. With size0 =3D=3D 1, check_mul_overflow() does not trigger and dma_l= ength() returns 0 instead of U64_MAX. The caller's U64_MAX check then passe=
    s, region_size[] stays 0, and the bounds check in ethosu_job.c is bypassed,=
    allowing hardware to execute DMA with stale physical addresses. Fix by che= cking for U64_MAX at the start of dma_length() before any arithmetic, consi= stent with the sentinel value used throughout the driver to detect uninitia= lized fields.</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53170" target=3D= "_blank" rel=3D"noopener">CVE-2026-53170</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: acc= el/ethosu: fix arithmetic issues in dma_length() dma_length() derives DMA r= egion usage from command stream values and updates region_size[]: len =3D (= (len + stride[0]) * size0 + stride[1]) * size1 region_size[region] =3D max(= ..., len + dma-&gt;offset) Several arithmetic issues can corrupt the derive=
    d region size: - signed stride values may underflow when added to len - int= ermediate multiplications may overflow - len + dma-&gt;offset may overflow = during region_size updates - dma_length() error returns were not validated =
    by the caller region_size[] is later used by ethosu_job.c to validate comma=
    nd stream accesses against GEM buffer sizes. Arithmetic wraparound can ther= efore under-report region usage and bypass the bounds validation. Fix by va= lidating signed additions, using overflow helpers for multiplications and o= ffset updates, and propagating dma_length() failures to the caller.</td> <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53171" target=3D= "_blank" rel=3D"noopener">CVE-2026-53171</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sta= ging: rtl8723bs: rtw_mlme: add bounds checks before ie_length subtraction A=
    dd guards to ensure ie_length is large enough before subtracting fixed IE o= ffsets to prevent unsigned integer underflow.</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53178" target=3D= "_blank" rel=3D"noopener">CVE-2026-53178</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: RDM= A/core: Validate the passed in fops for ib_get_ucaps() Sashiko pointed out =
    it is not safe to rely only on the devt because char/block alias so if the = user finds a block device with the same dev_t it can masquerade as a ucap c= dev fd. Test the f_ops to only accept authentic cdevs.</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53188" target=3D= "_blank" rel=3D"noopener">CVE-2026-53188</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ksm= bd: fix use-after-free of a deferred file_lock on double SMB2_CANCEL A defe= rred byte-range lock (an SMB2_LOCK that blocks) registers an async work on = conn-&gt;async_requests via setup_async_work(), with cancel_fn =3D smb2_rem= ove_blocked_lock and cancel_argv[0] pointing at the struct file_lock. When = the request is cancelled, the worker frees the file_lock with locks_free_lo= ck() and takes the cancelled early-exit, which "goto out"s and never reache=
    s release_async_work() -- the only site that unlinks the work from conn-&gt= ;async_requests and clears cancel_fn/cancel_argv. The work therefore stays = matchable on async_requests with a live cancel_fn pointing at the freed fil= e_lock, until connection teardown finally runs release_async_work(). smb2_c= ancel() fires cancel_fn unconditionally with no state guard, so a second SM= B2_CANCEL for the same AsyncId, arriving in that window, re-runs smb2_remov= e_blocked_lock() on the freed file_lock -- a slab use-after-free: BUG: KASA=
    N: slab-use-after-free in __locks_delete_block __locks_delete_block locks_d= elete_block ksmbd_vfs_posix_lock_unblock smb2_remove_blocked_lock smb2_canc=
    el &lt;- 2nd SMB2_CANCEL fires cancel_fn handle_ksmbd_work Allocated by ...=
    : locks_alloc_lock &lt;- smb2_lock Freed by ...: locks_free_lock &lt;- smb2= _lock (cancelled branch) ... cache file_lock_cache of size 192 Reproduced o=
    n mainline with KASAN by an authenticated SMB client. Skip a work whose sta=
    te is already KSMBD_WORK_CANCELLED so its cancel callback cannot be fired a=
    second time.</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53198" target=3D= "_blank" rel=3D"noopener">CVE-2026-53198</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: KVM=
    : arm64: nv: Fix handling of XN[0] when !FEAT_XNX XN has already been extra= cted from its bitfield position so using FIELD_PREP() on the mask that clea=
    rs XN[0] is completely broken, having the effect of unconditionally grantin=
    g execute permissions... Fix the obvious mistake by manipulating the right = bit.</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53200" target=3D= "_blank" rel=3D"noopener">CVE-2026-53200</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : mvpp2: sync RX data at the hardware packet offset mvpp2 programs the RX q= ueue packet offset, so hardware writes received data at dma_addr + MVPP2_SK= B_HEADROOM. The current CPU sync starts at dma_addr and only covers rx_byte=
    s + MVPP2_MH_SIZE bytes, which syncs the unused headroom and misses the sam=
    e number of bytes at the packet tail. On non-coherent DMA systems this can = leave the CPU reading stale cache contents for the end of the received fram=
    e. Use dma_sync_single_range_for_cpu() with MVPP2_SKB_HEADROOM as the range=
    offset so the sync covers the Marvell header and packet data actually writ= ten by hardware.</td>
    <td>2026-06-25</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53217" target=3D= "_blank" rel=3D"noopener">CVE-2026-53217</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /mlx5: Fix slab-out-of-bounds in mlx5_query_nic_vport_mac_list mlx5_query_n= ic_vport_mac_list() sizes its firmware command buffer using the PF's log_ma= x_current_uc/mc_list capabilities. When querying a VF vport with a larger c= onfigured max (via devlink), the firmware response can overflow this buffer=
    : BUG: KASAN: slab-out-of-bounds in mlx5_query_nic_vport_mac_list+0x453/0x4=
    c0 [mlx5_core] Read of size 4 at addr ff1100013ffc8a12 by task kworker/u96:= 2/385 CPU: 12 UID: 0 PID: 385 Comm: kworker/u96:2 Not tainted 7.0.0-rc6+ #1=
    PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009) Workqueue: mlx5= _esw_wq esw_vport_change_handler [mlx5_core] Call Trace: &lt;TASK&gt; dump_= stack_lvl+0x69/0xa0 print_report+0x176/0x4e4 kasan_report+0xc8/0x100 mlx5_q= uery_nic_vport_mac_list+0x453/0x4c0 [mlx5_core] esw_update_vport_addr_list+= 0x2e3/0xda0 [mlx5_core] esw_vport_change_handle_locked+0xa1f/0x1060 [mlx5_c= ore] esw_vport_change_handler+0x6a/0x90 [mlx5_core] process_one_work+0x87f/= 0x15e0 worker_thread+0x62b/0x1020 kthread+0x375/0x490 ret_from_fork+0x4dc/0= x810 ret_from_fork_asm+0x11/0x20 &lt;/TASK&gt; Fix by querying the vport's = own HCA caps to size the buffer correctly. Refactor the function to allocat=
    e and return the MAC list internally, removing the caller's dependency on k= nowing the correct max.</td>
    <td>2026-06-25</td>
    <td>8.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53230" target=3D= "_blank" rel=3D"noopener">CVE-2026-53230</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : phy: clean the sfp upstream if phy probing fails Sashiko reported that we=
    don't call sfp_bus_del_upstream() in the probe failure path, so let's add = it, otherwise the sfp-bus is left with a dangling 'upstream' field, that ma=
    y be used later on during SFP events. This issue existed before the generic=
    phylib sfp support, back when drivers were calling phy_sfp_probe themselve= s.</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53232" target=3D= "_blank" rel=3D"noopener">CVE-2026-53232</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: xfr=
    m: iptfs: fix use-after-free on first_skb in __input_process_payload __inpu= t_process_payload() stores first_skb into xtfs-&gt;ra_newskb under drop_loc=
    k when starting partial reassembly, then unlocks and breaks out of the proc= essing loop. The post-loop check reads xtfs-&gt;ra_newskb without the lock =
    to decide whether first_skb is still owned: if (first_skb &amp;&amp; first_= iplen &amp;&amp; !defer &amp;&amp; first_skb !=3D xtfs-&gt;ra_newskb) Betwe=
    en spin_unlock and this read, a concurrent CPU running iptfs_reassem_cont()=
    (or the drop_timer hrtimer) can complete reassembly, NULL xtfs-&gt;ra_news= kb, and free the skb. The check then evaluates first_skb !=3D NULL as true,=
    and pskb_trim/ip_summed/consume_skb operate on the freed skb - a use-after= -free in skbuff_head_cache. Replace the unlocked read with a local bool tha=
    t records whether first_skb was handed to the reassembly state in the curre=
    nt call. The flag is set after the existing spin_unlock, before the break, = using the pointer equality that is stable at that point (first_skb =3D=3D s=
    kb iff first_skb was stored in ra_newskb).</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53240" target=3D= "_blank" rel=3D"noopener">CVE-2026-53240</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : airoha: Fix use-after-free in metadata dst teardown airoha_metadata_dst_f= ree() runs metadata_dst_free() which frees the metadata_dst with kfree() im= mediately, bypassing the RCU grace period. In the RX path, skb_dst_set_nore= f() sets a non-refcounted pointer from the skb to the metadata_dst. This fu= nction requires RCU read-side protection and the dst must remain valid unti=
    l all RCU readers complete. Since metadata_dst_free() calls kfree() directl=
    y, an use-after-free can occur if any skb still holds a noref pointer to th=
    e dst when the driver tears it down. Replace metadata_dst_free() with dst_r= elease() which properly goes through the refcount path: when the refcount d= rops to zero, it schedules the actual free via call_rcu_hurry(), ensuring a=
    ll RCU readers have completed before the memory is freed.</td> <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53248" target=3D= "_blank" rel=3D"noopener">CVE-2026-53248</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: RFCOMM: validate skb length in MCC handlers The RFCOMM MCC handlers=
    cast skb-&gt;data to protocol-specific structs without validating skb-&gt;= len first. A malicious remote device can send truncated MCC frames and trig= ger out-of-bounds reads in these handlers. Fix this by using skb_pull_data(=
    ) to validate and access the required data before dereferencing it. rfcomm_= recv_rpn() requires special handling since ETSI TS 07.10 allows 1-byte RPN = requests. Handle this by validating only the DLCI byte first, and validatin=
    g the full struct only when len &gt; 1.</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53254" target=3D= "_blank" rel=3D"noopener">CVE-2026-53254</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: RFCOMM: hold listener socket in rfcomm_connect_ind() rfcomm_get_soc= k_by_channel() scans rfcomm_sk_list under the list lock, but returns the se= lected listener after dropping that lock without taking a reference. rfcomm= _connect_ind() then locks the listener, queues a child socket on it, and ma=
    y notify it after unlocking it. The buggy scenario involves two paths, with=
    each column showing the order within that path: rfcomm_connect_ind(): list= ener close: 1. Find parent in 1. close() enters rfcomm_get_sock_by_channel(=
    ) rfcomm_sock_release(). 2. Drop rfcomm_sk_list.lock 2. rfcomm_sock_shutdow= n() without pinning parent. closes the listener. 3. Call lock_sock(parent) = and 3. rfcomm_sock_kill() bt_accept_enqueue(parent, unlinks and puts parent=
    . sk, true). 4. Read parent flags and may 4. parent can be freed. call sk_s= tate_change(). If close wins the race, parent can be freed before rfcomm_co= nnect_ind() reaches lock_sock(), bt_accept_enqueue(), or the deferred-setup=
    callback. Take a reference on the listener before leaving rfcomm_sk_list.l= ock. After lock_sock() succeeds, recheck that it is still in BT_LISTEN befo=
    re queueing a child, cache the deferred-setup bit while the parent is locke=
    d, and drop the reference after the last parent use. KASAN reported a slab-= use-after-free in lock_sock_nested() from rfcomm_connect_ind(), with the fr= eeing stack going through rfcomm_sock_kill() and rfcomm_sock_release().</td=

    <td>2026-06-25</td>
    <td>8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53256" target=3D= "_blank" rel=3D"noopener">CVE-2026-53256</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: bridge: make ebt_snat ARP rewrite writable The ebtables SNAT target=
    keeps the Ethernet source address rewrite behind skb_ensure_writable(skb, = 0). This is intentional: at the bridge ebtables hooks the Ethernet header i=
    s addressed through skb_mac_header()/eth_hdr(), while skb-&gt;data points a=
    t the Ethernet payload. Asking skb_ensure_writable() for ETH_HLEN bytes wou=
    ld check the payload, not the Ethernet header, and would reintroduce the sm= all packet regression fixed by commit 63137bc5882a. However, the optional A=
    RP sender hardware address rewrite is different. It writes through skb_stor= e_bits() at an offset relative to skb-&gt;data: skb_store_bits(skb, sizeof(= struct arphdr), info-&gt;mac, ETH_ALEN) skb_header_pointer() only safely re= ads the ARP header; it does not make the later sender hardware address rang=
    e writable. If that range is still held in a nonlinear skb fragment backed =
    by a splice-imported file page, skb_store_bits() maps the frag page and cop= ies the new MAC address directly into it. Ensure the ARP SHA range is writa= ble before reading the ARP header and before calling skb_store_bits().</td> <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53266" target=3D= "_blank" rel=3D"noopener">CVE-2026-53266</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: conntrack_irc: fix possible out-of-bounds read When parsing fails a= fter we've matched the command string we should bail out instead of trying =
    to match a different command. This helper should be deprecated, given preva= lence of TLS I doubt it has any relevance in 2026.</td>
    <td>2026-06-25</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53268" target=3D= "_blank" rel=3D"noopener">CVE-2026-53268</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ipv=
    6: mcast: Fix use-after-free when processing MLD queries When processing an=
    MLD query, a pointer to the multicast group address is retrieved when init= ially parsing the packet. This pointer is later dereferenced without being = reloaded despite the fact that the skb header might have been reallocated f= ollowing the pskb_may_pull() calls, leading to a use-after-free [1]. Fix by=
    copying the multicast group address when the packet is initially parsed. [=
    1] BUG: KASAN: slab-use-after-free in __mld_query_work (net/ipv6/mcast.c:15= 12) Read of size 8 at addr ffff8881154b8e90 by task kworker/4:1/118 Workque= ue: mld mld_query_work Call Trace: &lt;TASK&gt; dump_stack_lvl (lib/dump_st= ack.c:94 lib/dump_stack.c:120) print_address_description.constprop.0 (mm/ka= san/report.c:378) print_report (mm/kasan/report.c:482) kasan_report (mm/kas= an/report.c:595) __mld_query_work (net/ipv6/mcast.c:1512) mld_query_work (n= et/ipv6/mcast.c:1563) process_one_work (kernel/workqueue.c:3314) worker_thr= ead (kernel/workqueue.c:3397 kernel/workqueue.c:3478) kthread (kernel/kthre= ad.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (= arch/x86/entry/entry_64.S:245) &lt;/TASK&gt; [...] Freed by task 118: kasan= _save_stack (mm/kasan/common.c:57) kasan_save_track (mm/kasan/common.c:78) = kasan_save_free_info (mm/kasan/generic.c:584) __kasan_slab_free (mm/kasan/c= ommon.c:253 mm/kasan/common.c:285) kfree (./include/linux/kasan.h:235 mm/sl= ub.c:2689 mm/slub.c:6251 mm/slub.c:6566) pskb_expand_head (net/core/skbuff.= c:2335) __pskb_pull_tail (net/core/skbuff.c:2878 (discriminator 4)) __mld_q= uery_work (net/ipv6/mcast.c:1495 (discriminator 1)) mld_query_work (net/ipv= 6/mcast.c:1563) process_one_work (kernel/workqueue.c:3314) worker_thread (k= ernel/workqueue.c:3397 kernel/workqueue.c:3478) kthread (kernel/kthread.c:4= 36) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x= 86/entry/entry_64.S:245)</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53275" target=3D= "_blank" rel=3D"noopener">CVE-2026-53275</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: KVM=
    : arm64: Take the SRCU lock for page table walks in fault injection and AT = emulation walk_s1() and kvm_walk_nested_s2() expect to be called while hold= ing kvm-&gt;srcu to guard against memslot changes. While this is generally = the case, __kvm_at_s12() and __kvm_find_s1_desc_level() call into the respe= ctive walkers without taking kvm-&gt;srcu. Fix by acquiring kvm-&gt;srcu pr= ior to the table walk in both instances.</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53277" target=3D= "_blank" rel=3D"noopener">CVE-2026-53277</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= mu/vt-d: Avoid NULL pointer dereference or refcount corruption Commit 60f03= 0f7418d ("iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE") fixed a NULL p= ointer dereference in an unlikely situation partly. If dev_pasid is not fou=
    nd in the dev_pasids list, it remains NULL. However, the teardown operation=
    s are executed unconditionally, this lead to a NULL pointer dereference or = refcount corruption. If the domain was never attached to this IOMMU, info w= ill be NULL, which would cause an immediate dereference when checking --inf= o-&gt;refcnt. Even if info is not NULL, decrementing the refcount without h= aving removed a valid PASID might unbalance the count. This could lead to p= remature dropping of the refcount to 0, potentially causing a use-after-fre=
    e for the remaining active devices sharing the domain. Fix it by returning = early if dev_pasid is NULL, before executing the teardown operations. Issue=
    found by AI review and suggested by Kevin Tian. https://sashiko.dev/#/patc= hset/20260421031347.1408890-1-zhenzhong.duan%40intel.com</td> <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53281" target=3D= "_blank" rel=3D"noopener">CVE-2026-53281</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: vfi= o/pci: Clean up DMABUFs before disabling function On device shutdown, make = vfio_pci_core_close_device() call vfio_pci_dma_buf_cleanup() before the fun= ction is disabled via vfio_pci_core_disable(). This ensures that all access=
    via DMABUFs is revoked before the function's BARs become inaccessible. Thi=
    s fixes an issue where, if the function is disabled first, a tiny window ex= ists in which the function's MSE is cleared and yet BARs could still be acc= essed via the DMABUF. The resources would also be freed and up for grabs by=
    a different driver.</td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53322" target=3D= "_blank" rel=3D"noopener">CVE-2026-53322</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nf_queue: hold bridge skb-&gt;dev while queued br_pass_frame_up() r= ewrites skb-&gt;dev from the ingress port to the bridge master before queue= ing bridge LOCAL_IN packets. NFQUEUE only holds references on state.in/out = and bridge physdevs, so a queued bridge packet can retain a freed bridge ma= ster in skb-&gt;dev until reinjection. When the verdict is reinjected later=
    , br_netif_receive_skb() re-enters the receive path with skb-&gt;dev still = pointing at the freed bridge master, triggering a use-after-free. Store skb= -&gt;dev in the queue entry, hold a reference on it for the queue lifetime,=
    and use the saved device when dropping queued packets during NETDEV_DOWN h= andling.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52912" target=3D= "_blank" rel=3D"noopener">CVE-2026-52912</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: ip6t_hbh: reject oversized option lists struct ip6t_opts stores at = most IP6T_OPTS_OPTSNR option descriptors, but hbh_mt6_check() does not reje=
    ct larger optsnr values supplied from userspace. Validate optsnr in the rul=
    e setup path so only match data that fits the fixed-size opts array can be = installed. This follows the existing xtables pattern of rejecting invalid u= ser-provided counts in checkentry() and keeps the packet matching path unch= anged. `struct ip6t_opts` has a fixed `opts[IP6T_OPTS_OPTSNR]` array, where=
    `IP6T_OPTS_OPTSNR` is 16, then off-by-one array access is possible: [ 137.= 924693][ T8692] UBSAN: array-index-out-of-bounds in ../net/ipv6/netfilter/i= p6t_hbh.c:110:29 [ 137.926167][ T8692] index 16 is out of range for type '_= _u16 [16]'</td>
    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52915" target=3D= "_blank" rel=3D"noopener">CVE-2026-52915</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sct=
    p: diag: reject stale associations in dump_one path The SCTP exact sock_dia=
    g lookup can hold a transport reference, block on lock_sock(sk), and then r= esume after sctp_association_free() has marked the association dead and fre=
    ed its bind address list. When that happens, inet_assoc_attr_size() and ine= t_diag_msg_sctpasoc_fill() can still dereference association state that is =
    no longer valid for reporting. In particular, inet_diag_msg_sctpasoc_fill()=
    may read an empty bind-address list as a real sctp_sockaddr_entry and trig= ger an out-of-bounds read from unrelated association memory. Reject the ass= ociation after taking the socket lock if it has been reaped or detached fro=
    m the endpoint, and report the lookup as stale. This keeps the exact dump-o=
    ne path from formatting torn association state.</td>
    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52917" target=3D= "_blank" rel=3D"noopener">CVE-2026-52917</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bat= man-adv: fix tp_meter counter underflow during shutdown batadv_tp_sender_sh= utdown() unconditionally decrements the "sending" atomic counter. If multip=
    le paths (e.g. timeout, user cancel, and normal finish) call this function,=
    the counter can underflow to -1. Since the sender logic treats any non-zer=
    o value as "still sending", a negative value causes the sender kthread to l= oop indefinitely. This leads to a use-after-free when the interface is remo= ved while the zombie thread is still active. Fix this by using atomic_xchg(=
    ) to ensure the counter only transitions from 1 to 0 once. [sven: added mis= sing change in batadv_tp_send]</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52919" target=3D= "_blank" rel=3D"noopener">CVE-2026-52919</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bat= man-adv: dat: handle forward allocation error batadv_dat_forward_data() cal=
    ls pskb_copy_for_clone() to duplicate an skb for each DHT candidate, but do=
    es not check the return value before passing it to batadv_send_skb_prepare_= unicast_4addr(). That function dereferences the skb unconditionally, so a f= ailed allocation triggers a NULL pointer dereference. Skip forwarding to th=
    e current DHT candidate on allocation failure.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52922" target=3D= "_blank" rel=3D"noopener">CVE-2026-52922</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ipc=
    : limit next_id allocation to the valid ID range The checkpoint/restore sys= ctl path can request the next SysV IPC id through ids-&gt;next_id. ipc_idr_= alloc() currently forwards that request to idr_alloc() with an open-ended u= pper bound. If the valid tail of the SysV IPC id space is full, the allocat= ion can spill beyond ipc_mni. The returned SysV IPC id still uses the norma=
    l index encoding, so later lookup and removal can target the wrong slot. Th=
    is leaves the real IDR entry behind and breaks the IDR state for the object=
    . The bug is in ipc_idr_alloc() in the checkpoint/restore path. 1. ids-&gt;= next_id is passed to: idr_alloc(&amp;ids-&gt;ipcs_idr, new, ipcid_to_idx(ne= xt_id), 0, ...) 2. The zero upper bound makes the allocation effectively op= en-ended. Once the valid SysV IPC tail is occupied, idr_alloc() can spill p= ast ipc_mni and allocate an entry beyond the valid IPC id range. 3. The new=
    object id is still encoded with the narrower SysV IPC index width: new-&gt= ;id =3D (new-&gt;seq &lt;&lt; ipcmni_seq_shift()) + idx 4. Later removal go=
    es through ipc_rmid(), which uses: ipcid_to_idx(ipcp-&gt;id) That truncates=
    the real IDR index. An object actually stored at a high index can then be = removed as if it lived at a low in-range index. 5. For shared memory, shm_d= estroy() frees the current object anyway, but the real high IDR slot is lef=
    t behind as a dangling pointer. 6. A subsequent walk of /proc/sysvipc/shm r= eaches the stale IDR entry and dereferences freed memory. Prevent this by b= ounding the requested allocation to ipc_mni so the checkpoint/restore path = fails once the valid range is exhausted.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52923" target=3D= "_blank" rel=3D"noopener">CVE-2026-52923</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: ebtables: fix OOB read in compat_mtw_from_user Luxiao Xu says: The = function compat_mtw_from_user() converts ebtables extensions from 32-bit us=
    er structures to kernel native structures. However, it lacks proper validat= ion of the user-supplied match_size/target_size. When certain extensions ar=
    e processed, the kernel-side translation logic may perform memory accesses = based on the extension's expected size. If the user provides a size smaller=
    than what the extension requires, it results in an out-of-bounds read as r= eported by KASAN. This fix introduces a check to ensure match_size is at le= ast as large as the extension's required compatsize. This covers matches, w= atchers, and targets, while maintaining compatibility with standard targets=
    . AFAIU this is relevant for matches that need to go though match-&gt;compa= t_from_user() call. Those that use plain memcpy with the user-provided size=
    are ok because the caller checks that size vs the start of the next rule e= ntry offset (which itself is checked vs. total size copied from userspace).=
    The -&gt;compat_from_user() callbacks assume they can read compatsize byte=
    s, so they need this extra check. Based on an earlier patch from Luxiao Xu.= </td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52927" target=3D= "_blank" rel=3D"noopener">CVE-2026-52927</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sct=
    p: stream: fully roll back denied add-stream state When ADD_OUT_STREAMS is = denied, SCTP only shrinks the queued chunks and then lowers outcnt. That le= aves removed stream metadata behind, so a later re-add can reuse a stale ex=
    t and hit a null-pointer dereference in the scheduler get path. Fix the rol= lback by tearing down the removed stream state the same way other stream re= sizes do. Unschedule the current scheduler state, drop the removed stream e=
    xt state with sctp_stream_outq_migrate(), and then reschedule the remaining=
    streams. This keeps scheduler-private RR/FC/PRIO lists consistent while fu= lly rolling back denied outgoing stream additions.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52929" target=3D= "_blank" rel=3D"noopener">CVE-2026-52929</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: xfr=
    m: ipcomp: Free destination pages on acomp errors Move the out_free_req lab=
    el up by a couple of lines so that the allocated dst SG list gets freed on = error as well as success.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52932" target=3D= "_blank" rel=3D"noopener">CVE-2026-52932</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: io_= uring/poll: fix signed comparison in io_poll_get_ownership() io_poll_get_ow= nership() uses a signed comparison to check whether poll_refs has reached t=
    he threshold for the slowpath: if (unlikely(atomic_read(&amp;req-&gt;poll_r= efs) &gt;=3D IO_POLL_REF_BIAS)) atomic_read() returns int (signed). When IO= _POLL_CANCEL_FLAG (BIT(31)) is set in poll_refs, the value becomes negative=
    in signed arithmetic, so the &gt;=3D 128 comparison always evaluates to fa= lse and the slowpath is never taken. Fix this by casting the atomic_read() = result to unsigned int before the comparison, so that the cancel flag is tr= eated as a large positive value and correctly triggers the slowpath.</td> <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52933" target=3D= "_blank" rel=3D"noopener">CVE-2026-52933</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: xfr=
    m: espintcp: do not reuse an in-progress partial send espintcp keeps a sing=
    le in-flight transmit in ctx-&gt;partial. Before building a new sk_msg, esp= intcp_sendmsg() first tries to flush that state through espintcp_push_msgs(=
    ). For blocking callers, espintcp_push_msgs() may return success even when = the previous partial send is still pending. espintcp_sendmsg() would then r= einitialize emsg-&gt;skmsg and reuse ctx-&gt;partial while the old transfer=
    still owns that state. Do not rebuild the send message when ctx-&gt;partia=
    l is still in progress. If espintcp_push_msgs() returns with emsg-&gt;len s= till set, fail the new send instead of overwriting the live partial state. = This is a memory-safety fix: reusing the live partial-send state can leave =
    a stale offset attached to a new sk_msg and lead to an out-of- bounds read =
    in the send path. tcp_sendmsg_locked() already handles waiting for send buf= fer memory, so the fix here is just to preserve espintcp's one-message-at-a= -time transmit state.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52935" target=3D= "_blank" rel=3D"noopener">CVE-2026-52935</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nf_log: validate MAC header was set before dumping it The fallback = path of dump_mac_header() guards the MAC header access only with "skb-&gt;m= ac_header !=3D skb-&gt;network_header", without checking skb_mac_header_was= _set(). When the MAC header is unset, mac_header is 0xffff, so the test pas= ses and skb_mac_header(skb) returns skb-&gt;head + 0xffff, ~64 KiB past the=
    buffer; the loop then reads dev-&gt;hard_header_len bytes out of bounds in=
    to the kernel log. This is reachable via the netdev logger: nf_log_unknown_= packet() calls dump_mac_header() unconditionally, and an skb sent through A= F_PACKET with PACKET_QDISC_BYPASS reaches the egress hook with mac_header s= till unset (__dev_queue_xmit(), which would reset it, is bypassed). Add the=
    skb_mac_header_was_set() check the ARPHRD_ETHER path already uses, and rep= lace the open-coded MAC header length test with skb_mac_header_len(). Only = skbs with an unset MAC header are affected; valid ones are dumped as before=
    . BUG: KASAN: slab-out-of-bounds in dump_mac_header (net/netfilter/nf_log_s= yslog.c:831) Read of size 1 at addr ffff88800ea49d3f by task exploit/148 Ca=
    ll Trace: kasan_report (mm/kasan/report.c:595) dump_mac_header (net/netfilt= er/nf_log_syslog.c:831) nf_log_netdev_packet (net/netfilter/nf_log_syslog.c= :938 net/netfilter/nf_log_syslog.c:963) nf_log_packet (net/netfilter/nf_log= .c:260) nft_log_eval (net/netfilter/nft_log.c:60) nft_do_chain (net/netfilt= er/nf_tables_core.c:285) nft_do_chain_netdev (net/netfilter/nft_chain_filte= r.c:307) nf_hook_slow (net/netfilter/core.c:619) nf_hook_direct_egress (net= /packet/af_packet.c:257) packet_xmit (net/packet/af_packet.c:280) packet_se= ndmsg (net/packet/af_packet.c:3114) __sys_sendto (net/socket.c:2265)</td> <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52942" target=3D= "_blank" rel=3D"noopener">CVE-2026-52942</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : skbuff: fix missing zerocopy reference in pskb_carve helpers pskb_carve_i= nside_header() and pskb_carve_inside_nonlinear() both copy the old skb_shar= ed_info header into a new buffer via memcpy(), which includes the destructo= r_arg pointer (uarg) for MSG_ZEROCOPY skbs. Neither function calls net_zcop= y_get() for the new shinfo, creating an unaccounted holder: every skb_share= d_info with destructor_arg set will call skb_zcopy_clear() once when freed,=
    but the corresponding net_zcopy_get() was never called for the new copy. R= epeated calls drive uarg-&gt;refcnt to zero prematurely, freeing ubuf_info_= msgzc while TX skbs still hold live destructor_arg pointers. KASAN reports = use-after-free on a freed ubuf_info_msgzc: BUG: KASAN: slab-use-after-free =
    in skb_release_data+0x77b/0x810 Read of size 8 at addr ffff88801574d3e8 by = task poc/220 Call Trace: skb_release_data+0x77b/0x810 kfree_skb_list_reason= +0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb= _queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x35= 4/0x1780 __sys_recvmsg+0xdf/0x180 Allocated by task 219: msg_zerocopy_reall= oc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0 Freed by task 219: ip_recv_= error+0x74a/0xb10 tcp_recvmsg+0x475/0x530 The skb consuming the late access=
    still referenced the same uarg via shinfo-&gt;destructor_arg copied by psk= b_carve_inside_nonlinear() without a refcount bump. This has been verified =
    to be reliably exploitable: a working proof-of-concept achieves full root p= rivilege escalation from an unprivileged local user on a default kernel con= figuration. The fix follows the pattern of pskb_expand_head() which has the=
    same memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_ge= t() is placed after skb_orphan_frags() succeeds, so the orphan error path n= eeds no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is plac=
    ed after all failure points and just before skb_release_data(), so no error=
    path needs cleanup at all -- matching pskb_expand_head() more closely and = avoiding the need for a balancing net_zcopy_put().</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52943" target=3D= "_blank" rel=3D"noopener">CVE-2026-52943</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Rev= ert "wireguard: device: enable threaded NAPI" This reverts commit 933466fc5= 0a8e4eb167acbd0d8ec96a078462e9c which is commit db9ae3b6b43c79b1ba87eea849f= d65efa05b4b2e upstream. We have had three independent production user repor=
    ts in combination with Cilium utilizing WireGuard as encryption underneath = that k8s Pod E/W traffic to certain peer nodes fully stalled. The situation=
    appears as follows: - Occurs very rarely but at random times under heavy n= etworking load. - Once the issue triggers the decryption side stops working=
    completely for that WireGuard peer, other peers keep working fine. The sta=
    ll happens also for newly initiated connections towards that particular Wir= eGuard peer. - Only the decryption side is affected, never the encryption s= ide. - Once it triggers, it never recovers and remains in this state, the C= PU/mem on that node looks normal, no leak, busy loop or crash. - bpftrace o=
    n the affected system shows that wg_prev_queue_enqueue fails, thus the MAX_= QUEUED_PACKETS (1024 skbs!) for the peer's rx_queue is reached. - Also, bpf= trace shows that wg_packet_rx_poll for that peer is never called again afte=
    r reaching this state for that peer. For other peers wg_packet_rx_poll does=
    get called normally. - Commit db9ae3b ("wireguard: device: enable threaded=
    NAPI") switched WireGuard to threaded NAPI by default. The default has not=
    been changed for triggering the issue, neither did CPU hotplugging occur (= i.e. 5bd8de2 ("wireguard: queueing: always return valid online CPU in wg_cp= umask_choose_online()")). - The issue has been observed with stable kernels=
    of v5.15 as well as v6.1. It was reported to us that v5.10 stable is worki=
    ng fine, and no report on v6.6 stable either (somewhat related discussion i=
    n [0] though). - In the WireGuard driver the only material difference betwe=
    en v5.10 stable and v5.15 stable is the switch to threaded NAPI by default.=
    [0] https://lore.kernel.org/netdev/CA+wXwBTT74RErDGAnj98PqS=3Dwvdh8eM1pi4q= 6tTdExtjnokKqA@mail.gmail.com/ Breakdown of the problem: 1) skbs arriving f=
    or decryption are enqueued to the peer-&gt;rx_queue in wg_packet_consume_da=
    ta via wg_queue_enqueue_per_device_and_peer. 2) The latter only moves the s=
    kb into the MPSC peer queue if it does not surpass MAX_QUEUED_PACKETS (1024=
    ) which is kept track in an atomic counter via wg_prev_queue_enqueue. 3) In=
    case enqueueing was successful, the skb is also queued up in the device qu= eue, round-robin picks a next online CPU, and schedules the decryption work= er. 4) The wg_packet_decrypt_worker, once scheduled, picks these up from th=
    e queue, decrypts the packets and once done calls into wg_queue_enqueue_per= _peer_rx. 5) The latter updates the state to PACKET_STATE_CRYPTED on succes=
    s and calls napi_schedule on the per peer-&gt;napi instance. 6) NAPI then p= olls via wg_packet_rx_poll. wg_prev_queue_peek checks on the peer-&gt;rx_qu= eue. It will wg_prev_queue_dequeue if the queue-&gt;peeked skb was not cach=
    ed yet, or just return the latter otherwise. (wg_prev_queue_drop_peeked lat=
    er clears the cache.) 7) From an ordering perspective, the peer-&gt;rx_queu=
    e has skbs in order while the device queue with the per-CPU worker threads = from a global ordering PoV can finish the decryption and signal the skb PAC= KET_STATE_CRYPTED out of order. 8) A situation can be observed that the fir=
    st packet coming in will be stuck waiting for the decryption worker to be s= cheduled for a longer time when the system is under pressure. 9) While this=
    is the case, the other CPUs in the meantime finish decryption and call int=
    o napi_schedule. 10) Now in wg_packet_rx_poll it picks up the first in-orde=
    r skb from the peer-&gt;rx_queue and sees that its state is still PACKET_ST= ATE_UNCRYPTED. The NAPI poll routine then exits e ---truncated---</td> <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52945" target=3D= "_blank" rel=3D"noopener">CVE-2026-52945</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fs/= fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling A SOFTIRQ-safe to = SOFTIRQ-unsafe lock order deadlock can occur in send_sigio() and send_sigur= g() when a process group receives a signal. When FASYNC is configured for a=
    process group (PIDTYPE_PGID), both functions use read_lock(&amp;tasklist_l= ock) to traverse the task list. However, they are frequently called from so= ftirq context: - send_sigio() via input_inject_event -&gt; kill_fasync - se= nd_sigurg() via tcp_check_urg -&gt; sk_send_sigurg (NET_RX_SOFTIRQ) The dea= dlock is caused by the rwlock writer fairness mechanism: 1. CPU 0 (process = context) holds read_lock(&amp;tasklist_lock) in do_wait(). 2. CPU 1 (proces=
    s context) attempts write_lock(&amp;tasklist_lock) in fork() or exit() and = spins, which blocks all new readers. 3. CPU 0 is interrupted by a softirq (= e.g., TCP URG packet reception). 4. The softirq calls send_sigurg() and att= empts to acquire read_lock(&amp;tasklist_lock), deadlocking because CPU 1 i=
    s waiting. Since PID hashing and do_each_pid_task() traversals are already = RCU-protected, the read_lock on tasklist_lock is no longer strictly require=
    d for safe traversal. Fix this by replacing tasklist_lock with rcu_read_loc= k(), aligning the process group signaling path with the single-PID path. Th=
    is also mitigates a potential remote denial of service vector via TCP URG p= ackets. Lockdep splat: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D WARNING: SOFTIRQ-safe -&gt; SOFTIRQ-unsaf=
    e lock order detected [...] Chain exists of: &amp;dev-&gt;event_lock --&gt;=
    &amp;f_owner-&gt;lock --&gt; tasklist_lock Possible interrupt unsafe locki=
    ng scenario: CPU0 CPU1 ---- ---- lock(tasklist_lock); local_irq_disable(); = lock(&amp;dev-&gt;event_lock); lock(&amp;f_owner-&gt;lock); &lt;Interrupt&g=
    t; lock(&amp;dev-&gt;event_lock); *** DEADLOCK ***</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52946" target=3D= "_blank" rel=3D"noopener">CVE-2026-52946</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : qrtr: fix refcount saturation and potential UAF in qrtr_port_remove In qr= tr_port_remove(), the socket reference count is decremented via __sock_put(=
    ) before the port is removed from the qrtr_ports XArray and before the RCU = grace period elapses. This breaks the fundamental RCU update paradigm. It e= xposes a race window where a concurrent RCU reader (such as qrtr_reset_port= s() or qrtr_port_lookup()) can obtain a pointer to the socket from the XArr= ay, and attempt to call sock_hold() on a socket whose reference count has a= lready dropped to zero. This exact race condition was hit during syzkaller = fuzzing, leading to the following refcount saturation warning and a potenti=
    al Use-After-Free: refcount_t: saturated; leaking memory. WARNING: CPU: 3 P= ID: 1273 at lib/refcount.c:22 refcount_warn_saturate+0xae/0x1d0 Modules lin= ked in: qrtr(+) bochs drm_shmem_helper ... Call Trace: &lt;TASK&gt; qrtr_re= set_ports net/qrtr/af_qrtr.c:768 [inline] [qrtr] __qrtr_bind.isra.0+0x48b/0= x570 net/qrtr/af_qrtr.c:805 [qrtr] qrtr_bind+0x17d/0x210 net/qrtr/af_qrtr.c= :901 [qrtr] kernel_bind+0xe4/0x120 net/socket.c:3592 qrtr_ns_init+0x1a6/0x3=
    80 net/qrtr/ns.c:715 [qrtr] qrtr_proto_init+0x3b/0xff0 net/qrtr/af_qrtr.c:1=
    69 [qrtr] do_one_initcall+0xf5/0x5e0 init/main.c:1283 ... &lt;/TASK&gt; Fix=
    this by deferring the reference count decrement until after the xa_erase()=
    and the synchronize_rcu() complete. (Note: The v1 of this patch incorrectl=
    y replaced __sock_put() with sock_put(). As Simon Horman pointed out, the c= allers of qrtr_port_remove() still hold a reference to the socket, so freei=
    ng the socket memory here would lead to a subsequent UAF in the caller. Thu=
    s, the __sock_put() is kept, but only repositioned to close the RCU race.)<=

    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52947" target=3D= "_blank" rel=3D"noopener">CVE-2026-52947</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /xe/dma-buf: fix UAF with retry loop Retry doesn't work here, since bo will=
    be freed on error, leading to UAF. However, now that we do the alloc &amp;=
    init before the attach, we can now combine this as one unit and have the i= nit do the alloc for us. This should make the retry safe. Reported by Sashi= ko. v2: Fix up the error unwind (CI) (cherry picked from commit 47966941825= 3e0f27f8cf5db01a731352ea592e7)</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52950" target=3D= "_blank" rel=3D"noopener">CVE-2026-52950</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /xe/dma-buf: handle empty bo and UAF races There look to be some nasty race=
    s here when triggering the invalidate_mappings hook: 1) We do xe_bo_alloc()=
    followed by the attach, before the actual full bo init step in xe_dma_buf_= init_obj(). However the bo is visible on the attachments list after the att= ach. This is bad since exporter driver, say amdgpu, can at any time call ba=
    ck into our invalidate_mappings hook, with an empty/bogus bo, leading to po= tential bugs/crashes. 2) Similar to 1) but here we get a UAF, when the inva= lidate_mappings hook is triggered. For example, we get as far as xe_bo_init= _locked() but this fails in some way. But here the bo will be freed on erro=
    r, but we still have it attached from dma-buf pov, so if the invalidate_map= pings is now triggered then the bo we access is gone and we trigger UAF and=
    more bugs/crashes. To fix this, move the attach step until after we actual=
    ly have a fully set up buffer object. Note that the bo is not published to = userspace until later, so not sure what the comment "Don't publish the bo u= ntil we have a valid attachment", is referring to. We have at least two dif= ferent customers reporting hitting a NULL ptr deref in evict_flags when imp= orting something from amdgpu, followed by triggering the evict flow. Hit ra=
    te is also pretty low, which would hint at some kind of race, so something = like 1) or 2) might explain this. v2: - Shuffle the order of the ops slight=
    ly (no functional change) - Improve the comment to better explain the order= ing (Matt B) (cherry picked from commit af1f2ad0c59fe4e2f924c526f66e968289d= 77971)</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52951" target=3D= "_blank" rel=3D"noopener">CVE-2026-52951</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= mu/vt-d: Fix oops due to out of scope access Below oops triggers when kill = QEMU process: Oops: general protection fault, probably for non-canonical ad= dress 0x7fffffff844eaaa7: 0000 [#1] SMP NOPTI Call Trace: &lt;TASK&gt; do_r= aw_spin_lock+0xaa/0xc0 _raw_spin_lock_irqsave+0x21/0x40 domain_remove_dev_p= asid+0x52/0x160 intel_nested_set_dev_pasid+0x1b9/0x1e0 __iommu_set_group_pa= sid+0x56/0x120 pci_dev_reset_iommu_done+0xe3/0x180 pcie_flr+0x65/0x160 __pc= i_reset_function_locked+0x5b/0x120 vfio_pci_core_close_device+0x63/0xe0 [vf= io_pci_core] vfio_df_close+0x4f/0xa0 vfio_df_unbind_iommufd+0x2d/0x60 vfio_= device_fops_release+0x3e/0x40 __fput+0xe5/0x2c0 task_work_run+0x58/0xa0 do_= exit+0x2c8/0x600 do_group_exit+0x2f/0xa0 get_signal+0x863/0x8c0 arch_do_sig= nal_or_restart+0x24/0x100 exit_to_user_mode_loop+0x87/0x380 do_syscall_64+0= x2ff/0x11e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The global static bloc= ked domain is a dummy domain without corresponding dmar_domain structure, a= ccessing beyond iommu_domain structure triggers oops easily. Fix it by retu=
    rn early in domain_remove_dev_pasid() like identity domain.</td> <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52953" target=3D= "_blank" rel=3D"noopener">CVE-2026-52953</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: lib= ceph: handle rbtree insertion error in decode_choose_args() A message of ty=
    pe CEPH_MSG_OSD_MAP contains an OSD map that itself contains a CRUSH map. T=
    he received CRUSH map may optionally contain choose_args that get decoded i=
    n decode_choose_args(). In this function, num_choose_arg_maps is read from = the message, and a corresponding number of crush_choose_arg_maps gets decod=
    ed afterwards. Each crush_choose_arg_map has a choose_args_index, which ser= ves as the key when inserting it into the choose_args rbtree of the decoded=
    crush_map. If a (potentially corrupted) message contains two crush_choose_= arg_maps with the same index, the assertion in insert_choose_arg_map() trig= gers a kernel BUG when trying to insert the second crush_choose_arg_map. Th=
    is patch fixes the issue by switching to the non-asserting rbtree insertion=
    function and rejecting the message if the insertion fails. [ idryomov: cha= ngelog ]</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52954" target=3D= "_blank" rel=3D"noopener">CVE-2026-52954</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: lib= ceph: Fix potential out-of-bounds access in __ceph_x_decrypt() In __ceph_x_= decrypt(), a part of the buffer p is interpreted as a ceph_x_encrypt_header=
    , and the magic field of this struct is accessed. This happens without any = guarantee that the buffer is large enough to hold this struct. The function=
    parameter ciphertext_len represents the length of the ciphertext to decryp=
    t and is guaranteed to be at most the remaining size of the allocated buffe=
    r p. However, this value is not necessarily greater than sizeof(ceph_x_encr= ypt_header). E.g., a message frame of type FRAME_TAG_AUTH_REPLY_MORE, that =
    is just as long to hold the ciphertext at its end with a ciphertext_len of =
    8 or less, can trigger an out-of-bounds memory access when accessing hdr-&g= t;magic. This patch fixes the issue by adding a check to ensure that the de= crypted plaintext in the buffer is large enough to represent at least the c= eph_x_encrypt_header.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52956" target=3D= "_blank" rel=3D"noopener">CVE-2026-52956</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: lib= ceph: Fix potential null-ptr-deref in decode_choose_args() A message of typ=
    e CEPH_MSG_OSD_MAP contains an OSD map that itself contains a CRUSH map. Wh=
    en decoding this CRUSH map in crush_decode(), an array of max_buckets CRUSH=
    buckets is decoded, where some indices may not refer to actual buckets and=
    are therefore set to NULL. The received CRUSH map may optionally contain c= hoose_args that get decoded in decode_choose_args(). When decoding a crush_= choose_arg_map, a series of choose_args for different buckets is decoded, w= ith the bucket_index being read from the incoming message. It is only check=
    ed that the bucket index does not exceed max_buckets, but not that it doesn=
    't point to an index with a NULL bucket. If a (potentially corrupted) messa=
    ge contains a crush_choose_arg_map including such a bucket_index, a null po= inter dereference may occur in the subsequent processing when attempting to=
    access the bucket with the given index. This patch fixes the issue by exte= nding the affected check. Now, it is only attempted to access the bucket if=
    it is not NULL.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52957" target=3D= "_blank" rel=3D"noopener">CVE-2026-52957</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: vir=
    t: sev-guest: Do not use host-controlled page order in cleanup path When is= suing an extended guest request (SVM_VMGEXIT_EXT_GUEST_REQUEST), get_ext_re= port() allocates a buffer to retrieve a certificate blob from the host, kee= ping track of its size in report_req-&gt;certs_len. However, the host may r= eturn SNP_GUEST_VMM_ERR_INVALID_LEN, indicating an invalid buffer size, as = well as the expected length of such buffer. get_ext_report() subsequently u= pdates report_req-&gt;certs_len with the host-controlled value, and cleans =
    up the buffer by computing a page order from such value. This is incorrect,=
    as the host-provided length may not match the page order of the original a= llocation, potentially resulting in corruption in the page allocator. Fix t= his by using alloc_pages_exact() instead, and reusing @npages to compute th=
    e size passed to free_pages_exact(). For consistency, also use @npages to c= ompute the size when allocating the pages, even though this last change has=
    no functional effect.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52959" target=3D= "_blank" rel=3D"noopener">CVE-2026-52959</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: cep=
    h: put folios not suitable for writeback The batch holds references to the = folios (see `filemap_get_folios`, `folio_batch_release`), so we need to `fo= lio_put` the folios we remove. Tested on v6.18.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52960" target=3D= "_blank" rel=3D"noopener">CVE-2026-52960</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : ena: PHC: Fix potential use-after-free in get_timestamp Move the phc-&gt;= active check and resp pointer assignment to after acquiring the spinlock. P= reviously, phc-&gt;active was checked without holding the lock, and resp wa=
    s cached from ena_dev-&gt;phc.virt_addr before the lock was acquired. If en= a_com_phc_destroy() runs between the lockless active check and the lock acq= uisition, it sets active=3Dfalse, releases the lock, frees the DMA memory, = and sets virt_addr=3DNULL. The get_timestamp path would then read a NULL vi= rt_addr and dereference it. With both the active check and the pointer read=
    under the lock, destroy cannot free the memory while get_timestamp is usin=
    g it.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52971" target=3D= "_blank" rel=3D"noopener">CVE-2026-52971</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fut= ex: Drop CLONE_THREAD requirement for private default hash alloc Currently = need_futex_hash_allocate_default() depends on strict pthread semantics, abu= sing CLONE_THREAD. This breaks the non-concurrency assumptions when doing t=
    he mm-&gt;futex_ref pcpu allocations, leading to bugs[0] when sharing the m=
    m in other ways; ie: BUG: KASAN: slab-use-after-free in futex_hash_put ... = where the +1 bias can end up on a percpu counter that mm-&gt;futex_ref no l= onger points at. Loosen the check to cover any CLONE_VM clone, except vfork= (). Excluding vfork keeps the existing paths untouched (no overhead), and w=
    e can't race in the first place: either the parent is suspended and the chi=
    ld runs alone, or mm-&gt;futex_ref is already allocated from an earlier CLO= NE_VM.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52973" target=3D= "_blank" rel=3D"noopener">CVE-2026-52973</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : tls: fix strparser anchor skb leak on offload RX setup failure When tls_s= et_device_offload_rx() fails at tls_dev_add(), the error path calls tls_sw_= free_resources_rx() to clean up the SW context that was initialized by tls_= set_sw_offload(). This function calls tls_sw_release_resources_rx() (which = stops the strparser via tls_strp_stop()) and tls_sw_free_ctx_rx() (which kf= rees the context), but never frees the anchor skb that was allocated by all= oc_skb(0) in tls_strp_init(). Note that tls_sw_free_resources_rx() is exclu= sively used for this "failed to start offload" code path, there's no other = caller. The leak did not exist before commit 84c61fe1a75b ("tls: rx: do not=
    use the standard strparser"), because the standard strparser doesn't try t=
    o pre-allocate an skb. The normal close path in tls_sk_proto_close() handle=
    s cleanup by calling tls_sw_strparser_done() (which calls tls_strp_done()) = after dropping the socket lock, because tls_strp_done() does cancel_work_sy= nc() and the strparser work handler takes the socket lock.</td> <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52974" target=3D= "_blank" rel=3D"noopener">CVE-2026-52974</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bon= ding: 3ad: implement proper RCU rules for port-&gt;aggregator syzbot found =
    a data-race in bond_3ad_get_active_agg_info / bond_3ad_state_machine_handle=
    r [1] which hints at lack of proper RCU implementation. Add __rcu qualifier=
    to port-&gt;aggregator, and add proper RCU API. [1] BUG: KCSAN: data-race =
    in bond_3ad_get_active_agg_info / bond_3ad_state_machine_handler write to 0= xffff88813cf5c4b0 of 8 bytes by task 36 on cpu 0: ad_port_selection_logic d= rivers/net/bonding/bond_3ad.c:1659 [inline] bond_3ad_state_machine_handler+= 0x9d5/0x2d60 drivers/net/bonding/bond_3ad.c:2569 process_one_work kernel/wo= rkqueue.c:3302 [inline] process_scheduled_works+0x4f0/0x9c0 kernel/workqueu= e.c:3385 worker_thread+0x58a/0x780 kernel/workqueue.c:3466 kthread+0x22a/0x= 280 kernel/kthread.c:436 ret_from_fork+0x146/0x330 arch/x86/kernel/process.= c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 read to 0xf= fff88813cf5c4b0 of 8 bytes by task 22063 on cpu 1: __bond_3ad_get_active_ag= g_info drivers/net/bonding/bond_3ad.c:2858 [inline] bond_3ad_get_active_agg= _info+0x8c/0x230 drivers/net/bonding/bond_3ad.c:2881 bond_fill_info+0xe0f/0= x10f0 drivers/net/bonding/bond_netlink.c:853 rtnl_link_info_fill net/core/r= tnetlink.c:906 [inline] rtnl_link_fill+0x1d7/0x4e0 net/core/rtnetlink.c:927=
    rtnl_fill_ifinfo+0xf8e/0x1380 net/core/rtnetlink.c:2168 rtmsg_ifinfo_build= _skb+0x11c/0x1b0 net/core/rtnetlink.c:4453 rtmsg_ifinfo_event net/core/rtne= tlink.c:4486 [inline] rtmsg_ifinfo+0x6d/0x110 net/core/rtnetlink.c:4495 __d= ev_notify_flags+0x76/0x390 net/core/dev.c:9790 netif_change_flags+0xac/0xd0=
    net/core/dev.c:9823 do_setlink+0x905/0x2950 net/core/rtnetlink.c:3180 rtnl= _group_changelink net/core/rtnetlink.c:3813 [inline] __rtnl_newlink net/cor= e/rtnetlink.c:3981 [inline] rtnl_newlink+0xf55/0x1400 net/core/rtnetlink.c:= 4109 rtnetlink_rcv_msg+0x64b/0x720 net/core/rtnetlink.c:6995 netlink_rcv_sk= b+0x123/0x220 net/netlink/af_netlink.c:2550 rtnetlink_rcv+0x1c/0x30 net/cor= e/rtnetlink.c:7022 netlink_unicast_kernel net/netlink/af_netlink.c:1318 [in= line] netlink_unicast+0x5a8/0x680 net/netlink/af_netlink.c:1344 netlink_sen= dmsg+0x5c8/0x6f0 net/netlink/af_netlink.c:1894 sock_sendmsg_nosec net/socke= t.c:787 [inline] __sock_sendmsg net/socket.c:802 [inline] ____sys_sendmsg+0= x563/0x5b0 net/socket.c:2698 ___sys_sendmsg+0x195/0x1e0 net/socket.c:2752 _= _sys_sendmsg net/socket.c:2784 [inline] __do_sys_sendmsg net/socket.c:2789 = [inline] __se_sys_sendmsg net/socket.c:2787 [inline] __x64_sys_sendmsg+0xd4= /0x160 net/socket.c:2787 x64_sys_call+0x194c/0x3020 arch/x86/include/genera= ted/asm/syscalls_64.h:47 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inl= ine] do_syscall_64+0x12c/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL= _64_after_hwframe+0x77/0x7f value changed: 0x0000000000000000 -&gt; 0xffff8= 8813cf5c400 Reported by Kernel Concurrency Sanitizer on: CPU: 1 UID: 0 PID:=
    22063 Comm: syz.0.31122 Tainted: G W syzkaller #0 PREEMPT(full) Tainted: [= W]=3DWARN Hardware name: Google Google Compute Engine/Google Compute Engine=
    , BIOS Google 04/18/2026</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52975" target=3D= "_blank" rel=3D"noopener">CVE-2026-52975</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /xe: Fix error cleanup in xe_exec_queue_create_ioctl() Two error handling i= ssues exist in xe_exec_queue_create_ioctl(): 1. When xe_hw_engine_group_add= _exec_queue() fails, the error path jumps to put_exec_queue which skips xe_= exec_queue_kill(). If the VM is in preempt fence mode, xe_vm_add_compute_ex= ec_queue() has already added the queue to the VM's compute exec queue list.=
    Skipping the kill leaves the queue on that list, leading to a dangling poi= nter after the queue is freed. 2. When xa_alloc() fails after xe_hw_engine_= group_add_exec_queue() has succeeded, the error path does not call xe_hw_en= gine_group_del_exec_queue() to remove the queue from the hw engine group li= st. The queue is then freed while still linked into the hw engine group, ca= using a use-after-free. Fix both by: - Changing the xe_hw_engine_group_add_= exec_queue() failure path to jump to kill_exec_queue so that xe_exec_queue_= kill() properly removes the queue from the VM's compute list. - Adding a de= l_hw_engine_group label before kill_exec_queue for the xa_alloc() failure p= ath, which removes the queue from the hw engine group before proceeding wit=
    h the rest of the cleanup. (cherry picked from commit 37c831f401746a45d510b= 312b0ed7a77b1e06ec8)</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52976" target=3D= "_blank" rel=3D"noopener">CVE-2026-52976</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: nei= gh: let neigh_xmit take skb ownership neigh_xmit always releases the skb, e= xcept when no neighbour table is found. But even the first added user of ne= igh_xmit (mpls) relied on neigh_xmit to release the skb (or queue it for tx=
    ). sashiko reported: If neigh_xmit() is called with an uninitialized neighb=
    or table (for example, NEIGH_ND_TABLE when IPv6 is disabled), it returns -E= AFNOSUPPORT and bypasses its internal out_kfree_skb error path. Because the=
    return value of neigh_xmit() is ignored here, does this leak the SKB? Assu=
    me full ownership and remove the last code path that doesn't xmit or free s= kb.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52981" target=3D= "_blank" rel=3D"noopener">CVE-2026-52981</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : airoha: fix BQL imbalance in TX path Fix a possible BQL imbalance in airo= ha_dev_xmit(), where inflight packets are accounted only for the AIROHA_NUM= _TX_RING netdev TX queues. The queue index is computed as: qid =3D skb_get_= queue_mapping(skb) % ARRAY_SIZE(qdma-&gt;q_tx) txq =3D netdev_get_tx_queue(= dev, qid); However, airoha_qdma_tx_napi_poll() accounts completions across = all netdev TX queues (num_tx_queues), leading to inconsistent BQL accountin=
    g. Also reset all netdev TX queues in the ndo_stop callback.</td> <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52983" target=3D= "_blank" rel=3D"noopener">CVE-2026-52983</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amdgpu: avoid double drm_exec_fini() in userq validate When new_addition i=
    s true, amdgpu_userq_vm_validate() calls drm_exec_fini(&amp;exec) before it= erating over the collected HMM ranges and calling amdgpu_ttm_tt_get_user_pa= ges(). If amdgpu_ttm_tt_get_user_pages() fails in that path, the code jumps=
    to unlock_all and calls drm_exec_fini(&amp;exec) a second time on the same=
    exec object. drm_exec_fini() is not idempotent: it frees exec-&gt;objects = and may also drop exec-&gt;contended and finalize the ww acquire context. R= oute that error path directly to the range cleanup once exec has already be=
    en finalized. Issue found using a prototype static analysis tool and confir= med by code review. (cherry picked from commit 2802952e4a07306da6ebe813ff1a= cacc5691851a)</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52987" target=3D= "_blank" rel=3D"noopener">CVE-2026-52987</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nf_tables: join hook list via splice_list_rcu() in commit phase Pub= lish new hooks in the list into the basechain/flowtable using splice_list_r= cu() to ensure netlink dump list traversal via rcu is safe while concurrent=
    ruleset update is going on.</td>
    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52988" target=3D= "_blank" rel=3D"noopener">CVE-2026-52988</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sch= ed/psi: fix race between file release and pressure write A potential race c= ondition exists between pressure write and cgroup file release regarding th=
    e priv member of struct kernfs_open_file, which triggers the uaf reported i=
    n [1]. Consider the following scenario involving execution on two separate = CPUs: CPU0 CPU1 =3D=3D=3D=3D =3D=3D=3D=3D vfs_rmdir() kernfs_iop_rmdir() cg= roup_rmdir() cgroup_kn_lock_live() cgroup_destroy_locked() cgroup_addrm_fil= es() cgroup_rm_file() kernfs_remove_by_name() kernfs_remove_by_name_ns() vf= s_write() __kernfs_remove() new_sync_write() kernfs_drain() kernfs_fop_writ= e_iter() kernfs_drain_open_files() cgroup_file_write() kernfs_release_file(=
    ) pressure_write() cgroup_file_release() ctx =3D of-&gt;priv; kfree(ctx); o= f-&gt;priv =3D NULL; cgroup_kn_unlock() cgroup_kn_lock_live() cgroup_get(cg= rp) cgroup_kn_unlock() if (ctx-&gt;psi.trigger) // here, trigger uaf for ct=
    x, that is of-&gt;priv The cgroup_rmdir() is protected by the cgroup_mutex,=
    it also safeguards the memory deallocation of of-&gt;priv performed within=
    cgroup_file_release(). However, the operations involving of-&gt;priv execu= ted within pressure_write() are not entirely covered by the protection of c= group_mutex. Consequently, if the code in pressure_write(), specifically th=
    e section handling the ctx variable executes after cgroup_file_release() ha=
    s completed, a uaf vulnerability involving of-&gt;priv is triggered. Theref= ore, the issue can be resolved by extending the scope of the cgroup_mutex l= ock within pressure_write() to encompass all code paths involving of-&gt;pr= iv, thereby properly synchronizing the race condition occurring between cgr= oup_file_release() and pressure_write(). And, if an live kn lock can be suc= cessfully acquired while executing the pressure write operation, it indicat=
    es that the cgroup deletion process has not yet reached its final stage; co= nsequently, the priv pointer within open_file cannot be NULL. Therefore, th=
    e operation to retrieve the ctx value must be moved to a point *after* the = live kn lock has been successfully acquired. In another situation, specific= ally after entering cgroup_kn_lock_live() but before acquiring cgroup_mutex=
    , there exists a different class of race condition: CPU0: write memory.pres= sure CPU1: write cgroup.pressure=3D0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D kernfs_fop_wri= te_iter() kernfs_get_active_of(of) pressure_write() cgroup_kn_lock_live(mem= ory.pressure) cgroup_tryget(cgrp) kernfs_break_active_protection(kn) ... bl= ocks on cgroup_mutex cgroup_pressure_write() cgroup_kn_lock_live(cgroup.pre= ssure) cgroup_file_show(memory.pressure, false) kernfs_show(false) kernfs_d= rain_open_files() cgroup_file_release(of) kfree(ctx) of-&gt;priv =3D NULL c= group_kn_unlock() ... acquires cgroup_mutex ctx =3D of-&gt;priv; // may now=
    be NULL if (ctx-&gt;psi.trigger) // NULL dereference Consequently, there i=
    s a possibility that of-&gt;priv is NULL, the pressure write needs to check=
    for this. Now that the scope of the cgroup_mutex has been expanded, the or= iginal explicit cgroup_get/put operations are no longer necessary, this is = because acquiring/releasing the live kn lock inherently executes a cgroup g= et/put operation. [1] BUG: KASAN: slab-use-after-free in pressure_write+0xa= 4/0x210 kernel/cgroup/cgroup.c:4011 Call Trace: pressure_write+0xa4/0x210 k= ernel/cgroup/cgroup.c:4011 cgroup_file_write+0x36f/0x790 kernel/cgroup/cgro= up.c:43 ---truncated---</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52991" target=3D= "_blank" rel=3D"noopener">CVE-2026-52991</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nfnetlink_osf: fix potential NULL dereference in ttl check The nf_o= sf_ttl() function accessed skb-&gt;dev to perform a local interface address=
    lookup without verifying that the device pointer was valid. Additionally, = the implementation utilized an in_dev_for_each_ifa_rcu loop to match the pa= cket source address against local interface addresses. It assumed that pack= ets from the same subnet should not see a decrement on the initial TTL. A p= acket might appear it is from the same subnet but it actually isn't especia= lly in modern environments with containers and virtual switching. Remove th=
    e device dereference and interface loop. Replace the logic with a switch st= atement that evaluates the TTL according to the ttl_check.</td> <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52998" target=3D= "_blank" rel=3D"noopener">CVE-2026-52998</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nat: use kfree_rcu to release ops Florian Westphal says: "Historica= lly this is not an issue, even for normal base hooks: the data path doesn't=
    use the original nf_hook_ops that are used to register the callbacks. Howe= ver, in v5.14 I added the ability to dump the active netfilter hooks from u= serspace. This code will peek back into the nf_hook_ops that are available =
    at the tail of the pointer-array blob used by the datapath. The nat hooks a=
    re special, because they are called indirectly from the central nat dispatc= her hook. They are currently invisible to the nfnl hook dump subsystem thou= gh. But once that changes the nat ops structures have to be deferred too." = Update nf_nat_register_fn() to deal with partial exposition of the hooks fr=
    om error path which can be also an issue for nfnetlink_hook.</td> <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53000" target=3D= "_blank" rel=3D"noopener">CVE-2026-53000</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ppp= oe: drop PFC frames RFC 2516 Section 7 states that Protocol Field Compressi=
    on (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support n= egotiating PFC for PPPoE sessions, and the current PPPoE driver assumes an = uncompressed (2-byte) protocol field. However, the generic PPP layer functi=
    on ppp_input() is not aware of the negotiation result, and still accepts PF=
    C frames. If a peer with a broken implementation or an attacker sends a fra=
    me with a compressed (1-byte) protocol field, the subsequent PPP payload is=
    shifted by one byte. This causes the network header to be 4-byte misaligne=
    d, which may trigger unaligned access exceptions on some architectures. To = reduce the attack surface, drop PPPoE PFC frames. Introduce ppp_skb_is_comp= ressed_proto() helper function to be used in both ppp_generic.c and pppoe.c=
    to avoid open-coding.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53003" target=3D= "_blank" rel=3D"noopener">CVE-2026-53003</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: af_= unix: Drop all SCM attributes for SOCKMAP. SOCKMAP can hide inflight fd fro=
    m AF_UNIX GC. When a socket in SOCKMAP receives skb with inflight fd, sk_ps= ock_verdict_data_ready() looks up the mapped socket and enqueue skb to its = psock-&gt;ingress_skb. Since neither the old nor the new GC can inspect the=
    psock queue, the hidden skb leaks the inflight sockets. Note that this can= not be detected via kmemleak because inflight sockets are linked to a globa=
    l list. In addition, SOCKMAP redirect breaks the Tarjan-based GC's assumpti=
    on that unix_edge.successor is always alive, which is no longer true once s=
    kb is redirected, resulting in use-after-free below. [0] Moreover, SOCKMAP = does not call scm_stat_del() properly, so unix_show_fdinfo() could report a=
    n incorrect fd count. sk_msg_recvmsg() does not support any SCM attributes =
    in the first place. Let's drop all SCM attributes before passing skb to the=
    SOCKMAP layer. [0]: BUG: KASAN: slab-use-after-free in unix_del_edges (net= /unix/garbage.c:118 net/unix/garbage.c:181 net/unix/garbage.c:251) Read of = size 8 at addr ffff888125362670 by task kworker/56:1/496 CPU: 56 UID: 0 PID=
    : 496 Comm: kworker/56:1 Not tainted 7.0.0-rc7-00263-gb9d8b856689d #3 PREEM= PT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0= -debian-1.17.0-1 04/01/2014 Workqueue: events sk_psock_backlog Call Trace: = &lt;TASK&gt; dump_stack_lvl (lib/dump_stack.c:122) print_report (mm/kasan/r= eport.c:379) kasan_report (mm/kasan/report.c:597) unix_del_edges (net/unix/= garbage.c:118 net/unix/garbage.c:181 net/unix/garbage.c:251) unix_destroy_f=
    pl (net/unix/garbage.c:317) unix_destruct_scm (./include/net/scm.h:80 ./inc= lude/net/scm.h:86 net/unix/af_unix.c:1976) sk_psock_backlog (./include/linu= x/skbuff.h:?) process_scheduled_works (kernel/workqueue.c:?) worker_thread = (kernel/workqueue.c:?) kthread (kernel/kthread.c:438) ret_from_fork (arch/x= 86/kernel/process.c:164) ret_from_fork_asm (arch/x86/entry/entry_64.S:258) = &lt;/TASK&gt; Allocated by task 955: kasan_save_track (mm/kasan/common.c:58=
    mm/kasan/common.c:78) __kasan_slab_alloc (mm/kasan/common.c:369) kmem_cach= e_alloc_noprof (mm/slub.c:4539) sk_prot_alloc (net/core/sock.c:2240) sk_all=
    oc (net/core/sock.c:2301) unix_create1 (net/unix/af_unix.c:1099) unix_creat=
    e (net/unix/af_unix.c:1169) __sock_create (net/socket.c:1606) __sys_socketp= air (net/socket.c:1811) __x64_sys_socketpair (net/socket.c:1863 net/socket.= c:1860 net/socket.c:1860) do_syscall_64 (arch/x86/entry/syscall_64.c:?) ent= ry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Freed by task 4= 96: kasan_save_track (mm/kasan/common.c:58 mm/kasan/common.c:78) kasan_save= _free_info (mm/kasan/generic.c:587) __kasan_slab_free (mm/kasan/common.c:28=
    7) kmem_cache_free (mm/slub.c:6165) __sk_destruct (net/core/sock.c:2282 net= /core/sock.c:2384) sk_psock_destroy (./include/net/sock.h:?) process_schedu= led_works (kernel/workqueue.c:?) worker_thread (kernel/workqueue.c:?) kthre=
    ad (kernel/kthread.c:438) ret_from_fork (arch/x86/kernel/process.c:164) ret= _from_fork_asm (arch/x86/entry/entry_64.S:258)</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53005" target=3D= "_blank" rel=3D"noopener">CVE-2026-53005</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ice=
    : fix double-free of tx_buf skb If ice_tso() or ice_tx_csum() fail, the err=
    or path in ice_xmit_frame_ring() frees the skb, but the 'first' tx_buf stil=
    l points to it and is marked as valid (ICE_TX_BUF_SKB). 'next_to_use' remai=
    ns unchanged, so the potential problem will likely fix itself when the next=
    packet is transmitted and the tx_buf gets overwritten. But if there is no = next packet and the interface is brought down instead, ice_clean_tx_ring() = -&gt; ice_unmap_and_free_tx_buf() will find the tx_buf and free the skb for=
    the second time. The fix is to reset the tx_buf type to ICE_TX_BUF_EMPTY i=
    n the error path, so that ice_unmap_and_free_tx_buf(). Move the initializat= ion of 'first' up, to ensure it's already valid in case we hit the lineariz= ation error path. The bug was spotted by AI while I had it looking for some= thing else. It also proposed an initial version of the patch. I reproduced = the bug and tested the fix by adding code to inject failures, on a build wi=
    th KASAN. I looked for similar bugs in related Intel drivers and did not fi=
    nd any.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53009" target=3D= "_blank" rel=3D"noopener">CVE-2026-53009</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /sched: taprio: fix use-after-free in advance_sched() on schedule switch In=
    advance_sched(), when should_change_schedules() returns true, switch_sched= ules() is called to promote the admin schedule to oper. switch_schedules() = queues the old oper schedule for RCU freeing via call_rcu(), but 'next' sti=
    ll points into an entry of the old oper schedule. The subsequent 'next-&gt;= end_time =3D end_time' and rcu_assign_pointer(q-&gt;current_entry, next) ar=
    e use-after-free. Fix this by selecting 'next' from the new oper schedule i= mmediately after switch_schedules(), and using its pre-calculated end_time.=
    setup_first_end_time() sets the first entry's end_time to base_time + inte= rval when the schedule is installed, so the value is already correct. The d= eleted 'end_time =3D sched_base_time(admin)' assignment was also harmful in= dependently: it would overwrite the new first entry's pre-calculated end_ti=
    me with just base_time.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53011" target=3D= "_blank" rel=3D"noopener">CVE-2026-53011</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: cry= pto: ccp - copy IV using skcipher ivsize AF_ALG rfc3686-ctr-aes-ccp request=
    s pass an 8-byte IV to the driver. ccp_aes_complete() restores AES_BLOCK_SI=
    ZE bytes into the caller's IV buffer while RFC3686 skciphers expose an 8-by=
    te IV, so the restore overruns the provided buffer. Use crypto_skcipher_ivs= ize() to copy only the algorithm's IV length.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53016" target=3D= "_blank" rel=3D"noopener">CVE-2026-53016</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: um:=
    Fix potential race condition in TLB sync During the TLB sync, we need to t= raverse and modify the page table, so we should hold the page table lock. S= ince full SMP support for threads within the same process is still missing,=
    let's disable the split page table lock for simplicity.</td> <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53020" target=3D= "_blank" rel=3D"noopener">CVE-2026-53020</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: gre= ybus: raw: fix use-after-free if write is called after disconnect If a user=
    writes to the chardev after disconnect has been called, the kernel panics = with the following trace (with CONFIG_INIT_ON_FREE_DEFAULT_ON=3Dy): BUG: ke= rnel NULL pointer dereference, address: 0000000000000218 ... Call Trace: &l= t;TASK&gt; gb_operation_create_common+0x61/0x180 gb_operation_create_flags+= 0x28/0xa0 gb_operation_sync_timeout+0x6f/0x100 raw_write+0x7b/0xc7 [gb_raw]=
    vfs_write+0xcf/0x420 ? task_mm_cid_work+0x136/0x220 ksys_write+0x63/0xe0 d= o_syscall_64+0xa4/0x290 entry_SYSCALL_64_after_hwframe+0x77/0x7f Disconnect=
    calls gb_connection_destroy, which ends up freeing the connection object. = When gb_operation_sync is called in the write file operations, its gets a f= reed connection as parameter and the kernel panics. The gb_connection_destr=
    oy cannot be moved out of the disconnect function, as the Greybus subsystem=
    expect all connections belonging to a bundle to be destroyed when disconne=
    ct returns. To prevent this bug, use a rw lock to synchronize access betwee=
    n write and disconnect. This guarantees that the write function doesn't try=
    to use a disconnected connection.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53024" target=3D= "_blank" rel=3D"noopener">CVE-2026-53024</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: gre= ybus: raw: fix use-after-free on cdev close This addresses a use-after-free=
    bug when a raw bundle is disconnected but its chardev is still opened by a=
    n application. When the application releases the cdev, it causes the follow= ing panic when init on free is enabled (CONFIG_INIT_ON_FREE_DEFAULT_ON=3Dy)=
    : refcount_t: underflow; use-after-free. WARNING: CPU: 0 PID: 139 at lib/re= fcount.c:28 refcount_warn_saturate+0xd0/0x130 ... Call Trace: &lt;TASK&gt; = cdev_put+0x18/0x30 __fput+0x255/0x2a0 __x64_sys_close+0x3d/0x80 do_syscall_= 64+0xa4/0x290 entry_SYSCALL_64_after_hwframe+0x77/0x7f The cdev is containe=
    d in the "gb_raw" structure, which is freed in the disconnect operation. Wh=
    en the cdev is released at a later time, cdev_put gets an address that poin=
    ts to freed memory. To fix this use-after-free, convert the struct device f= rom a pointer to being embedded, that makes the lifetime of the cdev and of=
    this device the same. Then, use cdev_device_add, which guarantees that the=
    device won't be released until all references to the cdev have been releas= ed. Finally, delegate the freeing of the structure to the device release fu= nction, instead of freeing immediately in the disconnect callback.</td> <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53025" target=3D= "_blank" rel=3D"noopener">CVE-2026-53025</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: NFS=
    D: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg In nfs= d4_add_rdaccess_to_wrdeleg, if fp-&gt;fi_fds[O_RDONLY] is already set by an= other thread, __nfs4_file_get_access should not be called to increment the = nfs4_file access count since that was already done by the thread that added=
    READ access to the file. The extra fi_access count in nfs4_file can preven=
    t the corresponding nfsd_file from being freed. When stopping nfs-server se= rvice, these extra access counts trigger a BUG in kmem_cache_destroy() that=
    shows nfsd_file object remaining on __kmem_cache_shutdown. This problem ca=
    n be reproduced by running the Git project's test suite over NFS.</td> <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53026" target=3D= "_blank" rel=3D"noopener">CVE-2026-53026</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Validate node_id in arena_alloc_pages() arena_alloc_pages() accepts a pla=
    in int node_id and forwards it through the entire allocation chain without = any bounds checking. Validate node_id before passing it down the allocation=
    chain in arena_alloc_pages().</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53031" target=3D= "_blank" rel=3D"noopener">CVE-2026-53031</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    , sockmap: Take state lock for af_unix iter When a BPF iterator program upd= ates a sockmap, there is a race condition in unix_stream_bpf_update_proto()=
    where the `peer` pointer can become stale[1] during a state transition TCP= _ESTABLISHED -&gt; TCP_CLOSE. CPU0 bpf CPU1 close -------- ---------- // un= ix_stream_bpf_update_proto() sk_pair =3D unix_peer(sk) if (unlikely(!sk_pai= r)) return -EINVAL; // unix_release_sock() skpair =3D unix_peer(sk); unix_p= eer(sk) =3D NULL; sock_put(skpair) sock_hold(sk_pair) // UaF More practical= ly, this fix guarantees that the iterator program is consistently provided = with a unix socket that remains stable during iterator execution. [1]: BUG:=
    KASAN: slab-use-after-free in unix_stream_bpf_update_proto+0x155/0x490 Wri=
    te of size 4 at addr ffff8881178c9a00 by task test_progs/2231 Call Trace: d= ump_stack_lvl+0x5d/0x80 print_report+0x170/0x4f3 kasan_report+0xe4/0x1c0 ka= san_check_range+0x125/0x200 unix_stream_bpf_update_proto+0x155/0x490 sock_m= ap_link+0x71c/0xec0 sock_map_update_common+0xbc/0x600 sock_map_update_elem+= 0x19a/0x1f0 bpf_prog_bbbf56096cdd4f01_selective_dump_unix+0x20c/0x217 bpf_i= ter_run_prog+0x21e/0xae0 bpf_iter_unix_seq_show+0x1e0/0x2a0 bpf_seq_read+0x= 42c/0x10d0 vfs_read+0x171/0xb20 ksys_read+0xff/0x200 do_syscall_64+0xf7/0x5=
    e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Allocated by task 2236: kasan_s= ave_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_slab_alloc+0x63/0x80=
    kmem_cache_alloc_noprof+0x1d5/0x680 sk_prot_alloc+0x59/0x210 sk_alloc+0x34= /0x470 unix_create1+0x86/0x8a0 unix_stream_connect+0x318/0x15b0 __sys_conne= ct+0xfd/0x130 __x64_sys_connect+0x72/0xd0 do_syscall_64+0xf7/0x5e0 entry_SY= SCALL_64_after_hwframe+0x76/0x7e Freed by task 2236: kasan_save_stack+0x30/= 0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x70 __kasan_slab= _free+0x47/0x70 kmem_cache_free+0x11c/0x590 __sk_destruct+0x432/0x6e0 unix_= release_sock+0x9b3/0xf60 unix_release+0x8a/0xf0 __sock_release+0xb0/0x270 s= ock_close+0x18/0x20 __fput+0x36e/0xac0 fput_close_sync+0xe5/0x1a0 __x64_sys= _close+0x7d/0xd0 do_syscall_64+0xf7/0x5e0 entry_SYSCALL_64_after_hwframe+0x= 76/0x7e</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53033" target=3D= "_blank" rel=3D"noopener">CVE-2026-53033</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    , arm64: Fix off-by-one in check_imm signed range check check_imm(bits, imm=
    ) is used in the arm64 BPF JIT to verify that a branch displacement (in arm=
    64 instruction units) fits into the signed N-bit immediate field of a B, B.= cond or CBZ/CBNZ encoding before it is handed to the encoder. The macro cur= rently tests for (imm &gt; 0 &amp;&amp; imm &gt;&gt; bits) || (imm &lt; 0 &= amp;&amp; ~imm &gt;&gt; bits) which admits values in [-2^N, 2^N) - effectiv= ely a signed (N+1)-bit range. A signed N-bit field only holds [-2^(N-1), 2^= (N-1)), so the check admits one extra bit of range on each side. In particu= lar, for check_imm19(), values in [2^18, 2^19) slip past the check but do n=
    ot fit into the 19-bit signed imm19 field of B.cond. aarch64_insn_encode_im= mediate() then masks the raw value into the 19-bit field, setting bit 18 (t=
    he sign bit) and flipping a forward branch into a backward one. Same class =
    of issue exists for check_imm26() and the B/BL encoding. Shift by (bits - 1=
    ) instead of bits so the actual signed N-bit range is enforced.</td> <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53036" target=3D= "_blank" rel=3D"noopener">CVE-2026-53036</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ocf= s2: validate bg_bits during freefrag scan [BUG] A crafted filesystem can tr= igger an out-of-bounds bitmap walk when OCFS2_IOC_INFO is issued with OCFS2= _INFO_FL_NON_COHERENT. BUG: KASAN: use-after-free in instrument_atomic_read=
    include/linux/instrumented.h:68 [inline] BUG: KASAN: use-after-free in _te= st_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] BU=
    G: KASAN: use-after-free in test_bit_le include/asm-generic/bitops/le.h:21 = [inline] BUG: KASAN: use-after-free in ocfs2_info_freefrag_scan_chain fs/oc= fs2/ioctl.c:495 [inline] BUG: KASAN: use-after-free in ocfs2_info_freefrag_= scan_bitmap fs/ocfs2/ioctl.c:588 [inline] BUG: KASAN: use-after-free in ocf= s2_info_handle_freefrag fs/ocfs2/ioctl.c:662 [inline] BUG: KASAN: use-after= -free in ocfs2_info_handle_request+0x1c66/0x3370 fs/ocfs2/ioctl.c:754 Read =
    of size 8 at addr ffff888031bce000 by task syz.0.636/1435 Call Trace: __dum= p_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xbe/0x130 lib/dump_sta= ck.c:120 print_address_description mm/kasan/report.c:378 [inline] print_rep= ort+0xd1/0x650 mm/kasan/report.c:482 kasan_report+0xfb/0x140 mm/kasan/repor= t.c:595 check_region_inline mm/kasan/generic.c:186 [inline] kasan_check_ran= ge+0x11c/0x200 mm/kasan/generic.c:200 __kasan_check_read+0x11/0x20 mm/kasan= /shadow.c:31 instrument_atomic_read include/linux/instrumented.h:68 [inline=
    ] _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inlin=
    e] test_bit_le include/asm-generic/bitops/le.h:21 [inline] ocfs2_info_freef= rag_scan_chain fs/ocfs2/ioctl.c:495 [inline] ocfs2_info_freefrag_scan_bitma=
    p fs/ocfs2/ioctl.c:588 [inline] ocfs2_info_handle_freefrag fs/ocfs2/ioctl.c= :662 [inline] ocfs2_info_handle_request+0x1c66/0x3370 fs/ocfs2/ioctl.c:754 = ocfs2_info_handle+0x18d/0x2a0 fs/ocfs2/ioctl.c:828 ocfs2_ioctl+0x632/0x6e0 = fs/ocfs2/ioctl.c:913 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioc= tl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x= 197/0x1e0 fs/ioctl.c:583 ... [CAUSE] ocfs2_info_freefrag_scan_chain() uses = on-disk bg_bits directly as the bitmap scan limit. The coherent path reads = group descriptors through ocfs2_read_group_descriptor(), which validates th=
    e descriptor before use. The non-coherent path uses ocfs2_read_blocks_sync(=
    ) instead and skips that validation, so an impossible bg_bits value can dri=
    ve the bitmap walk past the end of the block. [FIX] Compute the bitmap capa= city from the filesystem format with ocfs2_group_bitmap_size(), report desc= riptors whose bg_bits exceeds that limit, and clamp the scan to the compute=
    d capacity. This keeps the freefrag report going while avoiding reads beyon=
    d the buffer.</td>
    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53040" target=3D= "_blank" rel=3D"noopener">CVE-2026-53040</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ocf= s2: fix listxattr handling when the buffer is full [BUG] If an OCFS2 inode = has both inline and block-based xattrs, listxattr() can return a size large=
    r than the caller's buffer when the inline names consume that buffer exactl=
    y. kernel BUG at mm/usercopy.c:102! Oops: invalid opcode: 0000 [#1] SMP KAS=
    AN NOPTI RIP: 0010:usercopy_abort+0xb7/0xd0 mm/usercopy.c:102 Call Trace: _= _check_heap_object+0xe3/0x120 mm/slub.c:8243 check_heap_object mm/usercopy.= c:196 [inline] __check_object_size mm/usercopy.c:250 [inline] __check_objec= t_size+0x5c5/0x780 mm/usercopy.c:215 check_object_size include/linux/ucopys= ize.h:22 [inline] check_copy_size include/linux/ucopysize.h:59 [inline] cop= y_to_user include/linux/uaccess.h:219 [inline] listxattr+0xb0/0x170 fs/xatt= r.c:926 filename_listxattr fs/xattr.c:958 [inline] path_listxattrat+0x137/0= x320 fs/xattr.c:988 __do_sys_listxattr fs/xattr.c:1001 [inline] __se_sys_li= stxattr fs/xattr.c:998 [inline] __x64_sys_listxattr+0x7f/0xd0 fs/xattr.c:99=
    8 ... [CAUSE] Commit 936b8834366e ("ocfs2: Refactor xattr list and remove o= cfs2_xattr_handler().") replaced the old per-handler list accounting with o= cfs2_xattr_list_entry(), but it kept using size =3D=3D 0 to detect probe mo= de. That assumption stops being true once ocfs2_listxattr() finishes the in= line-xattr pass. If the inline names fill the caller buffer exactly, the bl= ock-xattr pass runs with a non-NULL buffer and a remaining size of zero. oc= fs2_xattr_list_entry() then skips the bounds check, keeps counting block na= mes, and returns a positive size larger than the supplied buffer. [FIX] Det= ect probe mode by testing whether the destination buffer pointer is NULL in= stead of whether the remaining size is zero. That restores the pre-refactor=
    behavior and matches the OCFS2 getxattr helpers. Once the remaining buffer=
    reaches zero while more names are left, the block-xattr pass now returns -= ERANGE instead of reporting a size larger than the allocated list buffer.</=

    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53041" target=3D= "_blank" rel=3D"noopener">CVE-2026-53041</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: soc= /tegra: cbb: Fix incorrect ARRAY_SIZE in fabric lookup tables Fix incorrect=
    ARRAY_SIZE usage in fabric lookup tables which could cause out-of-bounds a= ccess during target timeout lookup.</td>
    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53044" target=3D= "_blank" rel=3D"noopener">CVE-2026-53044</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: quo= ta: Fix race of dquot_scan_active() with quota deactivation dquot_scan_acti= ve() can race with quota deactivation in quota_release_workfn() like: CPU0 = (quota_release_workfn) CPU1 (dquot_scan_active) =3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D spin_lock(&amp;dq_list_lock); list_replace_init( &amp;releasing_dquo= ts, &amp;rls_head); /* dquot X on rls_head, dq_count =3D=3D 0, DQ_ACTIVE_B = still set */ spin_unlock(&amp;dq_list_lock); synchronize_srcu(&amp;dquot_sr= cu); spin_lock(&amp;dq_list_lock); list_for_each_entry(dquot, &amp;inuse_li= st, dq_inuse) { /* finds dquot X */ dquot_active(X) -&gt; true atomic_inc(&= amp;X-&gt;dq_count); } spin_unlock(&amp;dq_list_lock); spin_lock(&amp;dq_li= st_lock); dquot =3D list_first_entry(&amp;rls_head); WARN_ON_ONCE(atomic_re= ad(&amp;dquot-&gt;dq_count)); The problem is not only a cosmetic one as und=
    er memory pressure the caller of dquot_scan_active() can end up working on = freed dquot. Fix the problem by making sure the dquot is removed from relea= sing list when we acquire a reference to it.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53050" target=3D= "_blank" rel=3D"noopener">CVE-2026-53050</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /msm: Fix VM_BIND UNMAP locking Wrong argument meant that the objs involved=
    in UNMAP ops were not always getting locked. Since _NO_SHARE objs share a = common resv with the VM (which is always locked) this would only show up wi=
    th non-_NO_SHARE BOs. Patchwork: https://patchwork.freedesktop.org/patch/71= 3898/</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53054" target=3D= "_blank" rel=3D"noopener">CVE-2026-53054</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: dm = cache policy smq: fix missing locks in invalidating cache blocks In passthr= ough mode, the policy invalidate_mapping operation is called simultaneously=
    from multiple workers, thus it should be protected by a lock. Otherwise, w=
    e might end up with data races on the allocated blocks counter, or even use= -after-free issues with internal data structures when doing concurrent writ= es. Note that the existing FIXME in smq_invalidate_mapping() doesn't affect=
    passthrough mode since migration tasks don't exist there, but would need a= ttention if supporting fast device shrinking via suspend/resume without tar= get reloading. Reproduce steps: 1. Create a cache device consisting of 1024=
    cache entries dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmse= tup create cdata --table "0 131072 linear /dev/sdc 8192" dmsetup create cor=
    ig --table "0 262144 linear /dev/sdc 262144" dd if=3D/dev/zero of=3D/dev/ma= pper/cmeta bs=3D4k count=3D1 oflag=3Ddirect dmsetup create cache --table "0=
    262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2=
    metadata2 writethrough smq 0" 2. Populate the cache, and record the number=
    of cached blocks fio --name=3Dpopulate --filename=3D/dev/mapper/cache --rw= =3Drandwrite --bs=3D4k \ --size=3D64m --direct=3D1 nr_cached=3D$(dmsetup st= atus cache | awk '{split($7, a, "/"); print a[1]}') 3. Reload the cache int=
    o passthrough mode dmsetup suspend cache dmsetup reload cache --table "0 26= 2144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 me= tadata2 passthrough smq 0" dmsetup resume cache 4. Write to the passthrough=
    cache. By setting multiple jobs with I/O size equal to the cache block siz=
    e, cache blocks are invalidated concurrently from different workers. fio --= filename=3D/dev/mapper/cache --name=3Dtest --rw=3Drandwrite --bs=3D64k \ --= direct=3D1 --numjobs=3D2 --randrepeat=3D0 --size=3D64m 5. Check if demoted = matches cached block count. These numbers should match but may differ due t=
    o the data race. nr_demoted=3D$(dmsetup status cache | awk '{print $12}') e= cho "$nr_cached, $nr_demoted"</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53062" target=3D= "_blank" rel=3D"noopener">CVE-2026-53062</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /komeda: fix integer overflow in AFBC framebuffer size check The AFBC frame= buffer size validation calculates the minimum required buffer size by addin=
    g the AFBC payload size to the framebuffer offset. This addition is perform=
    ed without checking for integer overflow. If the addition oveflows, the siz=
    e check may incorrectly succed and allow userspace to provide an undersized=
    drm_gem_object, potentially leading to out-of-bounds memory access. Add us= age of check_add_overflow() to safely compute the minimum required size and=
    reject the framebuffer if an overflow is detected. This makes the AFBC siz=
    e validation more robust against malformed. Found by Linux Verification Cen= ter (linuxtesting.org) with SVACE.</td>
    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53068" target=3D= "_blank" rel=3D"noopener">CVE-2026-53068</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    , bpf: fix null-ptr-deref in xdp_master_redirect() for down master syzkalle=
    r reported a kernel panic in bond_rr_gen_slave_id() reached via xdp_master_= redirect(). Full decoded trace: https://syzkaller.appspot.com/bug?extid=3D8= 0e046b8da2820b6ba73 bond_rr_gen_slave_id() dereferences bond-&gt;rr_tx_coun= ter, a per-CPU counter that bonding only allocates in bond_open() when the = mode is round-robin. If the bond device was never brought up, rr_tx_counter=
    stays NULL. The XDP redirect path can still reach that code on a bond that=
    was never opened: bpf_master_redirect_enabled_key is a global static key, =
    so as soon as any bond device has native XDP attached, the XDP_TX -&gt; xdp= _master_redirect() interception is enabled for every slave system-wide. The=
    path xdp_master_redirect() -&gt; bond_xdp_get_xmit_slave() -&gt; bond_xdp_= xmit_roundrobin_slave_get() -&gt; bond_rr_gen_slave_id() then runs against =
    a bond that has no rr_tx_counter and crashes. Fix this in the generic xdp_m= aster_redirect() by refusing to call into the master's -&gt;ndo_xdp_get_xmi= t_slave() when the master device is not up. IFF_UP is only set after -&gt;n= do_open() has successfully returned, so this reliably excludes masters whos=
    e XDP state has not been fully initialized. Drop the frame with XDP_ABORTED=
    so the exception is visible via trace_xdp_exception() rather than silently=
    falling through. This is not specific to bonding: any current or future ma= ster that defers XDP state allocation to -&gt;ndo_open() is protected.</td> <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53069" target=3D= "_blank" rel=3D"noopener">CVE-2026-53069</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sct=
    p: disable BH before calling udp_tunnel_xmit_skb() udp_tunnel_xmit_skb() / = udp_tunnel6_xmit_skb() are expected to run with BH disabled. After commit 6= f1a9140ecda ("add xmit recursion limit to tunnel xmit functions"), on the p= ath: udp(6)_tunnel_xmit_skb() -&gt; ip(6)tunnel_xmit() dev_xmit_recursion_i= nc()/dec() must stay balanced on the same CPU. Without local_bh_disable(), = the context may move between CPUs, which can break the inc/dec pairing. Thi=
    s may lead to incorrect recursion level detection and cause packets to be d= ropped in ip(6)_tunnel_xmit() or __dev_queue_xmit(). Fix it by disabling BH=
    around both IPv4 and IPv6 SCTP UDP xmit paths. In my testing, after enabli=
    ng the SCTP over UDP: # ip net exec ha sysctl -w net.sctp.udp_port=3D9899 #=
    ip net exec ha sysctl -w net.sctp.encap_port=3D9899 # ip net exec hb sysct=
    l -w net.sctp.udp_port=3D9899 # ip net exec hb sysctl -w net.sctp.encap_por= t=3D9899 # ip net exec ha iperf3 -s - without this patch: # ip net exec hb = iperf3 -c 192.168.0.1 --sctp [ 5] 0.00-10.00 sec 37.2 MBytes 31.2 Mbits/sec=
    sender [ 5] 0.00-10.00 sec 37.1 MBytes 31.1 Mbits/sec receiver - with this=
    patch: # ip net exec hb iperf3 -c 192.168.0.1 --sctp [ 5] 0.00-10.00 sec 3= .14 GBytes 2.69 Gbits/sec sender [ 5] 0.00-10.00 sec 3.14 GBytes 2.69 Gbits= /sec receiver</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53070" target=3D= "_blank" rel=3D"noopener">CVE-2026-53070</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix OOB in pcpu_init_value An out-of-bounds read occurs when copying elem= ent from a BPF_MAP_TYPE_CGROUP_STORAGE map to another pcpu map with the sam=
    e value_size that is not rounded up to 8 bytes. The issue happens when: 1. =
    A CGROUP_STORAGE map is created with value_size not aligned to 8 bytes (e.g=
    ., 4 bytes) 2. A pcpu map is created with the same value_size (e.g., 4 byte=
    s) 3. Update element in 2 with data in 1 pcpu_init_value assumes that all s= ources are rounded up to 8 bytes, and invokes copy_map_value_long to make a=
    data copy, However, the assumption doesn't stand since there are some case=
    s where the source may not be rounded up to 8 bytes, e.g., CGROUP_STORAGE, = skb-&gt;data. the verifier verifies exactly the size that the source claims=
    , not the size rounded up to 8 bytes by kernel, an OOB happens when the sou= rce has only 4 bytes while the copy size(4) is rounded up to 8.</td> <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53076" target=3D= "_blank" rel=3D"noopener">CVE-2026-53076</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /rds: Restrict use of RDS/IB to the initial network namespace Prevent using=
    RDS/IB in network namespaces other than the initial one. The existing RDS/=
    IB code will not work properly in non-initial network namespaces.</td> <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53077" target=3D= "_blank" rel=3D"noopener">CVE-2026-53077</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix same-register dst/src OOB read and pointer leak in sock_ops When a BP=
    F sock_ops program accesses ctx fields with dst_reg =3D=3D src_reg, the SOC= K_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination=
    register in the !fullsock / !locked_tcp_sock path. Both macros borrow a te= mporary register to check is_fullsock / is_locked_tcp_sock when dst_reg =3D= =3D src_reg, because dst_reg holds the ctx pointer. When the check is false=
    (e.g., TCP_NEW_SYN_RECV state with a request_sock), dst_reg should be zero=
    ed but is not, leaving the stale ctx pointer: - SOCK_OPS_GET_SK: dst_reg re= tains the ctx pointer, passes NULL checks as PTR_TO_SOCKET_OR_NULL, and can=
    be used as a bogus socket pointer, leading to stack-out-of-bounds access i=
    n helpers like bpf_skc_to_tcp6_sock(). - SOCK_OPS_GET_FIELD: dst_reg retain=
    s the ctx pointer which the verifier believes is a SCALAR_VALUE, leaking a = kernel pointer. Fix both macros by: - Changing JMP_A(1) to JMP_A(2) in the = fullsock path to skip the added instruction. - Adding BPF_MOV64_IMM(si-&gt;= dst_reg, 0) after the temp register restore in the !fullsock path, placed a= fter the restore because dst_reg =3D=3D src_reg means we need src_reg intac=
    t to read ctx-&gt;temp.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53078" target=3D= "_blank" rel=3D"noopener">CVE-2026-53078</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Enforce regsafe base id consistency for BPF_ADD_CONST scalars When regsaf= e() compares two scalar registers that both carry BPF_ADD_CONST, check_scal= ar_ids() maps their full compound id (aka base | BPF_ADD_CONST flag) as one=
    idmap entry. However, it never verifies that the underlying base ids, that=
    is, with the flag stripped are consistent with existing idmap mappings. Th=
    is allows construction of two verifier states where the old state has R3 =
    =3D R2 + 10 (both sharing base id A) while the current state has R3 =3D R4 =
    + 10 (base id C, unrelated to R2). The idmap creates two independent entrie=
    s: A-&gt;B (for R2) and A|flag-&gt;C|flag (for R3), without catching that A= -&gt;C conflicts with A-&gt;B. State pruning then incorrectly succeeds. Fix=
    this by additionally verifying base ID mapping consistency whenever BPF_AD= D_CONST is set: after mapping the compound ids, also invoke check_ids() on = the base IDs (flag bits stripped). This ensures that if A was already mappe=
    d to B from comparing the source register, any ADD_CONST derivative must al=
    so derive from B, not an unrelated C.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53081" target=3D= "_blank" rel=3D"noopener">CVE-2026-53081</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : fix mm lifecycle in open-coded task_vma iterator The open-coded task_vma = iterator reads task-&gt;mm locklessly and acquires mmap_read_trylock() but = never calls mmget(). If the task exits concurrently, the mm_struct can be f= reed as it is not SLAB_TYPESAFE_BY_RCU, resulting in a use-after-free. Safe=
    ly read task-&gt;mm with a trylock on alloc_lock and acquire an mm referenc=
    e. Drop the reference via bpf_iter_mmput_async() in _destroy() and error pa= ths. bpf_iter_mmput_async() is a local wrapper around mmput_async() with a = fallback to mmput() on !CONFIG_MMU. Reject irqs-disabled contexts (includin=
    g NMI) up front. Operations used by _next() and _destroy() (mmap_read_unloc=
    k, bpf_iter_mmput_async) take spinlocks with IRQs disabled (pool-&gt;lock, = pi_lock). Running from NMI or from a tracepoint that fires with those locks=
    held could deadlock. A trylock on alloc_lock is used instead of the blocki=
    ng task_lock() (get_task_mm) to avoid a deadlock when a softirq BPF program=
    iterates a task that already holds its alloc_lock on the same CPU.</td> <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53085" target=3D= "_blank" rel=3D"noopener">CVE-2026-53085</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : bcmgenet: fix leaking free_bds While reclaiming the tx queue we fast forw= ard the write pointer to drop any data in flight. These dropped frames are = not added back to the pool of free bds. We also need to tell the netdev tha=
    t we are dropping said data.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53087" target=3D= "_blank" rel=3D"noopener">CVE-2026-53087</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} = instructions got extended into subprogs some time ago via commit 09b28d76ea=
    c4 ("bpf: Add abnormal return checks."). These are only allowed in subprogr= ams when the latter are BTF annotated and have scalar return types. The cod=
    e generator in bpf_gen_ld_abs() has an abnormal exit path (r0=3D0 + exit) f= rom legacy cBPF times. While the enforcement is on scalar return types, the=
    verifier must also simulate the path of abnormal exit if the packet data l= oad via ld_{abs,ind} failed. This is currently not the case. Fix it by havi=
    ng the verifier simulate both success and failure paths, and extend it in s= imilar ways as we do for tail calls. The success path (r0=3Dunknown, contin=
    ue to next insn) is pushed onto stack for later validation and the r0=3D0 a=
    nd return to the caller is done on the fall-through side.</td> <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53090" target=3D= "_blank" rel=3D"noopener">CVE-2026-53090</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix linked reg delta tracking when src_reg =3D=3D dst_reg Consider the ca=
    se of rX +=3D rX where src_reg and dst_reg are pointers to the same bpf_reg= _state in adjust_reg_min_max_vals(). The latter first modifies the dst_reg = in-place, and later in the delta tracking, the subsequent is_reg_const(src_= reg)/reg_const_value(src_reg) reads the post-{add,sub} value instead of the=
    original source. This is problematic since it sets an incorrect delta, whi=
    ch sync_linked_regs() then propagates to linked registers, thus creating a = verifier-vs-runtime mismatch. Fix it by just skipping this corner case.</td=

    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53092" target=3D= "_blank" rel=3D"noopener">CVE-2026-53092</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix stale offload-&gt;prog pointer after constant blinding When a dev-bou= nd-only BPF program (BPF_F_XDP_DEV_BOUND_ONLY) undergoes JIT compilation wi=
    th constant blinding enabled (bpf_jit_harden &gt;=3D 2), bpf_jit_blind_cons= tants() clones the program. The original prog is then freed in bpf_jit_prog= _release_other(), which updates aux-&gt;prog to point to the surviving clon=
    e, but fails to update offload-&gt;prog. This leaves offload-&gt;prog point= ing to the freed original program. When the network namespace is subsequent=
    ly destroyed, cleanup_net() triggers bpf_dev_bound_netdev_unregister(), whi=
    ch iterates ondev-&gt;progs and calls __bpf_prog_offload_destroy(offload-&g= t;prog). Accessing the freed prog causes a page fault: BUG: unable to handl=
    e page fault for address: ffffc900085f1038 Workqueue: netns cleanup_net RIP=
    : 0010:__bpf_prog_offload_destroy+0xc/0x80 Call Trace: __bpf_offload_dev_ne= tdev_unregister+0x257/0x350 bpf_dev_bound_netdev_unregister+0x4a/0x90 unreg= ister_netdevice_many_notify+0x2a2/0x660 ... cleanup_net+0x21a/0x320 The tes=
    t sequence that triggers this reliably is: 1. Set net.core.bpf_jit_harden=
    =3D2 (echo 2 &gt; /proc/sys/net/core/bpf_jit_harden) 2. Run xdp_metadata se= lftest, which creates a dev-bound-only XDP program on a veth inside a netns=
    (./test_progs -t xdp_metadata) 3. cleanup_net -&gt; page fault in __bpf_pr= og_offload_destroy Dev-bound-only programs are unique in that they have an = offload structure but go through the normal JIT path instead of bpf_prog_of= fload_compile(). This means they are subject to constant blinding's prog cl= one-and-replace, while also having offload-&gt;prog that must stay in sync.=
    Fix this by updating offload-&gt;prog in bpf_jit_prog_release_other(), alo= ngside the existing aux-&gt;prog update. Both are back-pointers to the prog=
    that must be kept in sync when the prog is replaced.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53094" target=3D= "_blank" rel=3D"noopener">CVE-2026-53094</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Use RCU-safe iteration in dev_map_redirect_multi() SKB path The DEVMAP_HA=
    SH branch in dev_map_redirect_multi() uses hlist_for_each_entry_safe() to i= terate hash buckets, but this function runs under RCU protection (called fr=
    om xdp_do_generic_redirect_map() in softirq context). Concurrent writers (_= _dev_map_hash_update_elem, dev_map_hash_delete_elem) modify the list using = RCU primitives (hlist_add_head_rcu, hlist_del_rcu). hlist_for_each_entry_sa= fe() performs plain pointer dereferences without rcu_dereference(), missing=
    the acquire barrier needed to pair with writers' rcu_assign_pointer(). On = weakly-ordered architectures (ARM64, POWER), a reader can observe a partial= ly-constructed node. It also defeats CONFIG_PROVE_RCU lockdep validation an=
    d KCSAN data-race detection. Replace with hlist_for_each_entry_rcu() using = rcu_read_lock_bh_held() as the lockdep condition, consistent with the rcu_d= ereference_check() used in the DEVMAP (non-hash) branch of the same functio= ns. Also fix the same incorrect lockdep_is_held(&amp;dtab-&gt;index_lock) c= ondition in dev_map_enqueue_multi(), where the lock is not held either.</td=

    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53096" target=3D= "_blank" rel=3D"noopener">CVE-2026-53096</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: s39= 0/bpf: Zero-extend bpf prog return values and kfunc arguments s390x ABI req= uires callers to zero-extend unsigned arguments and sign-extend signed argu= ments, and callees to zero-extend unsigned return values and sign-extend si= gned return values. s390 BPF JIT currently implements only sign extension. = Fix this omission and implement zero extension too.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53110" target=3D= "_blank" rel=3D"noopener">CVE-2026-53110</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fs/= omfs: reject s_sys_blocksize smaller than OMFS_DIR_START omfs_fill_super() = rejects oversized s_sys_blocksize values (&gt; PAGE_SIZE), but it does not = reject values smaller than OMFS_DIR_START (0x1b8 =3D 440). Later, omfs_make= _empty() uses sbi-&gt;s_sys_blocksize - OMFS_DIR_START as the length argume=
    nt to memset(). Since s_sys_blocksize is u32, a crafted filesystem image wi=
    th s_sys_blocksize &lt; OMFS_DIR_START causes an unsigned underflow there, = wrapping to a value near 2^32. That drives a ~4 GiB memset() from bh-&gt;b_= data + OMFS_DIR_START and overwrites kernel memory far beyond the backing b= lock buffer. Add the corresponding lower-bound check alongside the existing=
    upper-bound check in omfs_fill_super(), so that malformed images are rejec= ted during superblock validation before any filesystem data is processed.</=

    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53130" target=3D= "_blank" rel=3D"noopener">CVE-2026-53130</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: vso= ck/virtio: fix potential unbounded skb queue virtio_transport_inc_rx_pkt() = checks vvs-&gt;rx_bytes + len &gt; vvs-&gt;buf_alloc. virtio_transport_recv= _enqueue() skips coalescing for packets with VIRTIO_VSOCK_SEQ_EOM. If fed w= ith packets with len =3D=3D 0 and VIRTIO_VSOCK_SEQ_EOM, a very large number=
    of packets can be queued because vvs-&gt;rx_bytes stays at 0. Fix this by = estimating the skb metadata size: (Number of skbs in the queue) * SKB_TRUES= IZE(0)</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53132" target=3D= "_blank" rel=3D"noopener">CVE-2026-53132</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: RDM= A/umem: Fix truncation for block sizes &gt;=3D 4G When the iommu is used th=
    e linearization of the mapping can give a single block that is very large s= plit across multiple SG entries. When __rdma_block_iter_next() reassembles = the split SG entries it is overflowing the 32 bit stack values and computed=
    the wrong DMA addresses for blocks after the truncation. Use the right typ=
    es to hold DMA addresses.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53133" target=3D= "_blank" rel=3D"noopener">CVE-2026-53133</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /gem: Try to fix change_handle ioctl, attempt 4 [airlied: just added some c= omments on how to reenable] On-list because the cat is out of the bag and w= e're clearly not good enough to figure this out in private. The story thus = far: 5e28b7b94408 ("drm: Set old handle to NULL before prime swap in change= _handle") tried to fix a race condition between the gem_close and gem_chang= e_handle ioctls, but got a few things wrong: - There's a confusion with the=
    local variable handle, which is actually the new handle, and so the two-st= age trick was actually applied to the wrong idr slot. 7164d78559b0 ("drm/ge=
    m: fix race between change_handle and handle_delete") tried to fix that by = adding yet another code block, but forgot to add the error handling. Which = meant we now have two paths, both kinda wrong. - dc366607c41c ("drm: Replac=
    e old pointer to new idr") tried to apply another fix, but inconsistently, = again because of the handle confusion - this would be the right fix (kinda,=
    somewhat, it's a mess) if we'd do the two-stage approach for the new handl=
    e. Except that wasn't the intent of the original fix. We also didn't have a=
    n igt merged for the original ioctl, which is a big no-go. This was attempt=
    ed to address off-list in the original bugfix, and amd QA people claimed th=
    e bug was fixed now. Very clearly that's not the case. Here's my attempt to=
    sort this out: - Rename the local variable to new_handle, the old aliasing=
    with args-&gt;handle is just too dangerously confusing. - Merge the gem ob=
    j lookup with the two-stage idr_replace so that we avoid getting ourselves = confused there. - This means we don't have a surplus temporary reference an= ymore, only an inherited from the idr. A concurrent gem_close on the new_ha= ndle could steal that. Fix that with the same two-stage approach create_tai=
    l uses. This is a bit overkill as documented in the comment, but I also don=
    't trust my ability to understand this all correctly, so go with the establ= ished pattern we have from other ioctls instead for maximum paranoia. - Adj= ust error paths. I've tried to make the error and success paths common, bec= ause they are identical except for which handle is removed and on which we = call idr_replace to (re)install the object again. But that made things mess= ier to read, so I've left it at the more verbose version, which unfortunate=
    ly hides the symmetry in the entire code flow a bit. - While at it, also re= place the 7 space indent with 1 tab. And finally, because I flat out don't = trust my abilities here at all anymore: - Disable the ioctl until we have t=
    he igt situation and everything else sorted out on-list and with full conse= nsus. v2: Sashiko noticed that I didn't handle the error path for idr_repla=
    ce correctly, it must be checked with IS_ERR_OR_NULL like in gem_handle_del= ete. So yeah, definitely should just the existing paths 1:1 because this is=
    endless amounts of tricky. Also add the Fixes: line for the original ioctl=
    , I forgot that too.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53145" target=3D= "_blank" rel=3D"noopener">CVE-2026-53145</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: thu= nderbolt: Limit XDomain response copy to actual frame size tb_xdomain_copy(=
    ) copies req-&gt;response_size bytes from the received packet buffer regard= less of the actual frame size. When a short response arrives, this reads pa=
    st the valid frame data in the DMA pool buffer into stale contents from pre= vious transactions. Use the minimum of frame size and expected response siz=
    e for the copy length.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53146" target=3D= "_blank" rel=3D"noopener">CVE-2026-53146</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mm/= list_lru: drain before clearing xarray entry on reparent memcg_reparent_lis= t_lrus() clears the dying memcg's xarray entry with xas_store(&amp;xas, NUL=
    L) before reparenting its per-node lists into the parent. This opens a wind=
    ow where a concurrent list_lru_del() arriving for the dying memcg sees xa_l= oad() =3D=3D NULL, walks to the parent in lock_list_lru_of_memcg(), takes t=
    he parent's per-node lock, and calls list_del_init() on an item still physi= cally linked on the dying memcg's list. If another in-flight thread holds t=
    he dying memcg's per-node lock at the same moment (another list_lru_del, or=
    a list_lru_walk_one running an isolate callback), both threads modify -&gt= ;next/-&gt;prev pointers on the same physical list under different locks. A= djacent items can corrupt each other's links. Fix it by reversing the order=
    : reparent each per-node list and mark the child's list lru dead and then c= lear the xarray entry. Any concurrent list_lru op that finds the still-set = xarray entry either takes the dying memcg's per-node lock (synchronizing wi=
    th the drain) or sees LONG_MIN and walks to the parent, where the items now=
    live.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53153" target=3D= "_blank" rel=3D"noopener">CVE-2026-53153</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mis=
    c: fastrpc: fix use-after-free race in fastrpc_map_create fastrpc_map_looku=
    p returns a raw pointer after releasing fl-&gt;lock. The caller fastrpc_map= _create then calls fastrpc_map_get (kref_get_unless_zero) on this unprotect=
    ed pointer. A concurrent MEM_UNMAP can free the map between the lock releas=
    e and the kref operation, resulting in a use-after-free on the freed slab o= bject. Restore the take_ref parameter to fastrpc_map_lookup so the referenc=
    e is acquired atomically under fl-&gt;lock before the pointer is exposed to=
    the caller.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53160" target=3D= "_blank" rel=3D"noopener">CVE-2026-53160</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mis=
    c: fastrpc: fix use-after-free of fastrpc_user in workqueue context There i=
    s a race between fastrpc_device_release() and the workqueue that processes = DSP responses. When the user closes the file descriptor, fastrpc_device_rel= ease() frees the fastrpc_user structure. Concurrently, an in-flight DSP inv= ocation can complete and fastrpc_rpmsg_callback() schedules context cleanup=
    via schedule_work(&amp;ctx-&gt;put_work). If the workqueue runs fastrpc_co= ntext_free() in parallel with or after fastrpc_device_release() has freed t=
    he user structure, it dereferences the freed fastrpc_user. Depending on the=
    state of the context at the time of the race, any one of the following acc= esses can be hit: 1. fastrpc_buf_free() calls fastrpc_ipa_to_dma_addr(buf-&= gt;fl-&gt;cctx, ...) to strip the SID bits from the stored IOVA before pass= ing the physical address to dma_free_coherent(). 2. fastrpc_free_map() read=
    s map-&gt;fl-&gt;cctx-&gt;vmperms[0].vmid to reconstruct the source permiss= ion bitmask needed for the qcom_scm_assign_mem() call that returns memory f= rom the DSP VM back to HLOS. 3. fastrpc_free_map() acquires map-&gt;fl-&gt;= lock to safely remove the map node from the fl-&gt;maps list. The resulting=
    use-after-free manifests as: pc : fastrpc_buf_free+0x38/0x80 [fastrpc] lr =
    : fastrpc_context_free+0xa8/0x1b0 [fastrpc] fastrpc_context_free+0xa8/0x1b0=
    [fastrpc] fastrpc_context_put_wq+0x78/0xa0 [fastrpc] process_one_work+0x18= 0/0x450 worker_thread+0x26c/0x388 Add kref-based reference counting to fast= rpc_user. Have each invoke context take a reference on the user at allocati=
    on time and release it when the context is freed. Release the initial refer= ence in fastrpc_device_release() at file close. Move the teardown of the us=
    er structure - freeing pending contexts, maps, mmaps, and the channel conte=
    xt reference - into the kref release callback fastrpc_user_free(), so that =
    it runs only when the last reference is dropped, regardless of whether that=
    happens at device close or after the final in-flight context completes.</t=

    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53161" target=3D= "_blank" rel=3D"noopener">CVE-2026-53161</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mem= cg: use round-robin victim selection in refill_stock Harry Yoo reported tha=
    t get_random_u32_below() is not safe to call in the nmi context and memcg c= harge draining can happen in nmi context. More specifically get_random_u32_= below() is neither reentrant- nor NMI-safe: it acquires a per-cpu local_loc=
    k via local_lock_irqsave() on the batched_entropy_u32 state. An NMI that la= nds on a CPU mid-update of the ChaCha batch state and recurses into the ran= dom subsystem would corrupt that state. The memcg_stock local_trylock preve= nts re-entry on the percpu stock itself, but cannot protect an unrelated su= bsystem's per-cpu lock. Replace the random pick with a per-cpu round-robin = counter stored in memcg_stock_pcp and serialized by the same local_trylock = that already guards cached[] and nr_pages[]. No atomics, no random calls, n=
    o extra locks needed.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53162" target=3D= "_blank" rel=3D"noopener">CVE-2026-53162</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= ap: avoid potential null folio-&gt;mapping deref during error reporting Whe=
    n a buffered read fails, iomap_finish_folio_read() reports the error with f= serror_report_io(folio-&gt;mapping-&gt;host, ...). This is called after ifs= -&gt;read_bytes_pending has been decremented by the bytes attempted to be r= ead. For a folio split across multiple read completions, the folio is only = guaranteed to stay locked while read_bytes_pending &gt; 0. Once iomap_finis= h_folio_read() decrements read_bytes_pending, another in-flight read can co= mplete and end the read on the folio, which unlocks it. This allows truncat=
    e logic to run and detach the folio (set folio-&gt;mapping to NULL). The er= ror reporting path then can dereference a NULL folio-&gt;mapping. As report=
    ed by Sam Sun, this is the race that can occur: CPU0: failed completion CPU=
    1: final completion CPU2: truncate ----------------------- ----------------= ------ -------------- read_bytes_pending -=3D len finished =3D false /* pre= empted before fserror_report_io() */ read_bytes_pending -=3D len finished =
    =3D true folio_end_read() truncate clears folio-&gt;mapping fserror_report_= io( folio-&gt;mapping-&gt;host, ...) ^ NULL deref Fix this by reporting the=
    error first before decrementing ifs-&gt;read_bytes_pending.</td> <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53165" target=3D= "_blank" rel=3D"noopener">CVE-2026-53165</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: acc= el/ethosu: fix IFM region index out-of-bounds in command stream parser NPU_= SET_IFM_REGION extracts the region index with param &amp; 0x7f, giving a ma= ximum value of 127. However region_size[] and output_region[] in struct eth= osu_validated_cmdstream_info are both sized to NPU_BASEP_REGION_MAX (8), gi= ving valid indices [0..7]. Every other region assignment in the same switch=
    uses param &amp; 0x7: NPU_SET_OFM_REGION: st.ofm.region =3D param &amp; 0x=
    7; NPU_SET_IFM2_REGION: st.ifm2.region =3D param &amp; 0x7; NPU_SET_WEIGHT_= REGION: st.weight[0].region =3D param &amp; 0x7; NPU_SET_SCALE_REGION: st.s= cale[0].region =3D param &amp; 0x7; The 0x7f mask on IFM is inconsistent an=
    d appears to be a typo. feat_matrix_length() and calc_sizes() use the regio=
    n index directly as an array subscript into the kzalloc'd info struct: info= -&gt;region_size[fm-&gt;region] =3D max(...); A userspace caller supplying = NPU_SET_IFM_REGION with param &gt; 7 causes a write up to 127*8 =3D 1016 by= tes past the start of region_size[], corrupting adjacent kernel heap data. = Fix by applying the same &amp; 0x7 mask used by all other region assignment= s.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53172" target=3D= "_blank" rel=3D"noopener">CVE-2026-53172</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: acc= el/ethosu: fix OOB write in ethosu_gem_cmdstream_copy_and_validate() The co= mmand stream parsing loop increments the index variable a second time when =
    a 64-bit command word is encountered (bit 14 set), but does not re-check th=
    e loop bound before writing the second word: for (i =3D 0; i &lt; size / 4;=
    i++) { bocmds[i] =3D cmds[0]; if (cmd &amp; 0x4000) { i++; bocmds[i] =3D c= mds[1]; /* unchecked */ } } The buffer bocmds is backed by a DMA allocation=
    of exactly size bytes from drm_gem_dma_create(ddev, size), giving valid in= dices [0, size/4-1]. When i =3D=3D size/4 - 1 on entry to an iteration and = bit 14 of cmds[0] is set, bocmds[size/4-1] is written in bounds, i is then = incremented to size/4, and bocmds[size/4] writes four bytes past the end of=
    the allocation. Userspace controls both the buffer contents and the size a= rgument via the ioctl, making this a userspace-triggerable heap out-of-boun=
    ds write. Fix by checking the incremented index against the buffer bound be= fore the second write and returning -EINVAL if the buffer is too small to c= ontain the extended command.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53173" target=3D= "_blank" rel=3D"noopener">CVE-2026-53173</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ovl=
    : keep err zero after successful ovl_cache_get() ovl_iterate_merged() store=
    s PTR_ERR(cache) in err before checking IS_ERR(cache). On success err holds=
    the truncated cache pointer and can be returned as a bogus non-zero error.=
    The syzbot reproducer reaches this through overlay-on-overlay readdir: get= dents64 iterate_dir(outer overlay file) ovl_iterate_merged() ovl_cache_get(=
    ) ovl_dir_read_merged() ovl_dir_read() iterate_dir(inner overlay file) ovl_= iterate_merged() Only compute PTR_ERR(cache) on the error path.</td> <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53174" target=3D= "_blank" rel=3D"noopener">CVE-2026-53174</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: tim= ers/migration: Fix livelock in tmigr_handle_remote_up() tmigr_handle_remote= _cpu() skips timer_expire_remote() when cpu =3D=3D smp_processor_id(), assu= ming the local softirq path already handled this CPU's timers. This assumpt= ion is wrong because jiffies can advance after the handling of the CPU's gl= obal timers in run_timer_base(BASE_GLOBAL) and before tmigr_handle_remote()=
    evaluates the expiry times. As a consequence a timer which expires after t=
    he CPU local timer wheel advanced and becomes expired in the remote handlin=
    g is ignored and the callback is never invoked and removed from the timer w= heel. What's worse is that fetch_next_timer_interrupt_remote() keeps report= ing it as expired, and the event is re-queued with expires =3D=3D now on ea=
    ch iteration. The goto-again loop spins indefinitely. Fix this by calling t= imer_expire_remote() unconditionally. That's minimal overhead for the commo=
    n case as __run_timer_base() returns immediately if there is nothing to exp= ire in the local wheel. [ tglx: Amend change log and add a comment ]</td> <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53180" target=3D= "_blank" rel=3D"noopener">CVE-2026-53180</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: nl80211: reject oversized EMA RNR lists nl80211_parse_rnr_elems() stores=
    the parsed element count in a u8-backed cfg80211_rnr_elems::cnt field and = uses that count to size the flexible array allocation. Reject nested NL8021= 1_ATTR_EMA_RNR_ELEMS input once the count reaches 255, before incrementing =
    it again. This keeps the parser aligned with the data structure it fills an=
    d matches the existing bound check used by nl80211_parse_mbssid_elems().</t=

    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53182" target=3D= "_blank" rel=3D"noopener">CVE-2026-53182</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mpt= cp: allow subflow rcv wnd to shrink In MPTCP connection, the `window` field=
    in the TCP header refers to the MPTCP-level rcv_nxt and it's right edge sh= ould not move backward. Such constraint is enforced at DSS option generatio=
    n time. At the same time, the TCP stack ensures independently that the TCP-= level rcv wnd right's edge does not move backward. That in turn causes arti= ficial inflating of the MPTCP rcv window when the incoming data is acked at=
    the TCP level and is OoO in the MPTCP sequence space (or lands in the back= log). As a consequence, the incoming traffic can exceed the receiver rcvbuf=
    size even when the sender is not misbehaving. Prevent such scenario forcib=
    ly allowing the TCP subflow to shrink the TCP-level rcv wnd regardless of t=
    he current netns setting.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53183" target=3D= "_blank" rel=3D"noopener">CVE-2026-53183</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: udp=
    : clear skb-&gt;dev before running a sockmap verdict On the UDP receive pat=
    h skb-&gt;dev is repurposed as dev_scratch (the truesize/state cache set by=
    udp_set_dev_scratch()), through the union { struct net_device *dev; unsign=
    ed long dev_scratch; } in sk_buff. When a UDP socket is in a sockmap, sk_da= ta_ready is sk_psock_verdict_data_ready(), which calls udp_read_skb() -&gt;=
    recv_actor() (sk_psock_verdict_recv) to run the attached SK_SKB verdict pr= ogram in softirq. If that program calls a socket-lookup helper (bpf_sk_look= up_tcp/udp, bpf_skc_lookup_tcp), bpf_skc_lookup() does: if (skb-&gt;dev) ca= ller_net =3D dev_net(skb-&gt;dev); skb-&gt;dev still holds the dev_scratch = value (a non-NULL integer), so dev_net() dereferences it as a struct net_de= vice * and the kernel takes a general protection fault on a non-canonical a= ddress in softirq: Oops: general protection fault, probably for non-canonic=
    al address 0x1010000800004a0 CPU: 1 UID: 0 PID: 1406 Comm: syz.2.19 Not tai= nted 7.1.0-rc6 #1 PREEMPT(full) RIP: 0010:bpf_skc_lookup net/core/filter.c:= 7033 [inline] RIP: 0010:bpf_sk_lookup+0x45/0x160 net/core/filter.c:7047 Cal=
    l Trace: &lt;IRQ&gt; bpf_prog_4675cb904b7071f8+0x12e/0x14e bpf_prog_run_pin= _on_cpu+0xc6/0x1f0 sk_psock_verdict_recv+0x1ba/0x350 udp_read_skb+0x31a/0x3=
    70 sk_psock_verdict_data_ready+0x2e3/0x600 __udp_enqueue_schedule_skb+0x4c8= /0x650 udpv6_queue_rcv_one_skb+0x3ec/0x740 udp6_unicast_rcv_skb+0x11d/0x140=
    ip6_protocol_deliver_rcu+0x61e/0x950 ip6_input_finish+0xa9/0x150 NF_HOOK+0= x286/0x2f0 ip6_input+0x117/0x220 NF_HOOK+0x286/0x2f0 __netif_receive_skb+0x= 85/0x200 process_backlog+0x374/0x9a0 __napi_poll+0x4f/0x1c0 net_rx_action+0= x3b0/0x770 handle_softirqs+0x15a/0x460 do_softirq+0x57/0x80 &lt;/IRQ&gt; Th=
    e rmem charge that dev_scratch accounted for is released by skb_recv_udp() =
    on dequeue, just above, so the scratch is dead by the time recv_actor() run=
    s. Clear skb-&gt;dev so bpf_skc_lookup() falls back to sock_net(skb-&gt;sk)=
    , which skb_set_owner_sk_safe() set just above.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53184" target=3D= "_blank" rel=3D"noopener">CVE-2026-53184</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: zra=
    m: fix use-after-free in zram_bvec_write_partial() zram_read_page() picks t=
    he sync or async backing device read path based on whether the parent bio i=
    s NULL. zram_bvec_write_partial() passes its parent bio down, so for ZRAM_W=
    B slots the read is dispatched asynchronously and zram_read_page() returns =
    0 while the bio is still in flight. The caller then runs memcpy_from_bvec()=
    , zram_write_page() and __free_page() on the buffer, leaving the async read=
    to write into a freed page. zram_bvec_read_partial() was switched to NULL =
    in commit 4e3c87b9421d ("zram: fix synchronous reads") for the same reason;=
    the write_partial counterpart was missed.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53185" target=3D= "_blank" rel=3D"noopener">CVE-2026-53185</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: RDM= A/core: Validate cpu_id against nr_cpu_ids in DMAH alloc The cpu_id attribu=
    te supplied by user space through UVERBS_ATTR_ALLOC_DMAH_CPU_ID is passed d= irectly to cpumask_test_cpu() without first verifying that the value is wit= hin the valid CPU range. Passing such untrusted data to cpumask_test_cpu() = may lead to an out-of-bounds read of the underlying cpumask bitmap: the hel= per expands to a test_bit() that indexes the bitmap by cpu_id / BITS_PER_LO=
    NG with no bound check. In addition, on kernels built with CONFIG_DEBUG_PER= _CPU_MAPS it trips the WARN_ON_ONCE() in cpumask_check(); combined with pan= ic_on_warn this turns a bad user input into a machine reboot. Reject any cp= u_id that is not smaller than nr_cpu_ids with -EINVAL before it is used. Re= ported by Smatch.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53187" target=3D= "_blank" rel=3D"noopener">CVE-2026-53187</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mm/= huge_memory: update file PMD counter before folio_put() __split_huge_pmd_lo= cked() updates the file/shmem RSS counter after dropping the PMD mapping's = folio reference. If folio_put() drops the last reference, mm_counter_file()=
    can later read freed folio state via folio_test_swapbacked(). Move the cou= nter update before folio_put().</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53189" target=3D= "_blank" rel=3D"noopener">CVE-2026-53189</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: io_= uring/net: inherit IORING_CQE_F_BUF_MORE across bundle recv retries When a = bundle recv retries inside io_recv_finish(), the merge logic OR the saved c= flags from the previous iteration with the cflags returned by the new itera= tion: cflags =3D req-&gt;cqe.flags | (cflags &amp; CQE_F_MASK); Bits listed=
    in CQE_F_MASK are inherited from the new iteration, and all other bits (no= tably IORING_CQE_F_BUFFER and the buffer ID) come from the saved cflags. Be= fore this change CQE_F_MASK covered only IORING_CQE_F_SOCK_NONEMPTY and IOR= ING_CQE_F_MORE. When using provided buffer rings (IOU_PBUF_RING_INC) with i= ncremental mode, and bundle recv, io_kbuf_inc_commit() can leave the head r= ing entry partially consumed, __io_put_kbufs() then sets IORING_CQE_F_BUF_M= ORE on the returned cflags so userspace knows the buffer ID will be reused = for subsequent completions. Because IORING_CQE_F_BUF_MORE was not in CQE_F_= MASK, the merge above silently dropped it whenever the final retry iteratio=
    n partially consumed the buffer, and the subsequent req-&gt;cqe.flags =3D c= flags &amp; ~CQE_F_MASK save would have left a stale IORING_CQE_F_BUF_MORE =
    in the carried-over cflags had one been present. Userspace would then wrong= fully advance it ring head past an entry the kernel still uses. Add IORING_= CQE_F_BUF_MORE to CQE_F_MASK so it is both inherited from the new iteration=
    into the user-visible CQE and stripped from the saved cflags between itera= tions.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53191" target=3D= "_blank" rel=3D"noopener">CVE-2026-53191</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ALS=
    A: timer: Fix UAF at snd_timer_user_params() At releasing a timer object, e= .g. when a userspace timer (CONFIG_SND_UTIMER) gets closed and snd_timer_fr= ee() is called, it tries to detach the timer instances and release the reso= urces. However, it's still possible that other in-flight tasks are holding = the timer instance where the to-be-deleted timer object is associated, and = this may lead to racy accesses. Fortunately, most of ioctls dealing with th=
    e timer instance list already have the protection with register_mutex, and = this also avoids such races. But, SNDRV_TIMER_IOCTL_PARAMS isn't protected,=
    hence the concurrent ioctl may lead to use-after-free. This patch just add=
    s the guard with register_mutex to protect snd_timer_user_params() for cove= ring the code path as a quick workaround. It's no hot-path but rather a rar= ely issued ioctl, so the performance penalty doesn't matter.</td> <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53192" target=3D= "_blank" rel=3D"noopener">CVE-2026-53192</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ALS=
    A: timer: Forcibly close timer instances at closing When snd_timer object i=
    s freed via snd_timer_free() and still pending snd_timer_instance objects a=
    re assigned to the timer object, it tries to unlink all instances and just = set NULL to each ti-&gt;timer, then releases the resources immediately. The=
    problem is, however, when there are slave timer instances that are associa= ted with a master instance linked to this timer: namely, those slave instan= ces still point to the freed timer object although the master instance is u= nlinked, which may lead to user-after-free. The bug can be easily triggered=
    particularly when a new userspace-driven timers (CONFIG_SND_UTIMER) is inv= olved, since it can create and delete the timer object via a simple file op= en/close, while the other applications may keep accessing to that timer. Th=
    is patch is an attempt to paper over the problem above: now instead of just=
    unlinking, call snd_timer_close[_locked]() forcibly for each pending timer=
    instance, so that all assigned slave timer instances are properly detached=
    , too. Since snd_timer_close() might be called later by the driver that cre= ated that instance, the check of SNDRV_TIMER_IFLG_DEAD is added at the begi= nning, too.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53193" target=3D= "_blank" rel=3D"noopener">CVE-2026-53193</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: USB=
    : serial: kl5kusb105: fix bulk-out buffer overflow klsi_105_prepare_write_b= uffer() is called by the generic write path with the bulk-out buffer and it=
    s size (bulk_out_size, 64 bytes). It stores a two-byte length header at the=
    start of the buffer and copies the payload from the write fifo starting at=
    buf + KLSI_HDR_LEN, but passes the full buffer size as the number of bytes=
    to copy: count =3D kfifo_out_locked(&amp;port-&gt;write_fifo, buf + KLSI_H= DR_LEN, size, &amp;port-&gt;lock); When the fifo holds at least size bytes,=
    size bytes are copied starting two bytes into the size-byte buffer, writin=
    g KLSI_HDR_LEN bytes past its end. Copy at most size - KLSI_HDR_LEN bytes i= nstead, leaving room for the header as safe_serial already does. Writing bu= lk_out_size or more bytes to the tty triggers a slab out-of-bounds write, o= bserved with KASAN by emulating the device with dummy_hcd and raw-gadget: B= UG: KASAN: slab-out-of-bounds in kfifo_copy_out+0x83/0xc0 Write of size 64 =
    at addr ffff888112c62202 by task python3 kfifo_copy_out klsi_105_prepare_wr= ite_buffer [kl5kusb105] usb_serial_generic_write_start [usbserial] Allocate=
    d by task 139: usb_serial_probe [usbserial] The buggy address is located 2 = bytes inside of allocated 64-byte region The out-of-bounds write no longer = occurs with this change applied.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53194" target=3D= "_blank" rel=3D"noopener">CVE-2026-53194</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: hv_= netvsc: use kmap_local_page in netvsc_copy_to_send_buf netvsc_copy_to_send_= buf() copies page buffer entries into the VMBus send buffer using phys_to_v= irt() on the entry PFN. Entries for the RNDIS header and the skb linear dat=
    a come from kmalloc'd memory and are always in the kernel direct map, but e= ntries for skb fragments reference page cache or user pages, which on 32-bi=
    t x86 with CONFIG_HIGHMEM=3Dy can live above the LOWMEM boundary. For such =
    a page phys_to_virt() returns an address outside the direct map and the sub= sequent memcpy() faults on the transmit softirq path, which is fatal. Map t=
    he pages with kmap_local_page() instead, handling two properties of the pag=
    e buffer entries: - pb[i].pfn is a Hyper-V PFN at HV_HYP_PAGE_SIZE (4K) gra= nularity, not a native PFN. Reconstruct the physical address first and deri=
    ve the native page from it, so the mapping stays correct where PAGE_SIZE &g=
    t; HV_HYP_PAGE_SIZE (e.g. arm64 with 64K pages). - Since commit 41a6328b2c5=
    5 ("hv_netvsc: Preserve contiguous PFN grouping in the page buffer array"),=
    an entry describes a full physically contiguous fragment and pb[i].len can=
    exceed PAGE_SIZE, while kmap_local_page() maps a single page. Copy page by=
    page, splitting at native page boundaries. The copy path only handles pack= ets smaller than the send section size (6144 bytes by default); larger pack= ets take the cp_partial path where only the RNDIS header is copied. So entr= ies here are bounded by the section size and a copy is split at most once o=
    n 4K-page systems. On !CONFIG_HIGHMEM configs kmap_local_page() folds to pa= ge_address() and no mapping work is added.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53199" target=3D= "_blank" rel=3D"noopener">CVE-2026-53199</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Rev= ert "drm/xe: Skip exec queue schedule toggle if queue is idle during suspen=
    d" This reverts commit 8533051ce92015e9cc6f75e0d52119b9d91610b6. The idle-s= kip optimization bypasses GuC suspend, so the GPU may not perform the conte=
    xt switch that flushes TLB entries for invalidated userptr VMAs. In LR/pree= mpt-fence VM mode, this can lead to missed TLB invalidation and page faults=
    during userptr invalidation tests. Restore unconditional schedule toggling=
    on suspend so the context-switch TLB flush is always performed. This optim= ization will be reintroduced with a fix that does not skip suspend in LR/pr= eempt-fence VM mode. (cherry picked from commit 6a1e7934d9a6cf46aecae00a99c= 2603d1295e170)</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53201" target=3D= "_blank" rel=3D"noopener">CVE-2026-53201</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: acc= el/ivpu: Fix signed integer truncation in IPC receive Fix potential buffer = overflow where firmware-supplied data_size is cast to signed int before bei=
    ng used in min_t(). Large unsigned values (&gt;=3D 0x80000000) become negat= ive, causing unsigned wraparound and oversized memcpy operations that can o= verflow the stack buffer. Change min_t(int, ...) to min() as both values ar=
    e unsigned and can be handled by min() without explicit cast.</td> <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53202" target=3D= "_blank" rel=3D"noopener">CVE-2026-53202</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: acc= el/ivpu: Add buffer overflow check in MS get_info_ioctl Add validation that=
    the info size returned from the metric stream info query is not exceeded w= hen checked against the allocated buffer size. If the firmware returns a si=
    ze larger than the buffer, reject the operation with -EOVERFLOW instead of = proceeding with an incorrect buffer copy.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53203" target=3D= "_blank" rel=3D"noopener">CVE-2026-53203</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: acc= el/ivpu: Add bounds checks for firmware log indices Add validation that rea=
    d and write indices in the firmware log buffer are within valid bounds (&lt=
    ; data_size) before using them. If out-of-bounds indices are encountered (f= rom firmware), clamp them to safe values instead of proceeding with invalid=
    offsets. This prevents potential out-of-bounds buffer access when firmware=
    supplies invalid log indices.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53205" target=3D= "_blank" rel=3D"noopener">CVE-2026-53205</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: hci_sync: reject oversized Broadcast Announcement prepend Existing = advertising instances can already hold the maximum extended advertising pay= load. When hci_adv_bcast_annoucement() prepends the Broadcast Announcement = service data to that payload, the combined data may no longer fit in the te= mporary buffer used to rebuild the advertising data. Reject that case befor=
    e copying the existing payload and report the failure through the device lo=
    g. This keeps the existing advertising data intact and avoids overrunning t=
    he temporary buffer.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53209" target=3D= "_blank" rel=3D"noopener">CVE-2026-53209</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nft_tunnel: fix use-after-free on object destroy nft_tunnel_obj_des= troy() calls metadata_dst_free() which directly kfree()s the metadata_dst, = ignoring the dst_entry refcount. Packets that took a reference via dst_hold=
    () in nft_tunnel_obj_eval() and are still queued (e.g. in a netem qdisc) ar=
    e left with a dangling pointer. When these packets are eventually dequeued,=
    dst_release() operates on freed memory. Replace metadata_dst_free() with d= st_release() so the metadata_dst is freed only after all references are dro= pped. The dst subsystem already handles metadata_dst cleanup in dst_destroy=
    () when DST_METADATA is set.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53212" target=3D= "_blank" rel=3D"noopener">CVE-2026-53212</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : guard timestamp cmsgs to real error queue skbs skb_is_err_queue() treats = PACKET_OUTGOING as the sole marker for an skb from sk_error_queue. That ass= umption is not true for AF_PACKET sockets: outgoing packet taps are also de= livered to packet sockets with skb-&gt;pkt_type =3D=3D PACKET_OUTGOING, but=
    their skb-&gt;cb is owned by AF_PACKET instead of struct sock_exterr_skb. =
    If such an skb is received with timestamping enabled, the generic timestamp=
    cmsg path can read AF_PACKET control-buffer state as sock_exterr_skb::opt_= stats. With SO_RXQ_OVFL enabled, the packet drop counter overlaps opt_stats=
    . An odd drop count makes the path emit SCM_TIMESTAMPING_OPT_STATS with skb= -&gt;len and skb-&gt;data. For non-linear skbs this copies past the linear = head and can trigger hardened usercopy or disclose adjacent heap contents. = Keep skb_is_err_queue() local to net/socket.c, but make it verify that the = PACKET_OUTGOING marker is paired with the sock_rmem_free destructor install=
    ed by sock_queue_err_skb(). AF_PACKET receive skbs use normal receive owner= ship and no longer pass as error-queue skbs, while legitimate sk_error_queu=
    e entries keep the PACKET_OUTGOING marker and sock_rmem_free ownership.</td=

    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53223" target=3D= "_blank" rel=3D"noopener">CVE-2026-53223</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure In the XSK b= ranch of mlx5e_xmit_xdp_buff(), when sq-&gt;xmit_xdp_frame() returns false = (e.g. XDPSQ is full), the function returns without unmapping the DMA addres=
    s or freeing the xdp_frame allocated by xdp_convert_zc_to_xdp_frame(). The = xdpi_fifo push only happens on success, so the completion path cannot recov=
    er these entries. With CONFIG_DMA_API_DEBUG=3Dy, the leak surfaces on drive=
    r unbind: DMA-API: pci 0000:08:00.0: device driver has pending DMA allocati= ons while released from device [count=3D1116] One of leaked entries details=
    : [device address=3D0x000000010ffd7028] [size=3D1534 bytes] [mapped with DM= A_TO_DEVICE] [mapped as phy] WARNING: kernel/dma/debug.c:881 at dma_debug_d= evice_change+0x127/0x180 ... DMA-API: Mapped at: debug_dma_map_phys+0x4b/0x=
    d0 dma_map_phys+0xfd/0x2d0 mlx5e_xdp_handle+0x5ae/0xac0 [mlx5_core] mlx5e_x= sk_skb_from_cqe_mpwrq_linear+0xc4/0x170 [mlx5_core] mlx5e_handle_rx_cqe_mpw= rq+0xc1/0x290 [mlx5_core] Add the missing unmap + xdp_return_frame, matchin=
    g the cleanup already done in mlx5e_xdp_xmit(). has_frags is rejected earli=
    er in this branch, so no per-frag unmap is needed.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53229" target=3D= "_blank" rel=3D"noopener">CVE-2026-53229</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : add pskb_may_pull() to skb_gro_receive_list() skb_gro_receive_list() call=
    s skb_pull(skb, skb_gro_offset(skb)) without first ensuring the data is in = the linear area via pskb_may_pull(). When the skb arrives via napi_gro_frag= s(), skb_headlen can be 0 (all data in page fragments) while skb_gro_offset=
    is non-zero (after IP+TCP header parsing). The skb_pull() then decrements = skb-&gt;len by skb_gro_offset but skb-&gt;data_len stays unchanged, hitting=
    BUG_ON(skb-&gt;len &lt; skb-&gt;data_len) in __skb_pull(). The UDP fraglis=
    t GRO path already contains this guard at udp_offload.c:749. Adding it to s= kb_gro_receive_list() itself provides centralized protection for all caller=
    s (TCP, UDP, and any future protocols), and ensures the precondition of skb= _pull() is satisfied before it is called. On pskb_may_pull() failure, set N= API_GRO_CB(skb)-&gt;flush =3D 1 so the skb is not held as a new GRO head an=
    d is instead delivered through the normal receive path, matching the UDP ha= ndling.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53235" target=3D= "_blank" rel=3D"noopener">CVE-2026-53235</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: xfr=
    m: policy: fix use-after-free on inexact bin in xfrm_policy_bysel_ctx() Fix=
    the race by pruning the bin while still holding xfrm_policy_lock, before d= ropping it. Use __xfrm_policy_inexact_prune_bin() directly since the lock i=
    s already held. The wrapper xfrm_policy_inexact_prune_bin() becomes unused = and is removed. Race: CPU0 (XFRM_MSG_DELPOLICY) CPU1 (XFRM_MSG_NEWSPDINFO) = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D xfrm_policy_bysel_ctx(): spin_lock_bh(xfrm_policy_lock) bin =3D x= frm_policy_inexact_lookup() __xfrm_policy_unlink(pol) spin_unlock_bh(xfrm_p= olicy_lock) xfrm_policy_kill(ret) // wide window, lock not held xfrm_hash_r= ebuild(): spin_lock_bh(xfrm_policy_lock) __xfrm_policy_inexact_flush(): kfr= ee_rcu(bin) // bin freed spin_unlock_bh(xfrm_policy_lock) xfrm_policy_inexa= ct_prune_bin(bin) // UAF: bin is freed</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53239" target=3D= "_blank" rel=3D"noopener">CVE-2026-53239</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ALS=
    A: PCM: Fix wait queue list corruption in snd_pcm_drain() on linked streams=
    snd_pcm_drain() uses init_waitqueue_entry which does not clear entry.prev/= next, and add_wait_queue with a conditional remove_wait_queue that is skipp=
    ed when to_check is no longer in the group after concurrent UNLINK. The orp= haned wait entry remains on the unlinked substream sleep queue. On the next=
    drain iteration, add_wait_queue adds the entry to a new queue while still = linked on the old one, corrupting both lists. A subsequent wake_up derefere= nces NULL at the func pointer (mapped from the spinlock at offset 0 of the = misinterpreted wait_queue_head_t), causing a kernel panic. Replace init_wai= tqueue_entry/add_wait_queue/conditional remove_wait_queue with init_wait_en= try/prepare_to_wait/ finish_wait. init_wait_entry clears prev/next via INIT= _LIST_HEAD on each iteration and sets autoremove_wake_function which auto-r= emoves the entry on wake-up. finish_wait safely handles both the already-re= moved and still-queued cases.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53242" target=3D= "_blank" rel=3D"noopener">CVE-2026-53242</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: VFS=
    : fix possible failure to unlock in nfsd4_create_file() atomic_create() in = fs/namei.c drops the reference to the dentry when it returns an error. This=
    behaviour was imported into dentry_create() so that it will drop the refer= ence if an error is returned from atomic_create(), though not if vfs_create=
    () returns an error (in the case where -&gt;atomic_create is not supported)=
    . The caller - nfsd4_create_file() - is made aware of this by checking path= -&gt;dentry, which will either be a counted reference to a dentry, or an er= ror pointer. However the change to use start_creating()/end_creating() (whi=
    ch landed shortly before the dentry_create() change landed, though was like=
    ly developed around the same time) means that nfsd4_create_file() *needs* a=
    valid dentry so that it can unlock the parent. The net result is that if N= FSD exports a filesystem which uses -&gt;atomic_create, and if a call to -&= gt;atomic_create returns an error, then nfsd4_create_file() will pass an er= ror pointer to end_creating() and the parent will not be unlocked. Fix this=
    by changing dentry_create() to make sure path-&gt;dentry is always a valid=
    dentry, never an error-pointer. The actual error is already returned a dif= ferent way. Note that if -&gt;atomic_create() returns a different dentry (w= hich may not be possible in practice) we are guaranteed (because it is only=
    ever provided by d_spliace_alias()) that it will have the same d_parent an=
    d so it will have the same effect when passed to end_creating().</td> <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53244" target=3D= "_blank" rel=3D"noopener">CVE-2026-53244</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: xsk=
    : cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() The TX m= etadata area resides in the UMEM buffer which is memory-mapped and concurre= ntly writable by userspace. In xsk_skb_metadata(), csum_start and csum_offs=
    et are read from shared memory for bounds validation, then read again for s=
    kb assignment. A malicious userspace application can race to overwrite thes=
    e values between the two reads, bypassing the bounds check and causing out-= of-bounds memory access during checksum computation in the transmit path. F=
    ix this by reading csum_start and csum_offset into local variables once, th=
    en using the local copies for both validation and assignment. Note that oth=
    er metadata fields (flags, launch_time) and the cached csum fields may be m= utually inconsistent due to concurrent userspace writes, but this is benign=
    : the only security-critical invariant is that each field's validated value=
    is the same one used, which local caching guarantees.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53250" target=3D= "_blank" rel=3D"noopener">CVE-2026-53250</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: bnep: reject short frames before parsing A BNEP peer can send a sho=
    rt BNEP SDU. bnep_rx_frame() reads the packet type byte immediately and, fo=
    r control packets, reads the control opcode and setup UUID-size byte before=
    proving that those bytes are present. bnep_rx_control() also dereferences = the control opcode without rejecting an empty control payload. Use skb_pull= _data() for the fixed fields in bnep_rx_frame() so a NULL return gates each=
    dereference. Split the control handler so the frame path can pass an opcod=
    e that has already been pulled, and keep the byte-buffer wrapper for extens= ion control payloads. For BNEP_SETUP_CONN_REQ, name the UUID-size byte befo=
    re pulling the setup payload. struct bnep_setup_conn_req carries destinatio=
    n and source service UUIDs after that byte, each uuid_size bytes, so the pa= rser now documents that tuple explicitly instead of leaving the pull length=
    as an opaque multiplication. Validation reproduced this kernel report: KAS=
    AN slab-out-of-bounds in bnep_rx_frame.isra.0+0x130c/0x1790 The buggy addre=
    ss belongs to the object at ffff88800c0f7908 which belongs to the cache kma= lloc-8 of size 8 The buggy address is located 0 bytes to the right of alloc= ated 1-byte region [ffff88800c0f7908, ffff88800c0f7909) Read of size 1 Call=
    trace: dump_stack_lvl+0xb3/0x140 (?:?) print_address_description+0x57/0x3a=
    0 (?:?) bnep_rx_frame+0x130c/0x1790 (net/bluetooth/bnep/core.c:306) print_r= eport+0xb9/0x2b0 (?:?) __virt_addr_valid+0x1ba/0x3a0 (?:?) srso_alias_retur= n_thunk+0x5/0xfbef5 (?:?) kasan_addr_to_slab+0x21/0x60 (?:?) kasan_report+0= xe0/0x110 (?:?) process_one_work+0xfce/0x17e0 (kernel/workqueue.c:3200) wor= ker_thread+0x65c/0xe40 (?:?) __kthread_parkme+0x184/0x230 (?:?) kthread+0x3= 5e/0x470 (?:?) _raw_spin_unlock_irq+0x28/0x50 (?:?) ret_from_fork+0x586/0x8=
    70 (?:?) __switch_to+0x74f/0xdc0 (?:?) ret_from_fork_asm+0x1a/0x30 (?:?)</t=

    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53253" target=3D= "_blank" rel=3D"noopener">CVE-2026-53253</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ipv=
    6: anycast: insert aca into global hash under idev-&gt;lock syzbot reported=
    a splat [1]: a slab-use-after-free in ipv6_chk_acast_addr(), which walks t=
    he global inet6_acaddr_lst[] hash under RCU and dereferences a struct ifaca= ddr6 that has already been freed while still linked in the hash, so a later=
    reader walks into a dangling node. In __ipv6_dev_ac_inc() the aca is alloc= ated with refcount 1, then aca_get() bumps it to 2 to keep it alive across = the unlocked region. It is published to idev-&gt;ac_list under idev-&gt;loc=
    k, but ipv6_add_acaddr_hash() runs after write_unlock_bh(). A concurrent te= ardown (ipv6_ac_destroy_dev() from addrconf_ifdown(), under RTNL) can slip = into that window: CPU0 __ipv6_dev_ac_inc CPU1 ipv6_ac_destroy_dev (RTNL) --= ---------------------------- ------------------------------------ aca_alloc=
    () refcnt 1 aca_get() refcnt 2 write_lock_bh(idev-&gt;lock) add aca to ac_l= ist write_unlock_bh(idev-&gt;lock) write_lock_bh(idev-&gt;lock) pull aca of=
    f ac_list write_unlock_bh(idev-&gt;lock) ipv6_del_acaddr_hash(aca) hlist_de= l_init_rcu() is a no-op, aca is not in the hash yet aca_put() refcnt 2-&gt;=
    1 ipv6_add_acaddr_hash(aca) aca now inserted into the hash aca_put() refcnt=
    1-&gt;0 call_rcu(aca_free_rcu) -&gt; kfree(aca) The hash removal becomes a=
    no-op because the insertion has not happened yet, so once CPU0 inserts and=
    drops the last reference, the aca is freed while still linked in inet6_aca= ddr_lst[], and readers dereference freed memory after the slab slot is reus= ed. This window opened once RTNL stopped serializing the join path against = device teardown. Move ipv6_add_acaddr_hash() inside the idev-&gt;lock secti=
    on so the ac_list and hash insertions are atomic with respect to teardown: =
    a racing remover now either misses the aca entirely or finds it in both lis= ts. acaddr_hash_lock is now nested under idev-&gt;lock, which is acquired i=
    n softirq context, so switch all acaddr_hash_lock sites to spin_lock_bh() t=
    o avoid the irq lock inversion reported in [2]. [1] https://syzkaller.appsp= ot.com/bug?extid=3Da01df04303c131efbf3a [2] https://lore.kernel.org/netdev/= 6a194ef7.ba3b1513.1890b4.0000.GAE@google.com/</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53259" target=3D= "_blank" rel=3D"noopener">CVE-2026-53259</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: l2t=
    p: pppol2tp: hold reference to session in pppol2tp_ioctl() pppol2tp_ioctl()=
    read sock-&gt;sk-&gt;sk_user_data directly without any locks or reference = counting. If a controllable sleep was induced during copy_from_user() (e.g.=
    via a userfaultfd page fault sleep), a concurrent socket close could trigg=
    er pppol2tp_session_close() asynchronously. This frees the l2tp_session str= ucture via the l2tp_session_del_work workqueue. Upon resuming, the ioctl th= read dereferences the stale session pointer, resulting in a Use-After-Free = (UAF). Fix this by securely fetching the session reference using the RCU-sa= fe, refcounted helper pppol2tp_sock_to_session(sk) on entry. This locks the=
    session's refcount across the sleep. We structured the function to exit vi=
    a standard err breaks, guaranteeing that l2tp_session_put() is cleanly call=
    ed on all return paths to drop the reference. To preserve existing behavior=
    we validate the session and its magic signature only for the specific L2TP=
    commands that require it. This ensures that generic/unknown ioctls called =
    on an unconnected socket still return -ENOIOCTLCMD and correctly fall back =
    to generic handlers (e.g. in sock_do_ioctl()).</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53262" target=3D= "_blank" rel=3D"noopener">CVE-2026-53262</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /sched: act_api: use RCU with deferred freeing for action lifecycle When NE= WTFILTER and DELFILTER are run concurrently it is possible to create a race=
    with an associated action. Let's illustrate with CPU0 running NEWTFILTER a=
    nd CPU1 running DELFILTER: 0: mutex_lock() &lt;-- holds the idr lock 0: rcu= _read_lock() 0: p =3D idr_find(idr, index) &lt;-- action p is valid (RCU pr= otects IDR) 0: mutex_unlock() &lt;-- releases the idr lock 1: refcount_dec_= and_mutex_lock() &lt;-- refcnt 1-&gt;0, mutex held 1: idr_remove(idr, index=
    ) &lt;-- Action removed from IDR 1: mutex_unlock() &lt;-- mutex released al= lowing us to delete the action 1: tcf_action_cleanup(p); kfree(p) &lt;-- Kf= rees p immediately, no deferral 0: refcount_inc_not_zero(&amp;p-&gt;tcfa_re= fcnt) &lt;-- ouch, UAF p points to freed memory This patch fixes the race c= ondition between NEWTFILTER and DELFILTER by adding struct rcu_head to tc_a= ction used in the deferral and introducing a call_rcu() in the delete path =
    to defer the final kfree(). Note: this is a revert of commit d7fb60b9cafb (= "net_sched: get rid of tcfa_rcu") but also modernization/simplification to = directly use kfree_rcu(). Let's illustrate the new restored code path: 0: r= cu_read_lock() 1: refcount_dec_and_mutex_lock() &lt;-- refcnt 1-&gt;0, mute=
    x held 1: idr_remove(idr, index) 1: mutex_unlock() 1: call_rcu(&amp;p-&gt;t= cfa_rcu, tcf_action_rcu_free) &lt;-- defer kfree after grace period 0: p =
    =3D idr_find(idr, index) 0: refcount_inc_not_zero(&amp;p-&gt;tcfa_refcnt) &= lt;-- fails, refcnt already 0 1: rcu_read_unlock() &lt;-- release so freein=
    g can run after grace period After CPU1 calls idr_remove(), the object is n=
    o longer reachable through the IDR. CPU0's subsequent idr_find() will retur=
    n NULL, and even if it still held a stale pointer, the immediate kfree() is=
    now deferred until after the RCU grace period, so no UAF can occur.</td> <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53264" target=3D= "_blank" rel=3D"noopener">CVE-2026-53264</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: dm = cache policy smq: check allocation under invalidate lock commit 2d1f7b65f5d=
    e ("dm cache policy smq: fix missing locks in invalidating cache blocks") a= dded mq-&gt;lock around the destructive part of smq_invalidate_mapping(), b=
    ut left the e-&gt;allocated check outside the critical section. That leaves=
    a check-then-act race. Two concurrent invalidators can both observe e-&gt;= allocated as true before either of them takes mq-&gt;lock. The first invali= dator that acquires the lock removes the entry from the queues and hash tab=
    le and then calls free_entry(), which clears e-&gt;allocated and puts the e= ntry back on the free list. The second invalidator can then acquire mq-&gt;= lock and continue with the stale result of the unlocked check. This can cor= rupt the SMQ queues or hash table by deleting an entry that is no longer on=
    those structures. It can also hit the allocation check in free_entry() whe=
    n the same entry is freed again. Move the allocation check under mq-&gt;loc=
    k so the predicate and the destructive operations are serialized by the sam=
    e lock.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53265" target=3D= "_blank" rel=3D"noopener">CVE-2026-53265</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nft_ct: bail out on template ct in get eval I noticed this issue wh= ile looking at a historic syzbot report [1]. A rule like the one below is e= nough to trigger the bug: table ip t { chain pre { type filter hook prerout= ing priority raw; ct zone set 1 ct original saddr 1.2.3.4 accept } } The fi= rst expression attaches a per-cpu template ct via nft_ct_set_zone_eval() (n= f_ct_tmpl_alloc -&gt; kzalloc, tuple is all zero, nf_ct_l3num(ct) =3D=3D 0)=
    . The next expression then calls nft_ct_get_eval() on the same skb, treats = the template as a real ct and hits the 16-byte memcpy path. With dreg at NF= T_REG32_15 this overflows past struct nft_regs on the kernel stack; with sm= aller dreg values it silently clobbers adjacent registers. Reject template =
    ct at the eval entry and in nft_ct_get_fast_eval(), mirroring the check nft= _ct_set_eval() already has. Additionally, bound the address copy in NFT_CT_= SRC / NFT_CT_DST by priv-&gt;len instead of by nf_ct_l3num(ct): nf_ct_get_t= uple() zeroes the tuple before pkt_to_tuple() fills in only the protocol-re= levant leading bytes, so the trailing bytes of tuple-&gt;{src,dst}.u3.all a=
    re well-defined zero. priv-&gt;len is validated at rule load, so the copy s= ize is now bounded by the destination register rather than by an untrusted = field on the conntrack. [1]: https://syzkaller.appspot.com/bug?id=3D389cf09= cb72926114fce90dc85a2c3231dcb647c</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53267" target=3D= "_blank" rel=3D"noopener">CVE-2026-53267</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ipv=
    s: clear the svc scheduler ptr early on edit ip_vs_edit_service() while unb= inding the old scheduler clears the svc-&gt;scheduler ptr after the schedul=
    er module initiates RCU callbacks. This can cause packets to use the old sc= heduler at the time when svc-&gt;sched_data is already freed after RCU grac=
    e period. Fix it by clearing the ptr early in ip_vs_unbind_scheduler(), bef= ore the done_service method schedules any RCU callbacks. Also, if the new s= cheduler fails to initialize when replacing the old scheduler, try to resto=
    re the old scheduler while still returning the error code.</td> <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53270" target=3D= "_blank" rel=3D"noopener">CVE-2026-53270</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: tee=
    : optee: prevent use-after-free when the client exits before the supplicant=
    Commit 70b0d6b0a199 ("tee: optee: Fix supplicant wait loop") made the clie=
    nt wait as killable so it can be interrupted during shutdown or after a sup= plicant crash. This changes the original lifetime expectations: the client = task can now terminate while the supplicant is still processing its request=
    . If the client exits first it removes the request from its queue and kfree= ()s it, while the request ID remains in supp-&gt;idr. A subsequent lookup o=
    n the supplicant path then dereferences freed memory, leading to a use-afte= r-free. Serialise access to the request with supp-&gt;mutex: * Hold supp-&g= t;mutex in optee_supp_recv() and optee_supp_send() while looking up and tou= ching the request. * Let optee_supp_thrd_req() notice that the client has t= erminated and signal optee_supp_send() accordingly. With these changes the = request cannot be freed while the supplicant still has a reference, elimina= ting the race.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53273" target=3D= "_blank" rel=3D"noopener">CVE-2026-53273</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: ISO: Fix a use-after-free of the hci_conn pointer In iso_sock_rebin= d_bc(), the bis pointer is cached, then the socket lock is dropped: bis =3D=
    iso_pi(sk)-&gt;conn-&gt;hcon; /* Release the socket before lookups since t= hat requires hci_dev_lock * which shall not be acquired while holding sock_= lock for proper * ordering. */ release_sock(sk); hci_dev_lock(bis-&gt;hdev)=
    ; During the unlocked window, could a concurrent close() destroy the connec= tion and free the bis structure, causing hci_dev_lock(bis-&gt;hdev) to acce=
    ss memory after it is freed, fix this by using the hdev reference which was=
    safely acquired via iso_conn_get_hdev().</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53276" target=3D= "_blank" rel=3D"noopener">CVE-2026-53276</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: btr= fs: only release the dirty pages io tree after successful writes [WARNING] = With extra warning on dirty extent buffers at umount (aka, the next patch i=
    n the series), test case generic/388 can trigger the following warning abou=
    t dirty extent buffers at unmount time: BTRFS critical (device dm-2 state E=
    ): emergency shutdown BTRFS error (device dm-2 state E): error while writin=
    g out transaction: -30 BTRFS warning (device dm-2 state E): Skipping commit=
    of aborted transaction. BTRFS error (device dm-2 state EA): Transaction 9 = aborted (error -30) BTRFS: error (device dm-2 state EA) in cleanup_transact= ion:2068: errno=3D-30 Readonly filesystem BTRFS info (device dm-2 state EA)=
    : forced readonly BTRFS info (device dm-2 state EA): last unmount of filesy= stem 4fbf2e15-f941-49a0-bc7c-716315d2777c ------------[ cut here ]---------= --- WARNING: disk-io.c:3311 at invalidate_and_check_btree_folios+0xfd/0x1ca=
    [btrfs], CPU#8: umount/914368 CPU: 8 UID: 0 PID: 914368 Comm: umount Taint= ed: G OE 7.1.0-rc1-custom+ #372 PREEMPT(full) 2de38db8d1deae71fde295430a0ff= 3ab98ccf596 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknow=
    n 02/02/2022 RIP: 0010:invalidate_and_check_btree_folios+0xfd/0x1ca [btrfs]=
    Call Trace: &lt;TASK&gt; close_ctree+0x52e/0x574 [btrfs d2f0b1cd330d1287e7= a9919d112eadfc0e914efd] generic_shutdown_super+0x89/0x1a0 kill_anon_super+0= x16/0x40 btrfs_kill_super+0x16/0x20 [btrfs d2f0b1cd330d1287e7a9919d112eadfc= 0e914efd] deactivate_locked_super+0x2d/0xb0 cleanup_mnt+0xdc/0x140 task_wor= k_run+0x5a/0xa0 exit_to_user_mode_loop+0x123/0x4b0 do_syscall_64+0x243/0x7c=
    0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 &lt;/TASK&gt; ---[ end trace 000= 0000000000000 ]--- BTRFS warning (device dm-2 state EA): unable to release = extent buffer 30539776 owner 9 gen 9 refs 2 flags 0x7 BTRFS warning (device=
    dm-2 state EA): unable to release extent buffer 30621696 owner 257 gen 9 r= efs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release ext= ent buffer 30638080 owner 258 gen 9 refs 2 flags 0x7 BTRFS warning (device = dm-2 state EA): unable to release extent buffer 30654464 owner 7 gen 9 refs=
    2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent=
    buffer 30703616 owner 2 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 = state EA): unable to release extent buffer 30720000 owner 10 gen 9 refs 2 f= lags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buf= fer 30736384 owner 4 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 stat=
    e EA): unable to release extent buffer 30752768 owner 11 gen 9 refs 2 flags=
    0x7 I'm using a stripped down version, which seems to trigger the warning = more reliably: _fsstress_pid=3D"" workload() { dmesg -C mkfs.btrfs -f -K $d=
    ev &gt; /dev/null echo 1 &gt; /sys/kernel/debug/clear_warn_once mount $dev = $mnt $fsstress -w -n 1024 -p 4 -d $mnt &amp; _fsstress_pid=3D$! sleep 0 $go= down $mnt pkill --echo -PIPE fsstress &gt; /dev/null wait $_fsstress_pid un= set _fsstress_pid umount $mnt if dmesg | grep -q "WARNING"; then fail fi } = for (( i =3D 0; i &lt; $runtime; i++ )); do echo "=3D=3D=3D $i/$runtime =3D= =3D=3D" workload done [CAUSE] Inside btrfs_write_and_wait_transaction(), we=
    first try to write all dirty ebs, then wait for them to finish. After that=
    we call btrfs_extent_io_tree_release() to free all extent states from dirt= y_pages io tree. However if we hit an error from btrfs_write_marked_extent(=
    ), then we still call btrfs_extent_io_tree_release() to clear that dirty_pa= ges io tree, which may contain dirty records that we haven't yet submitted.=
    Furthermore, the later transaction cleanup path will utilize that dirty_pa= ges io tree to properly cleanup those dirty ebs, but since it's already emp= ty, no dirty ebs are properly cleaned up, thus will later trigger the warni= ngs inside invalidate_btree_folios(). ---truncated---</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53284" target=3D= "_blank" rel=3D"noopener">CVE-2026-53284</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /xe/eustall: Fix drm_dev_put called before stream disable in close In xe_eu= _stall_stream_close(), drm_dev_put() is called before the stream is disable=
    d and its resources are freed. If this drops the last reference, the device=
    structures could be freed while the subsequent cleanup code still accesses=
    them, leading to a use-after-free. Fix this by moving drm_dev_put() after = all device accesses are complete. This matches the ordering in xe_oa_releas= e(). (cherry picked from commit 35aff528f7297e949e5e19c9cd7fd748cf1cf21c)</=

    <td>2026-06-26</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53290" target=3D= "_blank" rel=3D"noopener">CVE-2026-53290</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : enetc: fix NTMP DMA use-after-free issue The AI-generated review reported=
    a potential DMA use-after-free issue [1]. If netc_xmit_ntmp_cmd() times ou=
    t and returns an error, the pending command is not explicitly aborted, whil=
    e ntmp_free_data_mem() unconditionally frees the DMA buffer. If the buffer = has already been reallocated elsewhere, this may lead to silent memory corr= uption. Because the hardware eventually processes the pending command and p= erform a DMA write of the response to the physical address of the freed buf= fer. To resolve this issue, this patch does the following modifications: 1.=
    Convert cbdr-&gt;ring_lock from a spinlock to a mutex The lock was origina= lly a spinlock in case NTMP operations might be invoked from atomic context=
    . After downstream support for all NTMP tables, no such usage has materiali= zed. A mutex lock is now required because the driver now needs to reclaim u= sed BDs and release associated DMA memory within the lock's context, while = dma_free_coherent() might sleep. 2. Introduce software command BD (struct n= etc_swcbd) The hardware write-back overwrites the addr and len fields of th=
    e BD, so the driver cannot rely on the hardware BD to free the associated D=
    MA memory. The driver now maintains a software shadow BD storing the DMA bu= ffer pointer, DMA address, and size. And netc_xmit_ntmp_cmd() only reclaims=
    older BDs when the number of used BDs reaches NETC_CBDR_CLEAN_WORK (16). T=
    he software BD enables correct DMA memory release. With this, struct ntmp_d= ma_buf and ntmp_free_data_mem() are no longer needed and are removed. 3. Re= quire callers to hold ring_lock across netc_xmit_ntmp_cmd() netc_xmit_ntmp_= cmd() releases the ring_lock before the caller finishes consuming the respo= nse. At this point, if a concurrent thread submits a new command, it may tr= igger ntmp_clean_cbdr() and free the DMA buffer while it is still in use. M= ove ring_lock ownership to the caller to ensure the response buffer cannot =
    be reclaimed prematurely. So the helpers ntmp_select_and_lock_cbdr() and nt= mp_unlock_cbdr() are added. These changes eliminate the DMA use-after-free = condition and ensure safe and consistent BD reclamation and DMA buffer life= cycle management.</td>
    <td>2026-06-26</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53300" target=3D= "_blank" rel=3D"noopener">CVE-2026-53300</a></td>
    </tr>

    <td class=3D"vendor-product">ljharb--shell-quote</td>
    <td>shell-quote prior to 1.8.5 finalizes parsed tokens in parse() using Arr= ay.prototype.concat as a reduce accumulator, which reallocates and copies t=
    he entire growing array on every iteration. As a result parse() runs in O(n= ^2) time relative to the number of input tokens. An attacker who can supply=
    an attacker-controlled string to any code path that calls parse() (no shel=
    l metacharacters are required; plain space-separated words suffice) can blo=
    ck the single-threaded Node.js event loop for an extended period with a sma=
    ll input, resulting in a denial of service. There is no code execution or d= ata disclosure; impact is to availability only. Fixed in 1.8.5.</td> <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13311" target=3D= "_blank" rel=3D"noopener">CVE-2026-13311</a></td>
    </tr>

    <td class=3D"vendor-product">lobehub--lobehub</td>
    <td>LobeHub is a work-and-lifestyle space to find, build, and collaborate w= ith agent teammates that grow with you. Prior to 2.1.57, the /webapi/proxy = endpoint on app.lobehub.com accepts a URL in the POST body and fetches it s= erver-side without any authentication. An attacker can use this to make arb= itrary outbound requests from LobeHub's infrastructure, leak Vercel deploym= ent details, and inject cookies on the lobehub.com domain through reflected=
    Set-Cookie headers. This vulnerability is fixed in 2.1.57.</td> <td>2026-06-23</td>
    <td>9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54157" target=3D= "_blank" rel=3D"noopener">CVE-2026-54157</a></td>
    </tr>

    <td class=3D"vendor-product">lostisland--faraday</td>
    <td>Faraday is an HTTP client library abstraction layer that provides a com= mon interface over many adapters. From 1.0.0 until 1.10.6 and 2.14.3, Farad= ay::NestedParamsEncoder, the default nested query parameter encoder/decoder=
    in Faraday, decodes nested query strings without enforcing a maximum nesti=
    ng depth. A crafted query string causes Faraday to build a deeply nested Ru=
    by Hash structure. The internal dehash routine then recursively walks this = attacker-controlled structure without a depth limit. At sufficient depth, R= uby raises an uncaught SystemStackError (stack level too deep), crashing th=
    e calling thread or worker. This can lead to denial of service in applicati= ons that pass attacker-controlled query strings to Faraday's nested query p= arsing or URL-building paths. This vulnerability is fixed in 1.10.6 and 2.1= 4.3.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54297" target=3D= "_blank" rel=3D"noopener">CVE-2026-54297</a></td>
    </tr>

    <td class=3D"vendor-product">MainWP--MainWP Child</td>
    <td>Unauthenticated Broken Access Control in MainWP Child &lt;=3D 6.1.1 ver= sions.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-27366" target=3D= "_blank" rel=3D"noopener">CVE-2026-27366</a></td>
    </tr>

    <td class=3D"vendor-product">MarketingFire--Widget Options</td>
    <td>Contributor Remote Code Execution (RCE) in Widget Options &lt;=3D 4.2.3=
    versions.</td>
    <td>2026-06-25</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54823" target=3D= "_blank" rel=3D"noopener">CVE-2026-54823</a></td>
    </tr>

    <td class=3D"vendor-product">MarlinFirmware--Marlin</td>
    <td>Marlin Firmware through 2.1.2.7, fixed in commit 1f255d1, when built wi=
    th MESH_BED_LEVELING enabled, contains an out-of-bounds write vulnerability=
    in the M421 G-code handler that allows attackers to corrupt firmware memor=
    y by supplying out-of-range X and Y grid indices. Attackers can send a sing=
    le crafted G-code command via USB serial, network interface, or malicious g= code file to write an attacker-controlled 32-bit float value past the z_val= ues array bounds, corrupting adjacent firmware variables and causing denial=
    of service or firmware state corruption.</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56111" target=3D= "_blank" rel=3D"noopener">CVE-2026-56111</a></td>
    </tr>

    <td class=3D"vendor-product">mastodon--mastodon</td>
    <td>Mastodon is a free, open-source social network server based on Activity= Pub. Prior to 4.5.10, 4.4.17, and 4.3.23, when using Ruby versions older th=
    an 3.4, PrivateAddressCheck.private_address? returns false for IPv4-mapped = IPv6 addresses (::ffff:a.b.c.d) corresponding to some private IPv4 addresse=
    s, depending on Ruby version, this can include loopback, RFC1918 private ne= tworks, and link-local space. An attacker who controls DNS for any domain c=
    an publish an AAAA record with such a mapped address; any outbound HTTP fet=
    ch Mastodon performs against that hostname then opens a real TCP connection=
    to the underlying IPv4 address, including 127.0.0.1 and cloud-metadata end= points such as 169.254.169.254. This vulnerability is fixed in 4.5.10, 4.4.= 17, and 4.3.23.</td>
    <td>2026-06-24</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47389" target=3D= "_blank" rel=3D"noopener">CVE-2026-47389</a></td>
    </tr>

    <td class=3D"vendor-product">mastodon--mastodon</td>
    <td>Mastodon is a free, open-source social network server based on Activity= Pub. Prior to 4.5.11, 4.4.18, and 4.3.24, a DoS can be triggered by (Uncaug=
    ht Exception vulerability), due to missing exception handling in the math s= anitizer. Malformed &lt;math&gt; nodes can result in a DoS of a whole serve=
    r or targeted users services, depending on the type of action that includes=
    the malformed nodes and the services interacting with it. This vulnerabili=
    ty is fixed in 4.5.11, 4.4.18, and 4.3.24.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50129" target=3D= "_blank" rel=3D"noopener">CVE-2026-50129</a></td>
    </tr>

    <td class=3D"vendor-product">max-mapper--extract-zip</td>
    <td>extract-zip does not validate symlink targets when extracting zip archi= ves. When processing a malicious zip file containing a symlink with a relat= ive path like '../../../../etc/passwd', extract-zip will extract the symlin=
    k without validation, allowing it to point outside the extraction directory=
    . Depending on how extract-zip is used, an attacker could read or write to = arbitrary files.</td>
    <td>2026-06-26</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56876" target=3D= "_blank" rel=3D"noopener">CVE-2026-56876</a></td>
    </tr>

    <td class=3D"vendor-product">MB connect line--mbCONNECT24</td>
    <td>An high privileged remote attacker can access a hidden configuration me= thod, that should not be accessible by any user, to modify critical program=
    parameters. This can result in a total loss of confidentiality, integrity = and availability.</td>
    <td>2026-06-23</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10521" target=3D= "_blank" rel=3D"noopener">CVE-2026-10521</a></td>
    </tr>

    <td class=3D"vendor-product">Melapress--WP Activity Log</td>
    <td>Subscriber Cross Site Scripting (XSS) in WP Activity Log &lt;=3D 5.6.3.=
    1 versions.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56005" target=3D= "_blank" rel=3D"noopener">CVE-2026-56005</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, A vulnerability exists in the optional LZ4 decompression path u= sed by MessagePack compression modes Lz4Block and Lz4BlockArray. The decode=
    r implementation is based on a deprecated fast-decompression algorithm that=
    does not take a source-length bound. A remote attacker can send a crafted = MessagePack payload with manipulated LZ4 token/length fields to force out-o= f-bounds reads from the compressed input buffer. In affected environments, = this can trigger an AccessViolationException during decompression, causing = process termination (denial of service). Under some conditions, limited uni= ntended memory disclosure from over-read data may also be possible before f= ailure. This vulnerability is fixed in 2.5.301 and 3.1.7.</td> <td>2026-06-22</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48109" target=3D= "_blank" rel=3D"noopener">CVE-2026-48109</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, MessagePackReader.TrySkip() recursively descends into nested ar= rays and maps without incrementing the reader depth or calling the configur=
    ed depth checks. This bypasses MessagePackSecurity.MaximumObjectGraphDepth,=
    the library's documented protection against deeply nested object graphs. M= any generated and dynamic formatters call reader.Skip() when they encounter=
    unknown map keys, unknown array members, ignored fields, or data that shou=
    ld be skipped for forward compatibility. A deeply nested value in one of th= ese skipped positions can therefore cause unbounded recursion and an uncatc= hable StackOverflowException. This vulnerability is fixed in 2.5.301 and 3.= 1.7.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48506" target=3D= "_blank" rel=3D"noopener">CVE-2026-48506</a></td>
    </tr>

    <td class=3D"vendor-product">MHSanaei--3x-ui</td>
    <td>3X-UI is a web control panel for managing Xray-core servers. Prior to 3= .3.1, an authenticated administrator can abuse the database import function= ality to achieve arbitrary file write on the host by modifying Xray configu= ration values stored in the database. This can be leveraged to obtain code = execution and persistent access as the user running Xray (including root wh=
    en Xray is running as root). This vulnerability is fixed in 3.3.1.</td> <td>2026-06-25</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55477" target=3D= "_blank" rel=3D"noopener">CVE-2026-55477</a></td>
    </tr>

    <td class=3D"vendor-product">miurahr--py7zr</td>
    <td>py7zr is a Python-based library and utility to support 7zip archive com= pression, decompression, encryption and decryption. Versions 1.1.2 and belo=
    w contain an an arbitrary file write vulnerability, which allows symbolic l= inks to be recreated outside the destination directory via crafted maliciou=
    s symbolic link chains. When using extractall to extract an archive, the li= brary restores these symbolic links, linking them to arbitrary directories =
    on the host file system. During extraction, the program only checks the lin=
    k arcname within the destination directory, but ignores the combined symlin=
    k path resolution. Attackers can exploit this vulnerability by constructing=
    malicious archives, thereby bypassing the directory boundary restrictions = implemented by the extractor. Subsequent extraction of regular files throug=
    h these symbolic links can result in arbitrary file writes. This vulnerabil= ity may lead to remote code execution, privilege escalation, data corruptio=
    n, or denial of service. This issue has been fixed in version 1.1.3.</td> <td>2026-06-24</td>
    <td>8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-23879" target=3D= "_blank" rel=3D"noopener">CVE-2026-23879</a></td>
    </tr>

    <td class=3D"vendor-product">MyBB--MyBB</td>
    <td>MyBB 1.8.40 does not restrict which usergroup a limited Admin Control P= anel user may assign when creating or editing users; the user module offers=
    the Administrators group (gid 4) and its datahandler's verify_usergroup() = unconditionally returns true. An admin holding only the delegated user-mana= gement permission can assign the Administrators group to an account and esc= alate to the full Administrator permission set.</td>
    <td>2026-06-28</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58054" target=3D= "_blank" rel=3D"noopener">CVE-2026-58054</a></td>
    </tr>

    <td class=3D"vendor-product">n8n--n8n</td>
    <td>n8n before 2.20.0 contains a credential exfiltration vulnerability in t=
    he POST /rest/dynamic-node-parameters/options endpoint that allows authenti= cated users to bypass Allowed HTTP Request Domains restrictions. Attackers = with credential access can cause the n8n server to issue HTTP requests with=
    credentials to unauthorized hosts, exfiltrating sensitive authentication d= ata.</td>
    <td>2026-06-22</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56348" target=3D= "_blank" rel=3D"noopener">CVE-2026-56348</a></td>
    </tr>

    <td class=3D"vendor-product">n8n--n8n</td>
    <td>n8n before version 2.4.0 contains a sql injection vulnerability in MySQ=
    L, PostgreSQL, and Microsoft SQL nodes that allows authenticated users to i= nject arbitrary SQL through unescaped identifier values in node configurati=
    on parameters. Attackers with workflow creation permissions can supply spec= ially crafted table or column names to execute unauthorized database comman=
    ds and compromise data integrity.</td>
    <td>2026-06-24</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56351" target=3D= "_blank" rel=3D"noopener">CVE-2026-56351</a></td>
    </tr>

    <td class=3D"vendor-product">NetComm Wireless Pty Ltd--NF20MESH</td> <td>NetComm NF20MESH routers running firmware R6B031 and earlier contain an=
    authenticated remote code execution vulnerability that allows authenticate=
    d attackers to execute arbitrary commands as root by injecting shell metach= aracters into the username JSON parameter processed by the dalStorage_addUs= erAccount function. Attackers can exploit the unsafe concatenation of user-= supplied input into a shell command string passed to rut_doSystemAction wit= hout sanitization to achieve full root-level command execution on the under= lying operating system.</td>
    <td>2026-06-23</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-35018" target=3D= "_blank" rel=3D"noopener">CVE-2026-35018</a></td>
    </tr>

    <td class=3D"vendor-product">NetComm Wireless Pty Ltd--NF20MESH</td> <td>NetComm NF20MESH routers running firmware R6B031 and earlier contain an=
    authentication bypass vulnerability that allows unauthenticated attackers =
    to gain administrative access by exploiting a hardcoded AES-256 key used to=
    encrypt session cookies for the web management interface. Attackers can fo= rge a valid encrypted session cookie using the shared hardcoded key and byp= ass authentication checks to obtain full administrative control of the mana= gement interface while any legitimate administrator session is active.</td> <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-35019" target=3D= "_blank" rel=3D"noopener">CVE-2026-35019</a></td>
    </tr>

    <td class=3D"vendor-product">newscred--Welcome Software Publishing</td>
    <td>The Welcome Software Publishing plugin for WordPress is vulnerable to A= rbitrary Options Update in all versions up to and including 0.0.31. This is=
    due to a missing capability check in the nc_setOption() function, which is=
    exposed via the nc.setOption XML-RPC method. The function authenticates th=
    e user via $wp_xmlrpc_server-&gt;login() (verifying credentials are valid) = but does not perform any authorization check such as current_user_can('mana= ge_options'). This makes it possible for authenticated attackers, with Subs= criber-level access and above, to update arbitrary WordPress options via XM= L-RPC requests. This can be leveraged to change the default_role option to = 'administrator' and then register a new administrator account, achieving fu=
    ll privilege escalation and site takeover.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-4297" target=3D"= _blank" rel=3D"noopener">CVE-2026-4297</a></td>
    </tr>

    <td class=3D"vendor-product">nicashmu--Cincopa video and media plug-in</td> <td>The Cincopa video and media plug-in plugin for WordPress is vulnerable =
    to Stored Cross-Site Scripting via cincopa Shortcode in Post Comments in al=
    l versions up to, and including, 1.163 due to insufficient input sanitizati=
    on and output escaping. This makes it possible for unauthenticated attacker=
    s to inject arbitrary web scripts in pages that will execute whenever a use=
    r accesses an injected page. Exploitation is possible because the plugin pr= ocesses the [cincopa] shortcode via a comment_text filter hook, allowing un= authenticated visitors who can post comments to supply a malicious shortcod=
    e argument that persists in the database.</td>
    <td>2026-06-24</td>
    <td>7.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10092" target=3D= "_blank" rel=3D"noopener">CVE-2026-10092</a></td>
    </tr>

    <td class=3D"vendor-product">nicolargo--glances</td>
    <td>Glances is an open-source system cross-platform monitoring tool. Prior =
    to 4.5.5, the Glances KVM/QEMU monitoring engine (glances/plugins/vms/engin= es/virsh.py) passes VM domain names, read directly from virsh list --all ou= tput, into f-string command templates that are processed by secure_popen().=
    secure_popen() is explicitly designed to interpret &amp;&amp;, |, and &gt;=
    as shell operators. Because domain names are never sanitised before interp= olation, any user with the ability to create or rename a KVM/QEMU virtual m= achine can execute arbitrary commands as the OS user running Glances - comm= only root on hypervisor hosts. This vulnerability is fixed in 4.5.5.</td> <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46606" target=3D= "_blank" rel=3D"noopener">CVE-2026-46606</a></td>
    </tr>

    <td class=3D"vendor-product">nicolargo--glances</td>
    <td>Glances is an open-source system cross-platform monitoring tool. Prior =
    to 4.5.5, glances/outdated.py uses pickle.load() to read a version-check ca= che file stored at a predictable, world-accessible path (~/.cache/glances/g= lances-version.db or $XDG_CACHE_HOME/glances/glances-version.db). No integr= ity check, signature verification, or format validation is performed before=
    deserialization. An attacker with write access to that path - through any =
    of several realistic local or container-level scenarios - can plant a malic= ious pickle file and achieve arbitrary code execution as the OS user runnin=
    g Glances the next time it starts with version checking enabled (the defaul= t). This vulnerability is fixed in 4.5.5.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46607" target=3D= "_blank" rel=3D"noopener">CVE-2026-46607</a></td>
    </tr>

    <td class=3D"vendor-product">nicolargo--glances</td>
    <td>Glances is an open-source system cross-platform monitoring tool. Prior =
    to 4.5.5, the Glances XML-RPC server (glances -s) introduced a configurable=
    CORS origin list in version 4.5.3 as a mitigation for CVE-2026-33533. Howe= ver, the implementation silently falls back to Access-Control-Allow-Origin:=
    * whenever cors_origins contains more than one entry. An operator who conf= igures an explicit two-entry allowlist (e.g. two internal dashboard origins=
    ) intending to restrict browser access instead receives the unrestricted wi= ldcard. A malicious web page served from any origin can issue a CORS simple=
    request to /RPC2 and read the full system monitoring dataset without the v= ictim's knowledge. This vulnerability is fixed in 4.5.5.</td> <td>2026-06-25</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46608" target=3D= "_blank" rel=3D"noopener">CVE-2026-46608</a></td>
    </tr>

    <td class=3D"vendor-product">nicolargo--glances</td>
    <td>Glances is an open-source system cross-platform monitoring tool. From 4= .0.8 until 4.5.5, the secure_popen() function in glances/secure.py interpre=
    ts &gt; (file redirection), | (pipe), and &amp;&amp; (command chaining) ope= rators in command strings. These operators are applied without any validati=
    on on the target file path, piped command, or chained command. When Applica= tion Monitoring Process (AMP) modules load their command or service_cmd con= figuration values from glances.conf, those values are passed directly to se= cure_popen() with no sanitization. This allows an attacker who can modify t=
    he Glances configuration file to write arbitrary content to arbitrary files= ystem paths (via &gt;), chain arbitrary commands (via &amp;&amp;), or pipe = command output to arbitrary programs (via |). This vulnerability is fixed i=
    n 4.5.5.</td>
    <td>2026-06-25</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53925" target=3D= "_blank" rel=3D"noopener">CVE-2026-53925</a></td>
    </tr>

    <td class=3D"vendor-product">nltk--nltk</td>
    <td>NLTK (Natural Language Toolkit) is a suite of open source Python module=
    s, data sets, and tutorials supporting research and development in Natural = Language Processing. Prior to 3.10.0-rc1, nltk.data.load() in NLTK is vulne= rable to path traversal via URL-encoded path separators and traversal segme= nts when using the nltk: URL scheme. The unsafe-path regex check is perform=
    ed before url2pathname() decodes the %xx sequences (a classic decode-after-= check / TOCTOU-style flaw), allowing an attacker to bypass the protection d= ocumented in NLTK's SECURITY.md and read arbitrary files from the filesyste=
    m. While literal traversal strings such as ../../../etc/passwd are correctl=
    y blocked, encoded variants such as %2fetc%2fpasswd, %2e%2e%2f..., and ..%2= f..%2f slip past the regex and are subsequently decoded into a real filesys= tem path. This vulnerability is fixed in 3.10.0-rc1.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54293" target=3D= "_blank" rel=3D"noopener">CVE-2026-54293</a></td>
    </tr>

    <td class=3D"vendor-product">nmedia--Frontend File Manager Plugin</td>
    <td>The Frontend File Manager Plugin plugin for WordPress is vulnerable to = Authenticated Arbitrary File Deletion in versions up to and including 23.6.=
    This is due to a case-sensitive bypass of the wpfm_dir_path parameter sani= tization in the wpfm_file_meta_update AJAX handler, where supplying WPFM_DI= R_PATH in uppercase evades the unset check and is normalized to wpfm_dir_pa=
    th by sanitize_key() during update_post_meta(), allowing an attacker to ove= rwrite the stored file path with an arbitrary filesystem path that is then = passed directly to unlink() in delete_file_locally() without any directory = containment validation. This makes it possible for authenticated attackers = with Subscriber-level access to delete arbitrary files on the server, inclu= ding sensitive files such as wp-config.php, potentially leading to full sit=
    e takeover.</td>
    <td>2026-06-27</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8095" target=3D"= _blank" rel=3D"noopener">CVE-2026-8095</a></td>
    </tr>

    <td class=3D"vendor-product">notepad-plus-plus--notepad-plus-plus</td> <td>Notepad++ is a free and open-source source code editor. Prior to 8.9.6.=
    1, the &lt;GUIConfig name=3D"commandLineInterpreter"&gt; tag in config.xml =
    is read by NppXml::value() (Parameters.cpp:6430) and stored in _nppGUI._com= mandLineInterpreter without any validation, whitelist, or digital signature=
    check. When the user triggers IDM_FILE_OPEN_CMD (File =C3=A2=E2=80=A0=E2= =80=99 Open Containing Folder =C3=A2=E2=80=A0=E2=80=99 cmd), NppCommands.cp= p:228 creates a Command object with this value and calls run(), which invok=
    es ShellExecute (RunDlg.cpp:221) with the attacker-controlled string as the=
    executable path. This vulnerability is fixed in 8.9.6.1.</td> <td>2026-06-26</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48778" target=3D= "_blank" rel=3D"noopener">CVE-2026-48778</a></td>
    </tr>

    <td class=3D"vendor-product">notepad-plus-plus--notepad-plus-plus</td> <td>Notepad++ is a free and open-source source code editor. Prior to 8.9.6.=
    1, the &lt;Command&gt; tag text content inside &lt;UserDefinedCommands&gt; =
    in shortcuts.xml is read by NppXml::value(aNode) (Parameters.cpp:3658) in t=
    he feedUserCmds() function and stored in UserCommand._cmd without any valid= ation. When the user clicks the corresponding entry in the Run menu, NppCom= mands.cpp:4264 creates a Command object with string2wstring(ucmd.getCmd()) = and calls run(), which invokes ShellExecute (RunDlg.cpp:221) with the attac= ker-controlled string as the executable path. The injected command appears =
    as a normal menu item in the Run menu, making it a viable persistence mecha= nism. This vulnerability is fixed in 8.9.6.1.</td>
    <td>2026-06-26</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48800" target=3D= "_blank" rel=3D"noopener">CVE-2026-48800</a></td>
    </tr>

    <td class=3D"vendor-product">notepad-plus-plus--notepad-plus-plus</td> <td>Notepad++ is a free and open-source source code editor. In v8.9.6.1, is= InTrustedDirectory() does NOT canonicalize the path before checking. It use=
    s a prefix-based check (PathIsPrefix() or equivalent) that matches paths st= arting with trusted directory strings. A path traversal using ..\..\ after =
    a trusted directory prefix passes the check while resolving to an untrusted=
    location. The CVE-2026-48800 patch adds isInTrustedDirectory() validation =
    in Command::run() (RunDlg.cpp) before calling ShellExecute(). This function=
    checks whether the resolved executable path is under a trusted directory. = This vulnerability is fixed in 8.9.6.2.</td>
    <td>2026-06-26</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52884" target=3D= "_blank" rel=3D"noopener">CVE-2026-52884</a></td>
    </tr>

    <td class=3D"vendor-product">NSquared--Simply Schedule Appointments</td> <td>Unauthenticated Cross Site Scripting (XSS) in Simply Schedule Appointme= nts &lt;=3D 1.6.12.2 versions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57317" target=3D= "_blank" rel=3D"noopener">CVE-2026-57317</a></td>
    </tr>

    <td class=3D"vendor-product">Online Web Tutor--Library Management System</t=

    <td>Unauthenticated SQL Injection in Library Management System &lt;=3D 3.5.=
    7 versions.</td>
    <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56034" target=3D= "_blank" rel=3D"noopener">CVE-2026-56034</a></td>
    </tr>

    <td class=3D"vendor-product">oooorgle--Quotes llama</td>
    <td>Unauthenticated SQL Injection in Quotes llama &lt;=3D 3.1.5 versions.</=

    <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56062" target=3D= "_blank" rel=3D"noopener">CVE-2026-56062</a></td>
    </tr>

    <td class=3D"vendor-product">Open Health Imaging Foundation (OHIF)--DICOM W=
    eb Viewer Framework</td>
    <td>Two data sources (DICOMWebProxy and DICOMJSON) shipped in the default c= onfiguration fetch an arbitrary URL parameter without validation. A global = authentication service in OHIF automatically injects the authenticated user=
    's OIDC Bearer token into the resulting requests, sending it to the attacke= r-controlled server. DICOMweb data sources are not impacted.</td> <td>2026-06-25</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12473" target=3D= "_blank" rel=3D"noopener">CVE-2026-12473</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, backend/open_webui/utils/oauth.= py::_process_picture_url calls validate_url(picture_url) on the initial URL=
    only, then invokes aiohttp.ClientSession.get(picture_url, ...) without all= ow_redirects=3DFalse. aiohttp's default is allow_redirects=3DTrue, max_redi= rects=3D10; the function does not pass the project's AIOHTTP_CLIENT_ALLOW_R= EDIRECTS env constant either. An attacker with a valid OAuth IdP identity c=
    an therefore submit a public URL that 302-redirects to an internal address = and read the internal response body via the attacker's own profile_image_ur=
    l field. This vulnerability is fixed in 0.9.6.</td>
    <td>2026-06-23</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54008" target=3D= "_blank" rel=3D"noopener">CVE-2026-54008</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, Open WebUI lets an authenticate=
    d user attach arbitrary file_id values to their own chat message without ch= ecking whether they own or can read those files. If the attacker then share=
    s that chat and grants themselves read access, has_access_to_file() treats = the victim file as accessible through the shared chat, and the file endpoin=
    ts read or delete the victim file. This vulnerability is fixed in 0.9.6.</t=

    <td>2026-06-23</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54010" target=3D= "_blank" rel=3D"noopener">CVE-2026-54010</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6,Open WebUI renders Mermaid block=
    s from Markdown files in the file preview panel and inserts the generated S=
    VG into the DOM using innerHTML. Because Mermaid is configured with securit= yLevel: 'loose', attacker-controlled Mermaid content can be rendered unsafe=
    ly in this flow. A working payload was validated through the Markdown previ=
    ew path, resulting in JavaScript execution in the victim's browser under th=
    e application origin. This vulnerability is fixed in 0.9.6.</td> <td>2026-06-23</td>
    <td>8.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54011" target=3D= "_blank" rel=3D"noopener">CVE-2026-54011</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, Open WebUI lets a user who can = create, update, or import workspace models store arbitrary meta.knowledge e= ntries on their model without checking whether they own or can read the ref= erenced files. Open WebUI then treats meta.knowledge entries of type file a=
    s an authorization source in two places: the built-in view_file tool reads = the file's extracted text, and has_access_to_file()'s model branch authoriz=
    es the file content and file delete endpoints. A malicious model owner can = therefore attach another user's file ID to their model metadata and read or=
    delete that private file. This vulnerability is fixed in 0.9.6.</td> <td>2026-06-23</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54012" target=3D= "_blank" rel=3D"noopener">CVE-2026-54012</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, Open WebUI patched SVG XSS in u= ser profile images and webhook profile images but forgot to apply the same = fix to model profile images. The ModelMeta class has no validate_profile_im= age_url field validator, and the model image serving endpoint has no MIME a= llowlist or nosniff header. Any authenticated user with workspace.models pe= rmission (enabled by default) can store a data:image/svg+xml;base64,... pay= load in a model's profile image and achieve full account takeover of anyone=
    who navigates to the image URL. This vulnerability is fixed in 0.9.6.</td> <td>2026-06-23</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54013" target=3D= "_blank" rel=3D"noopener">CVE-2026-54013</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, the SafePlaywrightURLLoader imp= lements a validate_url function to prevent SSRF attacks by checking the IP = address of the user-provided URL. However, this validation is performed onl=
    y on the initial URL. Since Playwright automatically follows HTTP redirects=
    (301/302) by default, an attacker can bypass the validation by providing a=
    safe URL that redirects to a restricted internal network address (e.g., lo= calhost, Docker container network, or Cloud Metadata). This allows the appl= ication to access internal services despite ENABLE_RAG_LOCAL_WEB_FETCH bein=
    g set to False This vulnerability is fixed in 0.9.6.</td>
    <td>2026-06-23</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54018" target=3D= "_blank" rel=3D"noopener">CVE-2026-54018</a></td>
    </tr>

    <td class=3D"vendor-product">OpenBSD--OpenBSD</td>
    <td>sys/kern/sysv_sem.c in OpenBSD through 7.9 has a use-after-free allowin=
    g local privilege escalation to root. This is a context switch use-after-fr=
    ee after tsleep in sys_semget().</td>
    <td>2026-06-25</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57589" target=3D= "_blank" rel=3D"noopener">CVE-2026-57589</a></td>
    </tr>

    <td class=3D"vendor-product">openremote--openremote</td>
    <td>OpenRemote before 1.25.0 contains an insecure direct object reference (= IDOR) vulnerability in the bulk alarm deletion endpoint that allows authent= icated users to permanently delete alarms belonging to other tenants by sup= plying arbitrary alarm IDs. The removeAlarms() method in AlarmResourceImpl.= java omits realm-scoping validation in its JPA query, enabling any user wit=
    h alarm-write permissions to enumerate sequential auto-increment alarm IDs = and delete cross-tenant alarm records without authorization.</td> <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56784" target=3D= "_blank" rel=3D"noopener">CVE-2026-56784</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to , the official openproject/openproject Docker image ships ENV SECRET_K= EY_BASE=3DOVERWRITE_ME as the default Rails master key. Combined with cooki= es_serializer =3D :marshal, this gives any logged-in user a deterministic M= arshal-deserialization path reachable via the /my/two_factor_devices cookie=
    reader This vulnerability is fixed in .</td>
    <td>2026-06-26</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46386" target=3D= "_blank" rel=3D"noopener">CVE-2026-46386</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.3 and 17.4.1, cache store poisoning leads to Remote Code Executio=
    n (RCE). This vulnerability is fixed in 17.3.3 and 17.4.1.</td> <td>2026-06-26</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52780" target=3D= "_blank" rel=3D"noopener">CVE-2026-52780</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.3 and 17.4.1, there is an IDOR through /projects/&lt;A&gt;/settin= gs/project_storages/&lt;A_ps_id&gt; via PATCH parameter "storages_project_s= torage[project_folder_id]" leads to Access to Unauthorized Resources. A pro= ject-admin in one project can hijack the managed Nextcloud or OneDrive fold=
    er of another project on the same storage by writing the victim project's p= roject_folder_id into the attacker's Storages::ProjectStorage row. The next=
    managed-folder sync overwrites the ACL on the referenced folder with the a= ttacker project's user list. This vulnerability is fixed in 17.3.3 and 17.4= .1.</td>
    <td>2026-06-26</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52782" target=3D= "_blank" rel=3D"noopener">CVE-2026-52782</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.3 and 17.4.1, there is a SQL injection in timestamps functionalit=
    y. OpenProject baseline comparison allows callers to request historic work-= package attributes using the timestamps parameter. This vulnerability is fi= xed in 17.3.3 and 17.4.1.</td>
    <td>2026-06-26</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52785" target=3D= "_blank" rel=3D"noopener">CVE-2026-52785</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.3 and 17.4.1, OpenProject's Storages module writes the OneDrive/S= harePoint userless OAuth access_token plaintext to Rails.cache under the de= terministic key storage.&lt;id&gt;.httpx_access_token, repopulated continuo= usly by an hourly cron and every userless-OAuth call site (see Write cadenc= e). None of the three allowed cache backends (file_store, memcache, redis) = encrypts at rest. An attacker with read access to the cache backend recover=
    s the Azure-AD application-tier bearer with an anonymous get over the memca= ched binary protocol (or the equivalent against Redis). This vulnerability =
    is fixed in 17.3.3 and 17.4.1.</td>
    <td>2026-06-26</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52783" target=3D= "_blank" rel=3D"noopener">CVE-2026-52783</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.3 and 17.4.1, there is a CSRF on TARGET through /users/:id via PO=
    ST parameter "user[admin]". This vulnerability is fixed in 17.3.3 and 17.4.= 1.</td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52784" target=3D= "_blank" rel=3D"noopener">CVE-2026-52784</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.3 and 17.4.1, the journal diff endpoint discloses hidden historic=
    al field values without enforcing object and field visibility. This vulnera= bility is fixed in 17.3.3 and 17.4.1.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47193" target=3D= "_blank" rel=3D"noopener">CVE-2026-47193</a></td>
    </tr>

    <td class=3D"vendor-product">pagekit--pagekit</td>
    <td>Pagekit CMS 1.0.18 contains a privilege escalation vulnerability that a= llows authenticated users with the 'user: manage users' permission to escal= ate privileges by assigning arbitrary custom roles to themselves due to mis= sing authorization checks in UserApiController::saveAction(). Attackers can=
    assign themselves a custom role with the 'system: manage packages' permiss= ion and then upload and install a malicious PHP package through the admin p= ackage installer to achieve remote code execution.</td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57518" target=3D= "_blank" rel=3D"noopener">CVE-2026-57518</a></td>
    </tr>

    <td class=3D"vendor-product">Paolo--GeoDirectory</td>
    <td>Unauthenticated SQL Injection in GeoDirectory &lt;=3D 2.8.162 versions.= </td>
    <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54831" target=3D= "_blank" rel=3D"noopener">CVE-2026-54831</a></td>
    </tr>

    <td class=3D"vendor-product">parse-community--parse-server</td>
    <td>Parse Server before 4.10.0 contains a supply chain vulnerability where = incorrect version tags were pushed to the repository linking to unreviewed = code in a personal fork. Attackers could exploit this by specifying affecte=
    d version tags in dependency declarations to execute unreviewed and potenti= ally malicious code.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2021-47986" target=3D= "_blank" rel=3D"noopener">CVE-2021-47986</a></td>
    </tr>

    <td class=3D"vendor-product">parse-community--parse-server</td>
    <td>Parse Server before 4.10.0 was affected by a supply chain incident in w= hich incorrect version tags were pushed to the official repository pointing=
    to an unreviewed personal fork of a contributor with write access. No rele= ases were published with these tags; a project was exposed only if it defin=
    ed a git-based dependency referencing one of the affected tags (for example=
    , parse-server#4.9.3). The code behind the tags was not reviewed or approve=
    d, and although no malicious code was identified, the introduction of secur= ity vulnerabilities could not be ruled out.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2021-47987" target=3D= "_blank" rel=3D"noopener">CVE-2021-47987</a></td>
    </tr>

    <td class=3D"vendor-product">Paymob--Paymob for WooCommerce</td> <td>Unauthenticated Broken Access Control in Paymob for WooCommerce &lt;=3D=
    4.1.2 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56025" target=3D= "_blank" rel=3D"noopener">CVE-2026-56025</a></td>
    </tr>

    <td class=3D"vendor-product">paytiumsupport--Paytium</td>
    <td>Unauthenticated Privilege Escalation in Paytium &lt;=3D 5.0.2 versions.= </td>
    <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56030" target=3D= "_blank" rel=3D"noopener">CVE-2026-56030</a></td>
    </tr>

    <td class=3D"vendor-product">Peplink--InControl</td>
    <td>Peplink InControl 2 through 2.14.2 before 2026-06-03 allows use of a se= micolon to bypass access-control rules for certain /rest/o/{orgId} endpoint= s.</td>
    <td>2026-06-26</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57920" target=3D= "_blank" rel=3D"noopener">CVE-2026-57920</a></td>
    </tr>

    <td class=3D"vendor-product">Perfmatters, Powered Kinsta + GeneratePress Do=
    cs Changelog Feature requests Legal Affiliate Contact--perfmatters</td> <td>Unauthenticated Cross Site Scripting (XSS) in perfmatters &lt;=3D 2.6.3=
    versions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56047" target=3D= "_blank" rel=3D"noopener">CVE-2026-56047</a></td>
    </tr>

    <td class=3D"vendor-product">PhysCode--Travel Booking</td>
    <td>Subscriber Arbitrary File Upload in Travel Booking &lt;=3D 2.2.5 versio= ns.</td>
    <td>2026-06-26</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56059" target=3D= "_blank" rel=3D"noopener">CVE-2026-56059</a></td>
    </tr>

    <td class=3D"vendor-product">Picklescan--Picklescan</td>
    <td>Picklescan before 0.0.33 fails to detect the numpy.f2py.crackfortran._e= val_length gadget in pickle __reduce__ methods, allowing arbitrary code exe= cution. Attackers can craft malicious pickle files that execute arbitrary P= ython code when loaded by victims who trust Picklescan's safety validation.= </td>
    <td>2026-06-22</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71339" target=3D= "_blank" rel=3D"noopener">CVE-2025-71339</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan before 1.0.4 fails to block at least seven Python standard l= ibrary modules (including uuid, _osx_support, _aix_support, _pyrepl.pager, = and imaplib) exposing eight functions that provide direct arbitrary command=
    execution. Attackers can craft malicious pickle files importing these unbl= ocked modules to achieve remote code execution while bypassing picklescan's=
    safety validation entirely.</td>
    <td>2026-06-23</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56315" target=3D= "_blank" rel=3D"noopener">CVE-2026-56315</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan through 0.0.26 fails to detect malicious pickle files that i= nvoke idlelib.pyshell.ModifiedInterpreter.runcode in __reduce__ methods. At= tackers can embed undetected code in pickle files that executes arbitrary c= ommands when the file is loaded via pickle.load(), enabling supply chain at= tacks on PyTorch models and saved Python objects. This is fixed in version = 0.0.30.</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71340" target=3D= "_blank" rel=3D"noopener">CVE-2025-71340</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan before 0.0.29 fails to detect the profile.Profile.runctx fun= ction when analyzing pickle files, allowing attackers to embed undetected m= alicious code. Remote attackers can craft malicious pickle files using prof= ile.Profile.runctx in the reduce method to achieve remote code execution wh=
    en the pickle file is loaded.</td>
    <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71341" target=3D= "_blank" rel=3D"noopener">CVE-2025-71341</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan before 0.0.30 (affected versions 0.0.26 and earlier) fails t=
    o detect the ensurepip._run_pip built-in function when scanning pickle file=
    s, allowing attackers to execute arbitrary code. Malicious pickle files emb= edding ensurepip._run_pip calls in __reduce__ methods bypass picklescan det= ection and achieve remote code execution upon pickle.load() invocation.</td=

    <td>2026-06-22</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71344" target=3D= "_blank" rel=3D"noopener">CVE-2025-71344</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan before 0.0.29 fails to detect malicious pickle files that ex= ploit idlelib.debugobj.ObjectTreeItem.SetText function in reduce methods. A= ttackers can craft pickle files with embedded code that bypasses picklescan=
    detection and executes arbitrary commands when pickle.load() is called.</t=

    <td>2026-06-24</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71354" target=3D= "_blank" rel=3D"noopener">CVE-2025-71354</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan before 0.0.29 fails to detect malicious pickle files that ex= ploit idlelib.autocomplete.AutoComplete.get_entity function in reduce metho= ds. Attackers can embed undetected code in pickle files that executes arbit= rary commands when loaded by victims using pickle.load().</td> <td>2026-06-22</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71358" target=3D= "_blank" rel=3D"noopener">CVE-2025-71358</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan before 0.0.29 fails to detect malicious idlelib.calltip.Call= tip.fetch_tip calls in pickle files, allowing remote code execution. Attack= ers can embed undetected payloads in pickle files that execute arbitrary co=
    de when loaded via pickle.load().</td>
    <td>2026-06-24</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71361" target=3D= "_blank" rel=3D"noopener">CVE-2025-71361</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan before 0.0.33 fails to detect malicious pickle files that in= voke numpy.f2py.crackfortran.myeval function through the reduce method. Att= ackers can craft malicious pickle files embedding arbitrary code that evade=
    s picklescan detection and executes remote code when loaded.</td> <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71365" target=3D= "_blank" rel=3D"noopener">CVE-2025-71365</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan before 0.0.28 fails to detect malicious torch.jit.unsupporte= d_tensor_ops.execWrapper function calls embedded in pickle files. Attackers=
    can craft malicious pickle files that bypass picklescan detection and exec= ute arbitrary code when loaded via pickle.load().</td>
    <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71370" target=3D= "_blank" rel=3D"noopener">CVE-2025-71370</a></td>
    </tr>

    <td class=3D"vendor-product">picklescan--picklescan</td>
    <td>picklescan before 0.0.29 fails to detect malicious pickle files using i= dlelib.autocomplete.AutoComplete.fetch_completions in reduce methods. Attac= kers can embed undetected code in pickle files that executes arbitrary comm= ands when loaded by victims.</td>
    <td>2026-06-23</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71376" target=3D= "_blank" rel=3D"noopener">CVE-2025-71376</a></td>
    </tr>

    <td class=3D"vendor-product">Pilz--PMI v8xx</td>
    <td>A stored cross-site scripting vulnerability in the Runtime component of=
    Pilz PASvisu before 1.14.1 and PMI v8xx up to and including 2.0.33992 allo=
    ws a low-privileged remote unauthenticated attacker to manipulate process d= ata with potential impact on integrity and/or availability.</td> <td>2026-06-22</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2023-45796" target=3D= "_blank" rel=3D"noopener">CVE-2023-45796</a></td>
    </tr>

    <td class=3D"vendor-product">Pilz--PMI v8xx</td>
    <td>A cross-site scripting vulnerability in the Builder Component of Pilz P= ASvisu before 1.14.1 allows a local unauthenticated attacker to inject mali= cious javascript and gain full control over the device.</td> <td>2026-06-22</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2023-45795" target=3D= "_blank" rel=3D"noopener">CVE-2023-45795</a></td>
    </tr>

    <td class=3D"vendor-product">piscinajs--piscina</td>
    <td>piscina is a node.js worker pool implementation. Prior to 6.0.0-rc.2, 5= .2.0, and 4.9.3, piscina's constructor and run() paths read the filename op= tion via plain member access. Both reads fall through the prototype chain w= hen the caller's options object doesn't have filename as an own property. W= hen Object.prototype.filename is polluted upstream the inherited value flow=
    s to worker_threads.Worker import and the attacker's .mjs runs in the worke=
    r. This vulnerability is fixed in 6.0.0-rc.2, 5.2.0, and 4.9.3.</td> <td>2026-06-22</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55388" target=3D= "_blank" rel=3D"noopener">CVE-2026-55388</a></td>
    </tr>

    <td class=3D"vendor-product">Pluggabl--Booster for WooCommerce</td> <td>Customer Arbitrary File Upload in Booster for WooCommerce &lt;=3D 8.0.1=
    versions.</td>
    <td>2026-06-26</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56027" target=3D= "_blank" rel=3D"noopener">CVE-2026-56027</a></td>
    </tr>

    <td class=3D"vendor-product">PluginUs.Net--MDTF</td>
    <td>Unauthenticated SQL Injection in MDTF &lt;=3D 1.3.7 versions.</td> <td>2026-06-25</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54843" target=3D= "_blank" rel=3D"noopener">CVE-2026-54843</a></td>
    </tr>

    <td class=3D"vendor-product">PluginUs.Net--MDTF</td>
    <td>Unauthenticated Local File Inclusion in MDTF &lt;=3D 1.3.8 versions.</t=

    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54845" target=3D= "_blank" rel=3D"noopener">CVE-2026-54845</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm allows a t= ransitive dependency alias from registry package metadata to contain path t= raversal segments. During install, pnpm later uses that alias as a filesyst=
    em path when linking dependency nodes. As a result, a registry package can = cause `pnpm install --ignore-scripts` to replace paths in the current proje=
    ct with symlinks to attacker-controlled dependency package directories. Thi=
    s vulnerability is fixed in 10.34.0 and 11.4.0.</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50016" target=3D= "_blank" rel=3D"noopener">CVE-2026-50016</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can persis=
    t package-manager bootstrap metadata in the first YAML document of pnpm-loc= k.yaml. Before the patch, direct pnpm execution trusted an already resolved=
    packageManagerDependencies entry when the committed env lockfile contained=
    matching pnpm and @pnpm/exe versions. A malicious repository could therefo=
    re commit package-manager lockfile package records and snapshots that bypas= sed fresh package-manager resolution, then cause pnpm to install and execut=
    e bytes selected by that committed lockfile state during automatic version = switching. This vulnerability is fixed in 10.34.2 and 11.5.3.</td> <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55698" target=3D= "_blank" rel=3D"noopener">CVE-2026-55698</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's patch ap= plication pipeline (@pnpm/patch-package) performs no path validation on fil=
    e paths extracted from .patch files. An attacker who contributes a maliciou=
    s patch file via a pull request can write attacker-controlled content to or=
    delete arbitrary files on the filesystem during pnpm install, as the user = running the install. The diff --git header paths containing ../../ sequence=
    s traverse out of the package directory, and the traversal is difficult to = catch in code review because patch file diff headers are opaque to most rev= iewers. This vulnerability is fixed in 10.34.0 and 11.4.0.</td> <td>2026-06-25</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50015" target=3D= "_blank" rel=3D"noopener">CVE-2026-50015</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.2 and 11.5.3, the generic pee= r-suffix normalizer also stripped parenthesized text from git, URL, tarball=
    , file, and other opaque locators. Approval for one source string could the= refore authorize a different attacker-controlled source whose locator norma= lized to the same value. This vulnerability is fixed in 10.34.2 and 11.5.3.= </td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55487" target=3D= "_blank" rel=3D"noopener">CVE-2026-55487</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can instal=
    l configDependencies declared in pnpm-workspace.yaml before command dispatc=
    h. Before the patch, a repository could declare pacquet or @pnpm/pacquet as=
    a config dependency and pnpm treated that repository-controlled dependency=
    as an install-engine opt-in. During install, pnpm resolved a platform-spec= ific @pacquet/&lt;platform&gt;-&lt;arch&gt;/pacquet binary from node_module= s/.pnpm-config/&lt;packageName&gt; and spawned it as the developer or CI us= er. This vulnerability is fixed in 10.34.2 and 11.5.3.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55697" target=3D= "_blank" rel=3D"noopener">CVE-2026-55697</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. From 11.3.0 until 11.5.3, `pnpm stage downlo= ad` derived a local filename from registry-controlled package name and vers= ion fields. A crafted manifest could escape the selected download directory=
    and overwrite another reachable file. The merged fix validates both fields=
    , derives one safe filename, and verifies the final destination before writ= ing. This vulnerability is fixed in 11.5.3.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55700" target=3D= "_blank" rel=3D"noopener">CVE-2026-55700</a></td>
    </tr>

    <td class=3D"vendor-product">podman-container-tools--podman</td>
    <td>Podman is a tool for managing OCI containers and pods. From 1.8.1 until=
    5.8.4, a container image that contains a environment variable with just a = key and no value can trick podman into passing that variable from the host = into the container. This is made worse by the fact that using an asterisk (=
    *) will cause podman to pass all host variables into the container. So esse= ntially a malicious image can exfiltrate all podman environment variables t= hat are set in the session from where the container is launched. This vulne= rability is fixed in 5.8.4 and 6.0.0.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57231" target=3D= "_blank" rel=3D"noopener">CVE-2026-57231</a></td>
    </tr>

    <td class=3D"vendor-product">Post Snippets--Post Snippets</td>
    <td>Contributor Remote Code Execution (RCE) in Post Snippets &lt;=3D 4.0.19=
    versions.</td>
    <td>2026-06-25</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56049" target=3D= "_blank" rel=3D"noopener">CVE-2026-56049</a></td>
    </tr>

    <td class=3D"vendor-product">poweradmin--poweradmin</td>
    <td>Poweradmin is a web-based DNS administration tool for PowerDNS server. = Versions prior to 4.2.4 and 4.3.3 use the attacker-controlled `HTTP_HOST` r= equest header as the authoritative source for building callback URLs in its=
    OIDC, SAML, and logout authentication flows without any validation. An una= uthenticated attacker can poison the `redirect_uri` sent to the Identity Pr= ovider, causing the IdP to redirect the victim's authorization code to an a= ttacker-controlled server - resulting in full account takeover with no cred= entials required. Versions 4.2.4 and 4.3.3 patch the issue.</td> <td>2026-06-23</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54588" target=3D= "_blank" rel=3D"noopener">CVE-2026-54588</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--Recursor</td>
    <td>A malicious authoritative server can send a crafted zone via the ZoneTo= Cache function that leads to cache poisoning.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-33612" target=3D= "_blank" rel=3D"noopener">CVE-2026-33612</a></td>
    </tr>

    <td class=3D"vendor-product">pravel--Invoice Generator</td>
    <td>The Invoice Generator plugin for WordPress is vulnerable to privilege e= scalation due to a missing capability check on the pravel_invoice_edit_acco= unt() AJAX action in versions up to, and including, 1.0.0. The handler is e= xposed via wp_ajax_nopriv_pravel_invoice_edit_account, accepts an attacker-= controlled user_id and user_email from POST data, and calls wp_update_user(=
    ) without verifying authentication, ownership, or a nonce. This makes it po= ssible for unauthenticated attackers to change the email address of any use=
    r, including administrators, and then trigger WordPress's password reset fl=
    ow to gain access to the targeted account.</td>
    <td>2026-06-27</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12415" target=3D= "_blank" rel=3D"noopener">CVE-2026-12415</a></td>
    </tr>

    <td class=3D"vendor-product">pravel--Invoice Generator</td>
    <td>The Invoice Generator plugin for WordPress is vulnerable to Account Tak= eover via Password Reset in all versions up to, and including, 1.0.0. This =
    is due to the `pravel_invoice_change_password()` function being registered =
    as a nopriv AJAX handler with no nonce verification and no authorization ch= eck, and performing a loose equality comparison between the supplied `reset= _activation_code` POST parameter and the target user's stored `forgot_email=
    ` user meta - a check that trivially evaluates to true (`'' =3D=3D ''`) for=
    any user who has never initiated a forgot-password request, which applies =
    to administrators under normal conditions. This makes it possible for unaut= henticated attackers to supply an arbitrary user ID via the `reset_user_id`=
    POST parameter, bypass the activation code check entirely by omitting `res= et_activation_code`, and set the target account's password to an attacker-c= hosen value, enabling full takeover of any account on the site, including a= dministrator accounts.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12416" target=3D= "_blank" rel=3D"noopener">CVE-2026-12416</a></td>
    </tr>

    <td class=3D"vendor-product">pravel--SignUp &amp; SignIn</td>
    <td>The SignUp &amp; SignIn plugin for WordPress is vulnerable to Authentic= ation Bypass via Weak Password Reset Validation leading to Account Takeover=
    in versions up to, and including, 1.0.0. This is due to the `pravel_change= _password()` AJAX handler - registered via `wp_ajax_nopriv_pravel_change_pa= ssword` and therefore accessible to unauthenticated users - performing no n= once verification, no capability check, and only a loose equality check bet= ween an attacker-supplied `reset_activation_code` POST parameter and the ta= rget user's `forgot_email` user meta value; when a user has never initiated=
    a password reset, `get_user_meta()` returns an empty string that trivially=
    satisfies this check against an omitted or empty attacker-supplied code. T= his makes it possible for unauthenticated attackers to change the password =
    of any WordPress user, including administrators, by sending a crafted POST = request to `admin-ajax.php` with `action=3Dpravel_change_password`, `reset_= user_id` set to the target account's user ID, and `new_password_custom` set=
    to an attacker-chosen password. Successful exploitation allows the attacke=
    r to authenticate with the newly set password and fully take over the targe= ted account, achieving administrator-level privilege escalation on the affe= cted site.</td>
    <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12417" target=3D= "_blank" rel=3D"noopener">CVE-2026-12417</a></td>
    </tr>

    <td class=3D"vendor-product">Premmerce--Premmerce Wishlist for WooCommerce<=

    <td>Unauthenticated SQL Injection in Premmerce Wishlist for WooCommerce &lt= ;=3D 1.1.11 versions.</td>
    <td>2026-06-25</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54849" target=3D= "_blank" rel=3D"noopener">CVE-2026-54849</a></td>
    </tr>

    <td class=3D"vendor-product">presire--qSnapper</td>
    <td>A time-to-check-time-of-use in polkit authentication of qSnapper before=
    version 1.3.3 allowed a local attacker to bypass qSnappers authentication = mechanism and operate e.g. as root user.</td>
    <td>2026-06-22</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41045" target=3D= "_blank" rel=3D"noopener">CVE-2026-41045</a></td>
    </tr>

    <td class=3D"vendor-product">presire--qSnapper</td>
    <td>A path traversal attack when using a "configName" parameter in qSnapper=
    before version 1.3.3 allowed a local attacker to use malicious config file=
    s for snapper and so cause a denial of service or potentially escalate priv= ileges to root.</td>
    <td>2026-06-22</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41046" target=3D= "_blank" rel=3D"noopener">CVE-2026-41046</a></td>
    </tr>

    <td class=3D"vendor-product">ProFTPD Project--ProFTPD</td>
    <td>ProFTPD through 1.3.9b and 1.3.10rc2 contains an access control bypass = vulnerability that allows authenticated FTP users to circumvent Directory A=
    CL restrictions by prefixing paths with /proc/self/root in the RNFR command=
    handler. Attackers can exploit the unresolved symlink components in dir_ca= nonical_path() to cause dir_check() to perform lexical path comparisons tha=
    t match no configured Directory block, enabling rename operations on files =
    in DenyAll-protected directories and subsequent retrieval of those files. M= itigation: Sessions configured with DefaultRoot (chroot) are not affected, =
    as chroot changes the directory to which /proc/self/root resolves.</td> <td>2026-06-24</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-35025" target=3D= "_blank" rel=3D"noopener">CVE-2026-35025</a></td>
    </tr>

    <td class=3D"vendor-product">protobufjs--protobuf.js</td>
    <td>protobufjs compiles protobuf definitions into JavaScript (JS) functions=
    . Prior to 7.6.1 and 8.4.1, protobufjs could recurse without a depth limit = while converting decoded messages to plain objects or JSON. This affected g= enerated toObject() conversion and the custom google.protobuf.Any JSON conv= ersion path. A crafted protobuf binary payload containing deeply nested Any=
    values could cause the JavaScript call stack to be exhausted during conver= sion to JSON. This vulnerability is fixed in 7.6.1 and 8.4.1.</td> <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48712" target=3D= "_blank" rel=3D"noopener">CVE-2026-48712</a></td>
    </tr>

    <td class=3D"vendor-product">protobufjs--protobufjs-cli</td>
    <td>protobufjs-cli is the command line add-on for protobuf.js. Prior to 1.3=
    .2 and 2.5.0, a previous fix for unsafe name handling in pbjs static / stat= ic-module code generation was incomplete. Affected versions of protobufjs-c=
    li could still emit unsafe JavaScript references when generating static out= put from crafted JSON descriptor input. The common case of parsing schemas = from .proto files is not affected. This is a bypass of CVE-2026-44295. An a= ttacker who can provide or influence pre-parsed JSON descriptors passed to = pbjs static code generation may be able to cause generated JavaScript outpu=
    t to contain attacker-controlled code. The injected code may execute if the=
    generated file is later executed or imported and an affected generated API=
    path is invoked. This vulnerability is fixed in 1.3.2 and 2.5.0.</td> <td>2026-06-22</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54271" target=3D= "_blank" rel=3D"noopener">CVE-2026-54271</a></td>
    </tr>

    <td class=3D"vendor-product">PSM Plugins--SupportCandy</td>
    <td>Subscriber Insecure Direct Object References (IDOR) in SupportCandy &lt= ;=3D 3.4.6 versions.</td>
    <td>2026-06-26</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54826" target=3D= "_blank" rel=3D"noopener">CVE-2026-54826</a></td>
    </tr>

    <td class=3D"vendor-product">pydicom--pynetdicom Library</td>
    <td>The qrscp application's C-STORE handler uses a specific instance from a= ttacker-supplied DICOM datasets directly in os.path.join() without sanitiza= tion, allowing file writes to arbitrary paths.</td>
    <td>2026-06-25</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56445" target=3D= "_blank" rel=3D"noopener">CVE-2026-56445</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect AWK Plugin</td>
    <td>OS Command Injection vulnerability in the process_string action of Rapi=
    d7 InsightConnect AWK Plugin on Linux allows remote attackers to execute ar= bitrary OS commands via the text or expression parameters due to unsafe she=
    ll command construction in the processing pipeline.</td>
    <td>2026-06-25</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8592" target=3D"= _blank" rel=3D"noopener">CVE-2026-8592</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect Ping Plugin</td>
    <td>OS Command Injection vulnerability in the ping action of Rapid7 Insight= Connect Ping Plugin on Linux allows remote attackers to execute arbitrary O=
    S commands via the host parameter due to insufficient input validation when=
    constructing shell commands.</td>
    <td>2026-06-25</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8660" target=3D"= _blank" rel=3D"noopener">CVE-2026-8660</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect Sed Plugin</td>
    <td>OS Command Injection vulnerability in Rapid7 InsightConnect Sed Plugin =
    on Linux allows authenticated attackers to execute arbitrary OS commands vi=
    a the expression parameter due to insufficient input validation.</td> <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9155" target=3D"= _blank" rel=3D"noopener">CVE-2026-9155</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect Sed Plugin</td> <td>Arbitrary File Write vulnerability in Rapid7 InsightConnect Sed Plugin =
    on Linux allows authenticated attackers to write attacker-controlled conten=
    t to arbitrary file paths via the expression parameter.</td> <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9154" target=3D"= _blank" rel=3D"noopener">CVE-2026-9154</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect TR Plugin</td>
    <td>OS Command Injection vulnerability in the TR action of Rapid7 InsightCo= nnect Translate=C2=A0Plugin on Linux allows remote attackers to execute arb= itrary OS commands via the text or expression parameters due to insufficien=
    t input sanitization in shell command construction.</td>
    <td>2026-06-25</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8665" target=3D"= _blank" rel=3D"noopener">CVE-2026-8665</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect Traceroute Plugin</td> <td>OS Command Injection vulnerability in the traceroute action of Rapid7 I= nsightConnect Traceroute Plugin on Linux allows remote attackers to execute=
    arbitrary OS commands via the host, port, max_ttl, count, or time_out requ= est parameters due to insufficient input validation when constructing shell=
    commands.</td>
    <td>2026-06-25</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8666" target=3D"= _blank" rel=3D"noopener">CVE-2026-8666</a></td>
    </tr>

    <td class=3D"vendor-product">rasta-mouse--pwnlift</td>
    <td>pwnlift before d7a9544, in a privileged deployment, contains a symlink = following vulnerability in the upload handler in Components/Pages/Home.razo= r.</td>
    <td>2026-06-23</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56815" target=3D= "_blank" rel=3D"noopener">CVE-2026-56815</a></td>
    </tr>

    <td class=3D"vendor-product">rclone--rclone</td>
    <td>Rclone is a command-line program to sync files and directories to and f= rom different cloud storage providers. From 1.46.0 until 1.74.3, rclone rcd=
    --rc-serve accepts unauthenticated GET and HEAD requests to paths of the f= orm: /[remote:path]/object. The remote value is parsed from the URL and pas= sed to normal backend initialization. Inline remote configuration can set b= ackend options that execute local commands during initialization. As a resu= lt, a single unauthenticated GET or HEAD request can execute a command as t=
    he rclone process user. This vulnerability is fixed in 1.74.3.</td> <td>2026-06-24</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49980" target=3D= "_blank" rel=3D"noopener">CVE-2026-49980</a></td>
    </tr>

    <td class=3D"vendor-product">RealMag777--FOX</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in FOX &lt;=3D 1.4.8 version= s.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57319" target=3D= "_blank" rel=3D"noopener">CVE-2026-57319</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Ansible Automation Platform 2=
    .5 for RHEL 8</td>
    <td>A missing authorization vulnerability was found in the Event-Driven Ans= ible (EDA) websocket API. The /api/eda/ws/ansible-rulebook endpoint does no=
    t verify user permissions when processing Worker messages. Any authenticate=
    d user can send a forged message with an arbitrary activation_id to receive=
    plaintext credentials associated with that activation, including OAuth tok= ens, vault passwords, and SSH keys.</td>
    <td>2026-06-23</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11807" target=3D= "_blank" rel=3D"noopener">CVE-2026-11807</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Apicurio Registry 3<=

    <td>A flaw was found in Apicurio Registry. The ContentTypeUtil.isParsableXm= l() method creates a SAXParserFactory without enabling secure processing fe= atures or disabling external entity resolution. An attacker with artifact-w= rite permission (or unauthenticated when the registry runs with default con= figuration) can upload a crafted XML document to trigger blind server-side = request forgery (SSRF) via external DTD/entity fetch, or cause denial of se= rvice via entity expansion.</td>
    <td>2026-06-25</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12975" target=3D= "_blank" rel=3D"noopener">CVE-2026-12975</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Apicurio Registry 3<=

    <td>A flaw was found in Apicurio Registry. The WSDLReaderAccessor creates a=
    wsdl4j WSDLReader without disabling the javax.wsdl.importDocuments feature=
    . When the VALIDITY rule is set to FULL, an attacker with Developer-role ac= cess can upload a WSDL document containing attacker-controlled import locat= ions, causing the registry to issue HTTP requests to arbitrary internal URL=
    s (server-side request forgery).</td>
    <td>2026-06-25</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12992" target=3D= "_blank" rel=3D"noopener">CVE-2026-12992</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Keycloak 26.4</td>
    <td>A flaw was found in Keycloak Policy Enforcer. This vulnerability allows=
    any authenticated user to bypass all authorization policies, including rol=
    e, scope, and User-Managed Access (UMA) permission checks. By including the=
    configured access-denied page path within a request URL, either as a path = segment or a query parameter, an attacker can gain unauthorized access to p= rotected resources.</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9800" target=3D"= _blank" rel=3D"noopener">CVE-2026-9800</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Keycloak 26.4</td>
    <td>A flaw was found in Keycloak. A remote attacker with administrative pri= vileges, specifically those with `manage-client` permission or access to cl= ient registration endpoints, could bypass client Uniform Resource Identifie=
    r (URI) validation. This is achieved by registering a malicious client with=
    a specially crafted redirect URI using a case-insensitive `javascript:` or=
    `data:` scheme. This Cross-Site Scripting (XSS) vulnerability allows for a= rbitrary code execution in the Keycloak origin when a victim clicks the cra= fted link, such as in the logout flow or the Admin Console.</td> <td>2026-06-25</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9086" target=3D"= _blank" rel=3D"noopener">CVE-2026-9086</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Keycloak 26.4</td>
    <td>A flaw was found in Keycloak. A missing authorization check in the Grou= pResource.addChild() endpoint within the Admin REST API allows an authentic= ated user with limited administrative privileges to reparent any existing g= roup. When Fine-Grained Admin Permissions v2 (FGAPv2) is enabled, an attack=
    er with management rights over a single low-privilege group can reparent a = highly privileged group (such as one possessing the realm-admin role) under=
    their managed group. Because group permissions follow a hierarchical struc= ture, this action unauthorizedly grants the attacker management and passwor= d-reset capabilities over the members of the targeted privileged group. An = attacker can exploit this to reset an administrator's password, compromise = the account, and achieve a full realm takeover, leading to a complete compr= omise of confidentiality, integrity, and availability.</td>
    <td>2026-06-25</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9099" target=3D"= _blank" rel=3D"noopener">CVE-2026-9099</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Keycloak 26.6</td>
    <td>A flaw was found in Keycloak. This JWT algorithm confusion vulnerabilit=
    y in the JWT Authorization Grant flow allows an attacker with valid client = credentials to bypass signature verification. By forging an assertion, the = attacker can create unauthorized access tokens. This enables the attacker t=
    o impersonate any federated user linked to the affected Identity Provider, = leading to unauthorized access and potential privilege escalation.</td> <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11800" target=3D= "_blank" rel=3D"noopener">CVE-2026-11800</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat OpenShift Container Platform = 4</td>
    <td>A flaw was found in the Windows Machine Config Operator (WMCO) for Red = Hat OpenShift Container Platform. The WICD CSR auto-approver validates that=
    a Certificate Signing Request contains the organization system:wicd-nodes = but does not reject additional organization values such as system:masters. =
    A compromised Windows worker node that holds WICD credentials can submit a = CSR that is auto-approved and signed by the cluster, yielding a client cert= ificate that grants cluster-administrator privileges and enabling full clus= ter takeover.</td>
    <td>2026-06-22</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54099" target=3D= "_blank" rel=3D"noopener">CVE-2026-54099</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat OpenShift Container Platform = 4</td>
    <td>A flaw was found in the Windows Machine Config Operator (WMCO) for Red = Hat OpenShift Container Platform. WMCO establishes SSH connections to Windo=
    ws worker nodes without verifying the remote server host key. An adjacent-n= etwork attacker who can intercept or redirect WMCO's SSH session can captur=
    e WICD and kubelet bootstrap credentials transferred during node configurat= ion, enabling compromise of Windows node identities in the cluster.</td> <td>2026-06-22</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54100" target=3D= "_blank" rel=3D"noopener">CVE-2026-54100</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat OpenShift Virtualization 4</t=

    <td>A flaw was found in KubeVirt's migration proxy. When spec.configuration= .migrations.disableTLS is set to true on the KubeVirt custom resource, the = target virt-handler binds a plain TCP listener on all interfaces (0.0.0.0/:=
    :) on a random port with no authentication, peer allow-list, or handshake t= oken. This listener proxies directly into the target virt-launcher's virtqe= mud control socket. An attacker with a running pod on the cluster network c=
    an connect to this listener and issue unfiltered libvirt RPC commands again=
    st another tenant's virtual machine, including reading VM memory and config= uration, modifying VM state via QMP, or destroying the VM. The bind address=
    is unconditionally 0.0.0.0 - configuring a dedicated migration network via=
    migrations.network only changes the advertised migration IP, not the liste= ner bind address, so the port remains reachable on the pod network even whe=
    n a dedicated migration network is configured. The API documentation descri= bes disableTLS as removing "the additional layer of live migration encrypti= on" without disclosing that it also removes all mutual authentication.</td> <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13325" target=3D= "_blank" rel=3D"noopener">CVE-2026-13325</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat OpenShift Virtualization 4</t=

    <td>A flaw was found in KubeVirt's safepath package used by virt-handler. T=
    he OpenAtNoFollow function uses O_PATH|O_NOFOLLOW to obtain a file descript=
    or to a path leaf, but downstream operations resolve the path via /proc/sel= f/fd/N using link-following syscalls. When the leaf is a symlink, the kerne=
    l dereferences it, defeating the intended no-follow protection. An attacker=
    with access to a virt-launcher pod can exploit this to redirect virt-handl= er's IPC socket connections, including the notify socket used for VM domain=
    lifecycle events. By hijacking this socket, the attacker can inject arbitr= ary domain events into virt-handler, causing it to take incorrect lifecycle=
    actions, corrupt VM state in the Kubernetes API, or crash - resulting in s= ustained denial of VM management services for all virtual machines on the a= ffected node. Additionally, the same symlink following flaw allows virt-han= dler to apply file ownership or permission changes to unintended host paths= .</td>
    <td>2026-06-24</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13201" target=3D= "_blank" rel=3D"noopener">CVE-2026-13201</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Satellite 6.19</td>
    <td>A flaw was found in the foreman-mcp-server. A session management vulner= ability in the MCP Server allows unauthenticated attackers to hijack active=
    administrative sessions due to an improper cache of authenticated client c= onnections, by trusting a non-secret session ID without re-validating authe= ntication tokens and by logging all newly created session IDs to standard l= ogs. This issue can result in privilege escalation and infrastructure-wide = code execution.</td>
    <td>2026-06-23</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12112" target=3D= "_blank" rel=3D"noopener">CVE-2026-12112</a></td>
    </tr>

    <td class=3D"vendor-product">rickknowles--Winstone Servlet Container</td> <td>Winstone Servlet Engine through 0.9.10 contains a path traversal vulner= ability that allows unauthenticated attackers to read arbitrary files by se= nding HTTP GET requests with dot-dot-slash sequences that are not sanitized=
    when serving static files from the configured webroot. Attackers can trave= rse outside the webroot directory using traversal-prefixed paths in a singl=
    e HTTP request to read any file accessible to the servlet engine process, i= ncluding sensitive system files when the service runs with elevated privile= ges.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56122" target=3D= "_blank" rel=3D"noopener">CVE-2026-56122</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and = 7.10.11, Rocket.Chat's CAS login handler forwards the client-supplied optio= ns.cas.credentialToken value straight into a MongoDB findOne({_id: ...}) qu= ery without any runtime type check. TypeScript's string parameter annotatio=
    n is erased at runtime, so an unauthenticated attacker can substitute a Mon= goDB query operator ({"$gt": ""}, {"$ne": null}, etc.) for what the server = expects to be an opaque ticket string. The injected operator matches the fi= rst unexpired document in the credential_tokens collection, bypassing the C=
    AS ticket check entirely. When any legitimate CAS or SAML SSO login is in f= light, the attacker's next DDP login call matches the same credential-token=
    row via the NoSQL operator and is issued a full Meteor auth token (userId =
    + token) bound to the victim. The token is immediately usable against the c= omplete REST and DDP surface as that user. If the victim is an administrato=
    r, this escalates to full instance compromise via Apps-Engine app install. = This vulnerability is fixed in 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.= 13.7, and 7.10.11.</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45688" target=3D= "_blank" rel=3D"noopener">CVE-2026-45688</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and = 7.10.11, an unauthenticated network attacker obtains a valid Rocket.Chat OA= uth access token for an arbitrary user by sending a single HTTP POST with M= ongoDB query operators to /oauth/token. The Rocket.Chat OAuth2 server does = not validate that grant parameters are strings before forwarding them to fi= ndOne({...}) against the oauth_apps and oauth_access_tokens collections, so=
    an attacker substitutes {"$ne": null} for client_id, client_secret, and re= fresh_token and receives a freshly minted {access_token, refresh_token} pai=
    r bound to whichever user's refresh token Mongo returned first. The resulti=
    ng access token is a first-class bearer credential against the full /api/v1=
    /* surface as that user. By iterating with $nin / $regex operators the atta= cker walks the entire oauth_access_tokens collection, collecting one fresh = access token per user per request. If any matched token belongs to an admin=
    , the stolen bearer gives full admin API access (including Apps-Engine app = installation, i.e. server-side code execution). No account, credentials, us= erId, or prior interaction with the instance are required. This vulnerabili=
    ty is fixed in 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.1= 1.</td>
    <td>2026-06-24</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45689" target=3D= "_blank" rel=3D"noopener">CVE-2026-45689</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and = 7.10.11, Rocket.Chat's sendFileMessage DDP method passes the entire attacke= r-supplied file object into Uploads.updateFileComplete, which merges it dir= ectly into a MongoDB $set update via Object.assign. There is no allow-list =
    of writable fields. An attacker can therefore rewrite any column on their o=
    wn upload record, notably store and the store-specific path fields. This vu= lnerability is fixed in 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, a=
    nd 7.10.11.</td>
    <td>2026-06-24</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45687" target=3D= "_blank" rel=3D"noopener">CVE-2026-45687</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13,=
    the POST /api/v1/fingerprint REST endpoint enforces authentication (authRe= quired: true) but performs no authorization check. Any authenticated user -=
    including a standard user role account - can call this endpoint with {"set= DeploymentAs": "new-workspace"} to permanently deregister the workspace fro=
    m Rocket.Chat Cloud. This wipes all cloud credentials, removes the workspac=
    e license, breaks push notifications for all users, and requires manual re-= registration to recover. This vulnerability is fixed in 8.5.1, 8.4.4, 8.3.6=
    , 8.2.6, 8.1.6, 8.0.7, and 7.10.13.</td>
    <td>2026-06-24</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55762" target=3D= "_blank" rel=3D"noopener">CVE-2026-55762</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13,=
    Rocket.Chat's Apple Sign-In handler verifies JWT signatures but skips clai=
    ms validation. Any Apple-signed JWT with a non-empty iss is accepted regard= less of aud, exp, nbf, or nonce. An attacker who obtains a target user's Ap= ple identity token (from server logs, an intercepted sign-in flow, or anoth=
    er application sharing the same Apple developer team) can replay it to auth= enticate as that user, with no expiration on the replay window. This vulner= ability is fixed in 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13.<=

    <td>2026-06-24</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55759" target=3D= "_blank" rel=3D"noopener">CVE-2026-55759</a></td>
    </tr>

    <td class=3D"vendor-product">Royal Plugins--Royal MCP</td>
    <td>Missing Authorization vulnerability in Royal Plugins Royal MCP allows E= xploiting Incorrectly Configured Access Control Security Levels. This issue=
    affects Royal MCP: from n/a through 1.4.25.</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54842" target=3D= "_blank" rel=3D"noopener">CVE-2026-54842</a></td>
    </tr>

    <td class=3D"vendor-product">rtk-ai--rtk</td>
    <td>rtk filters and compresses command outputs before they reach your LLM c= ontext. Prior to 0.42.2, the permission splitter did not conservatively spl=
    it or reject several shell constructs that Bash treats as command execution=
    boundaries or nested execution. As a result, a command beginning with an a= llowed prefix such as git could hide a second command behind one of these c= onstructs. rtk rewrite returned exit code 0, causing the Claude hook to emi=
    t permissionDecision: "allow". The rewritten command still contained the hi= dden command, so it ran without the user confirmation or denial that the pe= rmission rules were intended to enforce. This vulnerability is fixed in 0.4= 2.2.</td>
    <td>2026-06-23</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54555" target=3D= "_blank" rel=3D"noopener">CVE-2026-54555</a></td>
    </tr>

    <td class=3D"vendor-product">Rustaurius--Five Star Restaurant Menu</td> <td>Unauthenticated Broken Access Control in Five Star Restaurant Menu &lt;= =3D 2.5.2 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54835" target=3D= "_blank" rel=3D"noopener">CVE-2026-54835</a></td>
    </tr>

    <td class=3D"vendor-product">RustDesk--RustDesk</td>
    <td>RustDesk gates incoming control messages on per-capability flags rather=
    than on the session's authorized connection type, and a file-transfer sess= ion does not clear those flags. A peer holding only a valid FileTransfer au= thorization can inject keyboard and mouse input and reach the unguarded scr= eenshot and display-capture handlers, acting outside its granted scope.</td=

    <td>2026-06-28</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58056" target=3D= "_blank" rel=3D"noopener">CVE-2026-58056</a></td>
    </tr>

    <td class=3D"vendor-product">rustfs--rustfs</td>
    <td>RustFS is a distributed object storage system built in Rust. In 1.0.0-b= eta.4, authenticated users with only PutObject permission on their own buck=
    et can exploit a path traversal vulnerability in the Snowball auto-extract = feature to write arbitrary objects into other users' buckets, completely br= eaking multi-tenant isolation. The vulnerability chains three flaws: No ../=
    sanitization in tar entry key normalization; IAM wildcard matching uses ra=
    w (uncleaned) paths; and Filesystem path cleaning resolves ../ across bucke=
    t boundaries.</td>
    <td>2026-06-26</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49991" target=3D= "_blank" rel=3D"noopener">CVE-2026-49991</a></td>
    </tr>

    <td class=3D"vendor-product">rustfs--rustfs</td>
    <td>RustFS is a distributed object storage system built in Rust. From 1.0.0= -alpha.1 until 1.0.0-beta.9, RustFS contains an authorization bypass in the=
    bucket replication admin API. The ListRemoteTargetHandler handler for list= ing remote replication targets only checks whether request credentials exis=
    t, but does not verify that the caller has replication or administrator per= missions. As a result, an authenticated user with no effective bucket or ad= min permissions can list remote replication target configuration for a buck= et. Because the returned BucketTarget objects include remote target credent= ials, this can disclose replication access keys and secret keys. This vulne= rability is fixed in 1.0.0-beta.9.</td>
    <td>2026-06-26</td>
    <td>8.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55188" target=3D= "_blank" rel=3D"noopener">CVE-2026-55188</a></td>
    </tr>

    <td class=3D"vendor-product">rustfs--rustfs</td>
    <td>RustFS is a distributed object storage system built in Rust. From 1.0.0= -alpha.1 until 1.0.0-beta.9, when the FTP frontend is enabled, the FTP read=
    and probe handlers dispatch directly to the storage backend without ever c= alling the IAM authorization function that the FTP write/list handlers (and=
    the entire HTTP S3 path) use. As a result, any user who can authenticate t=
    o the FTP listener - including a user whose IAM policy contains an explicit=
    Deny on s3:GetObject - can read (RETR) and stat (SIZE/MDTM) any object in = any bucket, and probe any bucket (CWD), completely regardless of their IAM = policy. This vulnerability is fixed in 1.0.0-beta.9.</td>
    <td>2026-06-26</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55189" target=3D= "_blank" rel=3D"noopener">CVE-2026-55189</a></td>
    </tr>

    <td class=3D"vendor-product">Rymera Web Co--WC Vendors Marketplace</td> <td>Subscriber SQL Injection in WC Vendors Marketplace &lt;=3D 2.6.8 versio= ns.</td>
    <td>2026-06-25</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54838" target=3D= "_blank" rel=3D"noopener">CVE-2026-54838</a></td>
    </tr>

    <td class=3D"vendor-product">Saad Iqbal--APIExperts Square for WooCommerce<=

    <td>Insertion of Sensitive Information Into Sent Data vulnerability in Saad=
    Iqbal APIExperts Square for WooCommerce allows Retrieve Embedded Sensitive=
    Data. This issue affects APIExperts Square for WooCommerce: from n/a throu=
    gh 4.7.3.</td>
    <td>2026-06-25</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54848" target=3D= "_blank" rel=3D"noopener">CVE-2026-54848</a></td>
    </tr>

    <td class=3D"vendor-product">sahlberg--libnfs</td>
    <td>libnfs through 6.0.2 before 935b8db has an xid integer underflow in REA= D_IOVEC in rpc_read_from_socket in lib/socket.c during a connection to a cr= afted NFS server, when the expected pdu size exceeds the absolute pdu size = from the xid/record-marker.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57918" target=3D= "_blank" rel=3D"noopener">CVE-2026-57918</a></td>
    </tr>

    <td class=3D"vendor-product">SALESmanago--SALESmanago &amp; Leadoo</td> <td>Subscriber SQL Injection in SALESmanago &amp; Leadoo &lt;=3D 3.11.2 ver= sions.</td>
    <td>2026-06-25</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54822" target=3D= "_blank" rel=3D"noopener">CVE-2026-54822</a></td>
    </tr>

    <td class=3D"vendor-product">samuelclay--NewsBlur</td>
    <td>NewsBlur before version 14.5.0 contains a server-side request forgery v= ulnerability in the add_url endpoint that allows authenticated users to mak=
    e arbitrary server requests to internal networks by failing to filter priva=
    te IP addresses. Attackers can exploit this to access localhost services an=
    d cloud metadata endpoints, enabling internal network scanning and sensitiv=
    e data exfiltration.</td>
    <td>2026-06-25</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56771" target=3D= "_blank" rel=3D"noopener">CVE-2026-56771</a></td>
    </tr>

    <td class=3D"vendor-product">schwehr--libais</td>
    <td>libais through 0.15 VdmStream::AddLine uses an unchecked sentinel value=
    as a vector index when processing AIS sentences with empty or out-of-range=
    sequential message IDs. Remote attackers can crash services or vessel syst= ems by sending crafted AIVDM sentences over VHF marine radio or IP feeds, c= ausing out-of-bounds memory access and potential corruption.</td> <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56770" target=3D= "_blank" rel=3D"noopener">CVE-2026-56770</a></td>
    </tr>

    <td class=3D"vendor-product">Shenzhen Cudy Technology Co., Ltd.--LT300 3.0<=

    <td>Cudy LT300 3.0 running firmware prior to version 2.5.12 contains an OS = command injection vulnerability that allows authenticated attackers to exec= ute arbitrary commands by injecting shell metacharacters into the cbid.syst= em.ntp.current POST parameter in the system time configuration interface. A= ttackers can submit malicious payloads through the NTP settings endpoint to=
    achieve remote code execution on the underlying system.</td> <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-32833" target=3D= "_blank" rel=3D"noopener">CVE-2026-32833</a></td>
    </tr>

    <td class=3D"vendor-product">Shenzhen i365-Tech Co. Ltd.--Setracker2 Parent=
    al Control App (Android) package com.tgelec.setracker</td>
    <td>Setracker2 Android Companion App com.tgelec.setracker versions 3.1.5 an=
    d prior only require the password hash when authenticating with backend ser= vices from the client. This could allow an attacker, who knows the hash, to=
    authenticate and gain full access.</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9222" target=3D"= _blank" rel=3D"noopener">CVE-2026-9222</a></td>
    </tr>

    <td class=3D"vendor-product">Shenzhen i365-Tech Co. Ltd.--Setracker2 Parent=
    al Control App (Android) package com.tgelec.setracker</td>
    <td>Setracker2 Android Companion App com.tgelec.setracker versions 3.1.5 an=
    d prior encrypts requests between the watch and its backend with static har= dcoded AES keys and initialization vectors. This allows an attacker to decr= ypt Setracker2 watch traffic.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9220" target=3D"= _blank" rel=3D"noopener">CVE-2026-9220</a></td>
    </tr>

    <td class=3D"vendor-product">Shenzhen i365-Tech Co. Ltd.--Setracker2 Parent=
    al Control App (Android) package com.tgelec.setracker</td>
    <td>The Setracker2 Android Companion App (com.tgelec.setracker) versions 3.= 1.5 and earlier uses MD5 to generate a request signature for authenticating=
    communications between the mobile client and the backend REST API. Attacke=
    rs could potentially reverse the signature to recover the session ID. With = the session ID exposed, an attacker could impersonate the legitimate user a=
    nd issue authenticated API requests.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9221" target=3D"= _blank" rel=3D"noopener">CVE-2026-9221</a></td>
    </tr>

    <td class=3D"vendor-product">Significant-Gravitas--AutoGPT</td>
    <td>AutoGPT is a workflow automation platform for creating, deploying, and = managing continuous artificial intelligence agents. Prior to 0.6.52, an aut= henticated user can bypass the SSRF / private-IP protections in SendWebRequ= estBlock and reach internal network services. _is_ip_blocked() in backend/b= ackend/util/request.py does not normalize IPv4-mapped IPv6 addresses before=
    checking resolved IPs against the blocked IPv4 ranges, and does not block = special-use ranges such as 100.64.0.0/10 (CGNAT, RFC 6598). A hostname that=
    resolves to an IPv4-mapped IPv6 address therefore passes validation and th=
    e request reaches the embedded internal IPv4 endpoint. This affects all Aut= oGPT Platform deployments. This vulnerability is fixed in 0.6.52.</td> <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56663" target=3D= "_blank" rel=3D"noopener">CVE-2026-56663</a></td>
    </tr>

    <td class=3D"vendor-product">Significant-Gravitas--AutoGPT</td>
    <td>AutoGPT is a workflow automation platform for creating, deploying, and = managing continuous artificial intelligence agents. In versions prior to 0.= 6.52, the Fill Text Template block is vulnerable to a Denial of Service (Do=
    S) attack. While the backend implements a SandboxedEnvironment to prevent u= nauthorized attribute access (e.g., blocking __class__), it fails to limit = the computational complexity or execution time of the expressions. An attac= ker can input computationally expensive Python/Jinja2 expressions that cons= ume the server's CPU and memory, leading to a complete system hang or crash=
    . In multi-tenant or self-hosted environments, this results in a complete s= ervice outage and "noisy neighbor" effects that require manual administrati=
    ve intervention to recover. This issue has been fixed in version 0.6.52.</t=

    <td>2026-06-24</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-33235" target=3D= "_blank" rel=3D"noopener">CVE-2026-33235</a></td>
    </tr>

    <td class=3D"vendor-product">Site Building with Toolset--Toolset Forms</td> <td>Unauthenticated Insecure Direct Object References (IDOR) in Toolset For=
    ms &lt;=3D 2.6.24 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56069" target=3D= "_blank" rel=3D"noopener">CVE-2026-56069</a></td>
    </tr>

    <td class=3D"vendor-product">siyuan-note--siyuan</td>
    <td>SiYuan is an open-source personal knowledge management system. Prior to=
    3.7.0, SiYuan contains a stored cross-site scripting (XSS) vulnerability i=
    n the Attribute View (database) asset cell renderer that escalates to remot=
    e code execution (RCE) in the Electron desktop client. This vulnerability i=
    s fixed in 3.7.0.</td>
    <td>2026-06-24</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50551" target=3D= "_blank" rel=3D"noopener">CVE-2026-50551</a></td>
    </tr>

    <td class=3D"vendor-product">siyuan-note--siyuan</td>
    <td>SiYuan is an open-source personal knowledge management system. Prior to=
    3.7.0, CSS snippet body containing &lt;/style&gt; breaks out of its surrou= nding &lt;style&gt; tag when renderSnippet() interpolates it via insertAdja= centHTML. A payload like runs arbitrary JavaScript in the renderer. On Elec= tron desktop builds the renderer runs with nodeIntegration:true, so require= ('child_process') is reachable from the injected handler and the XSS chains=
    to host RCE. Snippets sync via the workspace repository, so an attacker wi=
    th write access to any synced workspace plants the payload once and it fire=
    s on every device that pulls. The bug also bypasses the user's enabledCSS /=
    enabledJS separation. A user who turned enabledJS off was making a deliber= ate call not to run untrusted JavaScript; the CSS path runs it anyway. This=
    vulnerability is fixed in 3.7.0.</td>
    <td>2026-06-24</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54067" target=3D= "_blank" rel=3D"noopener">CVE-2026-54067</a></td>
    </tr>

    <td class=3D"vendor-product">siyuan-note--siyuan</td>
    <td>SiYuan is an open-source personal knowledge management system. Prior to=
    3.7.0, the attribute-view (database) cell renderer genAVValueHTML interpol= ates cell content raw in four of its branches: text, url, phone, and mAsset=
    . A cell value like &lt;/textarea&gt;&lt;img src=3Dx onerror=3D"..."&gt; or=
    "&gt;&lt;img src=3Dx onerror=3D"..."&gt; breaks out of its surrounding tag=
    and runs arbitrary JavaScript in the renderer when the victim opens the bl= ock-attribute panel. On Electron desktop the renderer runs with nodeIntegra= tion:true, so the XSS chains to host RCE via require('child_process'). AV f= iles live under the workspace and ride normal sync, so an attacker with wri=
    te access to any synced workspace plants the payload once and it fires on e= very device that opens a panel containing that row.he kernel doesn't escape=
    on the way in either, so the malicious cell persists byte-for-byte. There'=
    s no equivalent of the html.EscapeAttrVal call that protects block IAL attr= ibutes at kernel/model/blockial.go:261. This vulnerability is fixed in 3.7.= 0.</td>
    <td>2026-06-24</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54158" target=3D= "_blank" rel=3D"noopener">CVE-2026-54158</a></td>
    </tr>

    <td class=3D"vendor-product">siyuan-note--siyuan</td>
    <td>SiYuan is an open-source personal knowledge management system. Prior to=
    3.7.0, it does not escape the untrusted fields (name, version, author, des= cription) when they are serialized into the data-obj HTML attribute of each=
    marketplace card. Because the attribute is single-quoted and the value is = produced with JSON.stringify() (which does not escape ', &lt;, or &gt;), a = package whose name contains a single quote breaks out of the attribute and = injects arbitrary HTML. In the desktop client the main BrowserWindow runs w= ith nodeIntegration: true, contextIsolation: false, so the injected markup = escalates from DOM XSS to arbitrary OS command execution. This is the same = root cause and same impact as the original advisory, reached through a sibl= ing sink the patch did not cover. This vulnerability is fixed in 3.7.0.</td=

    <td>2026-06-24</td>
    <td>9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55570" target=3D= "_blank" rel=3D"noopener">CVE-2026-55570</a></td>
    </tr>

    <td class=3D"vendor-product">siyuan-note--siyuan</td>
    <td>SiYuan is an open-source personal knowledge management system. Prior to=
    3.7.0, the patch for CVE-2026-41894 ("Path Traversal via Double URL Encodi= ng") sanitized the /export/ route but the identical root cause remains in t=
    he /assets/*path route. In publish mode (anonymous read-only HTTP endpoint,=
    default port 6808), an unauthenticated remote attacker can read arbitrary = files inside WorkspaceDir - including conf/conf.json (which contains the Ac= cessAuthCode SHA256 hash, API token, and sync keys), temp/siyuan.db, temp/b= locktree.db, and siyuan.log - by double-URL-encoding .. segments. This vuln= erability is fixed in 3.7.0.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54066" target=3D= "_blank" rel=3D"noopener">CVE-2026-54066</a></td>
    </tr>

    <td class=3D"vendor-product">siyuan-note--siyuan</td>
    <td>SiYuan is an open-source personal knowledge management system. Prior to=
    3.7.0, renderPackageREADME in kernel/bazaar/readme.go renders a Bazaar pac= kage README from Markdown to HTML with the lute engine and SetSanitize(true=
    ). The lute sanitizer is an event-handler blocklist: allowAttr rejects only=
    attribute names present in a fixed eventAttrs map copied from the w3school=
    s legacy handler list. That map omits modern event handlers. onpointerover,=
    onpointerdown, onauxclick, onbeforetoggle, onfocusin, onanimationstart, an=
    d ontransitionend are not in the list, so the sanitizer passes them through=
    verbatim on any tag. The frontend assigns the rendered HTML to mdElement.i= nnerHTML in app/src/config/bazaar.ts with no client-side DOMPurify on this = path, into a normal element in the main document (no iframe, no sandbox). T=
    he kernel sends no Content-Security-Policy, X-Frame-Options, or X-Content-T= ype-Options header on any response, so an inline handler runs when its even=
    t fires. The README is rendered when an Administrator opens a package in Se= ttings =C3=A2=E2=80=A0=E2=80=99 Marketplace, after the one-time marketplace=
    trust consent. Install is not required. Result: a third-party Bazaar packa=
    ge author runs JavaScript in the Administrator's authenticated SiYuan origi=
    n when the Administrator views and interacts with the package listing, and = gains full control of the workspace. This vulnerability is fixed in 3.7.0.<=

    <td>2026-06-24</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54070" target=3D= "_blank" rel=3D"noopener">CVE-2026-54070</a></td>
    </tr>

    <td class=3D"vendor-product">socat--socat</td>
    <td>socat versions 1.8.0.0 through 1.8.1.1 contain a heap-based buffer over= flow vulnerability that allows a malicious SOCKS5 proxy server to overwrite=
    adjacent heap memory by exploiting a sign-extension flaw in the DOMAINNAME=
    reply parser. During connection setup, the domain name length byte is read=
    through a signed char field causing a negative bytes_to_read value that is=
    implicitly converted to size_t, resulting in an unbounded heap write into = the 262-byte reply buffer with attacker-controlled size and content.</td> <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56123" target=3D= "_blank" rel=3D"noopener">CVE-2026-56123</a></td>
    </tr>

    <td class=3D"vendor-product">SourceCodester--Class and Exam Timetabling Sys= tem</td>
    <td>A vulnerability was found in SourceCodester Class and Exam Timetabling = System 1.0. This affects an unknown function of the file /preview.php. Perf= orming a manipulation of the argument course_year_section results in sql in= jection. The attack can be initiated remotely. The exploit has been made pu= blic and could be used.</td>
    <td>2026-06-28</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13485" target=3D= "_blank" rel=3D"noopener">CVE-2026-13485</a></td>
    </tr>

    <td class=3D"vendor-product">SourceCodester--Class and Exam Timetabling Sys= tem</td>
    <td>A vulnerability was determined in SourceCodester Class and Exam Timetab= ling System 1.0/6.php. This impacts an unknown function of the file /previe= w6.php. Executing a manipulation of the argument course_year_section can le=
    ad to sql injection. The attack can be launched remotely. The exploit has b= een publicly disclosed and may be utilized.</td>
    <td>2026-06-28</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13486" target=3D= "_blank" rel=3D"noopener">CVE-2026-13486</a></td>
    </tr>

    <td class=3D"vendor-product">SourceCodester--Class and Exam Timetabling Sys= tem</td>
    <td>A vulnerability was identified in SourceCodester Class and Exam Timetab= ling System 1.0. Affected is an unknown function of the file /archive.php. = The manipulation of the argument sy leads to sql injection. The attack may =
    be initiated remotely. The exploit is publicly available and might be used.= </td>
    <td>2026-06-28</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13487" target=3D= "_blank" rel=3D"noopener">CVE-2026-13487</a></td>
    </tr>

    <td class=3D"vendor-product">SourceCodester--Class and Exam Timetabling Sys= tem</td>
    <td>A security flaw has been discovered in SourceCodester Class and Exam Ti= metabling System 1.0/7.php. Affected by this vulnerability is an unknown fu= nctionality of the file /preview7.php. The manipulation of the argument cou= rse_year_section results in sql injection. The attack may be launched remot= ely. The exploit has been released to the public and may be used for attack= s.</td>
    <td>2026-06-28</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13488" target=3D= "_blank" rel=3D"noopener">CVE-2026-13488</a></td>
    </tr>

    <td class=3D"vendor-product">Spring--Spring Statemachine</td>
    <td>Spring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Re= dis and ZooKeeper) deserialise persisted state-machine contexts without enf= orcing a class allowlist (CWE-502, deserialisation of untrusted data), whic=
    h can lead to remote code execution inside the application JVM. Affected ve= rsions: Spring Statemachine 4.0.0 through 4.0.1 Spring Statemachine 3.2.0 t= hrough 3.2.4</td>
    <td>2026-06-23</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41862" target=3D= "_blank" rel=3D"noopener">CVE-2026-41862</a></td>
    </tr>

    <td class=3D"vendor-product">Stranger Studios--Paid Memberships Pro - Add M= ember From Admin</td>
    <td>Unauthenticated Cross Site Request Forgery (CSRF) in Paid Memberships P=
    ro - Add Member From Admin &lt;=3D 0.7.2 versions.</td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57659" target=3D= "_blank" rel=3D"noopener">CVE-2026-57659</a></td>
    </tr>

    <td class=3D"vendor-product">style-dictionary--style-dictionary</td>
    <td>Style Dictionary, a build system for creating cross-platform styles, ha=
    s a prototype pollution vulnerability starting in version 4.3.0 and prior t=
    o version 5.4.4. Impact users have: direct usage of `convertTokenData(token=
    s, { output: 'object' });`; indirect usage, via using Expand API; and/or in= direct usage via SD's transform lifecycle. Impact is high for this when sty= le-dictionary is used as an integration in a NodeJS server application. Imp= act is moderate for when style-dictionary is used as an integration in a We=
    b application. Impact is low for most common cases where the user of style-= dictionary also maintains the tokens, and access is limited via read/write = access to the repository/workflows where it is used. A patch has been publi= shed in version `5.4.4`. The only known workaround is to sanitize token dat=
    a first. Whether using DTCG format or old Style Dictionary format, check th=
    e token data object recursively for any object keys that include `__proto__= `.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54639" target=3D= "_blank" rel=3D"noopener">CVE-2026-54639</a></td>
    </tr>

    <td class=3D"vendor-product">StylemixThemes--Motors</td>
    <td>Unauthenticated Broken Access Control in Motors &lt;=3D 1.4.109 version= s.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54828" target=3D= "_blank" rel=3D"noopener">CVE-2026-54828</a></td>
    </tr>

    <td class=3D"vendor-product">StylemixThemes--Splash - Sport Club WordPress = Theme for Basketball, Football, Hockey</td>
    <td>Contributor Local File Inclusion in Splash - Sport Club WordPress Theme=
    for Basketball, Football, Hockey &lt;=3D 4.4.3 versions.</td> <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-68063" target=3D= "_blank" rel=3D"noopener">CVE-2025-68063</a></td>
    </tr>

    <td class=3D"vendor-product">SureCart--SureCart</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in SureCart &lt;=3D 4.3.2 ve= rsions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57314" target=3D= "_blank" rel=3D"noopener">CVE-2026-57314</a></td>
    </tr>

    <td class=3D"vendor-product">Syed Balkhi--Intranet &amp; Private Site All-I= n-One Intranet</td>
    <td>Unauthenticated Broken Access Control in Intranet &amp;amp; Private Sit=
    e &amp;#8211; All-In-One Intranet &lt;=3D 1.8.1 versions.</td> <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54837" target=3D= "_blank" rel=3D"noopener">CVE-2026-54837</a></td>
    </tr>

    <td class=3D"vendor-product">TablePress--TablePress</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in TablePress &lt;=3D 3.3.1 = versions.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56051" target=3D= "_blank" rel=3D"noopener">CVE-2026-56051</a></td>
    </tr>

    <td class=3D"vendor-product">teableio--teable</td>
    <td>Teable's v2 REST API controller lacks @Permissions metadata on ORPC end= points, allowing any authenticated user to bypass authorization checks. Att= ackers can read table schemas, create tables, and modify or delete records = across bases and tables via endpoints like GET /api/v2/tables/get and POST = /api/v2/tables/updateRecords.</td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56773" target=3D= "_blank" rel=3D"noopener">CVE-2026-56773</a></td>
    </tr>

    <td class=3D"vendor-product">Templatespare--TemplateSpare</td> <td>Administrator Arbitrary File Upload in TemplateSpare &lt;=3D 4.2.0 vers= ions.</td>
    <td>2026-06-26</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57658" target=3D= "_blank" rel=3D"noopener">CVE-2026-57658</a></td>
    </tr>

    <td class=3D"vendor-product">tenable--Tenable Identity Exposure</td> <td>Tenable Identity Exposure contains multiple unauthenticated API endpoin=
    ts under /w/api/* that expose sensitive application configuration data incl= uding cleartext LDAP credentials, SAML configuration, user accounts, and di= rectory settings to unauthenticated remote attackers. Affected responses ar=
    e served with Cache-Control: public headers and without Vary: Cookie, allow= ing reverse proxies and CDNs to cache and serve sensitive data to unauthent= icated users even after authentication is applied.</td>
    <td>2026-06-23</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13007" target=3D= "_blank" rel=3D"noopener">CVE-2026-13007</a></td>
    </tr>

    <td class=3D"vendor-product">Tenda--JD12L</td>
    <td>A security vulnerability has been detected in Tenda JD12L 16.03.53.23. = Impacted is the function formSetPPTPServer of the file /goform/SetPptpServe= rCfg. Such manipulation of the argument startIp leads to stack-based buffer=
    overflow. The attack can be launched remotely. The exploit has been disclo= sed publicly and may be used.</td>
    <td>2026-06-28</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13515" target=3D= "_blank" rel=3D"noopener">CVE-2026-13515</a></td>
    </tr>

    <td class=3D"vendor-product">Tenda--JD12L</td>
    <td>A vulnerability was detected in Tenda JD12L 16.03.53.23. The affected e= lement is the function fromSetWifiGusetBasic of the file /goform/WifiGuestS= et. Performing a manipulation of the argument shareSpeed results in stack-b= ased buffer overflow. The attack may be initiated remotely. The exploit is = now public and may be used.</td>
    <td>2026-06-28</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13516" target=3D= "_blank" rel=3D"noopener">CVE-2026-13516</a></td>
    </tr>

    <td class=3D"vendor-product">ThemeCatcher--Quform</td>
    <td>Subscriber Arbitrary File Upload in Quform &lt;=3D 2.23.0 versions.</td=

    <td>2026-06-26</td>
    <td>9.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56058" target=3D= "_blank" rel=3D"noopener">CVE-2026-56058</a></td>
    </tr>

    <td class=3D"vendor-product">Themefic--Tourfic</td>
    <td>Subscriber SQL Injection in Tourfic &lt;=3D 2.22.5 versions.</td> <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56064" target=3D= "_blank" rel=3D"noopener">CVE-2026-56064</a></td>
    </tr>

    <td class=3D"vendor-product">themefic--Tourfic AI Powered Travel Booking, H= otel Booking &amp; Car Rental WordPress Plugin</td>
    <td>The Tourfic - AI Powered Travel Booking, Hotel Booking &amp; Car Rental=
    WordPress Plugin plugin for WordPress is vulnerable to generic SQL Injecti=
    on via the 'post_id' parameter in all versions up to, and including, 2.22.7=
    due to insufficient escaping on the user supplied parameter and lack of su= fficient preparation on the existing SQL query. This makes it possible for = unauthenticated attackers to append additional SQL queries into already exi= sting queries that can be used to extract sensitive information from the da= tabase. The AJAX handler is registered for unauthenticated users via wp_aja= x_nopriv_tf_room_availability, and the required nonce is emitted on the pub= lic single-hotel page template, allowing unauthenticated attackers to freel=
    y obtain a valid nonce and reach the vulnerable code path.</td> <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12937" target=3D= "_blank" rel=3D"noopener">CVE-2026-12937</a></td>
    </tr>

    <td class=3D"vendor-product">ThemeFusion--Fusion Builder</td>
    <td>Contributor Privilege Escalation in Fusion Builder &lt;=3D 3.15.4 versi= ons.</td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56008" target=3D= "_blank" rel=3D"noopener">CVE-2026-56008</a></td>
    </tr>

    <td class=3D"vendor-product">ThemeHunk--Advance Product Search</td> <td>Unauthenticated SQL Injection in Advance Product Search &lt;=3D 1.4.4 v= ersions.</td>
    <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56070" target=3D= "_blank" rel=3D"noopener">CVE-2026-56070</a></td>
    </tr>

    <td class=3D"vendor-product">themewant--Easy Elements for Elementor =E2=80=
    =9C Addons &amp; Website Templates</td>
    <td>Unauthenticated Privilege Escalation in Easy Elements for Elementor &am= p;#8211; Addons &amp;amp; Website Templates &lt;=3D 1.4.9 versions.</td> <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56028" target=3D= "_blank" rel=3D"noopener">CVE-2026-56028</a></td>
    </tr>

    <td class=3D"vendor-product">Tomdever--wpForo Forum</td>
    <td>Contributor SQL Injection in wpForo Forum &lt;=3D 3.0.9 versions.</td> <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57636" target=3D= "_blank" rel=3D"noopener">CVE-2026-57636</a></td>
    </tr>

    <td class=3D"vendor-product">tomojitakasu--RTKLIB</td>
    <td>RTKLIB through 2.4.3 contains an out-of-bounds write vulnerability in d= ecode_type1033 function that fails to clamp length counters to destination = buffer size, allowing up to 191-byte overflow into fixed 64-byte descriptor=
    fields. An attacker controlling an NTRIP or serial RTCM3 correction stream=
    can craft a valid CRC-bearing type-1033 message to corrupt adjacent rtcm_t=
    object members, potentially achieving arbitrary code execution or denial o=
    f service.</td>
    <td>2026-06-25</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56786" target=3D= "_blank" rel=3D"noopener">CVE-2026-56786</a></td>
    </tr>

    <td class=3D"vendor-product">ToolJet--ToolJet</td>
    <td>ToolJet is the open-source foundation am AI-native platform for buildin=
    g and deploying internal tools, workflows and AI agents. Prior to 3.20.178-= lts, there's an SSRF in the RestAPI data source component. The RestAPI data=
    source executes HTTP requests server-side, and its private IP filter only = checks the hostname string - not the resolved IP. DNS names like 169.254.16= 9.254.nip.io resolve to the Azure IMDS link-local address and bypass the fi= lter entirely. This allows any authenticated user (free tier) to steal Azur=
    e managed identity tokens for the AKS production cluster. This vulnerabilit=
    y is fixed in 3.20.178-lts.</td>
    <td>2026-06-25</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55412" target=3D= "_blank" rel=3D"noopener">CVE-2026-55412</a></td>
    </tr>

    <td class=3D"vendor-product">Traefik--Traefik</td>
    <td>Traefik before 2.10.5 and 3.0.0-beta4 is affected by a denial-of-servic=
    e vulnerability in HTTP/2 request handling inherited from the Go standard l= ibrary's HTTP/2 implementation (CVE-2023-44487 / CVE-2023-39325, the 'Rapid=
    Reset' technique). A remote attacker can rapidly create and cancel HTTP/2 = streams to exhaust server resources and cause service unavailability.</td> <td>2026-06-23</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2023-54365" target=3D= "_blank" rel=3D"noopener">CVE-2023-54365</a></td>
    </tr>

    <td class=3D"vendor-product">Tribulant Software--Newsletters</td> <td>newsletters_subscribers Broken Access Control in Newsletters &lt;=3D 4.=
    13 versions.</td>
    <td>2026-06-26</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57645" target=3D= "_blank" rel=3D"noopener">CVE-2026-57645</a></td>
    </tr>

    <td class=3D"vendor-product">Tribulant Software--Newsletters</td> <td>Unauthenticated Broken Access Control in Newsletters &lt;=3D 4.13 versi= ons.</td>
    <td>2026-06-26</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54840" target=3D= "_blank" rel=3D"noopener">CVE-2026-54840</a></td>
    </tr>

    <td class=3D"vendor-product">TryGhost--Ghost</td>
    <td>Ghost is a Node.js content management system. From until 6.37.0, when G= host is behind a shared caching layer that results in cached content being = shared between different visitors, an unauthenticated user could send an x-= ghost-preview header that altered the rendered frontend response. In affect=
    ed cache configurations, that response could be stored and served to subseq= uent visitors requesting the same page, allowing cache poisoning of request= -specific preview output. When running Ghost's frontend and admin panel on = the same domain this could be used to take over staff user accounts. When r= unning these on different domains staff accounts have no exposure. This vul= nerability is fixed in 6.37.0.</td>
    <td>2026-06-24</td>
    <td>9.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53943" target=3D= "_blank" rel=3D"noopener">CVE-2026-53943</a></td>
    </tr>

    <td class=3D"vendor-product">TryGhost--Ghost</td>
    <td>@tryghost/activitypub is Ghost's social/federation client app. Prior to=
    3.1.0, the ActivityPub client in Ghost was vulnerable to JavaScript inject= ion on posts shared by a maliciously customised ActivityPub server. This vu= lnerability is fixed in 3.1.0.</td>
    <td>2026-06-24</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53950" target=3D= "_blank" rel=3D"noopener">CVE-2026-53950</a></td>
    </tr>

    <td class=3D"vendor-product">twentyhq--twenty</td>
    <td>Twenty is an open-source CRM (customer relationship management) platfor=
    m. Prior to 2.9.0, Twenty was vulnerable to a cross-workspace insecure dire=
    ct object reference (IDOR) in the AI agent monitor's AgentTurnResolver, in = packages/twenty-server/src/engine/metadata-modules/ai/ai-agent-monitor/reso=
    lvers/agent-turn.resolver.ts. The agentTurns(agentId) query and the evalua= teAgentTurn(turnId) mutation looked up rows by agentId or id only; although=
    AgentTurnEntity has a workspaceId column, it was not included in the WHERE=
    clause, and the class-level guards only checked that the caller was authen= ticated in some workspace rather than that the requested object belonged to=
    it, with the same flaw present in agent-turn-grader.service.ts. As a resul=
    t, any authenticated user with the AI settings flag, a workspace owner by d= efault, could target any other workspace on the same instance given the vic= tim's agentId or turnId: agentTurns returned the victim's full chat history=
    including message parts such as raw chat text, tool calls, and tool output=
    s, while evaluateAgentTurn inserted an agentTurnEvaluation row with the vic= tim's workspaceId and fed the victim's turn into the default LLM. The agent=
    Id and turnId are non-guessable UUIDs but are exposed in the URL of the set= tings page. This issue is fixed in version 2.9.0.</td>
    <td>2026-06-24</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55583" target=3D= "_blank" rel=3D"noopener">CVE-2026-55583</a></td>
    </tr>

    <td class=3D"vendor-product">Tyche Softwares.--Abandoned Cart Pro for WooCo= mmerce</td>
    <td>Subscriber Privilege Escalation in Abandoned Cart Pro for WooCommerce &= lt;=3D 10.4.0 versions.</td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56010" target=3D= "_blank" rel=3D"noopener">CVE-2026-56010</a></td>
    </tr>

    <td class=3D"vendor-product">tychesoftwares--Print Invoice &amp; Delivery N= otes for WooCommerce</td>
    <td>Unauthenticated Sensitive Data Exposure in Print Invoice &amp; Delivery=
    Notes for WooCommerce &lt;=3D 7.1.1 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56060" target=3D= "_blank" rel=3D"noopener">CVE-2026-56060</a></td>
    </tr>

    <td class=3D"vendor-product">Ubuntu--Canonical ADSys</td>
    <td>An issue was discovered in Canonical ADSys upstream versions through v0= .16.2. During Active Directory Certificate Services (AD CS) certificate aut= o-enrollment via the vendored Samba client script (internal/policies/certif= icate/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py), ADSys utilizes a = plaintext HTTP connection (http://) instead of a secure HTTPS connection (h= ttps://) to request the CA certificate from the Active Directory Certificat=
    e Services server (GetCACert). An unauthenticated network attacker position=
    ed between the managed Ubuntu host and the configured AD CS CA hostname can=
    conduct a Man-in-the-Middle (MITM) attack. By intercepting the plaintext H= TTP request, the attacker can supply an arbitrary, attacker-controlled Root=
    CA certificate. Because the system automatically accepts this certificate = and registers it into the local system trust store via update-ca-certificat= es, this results in system-wide trust store poisoning. Consequently, TLS cl= ients utilizing the operating system trust store on the affected machine wi=
    ll accept rogue certificates for arbitrary domains, enabling persistent dec= ryption and interception of subsequent TLS connections. This issue is resol= ved in version v0.16.3.</td>
    <td>2026-06-22</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12249" target=3D= "_blank" rel=3D"noopener">CVE-2026-12249</a></td>
    </tr>

    <td class=3D"vendor-product">ultimatemember--Ultimate Member User Profile, = Registration, Login, Member Directory, Content Restriction &amp; Membership=
    Plugin</td>
    <td>The Ultimate Member plugin for WordPress is vulnerable to Account Takeo= ver via Password Reset Link Disclosure in all versions up to and including = 2.11.4. This is due to a chain of three logic bugs: (1) an MD5 hash fallbac=
    k in get_directory_by_hash() that allows any post to be used as a member di= rectory by computing SUBSTRING(MD5(post_id), 11, 5), (2) a strstr() parsing=
    logic flaw in post_data() that allows bypassing WordPress's protected meta=
    key restrictions by placing '_um_' anywhere in the meta key name rather th=
    an at the start, and (3) missing field name validation in build_user_card_d= ata() that allows arbitrary field names including 'password_reset_link' to =
    be passed to um_filtered_value(). This makes it possible for authenticated = attackers with Contributor-level access and above to create a malicious pos=
    t via XMLRPC with crafted meta fields, use the MD5 fallback to point the me= mber directory AJAX handler to their post, inject 'password_reset_link' int=
    o the tagline_fields configuration, and leak live password reset URLs for a=
    ll users in the member directory response, including administrators.</td> <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7761" target=3D"= _blank" rel=3D"noopener">CVE-2026-7761</a></td>
    </tr>

    <td class=3D"vendor-product">Uncanny Owl--Uncanny Automator</td> <td>Unauthenticated PHP Object Injection in Uncanny Automator &lt;=3D 7.3.1=
    .2 versions.</td>
    <td>2026-06-26</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56031" target=3D= "_blank" rel=3D"noopener">CVE-2026-56031</a></td>
    </tr>

    <td class=3D"vendor-product">Uncanny Owl--Uncanny Automator Pro</td> <td>Subscriber PHP Object Injection in Uncanny Automator Pro &lt;=3D 7.3.0.=
    6 versions.</td>
    <td>2026-06-26</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56057" target=3D= "_blank" rel=3D"noopener">CVE-2026-56057</a></td>
    </tr>

    <td class=3D"vendor-product">unclecode--crawl4ai</td>
    <td>Crawl4AI is an open-source LLM friendly web crawler &amp; scraper. Prio=
    r to 0.8.7, the _safe_eval_expression() function in the computed fields fea= ture uses an AST validator that only blocks attributes starting with unders= core. Python generator and frame object attributes (gi_frame, f_back, f_bui= ltins) do NOT start with underscore, enabling a complete sandbox escape to = achieve arbitrary code execution. The attack requires no authentication (JW=
    T disabled by default) and is triggered via POST /crawl with a crafted extr= action schema. This vulnerability is fixed in 0.8.7.</td>
    <td>2026-06-23</td>
    <td>9.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53753" target=3D= "_blank" rel=3D"noopener">CVE-2026-53753</a></td>
    </tr>

    <td class=3D"vendor-product">unclecode--crawl4ai</td>
    <td>Crawl4AI is an open-source LLM friendly web crawler &amp; scraper. Prio=
    r to 0.8.9, the Docker API server applied its SSRF destination check to the=
    crawl target URL only, not to the proxy address. An unauthenticated reques=
    t could supply a proxy pointing at an internal IP and route the browser thr= ough it, reaching internal services and cloud-metadata endpoints, while usi=
    ng a perfectly valid crawl URL. The Docker API is unauthenticated by defaul=
    t. /crawl, /crawl/stream, and /crawl/job accept a browser_config (and crawl= er_config). The following all feed Chromium's egress and were unchecked: br= owser_config.proxy_config.server, browser_config.proxy (deprecated field), = crawler_config.proxy_config.server, and --proxy-server / --proxy-pac-url / = --proxy-bypass-list / --host-resolver-rules flags in browser_config.extra_a= rgs. This vulnerability is fixed in 0.8.9.</td>
    <td>2026-06-23</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53755" target=3D= "_blank" rel=3D"noopener">CVE-2026-53755</a></td>
    </tr>

    <td class=3D"vendor-product">unclecode--crawl4ai</td>
    <td>Crawl4AI is an open-source LLM friendly web crawler &amp; scraper. Prio=
    r to 0.8.8, the Docker API server's SSRF protection (validate_webhook_url /=
    validate_url_destination in deploy/docker/utils.py) used an explicit IPv4/= IPv6 CIDR blocklist that missed several address families. An attacker could=
    reach internal services and cloud metadata endpoints (e.g. 169.254.169.254=
    ) despite the filter by encoding an internal IPv4 address inside an IPv6 tr= ansition form, or by using the IPv6 unspecified address. Because the Docker=
    API is unauthenticated by default (jwt_enabled: false), no credentials are=
    required. This vulnerability is fixed in 0.8.8.</td>
    <td>2026-06-23</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53754" target=3D= "_blank" rel=3D"noopener">CVE-2026-53754</a></td>
    </tr>

    <td class=3D"vendor-product">ValvePress--Automatic</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in Automatic &lt; 3.135.1 ve= rsions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56045" target=3D= "_blank" rel=3D"noopener">CVE-2026-56045</a></td>
    </tr>

    <td class=3D"vendor-product">vanhauser-thc--thc-hydra</td>
    <td>Hydra through 9.7, fixed in commit 9cc84c2, contains a stack buffer ove= rflow in NTLM authentication across SMTP, POP3, IMAP, NNTP, HTTP, HTTP-Prox=
    y, and HTTP-Proxy-Urlenum modules when processing malicious NTLM Type-2 cha= llenges. A malicious server can send a crafted NTLM Type-2 challenge with a=
    n excessively long domain string, causing base64-encoded response data to o= verflow a 500-byte stack buffer by 18 to 330 bytes, enabling remote code ex= ecution on systems without stack protection.</td>
    <td>2026-06-25</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56766" target=3D= "_blank" rel=3D"noopener">CVE-2026-56766</a></td>
    </tr>

    <td class=3D"vendor-product">vllm-project--vllm</td>
    <td>vLLM is an inference and serving engine for large language models (LLMs=
    ). From 0.3.0 until 0.22.0, a vulnerability in ASGI web servers and starlet= te's trust on those web servers enables an authentication bypass of the Ope= nAI API AuthenticationMiddleware. It allows to use the API without providin=
    g the configured VLLM_API_KEY or --api-key. This vulnerability is fixed in = 0.22.0.</td>
    <td>2026-06-22</td>
    <td>9.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48746" target=3D= "_blank" rel=3D"noopener">CVE-2026-48746</a></td>
    </tr>

    <td class=3D"vendor-product">vllm-project--vllm</td>
    <td>vLLM is an inference and serving engine for large language models (LLMs=
    ). Prior to 0.22.1, the vLLM Dockerfile is vulnerable to a dependency confu= sion attack through the flashinfer-jit-cache package. The package is instal= led from a custom index (flashinfer.ai/whl/) using --extra-index-url, but t=
    he package name was not registered on PyPI, and UV_INDEX_STRATEGY=3D"unsafe= -best-match" is set globally. An attacker who registers flashinfer-jit-cach=
    e on PyPI with version 0.6.11.post2 can execute arbitrary code as root duri=
    ng the Docker build and backdoor every resulting container image, enabling = exfiltration of all user prompts, API credentials, and model data from prod= uction vLLM deployments This vulnerability is fixed in 0.22.1.</td> <td>2026-06-22</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54232" target=3D= "_blank" rel=3D"noopener">CVE-2026-54232</a></td>
    </tr>

    <td class=3D"vendor-product">vllm-project--vllm</td>
    <td>vLLM is an inference and serving engine for large language models (LLMs=
    ). Prior to 0.22.0, an assert-based security check in vLLM's activation fun= ction loading allows any unauthenticated attacker to achieve arbitrary code=
    execution on the server by publishing a malicious HuggingFace model, when = vLLM runs in Python optimized mode (python -O or PYTHONOPTIMIZE=3D1). This = vulnerability is fixed in 0.22.0.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41523" target=3D= "_blank" rel=3D"noopener">CVE-2026-41523</a></td>
    </tr>

    <td class=3D"vendor-product">vtk--vtk</td>
    <td>vtk vtk-dicom vtkDICOMItem::NewDataElement heap-based buffer overflow v= ulnerability</td>
    <td>2026-06-25</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-22879" target=3D= "_blank" rel=3D"noopener">CVE-2026-22879</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2023.10.24.08.03.sta= ble_00 until 0.2026.05.06.15.42.stable_01, Warp may open executable local f= iles through the operating system default file handler. A malicious Markdow=
    n document or project can contain a local-file link that appears as normal = rendered content. If a user opens the Markdown in Warp and clicks the link,=
    affected builds may route the resolved local file to a platform file opene=
    r instead of limiting the action to safe viewer/editor targets. This vulner= ability is fixed in 0.2026.05.06.15.42.stable_01.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48704" target=3D= "_blank" rel=3D"noopener">CVE-2026-48704</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2025.08.06.08.12.sta= ble_00 until 0.2026.05.06.15.42.stable_01, Warp contains a command injectio=
    n in the prompt branch selector. A user who can publish a branch to a Git r= epository opened in Warp can cause a crafted branch name to be interpreted =
    by the victim's shell if the victim selects that branch from the UI. This v= ulnerability is fixed in 0.2026.05.06.15.42.stable_01.</td>
    <td>2026-06-24</td>
    <td>8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48719" target=3D= "_blank" rel=3D"noopener">CVE-2026-48719</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2025.03.05.08.02.sta= ble_00 until 0.2026.05.06.15.42.stable_01, Warp accepts non-inline `OSC 133= 7;File` payloads from terminal output and materialize the decoded payload a=
    s a local file without an additional confirmation step. This vulnerability =
    is fixed in 0.2026.05.06.15.42.stable_01.</td>
    <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48720" target=3D= "_blank" rel=3D"noopener">CVE-2026-48720</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2025.10.08.08.12.sta= ble_00 until 0.2026.05.06.15.42.stable_01, Warp contains a command executio=
    n permission-check bypass in the default unsandboxed CLI agent profile. The=
    CLI profile is non-interactive and relies on a command denylist as a safet=
    y boundary for commands that should require confirmation. Because command s= trings were checked before canonicalizing leading environment-variable assi= gnments, an attacker who can influence the agent's command output may cause=
    denylisted commands to be treated as non-denylisted. This vulnerability is=
    fixed in 0.2026.05.06.15.42.stable_01.</td>
    <td>2026-06-24</td>
    <td>8.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48721" target=3D= "_blank" rel=3D"noopener">CVE-2026-48721</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2021.04.25.23.05.sta= ble_00 until 0.2026.05.06.15.42.stable_01, Warp allows terminal output to r= equest access to the local system clipboard. A malicious remote host, remot=
    e program, or other attacker-controlled terminal output source can trigger = clipboard reads or writes without a separate confirmation step. This crosse=
    s the trust boundary between untrusted terminal output and the user's local=
    desktop clipboard. This vulnerability is fixed in 0.2026.05.06.15.42.stabl= e_01.</td>
    <td>2026-06-24</td>
    <td>8.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48725" target=3D= "_blank" rel=3D"noopener">CVE-2026-48725</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2023.03.21.08.02.sta= ble_00 until 0.2026.05.06.15.42.stable_01, Warp contains a command injectio=
    n issue in the legacy SSH background command path. Warp used the remote wor= king directory reported by the session when building helper commands for SS= H-backed metadata collection. A remote host, repository, or directory name = controlled by an attacker could cause that helper command to execute additi= onal shell syntax on the remote host as the victim's authenticated SSH acco= unt. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.</td> <td>2026-06-24</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48732" target=3D= "_blank" rel=3D"noopener">CVE-2026-48732</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2025.04.09.08.11.sta= ble_00 until 0.2026.05.06.15.42.stable_01, Warp contains a command executio=
    n policy bypass in Agent code search tools. The affected Grep and FileGlob = actions are authorized as read/search operations, but their implementations=
    build shell command strings from Agent-controlled inputs (search text, pat= hs, glob patterns) and execute them in the active terminal session. This vu= lnerability is fixed in 0.2026.05.06.15.42.stable_01.</td>
    <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48703" target=3D= "_blank" rel=3D"noopener">CVE-2026-48703</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2024.02.20.08.01.sta= ble_01 until 0.2026.05.06.15.42.stable_01, Warp contains a command injectio=
    n issue in the Linux external editor launcher. Warp expanded freedesktop .d= esktop Exec templates for affected editor integrations and executed the exp= anded command through a shell. A user who opens an attacker-controlled loca=
    l file path through an affected external editor or system-default editor ro= ute can cause shell syntax embedded in that path to execute as the local us= er. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.</td> <td>2026-06-24</td>
    <td>7.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48731" target=3D= "_blank" rel=3D"noopener">CVE-2026-48731</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2024.03.12.08.02.sta= ble_01 until 0.2026.05.06.15.42.stable_01, Warp contains an OS command inje= ction vulnerability in the WSL URL-opening fallback. When Warp is running u= nder WSL and cannot open a URL through wslview, it falls back to a Windows = command processor path. A URL controlled through terminal output can reach = that fallback when the user opens the link. This vulnerability is fixed in = 0.2026.05.06.15.42.stable_01.</td>
    <td>2026-06-24</td>
    <td>7.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54699" target=3D= "_blank" rel=3D"noopener">CVE-2026-54699</a></td>
    </tr>

    <td class=3D"vendor-product">Wasiliy Strecker--Contest Gallery</td> <td>Contributor SQL Injection in Contest Gallery &lt;=3D 30.0.0 versions.</=

    <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57662" target=3D= "_blank" rel=3D"noopener">CVE-2026-57662</a></td>
    </tr>

    <td class=3D"vendor-product">webp-sh--webp_server_go</td>
    <td>WebP Server Go through 0.14.4 contains a path traversal vulnerability o=
    n Windows that allows unauthenticated attackers to read files outside the c= onfigured IMG_PATH directory by sending requests with percent-encoded backs= lashes (%5C) that bypass the path.Clean() sanitization in handler/router.go=
    . Attackers can exploit the discrepancy between Go's forward-slash-only pat=
    h normalization and Windows file system APIs that treat backslashes and for= ward slashes as equivalent to access arbitrary files on the host filesystem=
    accessible to the server process.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53779" target=3D= "_blank" rel=3D"noopener">CVE-2026-53779</a></td>
    </tr>

    <td class=3D"vendor-product">wedevs--Dokan Pro</td>
    <td>The Dokan Pro plugin for WordPress is vulnerable to time-based SQL Inje= ction via the via 'latitude' and 'longitude' parameters in all versions up = to, and including, 5.0.4 due to insufficient escaping on the user supplied = parameter and lack of sufficient preparation on the existing SQL query. Thi=
    s makes it possible for unauthenticated attackers to append additional SQL = queries into already existing queries that can be used to extract sensitive=
    information from the database.</td>
    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12077" target=3D= "_blank" rel=3D"noopener">CVE-2026-12077</a></td>
    </tr>

    <td class=3D"vendor-product">weDevs--weMail</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in weMail &lt;=3D 2.1.2 vers= ions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57322" target=3D= "_blank" rel=3D"noopener">CVE-2026-57322</a></td>
    </tr>

    <td class=3D"vendor-product">withastro--astro</td>
    <td>Astro is a web framework. Prior to 6.3.3, when a component uses a clien= t:* directive, Astro inserts named slot content into a data-astro-template = attribute without HTML escaping the slot name allowing an attacker to break=
    out of the attribute context and inject arbitrary HTML, resulting in refle= cted XSS during SSR. This vulnerability is fixed in 6.3.3.</td> <td>2026-06-22</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50146" target=3D= "_blank" rel=3D"noopener">CVE-2026-50146</a></td>
    </tr>

    <td class=3D"vendor-product">withastro--astro</td>
    <td>Astro is a web framework. Prior to 6.4.6, Astro SSR apps with prerender=
    ed error pages (/404 or /500 using export const prerender =3D true) fetch t= hose pages over HTTP at runtime when an error occurs. The URL for this fetc=
    h is derived from request.url, which in turn gets its origin from the incom= ing Host header. When the Host header is not validated against allowedDomai= ns, an attacker can point the fetch at an arbitrary host and read the respo= nse. This vulnerability is fixed in 6.4.6.</td>
    <td>2026-06-22</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54299" target=3D= "_blank" rel=3D"noopener">CVE-2026-54299</a></td>
    </tr>

    <td class=3D"vendor-product">WordPress.com--Gutenverse Form</td> <td>Unauthenticated Cross Site Scripting (XSS) in Gutenverse Form &lt;=3D 2= .4.7 versions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56040" target=3D= "_blank" rel=3D"noopener">CVE-2026-56040</a></td>
    </tr>

    <td class=3D"vendor-product">WordPress.com--Quick Interest Slider</td> <td>Unauthenticated Cross Site Scripting (XSS) in Quick Interest Slider &lt= ;=3D 3.1.6 versions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56039" target=3D= "_blank" rel=3D"noopener">CVE-2026-56039</a></td>
    </tr>

    <td class=3D"vendor-product">WP All Import--WP All Import</td> <td>Administrator SQL Injection in WP All Import &lt;=3D 4.0.1 versions.</t=

    <td>2026-06-26</td>
    <td>7.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57628" target=3D= "_blank" rel=3D"noopener">CVE-2026-57628</a></td>
    </tr>

    <td class=3D"vendor-product">WP Swings--Subscriptions for WooCommerce</td> <td>Unauthenticated Broken Access Control in Subscriptions for WooCommerce = &lt;=3D 1.9.5 versions.</td>
    <td>2026-06-26</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56061" target=3D= "_blank" rel=3D"noopener">CVE-2026-56061</a></td>
    </tr>

    <td class=3D"vendor-product">wpDataTables--wpDataTables</td> <td>Unauthenticated SQL Injection in wpDataTables &lt;=3D 7.4 versions.</td=

    <td>2026-06-26</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54825" target=3D= "_blank" rel=3D"noopener">CVE-2026-54825</a></td>
    </tr>

    <td class=3D"vendor-product">wpeverest--Everest Forms</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in Everest Forms &lt;=3D 3.4=
    .8 versions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57312" target=3D= "_blank" rel=3D"noopener">CVE-2026-57312</a></td>
    </tr>

    <td class=3D"vendor-product">wpjobportal--WP Job Portal</td>
    <td>Contributor SQL Injection in WP Job Portal &lt;=3D 2.5.2 versions.</td> <td>2026-06-26</td>
    <td>8.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57653" target=3D= "_blank" rel=3D"noopener">CVE-2026-57653</a></td>
    </tr>

    <td class=3D"vendor-product">WPMU DEV--Forminator</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in Forminator &lt;=3D 1.53.1=
    versions.</td>
    <td>2026-06-25</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56071" target=3D= "_blank" rel=3D"noopener">CVE-2026-56071</a></td>
    </tr>

    <td class=3D"vendor-product">WSO2--WSO2 API Manager</td>
    <td>The WSO2 API Manager's message flow component, when processing WS-Addre= ssing headers, does not sufficiently validate or restrict user-controlled i= nput within these headers. This omission allows an attacker to manipulate W= S-Addressing headers to specify arbitrary destinations for server-initiated=
    requests. Successful exploitation allows an unauthenticated attacker to co= ntrol the destination of server-initiated requests originating from the WSO=
    2 API Manager. This direct control can enable unauthorized access to intern=
    al network resources or services that would typically be inaccessible from = external networks.</td>
    <td>2026-06-26</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-2053" target=3D"= _blank" rel=3D"noopener">CVE-2026-2053</a></td>
    </tr>

    <td class=3D"vendor-product">Xtemos--WoodMart</td>
    <td>Unauthenticated Cross Site Scripting (XSS) in WoodMart &lt;=3D 8.5.3 ve= rsions.</td>
    <td>2026-06-26</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56072" target=3D= "_blank" rel=3D"noopener">CVE-2026-56072</a></td>
    </tr>

    <td class=3D"vendor-product">yashpokharna2555--restaurent-management-system= </td>
    <td>A vulnerability was identified in yashpokharna2555 restaurent-managemen= t-system. This affects an unknown function of the file /forgotpassword.php =
    of the component POST Parameter Handler. Such manipulation of the argument = email leads to sql injection. The attack can be launched remotely. The expl= oit is publicly available and might be used. This product does not use vers= ioning. This is why information about affected and unaffected releases are = unavailable. The project was informed of the problem early through an issue=
    report but has not responded yet.</td>
    <td>2026-06-28</td>
    <td>7.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13498" target=3D= "_blank" rel=3D"noopener">CVE-2026-13498</a></td>
    </tr>

    <td class=3D"vendor-product">YMC--YMC Filter</td>
    <td>Improper Neutralization of Special Elements used in an SQL Command ('SQ=
    L Injection') vulnerability in YMC Filter allows SQL Injection. This issue = affects YMC Filter: from n/a through 3.11.5.</td>
    <td>2026-06-25</td>
    <td>9.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54836" target=3D= "_blank" rel=3D"noopener">CVE-2026-54836</a></td>
    </tr>

    <td class=3D"vendor-product">yt-dlp--yt-dlp</td>
    <td>yt-dlp is a command-line audio/video downloader. Prior to 2026.06.09, a=
    vulnerability exists in yt-dlp that allows a remote attacker to write arbi= trary OS-shortcut files (such as .desktop, .url, .webloc) to the user's fil= esystem, bypassing the remediation for CVE-2024-38519. The allowlist explic= itly included the unsafe extensions .desktop, .url, and .webloc so that the=
    functionality of the --write-link option (and its variants) could be prese= rved. These allowlist inclusions can be exploited by an attacker to write m= alicious OS-shortcut files in the context of a media or subtitles download.=
    This vulnerability is fixed in 2026.06.09.</td>
    <td>2026-06-23</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50023" target=3D= "_blank" rel=3D"noopener">CVE-2026-50023</a></td>
    </tr>

    <td class=3D"vendor-product">yt-dlp--yt-dlp</td>
    <td>yt-dlp is a command-line audio/video downloader. Prior to 2026.06.09, i=
    f aria2c is used as an external downloader for a fragmented manifest format=
    (such as an HLS/DASH stream), yt-dlp passes insufficiently sanitized input=
    to aria2c that allows an attacker to perform an arbitrary file write. On W= indows platforms, this can lead to immediate arbitrary code execution. On n= on-Windows platforms, this can lead to arbitrary code execution upon the ne=
    xt invocation of yt-dlp. This vulnerability is fixed in 2026.06.09.</td> <td>2026-06-23</td>
    <td>8.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50574" target=3D= "_blank" rel=3D"noopener">CVE-2026-50574</a></td>
    </tr>

    <td class=3D"vendor-product">zaproxy--zap-extensions</td>
    <td>Zed Attack Proxy (ZAP) ViewState add-on before version 4 contains an in= secure deserialization vulnerability that allows attackers who control a pr= oxied web server to achieve arbitrary code execution by embedding a malicio=
    us serialized Java object in the javax.faces.ViewState HTTP response parame= ter. The JSFViewState.decode() method base64-decodes the ViewState value an=
    d passes it directly to ObjectInputStream.readObject() without a deserializ= ation filter, allowlist, or type restriction, causing the malicious object =
    to be deserialized within the ZAP JVM when the Desktop UI renders the ViewS= tate panel.</td>
    <td>2026-06-26</td>
    <td>8.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57527" target=3D= "_blank" rel=3D"noopener">CVE-2026-57527</a></td>
    </tr>

    <td class=3D"vendor-product">zephyrproject--zephyr</td>
    <td>Zephyr's IP socket recvmsg() implementation (subsys/net/lib/sockets/soc= kets_inet.c, insert_pktinfo()) validated the user-supplied ancillary (msg_c= ontrol) buffer using only the payload length (msg-msg_controllen &lt; pktin= fo_len) before writing a full control message consisting of an aligned cmsg=
    header plus the payload. Because the check omitted the cmsg header size, a=
    control buffer whose length falls in the under-checked window (e.g. 16-27 = bytes for IPv4 IP_PKTINFO on a 64-bit target, where a single element actual=
    ly occupies 28 bytes) passes the guard yet causes a fixed-size out-of-bound=
    s write of up to one cmsg header (~12 bytes) past the end of the buffer. Un= der CONFIG_USERSPACE the recvmsg verifier allocates a kernel-heap copy of t=
    he control buffer sized to msg_controllen and runs the implementation again=
    st it, so the overflow corrupts kernel heap memory and is triggerable from =
    an unprivileged userspace thread; in supervisor mode it corrupts the caller=
    's buffer. The path is reachable on a UDP/IP socket with IP_PKTINFO/IPV6_RE= CVPKTINFO (or hoplimit/timestamping) enabled when the application calls rec= vmsg() with an undersized control buffer and a datagram is received; part o=
    f the overwritten bytes (the destination IP in ipi_addr) is influenced by t=
    he received packet. The fix makes the capacity check use NET_CMSG_SPACE(pkt= info_len) (aligned header + aligned data) and returns -ENOMEM when the buff=
    er is too small. Affected: v3.6.0 through v4.4.0.</td>
    <td>2026-06-27</td>
    <td>8.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10643" target=3D= "_blank" rel=3D"noopener">CVE-2026-10643</a></td>
    </tr>

    <td class=3D"vendor-product">zephyrproject--zephyr</td>
    <td>Zephyr's BSD-sockets getaddrinfo() implementation (subsys/net/lib/socke= ts/getaddrinfo.c) passes a pointer to a stack-allocated state object (struc=
    t getaddrinfo_state ai_state) as the user_data of an asynchronous DNS resol= ver query. The socket layer waits on a semaphore with a timeout deliberatel=
    y set slightly longer than the resolver's own per-query timeout. When that = semaphore wait nonetheless times out (-EAGAIN) - which can occur when the r= esolver's timeout work is delayed by workqueue contention, or in the docume= nted multi-retry configuration where CONFIG_NET_SOCKETS_DNS_TIMEOUT exceeds=
    CONFIG_NET_SOCKETS_DNS_BACKOFF_INTERVAL - the pre-fix code retries the que=
    ry (goto again) without cancelling the previous one and without resetting t=
    he semaphore. The previous query slot remains active in the resolver with i=
    ts callback and the stack pointer as user_data, and ai_state-dns_id is over= written so the stale query can no longer be cancelled. A subsequent DNS res= ponse delivered over UDP and matched by its 16-bit transaction id (in dispa= tcher_cb()/dns_read()), or the resolver's own delayed query-timeout work, t= hen invokes dns_resolve_cb() against the now out-of-scope stack frame, writ= ing through the stale pointer (state-status, state-idx, state-ai_arr[], and=
    k_sem_give()). Because the triggering response is network-delivered and it=
    s 16-bit id is spoofable/replayable by an on- or off-path attacker, this is=
    a network-influenceable use-after-return that can corrupt reused stack mem= ory, leading to crashes/denial of service or memory corruption. The fix can= cels the timed-out query by name and type before retrying and resets the lo= cal semaphore, eliminating the stale callback path. Affected: Zephyr v4.0.0=
    through v4.4.0.</td>
    <td>2026-06-28</td>
    <td>7.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10646" target=3D= "_blank" rel=3D"noopener">CVE-2026-10646</a></td>
    </tr>

    <td class=3D"vendor-product">zephyrproject-rtos--Zephyr</td>
    <td>A malformed Bluetooth Classic SDP attribute can trigger a reachable ass= ertion in Zephyr's SDP parser. In subsys/bluetooth/host/classic/sdp.c, bt_s= dp_parse_attribute() accepts an input buffer once it contains the 1-byte at= tribute type and 2-byte attribute id, but then unconditionally pulls an add= itional byte for the value type without verifying that the byte is present.=
    A truncated 3-byte attribute (for example 09 00 09) therefore reaches net_= buf_simple_pull() with insufficient remaining length, triggering the __ASSE= RT_NO_MSG(buf-&gt;len &gt;=3D len) check and a kernel panic in assert-enabl=
    ed builds (denial of service). In builds where assertions are disabled, par= sing may continue past the end of the available buffer, leading to an out-o= f-bounds read and undefined behavior.</td>
    <td>2026-06-22</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10651" target=3D= "_blank" rel=3D"noopener">CVE-2026-10651</a></td>
    </tr>

    <td class=3D"vendor-product">zephyrproject-rtos--Zephyr</td>
    <td>A missing length validation in the Zephyr Bluetooth Host ISO receive pa=
    th can be triggered by malformed HCI ISO data. In bt_iso_recv() (subsys/blu= etooth/host/iso.c), when processing PB=3DSTART/SINGLE fragments, the code p= ulls a TS SDU header (8 bytes, ts=3D1) or a non-TS SDU header (4 bytes, ts= =3D0) without first verifying that buf-&gt;len contains at least that many = bytes. The outer HCI ISO length check in hci_iso() validates payload length=
    consistency but not the minimum inner SDU header size, so a packet with pa= yload length 1 passes hci_iso() and then reaches net_buf_pull_mem(), which = asserts buf-&gt;len &gt;=3D len. As a result, malformed ISO traffic determi= nistically triggers a kernel assert (denial of service) in assert-enabled b= uilds, and in non-assert builds the same path may proceed with an undersize=
    d buffer, leading to out-of-bounds read behavior. The issue affects product=
    s using the Zephyr Host with CONFIG_BT_ISO_RX enabled, particularly where i= ncoming HCI data can be influenced by a malicious or compromised controller=
    or malformed forwarded ISO traffic.</td>
    <td>2026-06-22</td>
    <td>7.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10658" target=3D= "_blank" rel=3D"noopener">CVE-2026-10658</a></td>
    </tr>

    <td class=3D"vendor-product">zephyrproject-rtos--Zephyr</td>
    <td>Zephyr's IPv6 network stack can be prevented from receiving or processi=
    ng future incoming packets by sending a small number of maliciously fragmen= ted IPv6 packets. When such a packet is handled by the fragment-header proc= essing path, the associated RX network packet buffer (allocated from a memo=
    ry slab) is not released back to the pool. Repeating the malicious packet e= xhausts all RX buffer slots, after which the device can no longer obtain RX=
    buffers and stops receiving traffic, resulting in a denial of service.</td=

    <td>2026-06-25</td>
    <td>7.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13351" target=3D= "_blank" rel=3D"noopener">CVE-2026-13351</a></td>
    </tr>

    <td class=3D"vendor-product">zohocorp--manageengine_adselfservice_plus</td> <td>In ManageEngine ADSelfService Plus, RecoveryManager Plus, M365 Manager = Plus, and ADAudit Plus, the SSO tickets generated to authenticate that sess= ion could be predicted by an unauthenticated user, leading to account takeo= ver.</td>
    <td>2026-06-23</td>
    <td>9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11374" target=3D= "_blank" rel=3D"noopener">CVE-2026-11374</a></td>
    </tr>
    </tbody>
    </table>
    <p><a href=3D"#top">Back to top</a></p>
    </div>
    <div id=3D"medium_v">
    <h2 id=3D"medium_v_title">Medium Vulnerabilities</h2>
    <table class=3D"table no-tablesaw" style=3D"table-layout: fixed; width: 100= %;" border=3D"1" summary=3D"Medium Vulnerabilities">
    <thead>

    <th class=3D"vendor-product" style=3D"width: 24%;" scope=3D"col">
    <span class=3D"primary-vendor">Primary</span><br><span class=3D"primary-ven= dor">Vendor</span> -- Product</th>
    <th style=3D"width: 44%;" scope=3D"col">Description</th>
    <th style=3D"width: 10%;" scope=3D"col">Published</th>
    <th style=3D"width: 8%;" scope=3D"col">CVSS Score</th>
    <th style=3D"width: 7%;" scope=3D"col">Source Info</th>
    </tr>
    </thead>
    <tbody>

    <td class=3D"vendor-product">1Panel-dev--MaxKB</td>
    <td>MaxKB before 2.10.0 contains a server-side request forgery vulnerabilit=
    y in tool creation and update endpoints that allows authenticated users to = make arbitrary server requests by supplying unvalidated downloadCallbackUrl=
    and download_url parameters. Attackers with default workspace USER role ca=
    n exploit this to access internal network services by providing malicious U= RLs to the ToolSerializer endpoints.</td>
    <td>2026-06-25</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56779" target=3D= "_blank" rel=3D"noopener">CVE-2026-56779</a></td>
    </tr>

    <td class=3D"vendor-product">24liveblog--24liveblog live blog tool</td>
    <td>The 24liveblog - live blog tool plugin for WordPress is vulnerable to E= xposure of Sensitive Information in versions up to, and including, 2.2. Thi=
    s is due to the lb24_block_enqueue_scripts() function being hooked to enque= ue_block_editor_assets and, for any non-administrator user, falling back to=
    loading the administrator-configured site-wide 24liveblog integration secr= ets (lb24_token, lb24_refresh_token, lb24_uid, lb24_uname) from the options=
    table via get_option() and emitting them through wp_localize_script() as t=
    he lb24BlockData JavaScript object. This makes it possible for authenticate=
    d attackers, with contributor-level access and above, to extract third-part=
    y 24liveblog account credentials (including the API token and refresh token=
    ) by simply opening the block editor and inspecting the page source.</td> <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9183" target=3D"= _blank" rel=3D"noopener">CVE-2026-9183</a></td>
    </tr>

    <td class=3D"vendor-product">24liveblog--24liveblog live blog tool</td>
    <td>The 24liveblog - live blog tool plugin for WordPress is vulnerable to u= nauthorized modification of data due to a missing capability check on the u= pdate_lb24_token() AJAX function in versions up to, and including, 2.2. The=
    handler only verifies the 'lb24' nonce (which is generated and localized t=
    o any user with block editor access via lb24_block_enqueue_scripts()) and d= oes not verify the user's capabilities or that the supplied user_id belongs=
    to the current user. This makes it possible for authenticated attackers, w= ith author-level access and above, to overwrite the lb24_token, lb24_uid, l= b24_refresh_token, and lb24_uname user meta values of any user (including a= dministrators) as well as the corresponding site-wide options, effectively = hijacking the plugin's integration with the 24liveblog service.</td> <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9184" target=3D"= _blank" rel=3D"noopener">CVE-2026-9184</a></td>
    </tr>

    <td class=3D"vendor-product">ABB--Control Builder A</td>
    <td>Uncontrolled Search Path Element vulnerability in ABB Control Builder A=
    , ABB 800xA for Advant Master. This issue affects Control Builder A: throug=
    h 1.4/4; 800xA for Advant Master: through 6.0.3-1, through 6.1.1-1, 6.1.1-3=
    , 6.2.0-1.</td>
    <td>2026-06-23</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-13162" target=3D= "_blank" rel=3D"noopener">CVE-2025-13162</a></td>
    </tr>

    <td class=3D"vendor-product">About Envato--BookPro</td>
    <td>Unauthenticated Insecure Direct Object References (IDOR) in BookPro &lt= ;=3D 1.1.0 versions.</td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-66123" target=3D= "_blank" rel=3D"noopener">CVE-2025-66123</a></td>
    </tr>

    <td class=3D"vendor-product">Adobe--Acrobat Reader</td>
    <td>Acrobat Reader versions 2020.009.20074, 2020.001.30002, 2017.011.30171,=
    2015.006.30523 and earlier are affected by an out-of-bounds read vulnerabi= lity that could lead to disclosure of sensitive memory. An attacker could l= everage this vulnerability to disclose sensitive information. Exploitation =
    of this issue requires user interaction in that a victim must open a malici= ous file.</td>
    <td>2026-06-23</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2020-9711" target=3D"= _blank" rel=3D"noopener">CVE-2020-9711</a></td>
    </tr>

    <td class=3D"vendor-product">Adobe--Acrobat Reader</td>
    <td>Adobe Acrobat and Reader versions 2020.009.20074 and earlier, 2020.001.= 30002, 2017.011.30171 and earlier, and 2015.006.30523 and earlier are affec= ted by an out-of-bounds read vulnerability that could lead to disclosure of=
    sensitive memory. An attacker could leverage this vulnerability to disclos=
    e sensitive information. Exploitation of this issue requires user interacti=
    on in that a victim must open a malicious file.</td>
    <td>2026-06-23</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2020-9713" target=3D"= _blank" rel=3D"noopener">CVE-2020-9713</a></td>
    </tr>

    <td class=3D"vendor-product">ailchev--SearchPlus</td>
    <td>The SearchPlus plugin for WordPress is vulnerable to unauthorized modif= ication and deletion of data in versions up to, and including, 1.7.1. This =
    is due to a missing capability check and missing nonce validation on the se= archplus_save_token_action_callback() and searchplus_reset_token_action_cal= lback() functions, both of which are exposed to unauthenticated users throu=
    gh the wp_ajax_nopriv_ hooks. This makes it possible for unauthenticated at= tackers to overwrite or delete the plugin's stored account token and accoun=
    t name options (dym_token, dym_name, searchplus_token, searchplus_name, sp_= token, sp_name).</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8617" target=3D"= _blank" rel=3D"noopener">CVE-2026-8617</a></td>
    </tr>

    <td class=3D"vendor-product">ajitdas--Devs Accounting Simple Accounting and=
    Invoicing Solution</td>
    <td>The Devs Accounting - Simple Accounting and Invoicing Solution plugin f=
    or WordPress is vulnerable to unauthorized modification/deletion of data du=
    e to a missing capability check on the delete_single_account() function in = versions up to, and including, 1.2.0. The REST route 'devs-accounting/v1/de= lete-account/(?P&lt;id&gt;\d+)' is registered without any permission_callba= ck, which causes WordPress to expose the endpoint to public, unauthenticate=
    d access. This makes it possible for unauthenticated attackers to soft-dele=
    te arbitrary accounting account records (wp_dac_accounts) by issuing a simp=
    le GET request to the endpoint with any account ID.</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9172" target=3D"= _blank" rel=3D"noopener">CVE-2026-9172</a></td>
    </tr>

    <td class=3D"vendor-product">ajitdas--Devs Accounting Simple Accounting and=
    Invoicing Solution</td>
    <td>The Devs Accounting - Simple Accounting and Invoicing Solution plugin f=
    or WordPress is vulnerable to Missing Authorization in all versions up to, = and including, 1.2.0. This is due to the get_single_account() REST API call= back being registered with a permission_callback that unconditionally retur=
    ns true, providing no authentication or authorization checks on the /devs-a= ccounting/v1/get-account/&lt;id&gt; endpoint. This makes it possible for un= authenticated attackers to read arbitrary private financial account records=
    (including account name, bank name, and opening balance) by enumerating th=
    e numeric account ID, resulting in sensitive information disclosure.</td> <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9175" target=3D"= _blank" rel=3D"noopener">CVE-2026-9175</a></td>
    </tr>

    <td class=3D"vendor-product">AKIN Software Computer Import Export Industry = and Trade Ltd.--e-Commerce</td>
    <td>Improper neutralization of input during web page generation ('cross-sit=
    e scripting') vulnerability in AKIN Software Computer Import Export Industr=
    y and Trade Ltd. E-Commerce allows Reflected XSS. This issue affects e-Comm= erce: before 1.25.01.06.</td>
    <td>2026-06-23</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10857" target=3D= "_blank" rel=3D"noopener">CVE-2026-10857</a></td>
    </tr>

    <td class=3D"vendor-product">Alps Electric Co., Ltd.--Remote Keyless Entry = System (RKES) R53R0</td>
    <td>Remote Keyless Entry System (RKES), using the 433 MHz key fob bearing F=
    CC ID CWTR53R0 manufactured by ALPS ALPINE CO., LTD., is vulnerable to a ro= ll-back attack against its rolling-code authentication.=C2=A0 An attacker w= ithin RF range who records two consecutive lock or unlock transmissions fro=
    m a legitimate key fob can later replay the same pair of transmissions repe= atedly. During testing, replaying the first captured transmission caused th=
    e RKES to enter a state in which replaying the second captured transmission=
    resulted in a successful lock or unlock operation of the vehicle. Tested a=
    nd confirmed on=C2=A0a 2024 Suzuki Swift (SWIFT ISG GLS AC 1.2 5P 4x2 TM).<=

    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49319" target=3D= "_blank" rel=3D"noopener">CVE-2026-49319</a></td>
    </tr>

    <td class=3D"vendor-product">alsa-project--alsa-lib</td>
    <td>The Advanced Linux Sound Architecture (ALSA) library before 1.2.16.1 co= ntains a double-free vulnerability in parse_def() in src/conf.c that allows=
    attackers to corrupt memory by supplying maliciously crafted ALSA configur= ation text. When parsing nested compound or array configuration blocks, par= se_def() fails to check return values before continuing, causing snd_config= _delete() to be called twice on the same already-freed node, resulting in a=
    NULL-pointer write or invalid memory read.</td>
    <td>2026-06-22</td>
    <td>6.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56109" target=3D= "_blank" rel=3D"noopener">CVE-2026-56109</a></td>
    </tr>

    <td class=3D"vendor-product">antlr--ANTLR4</td>
    <td>A security vulnerability has been detected in antlr ANTLR4 up to 4.13.2=
    . Affected by this vulnerability is the function GoTarget of the file tool/= src/org/antlr/v4/codegen/target/GoTarget.java of the component gofmt. The m= anipulation leads to command injection. The attack can only be performed fr=
    om a local environment. The exploit has been disclosed publicly and may be = used. The vendor was contacted early about this disclosure but did not resp= ond in any way.</td>
    <td>2026-06-28</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13501" target=3D= "_blank" rel=3D"noopener">CVE-2026-13501</a></td>
    </tr>

    <td class=3D"vendor-product">antlr--ANTLR4</td>
    <td>A vulnerability was detected in antlr ANTLR4 up to 4.13.2. Affected by = this issue is the function getImportedVocabFile of the file tool/src/org/an= tlr/v4/parse/TokenVocabParser.java of the component tokenVocab Grammar Opti=
    on Handler. The manipulation results in path traversal. The attack can be e= xecuted remotely. The exploit is now public and may be used. The vendor was=
    contacted early about this disclosure but did not respond in any way.</td> <td>2026-06-28</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13503" target=3D= "_blank" rel=3D"noopener">CVE-2026-13503</a></td>
    </tr>

    <td class=3D"vendor-product">antlr--ANTLR4</td>
    <td>A flaw has been found in antlr ANTLR4 up to 4.13.2. This affects the fu= nction ObjectInputStream.readObject of the file antlr4-maven-plugin/src/mai= n/java/org/antlr/mojo/antlr4/GrammarDependencies.java of the component Mave=
    n Plugin. This manipulation causes time-of-check time-of-use. The attack is=
    restricted to local execution. A high degree of complexity is needed for t=
    he attack. It is indicated that the exploitability is difficult. The exploi=
    t has been published and may be used. The vendor was contacted early about = this disclosure but did not respond in any way.</td>
    <td>2026-06-28</td>
    <td>4.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13502" target=3D= "_blank" rel=3D"noopener">CVE-2026-13502</a></td>
    </tr>

    <td class=3D"vendor-product">Arraytics--WPCafe</td>
    <td>Subscriber Broken Access Control in WPCafe &lt;=3D 3.0.14 versions.</td=

    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57622" target=3D= "_blank" rel=3D"noopener">CVE-2026-57622</a></td>
    </tr>

    <td class=3D"vendor-product">ArtifexSoftware--mupdf</td>
    <td>MuPDF before 1.27.0-rc1 contains an uncontrolled recursion vulnerabilit=
    y in the EPUB CSS rendering engine that allows remote attackers to cause a = denial of service by supplying a maliciously crafted EPUB file with deeply = nested HTML elements and inline CSS styles. The function value_from_inherit= able_property() in css-apply.c recurses through the CSS property inheritanc=
    e chain without a depth limit, exhausting the process stack and causing a c= rash in any application using MuPDF for EPUB rendering.</td> <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71382" target=3D= "_blank" rel=3D"noopener">CVE-2025-71382</a></td>
    </tr>

    <td class=3D"vendor-product">assistioai--Assistio</td>
    <td>The Assistio plugin for WordPress is vulnerable to unauthorized modific= ation of data due to a missing capability check and missing nonce verificat= ion on the assistio_plugin_delete_assistio_settings() function in versions =
    up to, and including, 1.1.2. This makes it possible for authenticated attac= kers, with Subscriber-level access and above, to delete the plugin's option=
    s including the critical 'assistiobot_oauth_settings' option, which disrupt=
    s the plugin's integration with the Assistio bot service.</td> <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8614" target=3D"= _blank" rel=3D"noopener">CVE-2026-8614</a></td>
    </tr>

    <td class=3D"vendor-product">authlib--authlib</td>
    <td>Authlib is a Python library which builds OAuth and OpenID Connect serve= rs. Prior to 1.6.10 and 1.7.1, Authlib's OAuth 2.0 authorization endpoint c=
    an be turned into an unauthenticated open redirect when a request uses an u= nsupported response_type and supplies an attacker-controlled redirect_uri. = The vulnerable behavior happens before client lookup and before any redirec=
    t URI validation. As a result, an attacker does not need a valid client reg= istration, an authenticated user, or any prior state. A single request to t=
    he authorization endpoint is enough to obtain a 302 Location response to an=
    arbitrary attacker-controlled URL. This vulnerability is fixed in 1.6.10 a=
    nd 1.7.1.</td>
    <td>2026-06-22</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41479" target=3D= "_blank" rel=3D"noopener">CVE-2026-41479</a></td>
    </tr>

    <td class=3D"vendor-product">bdthemes--Live Copy Paste for Elementor</td> <td>Contributor Broken Access Control in Live Copy Paste for Elementor &lt;= =3D 1.5.3 versions.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-63079" target=3D= "_blank" rel=3D"noopener">CVE-2025-63079</a></td>
    </tr>

    <td class=3D"vendor-product">berfect--Reviews and Rating Docplanner</td> <td>The Reviews and Rating - Docplanner plugin for WordPress is vulnerable =
    to authorization bypass in all versions up to, and including, 1.1.4. This i=
    s due to the plugin not properly verifying that a user is authorized to per= form an action. This makes it possible for authenticated attackers, with su= bscriber-level access and above, to trigger outbound scraping of external w= ebsites and write scraped review data into the wp_dp_reviews database table=
    , as well as send feature-request emails from the site administrator's emai=
    l address.</td>
    <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9619" target=3D"= _blank" rel=3D"noopener">CVE-2026-9619</a></td>
    </tr>

    <td class=3D"vendor-product">bitwarden--server</td>
    <td>Bitwarden Server before 2026.5.0 contains a broken access control vulne= rability that allows any authenticated user to access arbitrary organizatio=
    n billing data by supplying an arbitrary organizationId to the PreviewInvoi= ceController endpoints without membership or authorization checks. Attacker=
    s can exploit the missing ManageOrganizationBillingRequirement on the previ=
    ew invoice endpoints to retrieve Stripe-computed tax totals, subscription s= tatus, and billing details derived from any target organization's real cust= omer and subscription data.</td>
    <td>2026-06-25</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57521" target=3D= "_blank" rel=3D"noopener">CVE-2026-57521</a></td>
    </tr>

    <td class=3D"vendor-product">BlockArt--Magazine Blocks</td>
    <td>Contributor Cross Site Scripting (XSS) in Magazine Blocks &lt;=3D 1.8.3=
    versions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57650" target=3D= "_blank" rel=3D"noopener">CVE-2026-57650</a></td>
    </tr>

    <td class=3D"vendor-product">bPlugins--Flash &amp; HTML5 Video</td> <td>Unauthenticated Broken Access Control in Flash &amp; HTML5 Video &lt;=
    =3D 2.11.0 versions.</td>
    <td>2026-06-26</td>
    <td>5.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57323" target=3D= "_blank" rel=3D"noopener">CVE-2026-57323</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior are vulnerable to Open Redirect through a substring = check rather than a host check at str_contains($referer, CACTI_PATH_URL). W= hen the user's login_opts =3D=3D '1' (redirect to referer after login), the=
    function used $_SERVER['HTTP_REFERER'] directly. An attacker could craft a=
    referer such as https://evil.com/cacti/. Where CACTI_PATH_URL is /cacti/, = the substring matches and the user is redirected to evil.com after login. T=
    he pre-existing validate_redirect_url() helper at lib/html_utility.php perf= ormed proper validation but was not invoked from auth_login_redirect(). Thi=
    s issue has been fixed in version 1.2.31.</td>
    <td>2026-06-25</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40080" target=3D= "_blank" rel=3D"noopener">CVE-2026-40080</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior are vulnerable to Path Traversal through the Report = format_file Parameter, causing arbitrary file read. This vulnerability occu=
    rs in two stages. In the first stage (stored injection), lib/html_reports.p=
    hp at line 283 stores $save['format_file'] =3D $post['format_file'] directl=
    y into the database without any validation. In the second stage (file read)=
    , lib/reports.php at line 667 concatenates CACTI_PATH_FORMATS . '/' . $form= at_file, and line 670 then calls file($format_file), reading arbitrary file=
    s from the filesystem. This issue has been fixed in version 1.2.31.</td> <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40084" target=3D= "_blank" rel=3D"noopener">CVE-2026-40084</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior have missing session_regenerate_id() after login, le= ading to Session Fixation. session_regenerate_id() is NOT called after succ= essful login. The login flow at auth_login.php:203-207 directly sets $_SESS= ION[SESS_USER_ID] without rotating the session ID. The session cookie confi= guration is otherwise good (httponly=3Dtrue, samesite=3DStrict, secure=3Dtr=
    ue for HTTPS at include/global.php:513-537), but these do not prevent sessi=
    on fixation via same-site vectors. This issue has been fixed in version 1.2= .31.</td>
    <td>2026-06-25</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40082" target=3D= "_blank" rel=3D"noopener">CVE-2026-40082</a></td>
    </tr>

    <td class=3D"vendor-product">caddyserver--caddy</td>
    <td>Caddy is an extensible server platform that uses TLS by default. From 2= .4.0 until 2.11.3, the authorization layer and the /config traversal layer =
    do not agree on what object the path refers to. In this case, a path author= ized for one config object is accepted, but then resolves to a different co= nfig object during traversal. This happens because the authorization layer = uses string prefix matching and the /config traversal layer parses array in= dices numerically using strconv.Atoi(). This vulnerability is fixed in 2.11= .3.</td>
    <td>2026-06-23</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45692" target=3D= "_blank" rel=3D"noopener">CVE-2026-45692</a></td>
    </tr>

    <td class=3D"vendor-product">caddyserver--caddy</td>
    <td>Caddy is an extensible server platform that uses TLS by default. Prior =
    to 2.11.4, Caddy's stripHTML template function cannot reliably remove all H= TML tags from input strings. Certain malformed HTML, such as &lt;&lt;&gt;im=
    g src=3Dx onerror=3Dalert()&gt;, can bypass the tag-stripping logic, potent= ially leaving dangerous content in the output if it is later rendered as HT= ML. This may allow client-side XSS in cases where untrusted strings are ren= dered unsafely. This vulnerability is fixed in 2.11.4.</td>
    <td>2026-06-23</td>
    <td>4.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52846" target=3D= "_blank" rel=3D"noopener">CVE-2026-52846</a></td>
    </tr>

    <td class=3D"vendor-product">Canonical--LXD</td>
    <td>Nil-pointer dereference in CreateCustomVolumeFromBackup in LXD up to ve= rsion 6.8 and 5.21 on Linux allows an authenticated user with can_create_st= orage_volumes permissions to cause a denial of service via a specially craf= ted custom-volume backup tarball that omits the expires_at snapshot field.<=

    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9639" target=3D"= _blank" rel=3D"noopener">CVE-2026-9639</a></td>
    </tr>

    <td class=3D"vendor-product">Canonical--lxd</td>
    <td>In Canonical LXD versions 4.12 through 6.9, a Server-Side Request Forge=
    ry (SSRF) vulnerability in the image import functionality allows authentica= ted users with the can_create_images entitlement to interact with internal = network infrastructure via the /images endpoint. When importing an image fr=
    om a URL source, the LXD daemon fails to validate or restrict outbound dest= ination IP addresses, allowing connections to loopback, RFC1918 private ran= ges, and cloud metadata endpoints. This enables error-based port scanning a=
    nd unauthorized interaction with internal HTTP services from the daemon's n= etwork position.</td>
    <td>2026-06-26</td>
    <td>5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-28385" target=3D= "_blank" rel=3D"noopener">CVE-2026-28385</a></td>
    </tr>

    <td class=3D"vendor-product">Cap-go--capgo</td>
    <td>Cap-go before 12.128.2 contains multiple SQL injection vulnerabilities =
    in cloudflare.ts where user-controlled values from API request bodies are i= nterpolated directly into SQL query strings without sanitization or paramet= erization. Authenticated users with read-level API key permissions can inje=
    ct arbitrary SQL through deviceIds, search, version_name, cursor, and actio=
    ns parameters to access analytics data belonging to other users or applicat= ions.</td>
    <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56221" target=3D= "_blank" rel=3D"noopener">CVE-2026-56221</a></td>
    </tr>

    <td class=3D"vendor-product">Cap-go--capgo</td>
    <td>Cap-go before 12.128.2 contains an authorization bypass vulnerability i=
    n the GET /organization/members endpoint that allows org-limited API keys t=
    o bypass limited_to_orgs restrictions. Attackers with org-limited API keys = can read membership data including uid, email, image_url, role, and is_tmp = from organizations outside their assigned scope.</td>
    <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56310" target=3D= "_blank" rel=3D"noopener">CVE-2026-56310</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains an unsecured images bucket lacking any r=
    ow level security controls, allowing unauthenticated attackers to read, ins= ert, and delete stored app icons. Remote attackers can exploit this misconf= iguration to delete all icons and leak sensitive app IDs and user IDs.</td> <td>2026-06-24</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56302" target=3D= "_blank" rel=3D"noopener">CVE-2026-56302</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains a weak parsing vulnerability in the x-li= mited-key-id header that allows attackers to bypass subkey enforcement by s= ubmitting malformed values, zero, or duplicate headers that result in NaN o=
    r falsy values. Remote attackers can manipulate the x-limited-key-id header=
    to disable limited key scoping and execute requests using the main API key=
    context instead of restricted subkey permissions.</td>
    <td>2026-06-22</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56306" target=3D= "_blank" rel=3D"noopener">CVE-2026-56306</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains a credential validation vulnerability in=
    the POST /functions/v1/private/validate_password_compliance endpoint that =
    is callable using only the public Supabase key without authentication. The = endpoint is CORS-permissive with wildcard origin allowance and lacks rate l= imiting, enabling attackers to perform password spraying and credential stu= ffing attacks to compromise user accounts.</td>
    <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56234" target=3D= "_blank" rel=3D"noopener">CVE-2026-56234</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains an authorization bypass vulnerability in=
    the public.get_current_plan_max_org RPC function that allows unauthenticat=
    ed attackers to retrieve arbitrary organization plan limits. Attackers can = call the RPC endpoint with any organization UUID using only the public Supa= base key to disclose billing information including MAU, bandwidth, storage,=
    and build time limits for any organization.</td>
    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56311" target=3D= "_blank" rel=3D"noopener">CVE-2026-56311</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo (backend Supabase edge functions) before 12.128.2 does not apply = the global authentication middleware to the GET /private/role_bindings/:org= _id endpoint, unlike the POST and DELETE role_bindings routes, so unauthent= icated requests reach the handler instead of being rejected at the middlewa=
    re layer. The handler still performs its own authorization check and return=
    s Unauthorized, so no direct data exposure occurs; the flaw is inconsistent=
    authentication enforcement across HTTP methods that could enable authoriza= tion bypass if the handler logic changes.</td>
    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56321" target=3D= "_blank" rel=3D"noopener">CVE-2026-56321</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains an information disclosure vulnerability =
    in the public.exist_app_v2 RPC function that allows unauthenticated attacke=
    rs to enumerate app_ids by calling POST /rest/v1/rpc/exist_app_v2 with arbi= trary appid parameters. Remote attackers can exploit this SECURITY DEFINER = function to determine whether specific app_ids exist in the public.apps tab= le, enabling cross-tenant app enumeration and privacy violations.</td> <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56337" target=3D= "_blank" rel=3D"noopener">CVE-2026-56337</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains a denial of service vulnerability in the=
    /auth/v1/otp endpoint that prevents email verification for two-factor auth= entication due to captcha validation failures. Authenticated users cannot c= omplete 2FA enrollment as the backend consistently returns HTTP 500 errors = with captcha verification process failed messages, blocking access to secur= ity controls.</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56338" target=3D= "_blank" rel=3D"noopener">CVE-2026-56338</a></td>
    </tr>

    <td class=3D"vendor-product">Capgo--Capgo</td>
    <td>Capgo before 12.128.2 contains a denial of service vulnerability in the=
    POST /app/demo endpoint that allows authenticated users with org write per= missions to create unlimited demo applications without rate limiting or quo=
    ta enforcement. Attackers can repeatedly invoke this endpoint to generate a= pproximately 138 database write operations per request, causing degraded pe= rformance, increased costs, and potential service instability.</td> <td>2026-06-22</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56255" target=3D= "_blank" rel=3D"noopener">CVE-2026-56255</a></td>
    </tr>

    <td class=3D"vendor-product">Chris Carlevato--utm.codes</td>
    <td>Subscriber Server Side Request Forgery (SSRF) in utm.codes &lt;=3D 1.9.=
    0 versions.</td>
    <td>2026-06-26</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56026" target=3D= "_blank" rel=3D"noopener">CVE-2026-56026</a></td>
    </tr>

    <td class=3D"vendor-product">ChromeDevTools--chrome-devtools-mcp</td> <td>Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent=
    control and inspect a live Chrome browser. From 0.20.0 until 1.1.0, The ch= rome-devtools-mcp daemon writes its PID file with fs.writeFileSync() to a d= eterministic runtime path. On typical macOS environments, and on Linux sess= ions where $XDG_RUNTIME_DIR is unset, that runtime path falls back to /tmp/= chrome-devtools-mcp-&lt;uid&gt;/daemon.pid. Because the write does not use = O_NOFOLLOW, a local low-privilege user on the same POSIX host can pre-creat=
    e /tmp/chrome-devtools-mcp-&lt;victim_uid&gt;/daemon.pid as a symlink to a = file writable by the victim. When the victim later starts daemon mode, fs.w= riteFileSync() follows the symlink and truncates the target file to the dae= mon PID string. This vulnerability is fixed in 1.1.0.</td>
    <td>2026-06-24</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53765" target=3D= "_blank" rel=3D"noopener">CVE-2026-53765</a></td>
    </tr>

    <td class=3D"vendor-product">ChromeDevTools--chrome-devtools-mcp</td> <td>Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent=
    control and inspect a live Chrome browser. From 0.24.0 until 1.1.0, McpCon= text.validatePath() enforces workspace roots by checking whether path.resol= ve(filePath) textually falls under one of the configured root paths. path.r= esolve() does not canonicalize symbolic links. As a result, a symlink insid=
    e a configured workspace root can point to a file outside that root, pass v= alidation, and then be followed by downstream file read/write operations. T= his bypass applies even when the MCP client correctly declares the roots ca= pability with a non-empty list. It is separate from the documented legacy b= ehavior where missing roots capability allows all paths. The practical impa=
    ct is a workspace-boundary bypass. In the write direction, filePath-writing=
    tools can overwrite out-of-root files through an in-root symlink. In the r= ead direction, upload_file can read through the symlink and send the file t=
    o the currently selected web page. This vulnerability is fixed in 1.1.0.</t=

    <td>2026-06-24</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53766" target=3D= "_blank" rel=3D"noopener">CVE-2026-53766</a></td>
    </tr>

    <td class=3D"vendor-product">chuhpl--Book a Room Event Calendar</td>
    <td>The Book a Room Event Calendar plugin for WordPress is vulnerable to Cr= oss-Site Request Forgery in all versions up to, and including, 1.9. This is=
    due to missing or incorrect nonce validation on the settings_form()/update= _settings() functionality. The plugin's options page handler dispatches on = the 'action' POST parameter and calls update_settings(), which persists plu= gin configuration (including the external database host, username, password=
    , prefix, database name, encryption key, and registration page URL) via upd= ate_option(), without ever generating a nonce field in the settings form or=
    verifying one (no wp_nonce_field(), check_admin_referer(), or wp_verify_no= nce() exists anywhere in the plugin). This makes it possible for unauthenti= cated attackers to modify the plugin's database connection settings via a f= orged request granted they can trick a site administrator into performing a=
    n action such as clicking on a link.</td>
    <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9721" target=3D"= _blank" rel=3D"noopener">CVE-2026-9721</a></td>
    </tr>

    <td class=3D"vendor-product">Code Amp--Forget About Shortcode Buttons</td> <td>Contributor Broken Access Control in Forget About Shortcode Buttons &lt= ;=3D 2.1.3 versions.</td>
    <td>2026-06-26</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-63041" target=3D= "_blank" rel=3D"noopener">CVE-2025-63041</a></td>
    </tr>

    <td class=3D"vendor-product">codepeople--CodePeople Post Map for Google Map= s</td>
    <td>The CodePeople Post Map for Google Maps plugin for WordPress is vulnera= ble to Stored Cross-Site Scripting via 'cpm_point' Post Meta in all version=
    s up to, and including, 1.2.6 due to insufficient input sanitization and ou= tput escaping. This makes it possible for authenticated attackers, with Con= tributor-level access and above, to inject arbitrary web scripts in pages t= hat will execute whenever a user accesses an injected page.</td> <td>2026-06-27</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13335" target=3D= "_blank" rel=3D"noopener">CVE-2026-13335</a></td>
    </tr>

    <td class=3D"vendor-product">Contempoinc--Real Estate 7</td> <td>Unauthenticated Cross Site Request Forgery (CSRF) in Real Estate 7 &lt;= =3D 3.5.9 versions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57641" target=3D= "_blank" rel=3D"noopener">CVE-2026-57641</a></td>
    </tr>

    <td class=3D"vendor-product">Crawl4AI--Crawl4AI</td>
    <td>Crawl4AI before 0.8.7 contains an authentication bypass vulnerability i=
    n the monitor router endpoints that allows unauthenticated attackers to acc= ess destructive operations. Remote attackers can invoke the /monitor/action= s/cleanup endpoint and manipulate monitoring state without authentication, = causing service disruption.</td>
    <td>2026-06-24</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56262" target=3D= "_blank" rel=3D"noopener">CVE-2026-56262</a></td>
    </tr>

    <td class=3D"vendor-product">Crawl4AI--Crawl4AI</td>
    <td>Crawl4AI before 0.8.7 contains a stored cross-site scripting vulnerabil= ity in the monitor dashboard that renders crawl URLs and error messages via=
    innerHTML without escaping. An attacker can submit a crafted crawl request=
    with malicious markup that executes in an operator's browser when viewing = the dashboard.</td>
    <td>2026-06-23</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56263" target=3D= "_blank" rel=3D"noopener">CVE-2026-56263</a></td>
    </tr>

    <td class=3D"vendor-product">Creative Themes--Blocksy Companion Pro</td> <td>Unauthenticated Insecure Direct Object References (IDOR) in Blocksy Com= panion Pro &lt;=3D 2.1.46 versions.</td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57630" target=3D= "_blank" rel=3D"noopener">CVE-2026-57630</a></td>
    </tr>

    <td class=3D"vendor-product">CridioStudio--ListingPro</td>
    <td>Subscriber Cross Site Scripting (XSS) in ListingPro &lt;=3D 2.9.11 vers= ions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56046" target=3D= "_blank" rel=3D"noopener">CVE-2026-56046</a></td>
    </tr>

    <td class=3D"vendor-product">danny-avila--LibreChat</td>
    <td>LibreChat is an enhanced ChatGPT clone that supports multiple AI provid= ers. Prior to 0.8.4-rc1, the fix for CVE-2024-11171 (commit bb58a2d0) added=
    limits: { fileSize } to createMulterInstance() in the file upload routes. = However, the POST /api/convos/import endpoint uses a separate multer instan=
    ce that was never updated with the same limits configuration. Combined with=
    the application-level size check being disabled by default (the CONVERSATI= ON_IMPORT_MAX_FILE_SIZE_BYTES env var is commented out in .env.example), an=
    authenticated user can upload arbitrarily large files to exhaust server di=
    sk space and memory. This vulnerability is fixed in 0.8.4-rc1.</td> <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54024" target=3D= "_blank" rel=3D"noopener">CVE-2026-54024</a></td>
    </tr>

    <td class=3D"vendor-product">danny-avila--LibreChat</td>
    <td>LibreChat is an enhanced ChatGPT clone that supports multiple AI provid= ers. Prior to 0.8.4-rc1, the POST /api/files/images endpoint allows any aut= henticated user to upload files into any agent's tool_resources (e.g., cont= ext, execute_code) without verifying ownership or EDIT permission on the ta= rget agent. A permission check was added to the POST /api/files route in a = previous patch, but the image upload route was never updated with the same = check. An attacker can simply use the image endpoint instead of the file en= dpoint to bypass the authorization entirely. This vulnerability is fixed in=
    0.8.4-rc1.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54027" target=3D= "_blank" rel=3D"noopener">CVE-2026-54027</a></td>
    </tr>

    <td class=3D"vendor-product">danny-avila--LibreChat</td>
    <td>LibreChat is an enhanced ChatGPT clone that supports multiple AI provid= ers. Prior to 0.8.4-rc1, the fix for CVE-2025-7105 added forkIpLimiter and = forkUserLimiter rate limiters to POST /api/convos/fork to prevent rapid-fir=
    e conversation duplication. However, the POST /api/convos/duplicate endpoin=
    t - which is in the same file and performs the exact same expensive databas=
    e operations - was not given any rate limiter. An authenticated user can by= pass the CVE-2025-7105 fix by using /duplicate instead of /fork to exhaust = server resources. This vulnerability is fixed in 0.8.4-rc1.</td> <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54037" target=3D= "_blank" rel=3D"noopener">CVE-2026-54037</a></td>
    </tr>

    <td class=3D"vendor-product">danny-avila--LibreChat</td>
    <td>LibreChat is an enhanced ChatGPT clone that supports multiple AI provid= ers. Prior to 0.8.4-rc1, there is a vulnerability in LibreChat's markdown a= rtifact preview pipeline. The marked library v15.0.12 does not HTML-escape = double-quote characters in image alt text when a custom renderer falls thro= ugh to the default renderer. LibreChat's generateMarkdownHtml function (in = client/src/utils/markdown.ts) installs a custom image renderer that returns=
    false for URLs passing the isSafeUrl allowlist check, which causes marked =
    to fall back to its built-in renderer. That built-in renderer inserts the r=
    aw alt text into the alt=3D"..." attribute without escaping double-quote ch= aracters. An attacker can craft an alt text such as " onload=3D"payload to = break out of the attribute and inject an arbitrary event handler. The resul= ting HTML is then assigned to document.getElementById('content').innerHTML = inside the Sandpack preview iframe, causing the payload to execute in the v= ictim's browser. This vulnerability is fixed in 0.8.4-rc1.</td> <td>2026-06-25</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54025" target=3D= "_blank" rel=3D"noopener">CVE-2026-54025</a></td>
    </tr>

    <td class=3D"vendor-product">danny-avila--LibreChat</td>
    <td>LibreChat is an enhanced ChatGPT clone that supports multiple AI provid= ers. Prior to 0.8.4-rc1, the DELETE /api/messages/:conversationId/:messageI=
    d endpoint allows any authenticated user to delete any other user's message=
    s. The validateMessageReq middleware only validates that the conversationId=
    belongs to the requesting user, but the handler calls deleteMessages({ mes= sageId }) using only the messageId as the MongoDB filter - without adding a=
    user constraint. An attacker provides their own valid conversationId (to p= ass validation) and the victim's messageId (to target deletion), resulting =
    in permanent, irrecoverable message deletion. This vulnerability is fixed i=
    n 0.8.4-rc1.</td>
    <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54029" target=3D= "_blank" rel=3D"noopener">CVE-2026-54029</a></td>
    </tr>

    <td class=3D"vendor-product">danny-avila--LibreChat</td>
    <td>LibreChat is an enhanced ChatGPT clone that supports multiple AI provid= ers. Prior to 0.8.4-rc1, the GET /api/auth/2fa/enable endpoint can be calle=
    d by an authenticated user (or attacker with a stolen session) even when 2F=
    A is already fully enabled on the account. This endpoint overwrites the exi= sting TOTP secret, generates new backup codes, and sets twoFactorEnabled to=
    false - all without requiring any TOTP or backup code verification. An att= acker with a valid session token can completely take over a victim's 2FA, l= ocking the legitimate user out of their own two-factor authentication. This=
    vulnerability is fixed in 0.8.4-rc1.</td>
    <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54036" target=3D= "_blank" rel=3D"noopener">CVE-2026-54036</a></td>
    </tr>

    <td class=3D"vendor-product">danny-avila--LibreChat</td>
    <td>LibreChat is an enhanced ChatGPT clone that supports multiple AI provid= ers. Prior to 0.8.4-rc1, the POST /api/auth/2fa/backup/regenerate endpoint = regenerates all 2FA backup codes without requiring any TOTP token or existi=
    ng backup code verification. An attacker with a stolen session token can si= lently replace a victim's backup codes and use them to bypass 2FA login or = disable 2FA entirely. This vulnerability is fixed in 0.8.4-rc1.</td> <td>2026-06-25</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54040" target=3D= "_blank" rel=3D"noopener">CVE-2026-54040</a></td>
    </tr>

    <td class=3D"vendor-product">Databend--Databend</td>
    <td>A vulnerability was identified in Databend up to 1.2.881 on HTTP. This = affects the function ClientSessionManager::state_key of the file src/query/= service/src/servers/http/v1/session/client_session_manager.rs of the compon= ent Tenant Handler. The manipulation leads to authorization bypass. It is p= ossible to initiate the attack remotely. The exploit is publicly available = and might be used. The pull request to fix this issue awaits acceptance.</t=

    <td>2026-06-28</td>
    <td>6.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13512" target=3D= "_blank" rel=3D"noopener">CVE-2026-13512</a></td>
    </tr>

    <td class=3D"vendor-product">daytonaio--daytona</td>
    <td>Daytona is a secure and elastic infrastructure runtime for AI-generated=
    code execution and agent workflows. Prior to 0.185.0, a cross-tenant autho= rization flaw in Daytona's notification WebSocket gateway allowed any authe= nticated user to subscribe to another organization's realtime notification = channel and passively receive that organization's events. This vulnerabilit=
    y is fixed in 0.185.0.</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54324" target=3D= "_blank" rel=3D"noopener">CVE-2026-54324</a></td>
    </tr>

    <td class=3D"vendor-product">daytonaio--daytona</td>
    <td>Daytona is a secure and elastic infrastructure runtime for AI-generated=
    code execution and agent workflows. Prior to 0.185.0, the daemon's git clo=
    ne implementation disabled TLS certificate verification. When a clone reque=
    st carried Git credentials, the daemon sent the HTTP Basic Authorization he= ader to the remote over a connection whose certificate was never validated,=
    on both the go-git and native git CLI code paths. An attacker able to inte= rcept clone traffic could present any TLS certificate, capture the Git cred= entials supplied for the clone, and serve tampered repository content into = the sandbox. This vulnerability is fixed in 0.185.0.</td>
    <td>2026-06-23</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54323" target=3D= "_blank" rel=3D"noopener">CVE-2026-54323</a></td>
    </tr>

    <td class=3D"vendor-product">daytonaio--daytona</td>
    <td>Daytona is a secure and elastic infrastructure runtime for AI-generated=
    code execution and agent workflows. Prior to 0.186, a sandbox volume refer= ence (volumeId, which may also be a volume name) was forwarded to the runne=
    r and used to build the host bind-mount source path without confinement. A = reference containing path-traversal sequences could in principle resolve th=
    e mount source outside the intended per-volume base directory. This vulnera= bility is fixed in 0.186.</td>
    <td>2026-06-23</td>
    <td>4.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54319" target=3D= "_blank" rel=3D"noopener">CVE-2026-54319</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Display and Peripheral Manager</td>
    <td>Dell Display and Peripheral Manager (DDPM Mac), versions prior to 2.3, = contain a Concurrent Execution using Shared Resource with Improper Synchron= ization ('Race Condition') vulnerability. A low-privileged attacker with lo= cal access could potentially exploit this vulnerability, leading to Elevati=
    on of Privileges.</td>
    <td>2026-06-25</td>
    <td>6.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46732" target=3D= "_blank" rel=3D"noopener">CVE-2026-46732</a></td>
    </tr>

    <td class=3D"vendor-product">Dell--Wyse Management Suite (WMS)</td>
    <td>Dell Wyse Management Suite (WMS), versions prior to WMS 2605, contain a=
    Use of Default Credentials vulnerability. A high privileged attacker with = local access could potentially exploit this vulnerability, leading to Infor= mation Disclosure.</td>
    <td>2026-06-22</td>
    <td>6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44273" target=3D= "_blank" rel=3D"noopener">CVE-2026-44273</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8= .0, the Node.js compatibility TCP path checked the permission against the o= riginal hostname string before resolution and then did not re-check after r= esolution. A caller could therefore pass a numeric alias of an IP address (= for example the decimal integer 2130706433 or the hex form 0x7f000001, both=
    of which resolve to 127.0.0.1) and reach the denied destination through no= de:net.connect or node:http.request's { host, port } options form. This vul= nerability is fixed in 2.8.0.</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49411" target=3D= "_blank" rel=3D"noopener">CVE-2026-49411</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7= .12, when Deno was run in BYONM mode (nodeModulesDir: "manual"), the module=
    resolver did not validate that a package's resolved entrypoint stayed with=
    in its node_modules/&lt;pkg&gt;/ directory. A malicious package.json whose = main field contained .. segments was able to resolve to an arbitrary path o=
    n disk, and the resolver then read that file without consulting the --allow= -read allowlist. This let a require("evil-pkg") call return the contents of=
    a file that a direct Deno.readTextFileSync(...) call would have been block=
    ed from reading. This vulnerability is fixed in 2.7.12.</td> <td>2026-06-23</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49406" target=3D= "_blank" rel=3D"noopener">CVE-2026-49406</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8= .1, when fetch() was called, Deno checked the destination hostname against = --deny-net rules but did not re-check the IP addresses that hostname resolv=
    ed to. An attacker-controlled script could use a specially crafted domain n= ame that passes the hostname check yet resolves to a denied IP, bypassing t=
    he network restriction entirely. This vulnerability is fixed in 2.8.1.</td> <td>2026-06-23</td>
    <td>5.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49859" target=3D= "_blank" rel=3D"noopener">CVE-2026-49859</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8= .1, when a WebSocket connection was opened, Deno checked the destination ho= stname against --deny-net rules but did not re-check the IP addresses that = hostname resolved to. An attacker-controlled script could use a specially c= rafted domain name that passes the hostname check yet resolves to a denied = IP, bypassing the network restriction entirely. This vulnerability is fixed=
    in 2.8.1.</td>
    <td>2026-06-23</td>
    <td>5.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49860" target=3D= "_blank" rel=3D"noopener">CVE-2026-49860</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8= .1, environment access is gated by the env permission. You can deny it with=
    --deny-env, or restrict it to a specific allowlist with --allow-env=3DFOO,= BAR. The expectation is that a program running without env permission canno=
    t change process.env. process.loadEnvFile() (the Node-compatible API for lo= ading variables from a .env file) does not honor this. It only checks that = the program has read permission for the dotenv file, then writes every key =
    in that file into the process environment - even when env access is denied.=
    In effect, --allow-read plus a writable or attacker-controlled .env file i=
    s enough to defeat --deny-env. This vulnerability is fixed in 2.8.1.</td> <td>2026-06-23</td>
    <td>5.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49983" target=3D= "_blank" rel=3D"noopener">CVE-2026-49983</a></td>
    </tr>

    <td class=3D"vendor-product">denoland--deno</td>
    <td>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7= .5, a Deno program that opens a client WebSocket connection could be crashe=
    d by the remote server. While handling the WebSocket handshake response, De=
    no parsed the Sec-WebSocket-Protocol and Sec-WebSocket-Extensions response = headers in a way that assumed their bytes were always printable ASCII. A re= sponse header containing non-visible-ASCII bytes (0x80-0xFF) caused a panic=
    that aborted the entire Deno process. This vulnerability is fixed in 2.7.5= .</td>
    <td>2026-06-23</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55517" target=3D= "_blank" rel=3D"noopener">CVE-2026-55517</a></td>
    </tr>

    <td class=3D"vendor-product">Digiwin--EasyFlow .NET</td>
    <td>EasyFlow .NET developed by Digiwin has a Stored Cross-Site Scripting vu= lnerability, allowing authenticated remote attackers to inject persistent J= avaScript code executed in users' browsers upon page load.</td> <td>2026-06-22</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12580" target=3D= "_blank" rel=3D"noopener">CVE-2026-12580</a></td>
    </tr>

    <td class=3D"vendor-product">docling-project--docling</td>
    <td>Docling simplifies document processing by parsing diverse formats and p= roviding integrations with the generative AI ecosystem. From 2.45.0 until 2= .91.0, the METS-GBS backend's XML parsing and the input document format det= ection lacked security controls. An attacker could craft malicious METS-GBS=
    archives that, when processed, could read sensitive files, exhaust system = resources, or cause application crashes. This vulnerability is fixed in 2.9= 1.0.</td>
    <td>2026-06-26</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44018" target=3D= "_blank" rel=3D"noopener">CVE-2026-44018</a></td>
    </tr>

    <td class=3D"vendor-product">docling-project--docling</td>
    <td>Docling simplifies document processing by parsing diverse formats and p= roviding integrations with the generative AI ecosystem. From 2.73.0 until 2= .91.0, he LaTeX backend's handling of \includegraphics, \input, and \includ=
    e commands lacked path containment validation. Attackers could craft malici= ous LaTeX documents with path traversal sequences to read arbitrary files f= rom the file system accessible to the process, include sensitive files in t=
    he converted document output, or potentially access configuration files, cr= edentials, or other sensitive data This vulnerability is fixed in 2.91.0.</=

    <td>2026-06-24</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44022" target=3D= "_blank" rel=3D"noopener">CVE-2026-44022</a></td>
    </tr>

    <td class=3D"vendor-product">dokaninc--Dokan: AI Powered WooCommerce Multiv= endor Marketplace Solution Build Your Own Amazon, eBay, Etsy</td>
    <td>The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution - Bu= ild Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Store=
    d Cross-Site Scripting via Product SKU in all versions up to, and including=
    , 5.0.4 due to insufficient input sanitization and output escaping. This ma= kes it possible for authenticated attackers, with custom-level access and a= bove, to inject arbitrary web scripts in pages that will execute whenever a=
    user accesses an injected page. The malicious payload is delivered to site=
    visitors - including unauthenticated users - when the store search widget = inserts the unescaped AJAX response HTML into the DOM via jQuery's .html() = method.</td>
    <td>2026-06-27</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11783" target=3D= "_blank" rel=3D"noopener">CVE-2026-11783</a></td>
    </tr>

    <td class=3D"vendor-product">dokaninc--Dokan: AI Powered WooCommerce Multiv= endor Marketplace Solution Build Your Own Amazon, eBay, Etsy</td>
    <td>The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution - Bu= ild Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Insec= ure Direct Object Reference in all versions up to, and including, 5.0.4 via=
    the 'id' parameter due to missing validation on a user controlled key. Thi=
    s makes it possible for authenticated attackers, with subscriber-level acce=
    ss and above, to read any other vendor's products - including unpublished d= raft and pending listings - exposing product names, prices, SKUs, and descr= iptions belonging to other vendors. The permission callbacks for both the c= ollection endpoint and the single-item endpoint only verify the generic ven= dor capability ('dokan_view_product_menu' / 'dokandar'), which every vendor=
    holds, rather than confirming the requested author ID or product ownership=
    matches the authenticated user.</td>
    <td>2026-06-27</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11987" target=3D= "_blank" rel=3D"noopener">CVE-2026-11987</a></td>
    </tr>

    <td class=3D"vendor-product">dokku--dokku</td>
    <td>Dokku is a docker-powered PaaS. Prior to 0.38.2, the git:auth command c= reates $DOKKU_ROOT/.netrc using bash's touch command, which applies the def= ault umask of 0644. This pre-creation defeats the netrc binary's built-in 0= 600 permission setting, leaving git credentials readable by any local user = who can traverse the dokku home directory. This vulnerability is fixed in 0= .38.2.</td>
    <td>2026-06-26</td>
    <td>5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45407" target=3D= "_blank" rel=3D"noopener">CVE-2026-45407</a></td>
    </tr>

    <td class=3D"vendor-product">dornaweb--Product Specifications for Woocommer= ce</td>
    <td>The Product Specifications for WooCommerce plugin for WordPress is vuln= erable to unauthorized modification, creation, and deletion of data in vers= ions up to and including 0.8.9. This is due to a missing capability check a=
    nd missing nonce verification in the __invoke() methods of the AttributeGro= upController and AttributeController classes, which are bound to the 'dwps_= modify_groups' and 'dwps_modify_attributes' AJAX actions. This makes it pos= sible for authenticated attackers, with Subscriber-level access and above, =
    to create, edit, and delete arbitrary product specification groups and attr= ibutes (taxonomy terms in the 'spec-group' and attribute taxonomies), corru= pting business data and impacting the site's frontend display.</td> <td>2026-06-27</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11364" target=3D= "_blank" rel=3D"noopener">CVE-2026-11364</a></td>
    </tr>

    <td class=3D"vendor-product">Dynabook Inc.--Generic IO &amp; Memory Access = driver</td>
    <td>Generic IO &amp; Memory Access driver for PCs provided by TOSHIBA CORPO= RATION and Dynabook Inc. exposes its IOCTL with insufficient access control=
    . A logged-in user with no administrative privilege may access physical mem= ory.</td>
    <td>2026-06-25</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56129" target=3D= "_blank" rel=3D"noopener">CVE-2026-56129</a></td>
    </tr>

    <td class=3D"vendor-product">earendil-works--pi</td>
    <td>Pi is a minimal terminal coding harness. Pi before 0.79.0 loaded projec= t-local configuration and resources from a repository's .pi directory witho=
    ut first asking the user to trust that repository. This included project-lo= cal extensions, which are executable TypeScript or JavaScript modules loade=
    d into the Pi process. An attacker who controls a repository could place Pi= -specific project resources in that repository. If a user then started Pi f= rom that working tree, the project-local extension code could run with the = same privileges as the local Pi process without the user having a convenien=
    t way to make a trust decision. This vulnerability is fixed in 0.79.0.</td> <td>2026-06-23</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54325" target=3D= "_blank" rel=3D"noopener">CVE-2026-54325</a></td>
    </tr>

    <td class=3D"vendor-product">Eclipse Foundation--Eclipse Open VSX</td>
    <td>Open VSX Registry does not sanitize SVG files uploaded as extension ico=
    ns prior to storage, and serves them with Content-Type: image/svg+xml witho=
    ut security headers such as Content-Security-Policy or Content-Disposition:=
    attachment. This allows an attacker to publish an extension with a malicio=
    us SVG icon and achieve stored cross-site scripting (XSS) when a user navig= ates directly to the icon URL. On deployments using local storage, script e= xecution occurs within the Open VSX application origin, enabling session hi= jacking, authentication token theft, and unauthorized extension publishing.=
    On deployments backed by external storage (such as open-vsx.org with an S3= -backed CDN), execution is confined to the storage origin, reducing impact = but still permitting phishing attacks and credential harvesting through att= acker-crafted pages.</td>
    <td>2026-06-23</td>
    <td>4.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-4983" target=3D"= _blank" rel=3D"noopener">CVE-2026-4983</a></td>
    </tr>

    <td class=3D"vendor-product">Elementor--Elementor Website Builder</td> <td>Contributor Sensitive Data Exposure in Elementor Website Builder &lt;=
    =3D 4.1.3 versions.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57619" target=3D= "_blank" rel=3D"noopener">CVE-2026-57619</a></td>
    </tr>

    <td class=3D"vendor-product">eLightUp--Slim SEO</td>
    <td>Contributor Broken Access Control in Slim SEO &lt;=3D 4.6.2 versions.</=

    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57429" target=3D= "_blank" rel=3D"noopener">CVE-2026-57429</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. From 1.26.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, the = envoy.filters.http.grpc_stats filter crashes (null pointer dereference / se= gfault) when a Connect protocol request (Content-Type: application/connect+= proto or application/connect+json) hits a direct_response route. A single u= nauthenticated HTTP request crashes the Envoy process. This vulnerability i=
    s fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47204" target=3D= "_blank" rel=3D"noopener">CVE-2026-47204</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. From 1.34.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, Envo=
    y crashes if an ext_proc server sends a single gRPC message containing mult= iple, specially crafted ProcessingResponse messages. This can occur when th=
    e first response in the batch causes the gRPC stream object to be destroyed=
    , leading to a use-after-free error when Envoy attempts to process subseque=
    nt responses in the same gRPC message. This vulnerability is fixed in 1.35.= 13, 1.36.9, 1.37.5, and 1.38.3.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47207" target=3D= "_blank" rel=3D"noopener">CVE-2026-47207</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, the OAuth2 HT=
    TP filter's encrypt()/decrypt() functions use AES-256-CBC without an authen= tication tag (no HMAC, no AEAD). The /callback endpoint returns HTTP 302 on=
    successful decryption and HTTP 401 on padding failure, creating a padding = oracle. An attacker who obtains the encrypted CodeVerifier cookie can recov=
    er the plaintext PKCE code_verifier in ~6,200 requests (~100 seconds), then=
    exchange it with a stolen authorization code to obtain the victim's access=
    token. This vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, and 1.38.1.= </td>
    <td>2026-06-26</td>
    <td>6.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47775" target=3D= "_blank" rel=3D"noopener">CVE-2026-47775</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. From 1.36.0 until 1.36.9, 1.37.5, and 1.38.3, a Use-After-F= ree (UAF) vulnerability leading to a sudden segmentation fault exists in En= voy's ext_authz HTTP filter when processing per-route authorization overrid=
    es concurrently with rapid downstream client disconnects. During standard r= equest lifecycles, Envoy instantiates the ext_authz filter with a foundatio= nal authorization client object (client_). If a matched route dictates a dy= namic per-route HTTP or gRPC authorization service override, the filter gen= erates a localized client. In the vulnerable implementation, this transient=
    client aggressively overwrote the default client_ unique pointer by execut= ing client_ =3D std::move(per_route_client). When a client rapidly establis= hes and subsequently tears down a stream (such as rapidly refreshing a prot= ected WebSocket endpoint), the downstream triggers the ConnectionManagerImp= l::doDeferredStreamDestroy() -&gt; ActiveStream::onResetStream() lifecycle.=
    Envoy immediately sequences Filter::onDestroy() in an attempt to securely = abort dispatched asynchronous authorization check transactions via client_-= &gt;cancel(). By destructing the default client abruptly during initiateCal=
    l, a memory lifecycle misalignment occurs within the async client manager. = The stream teardown fails to reliably track and cancel the dynamically boun=
    d asynchronous authorization tasks, orchestrating a sequence where a late a= synchronous callback from the network evaluates against a heavily destroyed=
    ActiveStream validation span, generating a UAF process crash. This vulnera= bility is fixed in 1.36.9, 1.37.5, and 1.38.3.</td>
    <td>2026-06-26</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47205" target=3D= "_blank" rel=3D"noopener">CVE-2026-47205</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. From 1.18.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, the = router filter contains a null pointer dereference vulnerability when handli=
    ng HTTP 303 (See Other) internal redirects for body-less non-GET/HEAD reque= sts. When a POST, PUT, DELETE, or PATCH request without a body is sent to a=
    route configured with internal redirect policy that includes 303 in redire= ct_response_codes, and the upstream responds with HTTP 303, the redirect ha= ndling code attempts to drain a request body buffer that was never allocate=
    d. This results in a segmentation fault that crashes the entire Envoy proce= ss. When route configured with internal_redirect_policy including 303 in re= direct_response_codes and upstream must return HTTP 303 response, an unauth= enticated attacker can exploit this to cause complete denial of service, te= rminating all active connections. This vulnerability is fixed in 1.35.13, 1= .36.9, 1.37.5, and 1.38.3.</td>
    <td>2026-06-26</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47221" target=3D= "_blank" rel=3D"noopener">CVE-2026-47221</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. From 1.37.0 until 1.37.5 and 1.38.3, the HTTP OAuth2 filter=
    (envoy.filters.http.oauth2) can leave an in-flight async token exchange at= tached to a downstream stream that has already been torn down. A late Async= Client completion can still invoke OAuth2Filter methods that use StreamDeco= derFilterCallbacks after that object's lifetime has ended, causing undefine=
    d behavior, worker crashes (availability loss), and use-after-free / invali= d-vptr failures under AddressSanitizer. This is a memory-safety / lifetime = issue in the data plane, not a trivial config bug. Remote code execution is=
    not claimed here; the primary demonstrated impact is DoS via crash and UB;=
    any further impact would be deployment- and allocator-dependent. This vuln= erability is fixed in 1.37.5 and 1.38.3.</td>
    <td>2026-06-26</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48090" target=3D= "_blank" rel=3D"noopener">CVE-2026-48090</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, in cases wher=
    e UDP DNS filter is configured with local resolution containing a name with=
    the length of 255 octets or remote resolution for a name of 255 octets lon=
    g can complete successfully, a query with such name will result in abnormal=
    process termination. The abnormal process termination is triggered by an i= nvalid runtime precondition that the query name is strictly less than 255 o= ctets, contradicting DNS specification rfc1035#section-2.3.4 that the name = can be 255 or less octets. This vulnerability is fixed in 1.35.11, 1.36.7, = 1.37.3, and 1.38.1.</td>
    <td>2026-06-26</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48497" target=3D= "_blank" rel=3D"noopener">CVE-2026-48497</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. From 1.34.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, a vu= lnerability exists in Envoy's TCP StatsD sink (TcpStatsdSink), where the th= read-local flusher buffer can be overflowed by exceptionally long statistic=
    names (e.g., &gt;16KiB). During formatting, TcpStatsdSink reserves a singl=
    e contiguous memory slice of 16KiB (FLUSH_SLICE_SIZE_BYTES). If formatting =
    a single metric exceeds the remaining capacity, the flusher initiates a buf= fer rotation but incorrectly continues to allocate another fixed 16KiB slic=
    e. If an attacker can trigger a statistic name longer than 16KiB-for exampl=
    e, by sending an HTTP or gRPC request with an extremely long request path (= :path) that is recorded by the grpc_stats filter configured with stats_for_= all_methods: true-the flusher will attempt to copy the metric name using me= mcpy operations beyond the allocated heap buffer boundaries. This leads to =
    a heap write overflow, which can cause immediate denial-of-service (process=
    crash) or potential remote code execution (RCE). This vulnerability is fix=
    ed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3.</td>
    <td>2026-06-26</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48706" target=3D= "_blank" rel=3D"noopener">CVE-2026-48706</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. From 1.34.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, PROX=
    Y Protocol v2 header generator emits TLVs beyond the maximum length of 6553=
    5 bytes, causing a mismatch between bytes written and the length field in t=
    he header. This can result in smuggled bytes on the upstream request. This = vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3.</td> <td>2026-06-26</td>
    <td>4.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47692" target=3D= "_blank" rel=3D"noopener">CVE-2026-47692</a></td>
    </tr>

    <td class=3D"vendor-product">envoyproxy--envoy</td>
    <td>Envoy is an open source edge and service proxy designed for cloud-nativ=
    e applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, a structural = flaw was identified in DefaultCertValidator::verifySubjectAltName where the=
    extracted DNS SAN string is cast to a C-style string using .c_str() before=
    being passed to the Utility::dnsNameMatch() algorithm. If the attacker ser= ves a certificate with a dNSName SAN containing an embedded NUL byte, the h= elper Utility::generalNameAsString captures the complete string including t=
    he NUL. However, when .c_str() evaluates it, implicit conversion to absl::s= tring_view inside dnsNameMatch relies on strlen(), prematurely truncating t=
    he evaluation context. Envoy evaluates trucated string against the exact re= quired config_san match and returns true, thereby successfully validating t=
    he string with the Nul byte for an upstream routing. This vulnerability is = fixed in 1.35.11, 1.36.7, 1.37.3, and 1.38.1.</td>
    <td>2026-06-26</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47778" target=3D= "_blank" rel=3D"noopener">CVE-2026-47778</a></td>
    </tr>

    <td class=3D"vendor-product">EVoke--EVoke CSMS</td>
    <td>Charging station authentication identifiers are publicly accessible via=
    web-based mapping platforms.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44622" target=3D= "_blank" rel=3D"noopener">CVE-2026-44622</a></td>
    </tr>

    <td class=3D"vendor-product">expresstech--Quiz and Survey Master (QSM) Easy=
    Quiz and Survey Maker</td>
    <td>The Quiz and Survey Master (QSM) - Easy Quiz and Survey Maker plugin fo=
    r WordPress is vulnerable to authorization bypass in all versions up to, an=
    d including, 11.1.4. This is due to the plugin not properly verifying that =
    a user is authorized to perform an action. This makes it possible for authe= nticated attackers, with contributor-level access and above, to create, mod= ify, and delete quiz output templates stored in the mlw_quiz_output_templat=
    es database table, including storing unsanitized HTML content such as arbit= rary script tags.</td>
    <td>2026-06-27</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9233" target=3D"= _blank" rel=3D"noopener">CVE-2026-9233</a></td>
    </tr>

    <td class=3D"vendor-product">fabricjs--fabric.js</td>
    <td>Fabric.js is a Javascript HTML5 canvas library. Prior to 7.4.0, a poten= tial Cross-Site Scripting (XSS) vulnerability exists in Fabric.js due to im= proper escaping of user-controlled input during SVG serialization via the t= oSVG() method. Specifically, the color field within the colorStops array of=
    a fabric.Gradient object is not properly escaped when converted into SVG &= lt;stop&gt; elements. If an application renders the generated SVG string in=
    to the DOM, this may allow an attacker to inject arbitrary HTML/SVG and exe= cute JavaScript in the victim's browser. This vulnerability is fixed in 7.4= .0.</td>
    <td>2026-06-22</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44311" target=3D= "_blank" rel=3D"noopener">CVE-2026-44311</a></td>
    </tr>

    <td class=3D"vendor-product">FasterXML--jackson-databind</td> <td>jackson-databind contains the general-purpose data-binding functionalit=
    y and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3= .1.4, UnwrappedPropertyHandler.processUnwrappedCreatorProperties() replays = buffered JSON into creator parameters but never consults prop.visibleInView= (activeView). The normal property-based creator path gates creator properti=
    es on the active view, but this unwrapped-creator replay path bypasses that=
    check, so a constructor parameter annotated with both @JsonView(AdminView.= class) and @JsonUnwrapped is populated from attacker JSON even when a more = restrictive view is active. This vulnerability is fixed in 2.21.4 and 3.1.4= .</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54518" target=3D= "_blank" rel=3D"noopener">CVE-2026-54518</a></td>
    </tr>

    <td class=3D"vendor-product">FasterXML--jackson-databind</td> <td>jackson-databind contains the general-purpose data-binding functionalit=
    y and tree-model for Jackson Data Processor. From 2.0.0 until 2.18.8, 2.21.=
    4, and 3.1.4, JDKFromStringDeserializer constructed InetSocketAddress with = new InetSocketAddress(host, port), which performs eager DNS name resolution=
    for hostname inputs at deserialization time. An application that binds unt= rusted JSON into a type containing an InetSocketAddress field issues an att= acker-chosen DNS query during readValue, before any application-level valid= ation or connect logic. The fix uses InetSocketAddress.createUnresolved(hos=
    t, port), deferring DNS to an explicit connect. This vulnerability is fixed=
    in 2.18.8, 2.21.4, and 3.1.4.</td>
    <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54514" target=3D= "_blank" rel=3D"noopener">CVE-2026-54514</a></td>
    </tr>

    <td class=3D"vendor-product">FasterXML--jackson-databind</td> <td>jackson-databind contains the general-purpose data-binding functionalit=
    y and tree-model for Jackson Data Processor. From 2.8.0 until 2.18.9, 2.21.=
    5, and 3.1.4, in BeanDeserializerBase.createContextual(), per-property @Jso= nIgnoreProperties exclusions are applied by _handleByNameInclusion(), produ= cing a contextual deserializer whose BeanPropertyMap has the ignored proper= ties removed. The subsequent per-property case-insensitivity block (trigger=
    ed by @JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) rebuilds from this._= beanProperties (the original, unfiltered map) instead of contextual._beanPr= operties, then overwrites the filtered map - restoring every property _hand= leByNameInclusion had just removed. The ignored property becomes writable a= gain. This vulnerability is fixed in 2.18.9, 2.21.5, and 3.1.4.</td> <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54515" target=3D= "_blank" rel=3D"noopener">CVE-2026-54515</a></td>
    </tr>

    <td class=3D"vendor-product">FasterXML--jackson-databind</td> <td>jackson-databind contains the general-purpose data-binding functionalit=
    y and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3= .1.4, POJOPropertiesCollector._renameProperties() allows a property with @J= sonProperty("renamed") on the getter and @JsonIgnore on the setter to be re= named rather than dropped. With MapperFeature.INFER_PROPERTY_MUTATORS enabl=
    ed (default), the private backing field is retained; during deserialization=
    BeanDeserializerFactory.addBeanProps() sees hasField()=3D=3Dtrue, builds a=
    FieldProperty, and makes the backing field writable. An attacker supplying=
    the renamed JSON key writes the backing field directly, bypassing the @Jso= nIgnore on the setter. This vulnerability is fixed in 3.1.4.</td> <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54516" target=3D= "_blank" rel=3D"noopener">CVE-2026-54516</a></td>
    </tr>

    <td class=3D"vendor-product">FasterXML--jackson-databind</td> <td>jackson-databind contains the general-purpose data-binding functionalit=
    y and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3= .1.4, in BeanDeserializer._deserializeUsingPropertyBased, the active-view (= @JsonView) filter was applied only to creator properties; the regular prope= rty-buffering branch performed no prop.visibleInView(activeView) check. A c= hange making SetterlessProperty.isMerging() return true routed setterless C= ollection/Map properties through this unguarded path, so a setterless colle= ction annotated with a restricted @JsonView is populated from attacker JSON=
    even when the active view excludes it. This vulnerability is fixed in 2.21=
    .4 and 3.1.4.</td>
    <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54517" target=3D= "_blank" rel=3D"noopener">CVE-2026-54517</a></td>
    </tr>

    <td class=3D"vendor-product">filamentphp--filament</td>
    <td>Filament is a collection of full-stack components for accelerated Larav=
    el development. From filament/actions 4.0.0 until 4.11.4 and 5.6.4 and from=
    filament/tables 3.0.0 until 3.3.51, the recordSelectOptionsQuery() method = may be used to scope the options available in the Select field for AttachAc= tion and AssociateAction. However, the built-in validation rule for these f= ields did not apply the same scope. As a result, a user who can trigger the=
    se actions could tamper with the Livewire component's state and submit an o= ut-of-scope value. This vulnerability is fixed in filament/actions 4.11.4 a=
    nd 5.6.4 and filament/tables 3.3.51.</td>
    <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48067" target=3D= "_blank" rel=3D"noopener">CVE-2026-48067</a></td>
    </tr>

    <td class=3D"vendor-product">filamentphp--filament</td>
    <td>Filament is a collection of full-stack components for accelerated Larav=
    el development. From 4.0.0 until 4.11.5 and 5.6.5, the ImageColumn and Imag= eEntry components render raw database values without escaping HTML. Where t=
    he data passed to these components isn't validated, an attacker could plant=
    malicious HTML or JavaScript and achieve stored XSS that executes for user=
    s who view the table or schema. This vulnerability is fixed in 4.11.5 and 5= .6.5.</td>
    <td>2026-06-22</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48167" target=3D= "_blank" rel=3D"noopener">CVE-2026-48167</a></td>
    </tr>

    <td class=3D"vendor-product">filamentphp--filament</td>
    <td>Filament is a collection of full-stack components for accelerated Larav=
    el development. From 3.0.0 until 3.3.52, 4.11.5, and 5.6.5, any schema can = contain a file upload form field, so Filament applies Livewire's WithFileUp= loads trait to the Livewire component the schema is embedded in. However, s= ome schemas, such as the panel login form, do not require file uploads, and=
    exposing unauthenticated temporary file uploads on these components is not=
    an acceptable risk. On these components, an unauthenticated attacker could=
    upload arbitrary files to the application's temporary storage, which could=
    be abused to exhaust disk space or inflate storage costs. This vulnerabili=
    ty is fixed in 3.3.52, 4.11.5, and 5.6.5.</td>
    <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48500" target=3D= "_blank" rel=3D"noopener">CVE-2026-48500</a></td>
    </tr>

    <td class=3D"vendor-product">filamentphp--filament</td>
    <td>Filament is a collection of full-stack components for accelerated Larav=
    el development. From 4.0.0 until 4.11.5 and 5.6.5, the login page has an ob= servable timing discrepancy that allows unauthenticated attackers to enumer= ate registered email addresses. The impact is limited to disclosing whether=
    an account exists for a given email. This vulnerability is fixed in 4.11.5=
    and 5.6.5.</td>
    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48166" target=3D= "_blank" rel=3D"noopener">CVE-2026-48166</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Prior to = 2.63.6, unchecked passwords maximums allow for an arbitrarily large passwor=
    d to be passed into the login API. This spikes CPU and memory, and after te= sting, crashes, heavily lags any container created, and has even made my do= cker daemon start to send errors with status code 500 even after the contai= ner was destroyed. This vulnerability is fixed in 2.63.6.</td> <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54092" target=3D= "_blank" rel=3D"noopener">CVE-2026-54092</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise through 2.2.7 contains a SQL injection vulnerability in the imp= ortChatflows API. Due to insufficient validation of the chatflow.id value, =
    an authenticated user can supply a crafted JSON import file whose id field =
    is concatenated unsanitized into a SQL IN clause, allowing arbitrary SQL to=
    be executed, including blind and error-based extraction of data from the c= redential table.</td>
    <td>2026-06-24</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71332" target=3D= "_blank" rel=3D"noopener">CVE-2025-71332</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.1.3 validates Custom MCP stdio environment variables a= gainst a denylist using a case-sensitive comparison, so on Windows, where e= nvironment names are case-insensitive, supplying 'node_options' bypasses th=
    e NODE_OPTIONS denylist entry. An authenticated user who can configure a Cu= stom MCP node can thereby inject NODE_OPTIONS --require and execute arbitra=
    ry code in the Flowise server context.</td>
    <td>2026-06-28</td>
    <td>5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58057" target=3D= "_blank" rel=3D"noopener">CVE-2026-58057</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.1.0 (npm package flowise, versions 3.0.13 and earlier)=
    uses a weak hardcoded default value 'Secre$t' for the TOKEN_HASH_SECRET en= vironment variable in packages/server/src/enterprise/utils/tempTokenUtils.t=
    s when the variable is not configured. This secret derives the AES-256-CBC = key used to encrypt user IDs and workspace IDs in the 'meta' field of JWT t= okens. An attacker who knows the default secret can decrypt this metadata t=
    o extract internal user and workspace identifiers, and re-encrypt manipulat=
    ed values such as altered user or workspace IDs. Because the JWT signature =
    is validated separately, decrypting or tampering with this metadata does no=
    t by itself grant access, but the disclosure of internal identifiers and po= ssible metadata manipulation could aid privilege escalation or unauthorized=
    data access.</td>
    <td>2026-06-24</td>
    <td>4.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56269" target=3D= "_blank" rel=3D"noopener">CVE-2026-56269</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, provid= ing only 32 iterations instead of the OWASP-recommended minimum of 10 round=
    s. Attackers can crack password hashes approximately 30 times faster with m= odern GPU hardware, potentially compromising all user accounts in a databas=
    e breach scenario.</td>
    <td>2026-06-24</td>
    <td>4.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56272" target=3D= "_blank" rel=3D"noopener">CVE-2026-56272</a></td>
    </tr>

    <td class=3D"vendor-product">Fortra--File Integrity Monitoring (FIM)</td> <td>Fortra File Integrity Monitoring (FIM), formerly Tripwire Enterprise, v= ersions prior to 9.4.0.1 contain a stored cross-site scripting (XSS) vulner= ability in the Asset View UI component. An authenticated user with sufficie=
    nt privileges to create or modify affected node or database configuration f= ields could store script content that may be rendered as HTML instead of sa= fely escaped text when the affected Asset View UI content is displayed.</td=

    <td>2026-06-23</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12163" target=3D= "_blank" rel=3D"noopener">CVE-2026-12163</a></td>
    </tr>

    <td class=3D"vendor-product">Fortra--File Integrity Monitoring (FIM)</td> <td>Fortra File Integrity Monitoring (FIM), formerly Tripwire Enterprise, v= ersions prior to 9.4.0 may assign incorrect or elevated effective permissio=
    ns to users created by the=C2=A0tetool import=C2=A0command while FIM is run= ning, particularly when the import also creates or changes roles or role-pe= rmission relationships.</td>
    <td>2026-06-23</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12164" target=3D= "_blank" rel=3D"noopener">CVE-2026-12164</a></td>
    </tr>

    <td class=3D"vendor-product">freedesktop.org--libslirp</td>
    <td>An out-of-bounds heap read and integer underflow in the TCP urgent data=
    handling (sosendoob) in freedesktop.org libslirp version before v4.9.2 on = hypervisor host environments (e.g., QEMU) allows a privileged guest VM atta= cker (root or CAP_NET_RAW) to leak gigabytes of sensitive host-process heap=
    memory via sending crafted TCP segments with manipulated URG flags and urg= ent pointers (ti_urp).</td>
    <td>2026-06-24</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9539" target=3D"= _blank" rel=3D"noopener">CVE-2026-9539</a></td>
    </tr>

    <td class=3D"vendor-product">FunnelKit--FunnelKit Payment Gateway for Strip=
    e WooCommerce</td>
    <td>Unauthenticated Cross Site Request Forgery (CSRF) in FunnelKit Payment = Gateway for Stripe WooCommerce &lt;=3D 1.14.0.3 versions.</td> <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57635" target=3D= "_blank" rel=3D"noopener">CVE-2026-57635</a></td>
    </tr>

    <td class=3D"vendor-product">Gemini Labs--Site Reviews</td>
    <td>Subscriber Sensitive Data Exposure in Site Reviews &lt;=3D 8.0.11 versi= ons.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57318" target=3D= "_blank" rel=3D"noopener">CVE-2026-57318</a></td>
    </tr>

    <td class=3D"vendor-product">GeoVision Inc.--GeoVision</td>
    <td>A memory corruption vulnerability exists in the GV-Cloud functionality =
    of GeoVision GV-VMS V20 20.0.2.=C2=A0 A specially crafted network request c=
    an lead to a denial of service. An attacker can impersonate the legitimate = server to trigger this vulnerability.</td>
    <td>2026-06-24</td>
    <td>6.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12488" target=3D= "_blank" rel=3D"noopener">CVE-2026-12488</a></td>
    </tr>

    <td class=3D"vendor-product">GhozyLab--Image Carousel</td>
    <td>Contributor Cross Site Scripting (XSS) in Image Carousel &lt;=3D 1.0.0.=
    41 versions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-68074" target=3D= "_blank" rel=3D"noopener">CVE-2025-68074</a></td>
    </tr>

    <td class=3D"vendor-product">github--github-mcp-server</td>
    <td>GitHub MCP Server is GitHub's official MCP Server. From 0.22.0 until 1.= 1.2, when running in HTTP mode with --lockdown-mode enabled, the RepoAccess= Cache is implemented as a process-global singleton initialized with the fir=
    st authenticated user's GraphQL client. All subsequent requests from differ= ent users share this singleton and their lockdown-related GraphQL queries a=
    re executed using the first user's credentials. The singleton is never upda= ted to reflect later users' tokens. This vulnerability is fixed in 1.1.2.</=

    <td>2026-06-26</td>
    <td>6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48529" target=3D= "_blank" rel=3D"noopener">CVE-2026-48529</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab EE affecting all versions from=
    13.11 prior to 18.11.6, 19.0 prior to 19.0.3, and 19.1 prior to 19.1.1 in = which incorrect authorization in DAST site profile management could allow a=
    user with Developer role to exfiltrate DAST site profile secrets under cer= tain conditions.</td>
    <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11379" target=3D= "_blank" rel=3D"noopener">CVE-2026-11379</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab CE/EE affecting all versions f= rom 17.5 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that un= der certain conditions could have allowed an unauthenticated user to view c= onfidential issue references on public projects due to improper authorizati=
    on checks.</td>
    <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-2238" target=3D"= _blank" rel=3D"noopener">CVE-2026-2238</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab EE affecting all versions from=
    18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under=
    certain conditions could have allowed an authenticated user to read or mod= ify another group's virtual registry cleanup policy settings without author= ization.</td>
    <td>2026-06-25</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-5309" target=3D"= _blank" rel=3D"noopener">CVE-2026-5309</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab CE/EE affecting all versions f= rom 14.8 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that un= der certain conditions could have allowed an authenticated user to conceal = content within a Snippet due to improper input validation.</td> <td>2026-06-25</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-1606" target=3D"= _blank" rel=3D"noopener">CVE-2026-1606</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab CE/EE affecting all versions f= rom 13.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that un= der certain conditions could have allowed an authenticated user with Report= er-level group permissions to view package metadata from projects with the = Package Registry disabled due to incorrect authorization checks in the grou=
    p packages feature.</td>
    <td>2026-06-25</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-5796" target=3D"= _blank" rel=3D"noopener">CVE-2026-5796</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab CE/EE affecting all versions f= rom 17.11 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that u= nder certain conditions could have allowed an authenticated user with devel= oper-role permissions to bypass package protection rules and overwrite prot= ected Maven package metadata due to incorrect authorization checks.</td> <td>2026-06-25</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-5952" target=3D"= _blank" rel=3D"noopener">CVE-2026-5952</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab CE/EE affecting all versions f= rom 9.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that und=
    er certain conditions could have allowed sensitive information to be writte=
    n to application logs due to insufficient filtering in a CI/CD API endpoint= .</td>
    <td>2026-06-25</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8330" target=3D"= _blank" rel=3D"noopener">CVE-2026-8330</a></td>
    </tr>

    <td class=3D"vendor-product">GNU--libidn</td>
    <td>GNU libidn before 1.44 is prone to out-of-bounds reads of=C2=A0uninitia= lized memory in the ToUnicode APIs because of mishandling in=C2=A0idna_to_u= nicode_internal. The affected code is not present in libidn2.</td> <td>2026-06-23</td>
    <td>4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57053" target=3D= "_blank" rel=3D"noopener">CVE-2026-57053</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, passwo= rd-reset tokens are generated using conf.Auth.ActivateCodeLives (the accoun= t-activation lifetime), not conf.Auth.ResetPasswordCodeLives. The token lif= etime is baked into the token itself at generation time and is re-extracted=
    from the token at verification time, making RESET_PASSWORD_CODE_LIVES irre= levant to actual enforcement. When an administrator configures a shorter re= set window (e.g., 10 minutes) for compliance or security reasons, reset tok= ens remain exploitable for the full activation lifetime instead, while the = reset email falsely advertises the shorter expiry. This vulnerability is fi= xed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>6.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52809" target=3D= "_blank" rel=3D"noopener">CVE-2026-52809</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, an ope=
    n redirect vulnerability exists in Gogs where attacker-controlled redirect_=
    to parameters can bypass validation, allowing redirection to arbitrary exte= rnal sites. All redirects in Gogs that are validated via the IsSameSite fun= ction are vulnerable. The function only inspects the first two characters o=
    f the URL string. This check fails to account for directory traversal seque= nces followed by backslashes. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52802" target=3D= "_blank" rel=3D"noopener">CVE-2026-52802</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, a mali= cious user with rights to create a new file on a repository or wiki page ca=
    n trigger a denial of service condition in which the pages containing the l= isting of files will return HTTP error 500 and render the web interface unu= sable for the repository or wiki. The issue is present in file internal/rou= te/repo/wiki.go and internal/route/repo/view.go where the pages try to reco= ver commit information. If errors are returned while recovering commit info= rmation, the page will return a 500 error and stop rendering, resulting in =
    a denial of service. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>4.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-64719" target=3D= "_blank" rel=3D"noopener">CVE-2025-64719</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. In 0.14.3 and earlier, = any authenticated user can watch a private repository they have no access t=
    o, because the access check in the Watch API handler is inverted. The code = checks if repoCtx.ViewerCanRead() (returns 404 when the user CAN read) inst= ead of if !repoCtx.ViewerCanRead() (return 404 when the user CANNOT read). = Once watching, the attacker's dashboard activity feed shows commit messages=
    , branch names, issue titles, and PR details from the private repository. I=
    f email notifications are enabled, the attacker also receives emails contai= ning issue and comment content.</td>
    <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52795" target=3D= "_blank" rel=3D"noopener">CVE-2026-52795</a></td>
    </tr>

    <td class=3D"vendor-product">gophish--gophish</td>
    <td>Gophish through 0.12.1 contains a denial of service vulnerability that = allows authenticated users with the User role to exhaust server memory by u= ploading a crafted Office document as an email template attachment. The App= lyTemplate() function in models/attachment.go processes Office documents as=
    ZIP archives and calls ioutil.ReadAll() on each contained file entry witho=
    ut enforcing size restrictions on uncompressed content, allowing a zip bomb=
    payload to expand to several gigabytes in memory and cause the process to =
    be terminated by the operating system.</td>
    <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39904" target=3D= "_blank" rel=3D"noopener">CVE-2026-39904</a></td>
    </tr>

    <td class=3D"vendor-product">gpriday--Page Builder by SiteOrigin</td>
    <td>The Page Builder by SiteOrigin plugin for WordPress is vulnerable to St= ored Cross-Site Scripting via panels_data Parameter in all versions up to, = and including, 2.34.3 due to insufficient input sanitization and output esc= aping. This makes it possible for authenticated attackers, with Contributor= -level access and above, to inject arbitrary web scripts in pages that will=
    execute whenever a user accesses an injected page. This is possible becaus=
    e the nonce and edit_post capability checks enforced during save are both s= atisfied by Contributor-level users for their own posts, and the panels_dat=
    a value is stored as post meta - outside the scope of WordPress's unfiltere= d_html carve-out - meaning no wp_kses fallback prevents the unsanitized WP_= Widget_Custom_HTML content from being persisted and later rendered verbatim=
    on the frontend.</td>
    <td>2026-06-27</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13295" target=3D= "_blank" rel=3D"noopener">CVE-2026-13295</a></td>
    </tr>

    <td class=3D"vendor-product">Grafana--Grafana OSS</td>
    <td>The Tempo and Loki datasource plugins construct backend HTTP requests b=
    y interpolating user-supplied input into URL paths without sanitization, en= abling path traversal. A Viewer-role user can: (1) capture admin-configured=
    datasource credentials (secureJsonData custom headers) by traversing to an=
    attacker-controlled endpoint, (2) invoke state-changing admin endpoints on=
    Tempo (e.g. /flush, /shutdown), and (3) exfiltrate internal service data v=
    ia Loki's CallResource which returns full HTTP response bodies.</td> <td>2026-06-22</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10601" target=3D= "_blank" rel=3D"noopener">CVE-2026-10601</a></td>
    </tr>

    <td class=3D"vendor-product">Grav--Grav</td>
    <td>Grav before 2.0.0-beta.2 contains an XML external entity injection vuln= erability in SVG file upload processing that allows authenticated attackers=
    to read arbitrary files. The application uses simplexml_load_string withou=
    t disabling external entity loading, enabling attackers to inject XXE paylo= ads via malicious SVG files to exfiltrate sensitive data.</td> <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56701" target=3D= "_blank" rel=3D"noopener">CVE-2026-56701</a></td>
    </tr>

    <td class=3D"vendor-product">Grav--Grav</td>
    <td>Grav before 1.6.30 contains a cross-site scripting vulnerability in the=
    Admin plugin page editor default security configuration. Privileged users = with page editing capabilities can inject malicious scripts to execute arbi= trary code and install malicious plugins for system access.</td> <td>2026-06-25</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2020-37256" target=3D= "_blank" rel=3D"noopener">CVE-2020-37256</a></td>
    </tr>

    <td class=3D"vendor-product">GravityKit--GravityView</td>
    <td>Unauthenticated Insecure Direct Object References (IDOR) in GravityView=
    &lt;=3D 3.0.0 versions.</td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57665" target=3D= "_blank" rel=3D"noopener">CVE-2026-57665</a></td>
    </tr>

    <td class=3D"vendor-product">GravityMore--Gravity Bookings</td>
    <td>The Gravity Forms Booking plugin for WordPress is vulnerable to time-ba= sed SQL Injection via the 'staff_id' parameter in all versions up to, and i= ncluding, 2.7.1 due to insufficient escaping on the user supplied parameter=
    and lack of sufficient preparation on the existing SQL query. This makes i=
    t possible for authenticated attackers, with Subscriber-level access and ab= ove, to append additional SQL queries into already existing queries that ca=
    n be used to extract sensitive information from the database.</td> <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-2508" target=3D"= _blank" rel=3D"noopener">CVE-2026-2508</a></td>
    </tr>

    <td class=3D"vendor-product">grokability--snipe-it</td>
    <td>Snipe-IT is an IT asset/license management system. In versions prior to=
    8.6.0, a user with only users.edit can send a PATCH to /api/v1/users/{thei= r_own_id} and grant themselves any permission except admin and superuser - = for example `assets.view`, `assets.create`, `reports.view`, import, etc. Th=
    e issue is patched in version 8.6.0.</td>
    <td>2026-06-23</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48493" target=3D= "_blank" rel=3D"noopener">CVE-2026-48493</a></td>
    </tr>

    <td class=3D"vendor-product">guzzle--guzzle</td>
    <td>Guzzle is an extensible PHP HTTP client. Prior to 7.12.1, in certain co= nfigurations, traffic expected to be protected by TLS on the hop to the pro=
    xy is transmitted in cleartext. Proxy authentication credentials (the Proxy= -Authorization header, proxy userinfo in the proxy URL, or CURLOPT_PROXYUSE= RPWD) are sent without encryption, and the CONNECT target host and port for=
    tunneled HTTPS requests are exposed. The built-in cURL handlers (GuzzleHtt= p\Handler\CurlHandler and GuzzleHttp\Handler\CurlMultiHandler, used by defa= ult whenever the PHP cURL extension is available) accept an https:// proxy.=
    libcurl older than 7.50.2 silently treats an https:// proxy as a plaintext=
    http:// proxy. The TLS connection to the proxy is never established, and t=
    he proxy leg is cleartext with no error or warning. An application is affec= ted when it sends requests through one of the built-in cURL handlers, confi= gures an https:// proxy expecting the proxy connection itself to be encrypt= ed, and runs with libcurl older than 7.50.2. This vulnerability is fixed in=
    7.12.1.</td>
    <td>2026-06-23</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55568" target=3D= "_blank" rel=3D"noopener">CVE-2026-55568</a></td>
    </tr>

    <td class=3D"vendor-product">guzzle--guzzle</td>
    <td>Guzzle is an extensible PHP HTTP client. Prior to 7.12.1, CookieJar inc= orrectly accepts cookies with a dot-only Domain attribute and whitespace-pa= dded variants. SetCookie::matchesDomain() removes leading dots from the coo= kie domain, normalizing dot-only values to the empty string; SetCookie::val= idate() only rejected a strictly empty domain, so these cookies could be st= ored and the empty normalized domain was treated as matching any request ho= st. An attacker-controlled origin that an application requests with a share=
    d cookie jar can therefore set a cookie that Guzzle later sends to unrelate=
    d hosts using the same jar. This may allow cookie injection or session fixa= tion against downstream services, depending on how those services interpret=
    the injected cookie. This vulnerability is fixed in 7.12.1.</td> <td>2026-06-23</td>
    <td>5.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55767" target=3D= "_blank" rel=3D"noopener">CVE-2026-55767</a></td>
    </tr>

    <td class=3D"vendor-product">guzzle--psr7</td>
    <td>guzzlehttp/psr7 is a PSR-7 HTTP message library implementation in PHP. = Prior to 2.12.1, guzzlehttp/psr7 did not reject CR/LF characters in certain=
    first-party HTTP start-line fields: the request method, protocol version, = and response reason phrase. If an application placed attacker-controlled da=
    ta into one of those fields and later serialized the PSR-7 message as raw H= TTP/1.x, for example with Message::toString() or an equivalent serializer, = the serialized message could contain attacker-controlled header lines. The = issue can also be reached through Message::parseRequest() or Message::parse= Response() when malformed raw messages are parsed into first-party PSR-7 ob= jects and then serialized again. Creating or modifying a Request, Response,=
    or other PSR-7 object alone is not sufficient. The issue requires the malf= ormed message to be serialized and written to the network, forwarded, repla= yed, or otherwise processed by software that does not independently reject = the malformed start line. This vulnerability is fixed in 2.12.1.</td> <td>2026-06-23</td>
    <td>4.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55766" target=3D= "_blank" rel=3D"noopener">CVE-2026-55766</a></td>
    </tr>

    <td class=3D"vendor-product">halo-dev--halo</td>
    <td>Halo is an open source website building tool. Prior to 2.24.3, a path t= raversal vulnerability in the backup download endpoint allows authenticated=
    administrators to read arbitrary files from the server filesystem. The bac= kup download endpoint (GET /apis/console.api.migration.halo.run/v1alpha1/ba= ckups/{name}/files/{filename}) in MigrationServiceImpl.download() resolves = the backup filename via Path.resolve() without validating that the resolved=
    path stays within the designated backups directory. Also, the Backup creat= ion endpoint (POST /apis/migration.halo.run/v1alpha1/backups) does not sani= tize the status fields during creation This vulnerability is fixed in 2.24.= 3.</td>
    <td>2026-06-25</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55439" target=3D= "_blank" rel=3D"noopener">CVE-2026-55439</a></td>
    </tr>

    <td class=3D"vendor-product">harmonic_design--HD Quiz</td>
    <td>The HD Quiz plugin for WordPress is vulnerable to Cross-Site Request Fo= rgery in versions 2.2.0 to 2.2.1. This is due to missing or incorrect nonce=
    validation on the hdq_validate_nonce function. This makes it possible for = unauthenticated attackers to delete or modify quizzes and questions, create=
    new quizzes, and change plugin settings via a forged request granted they = can trick a site administrator into performing an action such as clicking o=
    n a link.</td>
    <td>2026-06-27</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13422" target=3D= "_blank" rel=3D"noopener">CVE-2026-13422</a></td>
    </tr>

    <td class=3D"vendor-product">HCLSoftware--Traveler for Microsoft Outlook</t=

    <td>The HCL Traveler for Microsoft Outlook libraries are being flagged as p= otentially malicious software or an unrecognized application.</td> <td>2026-06-26</td>
    <td>6.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2024-23581" target=3D= "_blank" rel=3D"noopener">CVE-2024-23581</a></td>
    </tr>

    <td class=3D"vendor-product">HCLSoftware--Traveler for Microsoft Outlook</t=

    <td>HCL Traveler for Microsoft Outlook (HTMO) is susceptible to a sensitive=
    data exposure vulnerability which could allow an attacker to exploit appli= cation information to then attempt additional attacks and cause unknown beh= avior in the application.</td>
    <td>2026-06-27</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-59868" target=3D= "_blank" rel=3D"noopener">CVE-2025-59868</a></td>
    </tr>

    <td class=3D"vendor-product">HKUDS--OpenHarness</td>
    <td>OpenHarness ohmo gateway /resume and /summary slash commands default re= mote_invocable to True, allowing admitted remote senders to enumerate and l= oad arbitrary session snapshots by ID. Attackers can exploit this to access=
    victim snapshots containing private prompts, credentials, tool output, and=
    file paths via shared gateway channels.</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56695" target=3D= "_blank" rel=3D"noopener">CVE-2026-56695</a></td>
    </tr>

    <td class=3D"vendor-product">HKUDS--OpenHarness</td>
    <td>OpenHarness /issue and /pr_comments slash commands lack remote_invocabl= e=3DFalse protection, allowing remote channel senders to write attacker-con= trolled Markdown into project context files. Admitted remote attackers can = inject malicious content into .openharness/issue.md and .openharness/pr_com= ments.md files, which are subsequently injected into runtime system prompts=
    , persistently influencing local agent behavior.</td>
    <td>2026-06-23</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56696" target=3D= "_blank" rel=3D"noopener">CVE-2026-56696</a></td>
    </tr>

    <td class=3D"vendor-product">Hono--Hono</td>
    <td>Hono before 4.12.12 does not validate cookie names on the write path in=
    the setCookie(), serialize(), and serializeSigned() functions, allowing in= valid characters such as control characters (e.g. \r or \n) when an applica= tion passes a user-controlled cookie name. This can produce malformed Set-C= ookie header values. In modern runtimes such as Node.js and Cloudflare Work= ers, such invalid header values are rejected and cause a runtime error befo=
    re the response is sent, so header injection or response splitting could no=
    t be reproduced; the issue primarily affects correctness and robustness, re= sulting in runtime errors (availability) rather than confirmed header injec= tion.</td>
    <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56762" target=3D= "_blank" rel=3D"noopener">CVE-2026-56762</a></td>
    </tr>

    <td class=3D"vendor-product">hono--hono</td>
    <td>hono before 4.12.14 contains an html injection vulnerability in jsx ser= ver-side rendering that allows attackers to inject unintended html by using=
    malformed attribute names. Attackers can craft specially crafted attribute=
    keys containing characters like quotes or angle brackets to break html tag=
    boundaries and inject arbitrary attributes or elements.</td> <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56761" target=3D= "_blank" rel=3D"noopener">CVE-2026-56761</a></td>
    </tr>

    <td class=3D"vendor-product">honojs--hono</td>
    <td>Hono is a Web application framework that provides support for any JavaS= cript runtime. Prior to 4.12.25, the Body Limit Middleware trusts the reque= st's Content-Length header to decide whether a body is within the limit. On=
    AWS Lambda (API Gateway v1/v2, ALB, VPC Lattice, and Lambda@Edge) the body=
    is delivered fully buffered and the adapter builds the request with the cl= ient-declared Content-Length, which need not match the actual payload. A cl= ient can declare a tiny Content-Length while sending a much larger body, sl= ipping past the limit. This vulnerability is fixed in 4.12.25.</td> <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54288" target=3D= "_blank" rel=3D"noopener">CVE-2026-54288</a></td>
    </tr>

    <td class=3D"vendor-product">honojs--hono</td>
    <td>Hono is a Web application framework that provides support for any JavaS= cript runtime. Prior to 4.12.25, on Windows hosts, an encoded backslash (%5=
    C) in the request path decodes to \, which the Windows path resolver treats=
    as a separator. serve-static then resolves a single URL segment such as ad= min\secret.txt into a nested file under the root and serves it, letting an = attacker read static files meant to be protected behind prefix-mounted midd= leware. This vulnerability is fixed in 4.12.25.</td>
    <td>2026-06-22</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54286" target=3D= "_blank" rel=3D"noopener">CVE-2026-54286</a></td>
    </tr>

    <td class=3D"vendor-product">honojs--hono</td>
    <td>Hono is a Web application framework that provides support for any JavaS= cript runtime. Prior to 4.12.25, on AWS Lambda, the ALB single-header respo= nse and the VPC Lattice v2 response join multiple Set-Cookie headers into o=
    ne comma-separated value. Because commas also appear inside cookie attribut=
    es (for example Expires dates), clients cannot split the value back into in= dividual cookies and silently drop or misparse them. This vulnerability is = fixed in 4.12.25.</td>
    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54287" target=3D= "_blank" rel=3D"noopener">CVE-2026-54287</a></td>
    </tr>

    <td class=3D"vendor-product">honojs--hono</td>
    <td>Hono is a Web application framework that provides support for any JavaS= cript runtime. Prior to 4.12.25, on AWS Lambda@Edge, CloudFront delivers a = request header that appears more than once as several separate entries. The=
    adapter writes each value with Headers.set instead of Headers.append, so e= very value overwrites the previous one and only the last reaches the applic= ation. Repeated request headers such as X-Forwarded-For, Forwarded, and Via=
    are silently truncated to a single value. Request middleware sees only the=
    last value of a repeated header instead of the full chain. For application=
    s that base access control on the X-Forwarded-For chain, this can weaken or=
    alter that decision; for auditing, hop history is lost. This vulnerability=
    is fixed in 4.12.25.</td>
    <td>2026-06-22</td>
    <td>4.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54289" target=3D= "_blank" rel=3D"noopener">CVE-2026-54289</a></td>
    </tr>

    <td class=3D"vendor-product">iamranit--Advanced Contact Form 7 Compact DB</=

    <td>The Advanced Contact Form 7 - Compact DB plugin for WordPress is vulner= able to unauthorized deletion of data due to a missing capability check on = the cf7cdb_ajax_delete_user() function in versions up to, and including, 1.= 0.0. The handler is registered against both `wp_ajax_cf7cdb_delete` and `wp= _ajax_nopriv_cf7cdb_delete`, and it performs no nonce verification, no capa= bility check, and no ownership check before invoking `$wpdb-&gt;delete()` a= gainst the `wp_cf7cdb_data` table with an attacker-supplied integer ID. Thi=
    s makes it possible for unauthenticated attackers to delete arbitrary conta=
    ct form submission entries stored by the plugin by iterating sequential pri= mary-key IDs.</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12094" target=3D= "_blank" rel=3D"noopener">CVE-2026-12094</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Datacap</td>
    <td>IBM Datacap 9.1.7, 9.1.8, and 9.1.9 and IBM Datacap Navigator 9.1.7, 9.= 1.8, and 9.1.9 is vulnerable to cross-site scripting. This vulnerability al= lows an unauthenticated attacker to embed arbitrary JavaScript code in the = Web UI thus altering the intended functionality potentially leading to cred= entials disclosure within a trusted session.</td>
    <td>2026-06-22</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8059" target=3D"= _blank" rel=3D"noopener">CVE-2026-8059</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Datacap</td>
    <td>IBM Datacap 9.1.7, 9.1.8, and 9.1.9 and IBM Datacap Navigator 9.1.7, 9.= 1.8, and 9.1.9 allows an attacker to retrieve user passwords and cryptograp= hic keys from memory. Attacker can=C2=A0use the same keys to decrypt passwo= rd, gain access to the application and access sensitive=C2=A0data in the da= tabase.</td>
    <td>2026-06-22</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8636" target=3D"= _blank" rel=3D"noopener">CVE-2026-8636</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Db2 on Cloud Pak for Data and Db2 Warehou=
    se on Cloud Pak for Data</td>
    <td>IBM Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data v= ersions 4.8,5.0,5.1,5.2,5.3 could allow an authenticated user to cause a de= nial of service when creating new databases due to improper allocation of r= esources.</td>
    <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2024-54178" target=3D= "_blank" rel=3D"noopener">CVE-2024-54178</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Db2 on Cloud Pak for Data and Db2 Warehou=
    se on Cloud Pak for Data</td>
    <td>IBM Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data v= ersions 4.8, 5.0, 5.1, 5.2, 5.3 could allow a privileged user to perform op= erations and obtain sensitive information outside of their authority due to=
    improper token validation.</td>
    <td>2026-06-22</td>
    <td>6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-2669" target=3D"= _blank" rel=3D"noopener">CVE-2025-2669</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Db2 on Cloud Pak for Data and Db2 Warehou=
    se on Cloud Pak for Data</td>
    <td>IBM Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data v= ersions 4.8, 5.0, 5.1, 5.2, and 5.3 could allow an authenticated user to by= pass client-side validation and manipulate input data using man in the midd=
    le techniques.</td>
    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2023-33854" target=3D= "_blank" rel=3D"noopener">CVE-2023-33854</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Engineering Workflow Management</td>
    <td>IBM Engineering Workflow Management 7.0.2 through 7.0.2 Interim Fix 035=
    , 7.0.3 through 7.0.3 Interim Fix 017, and 7.1 through 7.1 Interim Fix 004 =
    is vulnerable to HTTP header injection, caused by improper validation of in= put by the HOST headers. This could allow an attacker to conduct various at= tacks against the vulnerable system, including cross-site scripting, cache = poisoning or session hijacking.</td>
    <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2024-51454" target=3D= "_blank" rel=3D"noopener">CVE-2024-51454</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Engineering Workflow Management</td>
    <td>IBM Engineering Workflow Management 7.0.3 through 7.0.3 Interim Fix 020=
    , and 7.1 through 7.1 Interim Fix 007 is vulnerable to cross-site scripting=
    . This vulnerability allows an authenticated user to embed arbitrary JavaSc= ript code in the Web UI thus altering the intended functionality potentiall=
    y leading to credentials disclosure within a trusted session.</td> <td>2026-06-22</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-33128" target=3D= "_blank" rel=3D"noopener">CVE-2025-33128</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--i</td>
    <td>IBM WebSphere Application Server and IBM WebSphere Application Server L= iberty are vulnerable to denial of service in the WebSphere WebServer Plug-=
    in component when an attacker can pass crafted requests to the web server.<=

    <td>2026-06-22</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10852" target=3D= "_blank" rel=3D"noopener">CVE-2026-10852</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--IBM Watson Speech Services Cartridge</td> <td>IBM Watson Speech Services Cartridge is vulnerable to Server-Side Reque=
    st Forgery (SSRF) in Sterling File Gateway, due to a flaw which may allow a=
    n authenticated attacker to send unauthorized requests from the system, pot= entially leading to network enumeration or facilitating other attacks [GHSA= -rr7j-v2q5-chgv] [CVE-2026-7253]. IBM Sterling File Gateway is used in our = speech runtimes. This vulnerabilitiy has been addressed. Please read the de= tails for remediation below.</td>
    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7253" target=3D"= _blank" rel=3D"noopener">CVE-2026-7253</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--TRIRIGA Application Platform</td>
    <td>IBM TRIRIGA Application Platform 5.0.2 through 5.0.3 is vulnerable to c= ross-site scripting. This vulnerability allows an authenticated user to emb=
    ed arbitrary JavaScript code in the Web UI thus altering the intended funct= ionality potentially leading to credentials disclosure within a trusted ses= sion.</td>
    <td>2026-06-22</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11372" target=3D= "_blank" rel=3D"noopener">CVE-2026-11372</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--WebSphere Application Server</td>
    <td>IBM WebSphere Application Server 9.0, and 8.5 and IBM WebSphere Applica= tion Server - Liberty 17.0.0.3 through 26.0.0.6 are vulnerable to a denial =
    of service, caused by sending a specially-crafted request. A remote attacke=
    r could exploit this vulnerability to cause the server to consume memory re= sources.</td>
    <td>2026-06-22</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9320" target=3D"= _blank" rel=3D"noopener">CVE-2026-9320</a></td>
    </tr>

    <td class=3D"vendor-product">itsourcecode--Hospital Management System</td> <td>A vulnerability was found in itsourcecode Hospital Management System 1.=
    0. The affected element is an unknown function of the file /ajaxmedicine.ph=
    p. The manipulation of the argument medicineid results in sql injection. It=
    is possible to launch the attack remotely. The exploit has been made publi=
    c and could be used.</td>
    <td>2026-06-28</td>
    <td>6.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13496" target=3D= "_blank" rel=3D"noopener">CVE-2026-13496</a></td>
    </tr>

    <td class=3D"vendor-product">itsourcecode--Hospital Management System</td> <td>A vulnerability was determined in itsourcecode Hospital Management Syst=
    em 1.0. The impacted element is an unknown function of the file /appointmen= t.php. This manipulation of the argument editid causes sql injection. The a= ttack can be initiated remotely. The exploit has been publicly disclosed an=
    d may be utilized.</td>
    <td>2026-06-28</td>
    <td>6.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13497" target=3D= "_blank" rel=3D"noopener">CVE-2026-13497</a></td>
    </tr>

    <td class=3D"vendor-product">itsourcecode--Hospital Management System</td> <td>A vulnerability has been found in itsourcecode Hospital Management Syst=
    em 1.0. Impacted is an unknown function of the file /adminprofile.php. The = manipulation of the argument loginid leads to sql injection. It is possible=
    to initiate the attack remotely. The exploit has been disclosed to the pub= lic and may be used.</td>
    <td>2026-06-28</td>
    <td>4.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13495" target=3D= "_blank" rel=3D"noopener">CVE-2026-13495</a></td>
    </tr>

    <td class=3D"vendor-product">jdx--mise</td>
    <td>mise manages dev tools like node, python, cmake, and terraform. From 20= 26.3.15 until 2026.6.4, mise loads github.credential_command from local pro= ject config before any trust decision, then executes that value with sh -c = when resolving a GitHub token. An attacker who can place a .mise.toml in a = repository can execute arbitrary shell commands when the victim runs a GitH= ub-related mise command and no higher-priority GitHub token environment var= iable is set. This vulnerability is fixed in 2026.6.4.</td>
    <td>2026-06-26</td>
    <td>6.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55448" target=3D= "_blank" rel=3D"noopener">CVE-2026-55448</a></td>
    </tr>

    <td class=3D"vendor-product">jdx--mise</td>
    <td>mise manages dev tools like node, python, cmake, and terraform. Prior t=
    o 2026.6.1, the mise HTTP backend builds its install symlink destination fr=
    om the raw resolved version string for non-latest versions. Normal tool ins= tall paths use the sanitized version pathname, but the HTTP backend's symli=
    nk path uses the raw value. On Unix-like systems, if that version is an abs= olute path, PathBuf::join discards the intended mise installs root. A repos= itory-controlled .tool-versions file can therefore make mise install create=
    a symlink outside the mise install tree. With bin_path, the same issue can=
    place an executable symlink under an attacker-selected absolute prefix, su=
    ch as a developer-tool prefix that is later added to PATH. This vulnerabili=
    ty is fixed in 2026.6.1.</td>
    <td>2026-06-26</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54557" target=3D= "_blank" rel=3D"noopener">CVE-2026-54557</a></td>
    </tr>

    <td class=3D"vendor-product">jegstudio--Gutenverse WordPress Blocks, Page B= uilder &amp; Site Editor</td>
    <td>The Gutenverse - WordPress Blocks, Page Builder &amp; Site Editor plugi=
    n for WordPress is vulnerable to Stored Cross-Site Scripting via admin sett= ings in all versions up to, and including, 3.8.0 due to insufficient input = sanitization and output escaping. This makes it possible for authenticated = attackers, with editor-level permissions and above, to inject arbitrary web=
    scripts in pages that will execute whenever a user accesses an injected pa= ge. This only affects multi-site installations and installations where unfi= ltered_html has been disabled.</td>
    <td>2026-06-27</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12399" target=3D= "_blank" rel=3D"noopener">CVE-2026-12399</a></td>
    </tr>

    <td class=3D"vendor-product">jellyfin--jellyfin</td>
    <td>Jellyfin is an open source self hosted media server. Prior to 10.11.9, =
    a potential XSS attack exists in Jellyfin which can allow a non-privileged = user to execute arbitrary Javascript in the context of a logged-in Administ= rative user, resulting in numerous potential issues. The Client header duri=
    ng an AuthenticateByName can contain arbitrary HTML and Javascript, which w= ill then be executed by the Administrative user when visiting the Access ta=
    b of the user in question from within the dashboard. This vulnerability is = fixed in 10.11.9.</td>
    <td>2026-06-24</td>
    <td>5.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49220" target=3D= "_blank" rel=3D"noopener">CVE-2026-49220</a></td>
    </tr>

    <td class=3D"vendor-product">JetBrains--Kotlin</td>
    <td>In JetBrains Kotlin before 2.4.20 code execution was possible via unsaf=
    e deserialization in the build cache metadata</td>
    <td>2026-06-26</td>
    <td>6.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53914" target=3D= "_blank" rel=3D"noopener">CVE-2026-53914</a></td>
    </tr>

    <td class=3D"vendor-product">JetBrains--YouTrack</td>
    <td>In JetBrains YouTrack before 2026.2.16593 improper authorisation in the=
    app configurations endpoint allowed modifying project settings</td> <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57923" target=3D= "_blank" rel=3D"noopener">CVE-2026-57923</a></td>
    </tr>

    <td class=3D"vendor-product">JetBrains--YouTrack</td>
    <td>In JetBrains YouTrack before 2026.2.16593 improper access control allow=
    ed reading users' private data via the comment templates endpoint</td> <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57921" target=3D= "_blank" rel=3D"noopener">CVE-2026-57921</a></td>
    </tr>

    <td class=3D"vendor-product">JetBrains--YouTrack</td>
    <td>In JetBrains YouTrack before 2026.2.16593 default role configuration ex= posed excessive user profile details</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57924" target=3D= "_blank" rel=3D"noopener">CVE-2026-57924</a></td>
    </tr>

    <td class=3D"vendor-product">JetBrains--YouTrack</td>
    <td>In JetBrains YouTrack before 2026.2.16593 improper access control allow=
    ed reading saved queries and tags</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57925" target=3D= "_blank" rel=3D"noopener">CVE-2026-57925</a></td>
    </tr>

    <td class=3D"vendor-product">jetmonsters--Restaurant Menu by MotoPress</td> <td>Subscriber Broken Access Control in Restaurant Menu by MotoPress &lt;=
    =3D 2.4.11 versions.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-63078" target=3D= "_blank" rel=3D"noopener">CVE-2025-63078</a></td>
    </tr>

    <td class=3D"vendor-product">JoomSky--JS Help Desk</td>
    <td>Unauthenticated Insecure Direct Object References (IDOR) in JS Help Des=
    k &lt;=3D 3.1.0 versions.</td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57652" target=3D= "_blank" rel=3D"noopener">CVE-2026-57652</a></td>
    </tr>

    <td class=3D"vendor-product">joomunited--WP Latest Posts</td>
    <td>The WP Latest Posts plugin for WordPress is vulnerable to Stored Cross-= Site Scripting via crafted image src attributes in post content in versions=
    up to, and including, 5.0.11. This is due to insufficient output escaping =
    in the field() and loop() functions, which extract the raw src attribute va= lue from &lt;img&gt; tags within post_content using a regular expression an=
    d then reconstruct new &lt;img&gt; elements or CSS background-image declara= tions by directly concatenating the unescaped value - bypassing WordPress's=
    kses filtering entirely. This makes it possible for authenticated attacker=
    s, with author-level access and above, to inject arbitrary web scripts in p= ages that will execute whenever a user accesses an injected page.</td> <td>2026-06-24</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9620" target=3D"= _blank" rel=3D"noopener">CVE-2026-9620</a></td>
    </tr>

    <td class=3D"vendor-product">joomunited--WP Meta SEO</td>
    <td>The WP Meta SEO plugin for WordPress is vulnerable to Server-Side Reque=
    st Forgery in all versions up to, and including, 4.5.18 via the 'new_link' = parameter. This makes it possible for authenticated attackers, with contrib= utor-level access and above, to make web requests to arbitrary locations or= iginating from the web application and can be used to query and modify info= rmation from internal services. The HTTP response status from outbound requ= ests is reflected back in the AJAX JSON response as status_code, providing =
    an enumeration oracle usable for probing internal hosts and cloud metadata = services.</td>
    <td>2026-06-24</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11370" target=3D= "_blank" rel=3D"noopener">CVE-2026-11370</a></td>
    </tr>

    <td class=3D"vendor-product">jotis--Blue Captcha</td>
    <td>The Blue Captcha plugin for WordPress is vulnerable to Cross-Site Reque=
    st Forgery in versions up to and including 2.0.1. This is due to missing or=
    incorrect nonce validation on the main admin panel (blcap_main_page) and o=
    n the Hall of Shame and Log subpages, which accept a 'blcap_action' / 'acti= on' parameter from $_REQUEST and perform destructive operations (plugin uni= nstall via blcap_uninstall(), log deletion via blcap_delete_logs(), Hall of=
    Shame deletion via blcap_delete_ip_db(), and adding IPs to the banned list=
    via update_option('blcap_settings')) with no wp_verify_nonce(), check_admi= n_referer(), or check_ajax_referer() calls anywhere in the codebase. This m= akes it possible for unauthenticated attackers to uninstall the plugin, del= ete audit logs, remove Hall of Shame entries, and add arbitrary IP addresse=
    s to the block list via a forged request granted they can trick a site admi= nistrator into performing an action such as clicking on a link.</td> <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10552" target=3D= "_blank" rel=3D"noopener">CVE-2026-10552</a></td>
    </tr>

    <td class=3D"vendor-product">k3s-io--k3s</td>
    <td>K3s is a fully conformant production-ready Kubernetes distribution. Pri=
    or to 1.35.3+k3s1, 1.34.6+k3s1, v1.33.10+k3s1, a path traversal vulnerabili=
    ty exists in K3s's etcd snapshot decompression functionality. Zip files con= taining archive members with maliciously crafted names can be written to ar= bitrary locations on the filesystem when an administrator restores the arch= ive as a compressed etcd snapshot. This vulnerability is fixed in 1.35.3+k3= s1, 1.34.6+k3s1, v1.33.10+k3s1.</td>
    <td>2026-06-25</td>
    <td>5.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54250" target=3D= "_blank" rel=3D"noopener">CVE-2026-54250</a></td>
    </tr>

    <td class=3D"vendor-product">kanboard--kanboard</td>
    <td>Kanboard through 1.2.52, fixed in commit 928c68a, UserViewController::r= emoveSession fails to validate the session id parameter before passing it t=
    o RememberMeSessionModel::remove, allowing authenticated users to delete ot= her users' Remember Me sessions. Attackers can enumerate sequential session=
    IDs and mass-invalidate persistent login sessions of any user, including a= dministrators, forcing re-authentication and causing denial of service.</td=

    <td>2026-06-25</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56774" target=3D= "_blank" rel=3D"noopener">CVE-2026-56774</a></td>
    </tr>

    <td class=3D"vendor-product">Kerry--BNE Testimonials</td>
    <td>Contributor Cross Site Scripting (XSS) in BNE Testimonials &lt;=3D 2.0.=
    8 versions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-68075" target=3D= "_blank" rel=3D"noopener">CVE-2025-68075</a></td>
    </tr>

    <td class=3D"vendor-product">kestra-io--kestra</td>
    <td>Kestra is an open-source, event-driven orchestration platform. Prior to=
    1.0.45 and 1.3.21, the previewFileFromExecution endpoint (GET /api/v1/{ten= ant}/executions/{executionId}/file/preview) contains an access control bypa=
    ss that allows any authenticated user to read output files from any other e= xecution within the same tenant, bypassing execution-level and namespace-le= vel isolation. This vulnerability is fixed in 1.0.45 and 1.3.21.</td> <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53577" target=3D= "_blank" rel=3D"noopener">CVE-2026-53577</a></td>
    </tr>

    <td class=3D"vendor-product">khoj-ai--khoj</td>
    <td>A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts=
    an unknown function of the file src/khoj/routers/api_chat.py of the compon= ent Conversation Sharing Handler. This manipulation of the argument convers= ation.agent causes incorrect authorization. Remote exploitation of the atta=
    ck is possible. The exploit has been published and may be used. The pull re= quest to fix this issue awaits acceptance.</td>
    <td>2026-06-28</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13508" target=3D= "_blank" rel=3D"noopener">CVE-2026-13508</a></td>
    </tr>

    <td class=3D"vendor-product">Knit Pay--UPI QR Code Payment Gateway for WooC= ommerce</td>
    <td>Customer Broken Access Control in UPI QR Code Payment Gateway for WooCo= mmerce &lt;=3D 1.6.2 versions.</td>
    <td>2026-06-25</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56023" target=3D= "_blank" rel=3D"noopener">CVE-2026-56023</a></td>
    </tr>

    <td class=3D"vendor-product">krishaweb--Advance Nav Menu Manager</td>
    <td>The Advance Nav Menu Manager plugin for WordPress is vulnerable to auth= orization bypass in all versions up to, and including, 1.3. This is due to = the plugin not properly verifying that a user is authorized to perform an a= ction. This makes it possible for authenticated attackers, with subscriber-= level access and above, to duplicate, copy, move, or publish nav_menu_item = posts via wp_insert_post(), modifying the site's navigation menus without a= uthorization.</td>
    <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8688" target=3D"= _blank" rel=3D"noopener">CVE-2026-8688</a></td>
    </tr>

    <td class=3D"vendor-product">langchain-ai--langchain</td>
    <td>LangChain is a framework for building agents and LLM-powered applicatio= ns. Prior to 1.3.9, several LangChain components that resolve filesystem pa= ths or expand search patterns do not consistently confine the resolved path=
    to the intended root directory. Affected behaviors include: a file-search = agent middleware that validates a starting directory but not the search pat= tern or the resolved target of matched files, so glob patterns and symlinks=
    can reach files outside the configured root; prompt- and chain/agent-confi= guration loaders that accept path fields and resolve them without confining=
    the result to a trusted base or rejecting symlink targets; and path-prefix=
    authorization checks that compare by string prefix without a path-segment = boundary, so a sibling path sharing the prefix is accepted. When these comp= onents receive path values, search patterns, or workspace contents influenc=
    ed by an untrusted source - including an LLM acting on untrusted input - th=
    e result can be disclosure of files outside the intended boundary. This vul= nerability is fixed in 1.3.9.</td>
    <td>2026-06-22</td>
    <td>5.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55443" target=3D= "_blank" rel=3D"noopener">CVE-2026-55443</a></td>
    </tr>

    <td class=3D"vendor-product">langflow-ai--langflow</td>
    <td>Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.9.0, Langflow is vulnerable to Path Traversal in the Kno= wledge Bases API (POST /api/v1/knowledge_bases). This occurs because user-s= upplied knowledge base names are used directly to create file paths without=
    proper sanitization or containment checks. An authenticated attacker can e= xploit this flaw to create directories and write files anywhere on the serv= er's filesystem. This vulnerability is fixed in 1.9.0.</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42867" target=3D= "_blank" rel=3D"noopener">CVE-2026-42867</a></td>
    </tr>

    <td class=3D"vendor-product">langflow-ai--langflow</td>
    <td>Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.10.0, the "Shareable Playground" (or "Public Flows" in c= ode) contains a potential arbitrary file-read vulnerability, depending on t=
    he exact flow configuration used. By making a flow public, public execution=
    of the flow is allowed. The execution request can contain a list of files = that gets read by Langflow and fed into the LLM. The files path can be any = path supported by the storage - it can be either a local file or S3 path if=
    supported by the local configuration This vulnerability is fixed in 1.10.0= .</td>
    <td>2026-06-23</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48520" target=3D= "_blank" rel=3D"noopener">CVE-2026-48520</a></td>
    </tr>

    <td class=3D"vendor-product">langflow-ai--langflow</td>
    <td>Langflow is a tool for building and deploying AI-powered agents and wor= kflows. Prior to 1.7.0, the logout button does not clear the session. The p= revious user stays logged in unless another user explicitly logs in. This v= ulnerability is fixed in 1.7.0.</td>
    <td>2026-06-23</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55423" target=3D= "_blank" rel=3D"noopener">CVE-2026-55423</a></td>
    </tr>

    <td class=3D"vendor-product">libssh2--libssh2</td>
    <td>libssh2 through 1.11.1 grows its publickey list with SSH2_REALLOC but d= oes not zero-initialize new entries before parsing populates them, so a par=
    se failure reaching the cleanup path leaves libssh2_publickey_list_free ope= rating on an uninitialized entry. A malicious SSH server offering the publi= ckey subsystem can use a malformed response to make cleanup free an uniniti= alized, attacker-influenceable attrs pointer in a connecting libssh2 client= .</td>
    <td>2026-06-28</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58051" target=3D= "_blank" rel=3D"noopener">CVE-2026-58051</a></td>
    </tr>

    <td class=3D"vendor-product">magepeopleteam--Booking and Rental Manager</td=

    <td>Unauthenticated Broken Access Control in Booking and Rental Manager &lt= ;=3D 2.7.1 versions.</td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57660" target=3D= "_blank" rel=3D"noopener">CVE-2026-57660</a></td>
    </tr>

    <td class=3D"vendor-product">Majestic Support--Majestic Support</td> <td>Subscriber Insecure Direct Object References (IDOR) in Majestic Support=
    &lt;=3D 1.1.7 versions.</td>
    <td>2026-06-26</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57646" target=3D= "_blank" rel=3D"noopener">CVE-2026-57646</a></td>
    </tr>

    <td class=3D"vendor-product">manuelpadillac--MP Customize Login Page</td> <td>The MP Customize Login Page plugin for WordPress is vulnerable to Cross= -Site Request Forgery (CSRF) in all versions up to and including 1.0. This =
    is due to a completely broken nonce validation in the enter_mpclp_login_opt= ions() function, which contains an inverted check (if wp_verify_nonce(...) =
    { return false; }) and is missing the required action parameter for wp_veri= fy_nonce(). As a result, the nonce check is effectively dead code: it never=
    blocks malicious requests because a CSRF-supplied empty/invalid nonce alwa=
    ys returns false, satisfying the inverted condition to continue execution. = Furthermore, the settings-update handler is hooked on init without any capa= bility check. This makes it possible for unauthenticated attackers to modif=
    y all plugin setting, including login page background, logo URL, image dime= nsions, button colors, and login message, by tricking a logged-in administr= ator into submitting a crafted request.</td>
    <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6292" target=3D"= _blank" rel=3D"noopener">CVE-2026-6292</a></td>
    </tr>

    <td class=3D"vendor-product">masteriyo--Masteriyo LMS LMS Course Builder, Q= uizzes &amp; Certificates</td>
    <td>The Masteriyo LMS - LMS Course Builder, Quizzes &amp; Certificates plug=
    in for WordPress is vulnerable to authorization bypass in all versions up t=
    o, and including, 2.2.1. This is due to the plugin not properly verifying t= hat a user is authorized to perform an action. This makes it possible for a= uthenticated attackers, with student-level access and above, to modify the = description (post content) of arbitrary course announcements authored by in= structors or administrators.</td>
    <td>2026-06-27</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11773" target=3D= "_blank" rel=3D"noopener">CVE-2026-11773</a></td>
    </tr>

    <td class=3D"vendor-product">mastodon--mastodon</td>
    <td>Mastodon is a free, open-source social network server based on Activity= Pub. Prior to 4.5.10, 4.4.17, and 4.3.23, Mastodon's normalization of incom= ing activities signed with Linked-Data Signatures does not sufficiently pro= tect the activities from a certain class of spoofing, allowing threat actor=
    s to remove JSON entries from valid signed activities from a third-party ac= tor. This vulnerability is fixed in 4.5.10, 4.4.17, and 4.3.23.</td> <td>2026-06-24</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48028" target=3D= "_blank" rel=3D"noopener">CVE-2026-48028</a></td>
    </tr>

    <td class=3D"vendor-product">mastodon--mastodon</td>
    <td>Mastodon is a free, open-source social network server based on Activity= Pub. Prior to 4.5.10, 4.4.17, and 4.3.23, Mastodon's normalization of incom= ing activities signed with Linked-Data Signatures does not sufficiently pro= tect the activities from a certain class of spoofing, allowing attackers to=
    re-arrange a valid signed JSON-LD activity from a third-party actor to hav=
    e it processed differently. This vulnerability is fixed in 4.5.10, 4.4.17, = and 4.3.23.</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46349" target=3D= "_blank" rel=3D"noopener">CVE-2026-46349</a></td>
    </tr>

    <td class=3D"vendor-product">mastodon--mastodon</td>
    <td>Mastodon is a free, open-source social network server based on Activity= Pub. From 4.3.0 until 4.5.11 and 4.4.18, Mastodon has a feature to let webs= ites credit authors of their articles. To prevent false attribution claims,=
    Mastodon uses the attributionDomains JSON-LD term, however, an error in ho=
    w it is defined makes Linked Data Signatures on the toot:attributionDomains=
    property ineffective. An attacker can arbitrarily modify the attributionDo= mains value of a legitimately signed Update activity and bypass Mastodon's = signature verification. This vulnerability is fixed in 4.5.11 and 4.4.18.</=

    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50128" target=3D= "_blank" rel=3D"noopener">CVE-2026-50128</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--github.com/mattermost/mattermost/s= erver/public</td>
    <td>The Mattermost Go module github.com/mattermost/mattermost/server/public=
    versions &lt; v0.1.22 fail to validate path parameters when constructing A=
    PI route paths which allows an attacker to redirect API calls to unintended=
    endpoints via crafted IDs containing path traversal components. Mattermost=
    Advisory ID: MMSA-2025-00532</td>
    <td>2026-06-26</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13426" target=3D= "_blank" rel=3D"noopener">CVE-2026-13426</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost</td>
    <td>Mattermost versions 10.11.x &lt;=3D 10.11.18, 11.6.x &lt;=3D 11.6.3, 11= .5.x &lt;=3D 11.5.6 fail to validate attachment URLs against internal or pr= ivate IP ranges in the Mattermost Agents plugin MCP server which allows an = attacker with access to the MCP server in stdio mode to perform server-side=
    request forgery (SSRF) and exfiltrate data from internal network services = via supplying internal URLs as file attachments in post creation requests..=
    Mattermost Advisory ID: MMSA-2026-00635</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-4339" target=3D"= _blank" rel=3D"noopener">CVE-2026-4339</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost</td>
    <td>Mattermost versions 11.7.x &lt;=3D 11.7.0, 11.6.x &lt;=3D 11.6.2, 11.5.=
    x &lt;=3D 11.5.5, 10.11.x &lt;=3D 10.11.17 Fail to validate channel ownersh=
    ip of an existing subscription before applying edits which allows an authen= ticated attacker to hijack subscriptions from channels they have no access =
    to via a crafted PUT request to the subscription edit endpoint.. Mattermost=
    Advisory ID: MMSA-2026-00650</td>
    <td>2026-06-22</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6062" target=3D"= _blank" rel=3D"noopener">CVE-2026-6062</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost</td>
    <td>Mattermost versions 11.7.x &lt;=3D 11.7.0, 11.6.x &lt;=3D 11.6.2, 11.5.=
    x &lt;=3D 11.5.5, 10.11.x &lt;=3D 10.11.17 fail to authenticate Atlassian C= onnect installed callbacks, allowing a remote unauthenticated attacker to i= nject a rogue sharedSecret and disrupt the Jira integration via POST to /ac= /installed during the pending-install window.. Mattermost Advisory ID: MMSA= -2026-00654</td>
    <td>2026-06-22</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6673" target=3D"= _blank" rel=3D"noopener">CVE-2026-6673</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost</td>
    <td>Mattermost Plugins versions &lt;=3D11.6 10.18.11 11.3.6 11.6.5.0 fail t=
    o sanitize error responses from the OpenAI API before logging, which allows=
    a user with access to server logs or support packets to obtain a valid or = partially reconstructable OpenAI API key via inspection of mattermost.log e= ntries generated during authentication failures. Mattermost Advisory ID: MM= SA-2026-00609</td>
    <td>2026-06-26</td>
    <td>6.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9699" target=3D"= _blank" rel=3D"noopener">CVE-2026-9699</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost</td>
    <td>Mattermost versions 11.7.x &lt;=3D 11.7.0, 11.6.x &lt;=3D 11.6.2, 11.5.=
    x &lt;=3D 11.5.5, 10.11.x &lt;=3D 10.11.17 fail to enforce administrator au= thorization on the {{setDefaultInstance}} call within the {{/gitlab connect=
    }} command handler, which allows any authenticated user to overwrite the gl= obal default GitLab instance configuration via the {{/gitlab connect &lt;in= stance-name&gt;}} slash command.. Mattermost Advisory ID: MMSA-2026-00644</=

    <td>2026-06-22</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-5139" target=3D"= _blank" rel=3D"noopener">CVE-2026-5139</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost</td>
    <td>Mattermost versions 11.7.x &lt;=3D 11.7.0, 11.6.x &lt;=3D 11.6.2, 11.5.=
    x &lt;=3D 11.5.5, 10.11.x &lt;=3D 10.11.17 fail to invalidate cached authen= tication state for active WebSocket connections during global session revoc= ation, which allows a user with an existing WebSocket connection to remain = authenticated and continue receiving real-time events until the cached sess= ion expires or the client reconnects.. Mattermost Advisory ID: MMSA-2026-00= 664</td>
    <td>2026-06-22</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9162" target=3D"= _blank" rel=3D"noopener">CVE-2026-9162</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost Google Drive Plugin</td=

    <td>The Mattermost Google Drive plugin before version 1.1.0 fails to valida=
    te channel membership in the file creation endpoint, allowing authenticated=
    users with a connected Google account to share Google Drive files to unaut= horized private channels and disclose private channel membership.</td> <td>2026-06-25</td>
    <td>4.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-2299" target=3D"= _blank" rel=3D"noopener">CVE-2026-2299</a></td>
    </tr>

    <td class=3D"vendor-product">maxfoundry--MaxButtons Create buttons</td>
    <td>The MaxButtons - Create buttons plugin for WordPress is vulnerable to R= eflected Cross-Site Scripting via the 'view' parameter in all versions up t=
    o, and including, 9.8.5 due to insufficient input sanitization and output e= scaping. This makes it possible for unauthenticated attackers to inject arb= itrary web scripts in pages that execute if they can successfully trick a u= ser into performing an action such as clicking on a link.</td> <td>2026-06-27</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13245" target=3D= "_blank" rel=3D"noopener">CVE-2026-13245</a></td>
    </tr>

    <td class=3D"vendor-product">Mervin Praison--Featured Image</td>
    <td>Author Cross Site Scripting (XSS) in Featured Image &lt;=3D 2.1 version= s.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57431" target=3D= "_blank" rel=3D"noopener">CVE-2026-57431</a></td>
    </tr>

    <td class=3D"vendor-product">metagauss--ProfileGrid User Profiles, Groups a=
    nd Communities</td>
    <td>The ProfileGrid - User Profiles, Groups and Communities plugin for Word= Press is vulnerable to Stored Cross-Site Scripting via the 'pm_author_messa= ge' parameter in the pm_send_message_to_author function in all versions up = to, and including, 5.9.9.2 due to insufficient input sanitization and outpu=
    t escaping. This makes it possible for authenticated attackers, with Subscr= iber-level access and above, to inject arbitrary web scripts in pages that = will execute whenever a user accesses an injected page. The vulnerability w=
    as partially patched in version 5.9.8.5.</td>
    <td>2026-06-23</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-4610" target=3D"= _blank" rel=3D"noopener">CVE-2026-4610</a></td>
    </tr>

    <td class=3D"vendor-product">metagauss--RegistrationMagic Custom Registrati=
    on Forms, User Registration, Payment, and User Login</td>
    <td>The RegistrationMagic - Custom Registration Forms, User Registration, P= ayment, and User Login plugin for WordPress is vulnerable to Authentication=
    Bypass via Insufficient Verification of Data Authenticity in all versions =
    up to and including 6.0.8.6. This is due to the PayPal IPN `callback` handl=
    er being registered as a nopriv AJAX action with no authentication or nonce=
    requirement, and critically because the handler updates the payment log da= tabase row with attacker-controlled POST data - including `payment_status` = and the `custom` field encoding the target `user_id` - before PayPal IPN va= lidation is performed, meaning the database remains poisoned even when vali= dation subsequently fails. This makes it possible for unauthenticated attac= kers to authenticate as any WordPress user, including administrators, by su= bmitting a forged IPN request that overwrites a payment log entry's `user_i=
    d` with that of a target account, then visiting the success return URL with=
    a legitimately obtained security hash to cause the plugin to issue real Wo= rdPress authentication cookies for the targeted account.</td> <td>2026-06-27</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9242" target=3D"= _blank" rel=3D"noopener">CVE-2026-9242</a></td>
    </tr>

    <td class=3D"vendor-product">Mintplex-Labs--anything-llm</td>
    <td>AnythingLLM is an application that turns pieces of content into context=
    that any LLM can use as references during chatting. Prior to 1.13.0, on Wi= ndows, the document folder listing route can accept an encoded absolute Win= dows path that resolves outside the intended documents directory. The share=
    d path containment helper rejects POSIX-style "../" traversal but does not = reject Windows-style parent paths returned by path.relative(), such as ".."=
    . This vulnerability is fixed in 1.13.0.</td>
    <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48789" target=3D= "_blank" rel=3D"noopener">CVE-2026-48789</a></td>
    </tr>

    <td class=3D"vendor-product">mirsoftware--MIR blocks and shortcodes</td> <td>The MIR blocks and shortcodes plugin for WordPress is vulnerable to Sto= red Cross-Site Scripting via the 'title' attribute (and other attributes su=
    ch as 'ready_animation_text') of the 'msc_stats' shortcode in versions up t=
    o, and including, 1.0.0. This is due to insufficient input sanitization and=
    output escaping on user supplied shortcode attributes inside the msc_stats=
    () rendering function. This makes it possible for authenticated attackers, = with contributor-level access and above, to inject arbitrary web scripts in=
    pages that will execute whenever a user accesses an injected page.</td> <td>2026-06-24</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8896" target=3D"= _blank" rel=3D"noopener">CVE-2026-8896</a></td>
    </tr>

    <td class=3D"vendor-product">MLflow--MLflow</td>
    <td>A vulnerability has been found in MLflow up to 4666cffc7912ea606d592fc3= 8d6a75e2935f65e7. The impacted element is an unknown function of the compon= ent Experiment-scoped Label Schema CRUD API. Such manipulation leads to mis= sing authorization. It is possible to launch the attack remotely. A high co= mplexity level is associated with this attack. The exploitability is regard=
    ed as difficult. The exploit has been disclosed to the public and may be us= ed. A reply to the GitHub issue explains, that "[t]he labeling schema PR ha=
    s not been merged yet. The auth handlers will be added before the release."= </td>
    <td>2026-06-28</td>
    <td>5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13484" target=3D= "_blank" rel=3D"noopener">CVE-2026-13484</a></td>
    </tr>

    <td class=3D"vendor-product">motioneye-project--motioneye</td>
    <td>motionEye (mEye) is an online interface for motion software, which is a=
    video surveillance program with motion detection. Versions prior to 0.44.0=
    are vulnerable to path traversal in the picture and movie API endpoints, s= uhc as /picture/{id}/preview/{filename}. Neither the API handlers, nor the = mediafiles.py functions such as get_media_preview() check for .. sequences =
    in the filename parameter, except for get_media_content(). This allows an a= uthenticated user with normal (non-admin) privileges to read arbitrary file=
    s from the filesystem as the motionEye process user, such as: /etc/passwd, = /etc/shadow, motionEye config files containing password hashes and plaintex=
    t passwords, SSH keys, and other cameras' surveillance footage. This issue = has been fixed in version 0.44.0.</td>
    <td>2026-06-24</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-31978" target=3D= "_blank" rel=3D"noopener">CVE-2026-31978</a></td>
    </tr>

    <td class=3D"vendor-product">motioneye-project--motioneye</td>
    <td>motionEye (mEye) is an online interface for motion software, a video su= rveillance program with motion detection. Versions prior to 0.44.0 create t=
    he configuration file /etc/motioneye/motion.conf with 644 permissions (-rw-= r--r--), making it readable by any local user on the system. This file cont= ains sensitive data including the admin password hash, which can be leverag=
    ed by other vulnerabilities to escalate privileges. Additionally, per-camer=
    a configuration files (camera-*.conf) are also created with the same 644 pe= rmissions, potentially exposing camera-specific credentials and settings. T=
    he exposed SHA1 admin password hash can be cracked offline to recover the p= laintext password, used directly to forge authenticated admin API requests = via the signature authentication weakness (GHSA-45h7-499j-7ww3), and chaine=
    d with the OS command injection flaw (CVE-2025-60787) to escalate a local u= nprivileged user to the Motion daemon user (often root), enabling full syst=
    em compromise. This issue has been fixed in version 0.44.0.</td> <td>2026-06-24</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-32315" target=3D= "_blank" rel=3D"noopener">CVE-2026-32315</a></td>
    </tr>

    <td class=3D"vendor-product">motordesk--MotorDesk</td>
    <td>The MotorDesk plugin for WordPress is vulnerable to Cross-Site Request = Forgery in all versions up to, and including, 1.1.2. This is due to missing=
    or incorrect nonce validation on the motordesk_admin_home function. This m= akes it possible for unauthenticated attackers to update the plugin's confi= guration settings, including the search page URI and custom template direct= ory path via a forged request granted they can trick a site administrator i= nto performing an action such as clicking on a link.</td>
    <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9724" target=3D"= _blank" rel=3D"noopener">CVE-2026-9724</a></td>
    </tr>

    <td class=3D"vendor-product">myCred--License Manager for WooCommerce</td> <td>Unauthenticated Insecure Direct Object References (IDOR) in License Man= ager for WooCommerce &lt;=3D 3.0.15 versions.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56013" target=3D= "_blank" rel=3D"noopener">CVE-2026-56013</a></td>
    </tr>

    <td class=3D"vendor-product">MyScale--MyScaleDB</td>
    <td>A security flaw has been discovered in MyScale MyScaleDB up to 1.8.0. T= his vulnerability affects the function SegmentId::getCacheKey in the librar=
    y src/VectorIndex/Common/SegmentId.h. The manipulation results in insuffici= ent verification of data authenticity. It is possible to launch the attack = remotely. A high complexity level is associated with this attack. It is sta= ted that the exploitability is difficult. The exploit has been released to = the public and may be used for attacks. The pull request to fix this issue = awaits acceptance.</td>
    <td>2026-06-28</td>
    <td>5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13513" target=3D= "_blank" rel=3D"noopener">CVE-2026-13513</a></td>
    </tr>

    <td class=3D"vendor-product">n8n--n8n</td>
    <td>n8n before 1.123.25 (1.x) and before 2.11.2 (2.x), with the fix also in= cluded in 2.12.0, contains a stored cross-site scripting vulnerability in t=
    he Form Trigger node's CSS sanitization that allows authenticated users to = inject malicious scripts. Attackers with workflow creation permissions can = inject XSS payloads that execute persistently for all form visitors, enabli=
    ng form hijacking and phishing attacks.</td>
    <td>2026-06-24</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56358" target=3D= "_blank" rel=3D"noopener">CVE-2026-56358</a></td>
    </tr>

    <td class=3D"vendor-product">n8n--n8n</td>
    <td>n8n before 1.123.15 and 2.5.0 contains a webhook forgery vulnerability =
    in the GitHub Webhook Trigger node that fails to implement HMAC-SHA256 sign= ature verification. Attackers who know the webhook URL can send unsigned PO=
    ST requests to trigger workflows with arbitrary data, spoofing GitHub webho=
    ok events.</td>
    <td>2026-06-22</td>
    <td>4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56357" target=3D= "_blank" rel=3D"noopener">CVE-2026-56357</a></td>
    </tr>

    <td class=3D"vendor-product">nanocoai--nanoclaw</td>
    <td>NanoClaw before 2.1.17 contains a privilege escalation vulnerability in=
    the handleApprovalsResponse function that fails to verify responder role a= uthorization. Attackers with a valid questionId can approve or reject privi= leged actions like package installation by submitting approval response pay= loads without proper role validation.</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56402" target=3D= "_blank" rel=3D"noopener">CVE-2026-56402</a></td>
    </tr>

    <td class=3D"vendor-product">nanocoai--nanoclaw</td>
    <td>NanoClaw before 2.1.17 contains a symlink following vulnerability in fo= rwardAttachedFiles that allows container-controlled agents to exfiltrate ho= st-readable files. The host validates attachment filenames using only isSaf= eAttachmentName before copying with fs.copyFileSync, which follows symlinks=
    without containment checks, allowing malicious agents to disclose arbitrar=
    y host files.</td>
    <td>2026-06-23</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56692" target=3D= "_blank" rel=3D"noopener">CVE-2026-56692</a></td>
    </tr>

    <td class=3D"vendor-product">nanocoai--nanoclaw</td>
    <td>NanoClaw before 2.1.17 contains a privilege escalation vulnerability in=
    the create_agent delivery-action handler that performs privileged central-= database writes without host-side authorization checks. Confined agent cont= ainers can invoke create_agent to create arbitrary agent groups, container = configurations, and destinations, escalating beyond their intended confinem= ent boundary.</td>
    <td>2026-06-23</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56693" target=3D= "_blank" rel=3D"noopener">CVE-2026-56693</a></td>
    </tr>

    <td class=3D"vendor-product">nanocoai--nanoclaw</td>
    <td>NanoClaw before 2.1.0 contains a privilege escalation vulnerability in = the channel-registration approval flow where handleChannelApprovalResponse = fails to validate admin privileges over target agent groups. Scoped admins = can submit forged or stale connect callback values to wire messaging channe=
    ls into out-of-scope agent groups, exposing unauthorized groups to unapprov=
    ed channels and enabling unauthorized observation or control of restricted = agent group activity.</td>
    <td>2026-06-23</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56694" target=3D= "_blank" rel=3D"noopener">CVE-2026-56694</a></td>
    </tr>

    <td class=3D"vendor-product">Nelio Software--Nelio Content</td>
    <td>Contributor Broken Access Control in Nelio Content &lt;=3D 4.3.4 versio= ns.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57648" target=3D= "_blank" rel=3D"noopener">CVE-2026-57648</a></td>
    </tr>

    <td class=3D"vendor-product">NetworkConfiguration--dhcpcd</td>
    <td>dhcpcd through 10.3.2, fixed in commit 708b4a5, contains a memory leak = vulnerability in the IPv6 Router Advertisement route information handling t= hat allows an unauthenticated same-link attacker to cause denial of service=
    by sending crafted Router Advertisements. Attackers can repeatedly send Ro= uter Advertisements containing Route Information options with a lifetime of=
    zero, triggering unfreed allocations in routeinfo_findalloc() that cause l= inear memory exhaustion and eventual daemon crash.</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56116" target=3D= "_blank" rel=3D"noopener">CVE-2026-56116</a></td>
    </tr>

    <td class=3D"vendor-product">NetworkConfiguration--dhcpcd</td>
    <td>dhcpcd through 10.3.2, fixed in commit 5733d3c, contains a heap use-aft= er-free vulnerability that allows unauthenticated same-link attackers to cr= ash the daemon by sending a crafted DHCPv6 RENEW reply with RFC6603 OPTION_= PD_EXCLUDE and both preferred and valid lifetimes set to zero. Attackers ac= ting as or impersonating a DHCPv6 server can trigger dhcp6_deprecatedele() =
    to free a delegated child address while an outer TAILQ_FOREACH_SAFE iterato=
    r in dhcp6_deprecateaddrs() still holds the freed pointer, causing a use-af= ter-free when TAILQ_REMOVE is reached.</td>
    <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56113" target=3D= "_blank" rel=3D"noopener">CVE-2026-56113</a></td>
    </tr>

    <td class=3D"vendor-product">NetworkConfiguration--dhcpcd</td>
    <td>dhcpcd through 10.3.2, fixed in commit 2f00c7b, contains a one-byte sta=
    ck out-of-bounds write vulnerability in dhcp6_makemessage() in src/dhcp6.c = that allows unauthenticated same-link attackers to write beyond a fixed loc=
    al buffer by serializing an oversized RFC6603 OPTION_PD_EXCLUDE option body=
    . Attackers can send a crafted DHCPv6 ADVERTISE message containing an IA_PD=
    IAPREFIX /0 with a valid OPTION_PD_EXCLUDE using an exclude prefix length =
    of /121 through /128 to trigger the out-of-bounds write and potentially cor= rupt adjacent stack memory.</td>
    <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56114" target=3D= "_blank" rel=3D"noopener">CVE-2026-56114</a></td>
    </tr>

    <td class=3D"vendor-product">NetworkConfiguration--dhcpcd</td>
    <td>dhcpcd through 10.3.2, fixed in commit 78ea09e, contains a heap use-aft= er-free vulnerability in the control socket handling within src/control.c t= hat allows local unprivileged attackers to trigger memory corruption when p= rivilege separation is disabled. Attackers can connect to the control socke=
    t and send a privileged command such as -x, causing control_recvdata() to f= ree the client object while the same READ+HANGUP event subsequently reaches=
    control_hangup() with the stale pointer, resulting in a use-after-free con= dition exploitable in deployments using --disable-privsep or where privsep = initialization has failed with the control socket operating in mode 0666.</=

    <td>2026-06-23</td>
    <td>4.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56117" target=3D= "_blank" rel=3D"noopener">CVE-2026-56117</a></td>
    </tr>

    <td class=3D"vendor-product">Nexcess--WPComplete</td>
    <td>Subscriber Broken Access Control in WPComplete &lt;=3D 2.9.5.5 versions= .</td>
    <td>2026-06-26</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57661" target=3D= "_blank" rel=3D"noopener">CVE-2026-57661</a></td>
    </tr>

    <td class=3D"vendor-product">nghttp2--nghttp2</td>
    <td>nghttp2's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade req= uest that also carries a Content-Length header and body onto reusable keep-= alive backend connections, re-adding the Upgrade and Connection headers whi=
    le passing Content-Length verbatim. A backend that resolves the resulting a= mbiguous message in the attacker's favor enables HTTP request/response smug= gling and cross-client response-queue poisoning.</td>
    <td>2026-06-28</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58055" target=3D= "_blank" rel=3D"noopener">CVE-2026-58055</a></td>
    </tr>

    <td class=3D"vendor-product">nicolargo--glances</td>
    <td>Glances is an open-source system cross-platform monitoring tool. Prior =
    to 4.5.5, the Glances XML-RPC server (glances -s, implemented in glances/se= rver.py) does not validate the HTTP Host header, leaving it vulnerable to D=
    NS rebinding attacks. An attacker can exploit DNS rebinding to exfiltrate t=
    he full system monitoring dataset from a victim's browser. This vulnerabili=
    ty is fixed in 4.5.5.</td>
    <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46611" target=3D= "_blank" rel=3D"noopener">CVE-2026-46611</a></td>
    </tr>

    <td class=3D"vendor-product">nK--Ghost Kit</td>
    <td>Contributor Cross Site Scripting (XSS) in Ghost Kit &lt;=3D 3.6.0 versi= ons.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57651" target=3D= "_blank" rel=3D"noopener">CVE-2026-57651</a></td>
    </tr>

    <td class=3D"vendor-product">Nmap--Nmap</td>
    <td>Nmap through 7.99 does not keep the IPv6 extension-header walk within t=
    he captured packet in ipv6_get_data_primitive (libnetutil/netutil.cc), so t=
    he pointer advances past the buffer and the remaining-length computation un= derflows to a large value. A scanned target or on-path attacker returning a=
    crafted IPv6 response with a truncated extension header can trigger out-of= -bounds reads and a crash during raw IPv6 scans.</td>
    <td>2026-06-28</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58058" target=3D= "_blank" rel=3D"noopener">CVE-2026-58058</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, a reflected XSS vulnerability exists in the Page Leaving Warning pa= ge. The ncRedirectUrl and ncBackUrl query parameters are used in window.loc= ation.href and &lt;a&gt; tag bindings without validation, allowing javascri= pt: URI injection. This vulnerability is fixed in 2026.04.1.</td> <td>2026-06-23</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46547" target=3D= "_blank" rel=3D"noopener">CVE-2026-46547</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.4, the uploadViaURL path in the v1/v2 attachment API did not enforce N= C_ATTACHMENT_FIELD_SIZE against the remote content-length or against the re= sponse stream. An authenticated user (Editor+) could direct the server to d= ownload arbitrarily large files, exhausting disk space and causing denial o=
    f service. In packages/nocodb/src/services/attachments.service.ts, the HEAD=
    probe read content-length but never compared it to NC_ATTACHMENT_FIELD_SIZ=
    E; the subsequent storageAdapter.fileCreateByUrl() performed the download w= ithout maxContentLength. This vulnerability is fixed in 2026.04.4.</td> <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46551" target=3D= "_blank" rel=3D"noopener">CVE-2026-46551</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, an authenticated user with columnAdd permission on a Postgres-backe=
    d base can inject arbitrary SQL into the formula engine via the optional di= rection argument of ARRAYSORT(...). The value is unrestricted by formula va= lidation and embedded into a knex.raw ORDER BY clause, executing during col= umn creation and on every subsequent record read of the formula column. The=
    vulnerability is specific to the Postgres mapping for ARRAYSORT in package= s/nocodb/src/db/functionMappings/pg.ts. This vulnerability is fixed in 2026= .04.1.</td>
    <td>2026-06-23</td>
    <td>6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47375" target=3D= "_blank" rel=3D"noopener">CVE-2026-47375</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, the refresh-token cookie was set with httpOnly: true but missing bo=
    th the secure flag and the sameSite attribute. Over plain HTTP the cookie c= ould be intercepted on the network; without sameSite, browsers attached it =
    to cross-site POSTs, enabling CSRF against the token-refresh endpoint. This=
    vulnerability is fixed in 2026.04.1.</td>
    <td>2026-06-23</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46550" target=3D= "_blank" rel=3D"noopener">CVE-2026-46550</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, shared-base sessions were granted the same base-member capabilities=
    as authenticated viewers. Using only the shared-base UUID (xc-shared-base-= id), an attacker could enumerate base members and invite an arbitrary email=
    into the base as a real member. The invited user could then redeem the inv= ite via the normal signup flow and retain authenticated access even after t=
    he owner revoked the shared link. Shared-base sessions were mapped to Proje= ctRoles.VIEWER in packages/nocodb/src/strategies/base-view.strategy/base-vi= ew.strategy.ts, and packages/nocodb/src/utils/acl.ts granted baseUserList a=
    nd userInvite to that role. The shared frontend (packages/nc-gui/composable= s/useApi/interceptors.ts) deliberately removed auth headers in favour of th=
    e shared-base header, but the ACL middleware did not distinguish shared ses= sions from genuine viewers. This vulnerability is fixed in 2026.04.1.</td> <td>2026-06-23</td>
    <td>5.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46552" target=3D= "_blank" rel=3D"noopener">CVE-2026-46552</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, the request-filtering-agent SSRF protection was non-functional in t=
    he four notification webhook plugins (Slack, Discord, Mattermost, Teams) be= cause httpAgent / httpsAgent were passed as part of the request body rather=
    than the axios config. An authenticated user with hook-creation permission=
    could direct outbound POST requests to arbitrary internal hosts. This vuln= erability is fixed in 2026.04.1.</td>
    <td>2026-06-23</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46548" target=3D= "_blank" rel=3D"noopener">CVE-2026-46548</a></td>
    </tr>

    <td class=3D"vendor-product">nodeca--js-yaml</td>
    <td>js-yaml is a JavaScript YAML parser and dumper. Prior to 4.2.0, a craft=
    ed YAML document can trigger algorithmic CPU exhaustion in js-yaml merge-ke=
    y processing (&lt;&lt;) by repeating the same alias many times in a merge s= equence. This causes quadratic parse-time behavior relative to input size a=
    nd can block a Node.js worker/event loop for seconds with a relatively smal=
    l payload (tens of KB), resulting in denial of service. The issue is in mer=
    ge handling inside lib/loader.js. This vulnerability is fixed in 4.2.0.</td=

    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53550" target=3D= "_blank" rel=3D"noopener">CVE-2026-53550</a></td>
    </tr>

    <td class=3D"vendor-product">Noor Alam--Gmail SMTP</td>
    <td>Unauthenticated Cross Site Request Forgery (CSRF) in Gmail SMTP &lt;=3D=
    1.2.3.19 versions.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57657" target=3D= "_blank" rel=3D"noopener">CVE-2026-57657</a></td>
    </tr>

    <td class=3D"vendor-product">notepad-plus-plus--notepad-plus-plus</td> <td>Notepad++ is a free and open-source source code editor. Prior to 8.9.6.=
    1, a local process in the same interactive Windows session can send a malfo= rmed WM_COPYDATA message to Notepad++ using the COPYDATA_FULL_CMDLINE path.=
    The handler appears to process COPYDATASTRUCT.lpData as an unbounded NUL-t= erminated wchar_t* instead of enforcing COPYDATASTRUCT.cbData. This vulnera= bility is fixed in 8.9.6.1.</td>
    <td>2026-06-26</td>
    <td>5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48770" target=3D= "_blank" rel=3D"noopener">CVE-2026-48770</a></td>
    </tr>

    <td class=3D"vendor-product">nrwl--nx</td>
    <td>Nx is a monorepo solution for TypeScript and polyglot codebases. From 1= 7.0.4 until 22.7.2 and 23.0.0-beta.2, the local HTTP server started by nx g= raph sent Access-Control-Allow-Origin: * on every response, letting any web= site a developer visited read the server's responses cross-origin - includi=
    ng the full project graph and the output of the /help endpoint, which runs =
    a target's configured help command. The practical impact is typically cross= -origin information disclosure, but can be arbitrary command injection in r= are cases. This vulnerability is fixed in 22.7.2 and 23.0.0-beta.2.</td> <td>2026-06-26</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54753" target=3D= "_blank" rel=3D"noopener">CVE-2026-54753</a></td>
    </tr>

    <td class=3D"vendor-product">Nuxt--Nuxt</td>
    <td>Nuxt versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 contain a server= -side open redirect vulnerability in navigateTo that fails to properly vali= date path-normalized payloads like /..//evil.com and /.//evil.com. Attacker=
    s can bypass external-host checks using path-normalization techniques to re= direct users to attacker-controlled sites via the Location header or meta-r= efresh, enabling phishing and OAuth authorization-code theft.</td> <td>2026-06-22</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56326" target=3D= "_blank" rel=3D"noopener">CVE-2026-56326</a></td>
    </tr>

    <td class=3D"vendor-product">Nuxt--Nuxt</td>
    <td>Nuxt versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 accept protocol-= relative paths such as //evil.com in the reloadNuxtApp function; these pass=
    the script-protocol check but resolve to a cross-origin URL against the cu= rrent page protocol. Attackers can inject paths like //evil.com to redirect=
    users to attacker-controlled hosts, enabling phishing and OAuth authorizat= ion-code theft.</td>
    <td>2026-06-22</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56697" target=3D= "_blank" rel=3D"noopener">CVE-2026-56697</a></td>
    </tr>

    <td class=3D"vendor-product">Nuxt--Nuxt</td>
    <td>Nuxt versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 fail to validate=
    script-capable URLs in the navigateTo open option, allowing client-side sc= ript execution. Attackers can supply javascript: URLs through the open para= meter to execute arbitrary scripts in the application's origin when user-co= ntrolled input is passed to navigateTo.</td>
    <td>2026-06-22</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56698" target=3D= "_blank" rel=3D"noopener">CVE-2026-56698</a></td>
    </tr>

    <td class=3D"vendor-product">Nuxt--Nuxt</td>
    <td>Nuxt 4.0.0 before 4.4.7 and 3.18.0 before 3.21.7, when running the deve= lopment server (nuxt dev) on Linux, binds the vite-node IPC server to an ab= stract-namespace Unix socket without permission restrictions, allowing loca=
    l users to enumerate and connect. Unprivileged co-resident users can exploi=
    t the unprotected module request handler to read arbitrary files such as .e=
    nv and SSH keys through the SSR plugin pipeline. Production builds are unaf= fected, as the IPC server runs only in development.</td>
    <td>2026-06-23</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56301" target=3D= "_blank" rel=3D"noopener">CVE-2026-56301</a></td>
    </tr>

    <td class=3D"vendor-product">Omnisend--Email Marketing for WooCommerce by O= mnisend</td>
    <td>Subscriber Broken Access Control in Email Marketing for WooCommerce by = Omnisend &lt;=3D 1.19.0 versions.</td>
    <td>2026-06-26</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57632" target=3D= "_blank" rel=3D"noopener">CVE-2026-57632</a></td>
    </tr>

    <td class=3D"vendor-product">Opal_WP--Auros Core</td>
    <td>Unauthenticated Content Injection in Auros Core &lt;=3D 5.3.1 versions.= </td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-64637" target=3D= "_blank" rel=3D"noopener">CVE-2025-64637</a></td>
    </tr>

    <td class=3D"vendor-product">open-telemetry--opentelemetry-js</td> <td>opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0=
    , W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce si=
    ze limits when parsing inbound baggage HTTP headers. The W3C Baggage specif= ication recommends a maximum of 8,192 bytes and 180 entries; these limits w= ere only enforced on the outbound (inject()) path, not on the inbound (extr= act()) path. Parsing oversized baggage causes memory allocation proportiona=
    l to the header size without any cap. This vulnerability is fixed in 2.8.0.= </td>
    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54285" target=3D= "_blank" rel=3D"noopener">CVE-2026-54285</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, POST /api/chat/completions acce= pts an image_url.url value that, when it does NOT start with http://, https= ://, or data:image/, is interpreted as a file id and resolved against the g= lobal file table with no ownership check. an authenticated user can therefo=
    re set image_url.url to another user's file id, the server reads that file = from disk, base64-encodes it, and injects the data URI into the LLM request=
    . the user then prompts the LLM to describe / OCR the file and reads the co= ntent back. This vulnerability is fixed in 0.9.6.</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54009" target=3D= "_blank" rel=3D"noopener">CVE-2026-54009</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, Open WebUI's prompt version-his= tory endpoints authorize the prompt_id in the URL but then act on caller-su= pplied history IDs without verifying that the history row belongs to that p= rompt (history_entry.prompt_id =3D=3D prompt.id). This affects /api/v1/prom= pts/id/{prompt_id}/history/diff, /api/v1/prompts/id/{prompt_id}/update/vers= ion, and /api/v1/prompts/id/{prompt_id}/history/{history_id}. An authentica= ted user with access to any prompt they control, plus a victim prompt_histo= ry.id, can read or delete another user's private prompt history. This vulne= rability is fixed in 0.9.6.</td>
    <td>2026-06-23</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54015" target=3D= "_blank" rel=3D"noopener">CVE-2026-54015</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, Open WebUI added collection-lev=
    el ACL checks, but the patch can still be bypassed when Milvus multitenancy=
    mode is enabled. The ACL allows unknown non-KB collection names as legacy/= ephemeral collections. In Milvus multitenancy mode, that user-controlled co= llection name becomes a resource_id and is interpolated into a Milvus expre= ssion without escaping. This is caused by an incomplete fix for CVE-2026-44= 560 This vulnerability is fixed in 0.9.6.</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54019" target=3D= "_blank" rel=3D"noopener">CVE-2026-54019</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, several direct, index-addressed=
    Ollama proxy routes accept a caller-supplied url_idx path parameter and us=
    e it as a raw index into the admin-configured OLLAMA_BASE_URLS list. Access=
    control on these routes validates only whether the user may use the reques= ted model, never which backend the request is routed to. Any authenticated = user can append an arbitrary url_idx to force their request onto an Ollama = backend they were never authorized to reach, including internal, higher-pri= vilege, or explicitly admin-disabled backends. This vulnerability is fixed =
    in 0.9.6.</td>
    <td>2026-06-23</td>
    <td>6.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54021" target=3D= "_blank" rel=3D"noopener">CVE-2026-54021</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.8.11, the ydoc:document:join Socket.=
    IO handler checks note ownership only when the document_id starts with note=
    : (colon). However, the YdocManager storage layer normalizes all document I=
    Ds by replacing colons with underscores (document_id.replace(":", "_")). An=
    attacker can join a document room using note_&lt;id&gt; (underscore) inste=
    ad of note:&lt;id&gt; (colon), bypassing the authorization check entirely w= hile accessing the same underlying Yjs document. The server then returns th=
    e full document state, leaking the victim's private note contents. This vul= nerability is fixed in 0.8.11.</td>
    <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54022" target=3D= "_blank" rel=3D"noopener">CVE-2026-54022</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, POST /api/v1/calendars/events/{= event_id}/update validates that the caller has write access to the calendar=
    the event currently belongs to, but does not validate the destination cale= ndar_id supplied in the request body. The model layer then persists the new=
    calendar_id unconditionally. A regular user-role account can therefore cre= ate an event in their own calendar and immediately move it into any other u= ser's calendar whose ID they know - bypassing the authorization check that = create_event correctly performs. This vulnerability is fixed in 0.9.6.</td> <td>2026-06-23</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54006" target=3D= "_blank" rel=3D"noopener">CVE-2026-54006</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, a path traversal vulnerability = exists in open-webui's cache file serving endpoint that allows any authenti= cated user to read files from sibling directories outside the intended cach=
    e directory, by exploiting an incomplete startswith containment check that = lacks a trailing path separator. The root cause is that serve_cache_file() =
    in open_webui/main.py validates the resolved path with file_path.startswith= (os.path.abspath(CACHE_DIR)) - without appending os.sep. This allows any pa=
    th resolving to a sibling directory whose name begins with cache (e.g. cach= e_sibling, cache_backup, cached_models) to pass validation. This vulnerabil= ity is fixed in 0.9.6.</td>
    <td>2026-06-23</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54014" target=3D= "_blank" rel=3D"noopener">CVE-2026-54014</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, Open WebUI has a Broken Object = Level Authorization (BOLA) vulnerability in the builtin search_knowledge_fi= les tool. When native function calling is enabled and the selected model ha=
    s no attached knowledge bases, an authenticated user can call search_knowle= dge_files with an arbitrary knowledge_id. The function then returns file me= tadata from that knowledge base without checking whether the user has read = access. This allows unauthorized enumeration of private or restricted knowl= edge base files. This vulnerability is fixed in 0.9.6.</td>
    <td>2026-06-23</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54016" target=3D= "_blank" rel=3D"noopener">CVE-2026-54016</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.2 and 17.4.0, a Missing Authorization vulnerability exists in Ope= nProject's CostReportsController. The rename and update actions allow any a= uthenticated user to modify the name, filters, and grouping of any Public c= ost report in the system without verifying ownership or permission level. A=
    n attacker who discovers or guesses a public report's numeric ID can rename=
    or overwrite its filter configuration without any warning to the report's = owner. This vulnerability is fixed in 17.3.2 and 17.4.0.</td> <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44734" target=3D= "_blank" rel=3D"noopener">CVE-2026-44734</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.2 and 17.4.0, the GET /api/v3/shares endpoint returns share detai=
    ls for ALL work packages in a project to any user with the view_shared_work= _packages permission. The authorization check operates at the project level=
    only - it does not verify the requesting user can actually view each indiv= idual shared work package. This allows a regular project member to discover=
    work package IDs and subjects (including confidential titles), which users=
    have been granted shared access, what role level was assigned (Editor, Com= menter, Viewer). This vulnerability is fixed in 17.3.2 and 17.4.0.</td> <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44735" target=3D= "_blank" rel=3D"noopener">CVE-2026-44735</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.4.0, the GET /api/v3/relations endpoint allows any authenticated us=
    er to retrieve relations - and the subject (title) of work packages they ha=
    ve no permission to view - by supplying an arbitrary work package ID in the=
    involved, fromId, or toId filter. This bypasses the Relation.visible scope=
    due to a flawed performance optimization in RelationQuery. This vulnerabil= ity is fixed in 17.4.0.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44736" target=3D= "_blank" rel=3D"noopener">CVE-2026-44736</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.3 and 17.4.1, the HTML sanitizer grants &lt;macro&gt; elements un= restricted data-* attributes via :data wildcard. An attacker injects data-c= ontroller=3D"poll-for-changes" into a work package description, causing Sti= mulus.js to mount a controller that fetches an attacker-uploaded attachment=
    and passes it to renderStreamMessage(). This executes arbitrary Turbo Stre=
    am actions - including redirect_to - in every victim's authenticated browse=
    r session, redirecting them to an attacker-controlled server. This vulnerab= ility is fixed in 17.3.3 and 17.4.1.</td>
    <td>2026-06-26</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52781" target=3D= "_blank" rel=3D"noopener">CVE-2026-52781</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.4.0, OpenProject's rich text (markdown) rendering pipeline uses San= itize::Config::RELAXED[:css] for inline style sanitization. This configurat= ion permits essentially all CSS properties in style attributes on permitted=
    HTML elements (figure, img, table, th, tr, td). This allows any authentica= ted user with write access to formattable text fields (work package descrip= tions, comments, project descriptions, news) to inject CSS This vulnerabili=
    ty is fixed in 17.4.0.</td>
    <td>2026-06-26</td>
    <td>5.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44696" target=3D= "_blank" rel=3D"noopener">CVE-2026-44696</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.2 and 17.4.0, Business Logic Error on OpenProject through PATCH r= equest to /api/v3/users/me permits to bypass password requirements. A passw= ord validation flaw in the change password behavior allows attackers to cha= nge a user's password only with an active session takeover. This vulnerabil= ity is fixed in 17.3.2 and 17.4.0.</td>
    <td>2026-06-26</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44733" target=3D= "_blank" rel=3D"noopener">CVE-2026-44733</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.3 and 17.4.1, a cross-project IDOR / authorization context confus= ion in the Calendar and Team Planner modules allows a user with management = permissions in one project to delete public Calendar or Team Planner Querie=
    s from another project where they do not have the corresponding management = permissions. Both modules authorize the request against the project identif= ied by :project_id in the URL, but the actual Query object is loaded later =
    by :id from Query.visible(current_user) without verifying that the loaded Q= uery belongs to the authorized project. As a result, an attacker can use pe= rmissions from Project A to delete shared/public Calendar or Team Planner v= iews from Project B, causing integrity impact and limited availability impa=
    ct for users relying on those shared views. This vulnerability is fixed in = 17.3.3 and 17.4.1.</td>
    <td>2026-06-26</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52779" target=3D= "_blank" rel=3D"noopener">CVE-2026-52779</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.2 and 17.4.0, the web application's meetings filter feature leaks=
    whether a given user ID corresponds to a valid account and discloses the u= ser's full name, allowing an attacker to enumerate all existing user accoun=
    ts by probing user IDs and observing differences in the server response. Th=
    is vulnerability is fixed in 17.3.2 and 17.4.0.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44731" target=3D= "_blank" rel=3D"noopener">CVE-2026-44731</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.3.2 and 17.4.0, OpenProject exposes a document update endpoint used=
    to modify existing documents. The target document is loaded with visibilit=
    y checks and then updated. During update, attacker-controlled attributes ar=
    e applied to the persisted record before authorization is enforced. As a re= sult, a user without :manage_documents in the source project can move and m= odify foreign project documents by setting project_id in a single PATCH req= uest. This vulnerability is fixed in 17.3.2 and 17.4.0.</td> <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44732" target=3D= "_blank" rel=3D"noopener">CVE-2026-44732</a></td>
    </tr>

    <td class=3D"vendor-product">opf--openproject</td>
    <td>OpenProject is open-source, web-based project management software. Prio=
    r to 17.4.0, `GET /api/v3/meetings/:meeting_id/agenda_items/:agenda_item_id=
    ` discloses private work package data from a linked work package that belon=
    gs to a private/inaccessible project. This vulnerability is fixed in 17.4.0= .</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49355" target=3D= "_blank" rel=3D"noopener">CVE-2026-49355</a></td>
    </tr>

    <td class=3D"vendor-product">osiris8--Osiris Signature Banner</td>
    <td>The Osiris Signature Banner plugin for WordPress is vulnerable to Cross= -Site Request Forgery in all versions up to, and including, 0.5. This is du=
    e to missing or incorrect nonce validation on a function. This makes it pos= sible for unauthenticated attackers to update settings and inject malicious=
    web scripts via a forged request granted they can trick a site administrat=
    or into performing an action such as clicking on a link.</td> <td>2026-06-24</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8905" target=3D"= _blank" rel=3D"noopener">CVE-2026-8905</a></td>
    </tr>

    <td class=3D"vendor-product">owencutajar--EntreDroppers</td>
    <td>The EntreDroppers plugin for WordPress is vulnerable to Reflected Cross= -Site Scripting via PHP_SELF Parameter in all versions up to, and including=
    , 1.1.2 due to insufficient input sanitization and output escaping. This ma= kes it possible for unauthenticated attackers to inject arbitrary web scrip=
    ts in pages that execute if they can successfully trick a user into perform= ing an action such as clicking on a link. The payload is delivered via atta= cker-controlled path-info in the URL (e.g., /wp-admin/admin.php/"&gt;&lt;sc= ript&gt;alert(0)&lt;/script&gt;/?page=3DEntreDroppers.php), which PHP_SELF = reflects directly into the form action attribute.</td>
    <td>2026-06-24</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8628" target=3D"= _blank" rel=3D"noopener">CVE-2026-8628</a></td>
    </tr>

    <td class=3D"vendor-product">paradigmatools--Avalon23 Products Filter for W= ooCommerce</td>
    <td>The Avalon23 Products Filter for WooCommerce plugin for WordPress is vu= lnerable to Stored Cross-Site Scripting via the 'avalon23_qr' shortcode in = all versions up to, and including, 1.1.6. This is due to insufficient input=
    sanitization and output escaping on user-supplied shortcode attributes (no= tably 'title' and 'fixed_link') which are concatenated directly into single= -quoted HTML attributes by the AVALON23_HELPER::draw_html_item() helper wit= hout esc_attr() or any other encoding. This makes it possible for authentic= ated attackers, with Contributor-level access and above, to inject arbitrar=
    y web scripts in pages that will execute whenever a user accesses an inject=
    ed page.</td>
    <td>2026-06-24</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8865" target=3D"= _blank" rel=3D"noopener">CVE-2026-8865</a></td>
    </tr>

    <td class=3D"vendor-product">peregrinethemes--Hester Core</td>
    <td>Author Cross Site Scripting (XSS) in Hester Core &lt;=3D 1.1.8 versions= .</td>
    <td>2026-06-26</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57656" target=3D= "_blank" rel=3D"noopener">CVE-2026-57656</a></td>
    </tr>

    <td class=3D"vendor-product">phpseclib--phpseclib</td>
    <td>phpseclib is a PHP secure communications library. From 0.1.1 until 1.0.= 30, 2.0.55, and 3.0.54, when an application validates an untrusted X.509 ce= rtificate with phpseclib, X509::validateSignature() reads a URL out of that=
    certificate's Authority Information Access (AIA) extension and connects to=
    it. Attacker who supplies certificate fully controls host, port, and path =
    of that connection. URL fetching is enabled by default, and no destination =
    is blocked. An unauthenticated attacker can therefore make a validating ser= ver open connections to internal hosts and ports it should never reach, for=
    example loopback 127.0.0.1, cloud metadata address 169.254.169.254, and in= ternal-only services. This is a server-side request forgery (SSRF) caused b=
    y an insecure default. This vulnerability is fixed in 1.0.30, 2.0.55, and 3= .0.54.</td>
    <td>2026-06-22</td>
    <td>5.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55599" target=3D= "_blank" rel=3D"noopener">CVE-2026-55599</a></td>
    </tr>

    <td class=3D"vendor-product">pixelwelt--Image Sizes on Demand</td>
    <td>The Image Sizes on Demand plugin for WordPress is vulnerable to Reflect=
    ed Cross-Site Scripting via PHP_SELF Server Variable in all versions up to,=
    and including, 1.3 due to insufficient input sanitization and output escap= ing. This makes it possible for unauthenticated attackers to inject arbitra=
    ry web scripts in pages that execute if they can successfully trick a user = into performing an action such as clicking on a link. The injected payload = only executes in the context of an administrator, as the settings page requ= ires the manage_options capability to render.</td>
    <td>2026-06-24</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8622" target=3D"= _blank" rel=3D"noopener">CVE-2026-8622</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm passes the=
    lockfile-controlled git resolution.commit value to git fetch without a -- = separator or commit-format validation. For git dependencies fetched through=
    the shallow-fetch path, a malicious lockfile can replace the expected 40-c= haracter commit hash with a Git option such as --upload-pack=3D&lt;command&= gt;. For SSH and local transports, --upload-pack can execute the supplied c= ommand. HTTPS transports ignore --upload-pack, so the practical attack surf= ace is primarily SSH or local git dependencies. This vulnerability is fixed=
    in 10.34.0 and 11.4.0.</td>
    <td>2026-06-25</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50014" target=3D= "_blank" rel=3D"noopener">CVE-2026-50014</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's tarball = extraction worker skips integrity verification when the integrity field is = absent from the lockfile resolution. If an attacker can both modify pnpm-lo= ck.yaml to remove the integrity: field and cause the referenced registry UR=
    L to serve altered package content, pnpm install --frozen-lockfile can inst= all the altered package without an integrity error. npm's npm ci enforces i= ntegrity by default; pnpm's behavior of silently skipping verification is a=
    pnpm-specific fail-open gap. This vulnerability is fixed in 10.34.0 and 11= .4.0.</td>
    <td>2026-06-25</td>
    <td>6.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50021" target=3D= "_blank" rel=3D"noopener">CVE-2026-50021</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.0 and 11.4.0, `pnpm install` =
    in non-frozen mode can accept new remote package content after detecting th=
    at the downloaded tarball does not match the integrity recorded in pnpm-loc= k.yaml. When a package is already locked with an integrity value, and the r= egistry later serves different metadata and tarball content for the same pa= ckage name and version, pnpm initially reports an integrity mismatch. Howev= er, plain pnpm install then performs a resolution repair, accepts the regis= try's new integrity, updates the lockfile, installs the new content, and ex= its successfully. This means the lockfile integrity check does not act as a=
    hard stop by default. This vulnerability is fixed in 10.34.0 and 11.4.0.</=

    <td>2026-06-25</td>
    <td>6.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50573" target=3D= "_blank" rel=3D"noopener">CVE-2026-50573</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm and pacque=
    t expanded ${ENV_VAR} placeholders from repository-controlled .npmrc and pn= pm-workspace.yaml into registry request destinations and registry credentia= ls. A malicious repository could cause dependency resolution to send victim=
    environment secrets to an attacker-selected registry before lifecycle scri= pts run. This vulnerability is fixed in 10.34.2 and 11.5.3.</td> <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55180" target=3D= "_blank" rel=3D"noopener">CVE-2026-55180</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.2 and 11.5.3, Manifest bin ob= ject keys such as "", ".", and ".." passed pnpm's bin-name guard. When a ma= licious package was installed globally, later global remove, update, or add= -replacement flows could re-derive those names from the installed manifest = and pass path.join(globalBinDir, binName) to removeBin. For "." this target=
    s the global bin directory; for ".." this targets its parent. This vulnerab= ility is fixed in 10.34.2 and 11.5.3.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55699" target=3D= "_blank" rel=3D"noopener">CVE-2026-55699</a></td>
    </tr>

    <td class=3D"vendor-product">podman-container-tools--podman</td>
    <td>Podman is a tool for managing OCI containers and pods. From 3.0.0 until=
    5.7.1, running a malicious container image where the WORKDIR path contains=
    a symlink can create a directory or modify ownership on the host filesyste=
    m. Modified ownership is less likely to happen as that requires help from a=
    n untrusted/malicious process that mutates the host filesystem tree during = dereferencing of the WORKDIR path, to trigger a race condition. This vulner= ability is fixed in 5.7.1.</td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55686" target=3D= "_blank" rel=3D"noopener">CVE-2026-55686</a></td>
    </tr>

    <td class=3D"vendor-product">poweradmin--poweradmin</td>
    <td>Poweradmin is a web-based DNS administration tool for PowerDNS server. = Versions prior to 4.2.4 and 4.3.3 are vulnerable to CSV Injection (Formula = Injection) in its log export functionality. User-controlled data - specific= ally the username field - is written to exported CSV files without sanitizi=
    ng formula trigger characters (=3D, +, -, @). When an administrator exports=
    activity logs and opens the resulting CSV in a spreadsheet application (Mi= crosoft Excel, LibreOffice Calc, Google Sheets), any formula stored in a us= ername is executed by the application. This can be used for phishing attack=
    s against administrators or data exfiltration. Versions 4.2.4 and 4.3.3 pat=
    ch the issue.</td>
    <td>2026-06-23</td>
    <td>6.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47693" target=3D= "_blank" rel=3D"noopener">CVE-2026-47693</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--Authoritative</td>
    <td>An attacker can send a web request that causes unlimited memory allocat= ion in the internal web server, leading to a denial of service. The interna=
    l web server is disabled by default.</td>
    <td>2026-06-25</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42005" target=3D= "_blank" rel=3D"noopener">CVE-2026-42005</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--DNSdist</td>
    <td>An attacker might be able to cause outgoing TCP connections to backend =
    to be stuck until a timeout occurs instead of being released immediately, b=
    y sending IXFR queries. This could be used to cause a denial of service if = there is a limit to the number of concurrent connections to this backend, o=
    r if the process runs out of file descriptors.</td>
    <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40209" target=3D= "_blank" rel=3D"noopener">CVE-2026-40209</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--DNSdist</td>
    <td>An attacker can send crafted DNS over HTTP/3 queries, triggering an exc= eption that prevents some buffer from being freed right away. The buffer wi=
    ll be freed at the end of the QUIC connection, but on some setups it might =
    be possible to open enough concurrent DoH3 streams to trigger an out-of-mem= ory condition, resulting in a denial of service.</td>
    <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40211" target=3D= "_blank" rel=3D"noopener">CVE-2026-40211</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--DNSdist</td>
    <td>An out-of-bounds read might happen when SetMacAddrAction is used, poten= tially resulting in uninitialized memory being sent over the network or a c= rash.</td>
    <td>2026-06-25</td>
    <td>4.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40210" target=3D= "_blank" rel=3D"noopener">CVE-2026-40210</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--Recursor</td>
    <td>ECS zero scoped answers are stored in the packet cache while they shoul=
    d not. This impacts only configurations that have ECS enabled;</td> <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40012" target=3D= "_blank" rel=3D"noopener">CVE-2026-40012</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--Recursor</td>
    <td>A malicious authoritative server can send a crafted zone via the ZoneTo= Cache function that leads to a crash of the Recursor due to insuffcient inp=
    ut validation.</td>
    <td>2026-06-25</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42387" target=3D= "_blank" rel=3D"noopener">CVE-2026-42387</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--Recursor</td>
    <td>Incomplete validation of the SOA record present in a catalog zone might=
    lead to a crash.</td>
    <td>2026-06-25</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42388" target=3D= "_blank" rel=3D"noopener">CVE-2026-42388</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--Recursor</td>
    <td>This fix provides extra hardening for the 5.4.x branch by doing extra v= alidation of incoming answers from authoritative servers.</td> <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42389" target=3D= "_blank" rel=3D"noopener">CVE-2026-42389</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--Recursor</td>
    <td>An invalid zone might pass ZONEMD validation while it should not. This =
    is only relevant if ZoneToCache is configured with ZONEMD validation.</td> <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42390" target=3D= "_blank" rel=3D"noopener">CVE-2026-42390</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--Recursor</td>
    <td>Spoofing replies to Recursor might mark an IP of an authoritative serve=
    r as not supporting EDNS, causing valdiation of DNSSEC records served by th=
    at server to fail.</td>
    <td>2026-06-25</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52690" target=3D= "_blank" rel=3D"noopener">CVE-2026-52690</a></td>
    </tr>

    <td class=3D"vendor-product">protobufjs--protobuf.js</td>
    <td>protobufjs compiles protobuf definitions into JavaScript (JS) functions=
    . Prior to 8.6.0 and 7.6.3, protobufjs accepted certain schema-derived name=
    s that could collide with properties used by protobufjs runtime helpers. Th=
    e known affected names are fields named hasOwnProperty, field or oneof name=
    s such as $type when loaded through protobufjs JSON/reflection descriptors,=
    and service methods whose generated helper name is rpcCall. When affected = message or service types were used, protobufjs could read schema-controlled=
    data where it expected an own-property helper, reflected type metadata, or=
    the base RPC helper. This could cause deterministic exceptions or recursiv=
    e calls in affected decode post-checks, verification, object conversion, re= flected JSON serialization, or protobufjs RPC helper invocation. This vulne= rability is fixed in 8.6.0 and 7.6.3.</td>
    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54269" target=3D= "_blank" rel=3D"noopener">CVE-2026-54269</a></td>
    </tr>

    <td class=3D"vendor-product">protobufjs--protobuf.js</td>
    <td>protobufjs compiles protobuf definitions into JavaScript (JS) functions=
    . From 8.2.0 to 8.4.2, protobufjs preserved unknown wire elements in messag= e.$unknowns and did not provide a decode-time option to discard unknown fie= lds before retaining them. A crafted protobuf payload containing many unkno=
    wn fields could therefore cause a decoded message to retain substantially m= ore memory than the input size would suggest, even when unknown-field round= -tripping is not needed. protobufjs 8.5.0 added the relevant decode-time op= tions, allowing applications that decode untrusted protobuf data to disable=
    unknown-field retention during decode. protobufjs 8.6.2 flips the default =
    so unknown fields are discarded unless explicitly opted into.</td> <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54270" target=3D= "_blank" rel=3D"noopener">CVE-2026-54270</a></td>
    </tr>

    <td class=3D"vendor-product">Pylons--webob</td>
    <td>WebOb provides objects for HTTP requests and responses. Prior to 1.8.10=
    , the normalization of the HTTP Location header during a redirect is vulner= able to an open redirect: WebOb joins the redirect target to the request UR=
    I using Python's urljoin, and since Python 3.10 the underlying urlsplit str= ips ASCII tab, carriage return, and newline characters before parsing, so a=
    redirect target containing such characters can be reinterpreted as a proto= col-relative URL whose authority is an attacker-controlled host. This bypas= ses the CVE-2024-42353 fix that escaped a leading double slash, allowing an=
    attacker who influences the redirect location to send users to an arbitrar=
    y external site instead of the intended one. This vulnerability is fixed in=
    1.8.10.</td>
    <td>2026-06-22</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44889" target=3D= "_blank" rel=3D"noopener">CVE-2026-44889</a></td>
    </tr>

    <td class=3D"vendor-product">RAGapp--RAGapp</td>
    <td>A vulnerability has been found in RAGapp up to 0.1.5. Affected is the f= unction FileHandler.upload_file/FileHandler.remove_file of the file src/rag= app/backend/controllers/files.py of the component Knowledge File Handler. S= uch manipulation leads to path traversal. The attack can be executed remote= ly. The exploit has been disclosed to the public and may be used. The pull = request to fix this issue awaits acceptance.</td>
    <td>2026-06-28</td>
    <td>6.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13509" target=3D= "_blank" rel=3D"noopener">CVE-2026-13509</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect Finger Plugin</td>
    <td>OS Command Injection vulnerability in Rapid7 InsightConnect Finger Plug=
    in on Linux allows authenticated attackers to execute arbitrary OS commands=
    via the user or host parameters due to insufficient input validation in sh= ell command construction.</td>
    <td>2026-06-25</td>
    <td>6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8664" target=3D"= _blank" rel=3D"noopener">CVE-2026-8664</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect Markdown Plugin</td> <td>Server-Side Cross-Site Scripting and Server-Side Request Forgery vulner= ability in the markdown_to_pdf action of Rapid7 InsightConnect Markdown Plu= gin version 3.1.4 and earlier on Linux allows remote attackers to execute J= avaScript server-side and make arbitrary outbound HTTP requests via crafted=
    content embedded in Markdown input. The PDF rendering engine does not rest= rict script execution or outbound network access.</td>
    <td>2026-06-26</td>
    <td>4.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8661" target=3D"= _blank" rel=3D"noopener">CVE-2026-8661</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect RPM Plugin</td>
    <td>OS Command Injection vulnerability in Rapid7 InsightConnect RPM Plugin =
    on Linux allows authenticated attackers to execute arbitrary OS commands vi=
    a the repo, key, or name parameters due to insufficient input sanitization =
    in shell command construction.</td>
    <td>2026-06-24</td>
    <td>6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8663" target=3D"= _blank" rel=3D"noopener">CVE-2026-8663</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect Sed Plugin</td> <td>Arbitrary File Read vulnerability in Rapid7 InsightConnect Sed Plugin o=
    n Linux allows authenticated attackers to read arbitrary files via the expr= ession parameter due to insufficient input validation.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9153" target=3D"= _blank" rel=3D"noopener">CVE-2026-9153</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect SQLmap Plugin</td>
    <td>OS Command Injection vulnerability in Rapid7 InsightConnect SQLmap Plug=
    in on Linux allows authenticated attackers to execute arbitrary OS commands=
    via the api_host or api_port parameters during connection configuration du=
    e to insufficient input validation.</td>
    <td>2026-06-25</td>
    <td>6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8659" target=3D"= _blank" rel=3D"noopener">CVE-2026-8659</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect Tcpdump Plugin</td>
    <td>OS Command Injection vulnerability in Rapid7 InsightConnect Tcpdump Plu= gin on Linux allows authenticated attackers to execute arbitrary OS command=
    s via the options or filter parameters due to insufficient input sanitizati=
    on in shell command construction.</td>
    <td>2026-06-25</td>
    <td>6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8658" target=3D"= _blank" rel=3D"noopener">CVE-2026-8658</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Logging Subsystem for Red Hat OpenShi= ft</td>
    <td>A missing authorization flaw was found in the OpenShift Cluster Logging=
    Operator. The operator creates and forwards ServiceAccount tokens to outpu=
    t destinations without verifying that the ClusterLogForwarder creator has p= ermission to use those credentials, allowing a delegated editor to exfiltra=
    te SA tokens and escalate privileges.</td>
    <td>2026-06-23</td>
    <td>6.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10609" target=3D= "_blank" rel=3D"noopener">CVE-2026-10609</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Pen Drive Powered by Red Hat Lightspe= ed</td>
    <td>A flaw was found in the Pen Drive report generator. Cluster-sourced dat=
    a is rendered into HTML reports without proper escaping or sanitization. An=
    attacker with cluster administrator privileges can inject a stored cross-s= ite scripting (XSS) payload into cluster objects (such as ClusterVersion sp= ec.channel) that executes in the browser of any user who opens the generate=
    d HTML report.</td>
    <td>2026-06-25</td>
    <td>6.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13083" target=3D= "_blank" rel=3D"noopener">CVE-2026-13083</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Apicurio Registry 3<=

    <td>A flaw was found in Apicurio Registry. The DocumentBuilderAccessor corr= ectly blocks external DTD and schema access but does not disable DOCTYPE de= clarations or enable FEATURE_SECURE_PROCESSING. An attacker with artifact-w= rite permission can upload XML documents with internal entity-expansion pay= loads (billion-laughs variant) that cause CPU and heap exhaustion, partiall=
    y mitigated by the JAXP default 64,000 entity-expansion limit.</td> <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12993" target=3D= "_blank" rel=3D"noopener">CVE-2026-12993</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Keycloak 26.4</td>
    <td>A flaw was found in Keycloak's client registration service. A remote at= tacker, possessing a previously issued Registration Access Token (RAT), cou=
    ld exploit this vulnerability to re-enable a client that an administrator h=
    ad explicitly disabled. This bypasses security controls, allowing the attac= ker to reset the client's secret and potentially regain privileged API acce= ss. The primary impact includes unauthorized information disclosure and pot= ential integrity compromise.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9705" target=3D"= _blank" rel=3D"noopener">CVE-2026-9705</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Keycloak 26.4</td>
    <td>A flaw was found in Keycloak. A realm administrator with the "manage-re= alm" role can exploit this vulnerability by submitting an arbitrary filesys= tem path as a keystore parameter when creating a key provider component. Th=
    is allows the administrator to probe arbitrary filesystem paths, determinin=
    g which files exist and are readable by the Keycloak process. This informat= ion disclosure could be used to identify high-value targets for follow-on a= ttacks.</td>
    <td>2026-06-25</td>
    <td>4.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9083" target=3D"= _blank" rel=3D"noopener">CVE-2026-9083</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat build of Keycloak 26.4</td>
    <td>A flaw was found in org.keycloak.authorization. An authenticated user w= ith a granted User-Managed Access (UMA) permission ticket for one resource = can exploit this by using a specific permission request prefix to bypass pe= r-resource access control. This allows the user to gain unauthorized access=
    to all resources of that type within the same resource server, even if the=
    y do not have a ticket for those specific resources. This vulnerability req= uires the resource server to be configured in PERMISSIVE policy enforcement=
    mode and affects typed resources with ownerManagedAccess enabled, where no=
    explicit policy protects the resource type. The primary consequence is una= uthorized information disclosure or modification of resources.</td> <td>2026-06-25</td>
    <td>4.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9799" target=3D"= _blank" rel=3D"noopener">CVE-2026-9799</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td>
    <td>A flaw was found in the community.general Ansible collection's nexmo mo= dule. The module constructs HTTP requests to the Vonage/Nexmo SMS API by en= coding API credentials (api_key and api_secret) into URL query parameters a=
    nd sending them via GET requests. This causes credentials to be exposed in = web server access logs, proxy logs, HTTP Referer headers, and network monit= oring tools, despite the Ansible argument specification marking these param= eters as no_log. An attacker with access to any of these logging or monitor= ing points can obtain the full API credentials and gain unauthorized access=
    to the victim's Vonage/Nexmo account.</td>
    <td>2026-06-23</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11820" target=3D= "_blank" rel=3D"noopener">CVE-2026-11820</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td> <td>Module: plugins/modules/keyring_info.py CVSS 3.1: 5.5 MEDIUM - AV:L/AC:= L/PR:L/UI:N/S:U/C:H/I:N/A:N Issue: The module retrieves a passphrase from t=
    he OS native keyring (GNOME Keyring, macOS Keychain, Windows Credential Man= ager) and places it directly into result["passphrase"] with no output suppr= ession, no no_log protection, and no documentation warning. Root Cause: Lin=
    e 105 (protected): keyring_password=3Ddict(type=3D"str", required=3DTrue, n= o_log=3DTrue) Line 127 (NOT protected): result["passphrase"] =3D passphrase=
    Observed Output: { "changed": false, "passphrase": "MyMasterP@ssw0rd!SSH_K= ey_Secret" } Visible via register + debug: { "keyring_result": { "changed":=
    false, "passphrase": "MyMasterP@ssw0rd!SSH_Key_Secret" } } Impact: Master = passwords, SSH key passphrases and service credentials appear in all Ansibl=
    e output register: keyring_result followed by debug: var=3Dkeyring_result p= rints passphrase in full Ansible fact caching backends (Redis, JSON file, m= emcached) may persist the passphrase AWX/Tower job logs silently store the = live credential Fix: module.exit_json(changed=3DFalse, passphrase=3Dpassphr= ase, _ansible_no_log=3DTrue) Also add a documentation warning requiring cal= lers to use no_log: true at the task level. PoCs Fig 1: PoC execution showi=
    ng passphrase in plaintext output Fig 2: Source code showing no_log=3DTrue =
    on input (line 105) vs unprotected output (line 127)</td>
    <td>2026-06-23</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11819" target=3D= "_blank" rel=3D"noopener">CVE-2026-11819</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td>
    <td>A heap-based buffer overflow was found in dnsmasq. When DNSSEC validati=
    on and query logging are both enabled, logging of DS or DNSKEY replies cont= aining unsupported algorithm or digest types can cause dnsmasq to write pas=
    t the end of an internal logging buffer. A remote attacker able to supply s= uch a DNS response may crash the dnsmasq process, resulting in denial of se= rvice.</td>
    <td>2026-06-22</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12725" target=3D= "_blank" rel=3D"noopener">CVE-2026-12725</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td>
    <td>An out-of-bounds read vulnerability exists in dnsmasq's find_soa() func= tion in src/rfc1035.c. When parsing NS section records, extract_name() is c= alled with extrabytes=3D0, failing to validate that 10 additional bytes exi=
    st for fixed-length DNS record fields. A remote attacker controlling a DNS = zone can exploit this via a crafted NXDOMAIN response to cause a 10-byte he=
    ap out-of-bounds read, potentially accessing stale data from prior transact= ions.</td>
    <td>2026-06-23</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12969" target=3D= "_blank" rel=3D"noopener">CVE-2026-12969</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td>
    <td>A flaw was found in OpenSSH. A local unprivileged attacker on a Linux c= lient host can hijack client-side X11 forwarding connections. This is possi= ble by pre-binding the preferred abstract X socket name when X11 forwarding=
    is enabled and a local UNIX-domain X socket is used. A successful attack c=
    an compromise the confidentiality of forwarded X11 traffic, including sensi= tive window contents and input, and may allow some manipulation of the forw= arded session.</td>
    <td>2026-06-23</td>
    <td>5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55655" target=3D= "_blank" rel=3D"noopener">CVE-2026-55655</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td>
    <td>The fix for CVE-2026-2443 was regressed by a subsequent rework commit t= hat replaced specific overflow checks with a general signed comparison. Whe=
    n a client sends a Range request with a suffix length exceeding the content=
    size, the resulting negative start value is not properly clamped, leading =
    to malformed HTTP 206 responses and log flooding.</td>
    <td>2026-06-22</td>
    <td>4.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12549" target=3D= "_blank" rel=3D"noopener">CVE-2026-12549</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td>
    <td>A flaw was found in the GStreamer gst-plugins-bad package. When process= ing a malformed H.266/VVC video stream with a crafted aspect ratio indicato=
    r value, the H.266 parser performs an out-of-bounds read of up to 8 bytes f= rom adjacent memory. This flaw allows an attacker to craft a malicious H.26=
    6 video file or stream that, when processed by a GStreamer-based applicatio=
    n, could leak limited memory contents through video metadata, potentially e= xposing sensitive information from the application's address space.</td> <td>2026-06-23</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12891" target=3D= "_blank" rel=3D"noopener">CVE-2026-12891</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td>
    <td>A flaw was found in GStreamer's gst-plugins-bad package. When processin=
    g a specially crafted H.264 video file containing malformed MVC or SVC exte= nsion slice NAL units, a 1-byte heap out-of-bounds read can occur during pa= rsing. This happens when the parser attempts to check slice boundary inform= ation without first verifying that the NAL unit contains enough data beyond=
    the extension header. An attacker could exploit this by tricking a user in=
    to opening a malicious H.264 video file, potentially causing the applicatio=
    n to crash or leak a single byte of heap memory.</td>
    <td>2026-06-23</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12892" target=3D= "_blank" rel=3D"noopener">CVE-2026-12892</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td>
    <td>A flaw was found in OpenSSH. A malicious SSH server can exploit a doubl=
    e free vulnerability in the Diffie-Hellman Group Exchange (DH-GEX) client p= ath. This occurs during FIPS (Federal Information Processing Standards) mod=
    e known-group validation when the client processes attacker-controlled DH-G=
    EX group parameters. Successful exploitation leads to client-side process t= ermination, resulting in a Denial of Service (DoS).</td>
    <td>2026-06-23</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55653" target=3D= "_blank" rel=3D"noopener">CVE-2026-55653</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat OpenShift Virtualization 4</t=

    <td>A flaw was found in KubeVirt's virt-handler domain notify server. The g= RPC handlers for HandleDomainEvent and HandleK8SEvent derive the VMI identi=
    ty (namespace/name) solely from the request body without validating it agai= nst the connection's origin. Each virt-launcher pod connects through a per-= VMI pipe socket, but no identity tag is propagated from the pipe path to th=
    e server handlers. This allows a compromised virt-launcher process to send = forged domain lifecycle events for any other VMI scheduled on the same node=
    , causing virt-handler to erroneously update that VMI's state and disrupt i=
    ts lifecycle management.</td>
    <td>2026-06-24</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13208" target=3D= "_blank" rel=3D"noopener">CVE-2026-13208</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat OpenShift Virtualization 4</t=

    <td>A server-side request forgery (SSRF) flaw was found in KubeVirt's virt-= api port-forward handler. When processing a port-forward request to a Virtu= alMachineInstance (VMI), virt-api reads the target IP from vmi.Status.Inter= faces[0].IP and passes it directly to net.Dial() without validation. For VM=
    Is using non-masquerade network bindings (bridge or secondary-only), this I=
    P is reported by the QEMU guest agent running inside the VM and is fully co= ntrollable by the VM owner. An attacker with kubevirt.io:edit permissions c=
    an create a VM with a modified guest agent that reports an arbitrary IP add= ress, then request port-forward to establish a bidirectional TCP tunnel fro=
    m virt-api's cluster-internal network position to any routable destination,=
    bypassing NetworkPolicy isolation.</td>
    <td>2026-06-25</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13318" target=3D= "_blank" rel=3D"noopener">CVE-2026-13318</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat OpenShift Virtualization 4</t=

    <td>A flaw was found in KubeVirt's virt-handler network cache handling. The=
    WriteToCachedFile function writes data to a launcher-rooted path using os.= WriteFile and os.Chown without symlink protection. A user with access to th=
    e virt-launcher container can plant a symlink at the cache file path, causi=
    ng virt-handler to follow it and overwrite an arbitrary host file with JSON=
    content and change its ownership.</td>
    <td>2026-06-25</td>
    <td>4.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13218" target=3D= "_blank" rel=3D"noopener">CVE-2026-13218</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat OpenShift Virtualization 4</t=

    <td>A flaw was found in KubeVirt's network annotation generator. When a ten= ant creates a VirtualMachineInstance with a Multus network configuration, t=
    he supplied networkName value is written verbatim into the launcher pod's v= 1.multus-cni.io/default-network annotation without format validation or san= itization. The only admission check rejects empty strings; no DNS-1123 form=
    at validation, JSON detection, or special character rejection is performed.=
    When the ExternalNetResourceInjection Beta feature gate is enabled (off by=
    default, cluster-admin only), the NAD lookup that would otherwise catch ma= lformed names is skipped by design. A tenant with kubevirt.io:edit permissi= ons can inject a JSON-formatted NetworkSelectionElement array specifying an=
    arbitrary namespace, NAD name, static IP address, and MAC address. Multus =
    on the node parses this JSON and attaches the launcher pod to the specified=
    network attachment in any namespace, enabling cross-namespace network acce=
    ss and IP/MAC impersonation on network segments normally segregated from te= nant workloads. The ExternalNetResourceInjection feature gate was introduce=
    d in KubeVirt v1.8.0 (first shipped in OpenShift Virtualization 4.21).</td> <td>2026-06-26</td>
    <td>4.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13434" target=3D= "_blank" rel=3D"noopener">CVE-2026-13434</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Satellite 6.19</td>
    <td>A flaw was found in foreman-mcp-server. This component utilizes two dis= tinct logging mechanisms that can expose sensitive session and authenticati=
    on data. One mechanism logs session identifiers, which are treated as authe= ntication credentials, at an informational level. The other, when debug log= ging is enabled, incompletely sanitizes HTTP request headers, leading to th=
    e cleartext logging of sensitive information such as authorization tokens a=
    nd API keys. This vulnerability can result in a confidentiality breach, as = sensitive authentication data is persisted in plain text within container l= ogs, increasing the risk if logs are forwarded to a centralized platform.</=

    <td>2026-06-23</td>
    <td>6.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9073" target=3D"= _blank" rel=3D"noopener">CVE-2026-9073</a></td>
    </tr>

    <td class=3D"vendor-product">reepaydenmark--Frisbii Pay</td>
    <td>The Frisbii Pay plugin for WordPress is vulnerable to unauthorized modi= fication of data due to missing capability checks on the 'upload_csv' and '= process_batch' functions in all versions up to, and including, 1.8.9. This = makes it possible for authenticated attackers, with Subscriber-level access=
    and above, to upload arbitrary CSV data and overwrite WooCommerce payment = tokens, postmeta, and order meta records.</td>
    <td>2026-06-27</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-3462" target=3D"= _blank" rel=3D"noopener">CVE-2026-3462</a></td>
    </tr>

    <td class=3D"vendor-product">rentmy--RentMy Real-Time Rental Management Plu= gin</td>
    <td>The RentMy Real-Time Rental Management Plugin plugin for WordPress is v= ulnerable to authorization bypass in all versions up to, and including, 4.0= .4.1. This is due to the plugin not properly verifying that a user is autho= rized to perform an action. This makes it possible for unauthenticated atta= ckers to read, create, update, and delete event records stored in the rentm= y_events WordPress option, as well as overwrite the rentmy_locationId optio= n.</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8690" target=3D"= _blank" rel=3D"noopener">CVE-2026-8690</a></td>
    </tr>

    <td class=3D"vendor-product">rhewlif--Donation Thermometer</td> <td>Unauthenticated Broken Access Control in Donation Thermometer &lt;=3D 2= .2.7 versions.</td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-64636" target=3D= "_blank" rel=3D"noopener">CVE-2025-64636</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and = 7.10.12, in the visitors.info endpoint, https://developer.rocket.chat/apido= cs/get-visitor-information-by-id-1, token is returned in the response. It l= ooks like there's no use case for the token to be present in the response a=
    nd it would be a good security practice to remove it altogether. This vulne= rability is fixed in 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and = 7.10.12.</td>
    <td>2026-06-24</td>
    <td>6.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49278" target=3D= "_blank" rel=3D"noopener">CVE-2026-49278</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.0, the ImageElement component in packages/gazzodow=
    n renders user-controlled src values directly into &lt;a href&gt; and &lt;i=
    mg src&gt; attributes without protocol sanitization. Unlike the analogous L= inkSpan component - which uses sanitizeUrl to block javascript:, data:, and=
    vbscript: protocols - ImageElement passes the raw URL through unchanged. A=
    n authenticated user can post a markdown image with a javascript: URL that,=
    if clicked on an older browser, would execute arbitrary JavaScript in the = viewer's session. This vulnerability is fixed in 8.5.0.</td> <td>2026-06-24</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47733" target=3D= "_blank" rel=3D"noopener">CVE-2026-47733</a></td>
    </tr>

    <td class=3D"vendor-product">Roxnor--GetGenie</td>
    <td>Subscriber Sensitive Data Exposure in GetGenie &lt;=3D 4.4.2 versions.<=

    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57316" target=3D= "_blank" rel=3D"noopener">CVE-2026-57316</a></td>
    </tr>

    <td class=3D"vendor-product">rtk-ai--rtk</td>
    <td>@rtk-ai/rtk-rewrite transparently rewrites shell commands executed via = OpenClaw's exec tool to their RTK equivalents. In 1.0.0, the @rtk-ai/rtk-re= write OpenClaw plugin passes attacker-controlled input directly into a shel= l-backed execSync() template string without shell-safe escaping. JSON.strin= gify() wraps the value in double quotes and escapes inner double-quotes and=
    backslashes, but leaves $() and backtick shell metacharacters untouched. B= ecause execSync delegates execution to /bin/sh -c, the shell expands $(...)=
    substitutions even inside double-quoted strings, causing the injected subc= ommand to execute before rtk is invoked. An attacker who can influence the = exec tool's command parameter (e.g., via an LLM agent prompt or gateway/too= l-call input) achieves arbitrary OS command execution with the privileges o=
    f the plugin/gateway process.</td>
    <td>2026-06-23</td>
    <td>6.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55249" target=3D= "_blank" rel=3D"noopener">CVE-2026-55249</a></td>
    </tr>

    <td class=3D"vendor-product">rustfs--rustfs</td>
    <td>RustFS is a distributed object storage system built in Rust. In 1.0.0-b= eta.7 and earlier, the real-time metrics endpoint at /rustfs/admin/v3/metri=
    cs is accessible to any valid IAM user regardless of their assigned policy.=
    Every other admin handler in the codebase calls validate_admin_request to = enforce admin-action IAM checks; the MetricsHandler skips this call entirel=
    y. A restricted IAM user whose policy grants only access to their own bucke=
    t can read server-wide operational metrics including disk I/O statistics, n= etwork throughput, scanner cycle timing, and cluster RPC state.</td> <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55838" target=3D= "_blank" rel=3D"noopener">CVE-2026-55838</a></td>
    </tr>

    <td class=3D"vendor-product">samuelclay--NewsBlur</td>
    <td>NewsBlur before 14.5.0 contains a broken access control vulnerability t= hat allows authenticated users to read private notification feeds by supply= ing arbitrary user_id values to the GET /social/interactions endpoint witho=
    ut ownership verification. Attackers can enumerate user_id values to access=
    another user's follows, replies, and social activity without authorization= .</td>
    <td>2026-06-25</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56772" target=3D= "_blank" rel=3D"noopener">CVE-2026-56772</a></td>
    </tr>

    <td class=3D"vendor-product">secufor--Secufor_OAuth</td>
    <td>The Secufor_OAuth plugin for WordPress is vulnerable to unauthorized ac= cess in all versions up to, and including, 1.0.7. This is due to the plugin=
    not properly verifying that a user is authorized to perform an action. Thi=
    s makes it possible for unauthenticated attackers to disconnect the WordPre=
    ss site from its linked Secufor account by clearing the plugin's stored log=
    in token and user login configuration.</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7617" target=3D"= _blank" rel=3D"noopener">CVE-2026-7617</a></td>
    </tr>

    <td class=3D"vendor-product">SeedProd LLC.--SeedProd Pro</td>
    <td>Contributor Cross Site Scripting (XSS) in SeedProd Pro &lt; 6.19.5 vers= ions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57617" target=3D= "_blank" rel=3D"noopener">CVE-2026-57617</a></td>
    </tr>

    <td class=3D"vendor-product">seo_tools--Bulk SEO Image</td>
    <td>The Bulk SEO Image plugin for WordPress is vulnerable to Cross-Site Req= uest Forgery in versions up to and including 1.1. This is due to missing or=
    incorrect nonce validation on the plugin's settings page handler BulkSeoIm= age(), which dispatches to launchbulk() / BulkSeoImageGo() whenever the req= uest contains $_POST['bulkseoimage']. No wp_nonce_field() is emitted in the=
    form and no check_admin_referer()/wp_verify_nonce() is performed before bu= lk-overwriting the _wp_attachment_image_alt post meta for every image attac= hed to every published post and/or page. This makes it possible for unauthe= nticated attackers to bulk-overwrite image ALT-text metadata across the sit=
    e via a forged request granted they can trick a site administrator into per= forming an action such as clicking on a link.</td>
    <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11997" target=3D= "_blank" rel=3D"noopener">CVE-2026-11997</a></td>
    </tr>

    <td class=3D"vendor-product">SEOPress Free--SEOPress PRO</td>
    <td>Contributor Broken Access Control in SEOPress PRO &lt;=3D 9.1.1 version= s.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57430" target=3D= "_blank" rel=3D"noopener">CVE-2026-57430</a></td>
    </tr>

    <td class=3D"vendor-product">Shenzhen i365-Tech Co. Ltd.--Setracker2 Parent=
    al Control App (Android) package com.tgelec.setracker</td>
    <td>Setracker2 Android Companion App com.tgelec.setracker versions 3.1.5 an=
    d prior have a predictable registration ID derived from IMEI. The enrollmen=
    t system lacks additional authentication before assignment. If an attacker =
    is able to obtain the registration ID, they would be able to arbitrarily en= roll watches belonging to other users.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9219" target=3D"= _blank" rel=3D"noopener">CVE-2026-9219</a></td>
    </tr>

    <td class=3D"vendor-product">ShortPixel--ShortPixel Adaptive Images</td> <td>Unauthenticated Arbitrary File Deletion in ShortPixel Adaptive Images &= lt;=3D 3.11.4 versions.</td>
    <td>2026-06-26</td>
    <td>5.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56066" target=3D= "_blank" rel=3D"noopener">CVE-2026-56066</a></td>
    </tr>

    <td class=3D"vendor-product">Significant-Gravitas--AutoGPT</td>
    <td>AutoGPT is a workflow automation platform for creating, deploying, and = managing continuous artificial intelligence agents. Prior to , the `POST /a= pi/integrations/webhooks/{webhook_id}/ping` endpoint fetches the target web= hook by primary key alone without verifying that the webhook belongs to the=
    authenticated user. Any authenticated user can supply an arbitrary webhook= _id to confirm webhook existence, leak the webhook's OAuth provider type, a=
    nd in some cases trigger a ping delivery on behalf of another user. This vu= lnerability is fixed in .</td>
    <td>2026-06-26</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56823" target=3D= "_blank" rel=3D"noopener">CVE-2026-56823</a></td>
    </tr>

    <td class=3D"vendor-product">SiteGround--SiteGround Email Marketing</td> <td>Unauthenticated Broken Access Control in SiteGround Email Marketing &lt= ;=3D 1.7.5 versions.</td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-24547" target=3D= "_blank" rel=3D"noopener">CVE-2026-24547</a></td>
    </tr>

    <td class=3D"vendor-product">siyuan-note--siyuan</td>
    <td>SiYuan is an open-source personal knowledge management system. Prior to=
    3.7.0, the /api/icon/getDynamicIcon endpoint is explicitly excluded from a= uthentication in SiYuan's kernel router (router.go, "=C3=A4=C2=B8=C2=8D=C3= =A9=C5=93=E2=82=AC=C3=A8=C2=A6=C2=81=C3=A9=E2=80=B0=C2=B4=C3=A6=C2=9D=C6=92=
    " -- no auth needed). When called with type=3D8 and a valid block id parame= ter, this endpoint invokes RenderDynamicIconContentTemplate, which executes=
    a Go template that includes the querySQL and queryBlocks functions. These = functions run arbitrary SELECT statements against the SiYuan SQLite databas=
    e. An unauthenticated network-adjacent attacker who knows a valid block ID = can exfiltrate all user note content, tags, asset references, and block att= ributes from the database. This vulnerability is fixed in 3.7.0.</td> <td>2026-06-24</td>
    <td>5.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54068" target=3D= "_blank" rel=3D"noopener">CVE-2026-54068</a></td>
    </tr>

    <td class=3D"vendor-product">StatCounter--StatCounter</td>
    <td>Contributor Cross Site Scripting (XSS) in StatCounter &lt;=3D 2.1.1 ver= sions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57629" target=3D= "_blank" rel=3D"noopener">CVE-2026-57629</a></td>
    </tr>

    <td class=3D"vendor-product">studiowombat--Shoppable Images Lite</td> <td>Subscriber Broken Access Control in Shoppable Images Lite &lt;=3D 1.3 v= ersions.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57649" target=3D= "_blank" rel=3D"noopener">CVE-2026-57649</a></td>
    </tr>

    <td class=3D"vendor-product">Stylemix--MasterStudy LMS</td>
    <td>Subscriber Broken Access Control in MasterStudy LMS &lt;=3D 3.7.30 vers= ions.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57640" target=3D= "_blank" rel=3D"noopener">CVE-2026-57640</a></td>
    </tr>

    <td class=3D"vendor-product">surbma--Surbma | Infusionsoft Shortcode</td> <td>The Surbma | Infusionsoft Shortcode plugin for WordPress is vulnerable =
    to Stored Cross-Site Scripting via the 'infusionsoft-form' shortcode in ver= sions up to, and including, 2.0.1. This is due to insufficient input saniti= zation and output escaping on user-supplied 'account' and 'id' shortcode at= tributes in the surbma_infusionsoft_shortcode_shortcode() function, which a=
    re concatenated directly into a &lt;script&gt; tag's src attribute. This ma= kes it possible for authenticated attackers, with contributor-level access = and above, to inject arbitrary web scripts in pages that will execute whene= ver a user accesses an injected page.</td>
    <td>2026-06-27</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11597" target=3D= "_blank" rel=3D"noopener">CVE-2026-11597</a></td>
    </tr>

    <td class=3D"vendor-product">SureCart--SureCart</td>
    <td>Subscriber Cross Site Scripting (XSS) in SureCart &lt;=3D 4.2.2 version= s.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57313" target=3D= "_blank" rel=3D"noopener">CVE-2026-57313</a></td>
    </tr>

    <td class=3D"vendor-product">templatescoderthemes--Spexo</td>
    <td>The Spexo theme for WordPress is vulnerable to unauthorized access due =
    to a missing capability check on the activate_plugin function in all versio=
    ns up to, and including, 2.0.11. This makes it possible for authenticated a= ttackers, with Subscriber-level access and above, to activate a limited set=
    of plugins.</td>
    <td>2026-06-27</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12471" target=3D= "_blank" rel=3D"noopener">CVE-2026-12471</a></td>
    </tr>

    <td class=3D"vendor-product">tenable--Nessus</td>
    <td>A SQL injection vulnerability in Nessus allows a remote, unauthenticate=
    d attacker who controls reverse DNS records for a scanned host to inject ma= licious SQL into the scan results database, potentially enabling exfiltrati=
    on of scan-result data.</td>
    <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57587" target=3D= "_blank" rel=3D"noopener">CVE-2026-57587</a></td>
    </tr>

    <td class=3D"vendor-product">Themegrill--User Registration</td> <td>Unauthenticated Broken Access Control in User Registration &lt;=3D 5.2.=
    2 versions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52701" target=3D= "_blank" rel=3D"noopener">CVE-2026-52701</a></td>
    </tr>

    <td class=3D"vendor-product">Themeisle--Neve PRO</td>
    <td>Contributor Cross Site Scripting (XSS) in Neve PRO &lt;=3D 3.1.2 versio= ns.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57618" target=3D= "_blank" rel=3D"noopener">CVE-2026-57618</a></td>
    </tr>

    <td class=3D"vendor-product">Themeisle--PPOM for WooCommerce</td>
    <td>Improper Access Control vulnerability in Themeisle PPOM for WooCommerce=
    allows Exploiting Incorrectly Configured Access Control Security Levels. T= his issue affects PPOM for WooCommerce: from n/a through 33.0.18.</td> <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56050" target=3D= "_blank" rel=3D"noopener">CVE-2026-56050</a></td>
    </tr>

    <td class=3D"vendor-product">themeisle--Stripe Payment Forms by WP Full Pay=
    Accept Credit Card Payments, Donations &amp; Subscriptions</td>
    <td>The WP Full Stripe Free plugin for WordPress is vulnerable to Missing A= uthorization in versions up to, and including, 8.4.3 via the wpfs_update_fa= iled_payment_status AJAX action. The handler is registered through both wp_= ajax_ and wp_ajax_nopriv_ hooks and the underlying update_failed_payment_st= atus() function performs no capability check, no nonce verification, and no=
    logged-in check before calling $this-&gt;db-&gt;updatePaymentByEventId() w= ith attacker-controlled POST parameters. This makes it possible for unauthe= nticated attackers who can obtain a valid Stripe Payment Intent ID for the = target site (Payment Intent IDs are exposed to the customer browser during = normal Stripe.js checkout flows) to manipulate payment records in the site'=
    s database, marking previously successful payments as failed and overwritin=
    g failure codes and messages with attacker-supplied values.</td> <td>2026-06-27</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12432" target=3D= "_blank" rel=3D"noopener">CVE-2026-12432</a></td>
    </tr>

    <td class=3D"vendor-product">Themeum--Kirki</td>
    <td>Subscriber Server Side Request Forgery (SSRF) in Kirki &lt;=3D 6.0.11 v= ersions.</td>
    <td>2026-06-26</td>
    <td>4.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57627" target=3D= "_blank" rel=3D"noopener">CVE-2026-57627</a></td>
    </tr>

    <td class=3D"vendor-product">Tim Strifler--Exclusive Addons Elementor</td> <td>Improper Neutralization of Input During Web Page Generation ('Cross-sit=
    e Scripting') vulnerability in Tim Strifler Exclusive Addons Elementor allo=
    ws Stored XSS. This issue affects Exclusive Addons Elementor: from n/a thro= ugh 2.7.9.8.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57620" target=3D= "_blank" rel=3D"noopener">CVE-2026-57620</a></td>
    </tr>

    <td class=3D"vendor-product">tomojitakasu--RTKLIB</td>
    <td>RTKLIB through 2.4.3 contains an off-by-one out-of-bounds read vulnerab= ility in the decode_ssr3 function at src/rtcm3.c:1446 that allows remote at= tackers to trigger a global buffer overflow via crafted RTCM3 SSR messages = with attacker-controlled signal mode fields. Remote attackers can exploit t= his vulnerability by sending malicious SSR correction streams over NTRIP or=
    serial connections to cause denial of service or crash RTKLIB rovers and C= ORS servers.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56787" target=3D= "_blank" rel=3D"noopener">CVE-2026-56787</a></td>
    </tr>

    <td class=3D"vendor-product">tomojitakasu--RTKLIB</td>
    <td>RTKLIB through 2.4.3 contains a heap buffer overflow vulnerability in t=
    he readrnxobsb function in src/rinex.c that allows attackers to trigger mem= ory corruption by failing to clamp satellite count values from RINEX epoch = headers. Attackers can craft malicious RINEX files declaring more than 64 s= atellites per epoch to cause heap buffer overflow writes and out-of-bounds = stack reads, crashing RTKLIB-based applications including rnx2rtkp and RTKP= OST.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56789" target=3D= "_blank" rel=3D"noopener">CVE-2026-56789</a></td>
    </tr>

    <td class=3D"vendor-product">tomojitakasu--RTKLIB</td>
    <td>RTKLIB through 2.4.3 contains an out-of-bounds read vulnerability in ge= tcodepri function when processing unrecognized RINEX observation codes, all= owing attackers to trigger denial of service. Crafted RINEX files with unkn= own observation types cause negative array indexing into the codepris table=
    , resulting in reliable crashes and potential memory disclosure of adjacent=
    global data.</td>
    <td>2026-06-25</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56788" target=3D= "_blank" rel=3D"noopener">CVE-2026-56788</a></td>
    </tr>

    <td class=3D"vendor-product">ToolJet--ToolJet</td>
    <td>ToolJet is the open-source foundation am AI-native platform for buildin=
    g and deploying internal tools, workflows and AI agents. Prior to 3.20.1780= -lts, the authenticated endpoint POST /api/data-sources/decrypt returns the=
    decrypted plaintext for any credential whose credential_id is supplied in = the request body. Unlike every neighbouring data-source route, this handler=
    is not protected by ValidateDataSourceGuard, does not receive the calling = @User(), and the underlying CredentialsService.getValue() looks the credent= ial up by id only, with no organization scoping. As a result, any authentic= ated user of any organization can decrypt the data-source secrets of any ot= her organization by supplying that organization's credential_id - a cross-t= enant confidentiality breach. This vulnerability is fixed in 3.20.1780-lts.= </td>
    <td>2026-06-25</td>
    <td>6.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55411" target=3D= "_blank" rel=3D"noopener">CVE-2026-55411</a></td>
    </tr>

    <td class=3D"vendor-product">TortoiseGit team--TortoiseGit</td>
    <td>Argument Injection in TortoiseGitBlame via Malicious Git History Filena= mes Leads to Arbitrary File Write in TortoiseGit</td>
    <td>2026-06-24</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11968" target=3D= "_blank" rel=3D"noopener">CVE-2026-11968</a></td>
    </tr>

    <td class=3D"vendor-product">trainingbusinesspros--Groundhogg CRM, Newslett= ers, and Marketing Automation</td>
    <td>The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for = WordPress is vulnerable to generic SQL Injection via the 'after' parameter =
    in all versions up to, and including, 4.5.4 due to insufficient escaping on=
    the user supplied parameter and lack of sufficient preparation on the exis= ting SQL query. This makes it possible for authenticated attackers, with Sa= les Manager-level access and above, to append additional SQL queries into a= lready existing queries that can be used to extract sensitive information f= rom the database. The AJAX handler wp_ajax_groundhogg_get_contacts_table ha=
    s its capability check commented out and performs no nonce verification, me= aning any authenticated user regardless of role can reach the vulnerable co=
    de path.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13226" target=3D= "_blank" rel=3D"noopener">CVE-2026-13226</a></td>
    </tr>

    <td class=3D"vendor-product">trainingbusinesspros--Groundhogg CRM, Newslett= ers, and Marketing Automation</td>
    <td>The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for = WordPress is vulnerable to generic SQL Injection via the 'search' parameter=
    in all versions up to, and including, 4.5.5 due to insufficient escaping o=
    n the user supplied parameter and lack of sufficient preparation on the exi= sting SQL query. This makes it possible for authenticated attackers, with m= arketer-level access and above, to append additional SQL queries into alrea=
    dy existing queries that can be used to extract sensitive information from = the database.</td>
    <td>2026-06-27</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13331" target=3D= "_blank" rel=3D"noopener">CVE-2026-13331</a></td>
    </tr>

    <td class=3D"vendor-product">trainingbusinesspros--Groundhogg CRM, Newslett= ers, and Marketing Automation</td>
    <td>The Groundhogg - CRM, Newsletters, and Marketing Automation plugin for = WordPress is vulnerable to generic SQL Injection via 'query[select]' Parame= ter in all versions up to, and including, 4.5.5 due to insufficient escapin=
    g on the user supplied parameter and lack of sufficient preparation on the = existing SQL query. This makes it possible for authenticated attackers, wit=
    h Sales Representative-level access and above, to append additional SQL que= ries into already existing queries that can be used to extract sensitive in= formation from the database. The sanitized Contact_Query code path can be b= ypassed by supplying an invalid filter type (e.g., query[filters][0][0][typ= e]=3Dinvalid_filter_nonexistent), causing a FilterException to be caught an=
    d execution to fall through to the unsanitized Legacy_Contact_Query path.</=

    <td>2026-06-27</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13333" target=3D= "_blank" rel=3D"noopener">CVE-2026-13333</a></td>
    </tr>

    <td class=3D"vendor-product">TryGhost--Ghost</td>
    <td>Ghost is a Node.js content management system. From 6.0.9 until 6.21.1, = when making an external request, it is possible to bypass the IP filter tha=
    t ensures the request isn't going to an internal service using an IPv6 lite= ral which maps to a private IPv4 address. This vulnerability is fixed in 6.= 21.1.</td>
    <td>2026-06-24</td>
    <td>5.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53944" target=3D= "_blank" rel=3D"noopener">CVE-2026-53944</a></td>
    </tr>

    <td class=3D"vendor-product">TryGhost--Ghost</td>
    <td>Ghost is a Node.js content management system. From 6.19.4 until 6.21.1,=
    when re-rendering posts, Ghost would refetch missing image dimensions by i= ssuing an outbound HTTP request to the URL stored on an image card - withou=
    t restricting that URL to trusted image hosts. An authenticated staff user = able to create or edit posts could therefore point an image card at an atta= cker-chosen host and cause the Ghost server to request it on their behalf, = including hosts on internal networks or cloud instance metadata endpoints t= hat would not normally be reachable from the public internet. This vulnerab= ility is fixed in 6.21.1.</td>
    <td>2026-06-24</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53946" target=3D= "_blank" rel=3D"noopener">CVE-2026-53946</a></td>
    </tr>

    <td class=3D"vendor-product">TryGhost--Ghost</td>
    <td>Ghost is a Node.js content management system. From 5.18.0 until 6.21.1,=
    a discrepancy in responses from the members signin endpoints made it possi= ble for an unauthenticated attacker to determine whether a given email addr= ess belongs to a registered member of a Ghost site. This vulnerability is f= ixed in 6.21.1.</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53947" target=3D= "_blank" rel=3D"noopener">CVE-2026-53947</a></td>
    </tr>

    <td class=3D"vendor-product">TryGhost--Ghost</td>
    <td>Ghost is a Node.js content management system. From 6.19.4 until 6.21.1,=
    insufficient validation of the client-supplied Content-Type on Ghost's Adm=
    in API file upload endpoint allowed uploaded files to be served from the si=
    te with an attacker-chosen content type on S3/GCS storage backends. On inst= allations that serve uploaded files from the same origin as the site, this = could have been used to facilitate stored cross-site scripting against site=
    visitors or staff. This vulnerability is fixed in 6.21.1.</td> <td>2026-06-24</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53948" target=3D= "_blank" rel=3D"noopener">CVE-2026-53948</a></td>
    </tr>

    <td class=3D"vendor-product">TryGhost--Ghost</td>
    <td>Ghost is a Node.js content management system. From 5.46.1 until 6.21.2,=
    the validation applied to filters on the public API endpoints could be par= tially bypassed, making it possible to reveal private fields via a brute fo= rce attack. If SQLite was used as the database password hashes were fully a= ccessible. If MySQL was used as the database the password hashes' case (upp= ercase / lowercase) would have been lost, which would likely have rendered =
    a further brute force attack on the discovered hashes fruitless. This vulne= rability is fixed in 6.21.2.</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53949" target=3D= "_blank" rel=3D"noopener">CVE-2026-53949</a></td>
    </tr>

    <td class=3D"vendor-product">TryGhost--Ghost</td>
    <td>Ghost is a Node.js content management system. From 6.0.9 until 6.21.1, = Ghost's private-IP check for outbound HTTP requests could be bypassed via D=
    NS rebinding, allowing an attacker to coerce the Ghost server into reaching=
    hosts on internal networks through features that issue external fetches. T= his vulnerability is fixed in 6.21.1.</td>
    <td>2026-06-24</td>
    <td>4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53945" target=3D= "_blank" rel=3D"noopener">CVE-2026-53945</a></td>
    </tr>

    <td class=3D"vendor-product">tychesoftwares--Abandoned Cart Lite for WooCom= merce</td>
    <td>Unauthenticated Cross Site Request Forgery (CSRF) in Abandoned Cart Lit=
    e for WooCommerce &lt;=3D 6.8.0 versions.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57637" target=3D= "_blank" rel=3D"noopener">CVE-2026-57637</a></td>
    </tr>

    <td class=3D"vendor-product">tychesoftwares--Payment Gateway Based Fees and=
    Discounts for WooCommerce</td>
    <td>Unauthenticated Insecure Direct Object References (IDOR) in Payment Gat= eway Based Fees and Discounts for WooCommerce &lt;=3D 3.0.0 versions.</td> <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56048" target=3D= "_blank" rel=3D"noopener">CVE-2026-56048</a></td>
    </tr>

    <td class=3D"vendor-product">ueberdosis--tiptap-php</td>
    <td>Tiptap for PHP before version 2.1.1 contains an input validation vulner= ability that allows authenticated attackers to cause a denial of service by=
    submitting Tiptap JSON with the attrs.href field set to an array instead o=
    f a string, causing an unhandled TypeError in the Link::isAllowedUri() func= tion when passed to preg_match(). Attackers can persist malformed JSON reco= rds that permanently crash the server-side HTML rendering pipeline for all = subsequent viewers of that record until the database entry is manually repa= ired.</td>
    <td>2026-06-24</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47110" target=3D= "_blank" rel=3D"noopener">CVE-2026-47110</a></td>
    </tr>

    <td class=3D"vendor-product">ultrajson--ultrajson</td>
    <td>UltraJSON is a fast JSON encoder and decoder written in pure C with bin= dings for Python 3.7+. Prior to 5.13.0, ujson.dumps() (or ujson.dump() or u= json.encode()) have a reject_bytes=3DFalse option. When set, they may accep=
    t malformed or truncated UTF-8 byte sequences, silently rewriting them into=
    different Unicode characters instead of rejecting them. This leads to inpu=
    t validation bypass and data integrity issues. This vulnerability is fixed =
    in 5.13.0.</td>
    <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54911" target=3D= "_blank" rel=3D"noopener">CVE-2026-54911</a></td>
    </tr>

    <td class=3D"vendor-product">verenigingvanregistrars--Generate Security.txt= </td>
    <td>The Generate Security.txt plugin for WordPress is vulnerable to authori= zation bypass in all versions up to, and including, 1.0.12. This is due to = the plugin not properly verifying that a user is authorized to perform an a= ction. This makes it possible for authenticated attackers, with subscriber-= level access and above, to delete the site's security.txt file from the ser= ver filesystem or create the .well-known directory by directly invoking the=
    delete_securitytxt or create_wellknown_folder AJAX actions.</td> <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9616" target=3D"= _blank" rel=3D"noopener">CVE-2026-9616</a></td>
    </tr>

    <td class=3D"vendor-product">VillaTheme--Bopo WooCommerce Product Bundle Bu= ilder</td>
    <td>Unauthenticated Sensitive Data Exposure in Bopo - WooCommerce Product B= undle Builder &lt;=3D 1.1.6 versions.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57664" target=3D= "_blank" rel=3D"noopener">CVE-2026-57664</a></td>
    </tr>

    <td class=3D"vendor-product">VillaTheme--GIFT4U</td>
    <td>Unauthenticated Broken Access Control in GIFT4U &lt;=3D 1.0.10 versions= .</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57324" target=3D= "_blank" rel=3D"noopener">CVE-2026-57324</a></td>
    </tr>

    <td class=3D"vendor-product">vim--vim</td>
    <td>Vim is an open source, command line text editor. From 9.1.1784 until 9.= 2.0678, when the bundled zip plugin autoload/zip.vim falls back to PowerShe=
    ll to browse, read, extract, update or delete entries in a zip archive, it = builds the PowerShell command by inserting archive entry names that are quo= ted only for the shell, not for PowerShell. A crafted entry name can break = out of the intended string context and cause PowerShell to execute arbitrar=
    y commands with the privileges of the user running Vim, triggered by openin=
    g, viewing or extracting the archive. This vulnerability is fixed in 9.2.06= 78.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57453" target=3D= "_blank" rel=3D"noopener">CVE-2026-57453</a></td>
    </tr>

    <td class=3D"vendor-product">vim--vim</td>
    <td>Vim is an open source, command line text editor. Prior to 9.2.0662, the=
    dump_prefixes() function in src/spell.c walks a spell-file prefix trie ite= ratively with a depth counter while dumping the prefixes that apply to a wo= rd. The counter is bounded only by the trie structure itself; it is never c= hecked against the size of the fixed MAXWLEN-element stack arrays it indexe=
    s (prefix[], arridx[], curi[]). A crafted .spl file, loaded when the user d= umps the word list, can drive the descent arbitrarily deep, so the function=
    writes past the end of those arrays. This is a stack out-of-bounds write t= hat corrupts the call frame and crashes the editor. This vulnerability is f= ixed in 9.2.0662.</td>
    <td>2026-06-25</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55892" target=3D= "_blank" rel=3D"noopener">CVE-2026-55892</a></td>
    </tr>

    <td class=3D"vendor-product">vim--vim</td>
    <td>Vim is an open source, command line text editor. Prior to 9.2.0670, get= _text_props() in src/textprop.c reads a uint16 property count stored inline=
    after a line's text and returns it as the number of 32-byte textprop_T ent= ries that follow. The only check is a floor that guarantees room for a sing=
    le entry; the count is never checked against the amount of data actually pr= esent. A line that declares a large count while carrying little data causes=
    consumers to read far past the end of the line buffer. Such a line can be = delivered through a crafted undo file, leading to a crash. This vulnerabili=
    ty is fixed in 9.2.0670.</td>
    <td>2026-06-25</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57451" target=3D= "_blank" rel=3D"noopener">CVE-2026-57451</a></td>
    </tr>

    <td class=3D"vendor-product">vim--vim</td>
    <td>Vim is an open source, command line text editor. Prior to 9.2.0671, whe=
    n Vim opens a file encrypted with the VimCrypt~04! or VimCrypt~05! method (= xchacha20poly1305, requires the +sodium feature) whose body is shorter than=
    a single libsodium secretstream header, an unsigned length calculation und= erflows and a subsequent decryption call reads far past the end of the inpu=
    t buffer, crashing Vim. This vulnerability is fixed in 9.2.0671.</td> <td>2026-06-25</td>
    <td>5.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57452" target=3D= "_blank" rel=3D"noopener">CVE-2026-57452</a></td>
    </tr>

    <td class=3D"vendor-product">vinod-dalvi--Ivory Search WordPress Search Plu= gin</td>
    <td>The Ivory Search - WordPress Search Plugin plugin for WordPress is vuln= erable to Stored Cross-Site Scripting via 'menu_title' and 'menu_magnifier_= color' Settings in all versions up to, and including, 5.5.15 due to insuffi= cient input sanitization and output escaping. This makes it possible for au= thenticated attackers, with administrator-level access and above, to inject=
    arbitrary web scripts in pages that will execute whenever a user accesses =
    an injected page.</td>
    <td>2026-06-27</td>
    <td>4.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11356" target=3D= "_blank" rel=3D"noopener">CVE-2026-11356</a></td>
    </tr>

    <td class=3D"vendor-product">vllm-project--vllm</td>
    <td>vLLM is an inference and serving engine for large language models (LLMs=
    ). Prior to 0.22.0, vLLM's revision pinning controls do not consistently ap= ply to all artifacts loaded for a model. A deployment that supplies --revis= ion or --code-revision can still load dynamic code, GGUF files, image proce= ssors, retrieval side weights, or same-repository subfolder weights/config = from an unpinned/default revision. This is a supply-chain integrity issue f=
    or pinned vLLM deployments. Operators can believe they are serving a review=
    ed model revision while vLLM resolves behavior-affecting nested or sibling = artifacts outside that reviewed revision. This vulnerability is fixed in 0.= 22.0.</td>
    <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47155" target=3D= "_blank" rel=3D"noopener">CVE-2026-47155</a></td>
    </tr>

    <td class=3D"vendor-product">vllm-project--vllm</td>
    <td>vLLM is an inference and serving engine for large language models (LLMs=
    ). Prior to 0.23.1rc0, vLLM's /v1/audio/transcriptions endpoint limits comp= ressed upload size but not decoded PCM output. A 25MB OPUS file expands to = ~14.9GB of float32 PCM at decode time. This vulnerability is fixed in 0.23.= 1rc0.</td>
    <td>2026-06-22</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54233" target=3D= "_blank" rel=3D"noopener">CVE-2026-54233</a></td>
    </tr>

    <td class=3D"vendor-product">vllm-project--vllm</td>
    <td>vLLM is an inference and serving engine for large language models (LLMs=
    ). Prior to 0.23.1rc0, the fix for CVE-2026-22778, which introduced a sanit= ize_message helper that strips object-repr memory addresses from error mess= ages before they reach the client, is incomplete: several response paths ec=
    ho str(exc) directly to clients without calling sanitize_message. The unsan= itized sites include the Anthropic API router in vllm/entrypoints/anthropic= /api_router.py (the POST /v1/messages and POST /v1/messages/count_tokens ha= ndlers), the Server-Sent Events streaming converter in vllm/entrypoints/ant= hropic/serving.py, and the realtime speech-to-text WebSocket in vllm/entryp= oints/speech_to_text/realtime/connection.py. These paths catch the exceptio=
    n inside the route coroutine and construct the JSONResponse themselves, byp= assing the sanitizing global FastAPI exception handler, and WebSocket frame=
    s do not traverse that handler chain at all. Using the same primitive as th=
    e parent issue, an unauthenticated attacker can send malformed image bytes = through the Anthropic Messages API image content parts so that PIL.Image.op=
    en raises an UnidentifiedImageError whose message contains the BytesIO obje=
    ct repr, leaking the heap memory address verbatim in the error.message fiel=
    d of the response body. This vulnerability is fixed in 0.23.1rc0.</td> <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54236" target=3D= "_blank" rel=3D"noopener">CVE-2026-54236</a></td>
    </tr>

    <td class=3D"vendor-product">volcengine--OpenViking</td>
    <td>A vulnerability was detected in volcengine OpenViking up to 0.3.21. Thi=
    s affects the function str_to_uint64 of the file openviking/storage/vectord= b/utils/str_to_uint64.py of the component Local VectorDB Primary-key Label = Handler. The manipulation of the argument ID results in insufficient verifi= cation of data authenticity. The attack may be launched remotely. Attacks o=
    f this nature are highly complex. The exploitability is reported as difficu= lt. The pull request to fix this issue awaits acceptance.</td> <td>2026-06-28</td>
    <td>5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13507" target=3D= "_blank" rel=3D"noopener">CVE-2026-13507</a></td>
    </tr>

    <td class=3D"vendor-product">warpdotdev--warp</td>
    <td>Warp is an agentic development environment. From 0.2021.04.25.23.05.sta= ble_00 until 0.2026.05.06.15.42.stable_01, Warp accepted certain state-muta= ting terminal lifecycle hooks from the PTY stream without verifying that th=
    e hooks were emitted by Warp's shell integration for the active session. An=
    attacker who could cause a victim to view attacker-controlled terminal out= put in Warp could spoof selected lifecycle metadata, including the current = working directory reported for the active block or SSH session transport me= tadata. This vulnerability is fixed in 0.2026.05.06.15.42.stable_01.</td> <td>2026-06-24</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54686" target=3D= "_blank" rel=3D"noopener">CVE-2026-54686</a></td>
    </tr>

    <td class=3D"vendor-product">WCBoost--WCBoost Products Compare</td> <td>Unauthenticated Sensitive Data Exposure in WCBoost &amp;#8211; Products=
    Compare &lt;=3D 1.1.0 versions.</td>
    <td>2026-06-26</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57633" target=3D= "_blank" rel=3D"noopener">CVE-2026-57633</a></td>
    </tr>

    <td class=3D"vendor-product">webaways--NEX-Forms Ultimate Forms Plugin for = WordPress</td>
    <td>The NEX-Forms - Ultimate Forms Plugin for WordPress plugin for WordPres=
    s is vulnerable to authorization bypass in all versions up to, and includin=
    g, 9.2.2. This is due to the plugin not properly verifying that a user is a= uthorized to perform an action. This makes it possible for unauthenticated = attackers to enumerate sequential report IDs and download complete form sub= mission data - including names, email addresses, phone numbers, postal addr= esses, payment details, and uploaded file paths - for any saved report on t=
    he site.</td>
    <td>2026-06-27</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12404" target=3D= "_blank" rel=3D"noopener">CVE-2026-12404</a></td>
    </tr>

    <td class=3D"vendor-product">wedevs--Dokan Pro</td>
    <td>The Dokan Pro plugin for WordPress is vulnerable to time-based SQL Inje= ction via the 'orderby' parameter in all versions up to, and including, 5.0=
    .4 due to insufficient escaping on the user supplied parameter and lack of = sufficient preparation on the existing SQL query. This makes it possible fo=
    r authenticated attackers, with Subscriber-level access and above, to appen=
    d additional SQL queries into already existing queries that can be used to = extract sensitive information from the database.</td>
    <td>2026-06-25</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12079" target=3D= "_blank" rel=3D"noopener">CVE-2026-12079</a></td>
    </tr>

    <td class=3D"vendor-product">withastro--astro</td>
    <td>@astrojs/netlify is an adapter that allows Astro to deploy your hybrid =
    or server rendered site to Netlify. Prior to 7.0.13, @astrojs/netlify conve= rts Astro image.remotePatterns into Netlify Image CDN images.remote_images = regular expressions with broader semantics than Astro's canonical matcher. =
    A single wildcard hostname such as *.example.com is converted to an optiona=
    l subdomain regex, so the apex host matches. A single wildcard pathname suc=
    h as /ok/* is converted without end anchoring, so deeper paths match by pre= fix. This vulnerability is fixed in 7.0.13.</td>
    <td>2026-06-22</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54300" target=3D= "_blank" rel=3D"noopener">CVE-2026-54300</a></td>
    </tr>

    <td class=3D"vendor-product">withastro--astro</td>
    <td>Astro is a web framework. Prior to 6.4.6, the spreadAttributes function=
    in Astro's server-side rendering pipeline iterates over object keys and pa= sses them directly to addAttribute, which interpolates the key into the HTM=
    L output without escaping. When a developer uses the spread syntax {...prop=
    s} on an HTML element and the object keys come from an untrusted source (AP=
    I, CMS, URL parameters), an attacker can inject arbitrary HTML attributes i= ncluding event handlers like onmousemove, onclick, or break out of the attr= ibute context entirely to inject new elements. This vulnerability is fixed =
    in 6.4.6.</td>
    <td>2026-06-22</td>
    <td>4.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54298" target=3D= "_blank" rel=3D"noopener">CVE-2026-54298</a></td>
    </tr>

    <td class=3D"vendor-product">WP Folio Team--PPWP</td>
    <td>Contributor Insecure Direct Object References (IDOR) in PPWP &lt;=3D 1.= 9.19 versions.</td>
    <td>2026-06-26</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57634" target=3D= "_blank" rel=3D"noopener">CVE-2026-57634</a></td>
    </tr>

    <td class=3D"vendor-product">wp.insider--Affiliates Manager</td>
    <td>Affiliate Broken Access Control in Affiliates Manager &lt;=3D 2.9.49 ve= rsions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57654" target=3D= "_blank" rel=3D"noopener">CVE-2026-57654</a></td>
    </tr>

    <td class=3D"vendor-product">wpdevteam--Gutenberg Essential Blocks Page Bui= lder for Gutenberg Blocks &amp; Patterns</td>
    <td>The Gutenberg Essential Blocks - Page Builder for Gutenberg Blocks &amp=
    ; Patterns plugin for WordPress is vulnerable to Stored Cross-Site Scriptin=
    g via the 'configurablePrefix' Block Attribute in all versions up to, and i= ncluding, 6.1.4 due to insufficient input sanitization and output escaping.=
    This makes it possible for authenticated attackers, with Contributor-level=
    access and above, to inject arbitrary web scripts in pages that will execu=
    te whenever a user accesses an injected page.</td>
    <td>2026-06-25</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10833" target=3D= "_blank" rel=3D"noopener">CVE-2026-10833</a></td>
    </tr>

    <td class=3D"vendor-product">wpeverest--User Registration &amp; Membership = Free &amp; Paid Memberships, Subscriptions, Content Restriction, User Profi= le, Custom User Registration &amp; Login Builder</td>
    <td>The User Registration &amp; Membership - Free &amp; Paid Memberships, S= ubscriptions, Content Restriction, User Profile, Custom User Registration &= amp; Login Builder plugin for WordPress is vulnerable to unauthorized modif= ication of data due to missing validation checks in the confirm_payment() f= unction in all versions up to, and including, 5.2.0. This makes it possible=
    for unauthenticated attackers to bypass payment processing and activate pa=
    id memberships.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-1869" target=3D"= _blank" rel=3D"noopener">CVE-2026-1869</a></td>
    </tr>

    <td class=3D"vendor-product">WPManageNinja LLC--Fluent Booking</td> <td>Contributor Cross Site Scripting (XSS) in Fluent Booking &lt;=3D 2.1.0 = versions.</td>
    <td>2026-06-26</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57638" target=3D= "_blank" rel=3D"noopener">CVE-2026-57638</a></td>
    </tr>

    <td class=3D"vendor-product">wummel--patool</td>
    <td>Patool before 4.0.5 contains a path traversal vulnerability in the safe= _extract() function in patoolib/programs/py_tarfile.py when running on Pyth=
    on before 3.12, where the is_within_directory() helper uses os.path.commonp= refix() for character-level string comparison instead of path-level compari= son, allowing a crafted archive member path to bypass the containment check=
    . Attackers can supply a malicious archive with specially crafted member pa= ths to write arbitrary files.</td>
    <td>2026-06-26</td>
    <td>5.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-29509" target=3D= "_blank" rel=3D"noopener">CVE-2026-29509</a></td>
    </tr>

    <td class=3D"vendor-product">xpro--Xpro Addons 140+ Widgets for Elementor</=

    <td>The Xpro Addons - 140+ Widgets for Elementor plugin for WordPress is vu= lnerable to Stored Cross-Site Scripting via the 'custom_attributes' paramet=
    er in all versions up to, and including, 1.7.2 due to insufficient input sa= nitization and output escaping. This makes it possible for authenticated at= tackers, with author-level access and above, to inject arbitrary web script=
    s in pages that will execute whenever a user accesses an injected page.</td=

    <td>2026-06-24</td>
    <td>6.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11614" target=3D= "_blank" rel=3D"noopener">CVE-2026-11614</a></td>
    </tr>

    <td class=3D"vendor-product">yapacdev--WhatsOrder Instant Checkout for WooC= ommerce</td>
    <td>The WhatsOrder - Instant Checkout for WooCommerce plugin for WordPress =
    is vulnerable to Sensitive Information Exposure in all versions up to, and = including, 1.0.1 via the yapacdev_generate_order_pdf. This makes it possibl=
    e for unauthenticated attackers to extract sensitive customer PII and order=
    details - including full name, email address, phone number, billing addres=
    s, ordered items with quantities and prices, applied coupons, shipping meth= od, and order total - from any customer's invoice by enumerating sequential=
    order IDs. Invoice HTML files are written to the publicly accessible wp-co= ntent/uploads/whatsorder_invoices/ directory, which is created without an .= htaccess deny rule or index.php guard, making every invoice directly downlo= adable over HTTP with no authentication check.</td>
    <td>2026-06-24</td>
    <td>5.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9612" target=3D"= _blank" rel=3D"noopener">CVE-2026-9612</a></td>
    </tr>

    <td class=3D"vendor-product">yashpokharna2555--restaurent-management-system= </td>
    <td>A security flaw has been discovered in yashpokharna2555 restaurent-mana= gement-system. This impacts an unknown function of the file login_register.= php of the component Registration Handler. Performing a manipulation of the=
    argument Username results in cross site scripting. The attack may be initi= ated remotely. The exploit has been released to the public and may be used = for attacks. This product uses a rolling release model to deliver continuou=
    s updates. As a result, specific version information for affected or update=
    d releases is not available. The project was informed of the problem early = through an issue report but has not responded yet.</td>
    <td>2026-06-28</td>
    <td>4.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13499" target=3D= "_blank" rel=3D"noopener">CVE-2026-13499</a></td>
    </tr>

    <td class=3D"vendor-product">yt-dlp--yt-dlp</td>
    <td>yt-dlp is a command-line audio/video downloader. From 2023.09.24 until = 2026.06.09, if curl is used as an external downloader for yt-dlp, cookies m=
    ay be leaked to an unintended host upon HTTP redirect or when the host for = download fragments differs from their parent manifest's. At the file downlo=
    ad stage, the cookies are passed by yt-dlp to the file downloader via --coo= kie. However, unless these are loaded from a file, this operation does not = activate the cookie engine. As a result, curl will send cookies with reques=
    ts to domains or paths for which the cookies are not scoped. This vulnerabi= lity is fixed in 2026.06.09.</td>
    <td>2026-06-23</td>
    <td>6.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50019" target=3D= "_blank" rel=3D"noopener">CVE-2026-50019</a></td>
    </tr>

    <td class=3D"vendor-product">zephyrproject--zephyr</td>
    <td>The Zephyr Bluetooth LE Audio Basic Audio Profile (BAP) unicast client = mishandles peer-supplied ASE state notifications. In unicast_client_ep_qos_= state() (subsys/bluetooth/audio/bap_unicast_client.c), the handler writes a= ttacker-controlled QoS fields (interval, framing, phy, sdu, rtn, latency, p=
    d) through the stream-qos pointer with only a stream !=3D NULL guard. strea= m-qos is NULL for any stream that has been codec-configured via bt_bap_stre= am_config() but not yet added to a unicast group (it is set only by unicast= _group_add_stream()). A malicious or buggy remote ASCS server, to which the=
    local device is connected as a BAP unicast client, can send a GATT notific= ation announcing the ASE has entered the QoS Configured state while the loc=
    al endpoint is still in the Codec Configured state - a transition the dispa= tcher explicitly permits - during that window, causing a write through a NU=
    LL pointer and a crash (denial of service). The data written is itself remo= te-controlled. The defect shipped in v4.3.0 and v4.4.0 (and earlier). The f=
    ix re-points all BAP QoS storage to the always-valid embedded ep-qos struct=
    , eliminating the NULL dereference.</td>
    <td>2026-06-28</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10593" target=3D= "_blank" rel=3D"noopener">CVE-2026-10593</a></td>
    </tr>

    <td class=3D"vendor-product">zephyrproject--zephyr</td>
    <td>The Zephyr PL011 UART driver (drivers/serial/uart_pl011.c) contains an = unbounded software loop in pl011_irq_tx_enable() that repeatedly invokes th=
    e interrupt-driven application callback while the TX interrupt mask bit (PL= 011_IMSC_TXIM) is set, to work around the controller's level-transition TX-= interrupt behavior. When CTS hardware flow control is enabled (devicetree h= w-flow-control or runtime UART_CFG_FLOW_CTRL_RTS_CTS) and the wired serial = peer de-asserts CTS, the controller stops draining the TX FIFO; pl011_fifo_= fill() then returns 0 on every call while the application still has pending=
    data and therefore never disables the TX interrupt. The loop condition nev=
    er clears, so the thread that called uart_irq_tx_enable() (e.g. h4_send() i=
    n the Bluetooth HCI H4 driver) spins indefinitely, hanging the executing co= ntext and stalling the transport - a denial of service (CWE-835). An attack=
    er controlling the device attached to the UART's CTS line can trigger the h= ang by withholding CTS during transmission. Impact is availability only; th= ere is no memory-safety, confidentiality, or integrity consequence. The vul= nerable loop was introduced in commit b783bc8448ef (Feb 2025) and shipped i=
    n releases v4.1.0 through v4.4.0. The fix breaks out of the loop when CTS i=
    s blocking and arms the CTS modem-status interrupt to resume transmission w= hen CTS re-asserts.</td>
    <td>2026-06-24</td>
    <td>6.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10642" target=3D= "_blank" rel=3D"noopener">CVE-2026-10642</a></td>
    </tr>

    <td class=3D"vendor-product">zephyrproject--zephyr</td>
    <td>The Microchip SERCOM-G1 UART driver (drivers/serial/uart_mchp_sercom_g1= .c), used by the PIC32CM-JH SoC family, contains an out-of-bounds write in = its asynchronous (DMA) receive path. When uart_rx_enable() is invoked with =
    a one-byte receive buffer (len =3D=3D 1) and CONFIG_UART_MCHP_ASYNC is enab= led, the RX-complete ISR starts a single-beat DMA transfer while a received=
    byte is already pending in the SERCOM DATA register. On this SoC the perip= heral-triggered DMA start sequencing then writes one byte past the end of t=
    he caller-supplied buffer (CWE-787). The overflowed byte's value is the UAR=
    T RX data supplied by the connected serial peer (adjacent attacker), while = its size and location are fixed at one byte immediately after the buffer. E= xploitation requires the async UART config (not enabled by default on the i= n-tree PIC32CM-JH boards) and a consumer that enables RX with a one-byte bu= ffer; impact is limited single-byte memory corruption adjacent to the RX bu= ffer (possible crash / denial of service). The defect shipped in v4.4.0. Th=
    e fix reads the first byte with the CPU and, for one-byte buffers, performs=
    no DMA at all; for larger buffers it sizes the DMA for the remaining len-1=
    bytes.</td>
    <td>2026-06-28</td>
    <td>4.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10644" target=3D= "_blank" rel=3D"noopener">CVE-2026-10644</a></td>
    </tr>

    <td class=3D"vendor-product">zephyrproject-rtos--Zephyr</td>
    <td>Zephyr's ext2 directory-entry parser does not fully validate on-disk di= rectory entry structure before copying the entry name and advancing travers=
    al state. In ext2_fetch_direntry() (subsys/fs/ext2/ext2_diskops.c), the cod=
    e only checks de_name_len &lt;=3D EXT2_MAX_FILE_NAME and then copies the na=
    me with memcpy without validating the structural relationship between de_re= c_len, de_name_len, and the directory block boundary (for example that de_r= ec_len is non-zero, at least the size of the entry header, and that the rec= ord fits within the block). Callers such as find_dir_entry() and ext2_get_d= irentry() (subsys/fs/ext2/ext2_impl.c) then advance traversal using the unv= alidated de_rec_len. A crafted ext2 image can therefore cause an out-of-bou= nds read from the directory block buffer when a malformed entry near the en=
    d of a block triggers an oversized name copy, or a zero-progress infinite l= oop when de_rec_len =3D=3D 0. The issue is not reached at mount time but la= ter through directory traversal paths such as pathname lookup, stat/open/un= link/rename, and readdir. The primary impact is denial of service and out-o= f-bounds reads under attacker-controlled ext2 images mounted from untrusted=
    media.</td>
    <td>2026-06-22</td>
    <td>4.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10645" target=3D= "_blank" rel=3D"noopener">CVE-2026-10645</a></td>
    </tr>
    </tbody>
    </table>
    <p><a href=3D"#top">Back to top</a></p>
    </div>
    <div id=3D"low_v">
    <h2 id=3D"low_v_title">Low Vulnerabilities</h2>
    <table class=3D"table no-tablesaw" style=3D"table-layout: fixed; width: 100= %;" border=3D"1" summary=3D"Low Vulnerabilities">
    <thead>

    <th class=3D"vendor-product" style=3D"width: 24%;" scope=3D"col">
    <span class=3D"primary-vendor">Primary</span><br><span class=3D"primary-ven= dor">Vendor</span> -- Product</th>
    <th style=3D"width: 44%;" scope=3D"col">Description</th>
    <th style=3D"width: 10%;" scope=3D"col">Published</th>
    <th style=3D"width: 8%;" scope=3D"col">CVSS Score</th>
    <th style=3D"width: 7%;" scope=3D"col">Source Info</th>
    </tr>
    </thead>
    <tbody>

    <td class=3D"vendor-product">7-Zip--7-Zip</td>
    <td>7-Zip for Windows through 26.02 fails to preserve the Mark-of-the-Web w= hen extracting a crafted RAR5 archive, because its guard that suppresses an=
    archive-supplied Zone.Identifier stream matches the exact name 'Zone.Ident= ifier' while a RAR5 STM record named ':Zone.Identifier:$DATA' is not matche=
    d and NTFS canonicalizes it to the same stream, overwriting the propagated = Internet-zone marker with ZoneId=3D0. A second STM record named '::$DATA' o= verwrites the extracted file's default data stream, letting an attacker def= eat SmartScreen/MotW warnings and spoof file content.</td>
    <td>2026-06-28</td>
    <td>3.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-58052" target=3D= "_blank" rel=3D"noopener">CVE-2026-58052</a></td>
    </tr>

    <td class=3D"vendor-product">78--xiaozhi-esp32</td>
    <td>A weakness has been identified in 78 xiaozhi-esp32 up to 2.2.6. Affecte=
    d by this issue is the function ParseMessage of the file main/mcp_server.cc=
    of the component MCP Response Handler. This manipulation causes improper s= ynchronization. Remote exploitation of the attack is possible. The attack's=
    complexity is rated as high. The exploitation is known to be difficult. Th=
    e exploit has been made available to the public and could be used for attac= ks. The pull request to fix this issue awaits acceptance.</td> <td>2026-06-28</td>
    <td>3.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13489" target=3D= "_blank" rel=3D"noopener">CVE-2026-13489</a></td>
    </tr>

    <td class=3D"vendor-product">78--xiaozhi-esp32</td>
    <td>A vulnerability was detected in 78 xiaozhi-esp32 up to 2.2.6. This vuln= erability affects the function Application::GetInstance of the file main/pr= otocols/mqtt_protocol.cc of the component MQTT Goodbye Handler. Performing =
    a manipulation of the argument session_id results in denial of service. The=
    attack is possible to be carried out remotely. The complexity of an attack=
    is rather high. It is stated that the exploitability is difficult. The exp= loit is now public and may be used. The patch is named e182471f8c5a22434346= bd98da34d3b66c8c8b3e. It is recommended to apply a patch to fix this issue.= </td>
    <td>2026-06-28</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13491" target=3D= "_blank" rel=3D"noopener">CVE-2026-13491</a></td>
    </tr>

    <td class=3D"vendor-product">AIDC-AI--ComfyUI-Copilot</td>
    <td>A flaw has been found in AIDC-AI ComfyUI-Copilot up to 2.0.28. This iss=
    ue affects some unknown processing of the file backend/controller/conversat= ion_api.py of the component Workflow Checkpoint Restore Handler. Executing =
    a manipulation can lead to improper control of resource identifiers. The at= tack may be performed from remote. A high complexity level is associated wi=
    th this attack. The exploitability is assessed as difficult. The exploit ha=
    s been published and may be used. The pull request to fix this issue awaits=
    acceptance.</td>
    <td>2026-06-28</td>
    <td>3.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13493" target=3D= "_blank" rel=3D"noopener">CVE-2026-13493</a></td>
    </tr>

    <td class=3D"vendor-product">arc53--DocsGPT</td>
    <td>A flaw has been found in arc53 DocsGPT up to 0.18.0. The affected eleme=
    nt is the function encrypt_credentials of the file application/security/enc= ryption.py of the component Credential Storage. This manipulation causes in= sufficient verification of data authenticity. It is possible to initiate th=
    e attack remotely. The complexity of an attack is rather high. The exploita= bility is described as difficult. The exploit has been published and may be=
    used. The pull request to fix this issue awaits acceptance.</td> <td>2026-06-28</td>
    <td>3.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13483" target=3D= "_blank" rel=3D"noopener">CVE-2026-13483</a></td>
    </tr>

    <td class=3D"vendor-product">babel--babel</td>
    <td>Babel is a compiler for writing next generation JavaScript. Prior to 8.= 0.0-rc.6 and 7.29.6, @babel/core affected by an arbitrary file read via a s= ourceMappingURL comment. Using @babel/core to compile maliciously crafted c= ode can allow an attacker to read any source map from the system that is ru= nning Babel, if the attacker controls the input source code, can read the o= utput source code, and knows the path of the source map file that they want=
    to read. This vulnerability is fixed in 8.0.0-rc.6 and 7.29.6.</td> <td>2026-06-22</td>
    <td>3.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49356" target=3D= "_blank" rel=3D"noopener">CVE-2026-49356</a></td>
    </tr>

    <td class=3D"vendor-product">bitwarden--server</td>
    <td>Bitwarden Server before 2026.5.0 contains a JSON injection vulnerabilit=
    y in IntegrationTemplateProcessor.ReplaceTokens(), which substitutes user-c= ontrolled values into event-integration templates without JSON encoding. Wh=
    en an organization has configured an event integration whose template refer= ences a user-controlled token (such as #ActingUserName# or #UserName#, popu= lated from a member's display name), an authenticated member can set their = display name to JSON metacharacters and inject arbitrary key-value pairs in=
    to the rendered payloads delivered to webhook, SIEM, Slack, Teams, or Datad=
    og endpoints, making injected fields indistinguishable from legitimate temp= late output.</td>
    <td>2026-06-25</td>
    <td>3.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57522" target=3D= "_blank" rel=3D"noopener">CVE-2026-57522</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. In = versions 1.2.30 and below, the locale-dependent decimal formatting in rrdto= ol_function_update() can corrupt RRDtool metric values. The rrdtool_functio= n_update() function checks metric values with is_numeric() and concatenates=
    them into the RRDtool update command via PHP string interpolation. PHP's s= tring cast of floats is locale-sensitive: if LC_NUMERIC uses comma as decim=
    al separator (e.g., de_DE), a value of 1.5 becomes "1,5". RRDtool expects .=
    as decimal separator, causing metric data to shift into wrong columns or b=
    e silently dropped. No setlocale() reset is present in the update path. Thi=
    s causes a data integrity issue, but is not remotely exploitable; it requir=
    es server locale misconfiguration. The issue has been fixed in version 1.2.= 31.</td>
    <td>2026-06-24</td>
    <td>2.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39894" target=3D= "_blank" rel=3D"noopener">CVE-2026-39894</a></td>
    </tr>

    <td class=3D"vendor-product">Chess--Play and Learn App</td>
    <td>A weakness has been identified in Chess Play and Learn App up to 4.9.42=
    on Android. This issue affects some unknown processing of the file Android= Manifest.xml of the component com.chess. This manipulation causes exposure =
    of backup file to an unauthorized control sphere. It is feasible to perform=
    the attack on the physical device. The exploit has been made available to = the public and could be used for attacks. Upgrading the affected component =
    is advised. The vendor was informed early about this issue. They confirmed = the existence and that they will address it. Furthermore, they explain that=
    their bug bounty "explicitly excludes physical-access attacks". However, t= hey appreciate the quality of the report and aim at making a goodwill payme=
    nt to the researcher.</td>
    <td>2026-06-28</td>
    <td>2.4</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13514" target=3D= "_blank" rel=3D"noopener">CVE-2026-13514</a></td>
    </tr>

    <td class=3D"vendor-product">code-projects--Project Management System</td> <td>A vulnerability has been found in code-projects Project Management Syst=
    em 1.0. This vulnerability affects unknown code of the file /mail.php of th=
    e component Mail Compose Page. Such manipulation leads to cross site script= ing. The attack may be performed from remote. The exploit has been disclose=
    d to the public and may be used.</td>
    <td>2026-06-28</td>
    <td>3.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13504" target=3D= "_blank" rel=3D"noopener">CVE-2026-13504</a></td>
    </tr>

    <td class=3D"vendor-product">earendil-works--pi</td>
    <td>Pi is a minimal terminal coding harness. From 0.74.0 until 0.78.1, Pi H= TML exports render session Markdown into a static HTML file. It did not con= sistently reject unsafe Markdown link and image URL schemes. In versions wi=
    th scheme filtering, C0 control characters in the URL scheme could bypass t=
    he check because browsers normalize those characters before navigation. Thi=
    s vulnerability is fixed in 0.78.1.</td>
    <td>2026-06-23</td>
    <td>2.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54326" target=3D= "_blank" rel=3D"noopener">CVE-2026-54326</a></td>
    </tr>

    <td class=3D"vendor-product">earendil-works--pi</td>
    <td>Pi is a minimal terminal coding harness. From 0.74.0 until 0.78.1, Pi s= tored API keys and OAuth credentials in auth.json. A race condition in the = file write path could briefly create or rewrite this file with permissions = derived from the process umask before tightening the file to owner-only per= missions. This vulnerability is fixed in 0.78.1.</td>
    <td>2026-06-23</td>
    <td>2.2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54327" target=3D= "_blank" rel=3D"noopener">CVE-2026-54327</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab EE affecting all versions from=
    17.9 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under=
    certain conditions could have allowed an authenticated user with custom ro=
    le permissions to view, create, or delete protected environment configurati= ons despite CI/CD visibility being disabled for the project.</td> <td>2026-06-25</td>
    <td>3.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-0934" target=3D"= _blank" rel=3D"noopener">CVE-2026-0934</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab EE affecting all versions from=
    18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under=
    certain conditions could have allowed an authenticated user with limited p= ermissions to access project information due to insufficient authorization = checks.</td>
    <td>2026-06-25</td>
    <td>3.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-3176" target=3D"= _blank" rel=3D"noopener">CVE-2026-3176</a></td>
    </tr>

    <td class=3D"vendor-product">glpi-project--glpi</td>
    <td>A security vulnerability has been detected in glpi-project glpi 11.0.5/= 11.0.6/11.0.7. This affects the function Document::canViewFile of the file = front/document.send.php of the component Document Handler. Such manipulatio=
    n of the argument docid leads to authorization bypass. The attack can be ex= ecuted remotely. This attack is characterized by high complexity. It is ind= icated that the exploitability is difficult. The vendor was contacted early=
    about this disclosure.</td>
    <td>2026-06-28</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13490" target=3D= "_blank" rel=3D"noopener">CVE-2026-13490</a></td>
    </tr>

    <td class=3D"vendor-product">GNU--GNU SASL</td>
    <td>GNU SASL before 2.2.4 lacks sanitization of a short challenge in _gsasl= _ntlm_client_step in the NTLM client, which could result in memory disclosu=
    re via a crafted server.</td>
    <td>2026-06-23</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56968" target=3D= "_blank" rel=3D"noopener">CVE-2026-56968</a></td>
    </tr>

    <td class=3D"vendor-product">GnuPG--GnuPG</td>
    <td>CMS (Cryptographic Message Syntax) parsing in gpgsm in GnuPG through 2.= 5.20 mishandles the CMS format for AES-GCM because aes-ICVlen is supposed t=
    o be 12 bytes but 4 bytes is accepted. NOTE: this is related to CVE-2026-34= 182.</td>
    <td>2026-06-23</td>
    <td>2.9</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57062" target=3D= "_blank" rel=3D"noopener">CVE-2026-57062</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, specia= lly crafted issue index pattern can cause a panic when rendering, resulting=
    in denial of service. In internal/markup/markup.go, RenderIssueIndexPatter=
    n renders the issue index pattern to a link using com.Expand, which is not = safe: when the configured pattern contains an opening brace { but no closin=
    g brace }, strings.Index(template, "}") returns -1 and the subsequent slice=
    template[:-1] triggers a panic. Once such a pattern is set, any page in th=
    e affected repository that contains an issue index reference such as #1 bec= omes unavailable. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>3.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52796" target=3D= "_blank" rel=3D"noopener">CVE-2026-52796</a></td>
    </tr>

    <td class=3D"vendor-product">HCLSoftware--Connections</td>
    <td>HCL Connections contains a broken access control vulnerability that may=
    allow an unauthorized user to view data in a single specific scenario.</td=

    <td>2026-06-23</td>
    <td>3.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-15619" target=3D= "_blank" rel=3D"noopener">CVE-2025-15619</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--Datacap</td>
    <td>IBM Datacap 9.1.7, 9.1.8, and 9.1.9 and IBM Datacap Navigator 9.1.7, 9.= 1.8, and 9.1.9 exposes resources or functionality that isn't linked in the =
    UI but is accessible by directly requesting the URL, bypassing intended acc= ess controls.</td>
    <td>2026-06-22</td>
    <td>2.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9610" target=3D"= _blank" rel=3D"noopener">CVE-2026-9610</a></td>
    </tr>

    <td class=3D"vendor-product">ImageMagick--ImageMagick</td>
    <td>ImageMagick before 7.1.2-15 contains a memory leak vulnerability in mul= tiple coders that write raw pixel data where allocated objects are not prop= erly freed. Attackers can trigger this leak by processing specially crafted=
    images, causing memory exhaustion and denial of service.</td> <td>2026-06-24</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56368" target=3D= "_blank" rel=3D"noopener">CVE-2026-56368</a></td>
    </tr>

    <td class=3D"vendor-product">ImageMagick--ImageMagick</td>
    <td>ImageMagick before 7.1.2-19 contains an out-of-bounds access vulnerabil= ity in ConnectedComponentsImage() when processing connected-components arti= facts with invalid indices. Attackers can trigger access violations by spec= ifying malformed connected-components definitions via CLI, causing denial o=
    f service or potential code execution.</td>
    <td>2026-06-24</td>
    <td>3.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56370" target=3D= "_blank" rel=3D"noopener">CVE-2026-56370</a></td>
    </tr>

    <td class=3D"vendor-product">ImageMagick--ImageMagick</td>
    <td>ImageMagick before 7.1.2-15 and 6.9.13-40 contains a heap use-after-fre=
    e in the meta coder: when memory allocation fails, a single byte is written=
    to a stale pointer. Remote attackers can trigger it by processing speciall=
    y crafted image files, causing a denial of service.</td>
    <td>2026-06-23</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56376" target=3D= "_blank" rel=3D"noopener">CVE-2026-56376</a></td>
    </tr>

    <td class=3D"vendor-product">JetBrains--YouTrack</td>
    <td>In JetBrains YouTrack before 2026.2.16593 project settings disclosure v=
    ia the MCP was possible</td>
    <td>2026-06-26</td>
    <td>3.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57922" target=3D= "_blank" rel=3D"noopener">CVE-2026-57922</a></td>
    </tr>

    <td class=3D"vendor-product">JetBrains--YouTrack</td>
    <td>In JetBrains YouTrack before 2026.2.16593 the websandbox bridge was vul= nerable to a prototype pollution attack</td>
    <td>2026-06-26</td>
    <td>2.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57926" target=3D= "_blank" rel=3D"noopener">CVE-2026-57926</a></td>
    </tr>

    <td class=3D"vendor-product">Kludex--python-multipart</td>
    <td>Python-Multipart is a streaming multipart parser for Python. Prior to 0= .0.30, parse_options_header parsed Content-Disposition (and Content-Type) h= eaders with email.message.Message, which transparently applies RFC 2231/598=
    7 decoding. The extended parameter syntax (filename*=3Dcharset'lang'value, = name*=3D..., and the filename*0/filename*1 continuation form) is decoded an=
    d surfaced under the bare filename/name key, and overrides the plain parame= ter when both are present. RFC 7578 =C3=82=C2=A74.2 explicitly forbids the = filename* form in multipart/form-data. Components that follow RFC 7578, or = that do not implement RFC 2231/5987 decoding for multipart/form-data (WAFs,=
    proxies, gateways), may interpret such a header differently. An attacker c=
    an exploit that difference to smuggle a different field name or filename pa=
    st an upstream inspector to the backend. This vulnerability is fixed in 0.0= .30.</td>
    <td>2026-06-22</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53537" target=3D= "_blank" rel=3D"noopener">CVE-2026-53537</a></td>
    </tr>

    <td class=3D"vendor-product">Kludex--python-multipart</td>
    <td>Python-Multipart is a streaming multipart parser for Python. Prior to 0= .0.30, QuerystringParser treated ; as a field separator in application/x-ww= w-form-urlencoded bodies, in addition to &amp;. The WHATWG URL standard, mo= dern browsers, and Python's urllib.parse (since the CVE-2021-23336 fix) tre=
    at only &amp; as a separator. This creates a parser differential: the same = bytes are tokenized into different fields than a WHATWG compliant intermedi= ary would produce, allowing an attacker to smuggle extra form fields past a=
    n upstream body inspecting component. This vulnerability is fixed in 0.0.30= .</td>
    <td>2026-06-22</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53538" target=3D= "_blank" rel=3D"noopener">CVE-2026-53538</a></td>
    </tr>

    <td class=3D"vendor-product">Kludex--python-multipart</td>
    <td>Python-Multipart is a streaming multipart parser for Python. Prior to 0= .0.31, parse_form() did not validate the Content-Length header before using=
    it to bound its chunked read of the request body. A negative Content-Lengt=
    h turned the bounded read into a read-until-EOF, so the entire body was loa= ded into memory in a single read instead of in fixed-size chunks. This vuln= erability is fixed in 0.0.31.</td>
    <td>2026-06-22</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53540" target=3D= "_blank" rel=3D"noopener">CVE-2026-53540</a></td>
    </tr>

    <td class=3D"vendor-product">Kludex--starlette</td>
    <td>Starlette is a lightweight ASGI framework/toolkit. Prior to 1.3.0, the = HTTP request path is not validated before being used to reconstruct request= .url. Because request.url is rebuilt by concatenating {scheme}://{host}{pat=
    h} and re-parsing the result, a path that does not begin with / (for exampl=
    e @google.com) moves the authority boundary during re-parsing, so request.u= rl.hostname and request.url.netloc become attacker-controlled. Code that re= ads request.url.hostname (rather than the Host header or scope) can therefo=
    re be misled into trusting an attacker-supplied host. This vulnerability is=
    fixed in 1.3.0.</td>
    <td>2026-06-22</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54282" target=3D= "_blank" rel=3D"noopener">CVE-2026-54282</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost</td>
    <td>Mattermost versions 10.11.x &lt;=3D 10.11.18, 11.6.x &lt;=3D 11.6.3, 11= .5.x &lt;=3D 11.5.6 fail to properly apply markdown image rendering restric= tions to AI bot tool result posts, which allows an authenticated attacker t=
    o exfiltrate data to an attacker-controlled server via injecting markdown i= mage syntax into tool result content rendered by a victim's client.. Matter= most Advisory ID: MMSA-2026-00619</td>
    <td>2026-06-26</td>
    <td>3.5</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-3472" target=3D"= _blank" rel=3D"noopener">CVE-2026-3472</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost</td>
    <td>Mattermost versions 11.7.x &lt;=3D 11.7.0, 10.11.x &lt;=3D 10.11.17 fai=
    l to enforce bot-specific permission checks on the user active status endpo= int, which allows a User Manager with user management write access but no I= ntegrations access to deactivate bot accounts via the PUT /api/v4/users/{id= }/active API endpoint.. Mattermost Advisory ID: MMSA-2026-00667</td> <td>2026-06-22</td>
    <td>3.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8074" target=3D"= _blank" rel=3D"noopener">CVE-2026-8074</a></td>
    </tr>

    <td class=3D"vendor-product">Mattermost--Mattermost</td>
    <td>Mattermost versions 11.7.x &lt;=3D 11.7.0, 10.11.x &lt;=3D 10.11.17 fai=
    l to validate bot targets when demoting users to guests which allows a lowe= r-privileged administrator to degrade arbitrary bot accounts via the standa=
    rd demote-user API.. Mattermost Advisory ID: MMSA-2026-00669</td> <td>2026-06-22</td>
    <td>3.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8823" target=3D"= _blank" rel=3D"noopener">CVE-2026-8823</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, the OAuth token strategy attached oauth_scope and oauth_granted_res= ources to the request user, but the ACL middleware never consulted either. =
    An OAuth token issued with a restricted scope (e.g. MCP-only) therefore inh= erited the full permissions of the underlying user across all routes; the g= ranted_resources.base_id restriction was bypassed on org-level endpoints th=
    at don't populate req.context.base_id. This vulnerability is fixed in 2026.= 04.1.</td>
    <td>2026-06-23</td>
    <td>2</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46549" target=3D= "_blank" rel=3D"noopener">CVE-2026-46549</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--DNSdist</td>
    <td>An attacker sending a large number of crafted DNS queries might be able=
    to trigger a dynamic block being inserted with a value causing invalid out= put to be produced in the prometheus endpoint. The prometheus endpoint will=
    then be rejected by the scraper until the dynamic block expires.</td> <td>2026-06-25</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40011" target=3D= "_blank" rel=3D"noopener">CVE-2026-40011</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--DNSdist</td>
    <td>An attacker might be able to delay the processing of DoH3 queries by se= nding DoH3 GET queries with an invalid DATA frame.</td>
    <td>2026-06-25</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40208" target=3D= "_blank" rel=3D"noopener">CVE-2026-40208</a></td>
    </tr>

    <td class=3D"vendor-product">PowerDNS--DNSdist</td>
    <td>An attacker can send a crafted EDNS OPT record that will be ignored by = DNSdist's filtering rules, but will be rewritten as a valid OPT record when=
    EDNS Client Subnet is inserted, causing the backend to see the EDNS option= (s) that DNSdist did not filter.</td>
    <td>2026-06-25</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42004" target=3D= "_blank" rel=3D"noopener">CVE-2026-42004</a></td>
    </tr>

    <td class=3D"vendor-product">Rapid7--InsightConnect Compression Plugin</td> <td>Path Traversal vulnerability in the create_archive function of Rapid7 I= nsightConnect Compression Plugin on Linux allows authenticated attackers to=
    write to unintended file paths via crafted filename input. The impact is l= imited to file corruption as content cannot be controlled by the attacker.<=

    <td>2026-06-25</td>
    <td>3.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8662" target=3D"= _blank" rel=3D"noopener">CVE-2026-8662</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat Enterprise Linux 10</td>
    <td>A flaw was found in OpenSSH. This vulnerability, a heap out-of-bounds r= ead, occurs during the cleanup of GSSAPI (Generic Security Service Applicat= ion Programming Interface) indicators when a trailing NULL termination is m= issing in the auth-indicators array. A remote attacker, under specific conf= igurations involving GSSAPI authentication and a Kerberos environment, coul=
    d exploit this to cause the SSH authentication path to crash or abort. This=
    leads to a denial of service (DoS), impacting the availability of the SSH = service.</td>
    <td>2026-06-23</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55654" target=3D= "_blank" rel=3D"noopener">CVE-2026-55654</a></td>
    </tr>

    <td class=3D"vendor-product">Red Hat--Red Hat OpenShift Virtualization 4</t=

    <td>A flaw was found in KubeVirt's downward metrics virtio-serial server. T=
    he server reads guest requests using textproto.Reader.ReadLine(), which buf= fers input indefinitely until a newline character is received, with no leng=
    th limit or read deadline. A user with access to a VM guest that has the do= wnward metrics virtio-serial device configured can write a continuous byte = stream to the device, causing unbounded memory allocation in the virt-handl=
    er process until it is OOM-killed.</td>
    <td>2026-06-26</td>
    <td>3.8</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13322" target=3D= "_blank" rel=3D"noopener">CVE-2026-13322</a></td>
    </tr>

    <td class=3D"vendor-product">remix-run--react-router</td>
    <td>React Router is a router for React. From 7.12.0 until 7.15.1, certain C= SRF checks in React Router v7 Framework Mode were insufficient and run on P= OST requests, but were bypassed on PUT/PATCH/DELETE requests. This is a low=
    severity vulnerability because modern browser protections (CORS preflight,=
    SameSite cookies) already block the cross-origin attack vectors that this = missing CSRF check would otherwise gate. This vulnerability is fixed in 7.1= 5.1.</td>
    <td>2026-06-22</td>
    <td>3.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53663" target=3D= "_blank" rel=3D"noopener">CVE-2026-53663</a></td>
    </tr>

    <td class=3D"vendor-product">SimStudioAI--sim</td>
    <td>A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by = this vulnerability is an unknown functionality in the library apps/sim/lib/= core/security/deployment.ts of the component Password Protection Handler. P= erforming a manipulation results in use of weak hash. The attack is possibl=
    e to be carried out remotely. The attack's complexity is rated as high. The=
    exploitation appears to be difficult. The exploit has been made public and=
    could be used. The pull request to fix this issue awaits acceptance.</td> <td>2026-06-28</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13510" target=3D= "_blank" rel=3D"noopener">CVE-2026-13510</a></td>
    </tr>

    <td class=3D"vendor-product">skypilot-org--skypilot</td>
    <td>A vulnerability was detected in skypilot-org skypilot up to 0.12.0. Imp= acted is the function username.encode of the file sky/users/server.py of th=
    e component User ID Handler. The manipulation results in use of weak hash. = The attack may be performed from remote. This attack is characterized by hi=
    gh complexity. The exploitability is considered difficult. The exploit is n=
    ow public and may be used. The vendor was contacted early about this disclo= sure.</td>
    <td>2026-06-28</td>
    <td>3.7</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13482" target=3D= "_blank" rel=3D"noopener">CVE-2026-13482</a></td>
    </tr>

    <td class=3D"vendor-product">sparklemotion--nokogiri</td>
    <td>Nokogiri is an open source XML and HTML library for the Ruby programmin=
    g language. Prior to 1.19.4, the NONET parse option, which Nokogiri turns o=
    n by default for Nokogiri::XML::Schema (see CVE-2020-26247), was not correc= tly enforced on the JRuby implementation. As a result, a schema parsed with=
    default options could still cause external resources to be fetched over th=
    e network, potentially enabling SSRF or XXE attacks. This vulnerability is = fixed in 1.19.4.</td>
    <td>2026-06-25</td>
    <td>2.6</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57234" target=3D= "_blank" rel=3D"noopener">CVE-2026-57234</a></td>
    </tr>

    <td class=3D"vendor-product">tenable--Nessus</td>
    <td>A SQL injection vulnerability in Nessus allows an attacker to craft a m= alicious scan result file that, when imported by a privileged user, injects=
    malicious SQL into the scan results database, potentially enabling exfiltr= ation of scan-result data.</td>
    <td>2026-06-25</td>
    <td>3.3</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57588" target=3D= "_blank" rel=3D"noopener">CVE-2026-57588</a></td>
    </tr>

    <td class=3D"vendor-product">VoltAgent--VoltAgent</td>
    <td>A vulnerability was determined in VoltAgent up to 2.1.17. Affected by t= his issue is the function handleGetMemoryConversation of the file packages/= server-core/src/handlers/memory.handlers.ts of the component Memory REST AP=
    I. Executing a manipulation of the argument conversationId can lead to impr= oper authorization. The attack may be performed from remote. This attack is=
    characterized by high complexity. The exploitation is known to be difficul=
    t. The exploit has been publicly disclosed and may be utilized. The pull re= quest to fix this issue awaits acceptance.</td>
    <td>2026-06-28</td>
    <td>3.1</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13511" target=3D= "_blank" rel=3D"noopener">CVE-2026-13511</a></td>
    </tr>
    </tbody>
    </table>
    <p><a href=3D"#top">Back to top</a></p>
    </div>
    <div id=3D"snya_v">
    <h2 id=3D"snya_v_title">Severity Not Yet Assigned</h2>
    <table id=3D"table_severity_not_yet_assigned" class=3D"table no-tablesaw" s= tyle=3D"table-layout: fixed; width: 100%;" border=3D"1" summary=3D"Severity=
    Not Yet Assigned">
    <thead>

    <th class=3D"vendor-product" style=3D"width: 24%;" scope=3D"col">
    <span class=3D"primary-vendor">Primary</span><br><span class=3D"primary-ven= dor">Vendor</span> -- Product</th>
    <th style=3D"width: 44%;" scope=3D"col">Description</th>
    <th style=3D"width: 10%;" scope=3D"col">Published</th>
    <th style=3D"width: 8%;" scope=3D"col">CVSS Score</th>
    <th style=3D"width: 7%;" scope=3D"col">Source Info</th>
    </tr>
    </thead>
    <tbody>

    <td class=3D"vendor-product">AcademySoftwareFoundation--OpenColorIO</td> <td>OpenColorIO is a color management framework for visual effects and anim= ation. Prior to version 2.5.2, `FileFormatSpi3D.cpp:163` uses `sscanf` with=
    `%s` into 64-byte stack buffers when parsing LUT data lines. Input comes f= rom `lineBuffer[4096]`, so a crafted .spi3d file can overflow by ~4000 byte=
    s on non-Windows. Version 2.5.2 fixes the issue.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-42450" target=3D= "_blank" rel=3D"noopener">CVE-2026-42450</a></td>
    </tr>

    <td class=3D"vendor-product">ail project--ail framework</td>
    <td>A path traversal vulnerability exists in AIL Framework before the relea=
    se containing commit 0041456af25da0cdea1c1c4624e46baff2731d8f. An authentic= ated AIL user can supply crafted object identifiers through the investigati=
    on workflow to cause file paths to resolve outside the intended image, favi= con, or screenshot storage directories. This may allow the attacker to down= load and read arbitrary files that are accessible to the AIL process. The i= ssue occurs because user-controlled path components were joined with applic= ation storage paths without verifying that the resolved path remained withi=
    n the expected directory. The affected download functionality could then in= clude the contents of such files in a generated archive.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56448" target=3D= "_blank" rel=3D"noopener">CVE-2026-56448</a></td>
    </tr>

    <td class=3D"vendor-product">ail project--ail framework</td>
    <td>AIL did not restrict repeated failed attempts to verify a two-factor au= thentication (OTP) code. An attacker who had reached the 2FA verification s= tep, such as after successfully completing the password-authentication stag=
    e, could submit an unlimited number of OTP guesses. This could enable brute= -force guessing of a valid code and bypass the intended second authenticati=
    on factor, resulting in unauthorized account access. The patch introduces p= er-user failed-OTP tracking, blocks verification after 30 failed attempts f=
    or one hour, clears the counter after a successful OTP verification, and pr= ovides administrator recovery actions to purge affected lockouts.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56450" target=3D= "_blank" rel=3D"noopener">CVE-2026-56450</a></td>
    </tr>

    <td class=3D"vendor-product">aio-libs--aiohttp</td>
    <td>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.0, attacker-controlled input included into multipart= /payload headers can be used to modify a request to inject additional heade=
    rs or similar. In the unlikely situation that an application is passing use= r-controlled strings into MultipartWriter.append(headers=3D...) or Payload.= headers, then an attacker may be able to modify the request to inject heade=
    rs or change the contents of the request. This vulnerability is fixed in 3.= 14.0.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50269" target=3D= "_blank" rel=3D"noopener">CVE-2026-50269</a></td>
    </tr>

    <td class=3D"vendor-product">aio-libs--aiohttp</td>
    <td>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.1, no limit was present on the number of pipelined r= equests that could be queued. An attacker may be able to use pipelined requ= ests to use excessive amounts of memory, potentially leading to DoS. This v= ulnerability is fixed in 3.14.1.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54273" target=3D= "_blank" rel=3D"noopener">CVE-2026-54273</a></td>
    </tr>

    <td class=3D"vendor-product">aio-libs--aiohttp</td>
    <td>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.1, if an attacker sends large incomplete websocket f= rame payloads, it may be possible to bypass the usual size limits on memory=
    use. This vulnerability is fixed in 3.14.1.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54274" target=3D= "_blank" rel=3D"noopener">CVE-2026-54274</a></td>
    </tr>

    <td class=3D"vendor-product">aio-libs--aiohttp</td>
    <td>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed=
    when an existing connection is reused. If an application makes multiple re= quests to the same domain, but with different per-request server_hostname p= arameters, then the later calls may succeed by reusing the existing connect= ion when they should have been rejected due to the TLS SNI check. This vuln= erability is fixed in 3.14.1.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54275" target=3D= "_blank" rel=3D"noopener">CVE-2026-54275</a></td>
    </tr>

    <td class=3D"vendor-product">aio-libs--aiohttp</td>
    <td>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.1, DigestAuthMiddleware can send an authentication r= esponse after following a cross-origin redirect. This likely requires an op=
    en redirect vulnerability or similar on the target domain for an attacker t=
    o be able to execute. Further, the attacker is only receiving the digest, s=
    o should only be able to extract the user's credentials if the cryptography=
    is weak or there is some kind of password reuse. This vulnerability is fix=
    ed in 3.14.1.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54276" target=3D= "_blank" rel=3D"noopener">CVE-2026-54276</a></td>
    </tr>

    <td class=3D"vendor-product">aio-libs--aiohttp</td>
    <td>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.1, it is possible to bypass the max_line_size check =
    in parts of an HTTP request in the C parser. If using the optimised C parse=
    r (the default in pre-built wheels), then an attacker may be able to send o= versized lines through the HTTP parser and use an excessive amount of memor=
    y, potentially leading to DoS. This vulnerability is fixed in 3.14.1.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54277" target=3D= "_blank" rel=3D"noopener">CVE-2026-54277</a></td>
    </tr>

    <td class=3D"vendor-product">aio-libs--aiohttp</td>
    <td>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.1, during cleanup it is possible for a compressed re= quest body to be decompressed into memory in one chunk. An attacker may be = able to send a compressed payload in specific situations that could be deco= mpressed into memory, potentially leading to DoS (a zip bomb edge case). Th=
    is vulnerability is fixed in 3.14.1.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54278" target=3D= "_blank" rel=3D"noopener">CVE-2026-54278</a></td>
    </tr>

    <td class=3D"vendor-product">aio-libs--aiohttp</td>
    <td>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.1, host-only cookies that are saved with CookieJar.s= ave() and then restored later with CookieJar.load() lose their host-only st= atus. This vulnerability is fixed in 3.14.1.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54279" target=3D= "_blank" rel=3D"noopener">CVE-2026-54279</a></td>
    </tr>

    <td class=3D"vendor-product">aio-libs--aiohttp</td>
    <td>AIOHTTP is an asynchronous HTTP client/server framework for asyncio and=
    Python. Prior to 3.14.1, payload resources are not closed correctly when a=
    client disconnects in the middle of a write. If a payload is using an open=
    file or similar limited resource, then an attacker may be able to cause re= source starvation temporarily until garbage collection or similar closes th=
    e file. This vulnerability is fixed in 3.14.1.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54280" target=3D= "_blank" rel=3D"noopener">CVE-2026-54280</a></td>
    </tr>

    <td class=3D"vendor-product">Akaunting--Akaunting</td>
    <td>Akaunting 3.1.21 contains an authenticated stored cross-site scripting = vulnerability in the reusable delete confirmation flow. A user with permiss= ion to create or modify records, such as Items, can store HTML/JavaScript i=
    n the record name.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11942" target=3D= "_blank" rel=3D"noopener">CVE-2026-11942</a></td>
    </tr>

    <td class=3D"vendor-product">Akaunting--Akaunting</td>
    <td>Akaunting 3.1.21 contains an authenticated stored cross-site scripting = vulnerability in the document timeline shown on invoice and bill detail pag= es. An authenticated user can store HTML/JavaScript in their own profile na= me.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11943" target=3D= "_blank" rel=3D"noopener">CVE-2026-11943</a></td>
    </tr>

    <td class=3D"vendor-product">Akaunting--Akaunting</td>
    <td>Akaunting 3.1.21 contains an authenticated stored Cross-Site Scripting = vulnerability in the report management workflow. A user with permission to = create or update reports can store arbitrary HTML/JavaScript in the descrip= tion field of a report.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11994" target=3D= "_blank" rel=3D"noopener">CVE-2026-11994</a></td>
    </tr>

    <td class=3D"vendor-product">AMD--AMD Athlon 3000 Series Mobile Processors = with Radeon Graphics</td>
    <td>An observable timing discrepancy in the ASP could allow a privileged at= tacker to perform a brute-force attack against the hash message authenticat= ion code, allowing the input of an arbitrary message, potentially leading t=
    o a loss of data integrity.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2023-20572" target=3D= "_blank" rel=3D"noopener">CVE-2023-20572</a></td>
    </tr>

    <td class=3D"vendor-product">AMD--AMD Ryzen 3000 Series Desktop Processors<=

    <td>An observable timing discrepancy in the ASP could allow a privileged at= tacker to perform a brute-force attack against the hash message authenticat= ion code, allowing arbitrary message input, potentially leading to a loss o=
    f data integrity.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2023-20540" target=3D= "_blank" rel=3D"noopener">CVE-2023-20540</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-next.12, 21.2.13, 20.3.21, and 19.2.22, a Server-Side Request Forgery (SS= RF) vulnerability exists in @angular/platform-server. The issue stems from = how the server-side rendering (SSR) engine processes the request URL provid=
    ed to the rendering entry points. When an absolute-form URL (e.g., http://e= vil.com) is passed to the rendering engine, the internal ServerPlatformLoca= tion can be manipulated into adopting the attacker-controlled domain as the=
    "current" hostname. Consequently, any relative HttpClient requests or Plat= formLocation.hostname references are redirected to the attacker controlled = server, potentially exposing internal APIs or metadata services. This vulne= rability is fixed in 22.0.0-next.12, 21.2.13, 20.3.21, and 19.2.22.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46417" target=3D= "_blank" rel=3D"noopener">CVE-2026-46417</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>The Angular Language Service VS Code Extension provides a rich editing = experience for Angular templates. Prior to 21.2.4, the client-side Angular = Language Service VS Code extension reads the custom TypeScript SDK paths ty= pescript.tsdk and js/ts.tsdk.path directly from workspace configurations (.= vscode/settings.json) without verifying VS Code Workspace Trust state or as= king for user consent (located in client/src/client.ts). The client-side ex= tension then passes the parsed settings path as a command-line argument (--= tsdk) to the background Node.js language server process. During server init= ialization, the background language server resolves and dynamically imports=
    (via standard Node.js require()) the module library tsserverlibrary.js rel= ative to the workspace-specified custom directory path. An attacker can exp= loit this behavior by committing a repository containing a local malicious = tsserverlibrary.js script inside a custom folder, and a crafted .vscode/set= tings.json file pointing to that folder. When a developer opens the reposit= ory folder in VS Code, the extension automatically attempts to initialize a=
    nd load the server, which dynamically resolves, loads, and executes the mal= icious script silently in the background. This vulnerability is fixed in 21= .2.4.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49241" target=3D= "_blank" rel=3D"noopener">CVE-2026-49241</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-rc.2, 21.2.15, 20.3.22, and 19.2.23, an issue in the @angular/platform-se= rver package allows remote attackers to bypass host allowlist constraints a=
    nd direct server-side outgoing requests to arbitrary external endpoints. Th=
    is occurs due to a parser differential between the strict WHATWG URL parser=
    used for allowlist validation and the lenient Domino URL parser used to in= itialize the server emulated DOM. When a server-side request contains a mal= formed URL with a double port structure (e.g., http://evil.com:80:80/path),=
    Node's strict URL.canParse(url) logic returns false and skips host check v= alidation entirely. However, the same malformed URL is later accepted and p= arsed leniently by Domino's internal parser, which resolves the origin to h= ttp://evil.com:80. The Angular SSR HTTP request interceptor (relativeUrlsTr= ansformerInterceptorFn) then resolves all relative backend HTTP requests ag= ainst this adopted origin, executing the SSRF attack. This vulnerability is=
    fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50168" target=3D= "_blank" rel=3D"noopener">CVE-2026-50168</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-rc.2, 21.2.15 20.3.22, and 19.2.23, an issue in the @angular/service-work=
    er package compromises the integrity of request-policy enforcement during r= equest reconstruction. When the Angular Service Worker intercepts network r= equests for matched assets, it reconstructs a new Request object using an i= nternal helper function. During this reconstruction process, the helper fun= ction strips the strict, client-defined request redirect policy configurati=
    on (such as redirect: 'error'), falling back to the browser's default 'foll= ow' strategy. If the target web application makes client-side requests with=
    a strict policy (e.g., expecting a network error instead of automatically = following redirects), the service worker will bypass this instruction and a= utomatically follow HTTP 3xx redirects to other destinations. This acts as =
    an unintended proxy/intermediary ("Confused Deputy") and can result in cook= ie/credential exposure or same-origin session-restricted data leakage if pu= blic dynamic routes redirect to sensitive routes. This vulnerability is fix=
    ed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50169" target=3D= "_blank" rel=3D"noopener">CVE-2026-50169</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-rc.2, 21.2.15, 20.3.22, and 19.2.23, a vulnerability was discovered in @a= ngular/common when Server-Side Rendering (SSR) and hydration are enabled. T=
    he HttpTransferCache utility optimizes hydration by caching outgoing HTTP r= equests performed during SSR and transferring the cached state to the clien= t-side application via TransferState. However, the caching mechanism fails =
    to inspect the withCredentials flag or the Cookie header of outgoing reques= ts. As a result, credentialed, user-specific responses may be cached by def= ault in the shared TransferState payload. When these responses are serializ=
    ed into the HTML, any caching layer (such as a CDN, reverse proxy, or share=
    d server cache) that caches the SSR-rendered HTML page could inadvertently = cache and leak one user's private data to other users, leading to a high-se= verity information disclosure vulnerability. This vulnerability is fixed in=
    22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50170" target=3D= "_blank" rel=3D"noopener">CVE-2026-50170</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-rc.2, 21.2.15, 20.3.22, and 19.2.23, a Denial of Service (DoS) vulnerabil= ity exists in the @angular/common package of Angular. The formatNumber func= tion, which is also utilized by DecimalPipe, PercentPipe, and CurrencyPipe,=
    does not properly validate the upper bounds of the digitsInfo parameter. S= pecifically, the minimum and maximum fraction digits parsed from the digits= Info string (e.g., 1.2-4) are converted to integers and used without limits=
    . When parsing a maliciously crafted digitsInfo string with excessively lar=
    ge fraction digit values (e.g., 1.200000000-200000000), the internal roundN= umber function attempts to pad the digits array to match the requested frac= tion size. This results in an unbounded loop that repeatedly pushes element=
    s into an array. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.= 22, and 19.2.23.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50171" target=3D= "_blank" rel=3D"noopener">CVE-2026-50171</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>The Angular Language Service VS Code Extension provides a rich editing = experience for Angular templates. the client-side Angular Language Service =
    VS Code extension configures the tooltip Markdown renderer with the isTrust= ed: true option (located in client/src/client.ts). This setting instructs V=
    S Code to trust all rendered content it receives, which enables active elem= ents such as command: URIs. However, the background Angular Language Server=
    process fails to escape or sanitize brackets, raw links, and control chara= cters from JSDoc strings before forwarding the hover Markdown content (loca= ted in server/src/handlers/hover.ts and server/src/text_render.ts). An atta= cker can leverage this behavior by crafting a project TypeScript or JavaScr= ipt file (or a third-party npm package dependency) containing a malicious J= SDoc tooltip with an embedded active command link. When a developer hovers = over the target symbol to render the tooltip and clicks the malicious link,=
    the IDE executes the command sequence directly on the developer's host mac= hine. Prior to 21.2.4, This vulnerability is fixed in 21.2.4.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50178" target=3D= "_blank" rel=3D"noopener">CVE-2026-50178</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-rc.2, 21.2.15, 20.3.22, and 19.2.23, an issue in the @angular/service-wor= ker package compromises the integrity of request-policy enforcement during = request reconstruction. When the Angular Service Worker intercepts network = requests for matched assets, it reconstructs a new Request object using an = internal helper function. During this reconstruction process, the helper fu= nction strips explicit client-defined safety parameters: the credentials co= nfiguration (such as credentials: 'omit') and the HTTP cache mode configura= tion (such as cache: 'no-store'). These are reverted back to standard brows= er-default parameters (credentials: 'same-origin' and default HTTP cache pr= operties). This causes the browser to include active credentials (such as c= ookies or Authorization headers) on outbound requests where the client-side=
    developer explicitly instructed they should be omitted, leading to potenti=
    al session leaks. Additionally, it causes private or non-cacheable resource=
    s to be cached by the service worker's engine, making private page states a= ccessible or persistent inside the client's local cache post-logout. This v= ulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50184" target=3D= "_blank" rel=3D"noopener">CVE-2026-50184</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-rc.2, 21.2.16, 20.3.24, and 19.2.25, a Cross-Site Scripting (XSS) vulnera= bility exists in @angular/platform-server's DOM emulation dependency (domin=
    o) when serializing the content of raw-text elements (such as &lt;script&gt=
    ;, &lt;style&gt;, and &lt;iframe&gt;). domino supports escaping raw-text el= ements during serialization to prevent closing-tag breakout. However, a Uni= code index alignment bug existed in this escaping logic. In JavaScript, str= ing lengths and character indices are calculated based on UTF-16 code units=
    (where astral characters-such as emojis-occupy 2 code units / 4 bytes). If=
    the bound dynamic text contained astral Unicode characters before the clos= ing tag (e.g. &lt;/script&gt;, &lt;/style&gt;, or &lt;/iframe&gt;), the ind=
    ex offset calculation in domino's replacement logic shifted. This misalignm= ent caused domino to fail to replace or escape the closing tag, leaving it = raw and unescaped in the output HTML. An attacker who controls the dynamic = text can supply a payload containing both an astral Unicode character and a=
    closing tag (e.g., =C3=B0=C5=B8=CB=9C=E2=82=AC&lt;/iframe&gt;&lt;script&gt= ;alert(1)&lt;/script&gt;). When serialized on the server during SSR, the br= owser parses the unescaped closing tag, exits the raw-text context early, a=
    nd executes the subsequent &lt;script&gt; block, leading to same-origin Cro= ss-Site Scripting (XSS). This vulnerability is fixed in 22.0.0-rc.2, 21.2.1=
    6, 20.3.24, and 19.2.25.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50555" target=3D= "_blank" rel=3D"noopener">CVE-2026-50555</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-rc.2, 21.2.16, 20.3.24, and 19.2.25, a Cross-Site Scripting (XSS) vulnera= bility exists in @angular/platform-server's DOM emulation dependency (domin=
    o) when serializing the content of &lt;noscript&gt; elements. When renderin=
    g dynamic text content inside a &lt;noscript&gt; element via template bindi= ngs (such as {{ value }} or [textContent]), the template engine expects the=
    browser to render the content safely. Under Server-Side Rendering (SSR), d= omino is configured with scripting enabled, meaning &lt;noscript&gt; is tre= ated as a raw-text element. However, domino's serializer completely omitted=
    &lt;noscript&gt; from the list of raw-text elements requiring closing-tag = escaping during DOM serialization. As a result, any occurrence of &lt;/nosc= ript&gt; in the bound dynamic text was never escaped under any circumstance=
    s. The unescaped closing tag was serialized directly into the output HTML (= e.g. &lt;noscript&gt;&lt;/noscript&gt;&lt;script&gt;alert(1)&lt;/script&gt;= &lt;/noscript&gt;). When parsed by a browser, it closes the &lt;noscript&gt=
    ; block early, allowing the injected &lt;script&gt; block to execute in the=
    user's browser context, causing same-origin Cross-Site Scripting (XSS). Th=
    is vulnerability is fixed in 22.0.0-rc.2, 21.2.16, 20.3.24, and 19.2.25.</t=

    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50556" target=3D= "_blank" rel=3D"noopener">CVE-2026-50556</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-rc.2, 21.2.15, 20.3.22 and 19.2.22, an issue in the @angular/compiler and=
    @angular/core packages allows bypassing element and attribute sanitization= /validation through specific namespace workarounds. Specifically, namespace=
    d script elements (e.g., &lt;svg:script&gt; or &lt;:svg:script&gt;) were no=
    t properly identified as script elements by the Angular template preparser,=
    allowing them to pass through template compilation without being stripped.=
    Furthermore, security context schema mappings for element attributes did n=
    ot consistently handle attributes within namespaced elements (like SVG and = MathML), opening up gaps where malicious namespaced attributes could bypass=
    runtime and compile-time sanitizers. Combined, these flaws enable an attac= ker who can inject or supply a template/tag structure with custom namespace=
    s to bypass Angular's script-stripping logic and attribute sanitizers, lead= ing to client-side Cross-Site Scripting (XSS). This vulnerability is fixed =
    in 22.0.0-rc.2, 21.2.15, 20.3.22 and 19.2.22.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50557" target=3D= "_blank" rel=3D"noopener">CVE-2026-50557</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.= 0-rc.2, 21.2.15, 20.3.22, and 19.2.23, an issue in the @angular/core packag=
    e allows bypassing script-execution restrictions during dynamic component c= reation. Specifically, the dynamic component instantiation mechanism (creat= eComponent) failed to reject mounting components directly onto a &lt;script= &gt; or namespaced script element (such as &lt;svg:script&gt;). This enable=
    d the initialization of custom components on a tag that executes scripts, a= llowing attackers to hijack or inject script-executing hosts. This flaw ena= bles an attacker who can control the host element or selector parameter pas= sed to createComponent to initialize or mount an Angular component directly=
    onto a &lt;script&gt; tag, leading to execution of untrusted code or clien= t-side Cross-Site Scripting (XSS). This vulnerability is fixed in 22.0.0-rc= .2, 21.2.15, 20.3.22, and 19.2.23.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52725" target=3D= "_blank" rel=3D"noopener">CVE-2026-52725</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.=
    1, 21.2.17, and 20.3.25, an information disclosure vulnerability exists in = the @angular/service-worker package of the Angular framework. When the Serv= ice Worker fetches assets, it preserves metadata (such as headers) from the=
    original request. However, on cross-origin redirects, the Service Worker f= ails to strip sensitive headers, violating the Fetch redirect algorithm. Th=
    is allows a remote attacker to obtain sensitive credentials (e.g., Authoriz= ation tokens, Proxy-Authorization credentials, or session cookies) by trigg= ering a cross-origin redirect to an untrusted external origin. This vulnera= bility is fixed in 22.0.1, 21.2.17, and 20.3.25.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54264" target=3D= "_blank" rel=3D"noopener">CVE-2026-54264</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.=
    1, 21.2.17, and 20.3.25, an issue in the @angular/compiler package allows b= ypassing DOM property sanitization through the use of two-way property bind= ings. Specifically, when a native DOM property that requires sanitization (= such as innerHTML, srcdoc, src, href, data, or sandbox) is bound using the = two-way binding syntax (e.g., [(innerHTML)]=3D"value" or bindon-innerHTML= =3D"value"), the Angular template compiler failed to apply the appropriate = schema-derived sanitizer resolution to the TwoWayProperty operation. As a r= esult, native two-way DOM bindings were emitted without the required saniti= zer function, whereas equivalent one-way bindings would be properly sanitiz= ed. This flaw enables an attacker who can control the value of a two-way bo= und sensitive property to bypass Angular's built-in sanitization logic, pot= entially leading to client-side Cross-Site Scripting (XSS). This vulnerabil= ity is fixed in 22.0.1, 21.2.17, and 20.3.25.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54265" target=3D= "_blank" rel=3D"noopener">CVE-2026-54265</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.=
    1, 21.2.17, and 20.3.25, Angular's HttpTransferCache caches HTTP requests m= ade during Server-Side Rendering (SSR) so that they can be reused during cl= ient-side hydration. This avoids repeating the same HTTP requests on the cl= ient. The cached responses are stored in TransferState using a cache key ge= nerated by hashing request properties (method, response type, mapped URL, s= erialized body, and sorted query parameters). The cache keys are generated = using a weak 32-bit DJB2-like polynomial rolling hash. The 32-bit hash spac=
    e is extremely small, allowing attackers to find hash collisions. An attack=
    er can easily find a query parameter string (e.g., q=3DaaCAZMMM for a searc=
    h request) that produces the exact same 32-bit hash as a sensitive endpoint=
    (e.g., /api/user/profile). When a victim visits a crafted link containing = the colliding parameter, the SSR process executes both the search request a=
    nd the profile request. Due to the hash collision, the search response over= writes the profile response in the TransferState cache. This vulnerability =
    is fixed in 22.0.1, 21.2.17, and 20.3.25.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54266" target=3D= "_blank" rel=3D"noopener">CVE-2026-54266</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.=
    1, 21.2.17, and 20.3.25, to optimize client-side bootstrap in Server-Side R= endered (SSR) environments, Angular supports Hydration via provideClientHyd= ration(). During SSR, Angular serializes the application's runtime state (s= uch as cached HttpClient responses) and outputs it into the HTML stream as =
    a &lt;script&gt; tag with a predictable identifier. During client bootstrap=
    , Angular recovers this state by looking up the element via document.getEle= mentById('ng-state') and parsing its text content. Because the DOM element = lookup for the state container is predictable and relies solely on the ID s= elector (ng-state), it is susceptible to DOM Clobbering. If the application=
    binds untrusted user input or CMS content to element properties such as id=
    (e.g., &lt;div [id]=3D"userInput"&gt; or &lt;a id=3D"ng-state"&gt;) before=
    the genuine &lt;script&gt; tag is parsed by the browser, the attacker-cont= rolled element takes precedence in the DOM lookup. During hydration, when A= ngular calls document.getElementById('ng-state'), the browser returns the a= ttacker's clobbered element. Angular then attempts to parse the text conten=
    t or attributes of this clobbered element as JSON. This vulnerability is fi= xed in 22.0.1, 21.2.17, and 20.3.25.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54267" target=3D= "_blank" rel=3D"noopener">CVE-2026-54267</a></td>
    </tr>

    <td class=3D"vendor-product">angular--angular</td>
    <td>Angular is a development platform for building mobile and desktop web a= pplications using TypeScript/JavaScript and other languages. Prior to 22.0.=
    1, 21.2.17, and 20.3.25, a Denial of Service (DoS) vulnerability exists in = the @angular/common package of the Angular framework. The formatDate functi= on, which is also utilized by the standard Angular DatePipe, does not prope= rly limit or validate the length of the format parameter. When parsing a ma= liciously crafted, excessively long date format string (e.g., a repeating p= attern or very large string), the internal parser splits the string iterati= vely using a regular expression loop. This results in uncontrolled resource=
    consumption (high CPU utilization and excessive memory allocations), leadi=
    ng to a Denial of Service (DoS). This vulnerability is fixed in 22.0.1, 21.= 2.17, and 20.3.25.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54268" target=3D= "_blank" rel=3D"noopener">CVE-2026-54268</a></td>
    </tr>

    <td class=3D"vendor-product">anthropics--claude-code</td>
    <td>Claude Code is an agentic coding tool. From 0.2.54 until 2.1.163, becau=
    se the hostname huggingface.co was pre-approved as a bare hostname for the = WebFetch tool, any path on that domain-including attacker-controlled model = repositories-was auto-approved without a permission prompt or being subject=
    to --allowedTools restrictions. An attacker able to inject untrusted conte=
    nt into a Claude Code context could direct it to issue WebFetch requests ag= ainst attacker-controlled repository files (e.g. /resolve/main/config.json)=
    , which HuggingFace counts as downloads server-side, creating a covert out-= of-band channel for encoding and exfiltrating data Claude can access such a=
    s files, environment variables, or command output. Reliably exploiting this=
    required the ability to add untrusted content into a Claude Code context w= indow. This vulnerability is fixed in 2.1.163.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54316" target=3D= "_blank" rel=3D"noopener">CVE-2026-54316</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Airflow FTP=
    provider</td>
    <td>The Apache Airflow FTP provider's `FTPSHook.get_conn()` created an `ftp= lib.FTP_TLS` connection but never called `prot_p()`, so although the contro=
    l channel was TLS-protected the data channel was transmitted in cleartext. = Any deployment using `FTPSHook` or `FTPSFileTransmitOperator` to move files=
    over FTPS exposed file contents and credentials-in-transit to a network at= tacker able to observe the data connection. Upgrade apache-airflow-provider= s-ftp to `3.15.1` or later, which issues `PROT P` to encrypt the data chann= el.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49486" target=3D= "_blank" rel=3D"noopener">CVE-2026-49486</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Atlas</td> <td>An authenticated user can perform XSS. This issue affects Apache Atlas = versions 2.4.0 and earlier. Users are recommended to upgrade to version 2.5= .0, which fixes the issue.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-62198" target=3D= "_blank" rel=3D"noopener">CVE-2025-62198</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Doris MCP S= erver</td>
    <td>Apache Doris MCP Server contains a SQL injection vulnerability in a met= adata query path. A user-controlled database name is directly interpolated = into a SQL query, and the query is executed without passing the caller's au= thorization context. This may allow an authenticated attacker, or an anonym= ous attacker if authentication is disabled, to bypass SQL security validati=
    on and access metadata outside the intended database scope. Affected users = are recommended to upgrade to Doris version 0.6.1 or later, which fixes the=
    issue.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-66336" target=3D= "_blank" rel=3D"noopener">CVE-2025-66336</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache IoTDB</td> <td>Improper Limitation of a Pathname to a Restricted Directory ('Path Trav= ersal') vulnerability in Apache IoTDB. This issue affects Apache IoTDB: fro=
    m 2.0.0 before 2.0.6, from 1.0.0 before 1.3.6. Users are recommended to upg= rade to version 1.3.6 and 2.0.6, which fixes the issue.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-55017" target=3D= "_blank" rel=3D"noopener">CVE-2025-55017</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache IoTDB</td> <td>Improper Limitation of a Pathname to a Restricted Directory ('Path Trav= ersal') vulnerability in Apache IoTDB. This issue affects Apache IoTDB: fro=
    m 1.0.0 before 1.3.6, from 2.0.0 before 2.0.7. Users are recommended to upg= rade to version 1.3.6 and 2.0.7, which fixes the issue.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-64152" target=3D= "_blank" rel=3D"noopener">CVE-2025-64152</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Kerby</td> <td>By sending a deeply nested ASN1 structure to a Apache Kerby client or s= ervice, it's possible to trigger a StackOverFlow Exception which can lead t=
    o denial of service issues. Users are recommended to upgrade to version 2.1= .2, which fixes this issue.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57914" target=3D= "_blank" rel=3D"noopener">CVE-2026-57914</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Kerby</td> <td>It is possible to bypass the Kerberos pre-authentication check in Apach=
    e Kerby by sending a PA-DATA with an unrecognized or unsupported type. User=
    s are recommended to upgrade to version 2.1.2, which fixes this issue.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57915" target=3D= "_blank" rel=3D"noopener">CVE-2026-57915</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Kvrocks</td=

    <td>Improper Handling of Insufficient Permissions or Privileges vulnerabili=
    ty in Apache Kvrocks. This issue affects Apache Kvrocks: 2.8.0. Users are r= ecommended to upgrade to version 2.16.0, which fixes the issue.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41566" target=3D= "_blank" rel=3D"noopener">CVE-2026-41566</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Kvrocks</td=

    <td>Relative Path Traversal vulnerability in Apache Kvrocks. This issue aff= ects Apache Kvrocks: from 1.0.0 through 2.15.0. Users are recommended to up= grade to version 2.16.0, which fixes the issue.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45188" target=3D= "_blank" rel=3D"noopener">CVE-2026-45188</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Kvrocks</td=

    <td>A vulnerability in Apache Kvrocks. This issue affects Apache Kvrocks: f= rom 2.2.0 through 2.15.0. Users are recommended to upgrade to version 2.16.=
    0, which fixes the issue.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46751" target=3D= "_blank" rel=3D"noopener">CVE-2026-46751</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Kvrocks</td=

    <td>Redis Lua HEAP overflow in cjson library vulnerability in Apache Kvrock=
    s. This issue affects Apache Kvrocks: from 2.0.4 through 2.15.0. Users are = recommended to upgrade to version 2.16.0, which fixes the issue.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46752" target=3D= "_blank" rel=3D"noopener">CVE-2026-46752</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Kvrocks</td=

    <td>A vulnerability in Apache Kvrocks. This issue affects Apache Kvrocks: f= rom 2.6.0 through 2.15.0. Users are recommended to upgrade to version 2.16.=
    0, which fixes the issue.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54226" target=3D= "_blank" rel=3D"noopener">CVE-2026-54226</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache NiFi</td> <td>Authorization handling for component configuration verification request=
    s in Apache NiFi 1.15.0 through 2.9.0 allows clients with read access to su= bmit proposed configuration properties. The proposed properties override cu= rrent configuration, enabling users with read access to invoke predefined v= erification methods with alternative settings. Apache NiFi installations th=
    at do not implement different levels of authorization for viewing and modif= ying component configuration are not subject to this vulnerability. Upgradi=
    ng to Apache NiFi 2.10.0 is the recommended mitigation, requiring write acc= ess to submit configuration verification requests.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44911" target=3D= "_blank" rel=3D"noopener">CVE-2026-44911</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache NiFi</td> <td>Improper escaping of database table names in the CaptureChangeMySQL Pro= cessor included with Apache NiFi 1.2.0 through 2.9.0 allows for injecting S=
    QL commands using crafted naming. Manual quoted boundaries added in Apache = NiFi 1.8.0 narrowed the scope of potential injection options, but did not c= over additional strategies. Apache NiFi installations that do not use the C= aptureChangeMySQL Processor are not subject to this vulnerability. Upgradin=
    g to Apache NiFi 2.10.0 is the recommended mitigation, which incorporates m= ore robust identifier escaping.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44913" target=3D= "_blank" rel=3D"noopener">CVE-2026-44913</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache NiFi</td> <td>Apache NiFi 1.12.0 through 2.9.0 are missing authorization when replaci=
    ng Process Groups that include extension components with specific Required = Permissions based on the Restricted annotation. The Restricted annotation i= ndicates additional privileges required, but framework authorization did no=
    t check restricted status when handling requests to replace Process Groups.=
    The missing authorization permits a user with general write access to add = components with Restricted status. Apache NiFi installations that do not im= plement specific authorization for Restricted components are not subject to=
    this vulnerability because the framework enforces write permissions as the=
    security boundary. Upgrading to Apache NiFi 2.9.0 is the recommended mitig= ation, which removes the implementation of Restricted status authorization = from the framework.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44914" target=3D= "_blank" rel=3D"noopener">CVE-2026-44914</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache NiFi</td> <td>Apache NiFi 0.0.1 through 2.9.0 support building qualified URLs from on=
    e of several HTTP request headers that provide an alternative to the standa=
    rd Host header without validating the values provided. Apache NiFi 1.6.0 in= troduced a configurable application property to restrict values provided in=
    the HTTP Host header, but did not apply the validation to alternative Prox=
    y and Forwarded headers. The absence of proxy host header validation allowe=
    d a client to instruct Apache NiFi web services to construct invalid qualif= ied URLs for redirection or data references. Upgrading to Apache NiFi 2.10.=
    0 is the recommended mitigation, which implements validation for the X-Prox= yHost and X-Forwarded-Host HTTP request headers based on the nifi.web.proxy= .host property. Enabling header validation requires configuring the applica= tion with HTTPS. Reverse proxy servers in front of Apache NiFi are responsi= ble for filtering input request headers and providing allowed values to the=
    application.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54665" target=3D= "_blank" rel=3D"noopener">CVE-2026-54665</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Shiro</td> <td>When using Apache Shiro with the shiro-guice module in a web servlet co= ntext, a specially crafted HTTP request may cause an authentication bypass.=
    This vulnerability is similar to https://www.cve.org/CVERecord?id=3DCVE-20= 20-1957 https://www.cve.org/CVERecord , except that it affects the `shiro-g= uice` module instead of the `shiro-spring` module. This issue affects all A= pache Shiro versions through 2.x, and 3.0.0-alpha-1 only when using `shiro-= guice` module in a web servlet context. Upgrade to version 3.0.0 or later, = which fixes the issue.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56091" target=3D= "_blank" rel=3D"noopener">CVE-2026-56091</a></td>
    </tr>

    <td class=3D"vendor-product">Apache Software Foundation--Apache Shiro</td> <td>"Remember me" cookie age is not verified on the server. This potentiall=
    y allows an attacker to intercept a valid cookie and reuse it indefinitely,=
    even after the configured expiration time has passed. This issue affects a=
    ll Apache Shiro versions from 1.2.4 through 2.x, and 3.0.0-alpha-1, only wh=
    en RememberMe functionality is enabled. Upgrade to version 3.0.0 or later, = which fixes the issue.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56130" target=3D= "_blank" rel=3D"noopener">CVE-2026-56130</a></td>
    </tr>

    <td class=3D"vendor-product">Apple--Apple M1 GPU</td>
    <td>Apple M1 GPUs retain register file data between compute shader dispatch=
    es from different processes. A sandboxed Metal attacker app can run a GPU r= eader shader that reads stale register values left by a separate sandboxed = victim app. In the proof of concept, GPUVictim.app generates a fresh random=
    128-bit secret using SecRandomCopyBytes and loads it into GPU registers. G= PUAttacker.app, a separate sandboxed app, recovers the exact secret from st= ale GPU register state. NOTE: The vendor stated that this behavior affects = only legacy hardware and has already been addressed at the hardware level i=
    n current-generation Apple Silicon.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49269" target=3D= "_blank" rel=3D"noopener">CVE-2026-49269</a></td>
    </tr>

    <td class=3D"vendor-product">Apple--swift-nio-http2</td>
    <td>swift-nio-http2's HTTP/2-to-HTTP/1.1 codec did not validate pseudo-head=
    er values for control characters before placing them into the translated HT= TP/1.1 message. swift-nio-http2 1.44.1 adds validation of all pseudo-header=
    values (:path, :authority, :scheme, :method, and :status) at both the HPAC=
    K header validation layer and the HTTP/2-to-HTTP/1.1 translation layer. Req= uests or responses containing CR, LF, or NUL bytes in any pseudo-header val=
    ue are now rejected with a connection error. This issue is fixed in swift-n= io-http2 1.44.1.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-28898" target=3D= "_blank" rel=3D"noopener">CVE-2026-28898</a></td>
    </tr>

    <td class=3D"vendor-product">appsmithorg--appsmith</td>
    <td>Appsmith is a platform to build admin panels, internal tools, and dashb= oards. Prior to 1.99, the POST /api/v1/admin/send-test-email endpoint accep=
    ts attacker-controlled smtpHost and smtpPort values and establishes a raw J= avaMail TCP connection without any IP validation. This completely bypasses = WebClientUtils.IP_CHECK_FILTER, which only applies to Spring WebClient HTTP=
    requests. Additionally, the raw MailException.getMessage() is returned ver= batim in the API error response, enabling error-based internal port scannin=
    g and service banner enumeration. This vulnerability is fixed in 1.99.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49979" target=3D= "_blank" rel=3D"noopener">CVE-2026-49979</a></td>
    </tr>

    <td class=3D"vendor-product">appsmithorg--appsmith</td>
    <td>Appsmith is a platform to build admin panels, internal tools, and dashb= oards. Prior to 2.1, Appsmith's bundled supervisord exposes an XML-RPC inte= rface on port 9001, reachable from outside the container via a Caddy revers= e-proxy route at /supervisor/* on the public ingress. Combined with the APP= SMITH_SUPERVISOR_PASSWORD exposed via GET /api/v1/admin/env, any authentica= ted administrator can send arbitrary XML-RPC calls to supervisord and execu=
    te OS commands inside the Docker container via twiddler.addProgramToGroup. = This vulnerability is fixed in 2.1.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50189" target=3D= "_blank" rel=3D"noopener">CVE-2026-50189</a></td>
    </tr>

    <td class=3D"vendor-product">appsmithorg--appsmith</td>
    <td>Appsmith is a platform to build admin panels, internal tools, and dashb= oards. Prior to 2.1, the outbound HTTP host filter applied by WebClientUtil=
    s (used by the REST API and GraphQL datasource plugins) validates hosts aga= inst an exact-match string denylist. The comprehensive address-class check = (loopback, any-local, link-local, fc00::/7) exists only on a separate code = path used by SMTP, not by the HTTP plugin path. As a result, an authenticat=
    ed user can craft outbound requests that reach loopback-bound services insi=
    de the container. This vulnerability is fixed in 2.1.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55455" target=3D= "_blank" rel=3D"noopener">CVE-2026-55455</a></td>
    </tr>

    <td class=3D"vendor-product">aquasecurity--trivy</td>
    <td>Trivy is a security scanner. Prior to 0.71.0, when Trivy scans a Helm c= hart archive (.tgz), its custom tar unpacker reads each entry with io.ReadA= ll(tr) and no size limit. An attacker who can place a malicious .tgz file i=
    n the scanned path can craft a small compressed archive that decompresses t=
    o gigabytes, causing the Trivy process to be killed by the OS OOM killer. T= his vulnerability is fixed in 0.71.0.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54448" target=3D= "_blank" rel=3D"noopener">CVE-2026-54448</a></td>
    </tr>

    <td class=3D"vendor-product">aquasecurity--trivy</td>
    <td>Trivy is a security scanner. Prior to 0.71.1, when Trivy downloads an O=
    CI artifact, it uses the org.opencontainers.image.title annotation from the=
    artifact manifest as the destination filename without validation. An attac= ker who can make Trivy fetch an attacker-controlled artifact can supply a c= rafted annotation that resolves to a path outside the intended destination,=
    causing Trivy to write the layer content to an arbitrary location on the h= ost filesystem. This vulnerability is fixed in 0.71.1.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55092" target=3D= "_blank" rel=3D"noopener">CVE-2026-55092</a></td>
    </tr>

    <td class=3D"vendor-product">Aruba--ArubaSign</td>
    <td>Incorrect default permissions in ArubaSign, affecting versions prior to=
    v4.6.6. The vulnerability is caused by the assignment of inappropriate per= missions during the software's default installation, whereby the main execu= table and other programme files located in C:\Program Files have excessive = permissions for the 'Everyone' group. This could allow an unprivileged user=
    to replace the main executable and/or its components with a malicious file=
    , thereby enabling the execution of arbitrary code. In the worst-case scena= rio, if the malicious code is executed with elevated privileges (such as th= ose of Administrator or SYSTEM), the attacker could escalate privileges and=
    gain full control of the system, compromising both security and data integ= rity.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12602" target=3D= "_blank" rel=3D"noopener">CVE-2026-12602</a></td>
    </tr>

    <td class=3D"vendor-product">ash-project--ash</td>
    <td>Improperly Controlled Modification of Dynamically-Determined Object Att= ributes vulnerability in ash-project ash allows a user to set the value of =
    a private action argument that is intended to be controlled only by trusted=
    server-side code. Action arguments declared with public?: false are meant =
    to be set internally (for example via Ash.Changeset.set_private_argument/3)=
    and must not be settable from end-user input. When a changeset is built fr=
    om a parameter map, Ash filters out private arguments, but the filtering is=
    incomplete. In the regular changeset path (for_create, for_update, for_des= troy), private arguments are stripped only when the parameter key is an ato=
    m. When the key is a binary (string), as is the case for user-supplied para= meters, the private argument is kept and the user controls its value. In th=
    e atomic path (Ash.Changeset.fully_atomic_changeset/4, also reached through=
    atomic and bulk updates), private arguments are not stripped at all, regar= dless of whether the key is an atom or a binary. An attacker who can submit=
    parameters to an action that defines a private argument can therefore inje=
    ct a value for that argument. Depending on how the application uses the arg= ument (for example an acting_user_id driving authorization or record owners= hip), this can lead to an integrity violation or privilege escalation. This=
    issue affects ash: from 3.0.0 before 3.29.3.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55736" target=3D= "_blank" rel=3D"noopener">CVE-2026-55736</a></td>
    </tr>

    <td class=3D"vendor-product">ASUS--Armoury Crate</td>
    <td>A permissive list of allowed inputs in ASUS Armoury Crate allows a loca=
    l administrator to perform arbitrary memory read/write operations or cause =
    a system crash (BSOD) by bypassing the validation mechanism.Refer to the ' = Security Update for Armoury Crate App=C2=A0' section on the ASUS Security A= dvisory for more information.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8918" target=3D"= _blank" rel=3D"noopener">CVE-2026-8918</a></td>
    </tr>

    <td class=3D"vendor-product">ATEN--Unizon</td>
    <td>ATEN Unizon updateLicense Directory Traversal Arbitrary File Deletion V= ulnerability. This vulnerability allows remote attackers to delete arbitrar=
    y files on affected installations of ATEN Unizon. Authentication is require=
    d to exploit this vulnerability. The specific flaw exists within the update= License method. The issue results from the lack of proper validation of a u= ser-supplied path prior to using it in file operations. An attacker can lev= erage this vulnerability to delete files or create a denial-of-service cond= ition on the system. Was ZDI-CAN-28502.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9774" target=3D"= _blank" rel=3D"noopener">CVE-2026-9774</a></td>
    </tr>

    <td class=3D"vendor-product">ATEN--Unizon</td>
    <td>ATEN Unizon uploadSSL Directory Traversal Arbitrary File Deletion Vulne= rability. This vulnerability allows remote attackers to delete arbitrary fi= les on affected installations of ATEN Unizon. Authentication is required to=
    exploit this vulnerability. The specific flaw exists within the uploadSSL = method. The issue results from the lack of proper validation of a user-supp= lied path prior to using it in file operations. An attacker can leverage th=
    is vulnerability to delete files or create a denial-of-service condition on=
    the system. Was ZDI-CAN-28503.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9775" target=3D"= _blank" rel=3D"noopener">CVE-2026-9775</a></td>
    </tr>

    <td class=3D"vendor-product">ATEN--Unizon</td>
    <td>ATEN Unizon writeFileToHttpServletResponse Directory Traversal Informat= ion Disclosure Vulnerability. This vulnerability allows remote attackers to=
    disclose sensitive information on affected installations of ATEN Unizon. A= uthentication is not required to exploit this vulnerability. The specific f= law exists within the writeFileToHttpServletResponse method. The issue resu= lts from the lack of proper validation of a user-supplied path prior to usi=
    ng it in file operations. An attacker can leverage this vulnerability to di= sclose information in the context of SYSTEM. Was ZDI-CAN-28505.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9776" target=3D"= _blank" rel=3D"noopener">CVE-2026-9776</a></td>
    </tr>

    <td class=3D"vendor-product">ATEN--Unizon</td>
    <td>ATEN Unizon restoreDB Directory Traversal Remote Code Execution Vulnera= bility. This vulnerability allows remote attackers to execute arbitrary cod=
    e on affected installations of ATEN Unizon. Authentication is required to e= xploit this vulnerability. The specific flaw exists within the restoreDB me= thod. The issue results from the lack of proper validation of a user-suppli=
    ed path prior to using it in file operations. An attacker can leverage this=
    vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-28578.= </td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9777" target=3D"= _blank" rel=3D"noopener">CVE-2026-9777</a></td>
    </tr>

    <td class=3D"vendor-product">ATEN--Unizon</td>
    <td>ATEN Unizon ImportDeviceList Directory Traversal Remote Code Execution = Vulnerability. This vulnerability allows remote attackers to execute arbitr= ary code on affected installations of ATEN Unizon. Authentication is requir=
    ed to exploit this vulnerability. The specific flaw exists within the Impor= tDeviceList method. The issue results from the lack of proper validation of=
    a user-supplied path prior to using it in file operations. An attacker can=
    leverage this vulnerability to execute code in the context of SYSTEM. Was = ZDI-CAN-28579.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9778" target=3D"= _blank" rel=3D"noopener">CVE-2026-9778</a></td>
    </tr>

    <td class=3D"vendor-product">ATEN--Unizon</td>
    <td>ATEN Unizon doCryptoHugeFileToFile Improper Verification of Cryptograph=
    ic Signature Remote Code Execution Vulnerability. This vulnerability allows=
    remote attackers to execute arbitrary code on affected installations of AT=
    EN Unizon. Authentication is required to exploit this vulnerability. The sp= ecific flaw exists within the updateWar method. The issue results from an i= ncorrect implementation of cryptographic signature verification. An attacke=
    r can leverage this vulnerability to execute code in the context of SYSTEM.=
    Was ZDI-CAN-28590.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9779" target=3D"= _blank" rel=3D"noopener">CVE-2026-9779</a></td>
    </tr>

    <td class=3D"vendor-product">axiomatic-systems Bento4 --axiomatic-systems B= ento4=C2=A0</td>
    <td>A stack overflow in the AP4_StsdAtom::AP4_StsdAtom component of axiomat= ic-systems Bento4 before v1.8.9allows attackers to cause a Denial of Servic=
    e (DoS) via a crafted MP4 file.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-36907" target=3D= "_blank" rel=3D"noopener">CVE-2026-36907</a></td>
    </tr>

    <td class=3D"vendor-product">axiomatic-systems Bento4 --axiomatic-systems B= ento4=C2=A0</td>
    <td>A stack overflow in the AP4_Array&lt;AP4_TrunAtom::Entry&gt;::EnsureCap= acity component of axiomatic-systems Bento4 before v1.8.9allows attackers t=
    o cause a Denial of Service (DoS) via a crafted MP4 file.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-36908" target=3D= "_blank" rel=3D"noopener">CVE-2026-36908</a></td>
    </tr>

    <td class=3D"vendor-product">AzeoTech--DAQFactory</td>
    <td>In AzeoTech DAQFactory versions 21.1 and prior, a Use After Free vulner= ability can be exploited by an attacker using specially crafted .ctl files = which can result in code execution.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12921" target=3D= "_blank" rel=3D"noopener">CVE-2026-12921</a></td>
    </tr>

    <td class=3D"vendor-product">BerriAI--litellm</td>
    <td>LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or n= ative) format. Prior to 1.84.0, This vulnerability is fixed in 1.84.0.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49468" target=3D= "_blank" rel=3D"noopener">CVE-2026-49468</a></td>
    </tr>

    <td class=3D"vendor-product">Budibase--budibase</td>
    <td>Budibase is an open-source low-code platform. Prior to 3.39.0, an anony= mous attacker who knows or can enumerate a workspace id (app_...) and an S3= -source datasource id (ds_...) can call this endpoint with no auth and obta=
    in a 15-minute pre-signed PUT URL minted on the victim's IAM identity. The = endpoint also returns the publicUrl so the attacker knows exactly where the=
    ir PUT lands. Because bucket is attacker-controlled, the attacker can write=
    to any bucket those IAM credentials can write to, not only the bucket the = datasource was configured for. The Budibase server route POST /api/attachme= nts/:datasourceId/url (packages/server/src/api/routes/static.ts) is registe= red with only the recaptcha middleware. There is no authorized(...) middlew= are in the chain. The controller (packages/server/src/api/controllers/stati= c/index.ts::getSignedUploadURL) looks the requested datasource up, instanti= ates an AWS S3 client with the datasource's stored accessKeyId / secretAcce= ssKey, and returns an AWS Signature V4 pre-signed PutObjectCommand URL for = the caller-supplied bucket and key. The bucket is not pinned to the datasou= rce's configured bucket. The workspace context required by sdk.datasources.= get is sourced by getWorkspaceIdFromCtx (packages/backend-core/src/utils/ut= ils.ts) from any of: the x-budibase-app-id header, the JSON body appId, a p= ath segment that begins with the workspace prefix, or ?appId=3D. auth.build= AuthMiddleware([], { publicAllowed: true }) runs before any of this and exp= licitly allows anonymous requests. The currentWorkspace middleware's "deny = access to dev preview" branch only triggers under isBrowser(ctx) &amp;&amp;=
    !isApiKey(ctx); isBrowser checks the parsed User-Agent for a recognised br= owser, so any non-browser client (curl, the supplied PoC, any tool not sett= ing a browser UA) is neither and reaches dev workspaces too. This vulnerabi= lity is fixed in 3.39.0.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50137" target=3D= "_blank" rel=3D"noopener">CVE-2026-50137</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and below contain a Reflected XSS vulnerability in the html_au= th_footer. This issue has been fixed in version 1.2.31.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39897" target=3D= "_blank" rel=3D"noopener">CVE-2026-39897</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior are vulnerable to Path Traversal via filename parame= ter in package_import.php. This issue has been fixed in version 1.2.31.</td=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39899" target=3D= "_blank" rel=3D"noopener">CVE-2026-39899</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior are vulnerable to Reflected XSS via tab parameter in=
    the auth_profile.php JavaScript context. This issue has been fixed in vers= ion 1.2.31.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39900" target=3D= "_blank" rel=3D"noopener">CVE-2026-39900</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. In = versions 1.2.30 and prior, the rfilter request parameter is retrieved via t=
    he raw accessor grv() (rather than gfrv() with FILTER_VALIDATE_IS_REGEX val= idation) and concatenated directly into RLIKE SQL clauses in lib/html_graph= .php and lib/html_tree.php, which are reachable pre-authentication through = graph_view.php on installations with guest graph viewing enabled. Because t=
    he unbalanced-quote payload bypasses the regex validation that would otherw= ise reject it, an unauthenticated attacker can inject arbitrary SQL to comp= romise the confidentiality, integrity, and availability of the database. Th=
    is advisory is similar to GHSA-69gg-mjfm-jjpc. This issue has been fixed in=
    version 1.2.31.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39948" target=3D= "_blank" rel=3D"noopener">CVE-2026-39948</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior are vulnerable to Command Injection due to lack of s= anitization in the escape_command() function. The escape_command() function=
    at lib/rrd.php is a no-op: it returns $command unchanged. The command line=
    built by rrdtool_function_graph() is passed through this function and then=
    to shell_exec($full_commandline). The risk is in __rrd_execute() where tex= t_format values from graph templates (which may contain host variable subst= itutions) reach shell_exec without adequate escaping. This issue has been a= ddressed in version 1.2.31.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40079" target=3D= "_blank" rel=3D"noopener">CVE-2026-40079</a></td>
    </tr>

    <td class=3D"vendor-product">Cacti--cacti</td>
    <td>Cacti is an open source performance and fault management framework. Ver= sions 1.2.30 and prior have a package import signature validation bypass al= lows which allows self-signed packages. This issue has been fixed in versio=
    n 1.2.31.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-40941" target=3D= "_blank" rel=3D"noopener">CVE-2026-40941</a></td>
    </tr>

    <td class=3D"vendor-product">Caliptra--Core Runtime Firmware</td>
    <td>Incorrect check of function return value in Caliptra Core Runtime Firmw= are (ActivateFirmwareCmd::activate_fw modules) allows bypass of Caliptra Co= re's verification of the MCU FW during a hitless update. This issue affects=
    Core Runtime Firmware: from 2.0.0 through 2.0.1, 2.1.0.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-5818" target=3D"= _blank" rel=3D"noopener">CVE-2026-5818</a></td>
    </tr>

    <td class=3D"vendor-product">Caliptra--Core Runtime Firmware</td>
    <td>Missing cryptographic step in Caliptra Core Firmware (aes_256_gcm_updat=
    e module) results in an incorrect GCM authentication tag. When the streamin=
    g AES-256-GCM API is used with empty AAD, the hardware GHASH accumulator st= ate is not saved after the first update call, causing the final tag to excl= ude the first batch of processed ciphertext. Ciphertext produced by that ca=
    ll may be modified without the tag reflecting the change. This issue affect=
    s Core Runtime Firmware: from 2.0.0 through 2.0.1, 2.1.0.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6458" target=3D"= _blank" rel=3D"noopener">CVE-2026-6458</a></td>
    </tr>

    <td class=3D"vendor-product">Cboard--Cboard v0.4.2</td>
    <td>SQL Injection vulnerability in Cboard v.0.4.2 and before allows a remot=
    e attacker to execute arbitrary code via the getDimensionsValues component<=

    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52673" target=3D= "_blank" rel=3D"noopener">CVE-2026-52673</a></td>
    </tr>

    <td class=3D"vendor-product">chimurai--http-proxy-middleware</td> <td>http-proxy-middleware is node.js http-proxy middleware. From 0.16.0 unt=
    il 2.0.10, 3.0.6, and 4.1.0, http-proxy-middleware documents router proxy-t= able entries as host, path, or host+path selectors, but the host+path imple= mentation uses unanchored substring matching on attacker-controlled request=
    metadata. As a result, a crafted Host header that is only a superstring ma= tch for a configured host+path key can still route a request to an unintend=
    ed backend. This vulnerability is fixed in 2.0.10, 3.0.6, and 4.1.0.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55602" target=3D= "_blank" rel=3D"noopener">CVE-2026-55602</a></td>
    </tr>

    <td class=3D"vendor-product">cursor--cursor</td>
    <td>Cursor is a code editor built for programming with AI. Prior to 3.0, Cu= rsor runs agent terminal commands in a sandbox by default, and the sandbox = grants write access to the command's working directory. A flaw was identifi=
    ed in how the agent could modify the working_directory parameter, which cou=
    ld cause the sandbox to include writable paths outside the intended workspa= ce. A malicious agent could set working_directory to a sensitive location a=
    nd write arbitrary files outside the workspace under the user's privileges.=
    This enables non-sandboxed Remote Code Execution - for example by overwrit= ing the cursorsandbox helper so later commands run unsandboxed - with no us=
    er interaction beyond a benign prompt. This vulnerability is fixed in 3.0.<=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50548" target=3D= "_blank" rel=3D"noopener">CVE-2026-50548</a></td>
    </tr>

    <td class=3D"vendor-product">cursor--cursor</td>
    <td>Cursor is a code editor built for programming with AI. Prior to 3.0, Cu= rsor runs agent terminal commands in a sandbox by default. Before a Write, = the agent canonicalizes the target path to confirm it stays inside the work= space, but when canonicalization fails it falls back to the original path a=
    nd writes without approval. A malicious agent can create an in-workspace sy= mlink that points outside the workspace and force canonicalization to fail =
    - either because the target does not exist or because read permission is re= moved from the path - so the agent writes through the symlink to an arbitra=
    ry location without approval. A malicious agent could write arbitrary files=
    outside the workspace under the user's privileges. This enables non-sandbo= xed Remote Code Execution - for example by overwriting the cursorsandbox he= lper so later commands run unsandboxed - with no user interaction beyond a = benign prompt. This vulnerability is fixed in 3.0.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50549" target=3D= "_blank" rel=3D"noopener">CVE-2026-50549</a></td>
    </tr>

    <td class=3D"vendor-product">danpros--HTMLy</td>
    <td>HTMLy 3.1.1 contains a Server-Side Request Forgery (SSRF) vulnerability=
    in the RSS feed import functionality. The function get_feed() in system/ad= min/admin.php passes user-supplied $feed_url directly to file_get_contents(=
    ) without any validation. An authenticated attacker with administrative pri= vileges can exploit this by entering a crafted URL (e.g., http://dnslog.exa= mple.com, file:///etc/passwd, or http://169.254.169.254 in cloud contexts) = via Tools -&gt; Import RSS. The server will then make a request to the atta= cker-controlled target.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57940" target=3D= "_blank" rel=3D"noopener">CVE-2026-57940</a></td>
    </tr>

    <td class=3D"vendor-product">DAVIDO--Bytes::Random::Secure</td> <td>Bytes::Random::Secure versions through 0.29 for Perl share internal sta=
    te across forked processes. When an object is initialised before forking, o=
    r when the functional interface is used, then the internal state for the PR=
    NG is shared across processes and identical random streams will be produced=
    . Secrets generated in multiprocess applications are predictable across pro= cesses.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11625" target=3D= "_blank" rel=3D"noopener">CVE-2026-11625</a></td>
    </tr>

    <td class=3D"vendor-product">DAVIDO--Bytes::Random::Secure::Tiny</td> <td>Bytes::Random::Secure::Tiny versions through 1.011 for Perl share inter= nal state across forked processes. When an object is initialised before for= king, then the internal state for the PRNG is shared across processes and i= dentical random streams will be produced. Secrets generated in multiprocess=
    applications are predictable across processes.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11702" target=3D= "_blank" rel=3D"noopener">CVE-2026-11702</a></td>
    </tr>

    <td class=3D"vendor-product">Devolutions--Remote Desktop Manager</td> <td>Incorrect link resolution by display name in the custom PowerShell VPN = editor in Devolutions Remote Desktop Manager 2026.2.5 through 2026.2.11 all= ows an authenticated attacker with write access to a shared workspace to ex= ecute a PowerShell script in another user's context via a display name coll= ision with an existing VPN script link.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13372" target=3D= "_blank" rel=3D"noopener">CVE-2026-13372</a></td>
    </tr>

    <td class=3D"vendor-product">Devolutions--Server</td>
    <td>Improper input validation in the PAM AD discovery endpoints in Devoluti= ons Server 2026.2.4.0 through 2026.2.7.0 allows an authenticated user with = the UserGroupsView permission to coerce server-side authentication to an at= tacker-controlled host, exposing PAM provider credentials as a NTLMv2 chall= enge-response, via a crafted DomainName parameter.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12755" target=3D= "_blank" rel=3D"noopener">CVE-2026-12755</a></td>
    </tr>

    <td class=3D"vendor-product">dragonflydb--dragonfly</td>
    <td>Dragonfly is an in-memory data store built for modern application workl= oads. Prior to 1.39.9, Dragonfly has a RESP Protocol Injection via Lua redi= s.error_reply() in EvalSerializer. An authenticated user can inject arbitra=
    ry RESP messages into the connection's response stream, potentially causing=
    response desynchronization in connection-pool clients. This vulnerability =
    is fixed in 1.39.9.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47206" target=3D= "_blank" rel=3D"noopener">CVE-2026-47206</a></td>
    </tr>

    <td class=3D"vendor-product">DRIMO--DRIMO CMS</td>
    <td>DRIMO CMS is vulnerable to Reflected XSS via q parameter in searching f= unctionality. An attacker can prepare an URL that, when opened, results in = arbitrary JavaScript execution in the victim's browser. Product is in End O=
    f Life phase and will not receive any updates. However, deleting=C2=A0info.= php file mitigates the vulnerability,</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11772" target=3D= "_blank" rel=3D"noopener">CVE-2026-11772</a></td>
    </tr>

    <td class=3D"vendor-product">DROLSKY--List::SomeUtils::XS</td> <td>List::SomeUtils::XS versions before 0.59 for Perl have a heap buffer ov= erflow in the pairwise function. pairwise() collects the values returned by=
    the block into a heap buffer sized to the longer input array, then grows t=
    he buffer before each copy with a single quadrupling (alloc &lt;&lt;=3D 2) = instead of a loop. A block call that returns more than four times the curre=
    nt allocation in one invocation outgrows that one quadrupling, and the copy=
    writes past the end of the buffer. Any caller of pairwise() whose block re= turns, for a single pair, more than four times the longer input array's len= gth writes past the buffer and corrupts the heap.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12844" target=3D= "_blank" rel=3D"noopener">CVE-2026-12844</a></td>
    </tr>

    <td class=3D"vendor-product">Edgewall *Genshi*--Genshi</td>
    <td>Server side template inject (SSTI) in the expression evaluation compone=
    nt in Genshi Template Engine version 0.7.9 allows a remote attacker to achi= eve remote code execution (RCE) via crafted template expressions.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-0685" target=3D"= _blank" rel=3D"noopener">CVE-2026-0685</a></td>
    </tr>

    <td class=3D"vendor-product">electron--electron</td>
    <td>Electron is a framework for writing cross-platform desktop applications=
    using JavaScript, HTML and CSS. From 42.3.1 until 42.3.3, Buffer performs = incorrect byte length calculations resulting in heap buffer under/overflow.=
    Most apps will crash and some may perform incorrect buffer allocations in = the Node.js Buffer API resulting in unexpected truncation or allocation. Th=
    is vulnerability is fixed in 42.3.3.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54257" target=3D= "_blank" rel=3D"noopener">CVE-2026-54257</a></td>
    </tr>

    <td class=3D"vendor-product">elixir-plug--plug</td>
    <td>Inefficient algorithmic complexity in Plug's nested-parameter decoder a= llows an unauthenticated remote attacker to cause denial of service. Plug.C= onn.Query.decode/4 (and Plug.Conn.Query.decode_each/2) parse query strings = and application/x-www-form-urlencoded request bodies. When a key contains m= any bracketed segments such as a[a][a][a]=3D1, the decoder walks the bracke=
    ts and, for each of the N levels, performs a map operation keyed on an ever= -growing binary prefix of the key, hashing the full byte range at each step=
    . The total decode cost is therefore quadratic in the number of nesting lev= els. With the default Plug.Parsers.URLENCODED body limit of 1,000,000 bytes=
    , a single request can carry roughly 333,000 nesting levels and saturate a = BEAM scheduler for minutes. A small number of concurrent requests can satur= ate all schedulers and render a Plug-based server unresponsive. No authenti= cation or knowledge of application routes is required. This vulnerability i=
    s associated with program files lib/plug/conn/query.ex and program routines=
    Plug.Conn.Query.decode/4, Plug.Conn.Query.decode_each/2, Plug.Conn.Query.s= plit_keys/6, Plug.Conn.Query.insert_keys/3, and Plug.Conn.Query.finalize_po= inter/2. This issue affects plug from 1.15.0 before 1.15.5, 1.16.4, 1.17.2,=
    1.18.3, and 1.19.3.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54892" target=3D= "_blank" rel=3D"noopener">CVE-2026-54892</a></td>
    </tr>

    <td class=3D"vendor-product">FasterXML--jackson-databind</td> <td>jackson-databind contains the general-purpose data-binding functionalit=
    y and tree-model for Jackson Data Processor. From 2.13.0 until 2.14.0, a po= tential Denial-of-Service exists when attacker sends deeply nested JSON if = (and only if) the service reads deeply nested (1000s of levels) JSON as Jso= nNode (ObjectMapper.readTree()) and writes out same (or modifided) node usi=
    ng JsonNode.toString(). This can consume significant amount of resources wi=
    th concurrent relatively small requests (1000 nested arrays is 2kB). This v= ulnerability is fixed in 2.14.0.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50193" target=3D= "_blank" rel=3D"noopener">CVE-2026-50193</a></td>
    </tr>

    <td class=3D"vendor-product">FastStone--FastStone Image Viewer v8.3</td>
    <td>A heap overflow in the FSViewer.exe process of FastStone Image Viewer v= 8.3 allows attackers to cause a execute arbitrary code in the context of th=
    e current process via supplying a crafted JPEG 2000 (JP2) file.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-30040" target=3D= "_blank" rel=3D"noopener">CVE-2026-30040</a></td>
    </tr>

    <td class=3D"vendor-product">FastStone--FastStone Image Viewer v8.3</td>
    <td>An integer overflow in the PSD parser compnent of FastStone Image Viewe=
    r v8.3 allows attackers to execute arbitrary code or cause a Denial of Serv= ice (DoS) via supplying a crafted PSD file.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-30041" target=3D= "_blank" rel=3D"noopener">CVE-2026-30041</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Prior to = 2.63.6, the Hook Authentication feature in File Browser allows administrato=
    rs to delegate login verification to an external shell command. User-suppli=
    ed credentials (username and password) are interpolated into this command s= tring using os.Expand without sanitization. An unauthenticated remote attac= ker can inject shell metacharacters in the username or password field at th=
    e login screen, causing the server to execute arbitrary OS commands before = any authentication takes place. This is a critical pre-authentication RCE. = This vulnerability is fixed in 2.63.6.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54088" target=3D= "_blank" rel=3D"noopener">CVE-2026-54088</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Prior to = 2.33.8, when a shell interpreter is configured (e.g. /bin/sh -c), the comma=
    nd allowlist can be bypassed through shell metacharacters. The allowlist va= lidates only the first token of user input, but the entire raw string is ha= nded to the shell - semicolons, pipes, backticks, and $() all work to chain=
    arbitrary commands after a permitted one. This vulnerability is fixed in 2= .33.8.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54090" target=3D= "_blank" rel=3D"noopener">CVE-2026-54090</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Prior to = 2.63.6, filebrowser builds the download-as-zip / download-as-tar archive en= try names with filepath.ToSlash, which on a Linux host is a no-op for backs= lashes (\ is only a path separator on Windows). A file whose name contains = Windows-style traversal is accepted by the resource handlers, stored on the=
    Linux filesystem with a literal backslash name, and then emitted verbatim =
    as the archive entry name. Windows extractors interpret \ as a path separat=
    or and write the extracted file outside the extraction directory - arbitrar=
    y file write on the victim who downloads and extracts the archive. This vul= nerability is fixed in 2.63.6.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54093" target=3D= "_blank" rel=3D"noopener">CVE-2026-54093</a></td>
    </tr>

    <td class=3D"vendor-product">filebrowser--filebrowser</td>
    <td>File Browser is a file managing interface for uploading, deleting, prev= iewing, renaming, and editing files within a specified directory. Prior to = 2.63.6, a low-privileged authenticated user of filebrowser (with create + d= elete permissions in their own isolated scope) can silently destroy share-l= ink records belonging to any other user - including the administrator - by = performing a legitimate DELETE on a file in their own directory whose logic=
    al path happens to be a byte-prefix of another user's stored share.Link.Pat=
    h. The file contents of the victim are not exposed, but the victim's share = links are irrevocably wiped. This vulnerability is fixed in 2.63.6.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54097" target=3D= "_blank" rel=3D"noopener">CVE-2026-54097</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise through 2.2.4 contains an unauthenticated arbitrary file upload=
    vulnerability in the /api/v1/attachments endpoint when storageType is set =
    to local. Attackers can exploit path traversal in the chatId and chatflowId=
    parameters to upload malicious files to arbitrary directories, potentially=
    enabling remote code execution and server compromise.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-71333" target=3D= "_blank" rel=3D"noopener">CVE-2025-71333</a></td>
    </tr>

    <td class=3D"vendor-product">Flowise--Flowise</td>
    <td>Flowise before 3.1.0 contains a server-side request forgery vulnerabili=
    ty in the Execute Flow node that allows attackers to bypass security valida= tion by providing intranet addresses through the base URL field. Attackers = can initiate HTTP requests to internal network addresses, access cloud meta= data, and enumerate internal services by exploiting the missing secureFetch=
    verification in httpSecurity.ts.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56275" target=3D= "_blank" rel=3D"noopener">CVE-2026-56275</a></td>
    </tr>

    <td class=3D"vendor-product">FOSSBilling--FOSSBilling</td>
    <td>FOSSBilling is a billing and client management system that automates in= voicing, payments, and communication for online service businesses. Version=
    s 0.6.21 through 0.7.2 are vulnerable to IDOR through the support ticket cr= eation workflow. By manipulating rel_id when rel_type=3Dorder, an authentic= ated client can create a support ticket that references another client's or= der they do not own. The ticketCreateForClient() method accepted rel_id wit= hout verifying order ownership for non-upgrade tasks, allowing clients to l= ink a new ticket to another client's order by crafting the request. No cron=
    task automatically processes cancel/upgrade requests from ticket relations=
    ; staff action is required. This affects integrity and confidentiality: sta=
    ff could be misled into acting on the wrong order (e.g., cancellation or up= grade requests). While there is no client-to-client order data exposure, or= der IDs may appear in ticket context. This issue has been fixed in version = 0.8.0.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-64105" target=3D= "_blank" rel=3D"noopener">CVE-2025-64105</a></td>
    </tr>

    <td class=3D"vendor-product">FOSSBilling--FOSSBilling</td>
    <td>FOSSBilling is a free, open-source billing and client management system=
    . In versions 0.7.2 and prior, a query-construction flaw in client list end= points allowed authenticated clients to bypass tenant scoping and retrieve = other clients' data. Details In ServiceTransaction::getSearchQuery() and Or= der\Service::getSearchQuery(), OR-based search/action filters were appended=
    without grouping, allowing SQL operator precedence to evaluate OR clauses = independently of the enforced client_id constraint. Crafted requests could = therefore return records and metadata belonging to other clients, including=
    identifiers, amounts, status, timestamps, and related fields. This issue w=
    as fixed in version 0.8.0.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-23513" target=3D= "_blank" rel=3D"noopener">CVE-2026-23513</a></td>
    </tr>

    <td class=3D"vendor-product">FOSSBilling--FOSSBilling</td>
    <td>FOSSBilling is a free, open-source billing and client management system=
    . Starting in version 0.5.4 and prior to version 0.8.0, an authorization by= pass in the API role handling allows unauthenticated access to privileged `= /api/system/*` endpoints. Because `system` resolves to the cron admin ident= ity, attackers can invoke admin API methods without valid credentials, sess= ion, or CSRF token. Version 0.8.0 patches the issue. Some workarounds are a= vailable. Block external access to `/api/system/*` at reverse proxy/WAF, re= strict API access by trusted source IPs only (`api.allowed_ips`), rotate al=
    l admin/client API tokens immediately, invalidate active sessions and reset=
    high-privilege credentials, and/or review API request logs for suspicious = `/api/system/` access and treat as potential incident.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-27604" target=3D= "_blank" rel=3D"noopener">CVE-2026-27604</a></td>
    </tr>

    <td class=3D"vendor-product">FOSSBilling--FOSSBilling</td>
    <td>FOSSBilling is a free, open-source billing and client management system=
    . In versions 0.7.2 and prior, the Servicecustom Client API's __call method=
    accepts an order_id parameter and fetches the associated order without ver= ifying the authenticated client owns it, potentially exposing cross-client = data through IDOR. An authenticated client can access any other client's cu= stom service by guessing sequential order IDs. This can lead to a confident= iality breach - attackers can read client PII (name, email, phone, address,=
    company details, VAT number) and service configuration data belonging to o= ther clients. This issue has been fixed in version 0.8.0.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-27708" target=3D= "_blank" rel=3D"noopener">CVE-2026-27708</a></td>
    </tr>

    <td class=3D"vendor-product">FOSSBilling--FOSSBilling</td>
    <td>FOSSBilling is a free, open-source billing and client management system=
    . Versions prior to 0.8.0 have a Server-Side Template Injection (SSTI) vuln= erability in the template rendering system. Administrators with access to f= eatures that render Twig templates (email templates, mass mail campaigns, c= ustom payment adapters, and the `string_render` API endpoint) can inject ar= bitrary Twig expressions, leading to information disclosure and remote code=
    execution. The vulnerability exists because Twig templates are rendered wi= thout a sandbox, allowing access to the full Twig environment, API context,=
    and the application's dependency injection container. Version 0.8.0 patche=
    s the issue. Some workarounds are available. Audit existing email templates=
    for suspicious Twig expressions, rotate all admin and client API tokens, a= nd/or block external access to /api/system/* at reverse proxy/WAF to mitiga=
    te chaining with GHSA-78x5-c8gw-8279.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-28496" target=3D= "_blank" rel=3D"noopener">CVE-2026-28496</a></td>
    </tr>

    <td class=3D"vendor-product">FOSSBilling--FOSSBilling</td>
    <td>FOSSBilling is a free, open-source billing and client management system=
    . Versions 0.7.2 and prior expose a guest API endpoint, /api/guest/staff/cr= eate, intended for initial administrator bootstrap. Due to a flawed admin-e= xistence check, the endpoint remains usable after an administrator already = exists. The flawed guard check uses is_countable() on a value that returns =
    a Model_Admin object or null rather than a countable type, causing the expr= ession to always evaluate as true and bypass the intended protection. As a = result, an attacker can reach the unprotected endpoint to create a new admi= nistrator account and immediately authenticate, gaining a fully privileged = admin session even when an admin already exists. This issue has been fixed =
    in version 0.8.0.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-33543" target=3D= "_blank" rel=3D"noopener">CVE-2026-33543</a></td>
    </tr>

    <td class=3D"vendor-product">FOSSBilling--FOSSBilling</td>
    <td>FOSSBilling is a free, open-source billing and client management system=
    . In versions 0.5.4 through 0.7.2, the /run-patcher maintenance endpoint in=
    FOSSBilling was accessible without authentication, which allowed unauthent= icated remote users to trigger update patch routines that modify configurat= ion files, execute database schema changes, perform filesystem mutations, a=
    nd clear caches. The /run-patcher endpoint executes privileged maintenance = operations - configuration migrations, database patch execution (including = ALTER TABLE, DROP TABLE, UPDATE statements), filesystem deletions and renam= es, and cache clearing - without requiring administrator authentication, CS=
    RF validation, or CLI context. An unauthenticated remote attacker can trigg=
    er these operations by sending a simple HTTP GET request to /run-patcher, w= hich can be abused for denial-of-service attacks. Certain patches (e.g., ba= tch token regeneration for all admin and client accounts in patch 53, and s= ession invalidation) are disruptive even when re-executed against an alread= y-patched instance. Repeated or concurrent requests may also cause inconsis= tent database state. This issue has been fixed in version 0.8.0.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-43920" target=3D= "_blank" rel=3D"noopener">CVE-2026-43920</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev due to improper neutralization of user-controlled = input before generating HTML output in the Audit Trail component.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50698" target=3D= "_blank" rel=3D"noopener">CVE-2026-50698</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev. An authenticated attacker with write access to Au=
    to Repeat can persist HTML/JavaScript in reference_document using a whiteli= sted write path and trigger script execution when users open the affected A= uto Repeat form.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50699" target=3D= "_blank" rel=3D"noopener">CVE-2026-50699</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev due to improper neutralization of user-controlled = input in the frappe.get_avatar function.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50700" target=3D= "_blank" rel=3D"noopener">CVE-2026-50700</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Reflected Cross-Site Scripting (XSS) vulnerability exists in Frappe F= ramework version 17.0.0-dev due to improper neutralization of user-controll=
    ed input in the dashboard-view component.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50701" target=3D= "_blank" rel=3D"noopener">CVE-2026-50701</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev due to improper neutralization of user-controlled = input in the Desk desktop icon renderer.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50703" target=3D= "_blank" rel=3D"noopener">CVE-2026-50703</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev due to improper neutralization of user-controlled = input in the File View breadcrumb renderer.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50704" target=3D= "_blank" rel=3D"noopener">CVE-2026-50704</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Cross-Site Scripting (XSS) vulnerability exists in Frappe Framework v= ersion 17.0.0-dev due to improper neutralization of untrusted input in the = Form Dashboard headline renderer.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50705" target=3D= "_blank" rel=3D"noopener">CVE-2026-50705</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev due to improper neutralization of user-controlled = input in the MultiSelectDialog component.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50708" target=3D= "_blank" rel=3D"noopener">CVE-2026-50708</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev due to improper neutralization of user-controlled = input in the Notifications &gt; Events panel.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50709" target=3D= "_blank" rel=3D"noopener">CVE-2026-50709</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev due to unsafe evaluation of user-controlled data i=
    n the Number Card component.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50710" target=3D= "_blank" rel=3D"noopener">CVE-2026-50710</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev due to improper neutralization of user-controlled = input in the Number Card component.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50711" target=3D= "_blank" rel=3D"noopener">CVE-2026-50711</a></td>
    </tr>

    <td class=3D"vendor-product">Frappe--Frappe Framework</td>
    <td>A Stored Cross-Site Scripting (XSS) vulnerability exists in Frappe Fram= ework version 17.0.0-dev due to improper neutralization of user-controlled = input in the frappe.ui.Tree component</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50712" target=3D= "_blank" rel=3D"noopener">CVE-2026-50712</a></td>
    </tr>

    <td class=3D"vendor-product">FreeBSD--FreeBSD</td>
    <td>When used to deliver a signal to a specific thread, thr_kill2(2) called=
    p_cansignal() to determine whether the operation was permitted but did not=
    check the result before delivering the signal. The signal was sent even wh=
    en the permission check failed. The system call returned the resulting erro=
    r to the caller, but by then the signal had already been delivered. The mis= sing check allows an unprivileged local user who knows or can guess a targe= t's process and thread IDs to send any signal to a process they would not n= ormally be permitted to signal, including processes owned by other users or=
    by root. The same check enforces jail boundaries, so a jailed process can = signal processes on the host or in other jails. Thread IDs are allocated gl= obally and sequentially, and so can be discovered by brute force with no vi= sibility into the target. An attacker can stop or terminate arbitrary proce= sses, including critical system daemons, resulting in a Denial of Service (= DoS).</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45256" target=3D= "_blank" rel=3D"noopener">CVE-2026-45256</a></td>
    </tr>

    <td class=3D"vendor-product">FreeBSD--FreeBSD</td>
    <td>The KTLS receive path decrypted each record in place, assuming that the=
    mbufs holding received data were anonymous and safe to modify. This assump= tion does not hold for data placed on a socket by sendfile(2), which can re= ference file-backed memory directly through non-anonymous M_EXTPG pages or = EXT_SFBUF mbufs. When the sender transmits such data over a loopback connec= tion without enabling KTLS on the transmit side, the file-backed mbufs reac=
    h the receiver's decryption path unchanged. Decrypting a record in place th=
    en overwrites the backing file's page cache instead of a private copy of th=
    e data. An unprivileged local user who can read a file can overwrite its co= ntents with data of their choosing by sending the file over a loopback conn= ection on which they have enabled KTLS receive. The write modifies the page=
    cache directly, so it bypasses file flags such as schg and is written back=
    to disk. By overwriting a setuid binary or other trusted file, a local use=
    r can escalate privileges, potentially gaining full control of the affected=
    system.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45257" target=3D= "_blank" rel=3D"noopener">CVE-2026-45257</a></td>
    </tr>

    <td class=3D"vendor-product">FreeBSD--FreeBSD</td>
    <td>dsp_mmap_single() validated the requested mapping by checking the sum o=
    f the user-supplied offset and length against the buffer size. This additio=
    n could overflow, so that a large offset and length wrapped around and pass=
    ed the check. The offset was then narrowed from 64 to 32 bits when converte=
    d to a buffer address, yielding a mapping that extended past the audio buff=
    er into unrelated kernel memory. The /dev/dsp device nodes are world-access= ible by default. On a system with an audio device, either issue allows an u= nprivileged local user to read and write kernel memory, which can be used t=
    o escalate privileges, potentially gaining full control of the affected sys= tem. At a minimum, an attacker can crash the kernel, resulting in a Denial =
    of Service (DoS).</td>
    <td>2026-06-27</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45258" target=3D= "_blank" rel=3D"noopener">CVE-2026-45258</a></td>
    </tr>

    <td class=3D"vendor-product">FreeBSD--FreeBSD</td>
    <td>sigqueue(2) was marked as permitted in capability mode with the introdu= ction of Capsicum in 2011, but the implementation of kern_sigqueue did not = include a capability mode check restricting signal delivery to the calling = process's own PID. A process in capability mode can use sigqueue(2) to send=
    signals to any process it could signal following standard Unix permissions=
    , bypassing the Capsicum sandbox restriction. A compromised sandboxed proce=
    ss could interfere with other processes, for example by sending SIGKILL or = SIGSTOP. This could be any process running as the same user, or any process=
    , for a superuser sandboxed process.</td>
    <td>2026-06-27</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45259" target=3D= "_blank" rel=3D"noopener">CVE-2026-45259</a></td>
    </tr>

    <td class=3D"vendor-product">FreeBSD--FreeBSD</td>
    <td>The kernel handler for IPV6_MSFILTER dropped a serializing lock in orde=
    r to copy the source-filter list from userspace, then reacquired the lock. = During this window another thread could free the multicast filter structure=
    , leaving the handler with a stale pointer to freed memory. An unprivileged=
    local user can exploit this use-after-free to escalate privileges.</td> <td>2026-06-27</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49412" target=3D= "_blank" rel=3D"noopener">CVE-2026-49412</a></td>
    </tr>

    <td class=3D"vendor-product">FreeBSD--FreeBSD</td>
    <td>The Linuxulator determined whether a binary was set-user-ID or set-grou= p-ID by checking the P_SUGID process flag. During execve(2), this flag is n=
    ot yet set at the point where the auxiliary vector is constructed, so AT_SE= CURE was incorrectly set to zero for set-user-ID and set-group-ID executabl= es. An unprivileged local user can inject a shared library via LD_PRELOAD i= nto a set-user-ID or set-group-ID Linux binary, gaining the privileges of t= hat binary.</td>
    <td>2026-06-27</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49413" target=3D= "_blank" rel=3D"noopener">CVE-2026-49413</a></td>
    </tr>

    <td class=3D"vendor-product">FreeBSD--FreeBSD</td>
    <td>The ELF image activator cleared per-process ASLR preference flags for s= etuid binaries after the code that computes the PIE base address, rather th=
    an before. As a result, a user-requested ASLR disable was still in effect a=
    t the point where the base address was chosen. An unprivileged local user c=
    an disable ASLR for a setuid PIE binary by calling procctl(2) before execve= (2). This makes exploitation of any separate memory corruption vulnerabilit=
    y in that binary significantly easier.</td>
    <td>2026-06-27</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49414" target=3D= "_blank" rel=3D"noopener">CVE-2026-49414</a></td>
    </tr>

    <td class=3D"vendor-product">FreeBSD--FreeBSD</td>
    <td>The CONS_HISTORY ioctl handler did not adequately validate the requeste=
    d history size. A large value caused an integer overflow in the buffer size=
    calculation, resulting in a heap allocation smaller than expected. Subsequ= ent initialization of the buffer wrote beyond the end of the allocation. An=
    unprivileged local user with access to a vt(4) device can trigger an out-o= f-bounds write in the kernel, potentially escalating privileges.</td> <td>2026-06-27</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49416" target=3D= "_blank" rel=3D"noopener">CVE-2026-49416</a></td>
    </tr>

    <td class=3D"vendor-product">FreeBSD--FreeBSD</td>
    <td>Second, the audio buffer backing a mapping could be freed when the devi=
    ce was closed even though the mapping remained valid. The freed memory coul=
    d then be reused elsewhere while still accessible through the stale mapping=
    . The /dev/dsp device nodes are world-accessible by default. On a system wi=
    th an audio device, either issue allows an unprivileged local user to read = and write kernel memory, which can be used to escalate privileges, potentia= lly gaining full control of the affected system. At a minimum, an attacker = can crash the kernel, resulting in a Denial of Service (DoS).</td> <td>2026-06-27</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49417" target=3D= "_blank" rel=3D"noopener">CVE-2026-49417</a></td>
    </tr>

    <td class=3D"vendor-product">Gaudire--Assassin game</td>
    <td>The vulnerability is present in the '/addJugador' endpoint: * The 'keyJ= ugador' and 'keyJugadorObjectiu' parameters allow the modification of other=
    users' information without requiring prior authorization validation. This = could enable an authenticated attacker to alter any user's ID and change th= eir information. * The 'punts' and 'numObjectiusEliminats' fields allow arb= itrary data to be added because user input is not properly validated. This = makes it possible to obtain authentic prizes, awarded by city councils, by = falsifying game scores. * In the 'tokens' field, administrative privileges = can be self-assigned without server validation or prior authentication. Thi=
    s vulnerability could allow an authenticated attacker to grant themselves a= dministrator permissions and thus escalate privileges. * Numeric fields all=
    ow the entry of extremely long values, which can cause the system to crash.=
    Successful exploitation of this vulnerability could allow an authenticated=
    attacker to launch a denial-of-service (DoS) attack, preventing created ga= mes from being playable. * The 'urlImatge' parameter allows server-side req= uests to arbitrary URLs, enabling the retrieval of users' internal IP addre= sses, access to internal services, reading of local files, and unauthorized=
    interaction with third-party APIs. An authenticated attacker could gain ac= cess to sensitive data.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7165" target=3D"= _blank" rel=3D"noopener">CVE-2026-7165</a></td>
    </tr>

    <td class=3D"vendor-product">Gaudire--Assassin game</td>
    <td>Vulnerability involving the exposure of sensitive data provided without=
    adequate protection. The API exposes email and phone number data from the = 'email' and 'telefon' fields. This vulnerability is also present in the loc=
    al database, as it contains accessible sensitive information such as data o=
    n minors and municipal users. Successful exploitation of this vulnerability=
    could allow an unauthenticated remote attacker to gain access to sensitive=
    information and data.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7166" target=3D"= _blank" rel=3D"noopener">CVE-2026-7166</a></td>
    </tr>

    <td class=3D"vendor-product">Gaudire--Assassin game</td>
    <td>The vulnerability arises when the system fails to properly validate the=
    'email' field during the authentication process, allowing unverified or fa=
    ke email addresses to be accepted. This lack of validation enables the crea= tion of user accounts with fake email addresses, facilitating the mass crea= tion of fraudulent accounts. Successful exploitation of this vulnerability = could allow an authenticated attacker to carry out various attacks, such as=
    mass spam distribution, system abuse, or bypassing user controls, thereby = compromising the security and integrity of the system.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7167" target=3D"= _blank" rel=3D"noopener">CVE-2026-7167</a></td>
    </tr>

    <td class=3D"vendor-product">getk2.org--K2 extension for Joomla</td>
    <td>A Joomla user with K2 "create item" rights (Author tier by default) can=
    submit an article whose `embedVideo` POST field contains a raw `&lt;script= &gt;` tag; K2 stores it verbatim and renders it unescaped to any visitor of=
    the article page.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48940" target=3D= "_blank" rel=3D"noopener">CVE-2026-48940</a></td>
    </tr>

    <td class=3D"vendor-product">getk2.org--K2 extension for Joomla</td>
    <td>The K2 frontend `item.checkin` task accepts an unauthenticated `sigProF= older` query parameter and uses it directly to address a `JFolder::delete()=
    ` call under `/media/k2/galleries/`</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48941" target=3D= "_blank" rel=3D"noopener">CVE-2026-48941</a></td>
    </tr>

    <td class=3D"vendor-product">getk2.org--K2 extension for Joomla</td>
    <td>K2 =C3=A2=E2=80=B0=C2=A4 2.26 renders the `#__k2_users.image` column di= rectly into HTML `src` attributes via two distinct templates, in both cases=
    without HTML escaping.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48942" target=3D= "_blank" rel=3D"noopener">CVE-2026-48942</a></td>
    </tr>

    <td class=3D"vendor-product">getk2.org--K2 extension for Joomla</td>
    <td>K2 =C3=A2=E2=80=B0=C2=A4 2.24 contains a mass-assignment defect in the =
    K2 system user plugin `plg_user_k2`. A Registered Joomla user, by including=
    the field `K2UserForm=3D1` in a standard `com_users` `profile.save` POST, = can write arbitrary values into the `notes`, `image`, and `plugins` columns=
    of their own row in the `#__k2_users` table - none of which are exposed by=
    the K2 frontend profile-edit form.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48943" target=3D= "_blank" rel=3D"noopener">CVE-2026-48943</a></td>
    </tr>

    <td class=3D"vendor-product">getk2.org--K2 extension for Joomla</td>
    <td>The K2 frontend article-save handler accepts an `attachment[N][existing=
    ]` POST field that is concatenated with `JPATH_SITE/` and passed to `JFile:= :copy()`. `JPath::clean` does NOT strip `..`, and there is no allow-list of=
    source paths. An Author can therefore copy `configuration.php` (or any oth=
    er file readable by the web user - including `../../../etc/passwd`) into `/= media/k2/attachments/`, then retrieve the contents via the K2 attachment-do= wnload endpoint.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48944" target=3D= "_blank" rel=3D"noopener">CVE-2026-48944</a></td>
    </tr>

    <td class=3D"vendor-product">getk2.org--K2 extension for Joomla</td>
    <td>The K2 article gallery upload path accepts a zip/tar archive, extracts =
    it under `/media/k2/galleries/&lt;id&gt;/`, and only renames image files (g= if/jpg/jpeg/png/webp) to safe names - non-image files (including `.php`) ar=
    e extracted as-is and remain executable via direct HTTP access.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48945" target=3D= "_blank" rel=3D"noopener">CVE-2026-48945</a></td>
    </tr>

    <td class=3D"vendor-product">getk2.org--K2 extension for Joomla</td>
    <td>The K2 frontend article-attachment upload path accepts files whose exte= nsion is `.php`, and Apache's standard mod_php matches `\.php$` and execute=
    s them under the K2 web user. A K2 Author can upload a `shell.php`, then fe= tch `/media/k2/attachments/shell.php` and execute arbitrary PHP code in the=
    web server's context.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48946" target=3D= "_blank" rel=3D"noopener">CVE-2026-48946</a></td>
    </tr>

    <td class=3D"vendor-product">GIMP--GIMP</td>
    <td>GIMP HDR File Parsing Heap-based Buffer Overflow Remote Code Execution = Vulnerability. This vulnerability allows remote attackers to execute arbitr= ary code on affected installations of GIMP. User interaction is required to=
    exploit this vulnerability in that the target must visit a malicious page =
    or open a malicious file. The specific flaw exists within the parsing of HD=
    R files. The issue results from the lack of proper validation of the length=
    of user-supplied data prior to copying it to a heap-based buffer. An attac= ker can leverage this vulnerability to execute code in the context of the c= urrent process. Was ZDI-CAN-28266.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-2050" target=3D"= _blank" rel=3D"noopener">CVE-2026-2050</a></td>
    </tr>

    <td class=3D"vendor-product">GitHub--GitHub Copilot 1.372.0</td>
    <td>GitHub Copilot 1.372.0 allows filesystem access outside of a workspace = folder (without user approval) via a file-handler URI parameter to fetch_we= bpage. Therefore, exfiltration could occur if there is indirect prompt inje= ction.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-66389" target=3D= "_blank" rel=3D"noopener">CVE-2025-66389</a></td>
    </tr>

    <td class=3D"vendor-product">GitLab--GitLab</td>
    <td>GitLab has remediated an issue in GitLab CE/EE affecting all versions f= rom 8.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that und=
    er certain conditions could have allowed an authenticated user with maintai= ner-role permissions to make requests to internal network resources through=
    mirror synchronization due to improper URL validation.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12635" target=3D= "_blank" rel=3D"noopener">CVE-2026-12635</a></td>
    </tr>

    <td class=3D"vendor-product">GNOME--libxml2</td>
    <td>Use After Free in libxml2's xmlParseInternalSubset from GNOME libxml2 v= ersion 2.9.11 to 2.11.0 allows a remote attacker to cause a denial-of-servi=
    ce via maliciously crafted XML input with improper entity resolution handli= ng.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6653" target=3D"= _blank" rel=3D"noopener">CVE-2026-6653</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, when E= NABLE_REVERSE_PROXY_AUTHENTICATION is enabled, Gogs accepts the configured = authentication header (default: X-WEBAUTH-USER) directly from client reques=
    ts without validating that the request originated from a trusted reverse pr= oxy. Any remote attacker who can reach the Gogs service can forge this head=
    er to impersonate any user or trigger automatic account creation, completel=
    y bypassing authentication. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-25119" target=3D= "_blank" rel=3D"noopener">CVE-2026-25119</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, a repo= sitory admin collaborator can escalate their privileges to owner-level acce=
    ss by exploiting an off-by-one error in the ChangeCollaborationAccessMode f= unction. This vulnerability is fixed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52804" target=3D= "_blank" rel=3D"noopener">CVE-2026-52804</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, in new= _form.tmpl, milestone names are rendered with Go's default auto-escaping ({= {.Name}}), which converts &lt; to &amp;lt; etc. This prevents direct HTML i= njection. However, when the browser renders the DOM, the text content of th=
    e element contains the decoded original payload. Semantic UI 2.4.2's dropdo=
    wn component has preserveHTML: true as the default setting. When a user sel= ects a dropdown item, the internal set.text() method calls jQuery's .html()=
    with the item's text content. This re-parses the decoded text as HTML, cre= ating the injected element and triggering the JavaScript event handler. An = attacker can store an HTML/JavaScript payload in a milestone name, and when=
    any user opens the New Issue page and interacts with the milestone dropdow=
    n, the payload executes in their browser via Semantic UI's preserveHTML beh= avior. This vulnerability is fixed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52807" target=3D= "_blank" rel=3D"noopener">CVE-2026-52807</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, Git sm= art HTTP authorizes POST /git-receive-pack using the client-supplied servic=
    e query string (so ?service=3Dgit-upload-pack is evaluated as read access) = while routing still runs git receive-pack, allowing push where only read sh= ould be allowed. This vulnerability is fixed in 0.14.3.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52810" target=3D= "_blank" rel=3D"noopener">CVE-2026-52810</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, (*Repo= sitory).UploadRepoFiles checks for symlinks only on the leaf of the upload = target (osx.IsSymlink(targetPath)). The siblings UpdateRepoFile, DeleteRepo= File, and GetDiffPreview use hasSymlinkInPath, which lstats every component=
    - UploadRepoFiles is the lone outlier. An attacker with repo-write access = plus a multipart upload whose filename contains a literal backslash (preser= ved by filepath.Base on Linux, then converted to / by pathx.Clean) redirect=
    s the write through a previously-committed directory symlink. iox.CopyFile = opens the destination with os.Create (no O_NOFOLLOW), so the kernel follows=
    the parent symlink and writes attacker bytes anywhere the gogs UID can wri=
    te - ~git/.ssh/authorized_keys =C3=A2=E2=80=A0=E2=80=99 SSH foothold, or &l= t;repo&gt;.git/hooks/post-receive =C3=A2=E2=80=A0=E2=80=99 next-push RCE. T= his vulnerability is fixed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52811" target=3D= "_blank" rel=3D"noopener">CVE-2026-52811</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, Git LF=
    S storage is content-addressed by OID alone (&lt;LFS-root&gt;/&lt;oid[0]&gt= ;/&lt;oid[1]&gt;/&lt;oid&gt;) but per-repo authorization lives in the lfs_o= bject table keyed (repo_id, oid). serveUpload skips re-uploading when the O=
    ID file already exists on disk and inserts a new (repo_id, oid) row pointin=
    g at it without verifying the request body hashes to the OID being claimed.=
    Any user with write access to one repo can bind their repo to an OID owned=
    by a private repo and download the original bytes via their own download e= ndpoint. This vulnerability is fixed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52812" target=3D= "_blank" rel=3D"noopener">CVE-2026-52812</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, the Go=
    gs built-in Go SSH server is vulnerable to an unauthenticated, asymmetric D= enial of Service (DoS) attack. The application accepts inbound TCP connecti= ons and passes them to golang.org/x/crypto/ssh.NewServerConn inside a new g= oroutine without enforcing any read/write deadlines on the underlying net.C= onn. An unauthenticated attacker can open multiple TCP connections to the S=
    SH port and simply withhold the SSH protocol banner. This forces the server=
    to spawn an unbounded number of goroutines that block indefinitely waiting=
    for socket I/O. This leads to complete File Descriptor (FD) exhaustion, pr= eventing legitimate users from accessing the Git SSH service, and ultimatel=
    y destabilizing the entire Gogs process (e.g., causing internal log rotatio=
    n failures). This vulnerability is fixed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52814" target=3D= "_blank" rel=3D"noopener">CVE-2026-52814</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, Gogs h=
    as an unauthenticated information disclosure vulnerability. The GET /api/v1= /orgs/:orgname/teams endpoint at internal/route/api/v1/org_team.go:8 return=
    s all teams for any organization without requiring authentication. The rout=
    e group at internal/route/api/v1/api.go:380-385 lacks the reqToken() middle= ware, and the listTeams() handler performs no authentication check, exposin=
    g team IDs, names, descriptions, and permission levels to any unauthenticat=
    ed caller. This vulnerability is fixed in 0.14.3.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52815" target=3D= "_blank" rel=3D"noopener">CVE-2026-52815</a></td>
    </tr>

    <td class=3D"vendor-product">gogs--gogs</td>
    <td>Gogs is an open source self-hosted Git service. Prior to 0.14.3, the Ju= pyter Notebook (ipynb) sanitizer endpoint at POST /-/api/sanitize_ipynb all= ows arbitrary data: URIs without proper restrictions, potentially leading t=
    o Cross-Site Scripting (XSS). The endpoint uses bluemonday.UGCPolicy() with=
    p.AllowURLSchemes("data") which permits all data URI schemes including dat= a:text/html, enabling attackers to inject malicious HTML/JavaScript. Additi= onally, the endpoint has no authentication middleware, allowing any registe= red user to exploit this vulnerability. This vulnerability is fixed in 0.14= .3.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52816" target=3D= "_blank" rel=3D"noopener">CVE-2026-52816</a></td>
    </tr>

    <td class=3D"vendor-product">golang.org/x/image--golang.org/x/image/tiff</t=

    <td>The TIFF decoder does not set a limit on the size of tiles in tiled ima= ges, permitting a malicious or corrupt image containing a very large tile t=
    o cause unbounded memory consumption.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46602" target=3D= "_blank" rel=3D"noopener">CVE-2026-46602</a></td>
    </tr>

    <td class=3D"vendor-product">golang.org/x/image--golang.org/x/image/tiff</t=

    <td>The TIFF decoder can panic when decoding an invalid image with an out-o= f-bounds strip offset.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46604" target=3D= "_blank" rel=3D"noopener">CVE-2026-46604</a></td>
    </tr>

    <td class=3D"vendor-product">golang.org/x/image--golang.org/x/image/webp</t=

    <td>The webp decoder can panic when processing a VP8 chunk with dimensions = that do not match the canvas size.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46601" target=3D= "_blank" rel=3D"noopener">CVE-2026-46601</a></td>
    </tr>

    <td class=3D"vendor-product">Google Cloud--Cloud Console UIs</td>
    <td>A Missing Authorization vulnerability in a GraphQL private API operatio=
    n of the Google App Engine section of the Cloud Console allows an unauthent= icated remote attacker to leak sensitive App Engine request logs from other=
    projects using a specially crafted request. This vulnerability was patched=
    on 7 April 2026, and no customer action is needed.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8934" target=3D"= _blank" rel=3D"noopener">CVE-2026-8934</a></td>
    </tr>

    <td class=3D"vendor-product">Google Cloud--Gemini CLI</td>
    <td>Improper Neutralization used in an OS Command in the container launcher=
    in Google Gemini CLI (versions prior to 0.39.1) and run-gemini-cli GitHub = Action (versions prior to 0.1.22) on headless CI platforms allows an unpriv= ileged attacker to achieve pre-sandbox host-level code execution a maliciou= sly crafted .gemini/.env file.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12537" target=3D= "_blank" rel=3D"noopener">CVE-2026-12537</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Inappropriate implementation in DeviceBoundSessionCredentials in Google=
    Chrome prior to 149.0.7827.197 allowed a remote attacker to bypass same or= igin policy via a crafted HTML page. (Chromium security severity: High)</td=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13021" target=3D= "_blank" rel=3D"noopener">CVE-2026-13021</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Inappropriate implementation in Autofill in Google Chrome prior to 149.= 0.7827.197 allowed a remote attacker who had compromised the renderer proce=
    ss to leak cross-origin data via a crafted HTML page. (Chromium security se= verity: High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13022" target=3D= "_blank" rel=3D"noopener">CVE-2026-13022</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Uninitialized Use in GPU in Google Chrome prior to 149.0.7827.197 allow=
    ed a remote attacker who had compromised the renderer process to obtain pot= entially sensitive information from process memory via a crafted HTML page.=
    (Chromium security severity: High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13023" target=3D= "_blank" rel=3D"noopener">CVE-2026-13023</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Insufficient validation of untrusted input in Navigation in Google Chro=
    me prior to 149.0.7827.197 allowed a remote attacker who had compromised th=
    e renderer process to bypass site isolation via a crafted HTML page. (Chrom= ium security severity: High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13024" target=3D= "_blank" rel=3D"noopener">CVE-2026-13024</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Race in DevTools in Google Chrome prior to 149.0.7827.197 allowed a rem= ote attacker who had compromised the renderer process to potentially perfor=
    m a sandbox escape via a crafted HTML page. (Chromium security severity: Hi= gh)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13025" target=3D= "_blank" rel=3D"noopener">CVE-2026-13025</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in Digital Credentials in Google Chrome on Mac prior to = 149.0.7827.197 allowed a remote attacker to potentially exploit heap corrup= tion via a crafted HTML page. (Chromium security severity: High)</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13026" target=3D= "_blank" rel=3D"noopener">CVE-2026-13026</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in FileSystem in Google Chrome prior to 149.0.7827.197 a= llowed a remote attacker to potentially exploit heap corruption via a craft=
    ed HTML page. (Chromium security severity: High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13027" target=3D= "_blank" rel=3D"noopener">CVE-2026-13027</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in WebGL in Google Chrome on Android prior to 149.0.7827= .197 allowed a remote attacker to potentially perform a sandbox escape via =
    a crafted HTML page. (Chromium security severity: Critical)</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13028" target=3D= "_blank" rel=3D"noopener">CVE-2026-13028</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in Web Authentication in Google Chrome prior to 149.0.78= 27.197 allowed an attacker who convinced a user to install a malicious exte= nsion to potentially exploit heap corruption via a crafted Chrome Extension=
    . (Chromium security severity: High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13029" target=3D= "_blank" rel=3D"noopener">CVE-2026-13029</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Uninitialized Use in GPU in Google Chrome on Android prior to 149.0.782= 7.197 allowed a remote attacker to obtain potentially sensitive information=
    from process memory via a crafted HTML page. (Chromium security severity: = High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13030" target=3D= "_blank" rel=3D"noopener">CVE-2026-13030</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in Blink in Google Chrome prior to 149.0.7827.197 allowe=
    d a remote attacker to execute arbitrary code inside a sandbox via a crafte=
    d HTML page. (Chromium security severity: High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13031" target=3D= "_blank" rel=3D"noopener">CVE-2026-13031</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in WebGL in Google Chrome on Android prior to 149.0.7827= .197 allowed a remote attacker to potentially perform a sandbox escape via =
    a crafted HTML page. (Chromium security severity: Critical)</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13032" target=3D= "_blank" rel=3D"noopener">CVE-2026-13032</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Out of bounds read and write in Blink&gt;InterestGroups in Google Chrom=
    e prior to 149.0.7827.197 allowed a remote attacker to execute arbitrary co=
    de via a crafted HTML page. (Chromium security severity: Critical)</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13033" target=3D= "_blank" rel=3D"noopener">CVE-2026-13033</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Inappropriate implementation in Passwords in Google Chrome prior to 149= .0.7827.197 allowed a remote attacker who had compromised the renderer proc= ess to bypass site isolation via a crafted HTML page. (Chromium security se= verity: High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13034" target=3D= "_blank" rel=3D"noopener">CVE-2026-13034</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in Bluetooth in Google Chrome on Mac prior to 149.0.7827= .197 allowed a remote attacker to execute arbitrary code via a malicious pe= ripheral. (Chromium security severity: High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13035" target=3D= "_blank" rel=3D"noopener">CVE-2026-13035</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in Blink in Google Chrome prior to 149.0.7827.197 allowe=
    d a remote attacker to execute arbitrary code inside a sandbox via a crafte=
    d HTML page. (Chromium security severity: High)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13036" target=3D= "_blank" rel=3D"noopener">CVE-2026-13036</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in WebView in Google Chrome on Android prior to 149.0.78= 27.197 allowed a local attacker to execute arbitrary code inside a sandbox = via a crafted HTML page. (Chromium security severity: High)</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13037" target=3D= "_blank" rel=3D"noopener">CVE-2026-13037</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in Autofill in Google Chrome on Windows prior to 149.0.7= 827.197 allowed a remote attacker to execute arbitrary code via a crafted H= TML page. (Chromium security severity: Critical)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13038" target=3D= "_blank" rel=3D"noopener">CVE-2026-13038</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Integer overflow in Mojo in Google Chrome prior to 149.0.7827.201 allow=
    ed a remote attacker who had compromised the renderer process to potentiall=
    y perform a sandbox escape via a malicious file. (Chromium security severit=
    y: High)</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13281" target=3D= "_blank" rel=3D"noopener">CVE-2026-13281</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in Payments in Google Chrome on Android prior to 149.0.7= 827.201 allowed a local attacker to potentially exploit heap corruption via=
    physical access to the device. (Chromium security severity: High)</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13282" target=3D= "_blank" rel=3D"noopener">CVE-2026-13282</a></td>
    </tr>

    <td class=3D"vendor-product">Google--Chrome</td>
    <td>Use after free in AdFilter in Google Chrome on Android prior to 149.0.7= 827.201 allowed a remote attacker who convinced a user to engage in specifi=
    c UI gestures to execute arbitrary code via a crafted HTML page. (Chromium = security severity: High)</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13283" target=3D= "_blank" rel=3D"noopener">CVE-2026-13283</a></td>
    </tr>

    <td class=3D"vendor-product">Google--go-attestation</td>
    <td>Improper Validation of Specified Index, Position, or Offset in Input vu= lnerability in Google go-attestation. parseEfiSignatureList() does not adva= nce the buffer past vendor bytes before reading entries. For hashSHA256SigG= UID lists, this allows attacker-controlled vendor header bytes to be append=
    ed to the trusted SHA256 hash list. A crafted TPM event log could inject ar= bitrary SHA256 hashes into the verifier's trusted measurement database, ena= bling a remote attestation verifier to accept a compromised boot state. Thi=
    s issue affects go-attestation: through 0.6.0.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12681" target=3D= "_blank" rel=3D"noopener">CVE-2026-12681</a></td>
    </tr>

    <td class=3D"vendor-product">GPAC--MP4Box</td>
    <td>A use-after-free in the gf_sei_load_from_state_internal function (/filt= ers/sei_load.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to c= ause a Denial of Service (DoS) via supplying a crafted MPEG-2 TS file.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-60464" target=3D= "_blank" rel=3D"noopener">CVE-2025-60464</a></td>
    </tr>

    <td class=3D"vendor-product">GPAC--MP4Box</td>
    <td>A use-after-free in the gf_filter_pid_inst_swap function (/filter_core/= filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to cau=
    se a Denial of Service (DoS) via supplying a crafted media file.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-60465" target=3D= "_blank" rel=3D"noopener">CVE-2025-60465</a></td>
    </tr>

    <td class=3D"vendor-product">GPAC--MP4Box</td>
    <td>A use-after-free in the gf_filter_pid_get_packet function (/filter_core= /filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to ca= use a Denial of Service (DoS) via supplying a crafted media file.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-60466" target=3D= "_blank" rel=3D"noopener">CVE-2025-60466</a></td>
    </tr>

    <td class=3D"vendor-product">GPAC--MP4Box</td>
    <td>A use-after-free in the gf_filter_pid_inst_swap_delete_task function (/= filter_core/filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allows atta= ckers to cause a Denial of Service (DoS) via supplying a crafted media file= .</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-60467" target=3D= "_blank" rel=3D"noopener">CVE-2025-60467</a></td>
    </tr>

    <td class=3D"vendor-product">GPAC--MP4Box</td>
    <td>GPAC Multimedia Open Source Project GPAC Project/MP4Box 2.5-DEV-rev1593= -gfe88c3545-master is affected by: Buffer Overflow. The impact is: cause a = denial of service (local). The component is: filter_core/filter_pid.c (L:57= 4-580): function gf_filter_pid_inst_swap_delete_task() improperly accesses = freed objects during PID instance swap/delete cleanup, leading to heap use-= after-free. The attack vector is: Local (AV:L): a local, authenticated user=
    who processes a specially crafted MPEG-2 TS/MP4 file with MP4Box can trigg=
    er the bug during filter teardown (PID instance swap/delete), causing a cra= sh. =C3=82=C2=B6=C3=82=C2=B6 In GPAC s MP4Box, gf_filter_pid_inst_swap_dele= te_task() in filter_core/filter_pid.c may dereference objects after they ha=
    ve been freed when cleaning up PID instances after a swap/delete operation.=
    Crafted inputs (e.g., malformed MPEG-2 TS) can trigger a heap use-after-fr=
    ee and crash; exploitation may be possible.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-60468" target=3D= "_blank" rel=3D"noopener">CVE-2025-60468</a></td>
    </tr>

    <td class=3D"vendor-product">GPAC--MP4Box</td>
    <td>A use-after-free in the gf_filter_pid_reconfigure_task_discard function=
    (/filter_core/filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allows a= ttackers to cause a Denial of Service (DoS) via supplying a crafted media f= ile.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-60471" target=3D= "_blank" rel=3D"noopener">CVE-2025-60471</a></td>
    </tr>

    <td class=3D"vendor-product">GPAC--MP4Box</td>
    <td>A NULL pointer dereference in the gf_filter_in_parent_chain function (/= filter_core/filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allows atta= ckers to cause a Denial of Service (DoS) via supplying a crafted file.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-60473" target=3D= "_blank" rel=3D"noopener">CVE-2025-60473</a></td>
    </tr>

    <td class=3D"vendor-product">GPAC--MP4Box</td>
    <td>A buffer overflow in the gf_media_import function (/media_tools/av_pars= ers.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to cause a De= nial of Service (DoS) via supplying a crafted input.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-60474" target=3D= "_blank" rel=3D"noopener">CVE-2025-60474</a></td>
    </tr>

    <td class=3D"vendor-product">GPAC--MP4Box v2.4</td>
    <td>GPAC MP4Box v2.4 was discovered to contain a NULL pointer dereference i=
    n the gf_isom_add_track_kind() function at isomedia/isom_write.c. This vuln= erability allows attackers to cause a Denial of Service (DoS) via a crafted=
    MP4 file.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-55639" target=3D= "_blank" rel=3D"noopener">CVE-2025-55639</a></td>
    </tr>

    <td class=3D"vendor-product">Grocery-Store-Management-System--Grocery-Store= -Management-System</td> <td>GROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL-PHPMYADMIN v1.0 was=
    discovered to contain a SQL injection vulnerability in the scost parameter=
    in /grocery/search_products.php. This vulnerability allows attackers to ac= cess sensitive database information via a crafted SQL statement.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-37149" target=3D= "_blank" rel=3D"noopener">CVE-2026-37149</a></td>
    </tr>

    <td class=3D"vendor-product">HAYAJO--Mojolicious::Plugin::Web::Auth::OAuth2= </td>
    <td>Mojolicious::Plugin::Web::Auth::OAuth2 versions through 0.17 for Perl h= ave an insecure default state parameter. When no state generator is specifi=
    ed in the constructor, the module defaults to using a SHA-1 hash of predict= able and low-entropy sources, including the epoch time (which is leaked via=
    the HTTP Date header) and a call to Perl's built-in rand function. A predi= ctable state allows an attacker to hijack another user's session through cr= oss site request forgery (CSRF).</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9733" target=3D"= _blank" rel=3D"noopener">CVE-2026-9733</a></td>
    </tr>

    <td class=3D"vendor-product">Horner Automation--Cscape</td>
    <td>Horner Automation Cscape versions prior to 10.2 SP3 are vulnerable to a=
    n Out-of-Bounds Read vulnerability through parsing CSP files. Successful ex= ploitation of this vulnerability could allow an attacker to disclose inform= ation and execute arbitrary code.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12897" target=3D= "_blank" rel=3D"noopener">CVE-2026-12897</a></td>
    </tr>

    <td class=3D"vendor-product">HP Inc.--HP Dock Accessory</td>
    <td>A potential security vulnerability has been identified in the HP Access= ory WMI Provider installer for some HP Docking Stations, which might allow = escalation of privilege and/or arbitrary code execution. HP is releasing so= ftware updates to mitigate the potential vulnerability.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7539" target=3D"= _blank" rel=3D"noopener">CVE-2026-7539</a></td>
    </tr>

    <td class=3D"vendor-product">HYPR--Passwordless</td>
    <td>Missing authentication for critical function vulnerability in HYPR Pass= wordless on Windows allows Credentials Interception. This issue affects HYP=
    R Passwordless: before 11.1.1.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-4522" target=3D"= _blank" rel=3D"noopener">CVE-2026-4522</a></td>
    </tr>

    <td class=3D"vendor-product">IBM--WebSphere Application Server</td>
    <td>IBM WebSphere Application Server 8.5 and 9.0=C2=A0could allow a remote = attacker to bypass authentication and gain unauthorized access to JAX-WS ap= plications.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10845" target=3D= "_blank" rel=3D"noopener">CVE-2026-10845</a></td>
    </tr>

    <td class=3D"vendor-product">ImageMagick--ImageMagick</td>
    <td>ImageMagick before 7.1.2-15 and 6.9.13-40 contains a memory leak in cod= ers/txt.c when processing TXT files with texture attributes: the texture ob= ject allocated via ReadImage is not released when GetTypeMetrics fails, lea= king memory each time a crafted TXT file with a texture attribute is proces= sed.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56371" target=3D= "_blank" rel=3D"noopener">CVE-2026-56371</a></td>
    </tr>

    <td class=3D"vendor-product">ImageMagick--ImageMagick</td>
    <td>ImageMagick before 7.1.2-15 and 6.9.13-40 contains a command injection = vulnerability in the SVG decoder that allows attackers to inject arbitrary = MVG drawing commands. Attackers can craft malicious SVG files with injected=
    Magick Vector Graphics commands that execute during rendering.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56379" target=3D= "_blank" rel=3D"noopener">CVE-2026-56379</a></td>
    </tr>

    <td class=3D"vendor-product">Imagination Technologies--Graphics DDK</td>
    <td>A web page that contains unusual GPU shader code is loaded into the GPU=
    compiler process and can trigger a write out-of-bounds write crash in the = GPU shader compiler library. On certain platforms, when the compiler proces=
    s has system privileges this could enable further exploits on the device. A=
    n edge case using a very small value in GPU shader code can cause a segment= ation fault in the GPU shader compiler due to am out-of-bounds write.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-21734" target=3D= "_blank" rel=3D"noopener">CVE-2026-21734</a></td>
    </tr>

    <td class=3D"vendor-product">Imagination Technologies--Graphics DDK</td> <td>Kernel software installed and running inside a Host VM may post imprope=
    r commands to the GPU Firmware to trigger a memory read or write outside th=
    e permitted range of memory for the host kernel. Addresses passed to the GP=
    U Firmware can be used by the Firmware for more privileged memory accesses = than are permitted by the system.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45195" target=3D= "_blank" rel=3D"noopener">CVE-2026-45195</a></td>
    </tr>

    <td class=3D"vendor-product">isaacs--node-tar</td>
    <td>node-tar is a full-featured Tar for Node.js. Prior to 7.5.16, tar (node= -tar) applies a PAX extended header's size=3D record (and other PAX overrid= es) to the next header entry of any type, including intermediary metadata h= eaders such as a GNU long-name (L) or long-link (K) entry. Per POSIX pax, a=
    PAX extended header (x) describes the next file entry, not the intermediar=
    y extension headers that may sit between the x header and the file it annot= ates. Because node-tar lets the PAX size override the byte length of an int= ervening L/K/x header, an attacker can desynchronize node-tar's stream curs=
    or relative to every other mainstream tar implementation (GNU tar, libarchi= ve/bsdtar, Python tarfile, and the now-fixed tar-rs / astral-tokio-tar). Th=
    e result is a tar parser interpretation differential (CWE-436): a single cr= afted archive yields a different set of members under node-tar than under t=
    he reference tar tools. An attacker can use this to hide a member from one = parser while it is visible to another, which defeats security tooling whose=
    scanner and extractor disagree on archive contents (e.g. a malware/secret = scanner that lists entries with one library while a downstream step extract=
    s with another) This vulnerability is fixed in 7.5.16.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53655" target=3D= "_blank" rel=3D"noopener">CVE-2026-53655</a></td>
    </tr>

    <td class=3D"vendor-product">JASEI--Net::Statsite::Client</td> <td>Net::Statsite::Client versions through 1.1.0 for Perl allow metric inje= ctions. Net::Statsite::Client is a client for the statsite protocol, which =
    is a variant of statsd. Newlines are not removed from metric names, allowin=
    g metric injections. Values are not sanitised for newlines or other protoco=
    l control characters such as colons or pipes, allowing metric injections.</=

    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11373" target=3D= "_blank" rel=3D"noopener">CVE-2026-11373</a></td>
    </tr>

    <td class=3D"vendor-product">jellyfin--jellyfin</td>
    <td>Jellyfin is an open source self hosted media server. Prior to 10.11.10,=
    a specifically crafted MKV file containing forged filename tags can be lev= eraged to exploit missing path sanitization during playback. Jellyfin treat=
    s the MKV file name tag on MKV attachments as trusted and passes it unsanit= ized into Path.Combine(attachmentFolder, fileName) inside PathManager.GetAt= tachmentPath. Because .NET's Path.Combine neither normalises .. nor rejects=
    a rooted second argument, a crafted MKV can redirect Jellyfin's MKV attach= ment extraction to any absolute path on disk. This triggers on any playback=
    action of the affected video on a client which will attempt to burn in the=
    subtitles by default.g This vulnerability is fixed in 10.11.10.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49246" target=3D= "_blank" rel=3D"noopener">CVE-2026-49246</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Active Directory Plug= in</td>
    <td>Jenkins Active Directory Plugin 2.41.1 and earlier does not escape the = user name before building the LDAP search filter in the Windows native (ADS=
    I) authentication path, allowing unauthenticated attackers to inject LDAP w= ildcard characters to enumerate directory entries and to authenticate as a = matching user whose password they know without knowing their exact user nam= e.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57288" target=3D= "_blank" rel=3D"noopener">CVE-2026-57288</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Assembla Plugin</td> <td>Jenkins Assembla Plugin 1.4 and earlier does not configure its XML pars=
    er to prevent XML external entity (XXE) attacks, allowing attackers able to=
    control the responses of the configured Assembla server to extract secrets=
    from the Jenkins controller or perform server-side request forgery.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57303" target=3D= "_blank" rel=3D"noopener">CVE-2026-57303</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Assembla Plugin</td> <td>A missing permission check in Jenkins Assembla Plugin 1.4 and earlier a= llows attackers with Overall/Read permission to connect to an attacker-spec= ified URL using an attacker-specified username and password.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57304" target=3D= "_blank" rel=3D"noopener">CVE-2026-57304</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Assembla Plugin</td> <td>A cross-site request forgery (CSRF) vulnerability in Jenkins Assembla P= lugin 1.4 and earlier allows attackers to connect to an attacker-specified = URL using an attacker-specified username and password.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57305" target=3D= "_blank" rel=3D"noopener">CVE-2026-57305</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Bitbucket Push and Pu=
    ll Request Plugin</td>
    <td>Jenkins Bitbucket Push and Pull Request Plugin 3.3.8 and earlier uncond= itionally disables SSL/TLS certificate and hostname validation for connecti= ons sending Bearer token authenticated requests to the configured Bitbucket=
    Server endpoint, allowing attackers able to intercept network traffic to c= apture the token.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57289" target=3D= "_blank" rel=3D"noopener">CVE-2026-57289</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Contrast Continuous A= pplication Security Plugin</td>
    <td>A missing permission check in Jenkins Contrast Continuous Application S= ecurity Plugin 3.11 and earlier allows attackers with Overall/Read permissi=
    on to connect to an attacker-specified URL using an attacker-specified user= name, API key, and service key.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57297" target=3D= "_blank" rel=3D"noopener">CVE-2026-57297</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Contrast Continuous A= pplication Security Plugin</td>
    <td>A cross-site request forgery (CSRF) vulnerability in Jenkins Contrast C= ontinuous Application Security Plugin 3.11 and earlier allows attackers to = have Jenkins connect to an attacker-specified URL using an attacker-specifi=
    ed username, API key, and service key.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57298" target=3D= "_blank" rel=3D"noopener">CVE-2026-57298</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Contrast Continuous A= pplication Security Plugin</td>
    <td>Missing permission checks in Jenkins Contrast Continuous Application Se= curity Plugin 3.11 and earlier allow attackers with Overall/Read permission=
    to enumerate the names of configured Contrast metadata.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57299" target=3D= "_blank" rel=3D"noopener">CVE-2026-57299</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins EC2 Fleet Plugin</td> <td>A missing permission check in Jenkins EC2 Fleet Plugin 4.2.3.539.v8fedf= f2a_81c3 and earlier allows attackers with Overall/Read permission to conne=
    ct to an attacker-specified URL using attacker-specified credentials IDs ob= tained through another method, capturing AWS credentials stored in Jenkins.= </td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57294" target=3D= "_blank" rel=3D"noopener">CVE-2026-57294</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins EC2 Fleet Plugin</td> <td>A cross-site request forgery (CSRF) vulnerability in Jenkins EC2 Fleet = Plugin 4.2.3.539.v8fedff2a_81c3 and earlier allows attackers to connect to =
    an attacker-specified URL using attacker-specified credentials IDs obtained=
    through another method, capturing AWS credentials stored in Jenkins.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57295" target=3D= "_blank" rel=3D"noopener">CVE-2026-57295</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins External Workspace Ma= nager Plugin</td>
    <td>Jenkins External Workspace Manager Plugin 1.3.2 and earlier does not re= ject path traversal sequences in the custom workspace path provided to the = exwsAllocate Pipeline step, allowing attackers with Item/Configure permissi=
    on to read arbitrary files on the Jenkins controller file system, which can=
    lead to remote code execution.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57296" target=3D= "_blank" rel=3D"noopener">CVE-2026-57296</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins FitNesse Plugin</td> <td>Jenkins FitNesse Plugin 1.36 and earlier stores passwords unencrypted i=
    n job config.xml files on the Jenkins controller, where they can be viewed =
    by users with Extended Read permission or access to the Jenkins controller = file system.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57302" target=3D= "_blank" rel=3D"noopener">CVE-2026-57302</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Git client Plugin</td=

    <td>Jenkins Git client Plugin 6.6.0 and earlier does not correctly escape t=
    he workspace directory name when it is embedded into a generated SSH wrappe=
    r script, allowing attackers able to control the name of a build's working = directory to execute arbitrary operating system commands on the agent.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57282" target=3D= "_blank" rel=3D"noopener">CVE-2026-57282</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Git Parameter Plugin<=

    <td>A missing permission check in Jenkins Git Parameter Plugin 462.vdcf3df2= ed2ca_ and earlier allows attackers with Item/Read permission to obtain inf= ormation about the SCM repository used by a job, such as branch names, tag = names, and revision metadata.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57286" target=3D= "_blank" rel=3D"noopener">CVE-2026-57286</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Gitee Plugin</td> <td>Missing permission checks in Jenkins Gitee Plugin 1288.v18b_deb_c9069b_=
    and earlier allow attackers with Overall/Read permission to connect to an = attacker-specified URL using attacker-specified credentials IDs obtained th= rough another method.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57291" target=3D= "_blank" rel=3D"noopener">CVE-2026-57291</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Gitee Plugin</td>
    <td>A cross-site request forgery (CSRF) vulnerability in Jenkins Gitee Plug=
    in 1288.v18b_deb_c9069b_ and earlier allows attackers to connect to an atta= cker-specified URL using attacker-specified credentials IDs obtained throug=
    h another method.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57292" target=3D= "_blank" rel=3D"noopener">CVE-2026-57292</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Gitee Plugin</td>
    <td>An incorrect permission check in Jenkins Gitee Plugin 1288.v18b_deb_c90= 69b_ and earlier allows attackers with global Item/Configure permission (wh= ile lacking Item/Configure permission on any particular job) to enumerate c= redentials IDs of credentials stored in Jenkins.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57293" target=3D= "_blank" rel=3D"noopener">CVE-2026-57293</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins GitHub Branch Source = Plugin</td>
    <td>A missing permission check in Jenkins GitHub Branch Source Plugin 1967.= 1969.v205fd594c821 and earlier allows attackers with Overall/Read permissio=
    n to obtain the URLs of GitHub Enterprise servers configured in the global = plugin configuration.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57285" target=3D= "_blank" rel=3D"noopener">CVE-2026-57285</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Job Configuration His= tory Plugin</td>
    <td>Jenkins Job Configuration History Plugin 1356.ve360da_6c523a_ and earli=
    er does not redact the encrypted values of secrets when displaying historic=
    al job and agent configurations, allowing attackers with Extended Read perm= ission to view encrypted secret values that would otherwise be redacted.</t=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57287" target=3D= "_blank" rel=3D"noopener">CVE-2026-57287</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins MCP Server Plugin</td=

    <td>A missing permission check in Jenkins MCP Server Plugin 0.177.v629fdb_2= 557fe and earlier allows attackers with Item/Read permission to read the Pi= peline replay scripts of jobs they can access.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57300" target=3D= "_blank" rel=3D"noopener">CVE-2026-57300</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins OWASP ZAP Plugin</td> <td>Jenkins OWASP ZAP Plugin 1.0.7 and earlier performs build operations on=
    the Jenkins controller rather than the assigned agent, allowing attackers = with Item/Configure permission to execute arbitrary code on the Jenkins con= troller.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57301" target=3D= "_blank" rel=3D"noopener">CVE-2026-57301</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Pipeline: Groovy Plug= in</td>
    <td>A cross-site request forgery (CSRF) vulnerability in Jenkins Pipeline: = Groovy Plugin 4331.v9d06ed4658ff and earlier allows attackers to instantiat=
    e types related to job or system configuration other than Pipeline steps th= rough the Pipeline Snippet Generator.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57283" target=3D= "_blank" rel=3D"noopener">CVE-2026-57283</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Pipeline: Groovy Plug= in</td>
    <td>Jenkins Pipeline: Groovy Plugin 4331.v9d06ed4658ff and earlier does not=
    restrict the types that can be instantiated through the Pipeline Snippet G= enerator, allowing attackers to instantiate types related to job or system = configuration other than Pipeline steps.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57284" target=3D= "_blank" rel=3D"noopener">CVE-2026-57284</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Priority Sorter Plugi= n</td>
    <td>A cross-site request forgery (CSRF) vulnerability in Jenkins Priority S= orter Plugin 936.v2c01c6b_84449 and earlier allows attackers to overwrite t=
    he global job priority configuration.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57290" target=3D= "_blank" rel=3D"noopener">CVE-2026-57290</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Script Security Plugi= n</td>
    <td>Jenkins Script Security Plugin 1402.v94c9ce464861 and earlier does not = intercept the implicit type casts applied to the elements of typed for-each=
    loops in sandboxed Groovy scripts, allowing attackers able to provide such=
    scripts to invoke arbitrary constructors and bypass the sandbox protection= .</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57280" target=3D= "_blank" rel=3D"noopener">CVE-2026-57280</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Script Security Plugi= n</td>
    <td>Jenkins Script Security Plugin 1402.v94c9ce464861 and earlier does not = reject Groovy AST transformation annotations carrying an extensions member,=
    allowing attackers able to run sandboxed Groovy scripts to execute code ou= tside the sandbox if a suitable script is present on the classpath of the c= omponent that evaluates the script.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57281" target=3D= "_blank" rel=3D"noopener">CVE-2026-57281</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Zowe zDevOps Plugin</=

    <td>A cross-site request forgery (CSRF) vulnerability in Jenkins Zowe zDevO=
    ps Plugin 1.1.3.50.ve350c9b_450b_1 and earlier allows attackers to connect =
    to an attacker-specified URL using attacker-specified credentials IDs obtai= ned through another method, capturing credentials stored in Jenkins.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57306" target=3D= "_blank" rel=3D"noopener">CVE-2026-57306</a></td>
    </tr>

    <td class=3D"vendor-product">Jenkins Project--Jenkins Zowe zDevOps Plugin</=

    <td>A missing permission check in Jenkins Zowe zDevOps Plugin 1.1.3.50.ve35= 0c9b_450b_1 and earlier allows attackers with Overall/Read permission to co= nnect to an attacker-specified URL using attacker-specified credentials IDs=
    obtained through another method, capturing credentials stored in Jenkins.<=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57307" target=3D= "_blank" rel=3D"noopener">CVE-2026-57307</a></td>
    </tr>

    <td class=3D"vendor-product">joomcoder.com--JoomCCK extension for Joomla</t=

    <td>The Joomla extension JoomCCK exposes a front-end controller task, that = builds two SQL statements by directly concatenating a user-supplied request=
    parameter into the query string without escaping or parameterisation.</td> <td>2026-06-28</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49048" target=3D= "_blank" rel=3D"noopener">CVE-2026-49048</a></td>
    </tr>

    <td class=3D"vendor-product">jqlang--jq</td>
    <td>jq is a command-line JSON processor. Prior to 1.8.2, comparing two suff= iciently deeply nested arrays with the =3D=3D operator exhausts the C stack=
    on jq's ordinary command-line surface, resulting in denial of service via = stack exhaustion (uncontrolled recursion). The crash occurs in jq's recursi=
    ve structural comparison code, with the recursion repeating through jvp_arr= ay_equal() and jv_equal() in src/jv.c when comparing deeply nested arrays; =
    a nearby sort comparator path through jv_cmp() in src/jv_aux.c overflows th=
    e stack at a larger nesting depth from the same missing recursion guard. An= yone running jq comparisons on attacker-controlled deeply nested JSON value=
    s, or embedding jq in a context where untrusted data can reach the =3D=3D c= omparison path, is affected. This vulnerability is fixed in 1.8.2.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47770" target=3D= "_blank" rel=3D"noopener">CVE-2026-47770</a></td>
    </tr>

    <td class=3D"vendor-product">jqlang--jq</td>
    <td>jq is a command-line JSON processor. Prior to 1.8.2, on 32bit system, j= vp_string_append has a chance of integer/multiple overflowing and then caus= ing a massive buffer overrun. This vulnerability is fixed in 1.8.2.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54679" target=3D= "_blank" rel=3D"noopener">CVE-2026-54679</a></td>
    </tr>

    <td class=3D"vendor-product">jupyter--jupyter/jupyter</td>
    <td>A vulnerability in jupyter/nbconvert versions &lt;=3D 7.17.0 allows for=
    Cross-site Scripting (XSS) via unsanitized `text/vnd.mermaid` output in HT=
    ML exports. The `data_mermaid` block in `share/templates/lab/base.html.j2` = renders `text/vnd.mermaid` cell output directly into HTML without escaping,=
    enabling attackers to inject arbitrary HTML/JavaScript by breaking out of = the `&lt;pre&gt;` tag. This vulnerability impacts any server using nbconver=
    t to render notebooks as HTML, allowing attackers to execute arbitrary Java= Script in the context of users viewing the HTML export.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6658" target=3D"= _blank" rel=3D"noopener">CVE-2026-6658</a></td>
    </tr>

    <td class=3D"vendor-product">jupyter-server--jupyter_server</td>
    <td>Jupyter Server is the backend for Jupyter web applications. Prior to 2.= 20, the nbconvert HTTP handlers in jupyter_server render user-authored note= book HTML under the Jupyter origin without a sandbox directive in their Con= tent-Security-Policy. Combined with nbconvert.HTMLExporter's default non-sa= nitizing behavior, a notebook carrying an HTML payload in a display_data ou= tput triggers stored XSS with cookie access, full /api/* authority, and ker= nel RCE. This vulnerability is fixed in 2.20.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44727" target=3D= "_blank" rel=3D"noopener">CVE-2026-44727</a></td>
    </tr>

    <td class=3D"vendor-product">keras-team--keras-team/keras</td>
    <td>A path traversal vulnerability exists in keras-team/keras version 3.14.=
    0, specifically in the `DiskIOStore.make` method within the Keras 3 model s= aving and loading library. This vulnerability arises from the improper hand= ling of user-provided layer names, which are used to construct directory pa= ths without sanitizing for parent directory components (`..`). While forwar=
    d slashes (`/`) are restricted in layer names, directory traversal sequence=
    s are not. This allows an attacker to craft a malicious Keras model that, w= hen saved or loaded, can escape the intended temporary working directory an=
    d perform unauthorized file system operations, such as creating directories=
    or writing files in arbitrary locations.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12479" target=3D= "_blank" rel=3D"noopener">CVE-2026-12479</a></td>
    </tr>

    <td class=3D"vendor-product">Koha--Library Management System</td> <td>Cross-Site Scripting (XSS) vulnerability in the patron restriction type=
    administration page of Koha Library Management System through 25.11 allows=
    an authenticated remote attacker with administrator privileges to inject a= rbitrary web scripts via the restriction type label (display_text field)</t=

    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50765" target=3D= "_blank" rel=3D"noopener">CVE-2026-50765</a></td>
    </tr>

    <td class=3D"vendor-product">Koha--Library Management System</td>
    <td>A stored cross-site scripting (XSS) vulnerability in the OPAC item deta=
    il page of Koha Library Management System through 25.11 allows an authentic= ated remote attacker with edit_items permission to inject arbitrary web scr= ipts via the item public notes field (items.itemnotes).</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50766" target=3D= "_blank" rel=3D"noopener">CVE-2026-50766</a></td>
    </tr>

    <td class=3D"vendor-product">Koha--Library Management System</td>
    <td>A stored cross-site scripting (XSS) vulnerability in the item type admi= nistration page of Koha Library Management System through 25.11 allows an a= uthenticated remote attacker with administrator privileges to inject arbitr= ary web scripts via the item type check-in message field (checkinmsg)</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50767" target=3D= "_blank" rel=3D"noopener">CVE-2026-50767</a></td>
    </tr>

    <td class=3D"vendor-product">Lansweeper--lsrunase 2.0/lsencrypt 2.0</td> <td>Lansweeper lsrunase 2.0 and lsencrypt 2.0 use RC4 encryption with a har= dcoded 142-byte static key array to encrypt credentials. An 8-character pre= fix is stored in cleartext alongside the ciphertext. This allows an attacke=
    r with local access to recover any encrypted password to plaintext using a = single SHA-1 hash and RC4 decryption operation, with no brute force require= d.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39031" target=3D= "_blank" rel=3D"noopener">CVE-2026-39031</a></td>
    </tr>

    <td class=3D"vendor-product">lepture--mistune</td>
    <td>Mistune is a Python Markdown parser with renderers and plugins. Prior t=
    o 3.3.0, Mistune is vulnerable to a CPU exhaustion DoS due to superlinear (= approximately O(n=C3=82=C2=B2)) behavior in parse_link_text. When parsing M= arkdown containing many consecutive [ characters, parse_link_text repeatedl=
    y scans the input using a regex search inside a loop. Each iteration re-sca=
    ns a large portion of the remaining string, resulting in quadratic-time beh= avior. An attacker-controlled Markdown input can therefore trigger excessiv=
    e CPU usage with a very small payload. This vulnerability is fixed in 3.3.0= .</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49851" target=3D= "_blank" rel=3D"noopener">CVE-2026-49851</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bat= man-adv: v: stop OGMv2 on disabled interface When a batadv_hard_iface is di= sabled, its mesh_iface pointer is set to NULL. However, batadv_v_ogm_send_m= eshif() may still dispatch OGMs via batadv_v_ogm_queue_on_if() for interfac=
    es that have since lost their mesh_iface association. This results in a NUL=
    L pointer dereference when batadv_v_ogm_queue_on_if() unconditionally calls=
    netdev_priv() on the now NULL hard_iface-&gt;mesh_iface to retrieve the ba= tadv_priv. It is necessary to ensure that the batadv_v_ogm_queue_on_if() ch= ecks that it is using the same mesh_iface for which batadv_v_ogm_send_meshi= f() was called.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52913" target=3D= "_blank" rel=3D"noopener">CVE-2026-52913</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bat= man-adv: frag: disallow unicast fragment in fragment batadv_frag_skb_buffer=
    () is called by batadv_batman_skb_recv() when a BATADV_UNICAST_FRAG packet =
    is received. Once all fragments are collected and the packet is reassembled=
    , batadv_recv_frag_packet() calls batadv_batman_skb_recv() again to process=
    the defragmented payload. A malicious sender can craft a BATADV_UNICAST_FR=
    AG packet whose reassembled payload is itself a BATADV_UNICAST_FRAG packet = (matryoshka-style nesting). Each nesting level recurses through batadv_batm= an_skb_recv() without bound, growing the kernel stack until it is exhausted=
    . Since refragmentation or fragments in fragments are not actually allowed,=
    discard all packets which are still BATADV_UNICAST_FRAG packets after the = defragmentation process.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52916" target=3D= "_blank" rel=3D"noopener">CVE-2026-52916</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: ipset: stop hash:* range iteration at end The following hash set va= riants: hash:ip,mark hash:ip,port hash:ip,port,ip hash:ip,port,net iterate = IPv4 ranges with a 32-bit iterator. The iterator must stop once the last ad= dress in the requested range has been processed. Advancing it once more can=
    move the traversal state past the end of the request, so a later retry may=
    continue from an unintended position. Handle the iterator increment explic= itly at the end of the loop and stop once the upper bound has been processe=
    d. This keeps the existing retry behaviour intact for valid ranges while pr= eventing traversal from continuing past the original boundary.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52921" target=3D= "_blank" rel=3D"noopener">CVE-2026-52921</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: vrf=
    : Fix a potential NPD when removing a port from a VRF RCU readers that iden= tified a net device as a VRF port using netif_is_l3_slave() assume that a s= ubsequent call to netdev_master_upper_dev_get_rcu() will return a VRF devic=
    e. They then continue to dereference its l3mdev operations. This assumption=
    is not always correct and can result in a NPD [1]. There is no RCU synchro= nization when removing a port from a VRF, so it is possible for an RCU read=
    er to see a new master device (e.g., a bridge) that does not have l3mdev op= erations. Fix by adding RCU synchronization after clearing the IFF_L3MDEV_S= LAVE flag. Skip this synchronization when a net device is removed from a VR=
    F as part of its deletion and when the VRF device itself is deleted. In the=
    latter case an RCU grace period will pass by the time RTNL is released. [1=
    ] BUG: kernel NULL pointer dereference, address: 0000000000000000 [...] RIP=
    : 0010:l3mdev_fib_table_rcu (net/l3mdev/l3mdev.c:181) [...] Call Trace: &lt= ;TASK&gt; l3mdev_fib_table_by_index (net/l3mdev/l3mdev.c:201 net/l3mdev/l3m= dev.c:189) __inet_bind (net/ipv4/af_inet.c:499 (discriminator 3)) inet_bind= _sk (net/ipv4/af_inet.c:469) __sys_bind (./include/linux/file.h:62 (discrim= inator 1) ./include/linux/file.h:83 (discriminator 1) net/socket.c:1951 (di= scriminator 1)) __x64_sys_bind (net/socket.c:1969 (discriminator 1) net/soc= ket.c:1967 (discriminator 1) net/socket.c:1967 (discriminator 1)) do_syscal= l_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/sysca= ll_64.c:94 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entr= y/entry_64.S:130)</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52925" target=3D= "_blank" rel=3D"noopener">CVE-2026-52925</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bat= man-adv: clear current gateway during teardown batadv_gw_node_free() remove=
    s the gateway list entries during mesh teardown, but it does not clear the = currently selected gateway. This leaves stale gateway state behind across c= leanup and can break a later mesh recreation. Clear bat_priv-&gt;gw.curr_gw=
    before walking the gateway list so the selected gateway reference is dropp=
    ed as part of teardown.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52926" target=3D= "_blank" rel=3D"noopener">CVE-2026-52926</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: af_= unix: Reject SIOCATMARK on non-stream sockets SIOCATMARK reports whether th=
    e receive queue is at the urgent mark for MSG_OOB. In AF_UNIX, MSG_OOB is s= upported only for SOCK_STREAM sockets. SOCK_DGRAM and SOCK_SEQPACKET reject=
    MSG_OOB in sendmsg() and recvmsg(), so they should not support SIOCATMARK = either. Return -EOPNOTSUPP for non-stream sockets before checking the recei=
    ve queue.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52928" target=3D= "_blank" rel=3D"noopener">CVE-2026-52928</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ipc= /shm: serialize orphan cleanup with shm_nattch updates shm_destroy_orphaned=
    () walks the shm idr under shm_ids(ns).rwsem, but that does not serialize a=
    ll fields tested by shm_may_destroy(). In particular, shm_nattch is updated=
    while holding shm_perm.lock, and attach paths can do that without holding = the rwsem. Do not decide that an orphaned segment is unused before taking t=
    he object lock. Move the shm_may_destroy() check under shm_perm.lock, match= ing the other destroy paths, and unlock the segment when it no longer quali= fies for removal.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52930" target=3D= "_blank" rel=3D"noopener">CVE-2026-52930</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: cry= pto: jitterentropy - replace long-held spinlock with mutex jent_kcapi_rando= m() serializes the shared jitterentropy state, but it currently holds a spi= nlock across the jent_read_entropy() call. That path performs expensive jit= ter collection and SHA3 conditioning, so parallel readers can trigger stall=
    s as contending waiters spin for the same lock. To prevent non-preemptible = lock hold, replace rng-&gt;jent_lock with a mutex so contended readers slee=
    p instead of spinning on a shared lock held across expensive entropy genera= tion.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52936" target=3D= "_blank" rel=3D"noopener">CVE-2026-52936</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: tap=
    : fix stack info leak in tap_ioctl() SIOCGIFHWADDR In the SIOCGIFHWADDR pat=
    h, tap_ioctl() copies 16 bytes of an uninitialised on-stack struct sockaddr= _storage to userspace via ifr_hwaddr, but netif_get_mac_address() only writ=
    es sa_family and dev-&gt;addr_len (6 for Ethernet) bytes, leaving sa_data[6= ..13] uninitialised. Those 8 trailing bytes leak kernel stack contents; SIO= CGIFHWADDR on a macvtap chardev returns kernel .text and direct-map pointer=
    s, defeating KASLR. Initialise ss at declaration.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52937" target=3D= "_blank" rel=3D"noopener">CVE-2026-52937</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix NULL pointer dereference in bpf_sk_storage_clone and diag paths bpf_s= elem_unlink_nofail() sets SDATA(selem)-&gt;smap to NULL before removing the=
    selem from the storage hlist. A concurrent RCU reader in bpf_sk_storage_cl= one() can observe the selem still on the list with smap already NULL, causi=
    ng a NULL pointer dereference. general protection fault, probably for non-c= anonical address 0xdffffc000000000a: KASAN: null-ptr-deref in range [0x0000= 000000000050-0x0000000000000057] RIP: 0010:bpf_sk_storage_clone+0x1cd/0xaa0=
    net/core/bpf_sk_storage.c:174 Call Trace: &lt;IRQ&gt; sk_clone+0xfed/0x198=
    0 net/core/sock.c:2591 inet_csk_clone_lock+0x30/0x760 net/ipv4/inet_connect= ion_sock.c:1222 tcp_create_openreq_child+0x35/0x2680 net/ipv4/tcp_minisocks= .c:571 tcp_v4_syn_recv_sock+0x123/0xf90 net/ipv4/tcp_ipv4.c:1729 tcp_check_= req+0x8e1/0x2580 include/net/tcp.h:855 tcp_v4_rcv+0x1845/0x3b80 net/ipv4/tc= p_ipv4.c:2347 Add a NULL check for smap in bpf_sk_storage_clone(). bpf_sk_s= torage_diag_put_all() has the same issue. Add a NULL check and pass the val= idated smap directly to diag_get(), which is refactored to take smap as a p= arameter instead of reading it internally. bpf_sk_storage_diag_put() uses d= iag-&gt;maps[i] which is always valid under its refcount, so diag-&gt;maps[=
    i] is passed directly to diag_get().</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52938" target=3D= "_blank" rel=3D"noopener">CVE-2026-52938</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /rds: fix NULL deref in rds_ib_send_cqe_handler() on masked atomic completi=
    on rds_ib_xmit_atomic() always programs a masked atomic opcode (IB_WR_MASKE= D_ATOMIC_CMP_AND_SWP or IB_WR_MASKED_ATOMIC_FETCH_AND_ADD) for every RDS at= omic cmsg. But the completion-side switch in rds_ib_send_unmap_op() only ha= ndles the non-masked opcodes, so a masked atomic completion falls through t=
    o default and returns rm =3D=3D NULL while send-&gt;s_op is left set. rds_i= b_send_cqe_handler() then dereferences the NULL rm via rm-&gt;m_final_op, o= opsing in softirq context. An unprivileged AF_RDS sendmsg() of an atomic cm=
    sg over an active RDS/IB connection triggers it; on hardware that natively = accepts masked atomics (mlx4, mlx5) no extra setup is needed. RDS/IB: rds_i= b_send_unmap_op: unexpected opcode 0xd in WR! Oops: general protection faul=
    t [#1] SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000190-0x00000= 00000000197] RIP: rds_ib_send_cqe_handler+0x25c/0xb10 (net/rds/ib_send.c:28=
    2) Call Trace: &lt;IRQ&gt; rds_ib_send_cqe_handler (net/rds/ib_send.c:282) = poll_scq (net/rds/ib_cm.c:274) rds_ib_tasklet_fn_send (net/rds/ib_cm.c:294)=
    tasklet_action_common (kernel/softirq.c:943) handle_softirqs (kernel/softi= rq.c:573) run_ksoftirqd (kernel/softirq.c:479) &lt;/IRQ&gt; Kernel panic - = not syncing: Fatal exception in interrupt Handle the masked atomic opcodes =
    in the same case as the non-masked ones: they map to the same struct rds_me= ssage.atomic union member, so the existing container_of()/rds_ib_send_unmap= _atomic() body is correct for them.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52939" target=3D= "_blank" rel=3D"noopener">CVE-2026-52939</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: tun=
    : zero the whole vnet header in tun_put_user() tun_put_user() declares an o= n-stack struct virtio_net_hdr_v1_hash_tunnel without zeroing it. For a non-= tunnel skb, virtio_net_hdr_tnl_from_skb() only initializes the first 10 byt=
    es (sizeof(struct virtio_net_hdr)), leaving bytes 10..23 (num_buffers and t=
    he hash/tunnel fields) as stack garbage. An unprivileged user can set the v= net header size to 24 with TUNSETVNETHDRSZ, so __tun_vnet_hdr_put() copies = all 24 bytes of the partially-initialized struct to userspace, leaking 14 b= ytes of kernel stack on every read of a non-tunnel packet. Fix it the same = way tun_get_user() already does by zeroing the whole header right after dec= laration.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52940" target=3D= "_blank" rel=3D"noopener">CVE-2026-52940</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /smc: avoid NULL deref of conn-&gt;lnk in smc_msg_event tracepoint The smc_= msg_event tracepoint class, shared by smc_tx_sendmsg and smc_rx_recvmsg, un= conditionally dereferences smc-&gt;conn.lnk: __string(name, smc-&gt;conn.ln= k-&gt;ibname) conn-&gt;lnk is only set for SMC-R; for SMC-D it is NULL. Oth=
    er code on these paths already handles this (e.g. !conn-&gt;lnk in SMC_STAT= _RMB_TX_SIZE_SMALL()). With the tracepoint enabled, the first sendmsg()/rec= vmsg() on an SMC-D socket crashes: Oops: general protection fault, probably=
    for non-canonical address KASAN: null-ptr-deref in range [...] RIP: 0010:s= trlen+0x1e/0xa0 Call Trace: trace_event_raw_event_smc_msg_event (net/smc/sm= c_tracepoint.h:44) smc_rx_recvmsg (net/smc/smc_rx.c:515) smc_recvmsg (net/s= mc/af_smc.c:2859) __sys_recvfrom (net/socket.c:2315) __x64_sys_recvfrom (ne= t/socket.c:2326) do_syscall_64 The faulting address 0x3e0 is offsetof(struc=
    t smc_link, ibname), confirming the NULL -&gt;lnk deref. Enabling the trace= point requires root, but the trigger itself is unprivileged: socket(AF_SMC,=
    ...) has no capability check, and SMC-D negotiation needs no admin step on=
    s390 or on x86 with the loopback ISM device loaded. Log an empty device na=
    me for SMC-D instead of dereferencing NULL.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52941" target=3D= "_blank" rel=3D"noopener">CVE-2026-52941</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ksm= bd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_= SPARSE FSCTL_SET_SPARSE in fsctl_set_sparse() modifies the file's sparse at= tribute and saves it through xattr without any permission checks. This expo= ses two issues: 1) A client on a read-only share can change the sparse attr= ibute on files it opened, even though the share is read-only. Other FSCTL w= rite operations already check test_tree_conn_flag(work-&gt;tcon, KSMBD_TREE= _CONN_FLAG_WRITABLE), but FSCTL_SET_SPARSE does not. 2) Even on writable sh= ares, clients without FILE_WRITE_DATA or FILE_WRITE_ATTRIBUTES access shoul=
    d not modify the sparse attribute. Similar handle-level checks exist in oth=
    er functions but are missing here. Add both share-level writable check and = per-handle access check. Use goto out on error to avoid leaking file refere= nces.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52944" target=3D= "_blank" rel=3D"noopener">CVE-2026-52944</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: i2c=
    : dev: prevent integer overflow in I2C_TIMEOUT ioctl While fuzzing with Syz= kaller, a persistent `schedule_timeout: wrong timeout value` warning was ob= served, accompanied by SMBus controller state machine corruption. The I2C_T= IMEOUT ioctl accepts a user-provided timeout in multiples of 10 ms. The use=
    r argument is checked against INT_MAX, but it is subsequently multiplied by=
    10 before being passed to msecs_to_jiffies(). A malicious user can pass a = large value (e.g., 429496729) that passes the `arg &gt; INT_MAX` check but = overflows when multiplied by 10. This results in a truncated 32-bit unsigne=
    d value that bypasses the internal `(int)m &lt; 0` check in `msecs_to_jiffi= es()`. The truncated value is then assigned to `client-&gt;adapter-&gt;time= out` (a signed 32-bit int), which is reinterpreted as a negative number. Wh=
    en passed to wait_for_completion_timeout(), this negative value undergoes s= ign extension to a 64-bit unsigned long, triggering the `schedule_timeout` = warning and causing premature returns. This leaves the SMBus state machine =
    in an unrecoverable state, constituting a local Denial of Service (DoS). Fi=
    x this by bounding the user argument to `INT_MAX / 10`. [wsa: move the comm= ent as well]</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52948" target=3D= "_blank" rel=3D"noopener">CVE-2026-52948</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /ttm: Fix ttm_bo_shrink() infinite LRU walk on backup failure Apply the sam=
    e fix as b2ed01e7ad ("drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on sw= apout failure") to the ttm_bo_shrink() path. Move del_bulk_move from before=
    the backup to after success only, using ttm_resource_del_bulk_move_unevict= able() since the resource is now unevictable once fully backed up.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52949" target=3D= "_blank" rel=3D"noopener">CVE-2026-52949</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: cep=
    h: fix BUG_ON in __ceph_build_xattrs_blob() due to stale blob size The gene= ric/642 test-case can reproduce the kernel crash: [40243.605254] ----------= --[ cut here ]------------ [40243.605956] kernel BUG at fs/ceph/xattr.c:918=
    ! [40243.607142] Oops: invalid opcode: 0000 [#1] SMP PTI [40243.608067] CPU=
    : 7 UID: 0 PID: 498762 Comm: kworker/7:1 Not tainted 7.0.0-rc7+ #3 PREEMPT(= full) [40243.609700] Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX,=
    + 10.1 machine, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [40243.61182=
    0] Workqueue: ceph-msgr ceph_con_workfn [40243.612715] RIP: 0010:__ceph_bui= ld_xattrs_blob+0x1b8/0x1e0 [40243.613731] Code: 0f 84 82 fe ff ff e9 cf 8e =
    56 ff 48 8d 65 e8 31 c0 5b 41 5c 41 5d 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 =
    45 31 c9 c3 cc cc cc cc &lt;0f&gt; 0b 4c 8b 62 08 41 8b 85 24 07 00 00 49 8=
    3 c4 04 41 89 44 24 fc [40243.616888] RSP: 0018:ffffcc80c4d4b688 EFLAGS: 00= 010287 [40243.617773] RAX: 0000000000010026 RBX: 0000000000000001 RCX: 0000= 000000000000 [40243.618928] RDX: ffff8a773798dee0 RSI: 0000000000000000 RDI=
    : 0000000000000000 [40243.620158] RBP: ffffcc80c4d4b6a0 R08: 00000000000000=
    00 R09: 0000000000000000 [40243.621573] R10: 0000000000000000 R11: 00000000= 00000000 R12: ffff8a75f3b58000 [40243.622907] R13: ffff8a75f3b58000 R14: 00= 00000000000080 R15: 000000000000bffd [40243.624054] FS: 0000000000000000(00= 00) GS:ffff8a787d1b4000(0000) knlGS:0000000000000000 [40243.625331] CS: 001=
    0 DS: 0000 ES: 0000 CR0: 0000000080050033 [40243.626269] CR2: 000072f390b62= 3c0 CR3: 000000011c02a003 CR4: 0000000000372ef0 [40243.627408] Call Trace: = [40243.627839] &lt;TASK&gt; [40243.628188] __prep_cap+0x3fd/0x4a0 [40243.62= 8789] ? do_raw_spin_unlock+0x4e/0xe0 [40243.629474] ceph_check_caps+0x46a/0= xc80 [40243.630094] ? __lock_acquire+0x4a2/0x2650 [40243.630773] ? find_hel= d_lock+0x31/0x90 [40243.631347] ? handle_cap_grant+0x79f/0x1060 [40243.6320= 68] ? lock_release+0xd9/0x300 [40243.632696] ? __mutex_unlock_slowpath+0x3e= /0x340 [40243.633429] ? lock_release+0xd9/0x300 [40243.634052] handle_cap_g= rant+0xcf6/0x1060 [40243.634745] ceph_handle_caps+0x122b/0x2110 [40243.6354= 15] mds_dispatch+0x5bd/0x2160 [40243.636034] ? ceph_con_process_message+0x6= 5/0x190 [40243.636828] ? lock_release+0xd9/0x300 [40243.637431] ceph_con_pr= ocess_message+0x7a/0x190 [40243.638184] ? kfree+0x311/0x4f0 [40243.638749] =
    ? kfree+0x311/0x4f0 [40243.639268] process_message+0x16/0x1a0 [40243.639915=
    ] ? sg_free_table+0x39/0x90 [40243.640572] ceph_con_v2_try_read+0xf58/0x212=
    0 [40243.641255] ? lock_acquire+0xc8/0x300 [40243.641863] ceph_con_workfn+0= x151/0x820 [40243.642493] process_one_work+0x22f/0x630 [40243.643093] ? pro= cess_one_work+0x254/0x630 [40243.643770] worker_thread+0x1e2/0x400 [40243.6= 44332] ? __pfx_worker_thread+0x10/0x10 [40243.645020] kthread+0x109/0x140 [= 40243.645560] ? __pfx_kthread+0x10/0x10 [40243.646125] ret_from_fork+0x3f8/= 0x480 [40243.646752] ? __pfx_kthread+0x10/0x10 [40243.647316] ? __pfx_kthre= ad+0x10/0x10 [40243.647919] ret_from_fork_asm+0x1a/0x30 [40243.648556] &lt;= /TASK&gt; [40243.648902] Modules linked in: overlay hctr2 libpolyval chacha=
    libchacha adiantum libnh libpoly1305 essiv intel_rapl_msr intel_rapl_commo=
    n intel_uncore_frequency_common skx_edac_common nfit kvm_intel kvm irqbypas=
    s joydev ghash_clmulni_intel aesni_intel rapl input_leds mac_hid psmouse vg= a16fb serio_raw vgastate floppy i2c_piix4 pata_acpi bochs qemu_fw_cfg i2c_s= mbus sch_fq_codel rbd dm_crypt msr parport_pc ppdev lp parport efi_pstore [= 40243.654766] ---[ end trace 0000000000000000 ]--- Commit d93231a6bc8a ("ce= ph: prevent a client from exceeding the MDS maximum xattr size") moved the = required_blob_size computation to before the __build_xattrs() call, introdu= cing a race. __build_xattrs() releases and reacquires i_ceph_lock during ex= ecution. In that window, handle_cap_grant() may update i_xattrs.blob with a=
    newer MDS-provided blob and bump i_xattrs.version. When __bui ---truncated= ---</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52961" target=3D= "_blank" rel=3D"noopener">CVE-2026-52961</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: cep=
    h: fix a buffer leak in __ceph_setxattr() The old_blob in __ceph_setxattr()=
    can store ci-&gt;i_xattrs.prealloc_blob value during the retry. However, i=
    t is never called the ceph_buffer_put() for the old_blob object. This patch=
    fixes the issue of the buffer leak.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52962" target=3D= "_blank" rel=3D"noopener">CVE-2026-52962</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ALS=
    A: usb-audio: Bound MIDI endpoint descriptor scans snd_usbmidi_get_ms_info(=
    ) validates the internal MIDIStreaming endpoint descriptor size before usin=
    g baAssocJackID[], but the descriptor walker can still return a class-speci= fic endpoint descriptor whose bLength exceeds the remaining bytes in the en= dpoint-extra scan. That leaves later flexible-array reads bounded by bLengt=
    h, but not by the remaining bytes in the endpoint-extra scan. Stop walking = when bLength is zero or extends past the remaining endpoint-extra scan.</td=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52963" target=3D= "_blank" rel=3D"noopener">CVE-2026-52963</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ALS=
    A: usb-audio: Bound MIDI 2.0 endpoint descriptor scans The USB MIDI 2.0 end= point parser has the same descriptor walking pattern as the legacy MIDI par= ser. It validates bLength against bNumGrpTrmBlock before reading baAssoGrpT= rmBlkID[], but not against the remaining bytes in the endpoint-extra scan. =
    A malformed device can therefore make later baAssoGrpTrmBlkID[] reads consu=
    me bytes past the walked descriptor. Reject zero-length and overlong descri= ptors while walking endpoint extras.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52964" target=3D= "_blank" rel=3D"noopener">CVE-2026-52964</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure When ttm_tt= _swapout() fails, the current code calls ttm_resource_add_bulk_move() follo= wed by ttm_resource_move_to_lru_tail() to restore the resource's bulk_move = membership. However, ttm_resource_move_to_lru_tail() places the resource at=
    the tail of the LRU list which, relative to the walk cursor's hitch node (= placed immediately after the resource when it was yielded), puts the resour=
    ce *in front of the* the hitch. The next list_for_each_entry_continue() fro=
    m the hitch finds the same resource again, causing an infinite loop. Fix by=
    deferring del_bulk_move to the success path only. On the success path, TTM= _TT_FLAG_SWAPPED has just been set by ttm_tt_swapout() but the resource is = still tracked in the bulk_move range, so ttm_resource_del_bulk_move()'s !tt= m_resource_unevictable() guard would incorrectly skip the removal. Introduc=
    e ttm_resource_del_bulk_move_unevictable() which bypasses that guard.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52965" target=3D= "_blank" rel=3D"noopener">CVE-2026-52965</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm=
    : Replace old pointer to new idr Commit 5e28b7b94408 introduced a logical e= rror by failing to replace the newly generated IDR pointer to old id's poin= ter at the correct location within the "change handle" logic; this resulted=
    in the issue reported by syzbot [1]. Specifically, the new IDR object poin= ter is intended to replace the original id's pointer during the normal exec= ution flow. Additionally, an unnecessary conditional check for the ret exit=
    path has been removed. [1] !RB_EMPTY_ROOT(&amp;prime_fpriv-&gt;dmabufs) WA= RNING: drivers/gpu/drm/drm_prime.c:224 at drm_prime_destroy_file_private+0x= 48/0x60 drivers/gpu/drm/drm_prime.c:224, CPU#0: syz.0.17/5833 Call Trace: d= rm_file_free.part.0+0x7e6/0xcc0 drivers/gpu/drm/drm_file.c:269 drm_file_fre=
    e drivers/gpu/drm/drm_file.c:237 [inline] drm_close_helper.isra.0+0x186/0x2=
    00 drivers/gpu/drm/drm_file.c:290 drm_release+0x1ab/0x360 drivers/gpu/drm/d= rm_file.c:438</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52966" target=3D= "_blank" rel=3D"noopener">CVE-2026-52966</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: KVM=
    : s390: pci: fix GAIT table indexing due to double-scaling pointer arithmet=
    ic kvm_s390_pci_aif_enable(), kvm_s390_pci_aif_disable(), and aen_host_forw= ard() index the GAIT by manually multiplying the index with sizeof(struct z= pci_gaite). Since aift-&gt;gait is already a struct zpci_gaite pointer, thi=
    s double-scales the offset, accessing element aisb*16 instead of aisb. This=
    causes out-of-bounds accesses when aisb &gt;=3D 32 (with ZPCI_NR_DEVICES= =3D512) Fix by removing the erroneous sizeof multiplication.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52968" target=3D= "_blank" rel=3D"noopener">CVE-2026-52968</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: KVM=
    : Reject wrapped offset in kvm_reset_dirty_gfn() kvm_reset_dirty_gfn() guar=
    ds the gfn range with if (!memslot || (offset + __fls(mask)) &gt;=3D memslo= t-&gt;npages) return; but offset is u64 and the addition is unchecked. The = check can be silently bypassed by a u64 wrap. The dirty ring backing those = entries is MAP_SHARED at KVM_DIRTY_LOG_PAGE_OFFSET of the vcpu fd, so the V=
    MM can rewrite the slot and offset fields of any entry between when the ker= nel pushes them and when KVM_RESET_DIRTY_RINGS consumes them. On reset, kvm= _dirty_ring_reset() re-reads the values via READ_ONCE() and feeds them stra= ight back into this check; only the flags handshake is treated as the hando= ver, the slot/offset payload is taken on trust. Crafting two entries entry[= i].offset =3D 0xffffffffffffffc1 entry[i+1].offset =3D 0 makes the coalesci=
    ng loop in kvm_dirty_ring_reset() compute delta =3D (s64)(0 - 0xfffffffffff= fffc1) =3D 63 which falls in [0, BITS_PER_LONG), so it folds entry[i+1] int=
    o the existing mask by setting bit 63. The trailing kvm_reset_dirty_gfn() c= all then sees offset =3D 0xffffffffffffffc1 and __fls(mask) =3D 63; the sum=
    is 0 in u64 and the bounds check passes. That offset propagates into kvm_a= rch_mmu_enable_log_dirty_pt_masked() unchanged. On the legacy MMU path -- k= vm_memslots_have_rmaps() =3D=3D true, i.e. shadow paging, any VM that has a= llocated shadow roots, or a write-tracked slot -- it reaches gfn_to_rmap(),=
    which indexes slot-&gt;arch.rmap[0][] with a near-U64_MAX gfn. That is an = out-of-bounds load of a kvm_rmap_head, followed by a conditional clear of P= T_WRITABLE_MASK in whatever the loaded pointer points at. The path is reach= able from any process holding /dev/kvm. Range-check offset on its own first=
    , so the addition cannot wrap. memslot-&gt;npages is bounded well below U64= _MAX, so once offset &lt; npages holds, offset + __fls(mask) (with __fls(ma= sk) &lt; BITS_PER_LONG) stays in range.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52969" target=3D= "_blank" rel=3D"noopener">CVE-2026-52969</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nft_ct: fix missing expect put in obj eval nft_ct_expect_obj_eval()=
    allocates an expectation and may call nf_ct_expect_related(), but never dr= ops its local reference. Add nf_ct_expect_put(exp) before return to balance=
    allocation.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52970" target=3D= "_blank" rel=3D"noopener">CVE-2026-52970</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: cry= pto: af_alg - Cap AEAD AD length to 0x80000000 In order to prevent arithmet=
    ic overflows when checking the TX buffer size, cap the associated data leng=
    th to 0x80000000.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52972" target=3D= "_blank" rel=3D"noopener">CVE-2026-52972</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fut= ex: Prevent lockup in requeue-PI during signal/ timeout wakeup During wait-= requeue-pi (task A) and requeue-PI (task B) the following race can happen: = Task A Task B futex_wait_requeue_pi() futex_setup_timer() futex_do_wait() f= utex_requeue() CLASS(hb, hb1)(&amp;key1); CLASS(hb, hb2)(&amp;key2); *timeo= ut* futex_requeue_pi_wakeup_sync() requeue_state =3D Q_REQUEUE_PI_IGNORE *b= locks on hb-&gt;lock* futex_proxy_trylock_atomic() futex_requeue_pi_prepare=
    () Q_REQUEUE_PI_IGNORE =3D&gt; -EAGAIN double_unlock_hb(hb1, hb2) *retry* T= ask B acquires both hb locks and attempts to acquire the PI-lock of the top=
    most waiter (task B). Task A is leaving early due to a signal/ timeout and=
    started removing itself from the queue. It updates its requeue_state but c=
    an not remove it from the list because this requires the hb lock which is o= wned by task B. Usually task A is able to swoop the lock after task B unloc= ked it. However if task B is of higher priority then task A may not be able=
    to wake up in time and acquire the lock before task B gets it again. Espec= ially on a UP system where A is never scheduled. As a result task A blocks =
    on the lock and task B busy loops, trying to make progress but live locks t=
    he system instead. Tragic. This can be fixed by removing the top most waite=
    r from the list in this case. This allows task B to grab the next top waite=
    r (if any) in the next iteration and make progress. Remove the top most wai= ter if futex_requeue_pi_prepare() fails. Let the waiter conditionally remov=
    e itself from the list in handle_early_requeue_pi_wakeup().</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52977" target=3D= "_blank" rel=3D"noopener">CVE-2026-52977</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : psp: require admin permission for dev-set and key-rotate The dev-set and = key-rotate netlink operations modify shared device state (PSP version confi= guration and cryptographic key material, respectively) but do not require C= AP_NET_ADMIN. The only access control is psp_dev_check_access() which merel=
    y verifies netns membership.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52978" target=3D= "_blank" rel=3D"noopener">CVE-2026-52978</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : psp: check for device unregister when creating assoc psp_assoc_device_get= _locked() obtains a psp_dev reference via psp_dev_get_for_sock() (which use=
    s psp_dev_tryget() under RCU); it then acquires psd-&gt;lock and drops the = reference. Before the lock is taken, psp_dev_unregister() can run to comple= tion: take psd-&gt;lock, clear out state, unlock, drop the registration ref= erence. The expectation is that the lock prevents device unregistration, bu=
    t much like with netdevs special care has to be taken when "upgrading" a re= ference to a locked device. Add the missing check if device is still alive.=
    psp_dev_is_registered() exists already but had no callers, which makes me = wonder if I either forgot to add this or lost the check during refactoring.= ..</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52979" target=3D= "_blank" rel=3D"noopener">CVE-2026-52979</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sch= ed/fair: Clear rel_deadline when initializing forked entities A yield-trigg= ered crash can happen when a newly forked sched_entity enters the fair clas=
    s with se-&gt;rel_deadline unexpectedly set. The failing sequence is: 1. A = task is forked while se-&gt;rel_deadline is still set. 2. __sched_fork() in= itializes vruntime, vlag and other sched_entity state, but does not clear r= el_deadline. 3. On the first enqueue, enqueue_entity() calls place_entity()=
    . 4. Because se-&gt;rel_deadline is set, place_entity() treats se-&gt;deadl= ine as a relative deadline and converts it to an absolute deadline by addin=
    g the current vruntime. 5. However, the forked entity's deadline is not a v= alid inherited relative deadline for this new scheduling instance, so the c= onversion produces an abnormally large deadline. 6. If the task later calls=
    sched_yield(), yield_task_fair() advances se-&gt;vruntime to se-&gt;deadli= ne. 7. The inflated vruntime is then used by the following enqueue path, wh= ere the vruntime-derived key can overflow when multiplied by the entity wei= ght. 8. This corrupts cfs_rq-&gt;sum_w_vruntime, breaks EEVDF eligibility c= alculation, and can eventually make all entities appear ineligible. pick_ne= xt_entity() may then return NULL unexpectedly, leading to a later NULL dere= ference. A captured trace shows the effect clearly. Before yield, the entit= y's vruntime was around: 9834017729983308 After yield_task_fair() executed:=
    se-&gt;vruntime =3D se-&gt;deadline the vruntime jumped to: 19668035460670= 230 and the deadline was later advanced further to: 19668035463470230 This = shows that the deadline had already become abnormally large before yield_ta= sk_fair() copied it into vruntime. rel_deadline is only meaningful when se-= &gt;deadline really carries a relative deadline that still needs to be plac=
    ed against vruntime. A freshly forked sched_entity should not inherit or re= tain this state. Clear se-&gt;rel_deadline in __sched_fork(), together with=
    the other sched_entity runtime state, so that the first enqueue does not i= nterpret the new entity's deadline as a stale relative deadline.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52980" target=3D= "_blank" rel=3D"noopener">CVE-2026-52980</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /sched: netem: fix queue limit check to include reordered packets The queue=
    limit check in netem_enqueue() uses q-&gt;t_len which only counts packets =
    in the internal tfifo. Packets placed in sch-&gt;q by the reorder path (__q= disc_enqueue_head) are not counted, allowing the total queue occupancy to e= xceed sch-&gt;limit under reordering. Include sch-&gt;q.qlen in the limit c= heck.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52984" target=3D= "_blank" rel=3D"noopener">CVE-2026-52984</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= devsim: zero initialize struct iphdr in dummy sk_buff Syzbot reports a KMSA=
    N uninit-value originating from nsim_dev_trap_skb_build, with the allocatio=
    n also being performed in the same function. Fix this by calling skb_put_ze=
    ro instead of skb_put to guarantee zero initialization of the whole IP head= er.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52985" target=3D= "_blank" rel=3D"noopener">CVE-2026-52985</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fsn= otify: fix inode reference leak in fsnotify_recalc_mask() fsnotify_recalc_m= ask() fails to handle the return value of __fsnotify_recalc_mask(), which m=
    ay return an inode pointer that needs to be released via fsnotify_drop_obje= ct() when the connector's HAS_IREF flag transitions from set to cleared. Th=
    is manifests as a hung task with the following call trace: INFO: task umoun= t:1234 blocked for more than 120 seconds. Call Trace: __schedule schedule f= snotify_sb_delete generic_shutdown_super kill_anon_super cleanup_mnt task_w= ork_run do_exit do_group_exit The race window that triggers the iref leak: = Thread A (adding mark) Thread B (removing mark) =C3=A2=E2=80=9D=E2=82=AC=C3= =A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2= =E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2= =80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80= =9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D= =E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2= =82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82= =AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC =C3=A2=E2=80=9D=E2=82= =AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC= =C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3= =A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2= =E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2= =80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80= =9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D= =E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2=82=AC=C3=A2=E2=80=9D=E2= =82=AC=C3=A2=E2=80=9D=E2=82=AC fsnotify_add_mark_locked(): fsnotify_add_mar= k_list(): spin_lock(conn-&gt;lock) add mark_B(evictable) to list spin_unloc= k(conn-&gt;lock) return /* ---- gap: no lock held ---- */ fsnotify_detach_m= ark(mark_A): spin_lock(mark_A-&gt;lock) clear ATTACHED flag on mark_A spin_= unlock(mark_A-&gt;lock) fsnotify_put_mark(mark_A) fsnotify_recalc_mask(): s= pin_lock(conn-&gt;lock) __fsnotify_recalc_mask(): /* mark_A skipped: ATTACH=
    ED cleared */ /* only mark_B(evictable) remains */ want_iref =3D false has_= iref =3D true /* not yet cleared */ -&gt; HAS_IREF transitions true -&gt; f= alse -&gt; returns inode pointer spin_unlock(conn-&gt;lock) /* BUG: return = value discarded! * iput() and fsnotify_put_sb_watched_objects() * are never=
    called */ Fix this by deferring the transition true -&gt; false of HAS_IRE=
    F flag from fsnotify_recalc_mask() (Thread A) to fsnotify_put_mark() (threa=
    d B).</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52990" target=3D= "_blank" rel=3D"noopener">CVE-2026-52990</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fs/= adfs: validate nzones in adfs_validate_bblk() Reject ADFS disc records with=
    a zero zone count during boot block validation, before the disc record is = used. When nzones is 0, adfs_read_map() passes it to kmalloc_array(0, ...) = which returns ZERO_SIZE_PTR, and adfs_map_layout() then writes to dm[-1], c= ausing an out-of-bounds write before the allocated buffer. adfs_validate_dr= 0() already rejects nzones !=3D 1 for old-format images. Add the equivalent=
    check to adfs_validate_bblk() for new-format images so that a crafted imag=
    e with nzones =3D=3D 0 is rejected at probe time. Found by syzkaller.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52992" target=3D= "_blank" rel=3D"noopener">CVE-2026-52992</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: vso= ck/virtio: fix MSG_ZEROCOPY pinned-pages accounting virtio_transport_init_z= copy_skb() uses iter-&gt;count as the size argument for msg_zerocopy_reallo= c(), which in turn passes it to mm_account_pinned_pages() for RLIMIT_MEMLOC=
    K accounting. However, this function is called after virtio_transport_fill_= skb() has already consumed the iterator via __zerocopy_sg_from_iter(), so o=
    n the last skb, iter-&gt;count will be 0, skipping the RLIMIT_MEMLOCK enfor= cement. Pass pkt_len (the total bytes being sent) as an explicit parameter =
    to virtio_transport_init_zcopy_skb() instead of reading the already-consume=
    d iter-&gt;count. This matches TCP and UDP, which both call msg_zerocopy_re= alloc() with the original message size.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52994" target=3D= "_blank" rel=3D"noopener">CVE-2026-52994</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /rds: zero per-item info buffer before handing it to visitors rds_for_each_= conn_info() and rds_walk_conn_path_info() both hand a caller-allocated on-s= tack u64 buffer to a per-connection visitor and then copy the full item_len=
    bytes back to user space via rds_info_copy() regardless of how much of the=
    buffer the visitor actually wrote. rds_ib_conn_info_visitor() and rds6_ib_= conn_info_visitor() only write a subset of their output struct when the und= erlying rds_connection is not in state RDS_CONN_UP (src/dst addr, tos, sl a=
    nd the two GIDs via explicit memsets). Several u32 fields (max_send_wr, max= _recv_wr, max_send_sge, rdma_mr_max, rdma_mr_size, cache_allocs) and the 2-= byte alignment hole between sl and cache_allocs remain as whatever stack co= ntents preceded the visitor call and are then memcpy_to_user()'d out to use=
    r space. struct rds_info_rdma_connection and struct rds6_info_rdma_connecti=
    on are the only rds_info_* structs in include/uapi/linux/rds.h that are not=
    marked __attribute__((packed)), so they have a real alignment hole. The ot= her info visitors (rds_conn_info_visitor, rds6_conn_info_visitor, rds_tcp_t= c_info, ...) write all fields of their packed output struct today and are n=
    ot known to be vulnerable, but a future visitor that adds a conditional wri= te-path would have the same bug. Reproduction on a kernel built without CON= FIG_INIT_STACK_ALL_ZERO=3Dy: a local unprivileged user opens AF_RDS, sets S= O_RDS_TRANSPORT=3DIB, binds to a local address on an RDMA-capable netdev (r=
    xe soft-RoCE on any netdev is sufficient), sendto()'s any peer on the same = subnet (fails cleanly but installs an rds_connection in the global hash in = RDS_CONN_CONNECTING), then calls getsockopt(SOL_RDS, RDS_INFO_IB_CONNECTION= S). The returned 68-byte item contains 26 bytes of stack garbage including = kernel text/data pointers: 0..7 0a 63 00 01 0a 63 00 02 src=3D10.99.0.1 dst= =3D10.99.0.2 8..39 00 ... gids (memset-zeroed) 40..47 e0 92 a3 81 ff ff ff =
    ff kernel pointer (max_send_wr) 48..55 7f 37 b5 81 ff ff ff ff kernel point=
    er (rdma_mr_max) 56..59 01 00 08 00 rdma_mr_size (garbage) 60..61 00 00 tos=
    , sl 62..63 00 00 alignment padding 64..67 18 00 00 00 cache_allocs (garbag=
    e) Fix by zeroing the per-item buffer in both rds_for_each_conn_info() and = rds_walk_conn_path_info() before invoking the visitor. This covers the IPv4= /IPv6 IB visitors and hardens all current and future visitors against the s= ame class of bug. No functional change for visitors that fully populate the=
    ir output. Changes in v2: - retarget at the net tree (subject prefix "[PATC=
    H net v2]", net/rds: prefix in the title) - pick up Reviewed-by tags from S= harath Srinivasan and Allison Henderson</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52995" target=3D= "_blank" rel=3D"noopener">CVE-2026-52995</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ksm= bd: fix durable fd leak on ClientGUID mismatch in durable v2 open ksmbd_loo= kup_fd_cguid() returns a ksmbd_file with its refcount incremented via ksmbd= _fp_get(). parse_durable_handle_context() in the DURABLE_REQ_V2 case proper=
    ly releases this reference on every path inside the ClientGUID-match branch=
    , either by calling ksmbd_put_durable_fd() or by transferring ownership to = dh_info-&gt;fp for a successful reconnect. However, when an entry exists in=
    the global file table with the same CreateGuid but a different ClientGUID,=
    the code simply falls through to the new-open path without dropping the re= ference obtained from ksmbd_lookup_fd_cguid(). Per MS-SMB2 section 3.3.5.9.=
    10 ("Handling the SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2 Create Context"), t=
    he server MUST locate an Open whose Open.CreateGuid matches the request's C= reateGuid AND whose Open.ClientGuid matches the ClientGuid of the connectio=
    n that received the request. If no such Open is found, the server MUST cont= inue with the normal open execution phase. A CreateGuid hit with a ClientGU=
    ID mismatch is therefore the "Open not found" case: proceeding with a new o= pen is correct, but the reference obtained purely as a side effect of the l= ookup must not be leaked. Repeated requests that hit this mismatch pin glob= al_ft entries, prevent __ksmbd_close_fd() from ever running for the corresp= onding files, and defeat the durable scavenger, leading to long-lived resou= rce leaks. Release the reference in the mismatch path and clear dh_info-&gt= ;fp so subsequent logic does not mistake a non-matching lookup result for a=
    reconnect target.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52996" target=3D= "_blank" rel=3D"noopener">CVE-2026-52996</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /sched: sch_dualpi2: drain both C-queue and L-queue in dualpi2_change() Fix=
    dualpi2_change() to correctly enforce updated limit and memlimit values af= ter a configuration change of the dualpi2 qdisc. Before this patch, dualpi2= _change() always attempted to dequeue packets via the root qdisc (C-queue) = when reducing backlog or memory usage, and unconditionally assumed that a v= alid skb will be returned. When traffic classification results in packets b= eing queued in the L-queue while the C-queue is empty, this leads to a NULL=
    skb dereference during limit or memlimit enforcement. This is fixed by fir=
    st dequeuing from the C-queue path if it is non-empty. Once the C-queue is = empty, packets are dequeued directly from the L-queue. Return values from q= disc_dequeue_internal() are checked for both queues. When dequeuing from th=
    e L-queue, the parent qdisc qlen and backlog counters are updated explicitl=
    y to keep overall qdisc statistics consistent.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52997" target=3D= "_blank" rel=3D"noopener">CVE-2026-52997</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: xtables: restrict several matches to inet family This is a partial = revert of: commit ab4f21e6fb1c ("netfilter: xtables: use NFPROTO_UNSPEC in = more extensions") to allow ipv4 and ipv6 only. - xt_mac - xt_owner - xt_phy= sdev These extensions are not used by ebtables in userspace. Moreover, xt_r= ealm is only for ipv4, since dst-&gt;tclassid is ipv4 specific.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53001" target=3D= "_blank" rel=3D"noopener">CVE-2026-53001</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sct=
    p: fix OOB write to userspace in sctp_getsockopt_peer_auth_chunks sctp_gets= ockopt_peer_auth_chunks() checks that the caller's optval buffer is large e= nough for the peer AUTH chunk list with if (len &lt; num_chunks) return -EI= NVAL; but then writes num_chunks bytes to p-&gt;gauth_chunks, which lives a=
    t offset offsetof(struct sctp_authchunks, gauth_chunks) =3D=3D 8 inside opt= val. The check is missing the sizeof(struct sctp_authchunks) =3D 8-byte hea= der. When the caller supplies len =3D=3D num_chunks (for any num_chunks &gt=
    ; 0) the test passes but copy_to_user() writes sizeof(struct sctp_authchunk=
    s) =3D 8 bytes past the declared buffer. The sibling function sctp_getsocko= pt_local_auth_chunks() at the next line already has the correct check: if (= len &lt; sizeof(struct sctp_authchunks) + num_chunks) return -EINVAL; Align=
    the peer variant with its sibling. Reproducer confirms on v7.0-13-generic:=
    an unprivileged userspace caller that opens a loopback SCTP association wi=
    th AUTH enabled, queries num_chunks with a short optval, then issues the re=
    al getsockopt with len =3D=3D num_chunks and sentinel bytes painted past th=
    e buffer observes those sentinel bytes overwritten with the peer's AUTH chu=
    nk type. The bytes written are under the peer's control but land in the cal= ler's own userspace; this is not a kernel memory corruption, but it is a ke= rnel-side contract violation that can silently corrupt adjacent userspace d= ata.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53004" target=3D= "_blank" rel=3D"noopener">CVE-2026-53004</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ice=
    : fix potential NULL pointer deref in error path of ice_set_ringparam() ice= _set_ringparam nullifies tstamp_ring of temporary tx_rings, without clearin=
    g ICE_TX_RING_FLAGS_TXTIME bit. When ICE_TX_RING_FLAGS_TXTIME is set and th=
    e subsequent ice_setup_tx_ring() call fails, a NULL pointer dereference cou=
    ld happen in the unwinding sequence: ice_clean_tx_ring() -&gt; ice_is_txtim= e_cfg() =3D=3D true (ICE_TX_RING_FLAGS_TXTIME is set) -&gt; ice_free_tx_tst= amp_ring() -&gt; ice_free_tstamp_ring() -&gt; tstamp_ring-&gt;desc (NULL de= ref) Clear ICE_TX_RING_FLAGS_TXTIME bit to avoid the potential issue. Note = that this potential issue is found by manual code review. Compile test only=
    since unfortunately I don't have E830 devices.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53007" target=3D= "_blank" rel=3D"noopener">CVE-2026-53007</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ice=
    : fix race condition in TX timestamp ring cleanup Fix a race condition betw= een ice_free_tx_tstamp_ring() and ice_tx_map() that can cause a NULL pointe=
    r dereference. ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TX= TIME flag after NULLing the tstamp_ring. This could allow a concurrent ice_= tx_map call on another CPU to dereference the tstamp_ring, which could lead=
    to a NULL pointer dereference. CPU A:ice_free_tx_tstamp_ring() | CPU B:ice= _tx_map() --------------------------------|--------------------------------=
    - tx_ring-&gt;tstamp_ring =3D NULL | | ice_is_txtime_cfg() -&gt; true | tst= amp_ring =3D tx_ring-&gt;tstamp_ring | tstamp_ring-&gt;count // NULL deref!=
    flags &amp;=3D ~ICE_TX_FLAGS_TXTIME | Fix by: 1. Reordering ice_free_tx_ts= tamp_ring() to clear the flag before NULLing the pointer, with smp_wmb() to=
    ensure proper ordering. 2. Adding smp_rmb() in ice_tx_map() after the flag=
    check to order the flag read before the pointer read, using READ_ONCE() fo=
    r the pointer, and adding a NULL check as a safety net. 3. Converting tx_ri= ng-&gt;flags from u8 to DECLARE_BITMAP() and using atomic bitops (set_bit()=
    , clear_bit(), test_bit()) for all flag operations throughout the driver: -=
    ICE_TX_RING_FLAGS_XDP - ICE_TX_RING_FLAGS_VLAN_L2TAG1 - ICE_TX_RING_FLAGS_= VLAN_L2TAG2 - ICE_TX_RING_FLAGS_TXTIME</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53008" target=3D= "_blank" rel=3D"noopener">CVE-2026-53008</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: nex= thop: fix IPv6 route referencing IPv4 nexthop syzbot reported a panic [1] [= 2]. When an IPv6 nexthop is replaced with an IPv4 nexthop, the has_v4 flag =
    of all groups containing this nexthop is not updated. This is because nh_gr= oup_v4_update is only called when replacing AF_INET to AF_INET6, but the re= verse direction (AF_INET6 to AF_INET) is missed. This allows a stale has_v4= =3Dfalse to bypass fib6_check_nexthop, causing IPv6 routes to be attached t=
    o groups that effectively contain only AF_INET members. Subsequent route lo= okups then call nexthop_fib6_nh() which returns NULL for the AF_INET member=
    , leading to a NULL pointer dereference. Fix by calling nh_group_v4_update = whenever the family changes, not just AF_INET to AF_INET6. Reproducer: # AF= _INET6 blackhole ip -6 nexthop add id 1 blackhole # group with has_v4=3Dfal=
    se ip nexthop add id 100 group 1 # replace with AF_INET (no -6), has_v4 sta=
    ys false ip nexthop replace id 1 blackhole # pass stale has_v4 check ip -6 = route add 2001:db8::/64 nhid 100 # panic ping -6 2001:db8::1 [1] https://sy= zkaller.appspot.com/bug?id=3De17283eb2f8dcf3dd9b47fe6f67a95f71faadad0 [2] h= ttps://syzkaller.appspot.com/bug?id=3D8699b6ae54c9f35837d925686208402949e12= ef3</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53012" target=3D= "_blank" rel=3D"noopener">CVE-2026-53012</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mac= vlan: fix macvlan_get_size() not reserving space for IFLA_MACVLAN_BC_CUTOFF=
    macvlan_get_size() does not account for IFLA_MACVLAN_BC_CUTOFF, but macvla= n_fill_info() conditionally includes it when port-&gt;bc_cutoff !=3D 1. Thi=
    s causes nla_put_s32() to fail with -EMSGSIZE when the netlink skb runs out=
    of space, triggering a WARN_ON in rtnetlink and preventing the interface f= rom being dumped. The bug can be reproduced with: ip link add macvlan0 link=
    eth0 type macvlan mode bridge ip link set macvlan0 type macvlan bc_cutoff =
    0 ip -d link show macvlan0 # fails with -EMSGSIZE The bc_cutoff feature was=
    added in commit 954d1fa1ac93 ("macvlan: Add netlink attribute for broadcas=
    t cutoff"), which added the nla_put_s32() call in macvlan_fill_info() but m= issed adding the corresponding nla_total_size(4) in macvlan_get_size(). A f= ollow-up commit 55cef78c244d ("macvlan: add forgotten nla_policy for IFLA_M= ACVLAN_BC_CUTOFF") fixed the missing nla_policy entry but still did not fix=
    the size calculation.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53013" target=3D= "_blank" rel=3D"noopener">CVE-2026-53013</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /sched: act_mirred: fix wrong device for mac_header_xmit check in tcf_block= cast_redir In tcf_blockcast_redir(), when iterating block ports to redirect=
    packets to multiple devices, the mac_header_xmit flag is queried from the = wrong device. The loop sends to dev_prev but queries dev_is_mac_header_xmit= (dev) - which is the NEXT device in the iteration, not the one being sent t=
    o. This causes tcf_mirred_to_dev() to make incorrect decisions about whethe=
    r to push or pull the MAC header. When the block contains mixed device type=
    s (e.g., an ethernet veth and a tunnel device), intermediate devices get th=
    e wrong mac_header_xmit flag, leading to skb header corruption. In the wors=
    t case, skb_push_rcsum with an incorrect mac_len can exhaust headroom and p= anic. The last device in the loop is handled correctly (line 365-366 uses d= ev_is_mac_header_xmit(dev_prev)), confirming this is a copy-paste oversight=
    for the intermediate devices. Fix by using dev_prev instead of dev for the=
    mac_header_xmit query, consistent with the device actually being sent to.<=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53014" target=3D= "_blank" rel=3D"noopener">CVE-2026-53014</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ero= fs: unify lcn as u64 for 32-bit platforms As sashiko reported [1], `lcn` wa=
    s typed as `unsigned long` (or `unsigned int` sometimes), which is only 32 = bits wide on 32-bit platforms, which causes `(lcn &lt;&lt; lclusterbits)` t=
    o be truncated at 4 GiB. In order to consolidate the logic, just use `u64` = consistently around the codebase. [1] https://sashiko.dev/r/20260420034612.= 1899973-1-hsiangkao%40linux.alibaba.com</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53015" target=3D= "_blank" rel=3D"noopener">CVE-2026-53015</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: f2f=
    s: fix data loss caused by incorrect use of nat_entry flag Data loss can oc= cur when fsync is performed on a newly created file (before any checkpoint = has been written) concurrently with a checkpoint operation. The scenario is=
    as follows: create &amp; write &amp; fsync 'file A' write checkpoint - f2f= s_do_sync_file // inline inode - f2fs_write_inode // inode folio is dirty -=
    f2fs_write_checkpoint - f2fs_flush_merged_writes - f2fs_sync_node_pages - = f2fs_flush_nat_entries - f2fs_fsync_node_pages // no dirty node - f2fs_need= _inode_block_update // return false SPO and lost 'file A' f2fs_flush_nat_en= tries() sets the IS_CHECKPOINTED and HAS_LAST_FSYNC flags for the nat_entry=
    , but this does not mean that the checkpoint has actually completed success= fully. However, f2fs_need_inode_block_update() checks these flags and incor= rectly assumes that the checkpoint has finished. The root cause is that the=
    semantics of IS_CHECKPOINTED and HAS_LAST_FSYNC are only guaranteed after = the checkpoint write fully completes. This patch modifies f2fs_need_inode_b= lock_update() to acquire the sbi-&gt;node_write lock before reading the nat= _entry flags, ensuring that once IS_CHECKPOINTED and HAS_LAST_FSYNC are obs= erved to be set, the checkpoint operation has already completed.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53017" target=3D= "_blank" rel=3D"noopener">CVE-2026-53017</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: f2f=
    s: avoid reading already updated pages during GC We found the following iss=
    ue during fuzz testing: page: refcount:3 mapcount:0 mapping:00000000b6e89c6=
    5 index:0x18b2dc pfn:0x161ba9 memcg:f8ffff800e269c00 aops:f2fs_meta_aops in= o:2 flags: 0x52880000000080a9(locked|waiters|uptodate|lru|private|zone=3D1|= kasantag=3D0x4a) raw: 52880000000080a9 fffffffec6e17588 fffffffec0ccc088 a7= ffff8067063618 raw: 000000000018b2dc 0000000000000009 00000003ffffffff f8ff= ff800e269c00 page dumped because: VM_BUG_ON_FOLIO(folio_test_uptodate(folio=
    )) page_owner tracks the page as allocated post_alloc_hook+0x58c/0x5ec prep= _new_page+0x34/0x284 get_page_from_freelist+0x2dcc/0x2e8c __alloc_pages_nop= rof+0x280/0x76c __folio_alloc_noprof+0x18/0xac __filemap_get_folio+0x6bc/0x= dc4 pagecache_get_page+0x3c/0x104 do_garbage_collect+0x5c78/0x77a4 f2fs_gc+= 0xd74/0x25f0 gc_thread_func+0xb28/0x2930 kthread+0x464/0x5d8 ret_from_fork+= 0x10/0x20 ------------[ cut here ]------------ kernel BUG at mm/filemap.c:1= 563! folio_end_read+0x140/0x168 f2fs_finish_read_bio+0x5c4/0xb80 f2fs_read_= end_io+0x64c/0x708 bio_endio+0x85c/0x8c0 blk_update_request+0x690/0x127c sc= si_end_request+0x9c/0xb8c scsi_io_completion+0xf0/0x250 scsi_finish_command= +0x430/0x45c scsi_complete+0x178/0x6d4 blk_mq_complete_request+0xcc/0x104 s= csi_done_internal+0x214/0x454 scsi_done+0x24/0x34 which is similar to the p= roblem reported by syzbot: https://syzkaller.appspot.com/bug?extid=3D368675= 8660f980b402dc This case is consistent with the description in commit 9bf1a=
    3f ("f2fs: avoid GC causing encrypted file corrupted"): Page 1 is moved fro=
    m blkaddr A to blkaddr B by move_data_block, and after being written it is = marked as uptodate. Then, Page 1 is moved from blkaddr B to blkaddr C, VM_B= UG_ON_FOLIO was triggered in the endio initiated by ra_data_block. There is=
    no need to read Page 1 again from blkaddr B, since it has already been upd= ated. Therefore, avoid initiating I/O in this case.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53018" target=3D= "_blank" rel=3D"noopener">CVE-2026-53018</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: clk=
    : spacemit: ccu_mix: fix inverted condition in ccu_mix_trigger_fc() Fix inv= erted condition that skips frequency change trigger, causing kernel panics = during cpufreq scaling.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53019" target=3D= "_blank" rel=3D"noopener">CVE-2026-53019</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: scs=
    i: target: core: Fix integer overflow in UNMAP bounds check sbc_execute_unm= ap() checks LBA + range does not exceed the device capacity, but does not g= uard against LBA + range wrapping around on 64-bit overflow. Add an overflo=
    w check matching the pattern already used for WRITE_SAME in the same file.<=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53021" target=3D= "_blank" rel=3D"noopener">CVE-2026-53021</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: pla= tform/x86: dell-wmi-sysman: bound enumeration string aggregation populate_e= num_data() aggregates firmware-provided value-modifier and possible-value s= trings into fixed 512-byte struct members. The current code bounds each ind= ividual source string but then appends every string and separator with raw = strcat() and no remaining-space check. Switch the aggregation loops to a bo= unded append helper and reject enumeration packages whose combined strings =
    do not fit in the destination buffers. [ij: add include]</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53022" target=3D= "_blank" rel=3D"noopener">CVE-2026-53022</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fs/= ntfs3: terminate the cached volume label after UTF-8 conversion ntfs_fill_s= uper() loads the on-disk volume label with utf16s_to_utf8s() and stores the=
    result in sbi-&gt;volume.label. The converted label is later exposed throu=
    gh ntfs3_label_show() using %s, but utf16s_to_utf8s() only returns the numb=
    er of bytes written and does not add a trailing NUL. If the converted label=
    fills the entire fixed buffer, ntfs3_label_show() can read past the end of=
    sbi-&gt;volume.label while looking for a terminator. Terminate the cached = label explicitly after a successful conversion and clamp the exact-full cas=
    e to the last byte of the buffer.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53023" target=3D= "_blank" rel=3D"noopener">CVE-2026-53023</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fs/= ntfs3: fix missing run load for vcn0 in attr_data_get_block_locked() When a=
    compressed or sparse attribute has its clusters frame-aligned, vcn is roun= ded down to the frame start using cmask, which can result in vcn !=3D vcn0.=
    In this case, vcn and vcn0 may reside in different attribute segments. The=
    code already handles the case where vcn is in a different segment by loadi=
    ng its runs before allocation. However, it fails to load runs for vcn0 when=
    vcn0 resides in a different segment than vcn. This causes run_lookup_entry=
    () to return SPARSE_LCN for vcn0 since its segment was never loaded into th=
    e in-memory run list, triggering the WARN_ON(1). Fix this by adding a missi=
    ng check for vcn0 after the existing vcn segment check. If vcn0 falls outsi=
    de the current segment range [svcn, evcn1), find and load the attribute seg= ment containing vcn0 before performing the run lookup. The following scenar=
    io triggers the bug: attr_data_get_block_locked() vcn =3D vcn0 &amp; cmask = &lt;- vcn !=3D vcn0 after frame alignment load runs for vcn segment &lt;- v= cn0 segment not loaded! attr_allocate_clusters() &lt;- allocation succeeds = run_lookup_entry(vcn0) &lt;- vcn0 not in run -&gt; SPARSE_LCN WARN_ON(1) &l= t;- bug fires here!</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53027" target=3D= "_blank" rel=3D"noopener">CVE-2026-53027</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: usb=
    : typec: Fix error pointer dereference The variable tps-&gt;partner is chec= ked for an error pointer and then if it is, it sends an error message but d= oes not return and then immediately dereferenced a few lines below: tps-&gt= ;partner =3D typec_register_partner(tps-&gt;port, &amp;desc); if (IS_ERR(tp= s-&gt;partner)) dev_warn(tps-&gt;dev, "%s: failed to register partnet\n", _= _func__); if (desc.identity) { typec_partner_set_identity(tps-&gt;partner);=
    cd321x-&gt;cur_partner_identity =3D st.partner_identity; } Add early retur=
    n and fix spelling mistake in error message. Detected by Smatch: drivers/us= b/typec/tipd/core.c:827 cd321x_update_work() error: 'tps-&gt;partner' deref= erencing possible ERR_PTR()</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53028" target=3D= "_blank" rel=3D"noopener">CVE-2026-53028</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fs/= ntfs3: prevent uninitialized lcn caused by zero len syzbot reported a unini= t-value in ntfs_iomap_begin [1]. Since runs was not touched yet, run_lookup= _entry() immediately fails and returns false, which makes the value of "*le=
    n" 0. Simultaneously, the new value and err value are also 0, causing the l= ogic in attr_data_get_block_locked() to jump directly to ok, ultimately res= ulting in *lcn being triggered before it is set [1]. In ntfs_iomap_begin(),=
    the check for a 0 value in clen is moved forward to before updating lcn to=
    avoid this [1]. [1] BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1= 460 fs/ntfs3/inode.c:825 ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825=
    iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110 Local variable lcn created at:=
    ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53029" target=3D= "_blank" rel=3D"noopener">CVE-2026-53029</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: i3c=
    : master: renesas: Fix memory leak in renesas_i3c_i3c_xfers() The xfer stru= cture allocated by renesas_i3c_alloc_xfer() was never freed in the renesas_= i3c_i3c_xfers() function. Use the __free(kfree) cleanup attribute to automa= tically free the memory when the variable goes out of scope.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53030" target=3D= "_blank" rel=3D"noopener">CVE-2026-53030</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix NULL deref in map_kptr_match_type for scalar regs Commit ab6c637ad027=
    ("bpf: Fix a bpf_kptr_xchg() issue with local kptr") refactored map_kptr_m= atch_type() to branch on btf_is_kernel() before checking base_type(). A sca= lar register stored into a kptr slot has no btf, so the btf_is_kernel(reg-&= gt;btf) call dereferences NULL. Move the base_type() !=3D PTR_TO_BTF_ID gua=
    rd before any reg-&gt;btf access.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53032" target=3D= "_blank" rel=3D"noopener">CVE-2026-53032</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    , sockmap: Fix af_unix null-ptr-deref in proto update unix_stream_connect()=
    sets sk_state (`WRITE_ONCE(sk-&gt;sk_state, TCP_ESTABLISHED)`) _before_ it=
    assigns a peer (`unix_peer(sk) =3D newsk`). sk_state =3D=3D TCP_ESTABLISHE=
    D makes sock_map_sk_state_allowed() believe that socket is properly set up,=
    which would include having a defined peer. IOW, there's a window when unix= _stream_bpf_update_proto() can be called on socket which still has unix_pee= r(sk) =3D=3D NULL. CPU0 bpf CPU1 connect -------- ------------ WRITE_ONCE(s= k-&gt;sk_state, TCP_ESTABLISHED) sock_map_sk_state_allowed(sk) ... sk_pair = =3D unix_peer(sk) sock_hold(sk_pair) sock_hold(newsk) smp_mb__after_atomic(=
    ) unix_peer(sk) =3D newsk BUG: kernel NULL pointer dereference, address: 00= 00000000000080 RIP: 0010:unix_stream_bpf_update_proto+0xa0/0x1b0 Call Trace=
    : sock_map_link+0x564/0x8b0 sock_map_update_common+0x6e/0x340 sock_map_upda= te_elem_sys+0x17d/0x240 __sys_bpf+0x26db/0x3250 __x64_sys_bpf+0x21/0x30 do_= syscall_64+0x6b/0x3a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Initial idea=
    was to move peer assignment _before_ the sk_state update[1], but that invo= lved an additional memory barrier, and changing the hot path was rejected. = Then a NULL check during proto update in unix_stream_bpf_update_proto() was=
    considered[2], but the follow-up discussion[3] focused on the root cause, = i.e. sockmap update taking a wrong lock. Or, more specifically, missing uni= x_state_lock()[4]. In the end it was concluded that teaching sockmap about = the af_unix locking would be unnecessarily complex[5]. Complexity aside, si= nce BPF_PROG_TYPE_SCHED_CLS and BPF_PROG_TYPE_SCHED_ACT are allowed to upda=
    te sockmaps, sock_map_update_elem() taking the unix lock, as it is currentl=
    y implemented in unix_state_lock(): spin_lock(&amp;unix_sk(s)-&gt;lock), wo= uld be problematic. unix_state_lock() taken in a process context, followed =
    by a softirq-context TC BPF program attempting to take the same spinlock --=
    deadlock[6]. This way we circled back to the peer check idea[2]. [1]: http= s://lore.kernel.org/netdev/ba5c50aa-1df4-40c2-ab33-a72022c5a32e@rbox.co/ [2=
    ]: https://lore.kernel.org/netdev/20240610174906.32921-1-kuniyu@amazon.com/=
    [3]: https://lore.kernel.org/netdev/7603c0e6-cd5b-452b-b710-73b64bd9de26@l= inux.dev/ [4]: https://lore.kernel.org/netdev/CAAVpQUA+8GL_j63CaKb8hbxoL21i= zD58yr1NvhOhU=3Dj+35+3og@mail.gmail.com/ [5]: https://lore.kernel.org/bpf/C= AAVpQUAHijOMext28Gi10dSLuMzGYh+jK61Ujn+fZ-wvcODR2A@mail.gmail.com/ [6]: htt= ps://lore.kernel.org/bpf/dd043c69-4d03-46fe-8325-8f97101435cf@linux.dev/ Su= mmary of scenarios where af_unix/stream connect() may race a sockmap update=
    : 1. connect() vs. bpf(BPF_MAP_UPDATE_ELEM), i.e. sock_map_update_elem_sys(=
    ) Implemented NULL check is sufficient. Once assigned, socket peer won't be=
    released until socket fd is released. And that's not an issue because sock= _map_update_elem_sys() bumps fd refcnf. 2. connect() vs BPF program doing u= pdate Update restricted per verifier.c:may_update_sockmap() to BPF_PROG_TYP= E_TRACING/BPF_TRACE_ITER BPF_PROG_TYPE_SOCK_OPS (bpf_sock_map_update() only=
    ) BPF_PROG_TYPE_SOCKET_FILTER BPF_PROG_TYPE_SCHED_CLS BPF_PROG_TYPE_SCHED_A=
    CT BPF_PROG_TYPE_XDP BPF_PROG_TYPE_SK_REUSEPORT BPF_PROG_TYPE_FLOW_DISSECTO=
    R BPF_PROG_TYPE_SK_LOOKUP Plus one more race to consider: CPU0 bpf CPU1 con= nect -------- ------------ WRITE_ONCE(sk-&gt;sk_state, TCP_ESTABLISHED) soc= k_map_sk_state_allowed(sk) sock_hold(newsk) smp_mb__after_atomic() ---trunc= ated---</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53034" target=3D= "_blank" rel=3D"noopener">CVE-2026-53034</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    , sockmap: Fix af_unix iter deadlock bpf_iter_unix_seq_show() may deadlock = when lock_sock_fast() takes the fast path and the iter prog attempts to upd= ate a sockmap. Which ends up spinning at sock_map_update_elem()'s bh_lock_s= ock(): WARNING: possible recursive locking detected test_progs/1393 is tryi=
    ng to acquire lock: ffff88811ec25f58 (slock-AF_UNIX){+...}-{3:3}, at: sock_= map_update_elem+0xdb/0x1f0 but task is already holding lock: ffff88811ec25f=
    58 (slock-AF_UNIX){+...}-{3:3}, at: __lock_sock_fast+0x37/0xe0 other info t= hat might help us debug this: Possible unsafe locking scenario: CPU0 ---- l= ock(slock-AF_UNIX); lock(slock-AF_UNIX); *** DEADLOCK *** May be due to mis= sing lock nesting notation 4 locks held by test_progs/1393: #0: ffff88814b5= 9c790 (&amp;p-&gt;lock){+.+.}-{4:4}, at: bpf_seq_read+0x59/0x10d0 #1: ffff8= 8811ec25fd8 (sk_lock-AF_UNIX){+.+.}-{0:0}, at: bpf_seq_read+0x42c/0x10d0 #2=
    : ffff88811ec25f58 (slock-AF_UNIX){+...}-{3:3}, at: __lock_sock_fast+0x37/0= xe0 #3: ffffffff85a6a7c0 (rcu_read_lock){....}-{1:3}, at: bpf_iter_run_prog= +0x51d/0xb00 Call Trace: dump_stack_lvl+0x5d/0x80 print_deadlock_bug.cold+0= xc0/0xce __lock_acquire+0x130f/0x2590 lock_acquire+0x14e/0x2b0 _raw_spin_lo= ck+0x30/0x40 sock_map_update_elem+0xdb/0x1f0 bpf_prog_2d0075e5d9b721cd_dump= _unix+0x55/0x4f4 bpf_iter_run_prog+0x5b9/0xb00 bpf_iter_unix_seq_show+0x1f7= /0x2e0 bpf_seq_read+0x42c/0x10d0 vfs_read+0x171/0xb20 ksys_read+0xff/0x200 = do_syscall_64+0x6b/0x3a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53035" target=3D= "_blank" rel=3D"noopener">CVE-2026-53035</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: HID=
    : usbhid: fix deadlock in hid_post_reset() You can build a USB device that = includes a HID component and a storage or UAS component. The components can=
    be reset only together. That means that hid_pre_reset() and hid_post_reset=
    () are in the block IO error handling. Hence no memory allocation used in t= hem may do block IO because the IO can deadlock on the mutex held while res= etting a device and calling the interface drivers. Use GFP_NOIO for all all= ocations in them.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53037" target=3D= "_blank" rel=3D"noopener">CVE-2026-53037</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ima= _fs: Correctly create securityfs files for unsupported hash algos ima_tpm_c= hip-&gt;allocated_banks[i].crypto_id is initialized to HASH_ALGO__LAST if t=
    he TPM algorithm is not supported. However there are places relying on the = algorithm to be valid because it is accessed by hash_algo_name[]. On 6.12.4=
    0 I observe the following read out-of-bounds in hash_algo_name: =3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D BUG: KASAN: global-out-of-bounds in=
    create_securityfs_measurement_lists+0x396/0x440 Read of size 8 at addr fff= fffff83e18138 by task swapper/0/1 CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not = tainted 6.12.40 #3 Call Trace: &lt;TASK&gt; dump_stack_lvl+0x61/0x90 print_= report+0xc4/0x580 ? kasan_addr_to_slab+0x26/0x80 ? create_securityfs_measur= ement_lists+0x396/0x440 kasan_report+0xc2/0x100 ? create_securityfs_measure= ment_lists+0x396/0x440 create_securityfs_measurement_lists+0x396/0x440 ima_= fs_init+0xa3/0x300 ima_init+0x7d/0xd0 init_ima+0x28/0x100 do_one_initcall+0= xa6/0x3e0 kernel_init_freeable+0x455/0x740 kernel_init+0x24/0x1d0 ret_from_= fork+0x38/0x80 ret_from_fork_asm+0x11/0x20 &lt;/TASK&gt; The buggy address = belongs to the variable: hash_algo_name+0xb8/0x420 Memory state around the = buggy address: ffffffff83e18000: 00 01 f9 f9 f9 f9 f9 f9 00 01 f9 f9 f9 f9 =
    f9 f9 ffffffff83e18080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 &gt= ;ffffffff83e18100: 00 00 00 00 00 00 00 f9 f9 f9 f9 f9 00 05 f9 f9 ^ ffffff= ff83e18180: f9 f9 f9 f9 00 00 00 00 00 00 00 04 f9 f9 f9 f9 ffffffff83e1820=
    0: 00 00 00 00 00 00 00 00 04 f9 f9 f9 f9 f9 f9 f9 =3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D Seems like the TPM chip supports sha3_256, which i= sn't yet in tpm_algorithms: tpm tpm0: TPM with unsupported bank algorithm 0= x0027 That's TPM_ALG_SHA3_256 =3D=3D 0x0027 from "Trusted Platform Module 2=
    .0 Library Part 2: Structures", page 51 [1]. See also the related U-Boot al= gorithms update [2]. Thus solve the problem by creating a file name with "_= tpm_alg_&lt;ID&gt;" postfix if the crypto algorithm isn't initialized. This=
    is how it looks on the test machine (patch ported to v6.12 release): # ls =
    -1 /sys/kernel/security/ima/ ascii_runtime_measurements ascii_runtime_measu= rements_tpm_alg_27 ascii_runtime_measurements_sha1 ascii_runtime_measuremen= ts_sha256 binary_runtime_measurements binary_runtime_measurements_tpm_alg_2=
    7 binary_runtime_measurements_sha1 binary_runtime_measurements_sha256 polic=
    y runtime_measurements_count violations [1]: https://trustedcomputinggroup.= org/wp-content/uploads/Trusted-Platform-Module-2.0-Library-Part-2-Version-1= 84_pub.pdf [2]: https://lists.denx.de/pipermail/u-boot/2024-July/558835.htm= l</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53038" target=3D= "_blank" rel=3D"noopener">CVE-2026-53038</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ocf= s2: validate group add input before caching [BUG] OCFS2_IOC_GROUP_ADD can t= rigger a BUG_ON in ocfs2_set_new_buffer_uptodate(): kernel BUG at fs/ocfs2/= uptodate.c:509! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010:o= cfs2_set_new_buffer_uptodate+0x194/0x1e0 fs/ocfs2/uptodate.c:509 Code: ffff= e88f 42b9fe4c 89e64889 dfe8b4df Call Trace: ocfs2_group_add+0x3f1/0x1510 fs= /ocfs2/resize.c:507 ocfs2_ioctl+0x309/0x6e0 fs/ocfs2/ioctl.c:887 vfs_ioctl = fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioct=
    l fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x197/0x1e0 fs/ioctl.c:583 x64_sy= s_call+0x1144/0x26a0 arch/x86/include/generated/asm/syscalls_64.h:17 do_sys= call_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x93/0xf80 a= rch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP:=
    0033:0x7bbfb55a966d [CAUSE] ocfs2_group_add() calls ocfs2_set_new_buffer_u= ptodate() on a user-controlled group block before ocfs2_verify_group_and_in= put() validates that block number. That helper is only valid for newly allo= cated metadata and asserts that the block is not already present in the cho= sen metadata cache. The code also uses INODE_CACHE(inode) even though the g= roup descriptor belongs to main_bm_inode and later journal accesses use tha=
    t cache context instead. [FIX] Validate the on-disk group descriptor before=
    caching it, then add it to the metadata cache tracked by INODE_CACHE(main_= bm_inode). Keep the validation failure path separate from the later cleanup=
    path so we only remove the buffer from that cache after it has actually be=
    en inserted. This keeps the group buffer lifetime consistent across validat= ion, journaling, and cleanup.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53039" target=3D= "_blank" rel=3D"noopener">CVE-2026-53039</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fwc= tl: Fix class init ordering to avoid NULL pointer dereference on device rem= oval CXL is linked before fwctl in drivers/Makefile. Both use `module_init,=
    so `cxl_pci_driver_init()` runs first. When `cxl_pci_probe()` calls `fwctl= _register()` and then `device_add()`, fwctl_class is not yet registered bec= ause fwctl_init() hasn't run, causing `class_to_subsys()` to return NULL an=
    d skip knode_class initialization. On device removal, `class_to_subsys()` r= eturns non-NULL, and `device_del()` calls `klist_del()` on the uninitialize=
    d knode, triggering a NULL pointer dereference.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53042" target=3D= "_blank" rel=3D"noopener">CVE-2026-53042</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: efi= /capsule-loader: fix incorrect sizeof in phys array reallocation The kreall= oc() call for cap_info-&gt;phys in __efi_capsule_setup_info() uses sizeof(p= hys_addr_t *) instead of sizeof(phys_addr_t), which might be causing an und= ersized allocation. The allocation is also inconsistent with the initial ar= ray allocation in efi_capsule_open() that allocates one entry with sizeof(p= hys_addr_t), and the efi_capsule_write() function that stores phys_addr_t v= alues (not pointers) via page_to_phys(). On 64-bit systems where sizeof(phy= s_addr_t) =3D=3D sizeof(phys_addr_t *), this goes unnoticed. On 32-bit syst= ems with PAE where phys_addr_t is 64-bit but pointers are 32-bit, this allo= cates half the required space, which might lead to a heap buffer overflow w= hen storing physical addresses. This is similar to the bug fixed in commit = fccfa646ef36 ("efi/capsule-loader: fix incorrect allocation size") which fi= xed the same issue at the initial allocation site.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53047" target=3D= "_blank" rel=3D"noopener">CVE-2026-53047</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: gfs=
    2: prevent NULL pointer dereference during unmount When flushing out outsta= nding glock work during an unmount, gfs2_log_flush() can be called when sdp= -&gt;sd_jdesc has already been deallocated and sdp-&gt;sd_jdesc is NULL. Co= mmit 35264909e9d1 ("gfs2: Fix NULL pointer dereference in gfs2_log_flush") = added a check for that to gfs2_log_flush() itself, but it missed the sdp-&g= t;sd_jdesc dereference in gfs2_log_release(). Fix that.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53048" target=3D= "_blank" rel=3D"noopener">CVE-2026-53048</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: PCI=
    : tegra194: Fix CBB timeout caused by DBI access before core power-on When = PERST# is deasserted twice (assert -&gt; deassert -&gt; assert -&gt; deasse= rt), a CBB (Control Backbone) timeout occurs at DBI register offset 0x8bc (= PCIE_MISC_CONTROL_1_OFF). This happens because pci_epc_deinit_notify() and = dw_pcie_ep_cleanup() are called before reset_control_deassert() powers on t=
    he controller core. The call chain that causes the timeout: pex_ep_event_pe= x_rst_deassert() pci_epc_deinit_notify() pci_epf_test_epc_deinit() pci_epf_= test_clear_bar() pci_epc_clear_bar() dw_pcie_ep_clear_bar() __dw_pcie_ep_re= set_bar() dw_pcie_dbi_ro_wr_en() &lt;- Accesses 0x8bc DBI register reset_co= ntrol_deassert(pcie-&gt;core_rst) &lt;- Core powered on HERE The DBI regist= ers, including PCIE_MISC_CONTROL_1_OFF (0x8bc), are only accessible after t=
    he controller core is powered on via reset_control_deassert(pcie-&gt;core_r= st). Accessing them before this point results in a CBB timeout because the = hardware is not yet operational. Fix this by moving pci_epc_deinit_notify()=
    and dw_pcie_ep_cleanup() to after reset_control_deassert(pcie-&gt;core_rst=
    ), ensuring the controller is fully powered on before any DBI register acce= sses occur.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53051" target=3D= "_blank" rel=3D"noopener">CVE-2026-53051</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ASo=
    C: qcom: qdsp6: topology: check widget type before accessing data Check wid= get type before accessing the private data, as this could a virtual widget = which is no associated with a dsp graph, container and module. Accessing wi= tout check could lead to incorrect memory access.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53052" target=3D= "_blank" rel=3D"noopener">CVE-2026-53052</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /msm/dpu: fix mismatch between power and frequency During DPU runtime suspe= nd, calling dev_pm_opp_set_rate(dev, 0) drops the MMCX rail to MIN_SVS whil=
    e the core clock frequency remains at its original (highest) rate. When run= time resume re-enables the clock, this may result in a mismatch between the=
    rail voltage and the clock rate. For example, in the DPU bind path, the se= quence could be: cpu0: dev_sync_state -&gt; rpmhpd_sync_state cpu1: dpu_kms= _hw_init timeline 0 ------------------------------------------------&gt; t = After rpmhpd_sync_state, the voltage performance is no longer guaranteed to=
    stay at the highest level. During dpu_kms_hw_init, calling dev_pm_opp_set_= rate(dev, 0) drops the voltage, causing the MMCX rail to fall to MIN_SVS wh= ile the core clock is still at its maximum frequency. When the power is re-= enabled, only the clock is enabled, leading to a situation where the MMCX r= ail is at MIN_SVS but the core clock is at its highest rate. In this state,=
    the rail cannot sustain the clock rate, which may cause instability or sys= tem crash. Remove the call to dev_pm_opp_set_rate(dev, 0) from dpu_runtime_= suspend to ensure the correct vote is restored when DPU resumes. Patchwork:=
    https://patchwork.freedesktop.org/patch/710077/</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53056" target=3D= "_blank" rel=3D"noopener">CVE-2026-53056</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in ato= mic_enable() In case if we get errors in cdns_mhdp_link_up() or cdns_mhdp_r= eg_read() in atomic_enable, we will go to cdns_mhdp_modeset_retry_fn() and = will hit NULL pointer while trying to access the mutex. We need the connect=
    or to be set before that. Unlike in legacy cases with flag !DRM_BRIDGE_ATTA= CH_NO_CONNECTOR, we do not have connector initialised in bridge_attach(), s=
    o add the mhdp-&gt;connector_ptr in device structure to handle both cases w= ith DRM_BRIDGE_ATTACH_NO_CONNECTOR and !DRM_BRIDGE_ATTACH_NO_CONNECTOR, set=
    it in atomic_enable() earlier to avoid possible NULL pointer dereference i=
    n recovery paths like modeset_retry_fn() with the DRM_BRIDGE_ATTACH_NO_CONN= ECTOR flag set.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53058" target=3D= "_blank" rel=3D"noopener">CVE-2026-53058</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: dm = log: fix out-of-bounds write due to region_count overflow The local variabl=
    e region_count in create_log_context() is declared as unsigned int (32-bit)=
    , but dm_sector_div_up() returns sector_t (64-bit). When a device-mapper ta= rget has a sufficiently large ti-&gt;len with a small region_size, the divi= sion result can exceed UINT_MAX. The truncated value is then used to calcul= ate bitset_size, causing clean_bits, sync_bits, and recovering_bits to be a= llocated far smaller than needed for the actual number of regions. Subseque=
    nt log operations (log_set_bit, log_clear_bit, log_test_bit) use region ind= ices derived from the full untruncated region space, causing out-of-bounds = writes to kernel heap memory allocated by vmalloc. This can be reproduced b=
    y creating a mirror target whose region_count overflows 32 bits: dmsetup cr= eate bigzero --table '0 8589934594 zero' dmsetup create mymirror --table '0=
    8589934594 mirror \ core 2 2 nosync 2 /dev/mapper/bigzero 0 \ /dev/mapper/= bigzero 0' The status output confirms the truncation (sync_count=3D1 instea=
    d of 4294967297, because 0x100000001 was truncated to 1): $ dmsetup status = mymirror 0 8589934594 mirror 2 254:1 254:1 1/4294967297 ... This leads to a=
    kernel crash in core_in_sync: BUG: scheduling while atomic: (udev-worker)/= 9150/0x00000000 RIP: 0010:core_in_sync+0x14/0x30 [dm_log] CR2: 000000000000= 0008 Fixing recursive fault but reboot is needed! Fix by widening the local=
    region_count to sector_t and adding an explicit overflow check before the = value is assigned to lc-&gt;region_count.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53059" target=3D= "_blank" rel=3D"noopener">CVE-2026-53059</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: dm = cache metadata: fix memory leak on metadata abort retry When failing to acq= uire the root_lock in dm_cache_metadata_abort because the block_manager is = read-only, the temporary block_manager created outside the root_lock is not=
    properly released, causing a memory leak. Reproduce steps: This can be rep= roduced by reloading a new table while the metadata is read-only. While the=
    second call to dm_cache_metadata_abort is caused by lack of support for ta= ble preload in dm-cache, mentioned in commit 9b1cc9f251af ("dm cache: share=
    cache-metadata object across inactive and active DM tables"), it exposes t=
    he memory leak in dm_cache_metadata_abort when the function is called multi= ple times. Specifically, dm-cache fails to sync the new cache object's mode=
    during preresume, creating the reproducer condition. This issue could also=
    occur through concurrent metadata_operation_failed calls due to races in c= ache mode updates, but the table preload scenario below provides a reliable=
    reproducer. 1. Create a cache device with some faulty trailing metadata bl= ocks dmsetup create cmeta &lt;&lt;EOF 0 200 linear /dev/sdc 0 200 7992 erro=
    r EOF dmsetup create cdata --table "0 131072 linear /dev/sdc 8192" dmsetup = create corig --table "0 262144 linear /dev/sdc 262144" dd if=3D/dev/zero of= =3D/dev/mapper/cmeta bs=3D4k count=3D1 oflag=3Ddirect dmsetup create cache = --table "0 131072 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/c= orig 128 1 writethrough smq 0" 2. Suspend and resume the cache to start a n=
    ew metadata transaction and trigger metadata io errors on the next metadata=
    commit. dmsetup suspend cache dmsetup resume cache 3. Write to the cache d= evice to update metadata fio --filename=3D/dev/mapper/cache --name test --r= w=3Drandwrite --bs=3D4k \ --randrepeat=3D0 --direct=3D1 --size 64k 4. Prelo=
    ad the same table dmsetup reload cache --table "$(dmsetup table cache)" 5. = Resume the new table. This triggers the memory leak. dmsetup suspend cache = dmsetup resume cache kmemleak logs: &lt;snip&gt; unreferenced object 0xffff= 8880080c2010 (size 16): comm "dmsetup", pid 132, jiffies 4294982580 hex dum=
    p (first 16 bytes): 00 38 b9 07 80 88 ff ff 6a 6b 6b 6b 6b 6b 6b a5 ... bac= ktrace (crc 3118f31c): kmemleak_alloc+0x28/0x40 __kmalloc_cache_noprof+0x3d= 9/0x510 dm_block_manager_create+0x51/0x140 dm_cache_metadata_abort+0x85/0x3=
    20 metadata_operation_failed+0x103/0x1e0 cache_preresume+0xacd/0xe70 dm_tab= le_resume_targets+0xd3/0x320 __dm_resume+0x1b/0xf0 dm_resume+0x127/0x170 &l= t;snip&gt;</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53060" target=3D= "_blank" rel=3D"noopener">CVE-2026-53060</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: dm = cache: fix dirty mapping checking in passthrough mode switching As mentione=
    d in commit 9b1cc9f251af ("dm cache: share cache-metadata object across ina= ctive and active DM tables"), dm-cache assumed table reload occurs after su= spension, while LVM's table preload breaks this assumption. The dirty mappi=
    ng check for passthrough mode was designed around this assumption and is pe= rformed during table creation, causing the check to fail with preload while=
    metadata updates are ongoing. This risks loading dirty mappings into passt= hrough mode, resulting in data loss. Reproduce steps: 1. Create a writeback=
    cache with zero migration_threshold to produce dirty mappings dmsetup crea=
    te cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0=
    131072 linear /dev/sdc 8192" dmsetup create corig --table "0 262144 linear=
    /dev/sdc 262144" dd if=3D/dev/zero of=3D/dev/mapper/cmeta bs=3D4k count=3D=
    1 oflag=3Ddirect dmsetup create cache --table "0 262144 cache /dev/mapper/c= meta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writeback smq \ =
    2 migration_threshold 0" 2. Preload a table in passthrough mode dmsetup rel= oad cache --table "0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /de= v/mapper/corig 128 2 metadata2 passthrough smq 0" 3. Write to the first cac=
    he block to make it dirty fio --filename=3D/dev/mapper/cache --name=3Dpopul= ate --rw=3Dwrite --bs=3D4k \ --direct=3D1 --size=3D64k 4. Resume the inacti=
    ve table. Now it's possible to load the dirty block into passthrough mode. = dmsetup resume cache Fix by moving the checks to the preresume phase to sup= port table preloading. Also remove the unused function dm_cache_metadata_al= l_clean.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53061" target=3D= "_blank" rel=3D"noopener">CVE-2026-53061</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: dm = cache: fix write hang in passthrough mode The invalidate_remove() function = has incomplete logic for handling write hit bios after cache invalidation. =
    It sets up the remapping for the overwrite_bio but then drops it immediatel=
    y without submission, causing write operations to hang. Fix by adding a new=
    invalidate_committed() continuation that submits the remapped writes to th=
    e cache origin after metadata commit completes, while using the overwrite_e= ndio hook to ensure proper completion sequencing. This maintains existing c= oherency. Also improve error handling in invalidate_complete() to preserve = the original error status instead of using bio_io_error() unconditionally.<=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53063" target=3D= "_blank" rel=3D"noopener">CVE-2026-53063</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: dm = cache: fix null-deref with concurrent writes in passthrough mode In passthr= ough mode, when dm-cache starts to invalidate a cache entry and bio prison = cell lock fails due to concurrent write to the same cached block, mg-&gt;ce=
    ll remains NULL. The error path in invalidate_complete() attempts to unlock=
    and free the cell unconditionally, causing a NULL pointer dereference: KAS= AN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 0 = UID: 0 PID: 134 Comm: fio Not tainted 6.19.0-rc7 #3 PREEMPT RIP: 0010:dm_ce= ll_unlock_v2+0x3f/0x210 &lt;snip&gt; Call Trace: invalidate_complete+0xef/0= x430 map_bio+0x130f/0x1a10 cache_map+0x320/0x6b0 __map_bio+0x458/0x510 dm_s= ubmit_bio+0x40e/0x16d0 __submit_bio+0x419/0x870 &lt;snip&gt; Reproduce step=
    s: 1. Create a cache device dmsetup create cmeta --table "0 8192 linear /de= v/sdc 0" dmsetup create cdata --table "0 131072 linear /dev/sdc 8192" dmset=
    up create corig --table "0 262144 linear /dev/sdc 262144" dd if=3D/dev/zero=
    of=3D/dev/mapper/cmeta bs=3D4k count=3D1 oflag=3Ddirect dmsetup create cac=
    he --table "0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mappe= r/corig 128 2 metadata2 writethrough smq 0" 2. Promote the first data block=
    into cache fio --filename=3D/dev/mapper/cache --name=3Dpopulate --rw=3Dwri=
    te --bs=3D4k \ --direct=3D1 --size=3D64k 3. Reload the cache into passthrou=
    gh mode dmsetup suspend cache dmsetup reload cache --table "0 262144 cache = /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 pas= sthrough smq 0" dmsetup resume cache 4. Write to the first cached block con= currently fio --filename=3D/dev/mapper/cache --name test --rw=3Drandwrite -= -bs=3D4k \ --randrepeat=3D0 --direct=3D1 --numjobs=3D2 --size 64k Fix by ch= ecking if mg-&gt;cell is valid before attempting to unlock it.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53064" target=3D= "_blank" rel=3D"noopener">CVE-2026-53064</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ASo=
    C: sti: use managed regmap_field allocations The regmap_field objects alloc= ated at player init are never freed and may leak resources if the driver is=
    removed. Switch to devm_regmap_field_alloc() to automatically limit the li= fetime of the allocations the lifetime of the device.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53065" target=3D= "_blank" rel=3D"noopener">CVE-2026-53065</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /sun4i: backend: fix error pointer dereference The function drm_atomic_get_= plane_state() can return an error pointer and is not checked for it. Add er= ror pointer check. Detected by Smatch: drivers/gpu/drm/sun4i/sun4i_backend.= c:496 sun4i_backend_atomic_check() error: 'plane_state' dereferencing possi= ble ERR_PTR()</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53066" target=3D= "_blank" rel=3D"noopener">CVE-2026-53066</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: PCI=
    : endpoint: pci-ep-msi: Fix error unwind and prevent double alloc pci_epf_a= lloc_doorbell() stores the allocated doorbell message array in epf-&gt;db_m= sg/epf-&gt;num_db before requesting MSI vectors. If MSI allocation fails, t=
    he array is freed but the EPF state may still point to freed memory. Clear = epf-&gt;db_msg and epf-&gt;num_db on the MSI allocation failure path so tha=
    t later cleanup cannot double-free the array and callers can retry allocati= on. Also return -EBUSY when doorbells have already been allocated to preven=
    t leaking or overwriting an existing allocation.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53067" target=3D= "_blank" rel=3D"noopener">CVE-2026-53067</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error When hci_register_dev=
    () fails in hci_uart_register_dev() HCI_UART_PROTO_INIT is not cleared befo=
    re calling hu-&gt;proto-&gt;close(hu) and setting hu-&gt;hdev to NULL. This=
    means incoming UART data will reach the protocol-specific recv handler in = hci_uart_tty_receive() after resources are freed. Clear HCI_UART_PROTO_INIT=
    with a write lock before calling hu-&gt;proto-&gt;close() and setting hu-&= gt;hdev to NULL. The write lock ensures all active readers have completed a=
    nd no new reader can enter the protocol recv path before resources are free=
    d. This allows the protocol-specific recv functions to remove the "HCI_UART= _REGISTERED" guard without risking a null pointer dereference if hci_regist= er_dev() fails.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53073" target=3D= "_blank" rel=3D"noopener">CVE-2026-53073</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : reject short IPv4/IPv6 inputs in bpf_prog_test_run_skb bpf_prog_test_run_= skb() calls eth_type_trans() first and then uses skb-&gt;protocol to initia= lize sk family and address fields for the test run. For IPv4 and IPv6 packe= ts, it may access ip_hdr(skb) or ipv6_hdr(skb) even when the provided test = input only contains an Ethernet header. Reject the input earlier if the Eth= ernet frame carries IPv4/IPv6 EtherType but the L3 header is too short. Fol=
    d the IPv4/IPv6 header length checks into the existing protocol switch and = return -EINVAL before accessing the network headers.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53074" target=3D= "_blank" rel=3D"noopener">CVE-2026-53074</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= _sched: fix skb memory leak in deferred qdisc drops When the network stack = cleans up the deferred list via qdisc_run_end(), it operates on the root qd= isc. If the root qdisc do not implement the TCQ_F_DEQUEUE_DROPS flag the pa= ckets queue to free are never freed and gets stranded on the child's local = to_free list. Fix this by making qdisc_dequeue_drop() aware of the root qdi= sc. It fetches the root qdisc and check for the TCQ_F_DEQUEUE_DROPS flag. I=
    f the flag is present, the packet is appended directly to the root's to_fre=
    e list. Otherwise, drop it directly as it was done before the optimization = was implemented.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53079" target=3D= "_blank" rel=3D"noopener">CVE-2026-53079</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /sched: cls_fw: fix NULL dereference of "old" filters before change() Like = pointed out by Sashiko [1], since commit ed76f5edccc9 ("net: sched: protect=
    filter_chain list with filter_chain_lock mutex") TC filters are added to a=
    shared block and published to datapath before their -&gt;change() function=
    is called. This is a problem for cls_fw: an invalid filter created with th=
    e "old" method can still classify some packets before it is destroyed by th=
    e validation logic added by Xiang. Therefore, insisting with repeated runs =
    of the following script: # ip link add dev crash0 type dummy # ip link set = dev crash0 up # mausezahn crash0 -c 100000 -P 10 \ &gt; -A 4.3.2.1 -B 1.2.3=
    .4 -t udp "dp=3D1234" -q &amp; # sleep 1 # tc qdisc add dev crash0 egress_b= lock 1 clsact # tc filter add block 1 protocol ip prio 1 matchall \ &gt; ac= tion skbedit mark 65536 continue # tc filter add block 1 protocol ip prio 2=
    fw # ip link del dev crash0 can still make fw_classify() hit the WARN_ON()=
    in [2]: WARNING: ./include/net/pkt_cls.h:88 at fw_classify+0x244/0x250 [cl= s_fw], CPU#18: mausezahn/1399 Modules linked in: cls_fw(E) act_skbedit(E) C= PU: 18 UID: 0 PID: 1399 Comm: mausezahn Tainted: G E 7.0.0-rc6-virtme #17 P= REEMPT(full) Tainted: [E]=3DUNSIGNED_MODULE Hardware name: Red Hat KVM, BIO=
    S 1.16.3-2.el9 04/01/2014 RIP: 0010:fw_classify+0x244/0x250 [cls_fw] Code: =
    5c 49 c7 45 00 00 00 00 00 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 5b b8 ff ff =
    ff ff 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 90 &lt;0f&gt; 0b 90 eb a0 0=
    f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 RSP: 0018:ffffd1b7026bf8a=
    8 EFLAGS: 00010202 RAX: ffff8c5ac9c60800 RBX: ffff8c5ac99322c0 RCX: 0000000= 000000004 RDX: 0000000000000001 RSI: ffff8c5b74d7a000 RDI: ffff8c5ac8284f40=
    RBP: ffffd1b7026bf8d0 R08: 0000000000000000 R09: ffffd1b7026bf9b0 R10: 000= 00000ffffffff R11: 0000000000000000 R12: 0000000000010000 R13: ffffd1b7026b= f930 R14: ffff8c5ac8284f40 R15: 0000000000000000 FS: 00007fca40c37740(0000)=
    GS:ffff8c5b74d7a000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 000=
    0 CR0: 0000000080050033 CR2: 00007fca40e822a0 CR3: 0000000005ca0001 CR4: 00= 00000000172ef0 Call Trace: &lt;TASK&gt; tcf_classify+0x17d/0x5c0 tc_run+0x9= d/0x150 __dev_queue_xmit+0x2ab/0x14d0 ip_finish_output2+0x340/0x8f0 ip_outp= ut+0xa4/0x250 raw_sendmsg+0x147d/0x14b0 __sys_sendto+0x1cc/0x1f0 __x64_sys_= sendto+0x24/0x30 do_syscall_64+0x126/0xf80 entry_SYSCALL_64_after_hwframe+0= x77/0x7f RIP: 0033:0x7fca40e822ba Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb=
    b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c=
    00 00 00 0f 05 &lt;48&gt; 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 =
    83 ec 30 44 89 RSP: 002b:00007ffc248a42c8 EFLAGS: 00000246 ORIG_RAX: 000000= 000000002c RAX: ffffffffffffffda RBX: 000055ef233289d0 RCX: 00007fca40e822b=
    a RDX: 000000000000001e RSI: 000055ef23328c30 RDI: 0000000000000003 RBP: 00= 0055ef233289d0 R08: 00007ffc248a42d0 R09: 0000000000000010 R10: 00000000000= 00000 R11: 0000000000000246 R12: 000000000000001e R13: 00000000000186a0 R14=
    : 0000000000000000 R15: 00007fca41043000 &lt;/TASK&gt; irq event stamp: 104= 5778 hardirqs last enabled at (1045784): [&lt;ffffffff864ec042&gt;] __up_co= nsole_sem+0x52/0x60 hardirqs last disabled at (1045789): [&lt;ffffffff864ec= 027&gt;] __up_console_sem+0x37/0x60 softirqs last enabled at (1045426): [&l= t;ffffffff874d48c7&gt;] __alloc_skb+0x207/0x260 softirqs last disabled at (= 1045434): [&lt;ffffffff874fe8f8&gt;] __dev_queue_xmit+0x78/0x14d0 Then, bec= ause of the value in the packet's mark, dereference on 'q-&gt;handle' with = NULL 'q' occurs: BUG: kernel NULL pointer dereference, address: 00000000000= 00038 [...] RIP: 0010:fw_classify+0x1fe/0x250 [cls_fw] [...] Skip "old-styl=
    e" classification on shared blocks, so that the NULL dereference is fixed a=
    nd WARN_ON() is not hit anymore in the short lifetime of invalid cls_fw "ol= d-style" filters. [1] https://sashiko.dev/#/patchset/2 ---truncated---</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53080" target=3D= "_blank" rel=3D"noopener">CVE-2026-53080</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : hamradio: 6pack: fix uninit-value in sixpack_receive_buf sixpack_receive_= buf() does not properly skip bytes with TTY error flags. The while loop ite= rates through the flags buffer but never advances the data pointer (cp), an=
    d passes the original count (including error bytes) to sixpack_decode(). Th=
    is causes sixpack_decode() to process bytes that should have been skipped d=
    ue to TTY errors. The TTY layer does not guarantee that cp[i] holds a meani= ngful value when fp[i] is set, so passing those positions to sixpack_decode=
    () results in KMSAN reporting an uninit-value read. Fix this by processing = bytes one at a time, advancing cp on each iteration, and only passing valid=
    (non-error) bytes to sixpack_decode(). This matches the pattern used by sl= ip_receive_buf() and mkiss_receive_buf() for the same purpose.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53082" target=3D= "_blank" rel=3D"noopener">CVE-2026-53082</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix RCU stall in bpf_fd_array_map_clear() Add a missing cond_resched() in=
    bpf_fd_array_map_clear() loop. For PROG_ARRAY maps with many entries this = loop calls prog_array_map_poke_run() per entry which can be expensive, and = without yielding this can cause RCU stalls under load: rcu: Stack dump wher=
    e RCU GP kthread last ran: CPU: 0 UID: 0 PID: 30932 Comm: kworker/0:2 Not t= ainted 6.14.0-13195-g967e8def1100 #2 PREEMPT(undef) Workqueue: events prog_= array_map_clear_deferred RIP: 0010:write_comp_data+0x38/0x90 kernel/kcov.c:= 246 Call Trace: &lt;TASK&gt; prog_array_map_poke_run+0x77/0x380 kernel/bpf/= arraymap.c:1096 __fd_array_map_delete_elem+0x197/0x310 kernel/bpf/arraymap.= c:925 bpf_fd_array_map_clear kernel/bpf/arraymap.c:1000 [inline] prog_array= _map_clear_deferred+0x119/0x1b0 kernel/bpf/arraymap.c:1141 process_one_work= +0x898/0x19d0 kernel/workqueue.c:3238 process_scheduled_works kernel/workqu= eue.c:3319 [inline] worker_thread+0x770/0x10b0 kernel/workqueue.c:3400 kthr= ead+0x465/0x880 kernel/kthread.c:464 ret_from_fork+0x4d/0x80 arch/x86/kerne= l/process.c:153 ret_from_fork_asm+0x19/0x30 arch/x86/entry/entry_64.S:245 &= lt;/TASK&gt;</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53083" target=3D= "_blank" rel=3D"noopener">CVE-2026-53083</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : return VMA snapshot from task_vma iterator Holding the per-VMA lock acros=
    s the BPF program body creates a lock ordering problem when helpers acquire=
    locks that depend on mmap_lock: vm_lock -&gt; i_rwsem -&gt; mmap_lock -&gt=
    ; vm_lock Snapshot the VMA under the per-VMA lock in _next() via memcpy(), = then drop the lock before returning. The BPF program accesses only the snap= shot. The verifier only trusts vm_mm and vm_file pointers (see BTF_TYPE_SAF= E_TRUSTED_OR_NULL in verifier.c). vm_file is reference- counted with get_fi= le() under the lock and released via fput() on the next iteration or in _de= stroy(). vm_mm is already correct because lock_vma_under_rcu() verifies vma= -&gt;vm_mm =3D=3D mm. All other pointers are left as-is by memcpy() since t=
    he verifier treats them as untrusted.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53084" target=3D= "_blank" rel=3D"noopener">CVE-2026-53084</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix use-after-free in offloaded map/prog info fill When querying info for=
    an offloaded BPF map or program, bpf_map_offload_info_fill_ns() and bpf_pr= og_offload_info_fill_ns() obtain the network namespace with get_net(dev_net= (offmap-&gt;netdev)). However, the associated netdev's netns may be racing = with teardown during netns destruction. If the netns refcount has already r= eached 0, get_net() performs a refcount_t increment on 0, triggering: refco= unt_t: addition on 0; use-after-free. Although rtnl_lock and bpf_devs_lock = ensure the netdev pointer remains valid, they cannot prevent the netns refc= ount from reaching zero. Fix this by using maybe_get_net() instead of get_n= et(). maybe_get_net() uses refcount_inc_not_zero() and returns NULL if the = refcount is already zero, which causes ns_get_path_cb() to fail and the cal= ler to return -ENOENT -- the correct behavior when the netns is being destr= oyed.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53089" target=3D= "_blank" rel=3D"noopener">CVE-2026-53089</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: brcmfmac: Fix error pointer dereference The function brcmf_chip_add_core=
    () can return an error pointer and is not checked. Add checks for error poi= nter. Detected by Smatch: drivers/net/wireless/broadcom/brcm80211/brcmfmac/= chip.c:1010 brcmf_chip_recognition() error: 'core' dereferencing possible E= RR_PTR() drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c:1013 brcmf= _chip_recognition() error: 'core' dereferencing possible ERR_PTR() drivers/= net/wireless/broadcom/brcm80211/brcmfmac/chip.c:1016 brcmf_chip_recognition=
    () error: 'core' dereferencing possible ERR_PTR() drivers/net/wireless/broa= dcom/brcm80211/brcmfmac/chip.c:1019 brcmf_chip_recognition() error: 'core' = dereferencing possible ERR_PTR() drivers/net/wireless/broadcom/brcm80211/br= cmfmac/chip.c:1022 brcmf_chip_recognition() error: 'core' dereferencing pos= sible ERR_PTR() [add missing wifi: prefix]</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53093" target=3D= "_blank" rel=3D"noopener">CVE-2026-53093</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Fix abuse of kprobe_write_ctx via freplace uprobe programs are allowed to=
    modify struct pt_regs. Since the actual program type of uprobe is KPROBE, =
    it can be abused to modify struct pt_regs via kprobe+freplace when the kpro=
    be attaches to kernel functions. For example, SEC("?kprobe") int kprobe(str= uct pt_regs *regs) { return 0; } SEC("?freplace") int freplace_kprobe(struc=
    t pt_regs *regs) { regs-&gt;di =3D 0; return 0; } freplace_kprobe prog will=
    attach to kprobe prog. kprobe prog will attach to a kernel function. Witho=
    ut this patch, when the kernel function runs, its first arg will always be = set as 0 via the freplace_kprobe prog. To fix the abuse of kprobe_write_ctx= =3Dtrue via kprobe+freplace, disallow attaching freplace programs on kprobe=
    programs with different kprobe_write_ctx values.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53095" target=3D= "_blank" rel=3D"noopener">CVE-2026-53095</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work() When the=
    mt7996 pci chip is detaching, the mt7996_crash_data is released in mt7996_= coredump_unregister(). However, the work item dump_work may still be runnin=
    g or pending, leading to UAF bugs when the already freed crash_data is dere= ferenced again in mt7996_mac_dump_work(). The race condition can occur as f= ollows: CPU 0 (removal path) | CPU 1 (workqueue) mt7996_pci_remove() | mt79= 96_sys_recovery_set() mt7996_unregister_device() | mt7996_reset() mt7996_co= redump_unregister() | queue_work() vfree(dev-&gt;coredump.crash_data) | mt7= 996_mac_dump_work() | crash_data-&gt; // UAF Fix this by ensuring dump_work=
    is properly canceled before the crash_data is deallocated. Add cancel_work= _sync() in mt7996_unregister_device() to synchronize with any pending or ex= ecuting dump work.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53097" target=3D= "_blank" rel=3D"noopener">CVE-2026-53097</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work() When the=
    mt7915 pci chip is detaching, the mt7915_crash_data is released in mt7915_= coredump_unregister(). However, the work item dump_work may still be runnin=
    g or pending, leading to UAF bugs when the already freed crash_data is dere= ferenced again in mt7915_mac_dump_work(). The race condition can occur as f= ollows: CPU 0 (removal path) | CPU 1 (workqueue) mt7915_pci_remove() | mt79= 15_sys_recovery_set() mt7915_unregister_device() | mt7915_reset() mt7915_co= redump_unregister() | queue_work() vfree(dev-&gt;coredump.crash_data) | mt7= 915_mac_dump_work() | crash_data-&gt; // UAF Fix this by ensuring dump_work=
    is properly canceled before the crash_data is deallocated. Add cancel_work= _sync() in mt7915_unregister_device() to synchronize with any pending or ex= ecuting dump work.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53098" target=3D= "_blank" rel=3D"noopener">CVE-2026-53098</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Switch CONFIG_CFI_CLANG to CONFIG_CFI This was renamed in commit 23ef9d43= 9769 ("kcfi: Rename CONFIG_CFI_CLANG to CONFIG_CFI") as it is now a compile= r-agnostic option. Using the wrong name results in the code getting compile=
    d out. Meaning the CFI failures for btf_dtor_kfunc_t would still trigger.</=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53099" target=3D= "_blank" rel=3D"noopener">CVE-2026-53099</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: fix deadlock in remain-on-channel mt76_remain_on_channel() and mt7= 6_roc_complete() call mt76_set_channel() while already holding dev-&gt;mute=
    x. Since mt76_set_channel() also acquires dev-&gt;mutex, this results in a = deadlock. Use __mt76_set_channel() instead of mt76_set_channel(). Add cance= l_delayed_work_sync() for mac_work before acquiring the mutex in mt76_remai= n_on_channel() to prevent a secondary deadlock with the mac_work workqueue.= </td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53100" target=3D= "_blank" rel=3D"noopener">CVE-2026-53100</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: mt7921: fix potential deadlock in mt7921_roc_abort_sync roc_abort_= sync() can deadlock with roc_work(). roc_work() holds dev-&gt;mt76.mutex, w= hile cancel_work_sync() waits for roc_work() to finish. If the caller alrea=
    dy owns the same mutex, both sides block and no progress is possible. This = deadlock can occur during station removal when mt76_sta_state() -&gt; mt76_= sta_remove() -&gt; mt7921_mac_sta_remove() -&gt; mt7921_roc_abort_sync() in= vokes cancel_work_sync() while roc_work() is still running and holding dev-= &gt;mt76.mutex. This avoids the mutex deadlock and preserves exactly-once w= ork ownership.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53101" target=3D= "_blank" rel=3D"noopener">CVE-2026-53101</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() mt76_connac_= mcu_alloc_sta_req() allocates an skb which is expected to be freed eventual=
    ly by mt76_mcu_skb_send_msg(). However, currently if an intermediate functi=
    on fails before sending, the allocated skb is leaked. Specifically, mt76_co= nnac_mcu_sta_wed_update() and mt76_connac_mcu_sta_key_tlv() may fail, leadi=
    ng to an immediate memory leak in the error path. Fix this by explicitly fr= eeing the skb in these error paths. Commit 7c0f63fe37a5 ("wifi: mt76: mt799=
    6: fix memory leak on mt7996_mcu_sta_key_tlv error") made a similar change.=
    Compile tested only. Issue found using a prototype static analysis tool an=
    d code review.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53102" target=3D= "_blank" rel=3D"noopener">CVE-2026-53102</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync roc_abort_= sync() can deadlock with roc_work(). roc_work() holds dev-&gt;mt76.mutex, w= hile cancel_work_sync() waits for roc_work() to finish. If the caller alrea=
    dy owns the same mutex, both sides block and no progress is possible. This = deadlock can occur during station removal when mt76_sta_state() -&gt; mt76_= sta_remove() -&gt; mt7925_mac_sta_remove_link() -&gt; mt7925_mac_link_sta_r= emove() -&gt; mt7925_roc_abort_sync() invokes cancel_work_sync() while roc_= work() is still running and holding dev-&gt;mt76.mutex. This avoids the mut=
    ex deadlock and preserves exactly-once work ownership.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53103" target=3D= "_blank" rel=3D"noopener">CVE-2026-53103</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: Fix memory leak destroying device All MT76 rx queues have an assoc= iated page_pool even if the queue is not associated to a NAPI (e.g. WED RRO=
    queues with WED enabled). Destroy the page_pool running mt76_dma_cleanup r= outine during module unload. Moreover returns pages to the page pool if WED=
    is not enabled for WED RRO queues.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53104" target=3D= "_blank" rel=3D"noopener">CVE-2026-53104</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi Chec=
    k for a NULL `vif` before accessing `ieee80211_vif_is_mld(vif)` to avoid a = potential kernel panic in scenarios where `vif` might not be initialized.</=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53105" target=3D= "_blank" rel=3D"noopener">CVE-2026-53105</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : Do not allow deleting local storage in NMI Currently, local storage may d= eadlock when deferring freeing selem or local storage through kfree_rcu(), = call_rcu() or call_rcu_tasks_trace() in NMI or reentrant. Since deleting se= lem in NMI is an unlikely use case, partially mitigate it by returning erro=
    r when calling from bpf_xxx_storage_delete() helpers in NMI. Note that, it =
    is still possible to deadlock through reentrant. A full mitigation requires=
    returning error when irqs_disabled() is true, which, however is too heavy-= handed for bpf_xxx_storage_delete(). The long-term solution requires _noloc=
    k versions of call_rcu. Another possible solution is to defer the free thro= ugh irq_work [0], but it would grow the size of selem, which is non-ideal. = The check is only needed in bpf_selem_unlink(), which is used by helpers an=
    d syscalls. bpf_selem_unlink_nofail() is fine as it is called during map an=
    d owner tear down that never run in NMI or reentrant. [0] https://lore.kern= el.org/bpf/20260205190233.912-1-alexei.starovoitov@gmail.com/</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53106" target=3D= "_blank" rel=3D"noopener">CVE-2026-53106</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: libertas: don't kill URBs in interrupt context Serialization for the TX = path was enforced by calling usb_kill_urb()/usb_kill_anchored_urbs(), to pr= event transmission before a previous URB was completed. usb_tx_block() can =
    be called from interrupt context (e.g. in the HCD giveback path), so we can=
    't always use it to kill in-flight URBs. Prevent sleeping during interrupt = context by checking the tx_submitted anchor for existing URBs. We now retur=
    n -EBUSY, to indicate there's a pending request.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53107" target=3D= "_blank" rel=3D"noopener">CVE-2026-53107</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: pow= erpc/64s: Fix unmap race with PMD migration entries The following race is p= ossible with migration swap entries or device-private THP entries. e.g. whe=
    n move_pages is called on a PMD THP page, then there maybe an intermediate = state, where PMD entry acts as a migration swap entry (pmd_present() is tru= e). Then if an munmap happens at the same time, then this VM_BUG_ON() can h= appen in pmdp_huge_get_and_clear_full(). This patch fixes that. Thread A: m= ove_pages() syscall add_folio_for_migration() mmap_read_lock(mm) folio_isol= ate_lru(folio) mmap_read_unlock(mm) do_move_pages_to_node() migrate_pages()=
    try_to_migrate_one() spin_lock(ptl) set_pmd_migration_entry() pmdp_invalid= ate() # PMD: _PAGE_INVALID | _PAGE_PTE | pfn set_pmd_at() # PMD: migration = swap entry (pmd_present=3D0) spin_unlock(ptl) [page copy phase] # &lt;--- R= ACE WINDOW --&gt; Thread B: munmap() mmap_write_downgrade(mm) unmap_vmas() = -&gt; zap_pmd_range() zap_huge_pmd() __pmd_trans_huge_lock() pmd_is_huge():=
    # !pmd_present &amp;&amp; !pmd_none -&gt; TRUE (swap entry) pmd_lock() -&g=
    t; # spin_lock(ptl), waits for Thread A to release ptl pmdp_huge_get_and_cl= ear_full() VM_BUG_ON(!pmd_present(*pmdp)) # HITS! [ 287.738700][ T1867] ---= ---------[ cut here ]------------ [ 287.743843][ T1867] kernel BUG at arch/= powerpc/mm/book3s64/pgtable.c:187! cpu 0x0: Vector: 700 (Program Check) at = [c00000044037f4f0] pc: c000000000094ca4: pmdp_huge_get_and_clear_full+0x6c/= 0x23c lr: c000000000645dec: zap_huge_pmd+0xb0/0x868 sp: c00000044037f790 ms=
    r: 800000000282b033 current =3D 0xc0000004032c1a00 paca =3D 0xc000000004fe0= 000 irqmask: 0x03 irq_happened: 0x09 pid =3D 1867, comm =3D a.out kernel BU=
    G at :187! Linux version 6.19.0-12136-g14360d4f917c-dirty (powerpc64le-linu= x-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40)=
    #27 SMP PREEMPT Sun Feb 22 10:38:56 IST 2026 enter ? for help [link regist=
    er ] c000000000645dec zap_huge_pmd+0xb0/0x868 [c00000044037f790] c000000440= 37f7d0 (unreliable) [c00000044037f7d0] c000000000645dcc zap_huge_pmd+0x90/0= x868 [c00000044037f840] c0000000005724cc unmap_page_range+0x176c/0x1f40 [c0= 0000044037fa00] c000000000572ea0 unmap_vmas+0xb0/0x1d8 [c00000044037fa90] c= 0000000005af254 unmap_region+0xb4/0x128 [c00000044037fb50] c0000000005af400=
    vms_complete_munmap_vmas+0x138/0x310 [c00000044037fbe0] c0000000005b0f1c d= o_vmi_align_munmap+0x1ec/0x238 [c00000044037fd30] c0000000005b3688 __vm_mun= map+0x170/0x1f8 [c00000044037fdf0] c000000000587f74 sys_munmap+0x2c/0x40 [c= 00000044037fe10] c000000000032668 system_call_exception+0x128/0x350 [c00000= 044037fe50] c00000000000d05c system_call_vectored_common+0x15c/0x2ec ---- E= xception: 3000 (System Call Vectored) at 0000000010064a2c SP (7fff9b1ee9c0)=
    is in userspace 0:mon&gt; zh commit a30b48bf1b24 ("mm/migrate_device: impl= ement THP migration of zone device pages"), enabled migration for device-pr= ivate PMD entries. Hence this is one other path where this warning could ge=
    t trigger from. ------------[ cut here ]------------ WARNING: arch/powerpc/= mm/book3s64/hash_pgtable.c:199 at hash__pmd_hugepage_update+0x48/0x284, CPU= #3: hmm-tests/1905 Modules linked in: test_hmm CPU: 3 UID: 0 PID: 1905 Comm=
    : hmm-tests Tainted: G B W L N 7.0.0-rc1-01438-g7e2f0ee7581c #21 PREEMPT Ta= inted: [B]=3DBAD_PAGE, [W]=3DWARN, [L]=3DSOFTLOCKUP, [N]=3DTEST Hardware na= me: IBM pSeries (emulated by qemu) POWER10 (architected) 0x801200 0xf000006=
    of:SLOF,git-ee03ae pSeries NIP [c000000000096b70] hash__pmd_hugepage_updat= e+0x48/0x284 LR [c000000000096e7c] hash__pmdp_huge_get_and_clear+0xd0/0xd4 = Call Trace: [c000000604707670] [c000000004e102b8] 0xc000000004e102b8 (unrel= iable) [c000000604707700] [c00000000064ec3c] set_pmd_migration_entry+0x414/= 0x498 [c000000604707760] [c00000000063e5a4] migrate_vma_col ---truncated---= </td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53108" target=3D= "_blank" rel=3D"noopener">CVE-2026-53108</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: pow= erpc/pgtable-frag: Fix bad page state in pte_frag_destroy powerpc uses pt_f= rag_refcount as a reference counter for tracking it's pte and pmd page tabl=
    e fragments. For PTE table, in case of Hash with 64K pagesize, we have 16 f= ragments of 4K size in one 64K page. Patch series [1] "mm: free retracted p= age table by RCU" added pte_free_defer() to defer the freeing of PTE tables=
    when retract_page_tables() is called for madvise MADV_COLLAPSE on shmem ra= nge. [1]: https://lore.kernel.org/all/7cd843a9-aa80-14f-5eb2-33427363c20@go= ogle.com/ pte_free_defer() sets the active flag on the corresponding fragme= nt's folio &amp; calls pte_fragment_free(), which reduces the pt_frag_refco= unt. When pt_frag_refcount reaches 0 (no active fragment using the folio), =
    it checks if the folio active flag is set, if set, it calls call_rcu to fre=
    e the folio, it the active flag is unset then it calls pte_free_now(). Now,=
    this can lead to following problem in a corner case... [ 265.351553][ T183=
    ] BUG: Bad page state in process a.out pfn:20d62 [ 265.353555][ T183] page:=
    refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x20d62 [ 265= .355457][ T183] flags: 0x3ffff800000100(active|node=3D0|zone=3D0|lastcpupid= =3D0x7ffff) [ 265.358719][ T183] raw: 003ffff800000100 0000000000000000 5de= adbeef0000122 0000000000000000 [ 265.360177][ T183] raw: 0000000000000000 c= 0000000119caf58 00000000ffffffff 0000000000000000 [ 265.361438][ T183] page=
    dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set [ 265.362572][ T183] = Modules linked in: [ 265.364622][ T183] CPU: 0 UID: 0 PID: 183 Comm: a.out = Not tainted 6.18.0-rc3-00141-g1ddeaaace7ff-dirty #53 VOLUNTARY [ 265.364785=
    ][ T183] Hardware name: IBM pSeries (emulated by qemu) POWER10 (architected=
    ) 0x801200 0xf000006 of:SLOF,git-ee03ae pSeries [ 265.364908][ T183] Call T= race: [ 265.364955][ T183] [c000000011e6f7c0] [c000000001cfaa18] dump_stack= _lvl+0x130/0x148 (unreliable) [ 265.365202][ T183] [c000000011e6f7f0] [c000= 000000794758] bad_page+0xb4/0x1c8 [ 265.365384][ T183] [c000000011e6f890] [= c00000000079c020] __free_frozen_pages+0x838/0xd08 [ 265.365554][ T183] [c00= 0000011e6f980] [c0000000000a70ac] pte_frag_destroy+0x298/0x310 [ 265.365729=
    ][ T183] [c000000011e6fa30] [c0000000000aa764] arch_exit_mmap+0x34/0x218 [ = 265.365912][ T183] [c000000011e6fa80] [c000000000751698] exit_mmap+0xb8/0x8=
    20 [ 265.366080][ T183] [c000000011e6fc30] [c0000000001b1258] __mmput+0x98/= 0x300 [ 265.366244][ T183] [c000000011e6fc80] [c0000000001c81f8] do_exit+0x= 470/0x1508 [ 265.366421][ T183] [c000000011e6fd70] [c0000000001c95e4] do_gr= oup_exit+0x88/0x148 [ 265.366602][ T183] [c000000011e6fdc0] [c0000000001c96= ec] pid_child_should_wake+0x0/0x178 [ 265.366780][ T183] [c000000011e6fdf0]=
    [c00000000003a270] system_call_exception+0x1b0/0x4e0 [ 265.366958][ T183] = [c000000011e6fe50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2=
    ec The bad page state error occurs when such a folio gets freed (with activ=
    e flag set), from do_exit() path in parallel. ... this can happen when the = pte fragment was allocated from this folio, but when all the fragments get = freed, the pte_frag_refcount still had some unused fragments. Now, if this = process exits, with such folio as it's cached pte_frag in mm-&gt;context, t= hen during pte_frag_destroy(), we simply call pagetable_dtor() and pagetabl= e_free(), meaning it doesn't clear the active flag. This, can lead to the a= bove bug. Since we are anyway in do_exit() path, then if the refcount is 0,=
    then I guess it should be ok to simply clear the folio active flag before = calling pagetable_dtor() &amp; pagetable_free().</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53109" target=3D= "_blank" rel=3D"noopener">CVE-2026-53109</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bpf=
    : test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_enc=
    ap The bpf_lwt_xmit_push_encap helper needs to access skb_dst(skb)-&gt;dev =
    to calculate the needed headroom: err =3D skb_cow_head(skb, len + LL_RESERV= ED_SPACE(skb_dst(skb)-&gt;dev)); But skb-&gt;_skb_refdst may not be initial= ized when the skb is set up by bpf_prog_test_run_skb function. Executing bp= f_lwt_push_ip_encap function in this scenario will trigger null pointer der= eference, causing a kernel crash as Yinhao reported: [ 105.186365] BUG: ker= nel NULL pointer dereference, address: 0000000000000000 [ 105.186382] #PF: = supervisor read access in kernel mode [ 105.186388] #PF: error_code(0x0000)=
    - not-present page [ 105.186393] PGD 121d3d067 P4D 121d3d067 PUD 106c83067=
    PMD 0 [ 105.186404] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 105.186412] CPU: 3=
    PID: 3250 Comm: poc Kdump: loaded Not tainted 6.19.0-rc5 #1 [ 105.186423] = Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16= .3-2 04/01/2014 [ 105.186427] RIP: 0010:bpf_lwt_push_ip_encap+0x1eb/0x520 [=
    105.186443] Code: 0f 84 de 01 00 00 0f b7 4a 04 66 85 c9 0f 85 47 01 00 00=
    31 c0 5b 5d 41 5c 41 5d 41 5e c3 cc cc cc cc 48 8b 73 58 48 83 e6 fe &lt;4= 8&gt; 8b 36 0f b7 be ec 00 00 00 0f b7 b6 e6 00 00 00 01 fe 83 e6 f0 [ 105.= 186449] RSP: 0018:ffffbb0e0387bc50 EFLAGS: 00010246 [ 105.186455] RAX: 0000= 00000000004e RBX: ffff94c74e036500 RCX: ffff94c74874da00 [ 105.186460] RDX:=
    0000000000000000 RSI: 0000000000000000 RDI: ffff94c74e036500 [ 105.186463]=
    RBP: 0000000000000001 R08: 0000000000000002 R09: 0000000000000000 [ 105.18= 6467] R10: ffffbb0e0387bd50 R11: 0000000000000000 R12: ffffbb0e0387bc98 [ 1= 05.186471] R13: 0000000000000014 R14: 0000000000000000 R15: 000000000000000=
    2 [ 105.186484] FS: 00007f166aa4d680(0000) GS:ffff94c8b7780000(0000) knlGS:= 0000000000000000 [ 105.186490] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005= 0033 [ 105.186494] CR2: 0000000000000000 CR3: 000000015eade001 CR4: 0000000= 000770ee0 [ 105.186499] PKRU: 55555554 [ 105.186502] Call Trace: [ 105.1865= 07] &lt;TASK&gt; [ 105.186513] bpf_lwt_xmit_push_encap+0x2b/0x40 [ 105.1865= 22] bpf_prog_a75eaad51e517912+0x41/0x49 [ 105.186536] ? kvm_clock_get_cycle= s+0x18/0x30 [ 105.186547] ? ktime_get+0x3c/0xa0 [ 105.186554] bpf_test_run+= 0x195/0x320 [ 105.186563] ? bpf_test_run+0x10f/0x320 [ 105.186579] bpf_prog= _test_run_skb+0x2f5/0x4f0 [ 105.186590] __sys_bpf+0x69c/0xa40 [ 105.186603]=
    __x64_sys_bpf+0x1e/0x30 [ 105.186611] do_syscall_64+0x59/0x110 [ 105.18662=
    0] entry_SYSCALL_64_after_hwframe+0x76/0xe0 [ 105.186649] RIP: 0033:0x7f166= a97455d Temporarily add the setting of skb-&gt;_skb_refdst before bpf_test_= run to resolve the issue.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53111" target=3D= "_blank" rel=3D"noopener">CVE-2026-53111</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepa= re_bcn_tasklet The irq_prepare_bcn_tasklet is initialized in rtl_pci_init()=
    and scheduled when RTL_IMR_BCNINT interrupt is triggered by hardware. But =
    it is never killed in rtl_pci_deinit(). When the rtlwifi card probe fails o=
    r is being detached, the ieee80211_hw is deallocated. However, irq_prepare_= bcn_tasklet may still be running or pending, leading to use-after-free when=
    the freed ieee80211_hw is accessed in _rtl_pci_prepare_bcn_tasklet(). Simi= lar to irq_tasklet, add tasklet_kill() in rtl_pci_deinit() to ensure that i= rq_prepare_bcn_tasklet is properly terminated before the ieee80211_hw is re= leased. The issue was identified through static analysis.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53112" target=3D= "_blank" rel=3D"noopener">CVE-2026-53112</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: ath11k: fix memory leaks in beacon template setup The functions ath11k_m= ac_setup_bcn_tmpl_ema() and ath11k_mac_setup_bcn_tmpl_mbssid() allocate mem= ory for beacon templates but fail to free it when parameter setup returns a=
    n error. Since beacon templates must be released during normal execution, t= hey must also be released in the error handling paths to prevent memory lea= ks. Fix this by using unified exit paths with proper cleanup in the respect= ive error paths. Compile tested only. Issue found using a prototype static = analysis tool and code review.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53113" target=3D= "_blank" rel=3D"noopener">CVE-2026-53113</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: per= f/amd/ibs: Avoid calling perf_allow_kernel() from the IBS NMI handler Calli=
    ng perf_allow_kernel() from the NMI context is unsafe and could be fatal. C= apture the permission at event-initialization time by storing it in event-&= gt;hw.flags, and have the NMI handler rely on that cached flag instead of m= aking the call directly.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53114" target=3D= "_blank" rel=3D"noopener">CVE-2026-53114</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bus=
    : fsl-mc: use generic driver_override infrastructure When a driver is probe=
    d through __driver_attach(), the bus' match() callback is called without th=
    e device lock held, thus accessing the driver_override field without a lock=
    , which can cause a UAF. Fix this by using the driver-core driver_override = infrastructure taking care of proper locking internally. Note that calling = match() from __driver_attach() without the device lock held is intentional.=
    [1]</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53115" target=3D= "_blank" rel=3D"noopener">CVE-2026-53115</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: s39= 0/ap: use generic driver_override infrastructure When the AP masks are upda= ted via apmask_store() or aqmask_store(), ap_bus_revise_bindings() is calle=
    d after ap_attr_mutex has been released. This calls __ap_revise_reserved(),=
    which accesses the driver_override field without holding any lock, racing = against a concurrent driver_override_store() that may free the old string, = resulting in a potential UAF. Fix this by using the driver-core driver_over= ride infrastructure, which protects all accesses with an internal spinlock.=
    Note that unlike most other buses, the AP bus does not check driver_overri=
    de in its match() callback; the override is checked in ap_device_probe() an=
    d __ap_revise_reserved() instead. Also note that we do not enable the drive= r_override feature of struct bus_type, as AP - in contrast to most other bu= ses - passes "" to sysfs_emit() when the driver_override pointer is NULL. T= hus, printing "\n" instead of "(null)\n". Additionally, AP has a custom cou= nter that is modified in the corresponding custom driver_override_store().<=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53116" target=3D= "_blank" rel=3D"noopener">CVE-2026-53116</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: s39= 0/cio: use generic driver_override infrastructure When a driver is probed t= hrough __driver_attach(), the bus' match() callback is called without the d= evice lock held, thus accessing the driver_override field without a lock, w= hich can cause a UAF. Fix this by using the driver-core driver_override inf= rastructure taking care of proper locking internally. Note that calling mat= ch() from __driver_attach() without the device lock held is intentional. [1= ]</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53117" target=3D= "_blank" rel=3D"noopener">CVE-2026-53117</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: vdp=
    a: use generic driver_override infrastructure When a driver is probed throu=
    gh __driver_attach(), the bus' match() callback is called without the devic=
    e lock held, thus accessing the driver_override field without a lock, which=
    can cause a UAF. Fix this by using the driver-core driver_override infrast= ructure taking care of proper locking internally. Note that calling match()=
    from __driver_attach() without the device lock held is intentional. [1]</t=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53118" target=3D= "_blank" rel=3D"noopener">CVE-2026-53118</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: pla= tform/wmi: use generic driver_override infrastructure When a driver is prob=
    ed through __driver_attach(), the bus' match() callback is called without t=
    he device lock held, thus accessing the driver_override field without a loc=
    k, which can cause a UAF. Fix this by using the driver-core driver_override=
    infrastructure taking care of proper locking internally. Note that calling=
    match() from __driver_attach() without the device lock held is intentional=
    . [1]</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53119" target=3D= "_blank" rel=3D"noopener">CVE-2026-53119</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: PCI=
    : use generic driver_override infrastructure When a driver is probed throug=
    h __driver_attach(), the bus' match() callback is called without the device=
    lock held, thus accessing the driver_override field without a lock, which = can cause a UAF. Fix this by using the driver-core driver_override infrastr= ucture taking care of proper locking internally. Note that calling match() = from __driver_attach() without the device lock held is intentional. [1]</td=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53120" target=3D= "_blank" rel=3D"noopener">CVE-2026-53120</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: amd= -pstate: Fix memory leak in amd_pstate_epp_cpu_init() On failure to set the=
    epp, the function amd_pstate_epp_cpu_init() returns with an error code wit= hout freeing the cpudata object that was allocated at the beginning of the = function. Ensure that the cpudata object is freed before returning from the=
    function. This memory leak was discovered by Claude Opus 4.6 with the aid =
    of Chris Mason's AI review-prompts (https://github.com/masoncl/review-promp= ts/tree/main/kernel).</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53121" target=3D= "_blank" rel=3D"noopener">CVE-2026-53121</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: btr= fs: fix deadlock between reflink and transaction commit when using flushonc= ommit When using the flushoncommit mount option, we can have a deadlock bet= ween a transaction commit and a reflink operation that copied an inline ext= ent to an offset beyond the current i_size of the destination node. The dea= dlock happens like this: 1) Task A clones an inline extent from inode X to =
    an offset of inode Y that is beyond Y's current i_size. This means we copie=
    d the inline extent's data to a folio of inode Y that is beyond its EOF, us= ing a call to copy_inline_to_page(); 2) Task B starts a transaction commit = and calls btrfs_start_delalloc_flush() to flush delalloc; 3) The delalloc f= lushing sees the new dirty folio of inode Y and when it attempts to flush i=
    t, it ends up at extent_writepage() and sees that the offset of the folio i=
    s beyond the i_size of inode Y, so it attempts to invalidate the folio by c= alling folio_invalidate(), which ends up at btrfs' folio invalidate callbac=
    k - btrfs_invalidate_folio(). There it tries to lock the folio's range in i= node Y's extent io tree, but it blocks since it's currently locked by task =
    A - during a reflink we lock the inodes and the source and destination rang=
    es after flushing all delalloc and waiting for ordered extent completion - = after that we don't expect to have dirty folios in the ranges, the exceptio=
    n is if we have to copy an inline extent's data (because the destination of= fset is not zero); 4) Task A then attempts to start a transaction to update=
    the inode item, and then it's blocked since the current transaction is in = the TRANS_STATE_COMMIT_START state. Therefore task A has to wait for the cu= rrent transaction to become unblocked (its state &gt;=3D TRANS_STATE_UNBLOC= KED). So task A is waiting for the transaction commit done by task B, and t=
    he later waiting on the extent lock of inode Y that is currently held by ta=
    sk A. Syzbot recently reported this with the following stack traces: INFO: = task kworker/u8:7:1053 blocked for more than 143 seconds. Not tainted syzka= ller #0 "echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs" disables this=
    message. task:kworker/u8:7 state:D stack:23520 pid:1053 tgid:1053 ppid:2 t= ask_flags:0x4208060 flags:0x00080000 Workqueue: writeback wb_workfn (flush-= btrfs-46) Call Trace: &lt;TASK&gt; context_switch kernel/sched/core.c:5298 = [inline] __schedule+0x1553/0x5240 kernel/sched/core.c:6911 __schedule_loop = kernel/sched/core.c:6993 [inline] schedule+0x164/0x360 kernel/sched/core.c:= 7008 wait_extent_bit fs/btrfs/extent-io-tree.c:811 [inline] btrfs_lock_exte= nt_bits+0x59c/0x700 fs/btrfs/extent-io-tree.c:1914 btrfs_lock_extent fs/btr= fs/extent-io-tree.h:152 [inline] btrfs_invalidate_folio+0x43d/0xc40 fs/btrf= s/inode.c:7704 extent_writepage fs/btrfs/extent_io.c:1852 [inline] extent_w= rite_cache_pages fs/btrfs/extent_io.c:2580 [inline] btrfs_writepages+0x12ff= /0x2440 fs/btrfs/extent_io.c:2713 do_writepages+0x32e/0x550 mm/page-writeba= ck.c:2554 __writeback_single_inode+0x133/0x11a0 fs/fs-writeback.c:1750 writ= eback_sb_inodes+0x995/0x19d0 fs/fs-writeback.c:2042 wb_writeback+0x456/0xb7=
    0 fs/fs-writeback.c:2227 wb_do_writeback fs/fs-writeback.c:2374 [inline] wb= _workfn+0x41a/0xf60 fs/fs-writeback.c:2414 process_one_work kernel/workqueu= e.c:3276 [inline] process_scheduled_works+0xb6e/0x18c0 kernel/workqueue.c:3= 359 worker_thread+0xa53/0xfc0 kernel/workqueue.c:3440 kthread+0x388/0x470 k= ernel/kthread.c:436 ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158=
    ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 &lt;/TASK&gt; IN= FO: task syz.4.64:6910 blocked for more than 143 seconds. Not tainted syzka= ller #0 "echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs" disables this=
    message. task:syz.4.64 state:D stack:22752 pid:6910 tgid: ---truncated---<=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53122" target=3D= "_blank" rel=3D"noopener">CVE-2026-53122</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: md:=
    wake raid456 reshape waiters before suspend During raid456 reshape, direct=
    IO across the reshape position can sleep in raid5_make_request() waiting f=
    or reshape progress while still holding an active_io reference. If userspac=
    e then freezes reshape and writes md/suspend_lo or md/suspend_hi, mddev_sus= pend() kills active_io and waits for all in-flight IO to drain. This can de= adlock: the IO needs reshape progress to continue, but the reshape thread i=
    s already frozen, so the active_io reference is never dropped and suspend n= ever completes. raid5_prepare_suspend() already wakes wait_for_reshape for = dm-raid. Do the same for normal md suspend when reshape is already interrup= ted, so waiting raid456 IO can abort, drop its reference, and let suspend f= inish. The mdadm test tests/25raid456-reshape-deadlock reproduces the hang.= </td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53123" target=3D= "_blank" rel=3D"noopener">CVE-2026-53123</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ubl=
    k: reset per-IO canceled flag on each fetch If a ublk server starts recover= ing devices but dies before issuing fetch commands for all IOs, cancellatio=
    n of the fetch commands that were successfully issued may never complete. T= his is because the per-IO canceled flag can remain set even after the fetch=
    for that IO has been submitted - the per-IO canceled flags for all IOs in =
    a queue are reset together only once all IOs for that queue have been fetch= ed. So if a nonempty proper subset of the IOs for a queue are fetched when = the ublk server dies, the IOs in that subset will never successfully be can= celed, as their canceled flags remain set, and this prevents ublk_cancel_cm=
    d from actually calling io_uring_cmd_done on the commands, despite the fact=
    that they are outstanding. Fix this by resetting the per-IO cancel flags i= mmediately when each IO is fetched instead of waiting for all IOs for the q= ueue (which may never happen).</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53124" target=3D= "_blank" rel=3D"noopener">CVE-2026-53124</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: md:=
    fix array_state=3Dclear sysfs deadlock When "clear" is written to array_st= ate, md_attr_store() breaks sysfs active protection so the array can delete=
    itself from its own sysfs store method. However, md_attr_store() currently=
    drops the mddev reference before calling sysfs_unbreak_active_protection()=
    . Once do_md_stop(..., 0) has made the mddev eligible for delayed deletion,=
    the temporary kobject reference taken by sysfs_break_active_protection() c=
    an become the last kobject reference protecting the md kobject. That allows=
    sysfs_unbreak_active_protection() to drop the last kobject reference from = the current sysfs writer context. kobject teardown then recurses into kernf=
    s removal while the current sysfs node is still being unwound, and lockdep = reports recursive locking on kn-&gt;active with kernfs_drain() in the call = chain. Reproducer on an existing level: 1. Create an md0 linear array and a= ctivate it: mknod /dev/md0 b 9 0 echo none &gt; /sys/block/md0/md/metadata_= version echo linear &gt; /sys/block/md0/md/level echo 1 &gt; /sys/block/md0= /md/raid_disks echo "$(cat /sys/class/block/sdb/dev)" &gt; /sys/block/md0/m= d/new_dev echo "$(($(cat /sys/class/block/sdb/size) / 2))" &gt; \ /sys/bloc= k/md0/md/dev-sdb/size echo 0 &gt; /sys/block/md0/md/dev-sdb/slot echo activ=
    e &gt; /sys/block/md0/md/array_state 2. Wait briefly for the array to settl=
    e, then clear it: sleep 2 echo clear &gt; /sys/block/md0/md/array_state The=
    warning looks like: WARNING: possible recursive locking detected bash/588 =
    is trying to acquire lock: (kn-&gt;active#65) at __kernfs_remove+0x157/0x1d=
    0 but task is already holding lock: (kn-&gt;active#65) at sysfs_unbreak_act= ive_protection+0x1f/0x40 ... Call Trace: kernfs_drain __kernfs_remove kernf= s_remove_by_name_ns sysfs_remove_group sysfs_remove_groups __kobject_del ko= bject_put md_attr_store kernfs_fop_write_iter vfs_write ksys_write Restore = active protection before mddev_put() so the extra sysfs kobject reference i=
    s dropped while the mddev is still held alive. The actual md kobject deleti=
    on is then deferred until after the sysfs write path has fully returned.</t=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53125" target=3D= "_blank" rel=3D"noopener">CVE-2026-53125</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: blk= -cgroup: fix disk reference leak in blkcg_maybe_throttle_current() Add the = missing put_disk() on the error path in blkcg_maybe_throttle_current(). Whe=
    n blkcg lookup, blkg lookup, or blkg_tryget() fails, the function jumps to = the out label which only calls rcu_read_unlock() but does not release the d= isk reference acquired by blkcg_schedule_throttle() via get_device(). Since=
    current-&gt;throttle_disk is already set to NULL before the lookup, blkcg_= exit() cannot release this reference either, causing the disk to never be f= reed. Restore the reference release that was present as blk_put_queue() in = the original code but was inadvertently dropped during the conversion from = request_queue to gendisk.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53126" target=3D= "_blank" rel=3D"noopener">CVE-2026-53126</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: blo= ck: fix zones_cond memory leak on zone revalidation error paths When blk_re= validate_disk_zones() fails after disk_revalidate_zone_resources() has allo= cated args.zones_cond, the memory is leaked because no error path frees it.= </td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53127" target=3D= "_blank" rel=3D"noopener">CVE-2026-53127</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drb=
    d: Balance RCU calls in drbd_adm_dump_devices() Make drbd_adm_dump_devices(=
    ) call rcu_read_lock() before rcu_read_unlock() is called. This has been de= tected by the Clang thread-safety analyzer.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53128" target=3D= "_blank" rel=3D"noopener">CVE-2026-53128</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fs/= mbcache: cancel shrink work before destroying the cache mb_cache_destroy() = calls shrinker_free() and then frees all cache entries and the cache itself=
    , but it does not cancel the pending c_shrink_work work item first. If mb_c= ache_entry_create() schedules c_shrink_work via schedule_work() and the wor=
    k item is still pending or running when mb_cache_destroy() runs, mb_cache_s= hrink_worker() will access the cache after its memory has been freed, causi=
    ng a use-after-free. This is only reachable by a privileged user (root or C= AP_SYS_ADMIN) who can trigger the last put of a mounted ext2/ext4/ocfs2 fil= esystem. Cancel the work item with cancel_work_sync() before calling shrink= er_free(), ensuring the worker has finished and will not be rescheduled bef= ore the cache is torn down.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53129" target=3D= "_blank" rel=3D"noopener">CVE-2026-53129</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nft_fib: fix stale stack leak via the OIFNAME register For NFT_FIB_= RESULT_OIFNAME the destination register is declared with len =3D IFNAMSIZ (= four 32-bit registers), but on the lookup-fail, RTN_LOCAL and oif-mismatch = paths nft_fib{4,6}_eval() only writes one register via "*dest =3D 0". The r= emaining three registers are left as whatever was on the stack in nft_do_ch= ain()'s struct nft_regs, and a downstream expression that loads the registe=
    r span can leak that uninitialised kernel stack to userspace. The NFTA_FIB_= F_PRESENT existence check has the same shape: it is only meaningful for NFT= _FIB_RESULT_OIF, yet it was accepted for any result type while the eval sto= res a single byte via nft_reg_store8(), leaving the rest of the declared sp=
    an stale. Fix both: - replace the bare "*dest =3D 0" in the eval with nft_f= ib_store_result(), which strscpy_pad()s the whole IFNAMSIZ for OIFNAME (and=
    is already used on the other early-return path), and - restrict NFTA_FIB_F= _PRESENT to NFT_FIB_RESULT_OIF and declare its destination as a single u8, =
    so the marked span matches the one byte the eval writes.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53134" target=3D= "_blank" rel=3D"noopener">CVE-2026-53134</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amd/display: Fix NULL deref and buffer over-read in SDP debugfs [Why &amp;=
    How] dp_sdp_message_debugfs_write() dereferences connector-&gt;base.state-= &gt;crtc without checking for NULL. A connector can be connected but not bo= und to any CRTC (e.g. after hot-plug before the next atomic commit), causin=
    g a kernel crash when writing to the sdp_message debugfs node. The function=
    also ignores the user-provided size argument and always passes 36 bytes to=
    copy_from_user(), reading past the user buffer when size &lt; 36. Fix both=
    issues by: - Returning -ENODEV when connector-&gt;base.state or state-&gt;= crtc is NULL - Clamping write_size to min(size, sizeof(data)) (cherry picke=
    d from commit 6ab4c36a522842ff70474a1c0af2e40e50fc8300)</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53135" target=3D= "_blank" rel=3D"noopener">CVE-2026-53135</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amd/display: Clamp VBIOS HDMI retimer register count to array size [Why &a= mp; How] The VBIOS integrated info tables (v1_11 and v2_1) contain HdmiRegN=
    um and Hdmi6GRegNum fields that are used as loop bounds when copying retime=
    r I2C register settings into fixed-size arrays (dp*_ext_hdmi_reg_settings[9=
    ] and dp*_ext_hdmi_6g_reg_settings[3]). These u8 fields are not validated b= efore use, so a malformed VBIOS can specify values up to 255, causing an ou= t-of-bounds heap write during driver probe. Clamp each register count to th=
    e destination array size using min_t() before the copy loops, in both get_i= ntegrated_info_v11() and get_integrated_info_v2_1(). (cherry picked from co= mmit 5a7f0ef90195940c54b0f5bb85b87da55f038c69)</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53136" target=3D= "_blank" rel=3D"noopener">CVE-2026-53136</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size [Why &amp; Ho=
    w] During HDCP 2.x repeater authentication over HDMI, the driver reads the = sink's RxStatus register and extracts a 10-bit message size field (max valu=
    e 1023). This value is used as the read length for the ReceiverID list with= out being clamped to the size of the destination buffer rx_id_list[177]. A = malicious HDMI repeater could advertise a message size larger than the buff= er, causing an out-of-bounds write during the I2C read. Clamp the read leng=
    th in mod_hdcp_read_rx_id_list() to the size of the rx_id_list buffer, matc= hing the approach already used in the DP branch. (cherry picked from commit=
    229212219e4247d9486f8ba41ef087358490be09)</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53137" target=3D= "_blank" rel=3D"noopener">CVE-2026-53137</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amd/display: Bound VBIOS record-chain walk loops [Why &amp; How] All recor= d-chain walk loops in bios_parser.c and bios_parser2.c use for(;;) and only=
    terminate on a 0xFF record_type sentinel or zero record_size. A malformed = VBIOS image missing the terminator record causes unbounded iteration at pro=
    be time, potentially hundreds of thousands of iterations with record_size= =3D1. In the final iterations near the BIOS image boundary, struct casts be= yond the 2-byte header validated by GET_IMAGE can also read out of bounds. = Cap all 14 record-chain walk loops to BIOS_MAX_NUM_RECORD (256) iterations.=
    The atombios.h defines up to 22 distinct record types and atomfirmware.h h=
    as 13. Assuming an average of less than 10 records per type (which is reaso= nable since most are connector- based) 256 is a generous upper bound. (cher=
    ry picked from commit 95700a3d660287ed657d6892f7be9ffc0e294a93)</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53138" target=3D= "_blank" rel=3D"noopener">CVE-2026-53138</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /v3d: Skip CSD when it has zeroed workgroups A compute shader dispatch enco= des its workgroup counts in the CFG0..CFG2 registers. Kicking off a dispatc=
    h with a zero count in any of the three dimensions is invalid. First, the h= ardware will process 0 as 65536, while the user-space driver exposes a maxi= mum of 65535. Over that, a submission with a zeroed workgroup dimension sho= uld be a no-op. These zeroed counts can reach the dispatch path through an = indirect CSD job, whose workgroup counts are only known once the indirect b= uffer is read and may legitimately be zero, but such scenario should only r= esult in a no-op. Overwrite the indirect CSD job workgroup counts with the = indirect BO ones, even if they are zeroed, and don't submit the job to the = hardware when any of the workgroup counts is zero, so the job completes imm= ediately instead of running the shader.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53139" target=3D= "_blank" rel=3D"noopener">CVE-2026-53139</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /v3d: Fix vaddr leak when indirect CSD has zeroed workgroups v3d_rewrite_cs= d_job_wg_counts_from_indirect() maps both the indirect buffer and the workg= roup buffer and is expected to release them before returning. When any of t=
    he workgroup counts read from the buffer is zero, the function bailed out e= arly and skipped the cleanup, leaking the vaddr mappings of both BOs. Jump =
    to the cleanup path instead of returning directly, so the mappings are alwa=
    ys dropped.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53140" target=3D= "_blank" rel=3D"noopener">CVE-2026-53140</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /v3d: Fix global performance monitor reference counting In the SET_GLOBAL i= octl, v3d_perfmon_find() bumps the reference count on the perfmon it return=
    s, but v3d_perfmon_set_global_ioctl() and v3d_perfmon_delete() fail to rele= ase that reference on several paths: 1. v3d_perfmon_set_global_ioctl() leak=
    s the reference on its error paths. 2. CLEAR_GLOBAL leaks both the find ref= erence and the reference previously stashed in v3d-&gt;global_perfmon by th=
    e SET_GLOBAL ioctl that configured it. 3. Destroying a perfmon that is the = current global perfmon leaks the reference stashed by the SET_GLOBAL ioctl.=
    Release each of these references explicitly.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53141" target=3D= "_blank" rel=3D"noopener">CVE-2026-53141</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /xe/display: fix oops in suspend/shutdown without display The xe driver kee=
    ps track of whether to probe display, and whether display hardware is there=
    , using xe-&gt;info.probe_display. It gets set to false if there's no displ=
    ay after intel_display_device_probe(). However, the display may also be dis= abled via fuses, detected at a later time in intel_display_device_info_runt= ime_init(). In this case, the xe driver does for_each_intel_crtc() on unini= tialized mode config in xe_display_flush_cleanup_work(), leading to a NULL = pointer dereference, and generally calls display code with display info cle= ared. Check for intel_display_device_present() after intel_display_device_i= nfo_runtime_init(), and reset xe-&gt;info.probe_display as necessary. Also =
    do unset_display_features() for completeness, although display runtime init=
    has already done that. This will need to be unified across all cases later=
    . Move intel_display_device_info_runtime_init() call slightly earlier, simi= lar to i915, to avoid a bunch of unnecessary setup for no display cases. No=
    te #1: The xe driver has no business doing low level display plumbing like = for_each_intel_crtc() to begin with. It all needs to happen in display code=
    . Note #2: The actual bug is present already in commit 44e694958b95 ("drm/x= e/display: Implement display support"), but the oops was likely introduced = later at commit ddf6492e0e50 ("drm/xe/display: Make display suspend/resume = work on discrete"). (cherry picked from commit 7c3eb9f47533220888a672664481= 85fd0775d4da)</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53142" target=3D= "_blank" rel=3D"noopener">CVE-2026-53142</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 The = v11 MQD manager incorrectly assigned the CP-compute variants of checkpoint_= mqd/restore_mqd for KFD_MQD_TYPE_SDMA queues. These functions use sizeof(st= ruct v11_compute_mqd) (2048 bytes) instead of sizeof(struct v11_sdma_mqd) (= 512 bytes), causing a 1536-byte overflow. During CRIU checkpoint of an SDMA=
    queue on Navi3x: - checkpoint_mqd() reads 2048 bytes from a 512-byte SDMA = MQD buffer, leaking 1536 bytes of adjacent GTT memory to userspace During C= RIU restore: - restore_mqd() writes 2048 bytes into a 512-byte SDMA MQD buf= fer, corrupting 1536 bytes of adjacent GTT memory (often the ring buffer or=
    neighboring MQDs) This is a copy-paste regression unique to v11. All other=
    ASIC backends (cik, vi, v9, v10, v12) correctly use the SDMA-specific vari= ants. Add checkpoint_mqd_sdma() and restore_mqd_sdma() functions that prope= rly handle the smaller v11_sdma_mqd structure, matching the pattern used in=
    other MQD managers. (cherry picked from commit 6fa41db7ffdec97d62433adf03b= 7b9b759af8c2c)</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53143" target=3D= "_blank" rel=3D"noopener">CVE-2026-53143</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amdkfd: fix NULL dereference in get_queue_ids() When usr_queue_id_array is=
    NULL and num_queues is non-zero, get_queue_ids() returns NULL. The callers=
    check only IS_ERR() on the return value; since IS_ERR(NULL) =3D=3D false t=
    he check passes, and suspend_queues() calls q_array_invalidate() which imme= diately dereferences NULL while iterating num_queues times. Userspace can t= rigger this via kfd_ioctl_set_debug_trap() by supplying num_queues &gt; 0 w= ith a zero queue_array_ptr, causing a kernel panic. A NULL usr_queue_id_arr=
    ay with num_queues =3D=3D 0 is a legitimate no-op (q_array_invalidate never=
    executes, and resume_queues already guards all queue_ids dereferences behi=
    nd a NULL check). Return ERR_PTR(-EINVAL) only when num_queues is non-zero = and the pointer is absent; both callers already propagate IS_ERR() returns = correctly to userspace. (cherry picked from commit f165a82cdf503884bb179777= 1c61b2fcc72113d4)</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53144" target=3D= "_blank" rel=3D"noopener">CVE-2026-53144</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: thu= nderbolt: Clamp XDomain response data copy to allocation size tb_xdp_proper= ties_request() derives the per-packet copy length from the response header = without checking that it fits in the previously allocated data buffer. A ma= licious peer can set its length field larger than the declared data_length,=
    causing memcpy to write past the kcalloc allocation. Clamp the per-packet = copy length so that the cumulative offset never exceeds data_len.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53148" target=3D= "_blank" rel=3D"noopener">CVE-2026-53148</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: thu= nderbolt: Bound root directory content to block size __tb_property_parse_di= r() does not check that content_offset + content_len fits within block_len = for the root directory case. When rootdir-&gt;length equals or exceeds bloc= k_len - 2, the entry loop reads past the allocated property block. Add a bo= unds check after computing content_offset and content_len to reject directo= ries whose content extends past the block.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53149" target=3D= "_blank" rel=3D"noopener">CVE-2026-53149</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: thu= nderbolt: Reject zero-length property entries in validator tb_property_entr= y_valid() accepts entries with length =3D=3D 0 for DIRECTORY, DATA, and TEX=
    T types. A zero-length TEXT entry passes validation but causes an underflow=
    in the null-termination logic: property-&gt;value.text[property-&gt;length=
    * 4 - 1] =3D ' '; When property-&gt;length is 0 this writes to offset -1 r= elative to the allocation. Reject zero-length entries early in the validato=
    r since they have no valid representation in the XDomain property protocol.= </td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53150" target=3D= "_blank" rel=3D"noopener">CVE-2026-53150</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mmc=
    : dw_mmc-rockchip: Add missing private data for very old controllers The re= ally old controllers (rk2928, rk3066, rk3188) do not support UHS speeds at = all, and thus never handled phase data. For that reason it never had a pars= e_dt callback and no driver private data at all. Commit ff6f0286c896 ("mmc:=
    dw_mmc-rockchip: Add memory clock auto-gating support") makes the private = data sort of mandatory, because the init function checks whether phases are=
    configured internally or through the clock controller. This results in the=
    old SoCs then experiencing NULL-pointer dereferences when they try to acce=
    ss that private-data struct. While we could have if (priv) conditionals in = all places, it's way less cluttery to just give the old types their private= -data struct.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53152" target=3D= "_blank" rel=3D"noopener">CVE-2026-53152</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mm/= hugetlb: restore reservation on error in hugetlb folio copy paths Two sites=
    in mm/hugetlb.c allocate a hugetlb folio via alloc_hugetlb_folio() (consum= ing a VMA reservation) and then call copy_user_large_folio(), which became = int-returning in commit 1cb9dc4b475c ("mm: hwpoison: support recovery from = HugePage copy-on-write faults") and can now fail (e.g. -EHWPOISON on a hwpo= isoned source page). On the failure path, folio_put() restores the global h= ugetlb pool count through free_huge_folio(), but the per-VMA reservation ma=
    p entry is left marked consumed: - hugetlb_mfill_atomic_pte() resubmission = path (UFFDIO_COPY) - copy_hugetlb_page_range() fork-time CoW path when huge= tlb_try_dup_anon_rmap() fails (rare: pinned hugetlb anon folio under fork) = User-visible effect: on UFFDIO_COPY into a private hugetlb VMA where the re= submission copy fails, the reservation for that address is leaked from the = VMA's reserve map. A subsequent fault at the same address takes the no-rese= rvation path, and under hugetlb pool pressure the task is SIGBUSed at an ad= dress it had previously reserved. The fork-time CoW path leaks the same way=
    in the child VMA's reserve map, though it requires the much rarer combinat= ion of pinned hugetlb anon page + hwpoisoned source. Add the missing restor= e_reserve_on_error() call before folio_put() on both error paths.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53154" target=3D= "_blank" rel=3D"noopener">CVE-2026-53154</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mm/= huge_memory: use correct flags for device private PMD entry Commit 65edfda6= f3f2 ("mm/rmap: extend rmap and migration support device-private entries") = updated set_pmd_migration_entry() to use pmdp_huge_get_and_clear() in the s= oftleaf case, but made no further adjustments to the function itself. There= fore this function continues to incorrectly use pmd_write(), pmd_soft_dirty=
    () and pmd_uffd_wp() to determine whether the installed migration entry sho= uld be marked writable, softdirty or uffd-wp respectively. Whilst all are i= ncorrect, the most problematic of these is pmd_write(), as this can lead to=
    corrupted rmap state. On x86-64 _PAGE_SWP_SOFT_DIRTY is aliased to _PAGE_R=
    W. So calling pmd_write() on a softleaf will return the softdirty state enc= oded in the entry, assuming CONFIG_MEM_SOFT_DIRTY was enabled. This was obs= erved when running the hmm.hmm_device_private.anon_write_child selftest: 1.=
    The test faults in a range then migrates it such that a device-private THP=
    range is established. 2. The parent then migrates it to a device-private w= ritable PMD entry whose folio is entirely AnonExclusive with entire_mapcoun= t=3D1, softdirty set (accidentally correct write state). 3. The parent fork=
    s and the PMD entries are set to device-private read only entries, entire_m= apcount=3D2, softdirty still set. 4. [BUG] The child writes to the range th=
    en migrates to RAM - intending to install non-writable migration entries - = but replacing parent and child PMD mappings with WRITABLE entries due to mi= sinterpreting the softdirty bit. 5. In remove_migration_pmd(), if !softleaf= _is_migration_read(entry) we set the RMAP_EXCLUSIVE flag when calling folio= _add_anon_rmap_pmd() for both parent and child, which are therefore AnonExc= lusive. 6. [SPLAT] Child sets migrated folio entire_mapcount=3D1, parent se=
    ts entire_mapcount=3D2 and we end up with an AnonExclusive folio with entir= e_mapcount=3D2! Assert fires in __folio_add_anon_rmap(): VM_WARN_ON_FOLIO(f= olio_test_large(folio) &amp;&amp; folio_entire_mapcount(folio) &gt; 1 &amp;= &amp; PageAnonExclusive(cur_page), folio) This patch fixes the issue by cor= rectly referencing the softleaf entry fields for writable, softdirty and uf= fd-wp in set_pmd_migration_entry(). It also only updates A/D flags if the e= ntry is present as these are otherwise not meaningful for a softleaf entry.=
    This patch also flips the if (!present) { ... } else { ... } logic in set_= pmd_migration_entry() so it is easier to understand, and adds some comments=
    to make things clearer. I was able to bisect this to commit 775465fd26a3 (= "lib/test_hmm: add zone device private THP test infrastructure") which firs=
    t exposes this bug as it was the commit that permitted test_hmm to generate=
    the test. However commit 65edfda6f3f2 ("mm/rmap: extend rmap and migration=
    support device-private entries") is the commit that actually enabled this = behaviour.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53155" target=3D= "_blank" rel=3D"noopener">CVE-2026-53155</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: nvm= em: core: fix use-after-free bugs in error paths Fix several instances of e= rror paths in which we call __nvmem_device_put() - which may end up freeing=
    the underlying memory and other resources - and then keep on using the nvm=
    em structure. Always put the reference to the nvmem device as the last step=
    before returning the error code.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53156" target=3D= "_blank" rel=3D"noopener">CVE-2026-53156</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : phonet: free phonet_device after RCU grace period phonet_device_destroy()=
    removes a phonet_device from the per-net device list with list_del_rcu(), = but frees it immediately. RCU readers walking the same list can still hold =
    a pointer to the object after it has been removed, leading to a slab-use-af= ter-free. Use kfree_rcu(), matching the lifetime rule already used by phone= t_address_del() for the same object type.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53157" target=3D= "_blank" rel=3D"noopener">CVE-2026-53157</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mis=
    c: fastrpc: Fix NULL pointer dereference in rpmsg callback A NULL pointer d= ereference was observed on Hawi at boot when the DSP sends a glink message = before fastrpc_rpmsg_probe() has completed initialization: Unable to handle=
    kernel NULL pointer dereference at virtual address 0000000000000178 pc : _= raw_spin_lock_irqsave+0x34/0x8c lr : fastrpc_rpmsg_callback+0x3c/0xcc [fast= rpc] ... Call trace: _raw_spin_lock_irqsave+0x34/0x8c (P) fastrpc_rpmsg_cal= lback+0x3c/0xcc [fastrpc] qcom_glink_native_rx+0x538/0x6a4 qcom_glink_smem_= intr+0x14/0x24 [qcom_glink_smem] The faulting address 0x178 corresponds to = the lock variable inside struct fastrpc_channel_ctx, confirming that cctx i=
    s NULL when fastrpc_rpmsg_callback() attempts to take the spinlock. There a=
    re two issues here. First, dev_set_drvdata() is called before spin_lock_ini= t() and idr_init(), leaving a window where the callback can retrieve a vali=
    d cctx pointer but operate on an uninitialized spinlock. Second, the rpmsg = channel becomes live as soon as the driver is bound, so fastrpc_rpmsg_callb= ack() can fire before dev_set_drvdata() is called at all, resulting in dev_= get_drvdata() returning NULL. Fix both issues by moving all cctx initializa= tion ahead of dev_set_drvdata() so the structure is fully initialized befor=
    e it becomes visible to the callback, and add a NULL check in fastrpc_rpmsg= _callback() as a guard against any remaining window.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53158" target=3D= "_blank" rel=3D"noopener">CVE-2026-53158</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mis=
    c: fastrpc: fix DMA address corruption due to find_vma misuse fastrpc_get_a= rgs() uses find_vma() to look up the VMA for a user-provided pointer and co= mpute a DMA address offset. When the address falls in a gap before the retu= rned VMA, (ptr &amp; PAGE_MASK) - vma-&gt;vm_start underflows, corrupting t=
    he DMA address sent to the DSP. Replace find_vma() with vma_lookup(), which=
    returns NULL when the address is not contained within any VMA.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53159" target=3D= "_blank" rel=3D"noopener">CVE-2026-53159</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: loc= king/rtmutex: Skip remove_waiter() when waiter is not enqueued syzbot trigg= ered the following splat in remove_waiter() via FUTEX_CMP_REQUEUE_PI: KASAN=
    : null-ptr-deref in range [0x0000000000000a88-0x0000000000000a8f] class_raw= _spinlock_constructor remove_waiter+0x159/0x1200 kernel/locking/rtmutex.c:1= 561 rt_mutex_start_proxy_lock+0x103/0x120 futex_requeue+0x10e4/0x20d0 __x64= _sys_futex+0x34f/0x4d0 task_blocks_on_rt_mutex() does not arm the waiter up=
    on deadlock detection, leaving waiter-&gt;task nil, where 3bfdc63936dd ("rt= mutex: Use waiter::task instead of current in remove_waiter()") made this f= atal. Furthermore, rt_mutex_start_proxy_lock() should not be calling into r= emove_waiter() upon a successfully grabbing the rtmutex. 1a1fb985f2e2 ("fut= ex: Handle early deadlock return correctly"), moved the remove_waiter() out=
    of __rt_mutex_start_proxy_lock() (where 'ret' was only ever 0 or &lt; 0) i= nto the wrapper. Tighten this check to account for try_to_take_rt_mutex().<=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53163" target=3D= "_blank" rel=3D"noopener">CVE-2026-53163</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= mu/dma: Do not try to iommu_map a 0 length region in swiotlb iommu_dma_iova= _link_swiotlb() processes a mapping that is unaligned in three parts, the h= ead, middle and trailer. If the middle is empty because there are no aligne=
    d pages it will call down to iommu_map() with a 0 size which the iommupt im= plementation will fail as illegal. It then tries to do an error unwind and = starts from the wrong spot corrupting the mapping so the eventual destructi=
    on triggers a WARN_ON. Check for 0 length and avoid mapping and use offset = not 0 as the starting point to unlink. This is frequently triggered by usin=
    g some kinds of thunderbolt NVMe drives that trigger forced SWIOTLB for una= ligned memory. NVMe seems to pass in oddly aligned buffers for the passthro= ugh commands from smartctl that hit this condition.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53164" target=3D= "_blank" rel=3D"noopener">CVE-2026-53164</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fut= ex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-dea= dlock When FUTEX_CMP_REQUEUE_PI requeues a non-top waiter that already owns=
    the target PI futex, task_blocks_on_rt_mutex() returns -EDEADLK before set= ting waiter-&gt;task. The subsequent remove_waiter() in rt_mutex_start_prox= y_lock() dereferences the NULL waiter-&gt;task, causing a kernel crash. Add=
    a self-deadlock check for non-top waiters before calling rt_mutex_start_pr= oxy_lock(), analogous to the top-waiter check in futex_lock_pi_atomic().</t=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53166" target=3D= "_blank" rel=3D"noopener">CVE-2026-53166</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fus=
    e: limit FUSE_NOTIFY_RETRIEVE to uptodate folios FUSE_NOTIFY_RETRIEVE must =
    be limited to uptodate folios; !uptodate folios can contain uninitialized d= ata. Since FUSE_NOTIFY_RETRIEVE is intended to only return data that is alr= eady in the page cache and not wait for data from the FUSE daemon, treat !u= ptodate folios as if they weren't present. This only has security impact on=
    systems that don't enable automatic zero-initialization of all page alloca= tions via CONFIG_INIT_ON_ALLOC_DEFAULT_ON or init_on_alloc=3D1.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53167" target=3D= "_blank" rel=3D"noopener">CVE-2026-53167</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fus=
    e: reject fuse_notify() pagecache ops on directories The operations FUSE_NO= TIFY_STORE and FUSE_NOTIFY_RETRIEVE allow the FUSE daemon to actively write= /read pagecache contents. For directories with FOPEN_CACHE_DIR, the pagecac=
    he is used as kernel-internal cache storage, and userspace is not supposed =
    to have direct access to this cache - in particular, fuse_parse_cache() wil=
    l hit WARN_ON() if the cache contains bogus data. Reject FUSE_NOTIFY_STORE = and FUSE_NOTIFY_RETRIEVE on anything other than regular files with -EINVAL.= </td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53168" target=3D= "_blank" rel=3D"noopener">CVE-2026-53168</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: acc= el/ethosu: reject NPU_OP_RESIZE commands from userspace NPU_OP_RESIZE is a = U85-only command that the driver does not yet implement. The existing WARN_= ON(1) placeholder fires unconditionally whenever userspace submits this com= mand via DRM_IOCTL_ETHOSU_GEM_CREATE, causing unbounded kernel log spam. If=
    panic_on_warn is set the kernel panics, giving any unprivileged user with = access to the DRM device a trivial denial-of-service primitive. Replace the=
    WARN_ON(1) with an explicit -EINVAL return so the ioctl rejects the comman=
    d before it reaches hardware.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53169" target=3D= "_blank" rel=3D"noopener">CVE-2026-53169</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: bnx= t_en: Fix NULL pointer dereference PCIe errors detected by a Root Port or D= ownstream Port cause error recovery services to run on all subordinate devi= ces regardless of administrative state. The .error_detected() callback, bnx= t_io_error_detected(), disables and synchronizes IRQs via bnxt_disable_int_= sync(), which calls bnxt_cp_num_to_irq_num() to map completion rings to IRQ=
    s using bp-&gt;bnapi. Since bp-&gt;bnapi is allocated on NIC open and freed=
    on NIC close, PCIe error recovery on a closed NIC can dereference a NULL p= ointer. Check if bp-&gt;bnapi is NULL before disabling and synchronizing IR= Qs.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53177" target=3D= "_blank" rel=3D"noopener">CVE-2026-53177</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: sta= ging: rtl8723bs: fix buffer over-read in rtw_update_protection rtw_update_p= rotection() is called with a pointer offset into the ies buffer but the ful=
    l ie_length is passed, causing a potential buffer over-read.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53179" target=3D= "_blank" rel=3D"noopener">CVE-2026-53179</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: vso= ck/vmci: fix sk_ack_backlog leak on failed handshake When vmci_transport_re= cv_connecting_server() returns an error, vmci_transport_recv_listen() calls=
    vsock_remove_pending() but never calls sk_acceptq_removed(). This leaves s= k_ack_backlog incremented permanently. Repeated handshake failures (malform=
    ed packets, queue pair alloc failure, event subscribe failure) cause sk_ack= _backlog to climb toward sk_max_ack_backlog. Once it reaches the limit the = listener permanently refuses all new connections with -ECONNREFUSED, a sile=
    nt denial of service requiring a process restart to recover. The two existi=
    ng sk_acceptq_removed() calls in af_vsock.c do not cover this path: line 76=
    4 checks vsock_is_pending() which returns false after vsock_remove_pending(=
    ), and line 1889 is only reached on successful accept(). Fix by balancing s= k_acceptq_added() with sk_acceptq_removed() on the error path.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53181" target=3D= "_blank" rel=3D"noopener">CVE-2026-53181</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait(=
    ) dma_fence_unwrap_for_each() internally calls dma_fence_unwrap_first() whi=
    ch does cursor-&gt;chain =3D dma_fence_get(head), taking an extra reference=
    . On normal loop completion, dma_fence_unwrap_next() releases this via dma_= fence_chain_walk() -&gt; dma_fence_put(). When virtio_gpu_do_fence_wait() f= ails and the function returns early from inside the loop, the cursor-&gt;ch= ain reference is never released. This is the only caller in the entire kern=
    el that does an early return inside dma_fence_unwrap_for_each. Add dma_fenc= e_put(itr.chain) before the early return.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53190" target=3D= "_blank" rel=3D"noopener">CVE-2026-53190</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: USB=
    : serial: io_ti: fix heap overflow in build_i2c_fw_hdr() build_i2c_fw_hdr()=
    allocates a fixed-size buffer of (16*1024 - 512) + sizeof(struct ti_i2c_fi= rmware_rec) bytes, then copies le16_to_cpu(img_header-&gt;Length) bytes int=
    o it without validating that Length fits within the available space after t=
    he firmware record header. img_header-&gt;Length is a __le16 from the firmw= are file and can be up to 65535. check_fw_sanity() validates the total firm= ware size but not img_header-&gt;Length specifically. Fix by rejecting imag=
    es where img_header-&gt;Length exceeds the available destination space.</td=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53195" target=3D= "_blank" rel=3D"noopener">CVE-2026-53195</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: USB=
    : serial: io_ti: fix heap overflow in get_manuf_info() get_manuf_info() rea=
    ds le16_to_cpu(rom_desc-&gt;Size) bytes from the device I2C EEPROM into a b= uffer allocated with kmalloc_obj(), which is sizeof(struct edge_ti_manuf_de= scriptor) =3D 10 bytes. The Size field comes from the device and is only va= lidated (in check_i2c_image()) to make sure the descriptor fits within TI_M= AX_I2C_SIZE (16384 bytes), not against the destination buffer size. A malic= ious USB device can therefore set Size to any value up to 16377, causing a = heap overflow of up to 16367 bytes when plugged into a host running this dr= iver. valid_csum() is called after read_rom() and also iterates buffer[0..S= ize-1], compounding the out-of-bounds access. Fix by rejecting descriptors = with unexpected length before calling read_rom(). [ johan: amend commit mes= sage; also check for short descriptors ]</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53196" target=3D= "_blank" rel=3D"noopener">CVE-2026-53196</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: xfr=
    m: iptfs: fix ABBA deadlock in iptfs_destroy_state() iptfs_destroy_state() = calls hrtimer_cancel() while holding a spinlock that the timer callback als=
    o acquires, leading to an ABBA deadlock on SMP systems. For the output time=
    r (iptfs_timer): - iptfs_destroy_state() holds x-&gt;lock, calls hrtimer_ca= ncel() - iptfs_delay_timer() callback takes x-&gt;lock For the drop timer (= drop_timer): - iptfs_destroy_state() holds drop_lock, calls hrtimer_cancel(=
    ) - iptfs_drop_timer() callback takes drop_lock Both timers use HRTIMER_MOD= E_REL_SOFT, so their callbacks run in softirq context. When hrtimer_cancel(=
    ) is called for a soft timer that is currently executing on another CPU, hr= timer_cancel_wait_running() spins on softirq_expiry_lock -- the same lock h= eld by the softirq running the callback. If the callback is blocked waiting=
    for the spinlock held by the caller of hrtimer_cancel(), a circular depend= ency forms: CPU 0: holds lock_A -&gt; waits for softirq_expiry_lock CPU 1: = holds softirq_expiry_lock -&gt; waits for lock_A Fix by calling hrtimer_can= cel() before acquiring the respective locks. hrtimer_cancel() is safe to ca=
    ll without holding any lock and will wait for any in-progress callback to c= omplete. For the output timer, the lock is still acquired afterwards to dra=
    in the packet queue. For the drop timer, the lock/unlock pair is removed en= tirely since it only existed to serialize with the timer callback, which hr= timer_cancel() already guarantees. Found by source code audit.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53197" target=3D= "_blank" rel=3D"noopener">CVE-2026-53197</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fir= mware: stratix10-rsu: Fix NULL deref on rsu_send_msg() timeout in probe rsu= _send_msg() can return -ETIMEDOUT when wait_for_completion_interruptible_ti= meout() fires while the SMC call is still pending. In stratix10_rsu_probe()=
    , the error paths for COMMAND_RSU_DCMF_VERSION, COMMAND_RSU_DCMF_STATUS, CO= MMAND_RSU_MAX_RETRY and COMMAND_RSU_GET_SPT_TABLE call stratix10_svc_free_c= hannel() - which sets chan-&gt;scl to NULL - but then fall through and queu=
    e the next request on the same channel. The next svc kthread that runs will=
    dereference pdata-&gt;chan-&gt;scl in its receive callback path, triggerin=
    g a NULL pointer dereference identical to the one fixed by commit c45f72631= 00c ("firmware: stratix10-rsu: Fix NULL pointer dereference when RSU is dis= abled") for the COMMAND_RSU_STATUS path. Apply the same cleanup pattern to = the remaining failure paths: remove the async client, free the channel, and=
    return early so no further messages are queued on a channel whose scl has = been cleared. While at it, clean up stratix10_rsu_probe() in two ways witho=
    ut changing behavior: - Drop redundant zero-initialization of fields alread=
    y cleared by devm_kzalloc(): client.receive_cb, status.* and spt0/1_address=
    (INVALID_SPT_ADDRESS is 0x0). - Replace five identical 3-line error-cleanu=
    p blocks (stratix10_svc_remove_async_client() + stratix10_svc_free_channel(=
    ) + return ret) with goto labels (remove_async_client, free_channel), match= ing the standard kernel resource-unwinding pattern and making it easier to = extend the probe sequence without forgetting matching cleanup. Also move in= it_completion() next to mutex_init() so sync-primitive initialization is gr= ouped before anything that could trigger a callback. --- v2: Add a minor cl= ean-up of the function stratix10_rsu_probe() to have a centralize exit for = all the rsu_send_async_msg() and rsu_send_msg().</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53204" target=3D= "_blank" rel=3D"noopener">CVE-2026-53204</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: acc= el/ivpu: Add bounds check for firmware runtime memory Validate that the fir= mware runtime memory specified in the image header is properly aligned and = sized to hold the firmware image. This prevents errors during memory alloca= tion and image transfer.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53206" target=3D= "_blank" rel=3D"noopener">CVE-2026-53206</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mm/= memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison = Two concurrent madvise(MADV_HWPOISON) calls on the same hugetlb page can tr= igger a recursive spinlock self-deadlock (AA deadlock) on hugetlb_lock when=
    racing with a concurrent unmap: thread#0 thread#1 -------- -------- madvis= e(folio, MADV_HWPOISON) -&gt; poisons the folio successfully madvise(folio,=
    MADV_HWPOISON) unmap(folio) try_memory_failure_hugetlb get_huge_page_for_h= wpoison spin_lock_irq(&amp;hugetlb_lock) &lt;- held __get_huge_page_for_hwp= oison hugetlb_update_hwpoison() -&gt; MF_HUGETLB_FOLIO_PRE_POISONED goto ou=
    t: folio_put() refcount: 1 -&gt; 0 free_huge_folio() spin_lock_irqsave(&amp= ;hugetlb_lock) -&gt; AA DEADLOCK! The out: path in __get_huge_page_for_hwpo= ison() calls folio_put() to drop the GUP reference while the hugetlb_lock i=
    s still held by the hugetlb.c wrapper get_huge_page_for_hwpoison(). If conc= urrent unmap has released the page table mapping reference, folio_put() dro=
    ps the folio refcount to zero, triggering free_huge_folio() which attempts =
    to re-acquire the non-recursive hugetlb_lock. Fix this by moving hugetlb_lo=
    ck acquisition from the hugetlb.c wrapper into get_huge_page_for_hwpoison()=
    . Place spin_unlock_irq() before the folio_put() at the out: label so the f= olio is always released outside the lock. [akpm@linux-foundation.org: fix r= ace, rename label per Miaohe]</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53207" target=3D= "_blank" rel=3D"noopener">CVE-2026-53207</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: L2CAP: reject BR/EDR signaling packets over MTUsig net/bluetooth/l2= cap_core.c:l2cap_sig_channel() accepts BR/EDR signaling packets up to the c= hannel MTU and dispatches each command without enforcing the signaling MTU = (MTUsig). A Bluetooth BR/EDR peer within radio range can send a fixed-chann=
    el CID 0x0001 packet that is larger than MTUsig and contains many L2CAP_ECH= O_REQ commands before pairing. In a real-radio stock-kernel run, one 681-by=
    te signaling packet containing 168 zero-length ECHO_REQ commands made the t= arget transmit 168 ECHO_RSP frames over about 220 ms. Impact: a Bluetooth B= R/EDR peer within radio range, before pairing, can force 168 ECHO_RSP frame=
    s from one 681-byte fixed-channel signaling packet containing packed ECHO_R=
    EQ commands. Define Linux's BR/EDR signaling MTU as the spec minimum of 48 = bytes and reject any larger signaling packet with one L2CAP_COMMAND_REJECT_= RSP carrying L2CAP_REJ_MTU_EXCEEDED before any command is dispatched. The B= luetooth Core spec wording for MTUExceeded says the reject identifier shall=
    match the first request command in the packet, and that packets containing=
    only responses shall be silently discarded. Linux intentionally deviates f= rom that prescription: silently discarding desynchronizes the peer because = the remote stack never learns its responses were dropped, and locating the = first request command requires walking command headers past MTUsig, i.e. pr= ocessing bytes from a packet we have already decided is too large to proces=
    s. We therefore always emit one reject and use the identifier from the firs=
    t command header, a single fixed-offset byte read. The unrestricted BR/EDR = signaling parser and ECHO_REQ response path both trace to the initial git i= mport; no later introducing commit is available for a Fixes tag.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53208" target=3D= "_blank" rel=3D"noopener">CVE-2026-53208</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: tee=
    : shm: fix shm leak in register_shm_helper() register_shm_helper() allocate=
    s shm before calling iov_iter_npages(). If iov_iter_npages() returns 0, the=
    function jumps to err_ctx_put and leaks shm. This can be triggered by TEE_= IOC_SHM_REGISTER with struct tee_ioctl_shm_register_data where length is 0.=
    Jump to err_free_shm instead.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53210" target=3D= "_blank" rel=3D"noopener">CVE-2026-53210</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nft_meta_bridge: fix stale stack leak via IIFHWADDR register NFT_ME= TA_BRI_IIFHWADDR declares its destination register with len =3D ETH_ALEN (6=
    bytes), which the register-init tracking rounds up to two 32-bit registers=
    (8 bytes). nft_meta_bridge_get_eval() then does memcpy(dest, br_dev-&gt;de= v_addr, ETH_ALEN), writing only 6 bytes and leaving the upper 2 bytes of th=
    e second register as uninitialised nft_do_chain() stack. A downstream load =
    of that register span leaks those stale bytes to userspace. Zero the second=
    register before the memcpy so the full declared span is written.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53211" target=3D= "_blank" rel=3D"noopener">CVE-2026-53211</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /vc4: fix krealloc() memory leak Don't just overwrite the original pointer = passed to krealloc() with its return value without checking latter: MEM =3D=
    krealloc(MEM, SZ, GFP); If krealloc() returns NULL, that erases the pointe=
    r to the still allocated memory, hence leaks this memory. Instead, use a te= mporary variable, check it's not NULL and only then assign it to the origin=
    al pointer: TMP =3D krealloc(MEM, SZ, GFP); if (!TMP) return; MEM =3D TMP; = While on it, use krealloc_array().</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53213" target=3D= "_blank" rel=3D"noopener">CVE-2026-53213</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ipv=
    6: Fix a potential NPD in cleanup_prefix_route() addrconf_get_prefix_route(=
    ) can return the fib6_null_entry sentinel entry which has a NULL fib6_table=
    pointer. Therefore, before setting the route's expiration time, check that=
    we are not working with this entry, as otherwise a NPD will be triggered [= 1]. Note that the other callers of addrconf_get_prefix_route() are not susc= eptible to this bug: 1. addrconf_prefix_rcv(): Requests a route with the 'R= TF_ADDRCONF | RTF_PREFIX_RT' flags which are not set on fib6_null_entry. 2.=
    modify_prefix_route(): Fixed by commit a747e02430df ("ipv6: avoid possible=
    NULL deref in modify_prefix_route()"). 3. __ipv6_ifa_notify(): Calls ip6_d= el_rt() which specifically checks for fib6_null_entry and returns an error.=
    [1] Oops: general protection fault, probably for non-canonical address 0xd= ffffc0000000006: 0000 [#1] SMP KASAN KASAN: null-ptr-deref in range [0x0000= 000000000030-0x0000000000000037] [...] Call Trace: &lt;TASK&gt; __kasan_che= ck_byte (mm/kasan/common.c:573) lock_acquire.part.0 (kernel/locking/lockdep= .c:5842 (discriminator 1)) _raw_spin_lock_bh (kernel/locking/spinlock.c:182=
    (discriminator 1)) cleanup_prefix_route (net/ipv6/addrconf.c:1280) ipv6_de= l_addr (net/ipv6/addrconf.c:1342) inet6_addr_del.isra.0 (net/ipv6/addrconf.= c:3119) inet6_rtm_deladdr (net/ipv6/addrconf.c:4812) rtnetlink_rcv_msg (net= /core/rtnetlink.c:6997) netlink_rcv_skb (net/netlink/af_netlink.c:2555) net= link_unicast (net/netlink/af_netlink.c:1344) netlink_sendmsg (net/netlink/a= f_netlink.c:1899) __sock_sendmsg (net/socket.c:802 (discriminator 4)) ____s= ys_sendmsg (net/socket.c:2698) ___sys_sendmsg (net/socket.c:2752) __sys_sen= dmsg (net/socket.c:2784) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch= /x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/= entry_64.S:121)</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53214" target=3D= "_blank" rel=3D"noopener">CVE-2026-53214</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: nft_exthdr: fix register tracking for F_PRESENT flag nft_exthdr_ini= t() passes user-controlled priv-&gt;len to nft_parse_register_store(), whic=
    h marks that many bytes in the register bitmap as initialized. However, whe=
    n NFT_EXTHDR_F_PRESENT is set, the eval paths write only 1 byte (nft_reg_st= ore8) or 4 bytes (*dest =3D 0 on TCP/DCCP error path). When len &gt; 4, reg= isters beyond the first are never written, retaining uninitialized stack da=
    ta from nft_regs. Bail out if userspace requests too much data when F_PRESE=
    NT is set.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53218" target=3D= "_blank" rel=3D"noopener">CVE-2026-53218</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: x_tables: avoid leaking percpu counter pointers The native and comp=
    at get-entries paths copy the fixed rule entry header from the kernelized r= ule blob to userspace before overwriting the entry's counter fields with a = sanitized counter snapshot. On SMP kernels, entry-&gt;counters.pcnt contain=
    s the percpu allocation address used by x_tables rule counters. A caller ca=
    n provide a userspace buffer that faults during the initial fixed-header co=
    py after pcnt has been copied but before the later sanitized counter copy r= uns. The syscall then returns -EFAULT while leaving the raw percpu pointer =
    in userspace. Copy only the fixed entry prefix before counters from the ker= nelized rule blob, then copy the sanitized counter snapshot into the counte=
    r field. Apply this ordering to the IPv4, IPv6, and ARP native and compat g= et-entries implementations so a fault cannot expose the internal percpu cou= nter pointer.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53219" target=3D= "_blank" rel=3D"noopener">CVE-2026-53219</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: revalidate bridge ports ebt_redirect_tg() dereferences br_port_get_= rcu() return without a NULL check, causing a kernel panic when the bridge p= ort has been removed between the original hook invocation and an NFQUEUE re= inject. A mere NULL check isn't sufficient, however. As sashiko review poin=
    ts out userspace can not only remove the port from the bridge, it could als=
    o place the device in a different virtual device, e.g. macvlan. If this hap= pens, we must drop the packet, there is no way for us to reinject it into t=
    he bridge path. Switch to _upper API, we don't need the bridge port structu= re. Also, this fix keeps another bug intact: Both nfnetlink_log and nfnetli= nk_queue use CONFIG_BRIDGE_NETFILTER too aggressive, which prevents certain=
    logging features when queueing in bridge family: NETFILTER_FAMILY_BRIDGE c=
    an be enabled while the old CONFIG_BRIDGE_NETFILTER cruft is off. Fixes tag=
    is a common ancestor, this was always broken.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53220" target=3D= "_blank" rel=3D"noopener">CVE-2026-53220</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ptp=
    : ocp: fix resource freeing order Commit a60fc3294a37 ("ptp: rework ptp_clo= ck_unregister() to disable events") added a call to ptp_disable_all_events(=
    ) which changes the configuration of pins if they support EXTTS events. In = ptp_ocp_detach() pins resources are freed before ptp_clock_unregister() and=
    it leads to use-after-free during driver removal. Fix it by changing the o= rder of free/unregister calls. To avoid irq handler running on the other co=
    re while ptp device unregistering, call synchronize_irq() after HW is confi= gured to stop producing irqs and no irqs are in-flight.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53222" target=3D= "_blank" rel=3D"noopener">CVE-2026-53222</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: gpi=
    o: rockchip: fix generic IRQ chip leak on remove The driver allocates domai=
    n generic chips using irq_alloc_domain_generic_chips() during probe. Howeve=
    r, on driver remove/teardown, the generic chips are not automatically freed=
    when the IRQ domain is removed because the domain flags do not include IRQ= _DOMAIN_FLAG_DESTROY_GC. This causes both the domain generic chips structur=
    e and the associated generic chips to be leaked. Additionally, the generic = chips remain on the global gc_list and may later be visited by generic IRQ = chip suspend, resume, or shutdown callbacks after the GPIO bank has been re= moved, potentially resulting in a use-after-free and kernel crash. Fix the = resource leak by explicitly calling irq_domain_remove_generic_chips() befor=
    e removing the IRQ domain in rockchip_gpio_remove().</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53226" target=3D= "_blank" rel=3D"noopener">CVE-2026-53226</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : openvswitch: fix possible kfree_skb of ERR_PTR After the patch in the "Fi= xes" tag, the allocation of the "reply" skb can happen either before or aft=
    er locking the ovs_mutex. However, error cleanups still follow the classica=
    l reversed order, assuming "reply" is allocated before locking: it is freed=
    after unlocking. If "reply" allocation happens after locking the mutex and=
    it fails, "reply" is left with an ERR_PTR, and execution jumps to the corr= espondent cleanup stage which will try to free an invalid pointer. Fix this=
    by setting the pointer to NULL after having saved its error value.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53227" target=3D= "_blank" rel=3D"noopener">CVE-2026-53227</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : phy: don't try to setup PHY-driven SFP cages when using genphy We don't h= ave support for PHY-driver SFP cages with the genphy code. On top of that, =
    it was found by sashiko that running sfp_bus_add_upstream() for genphy dead= locks, as for genphy the PHY probing runs under RTNL, which isn't the case = for non-genphy drivers. This problem was reproduced, and does lead to a dea= dlock on RTNL. Before the blamed commit, the phy_sfp_probe() call was made =
    by individual PHY drivers, so there was no way to get to the SFP probing pa=
    th when using genphy. Let's therefore only run phy_sfp_probe when not using=
    genphy.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53231" target=3D= "_blank" rel=3D"noopener">CVE-2026-53231</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= dev: fix double-free in netdev_nl_bind_rx_doit() Sashiko flags that genlmsg= _reply() always consumes the skb. The error path calls nlmsg_free(rsp) so w=
    e can't jump directly to it. Let's not unbind, just propagate the error to = the user. This is the typical way of handling genlmsg_reply() failures. The=
    y shouldn't happen unless user does something silly like calling the kernel=
    with an already-full rcvbuf.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53233" target=3D= "_blank" rel=3D"noopener">CVE-2026-53233</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : ibm: emac: Fix use-after-free during device removal The driver was using = devm_register_netdev() which causes unregister_netdev() to be deferred unti=
    l the devres cleanup phase, which runs after emac_remove() returns. This cr= eates a use-after-free window where: 1. emac_remove() is called, which tear=
    s down hardware (cancels work, detaches modules, unregisters from MAL) 2. e= mac_remove() returns 3. devres cleanup runs and finally calls unregister_ne= tdev() During step 3, the network stack might still process packets, trigge= ring emac_irq(), emac_poll(), or other handlers that access now-freed hardw= are resources (dev-&gt;emacp, dev-&gt;mal, etc.). Fix this by replacing dev= m_register_netdev() with manual register_netdev() and calling unregister_ne= tdev() at the beginning of emac_remove(), before any hardware teardown. Thi=
    s ensures the network device is fully stopped and unregistered before hardw= are resources are released. The change is safe because: - dev-&gt;ndev is a= ssigned very early in probe (before any error paths that could bypass emac_= remove) - platform_set_drvdata() is only called after successful registrati= on, so emac_remove() only runs for fully registered devices - unregister_ne= tdev() is idempotent and safe to call on any registered device</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53234" target=3D= "_blank" rel=3D"noopener">CVE-2026-53234</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: tcp=
    : restrict SO_ATTACH_FILTER to priv users This patch restricts the use of S= O_ATTACH_FILTER (cBPF) on TCP sockets to users with CAP_NET_ADMIN capabilit=
    y. This blocks potential side-channel attack where an unprivileged applicat= ion attaches a filter to leak TCP sequence/acknowledgment numbers.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53236" target=3D= "_blank" rel=3D"noopener">CVE-2026-53236</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: gpi=
    o: mvebu: fix NULL pointer dereference in suspend/resume mvebu_pwm_suspend(=
    ) and mvebu_pwm_resume() are called for all GPIO banks during suspend/resum=
    e, but not all banks have PWM functionality. GPIO banks without PWM have mv= chip-&gt;mvpwm set to NULL. Calling mvebu_pwm_suspend() with mvpwm =3D=3D N= ULL causes a NULL pointer dereference when it tries to access mvpwm-&gt;bli= nk_select. Unable to handle kernel NULL pointer dereference at virtual addr= ess 00000020 when write [00000020] *pgd=3D00000000 Internal error: Oops: 81=
    5 [#1] PREEMPT ARM Modules linked in: CPU: 0 UID: 0 PID: 406 Comm: sh Not t= ainted 6.12.74-rt12-yocto-standard-g4e96f98fb7db-dirty #353 Hardware name: = Marvell Armada 370/XP (Device Tree) PC is at regmap_mmio_read+0x38/0x54 LR =
    is at regmap_mmio_read+0x38/0x54 pc : [&lt;c05fd2ac&gt;] lr : [&lt;c05fd2ac= &gt;] psr: 200f0013 sp : f0c11d10 ip : 00000000 fp : c100d2f0 r10: c14fb854=
    r9 : 00000000 r8 : 00000000 r7 : c1799c00 r6 : 00000020 r5 : 00000020 r4 :=
    c179c7c0 r3 : f0a231a0 r2 : 00000020 r1 : 00000020 r0 : 00000000 Flags: nz=
    Cv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none Control: 10c5387d Table=
    : 135ec059 DAC: 00000051 Call trace: regmap_mmio_read from _regmap_bus_reg_= read+0x78/0xac _regmap_bus_reg_read from _regmap_read+0x60/0x154 _regmap_re=
    ad from regmap_read+0x3c/0x60 regmap_read from mvebu_gpio_suspend+0xa4/0x14=
    c mvebu_gpio_suspend from dpm_run_callback+0x54/0x180 dpm_run_callback from=
    device_suspend+0x124/0x630 device_suspend from dpm_suspend+0x124/0x270 dpm= _suspend from dpm_suspend_start+0x64/0x6c dpm_suspend_start from suspend_de= vices_and_enter+0x140/0x8e8 suspend_devices_and_enter from pm_suspend+0x2fc= /0x308 pm_suspend from state_store+0x6c/0xc8 state_store from kernfs_fop_wr= ite_iter+0x10c/0x1f8 kernfs_fop_write_iter from vfs_write+0x270/0x468 vfs_w= rite from ksys_write+0x70/0xf0 ksys_write from ret_fast_syscall+0x0/0x54 Ad=
    d a NULL check for mvchip-&gt;mvpwm before calling the PWM suspend/resume f= unctions.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53237" target=3D= "_blank" rel=3D"noopener">CVE-2026-53237</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= label: validate unlabeled address and mask attribute lengths netlbl_unlabel= _addrinfo_get() used the address attribute length to determine whether the = attribute data could be read as an IPv4 or IPv6 address, but did not indepe= ndently validate the corresponding mask attribute length. A crafted Generic=
    Netlink request could therefore provide a valid IPv4/IPv6 address attribut=
    e with a shorter mask attribute, which would later be read as a full struct=
    in_addr or struct in6_addr. NLA_BINARY policy lengths are maximum lengths =
    by default, so use NLA_POLICY_EXACT_LEN() for the unlabeled IPv4/IPv6 addre=
    ss and mask attributes. This rejects short attributes during policy validat= ion and also exposes the exact length requirements through policy introspec= tion.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53238" target=3D= "_blank" rel=3D"noopener">CVE-2026-53238</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ALS=
    A: seq: dummy: fix UMP event stack overread The dummy sequencer port forwar=
    ds events by copying an incoming struct snd_seq_event into a stack temporar=
    y, rewriting source and destination, and dispatching the temporary to subsc= ribers. That legacy event storage is smaller than struct snd_seq_ump_event.=
    When a UMP event reaches the dummy client, the copy leaves the UMP flag se=
    t but only provides legacy-sized stack storage. The subscriber delivery pat=
    h then uses snd_seq_event_packet_size() and copies a UMP-sized packet from = that stack object, reading past the end of the temporary. Use the existing = union __snd_seq_event storage and copy the packet size reported for the inc= oming event before rewriting the common routing fields. This preserves the = full UMP packet for UMP events while keeping legacy event handling unchange= d.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53241" target=3D= "_blank" rel=3D"noopener">CVE-2026-53241</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: rse=
    q: Fix using an uninitialized stack variable in rseq_exit_user_update() The=
    re is an bug in which an uninitialized stack variable is used in rseq_exit_= user_update() as reported by syzbot: BUG: KMSAN: kernel-infoleak in rseq_se= t_ids_get_csaddr include/linux/rseq_entry.h:502 [inline] The local variable=
    : struct rseq_ids ids =3D { .cpu_id =3D task_cpu(t), .mm_cid =3D task_mm_ci= d(t), .node_id =3D cpu_to_node(ids.cpu_id), }; According to the C standard,=
    the evaluation order of expressions in an initializer list is indeterminat= ely sequenced. The compiler (Clang, in this KMSAN build) evaluates `cpu_to_= node(ids.cpu_id)` *before* `ids.cpu_id` is initialized with `task_cpu(t)`. = This is fixed by moving the assignment of ids.node_id outside the structure=
    initialization.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53243" target=3D= "_blank" rel=3D"noopener">CVE-2026-53243</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr In mrp_pdu_= parse_vecattr(), vector attribute events are encoded three per byte and val=
    en tracks the number of events left to process. The parser decrements valen=
    after processing the first and second events from each event byte, but not=
    after processing the third one. When valen is exactly a multiple of three,=
    the loop continues after the last valid event and consumes the next byte a=
    s a new event byte, applying a spurious event to the MRP applicant state. A= dditionally, when valen is zero the parser unconditionally consumes attrlen=
    bytes as FirstValue and advances the offset, even though per IEEE 802.1ak =
    a VectorAttribute with only a LeaveAllEvent has valen of zero and no FirstV= alue or Vector fields. This corrupts the offset for subsequent PDU parsing.=
    Also, when valen exceeds three the loop crosses byte boundaries but the at= tribute value is not incremented between the last event of one byte and the=
    first event of the next. This causes the first event of the next byte to u=
    se the same attribute value as the third event rather than the next consecu= tive value. Decrement valen after processing the third event, skip FirstVal=
    ue consumption when valen is zero, and increment the attribute value at the=
    end of each loop iteration.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53245" target=3D= "_blank" rel=3D"noopener">CVE-2026-53245</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ipv=
    4: restrict IPOPT_SSRR and IPOPT_LSRR options This patch restricts setting = Loose Source and Record Route (LSRR) and Strict Source and Record Route (SS= RR) IP options to users with CAP_NET_RAW capability. This prevents unprivil= eged applications from forcing packets to route through attacker-controlled=
    nodes to leak TCP ISN and possibly other protocol information. While LSRR = and SSRR are commonly filtered in many network environments, they may still=
    be supported and forwarded along some network paths. RFC 7126 (Recommendat= ions on Filtering of IPv4 Packets Containing IPv4 Options) recommend to dro=
    p these options in 4.3 and 4.4.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53249" target=3D= "_blank" rel=3D"noopener">CVE-2026-53249</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: ISO: Fix not releasing hdev reference on iso_conn_big_sync hci_get_= route() returns a reference-counted hci_dev pointer via hci_dev_hold(). The=
    function exits normally or with an error without ever releasing it.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53251" target=3D= "_blank" rel=3D"noopener">CVE-2026-53251</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: fix memory leak in error path of hci_alloc_dev() Early failures in = Bluetooth HCI UART configuration leak SRCU percpu memory. When device initi= alization fails before hci_register_dev() completes, the HCI_UNREGISTER fla=
    g is never set. As a result, when the device reference count reaches zero, = bt_host_release() evaluates this flag as false and falls back to a direct k= free(hdev). Because hci_release_dev() is bypassed, the SRCU struct initiali= zed early in hci_alloc_dev() is never cleaned up, resulting in a leak of pe= rcpu memory. Fix the leak by explicitly calling cleanup_srcu_struct() in th=
    e fallback (unregistered) branch of bt_host_release() before freeing the de= vice.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53252" target=3D= "_blank" rel=3D"noopener">CVE-2026-53252</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: Blu= etooth: MGMT: validate advertising TLV before type checks tlv_data_is_valid=
    () reads each advertising data field length from data[i], then inspects dat= a[i + 1] for managed EIR types before checking that the current field still=
    fits inside the supplied buffer. A malformed field whose length byte is th=
    e last byte of the buffer can therefore make the parser read one byte past = the advertising data. KASAN reported the following when a malformed MGMT_OP= _ADD_ADVERTISING request reached that path: BUG: KASAN: vmalloc-out-of-boun=
    ds in tlv_data_is_valid() Read of size 1 Call trace: tlv_data_is_valid() ad= d_advertising() hci_mgmt_cmd() hci_sock_sendmsg() Move the existing element= -length check before any type-octet inspection so each non-empty element is=
    proven to contain its type byte before the parser looks at data[i + 1].</t=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53255" target=3D= "_blank" rel=3D"noopener">CVE-2026-53255</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: cfg80211: enforce HE/EHT cap/oper consistency Xiang Mei reports that mac= 80211 could crash if eht_cap is set but eht_oper isn't. Rather than fixing = that for the individual user(s), enforce that both HE/EHT have consistent e= lements.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53257" target=3D= "_blank" rel=3D"noopener">CVE-2026-53257</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: fix leak if split 6 GHz scanning fails rdev-&gt;int_scan_req is leaked i=
    f cfg80211_scan() fails. Note that it's supposed to be released at ___cfg80= 211_scan_done() but this doesn't happen as rdev-&gt;scan_req is NULL at tha=
    t point, too, leading to the early return from the freeing function. unrefe= renced object 0xffff8881161d0800 (size 512): comm "wpa_supplicant", pid 379=
    , jiffies 4294749765 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 =
    00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 f0 81 13 16 8=
    1 88 ff ff ................ backtrace (crc c867fdb6): kmemleak_alloc+0x89/0= x90 __kmalloc_noprof+0x2fd/0x410 cfg80211_scan+0x133/0x730 nl80211_trigger_= scan+0xc69/0x1cc0 genl_family_rcv_msg_doit+0x204/0x2f0 genl_rcv_msg+0x431/0= x6b0 netlink_rcv_skb+0x143/0x3f0 genl_rcv+0x27/0x40 netlink_unicast+0x4f6/0= x820 netlink_sendmsg+0x797/0xce0 __sock_sendmsg+0xc4/0x160 ____sys_sendmsg+= 0x5e4/0x890 ___sys_sendmsg+0xf8/0x180 __sys_sendmsg+0x136/0x1e0 __x64_sys_s= endmsg+0x76/0xc0 x64_sys_call+0x13f0/0x17d0 Found by Linux Verification Cen= ter (linuxtesting.org).</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53258" target=3D= "_blank" rel=3D"noopener">CVE-2026-53258</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: dev= link: Release nested relation on devlink free devlink relation state is nor= mally released from devl_unregister(), which calls devlink_rel_put(). This = misses devlink instances that get a nested relation before registration and=
    then fail probe before devl_register() is reached. That flow can happen fo=
    r SFs. The child devlink gets linked to its parent before registration, the=
    n a later probe error calls devlink_free() directly. Since the instance was=
    never registered, devl_unregister() is not called and devlink-&gt;rel is l= eaked. Release any pending relation from devlink_free() as well. The regist= ered path is unchanged because devl_unregister() already clears devlink-&gt= ;rel before devlink_free() runs.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53261" target=3D= "_blank" rel=3D"noopener">CVE-2026-53261</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: 6lo= wpan: fix off-by-one in multicast context address compression The second me= mcpy in lowpan_iphc_mcast_ctx_addr_compress() uses &amp;data[1] as destinat= ion and &amp;ipaddr-&gt;s6_addr[11] as source, but both should be offset by=
    one: &amp;data[2] and &amp;ipaddr-&gt;s6_addr[12] respectively. This off-b= y-one has two consequences: 1. data[1] is overwritten with s6_addr[11], cor= rupting the RIID field in the compressed multicast address 2. data[5] is ne= ver written, so uninitialized kernel stack memory is transmitted over the n= etwork via lowpan_push_hc_data(), leaking kernel stack contents The correct=
    inline data layout must match what the decompression function lowpan_uncom= press_multicast_ctx_daddr() expects: data[0..1] =3D s6_addr[1..2] (flags/sc= ope + RIID) data[2..5] =3D s6_addr[12..15] (group ID) Also zero-initialize = the data array as a defensive measure against similar bugs in the future.</=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53263" target=3D= "_blank" rel=3D"noopener">CVE-2026-53263</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= filter: synproxy: add mutex to guard hook reference counting As the synprox=
    y infrastructure register netfilter hooks on-demand when a user adds the fi= rst iptables target or nftables expression, if done concurrently they can r= ace each other. Introduce a mutex to serialize the refcount control blocks = access from both frontends. While a per namespace mutex might be more effic= ient, it is not needed for target/expression like SYNPROXY.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53269" target=3D= "_blank" rel=3D"noopener">CVE-2026-53269</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ksm= bd: fix NULL-deref of opinfo-&gt;conn in oplock/lease break notifiers smb2_= oplock_break_noti() and smb2_lease_break_noti() read opinfo-&gt;conn into a=
    local with neither READ_ONCE() nor a NULL check. Both run from oplock_brea= k() after opinfo_get_list() has dropped ci-&gt;m_lock, so a concurrent SMB2=
    LOGOFF (session_fd_check()) can set op-&gt;conn =3D NULL under ci-&gt;m_lo=
    ck within that window. ksmbd_conn_r_count_inc(conn) then writes through NUL=
    L at offset 0xc4 -- a remotely triggerable oops. Guard both reads the way c= ompare_guid_key() already does: read opinfo-&gt;conn with READ_ONCE() and r= eturn early if it is NULL, before allocating the work struct so nothing lea= ks. A NULL conn means the client is gone and the break is moot, so return 0=
    ; oplock_break() treats that as success and runs the normal teardown.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53271" target=3D= "_blank" rel=3D"noopener">CVE-2026-53271</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ero= fs: fix use-after-free on sbi-&gt;sync_decompress z_erofs_decompress_kickof= f() can race with filesystem unmount, causing a use-after-free on sbi-&gt;s= ync_decompress. When I/O completes, z_erofs_endio() calls z_erofs_decompres= s_kickoff() to queue z_erofs_decompressqueue_work() asynchronously. Then, a= fter all folios are unlocked, unmount workflow can proceed and sbi will be = freed before accessing to sbi-&gt;sync_decompress. Thread (unmount) I/O com= pletion kworker queue_work z_erofs_decompressqueue_work (all folios are unl= ocked) cleanup_mnt .. erofs_kill_sb erofs_sb_free kfree(sbi) access sbi-&gt= ;sync_decompress // UAF!!</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53272" target=3D= "_blank" rel=3D"noopener">CVE-2026-53272</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net= /smc: fix sleep-inside-lock in __smc_setsockopt() causing local DoS A logic=
    flaw in __smc_setsockopt() allows a local unprivileged user to cause a Den= ial of Service (DoS) by holding the socket lock indefinitely. The function = __smc_setsockopt() calls copy_from_sockptr() while holding lock_sock(sk). B=
    y passing a userfaultfd-monitored memory page (or FUSE-backed memory on sys= tems where unprivileged userfaultfd is disabled) as the optval, an attacker=
    can halt execution during the copy operation, keeping the lock held. Combi= ned with asynchronous tear-down operations like shutdown(), this exhausts t=
    he kernel wq (kworkers) and triggers the hung task watchdog. [ 240.123456] = INFO: task kworker/u8:2 blocked for more than 120 seconds. [ 240.123489] Ca=
    ll Trace: [ 240.123501] smc_shutdown+... [ 240.123512] lock_sock_nested+...=
    This patch moves the user-space copy outside the lock_sock() critical sect= ion to prevent the issue.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53274" target=3D= "_blank" rel=3D"noopener">CVE-2026-53274</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: arm= _mpam: Check whether the config array is allocated before destroying it __d= estroy_component_cfg() is called to free the configuration array. It uses t=
    he embedded 'garbage' structure, which means the array has to be allocated.=
    If __destroy_component_cfg() is called from mpam_disable() before the conf= iguration was ever allocated, then a NULL pointer is dereferenced. Check fo=
    r this case and return early if the configuration is not allocated. __destr= oy_component_cfg() also frees the mbwu_state as this is allocated by __allo= cate_component_cfg(). As the mbwu_state is allocated after comp-&gt;cfg is = set, and is also under mpam_list_lock, only the first pointer needs checkin= g.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53278" target=3D= "_blank" rel=3D"noopener">CVE-2026-53278</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /gma500/oaktrail_lvds: fix hang on init failure The LVDS init code looks up=
    an I2C adapter using i2c_get_adapter() and tries to read the EDID before f= alling back to allocating and registering its own adapter. The error handli=
    ng does not separate these cases so on a late init failure it will try to d= eregister and free also an adapter that had previously been registered. Sin=
    ce i2c_get_adapter() takes another reference to the adapter, deregistration=
    hangs indefinitely while waiting for the reference to be released. Fix thi=
    s by only destroying adapters allocated during LVDS init on errors.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53279" target=3D= "_blank" rel=3D"noopener">CVE-2026-53279</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= mu: Fix NULL group-&gt;domain dereference in pci_dev_reset_iommu_done() Loc=
    al sashiko review pointed it out that group-&gt;domain could be NULL when a=
    default domain fails to allocate during the first probe, which can crash a=
    t domain-&gt;ops-&gt;attach_dev dereference in __iommu_attach_device() invo= ked by pci_dev_reset_iommu_done(). pci_dev_reset_iommu_prepare() is fine as=
    an old_domain pointer can be NULL. Skip the re-attach in pci_dev_reset_iom= mu_done() to fix the bug.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53280" target=3D= "_blank" rel=3D"noopener">CVE-2026-53280</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: x86= /kexec: Push kjump return address even for non-kjump kexec The version of p= urgatory code shipped by kexec-tools attempts to look above the top of its = stack to find a return address for a kjump, even in a non-kjump kexec. Afte=
    r the commit in Fixes: the word above the stack might not be there, leading=
    to a fault (which is at least now caught by my exception-handling code in = kexec). That commit fixed things for the actual kjump path, but no longer "= gratuitously" pushes the unused return address to the stack in the non-kjum=
    p path. Put that *back* in the non-kjump path, to prevent purgatory from cr= ashing when trying to access it.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53282" target=3D= "_blank" rel=3D"noopener">CVE-2026-53282</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= mu/amd: Bounds-check devid in __rlookup_amd_iommu() iommu_device_register()=
    walks every device on the PCI bus via bus_for_each_dev() and calls amd_iom= mu_probe_device() for each. The inlined check_device() path computes the de= vice's sbdf, calls rlookup_amd_iommu() to find the owning IOMMU, and only a= fterwards verifies devid &lt;=3D pci_seg-&gt;last_bdf. __rlookup_amd_iommu(=
    ) indexes rlookup_table[devid] with no bounds check of its own, so for a PC=
    I device whose BDF is not described by the IVRS, the lookup reads past the = end of the allocation before the caller's bounds check can run. This was ha= rmless before commit e874c666b15b ("iommu/amd: Change rlookup, irq_lookup, = and alias to use kvalloc()"): the table was a zeroed page-order allocation,=
    so the over-read returned NULL and the caller's NULL check skipped the dev= ice. After that commit the table is a tight kvcalloc() and the over-read re= turns adjacent slab contents, which check_device() then dereferences as a s= truct amd_iommu *, causing a boot-time GPF. Seen on Google Compute Engine c= t6e VMs, where the virtualized IVRS describes only the four TPU endpoints 0= 0:04.0-07.0; the gVNIC at 00:08.0 (devid 0x40) indexes 56 bytes past the 45= 6-byte allocation, into the adjacent kmalloc-512 slab object: pci 0000:00:0= 4.0: Adding to iommu group 0 pci 0000:00:05.0: Adding to iommu group 1 pci = 0000:00:06.0: Adding to iommu group 2 pci 0000:00:07.0: Adding to iommu gro=
    up 3 Oops: general protection fault, probably for non-canonical address 0x3= a64695f78746382: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 1 Comm: swapper/0 N=
    ot tainted 6.18.22 #1 Hardware name: Google Google Compute Engine/Google Co= mpute Engine, BIOS Google 12/06/2025 RIP: 0010:amd_iommu_probe_device+0x54/= 0x3a0 Call Trace: __iommu_probe_device+0x107/0x520 probe_iommu_group+0x29/0= x50 bus_for_each_dev+0x7e/0xe0 iommu_device_register+0xc9/0x240 iommu_go_to= _state+0x9c0/0x1c60 amd_iommu_init+0x14/0x40 pci_iommu_init+0x16/0x60 do_on= e_initcall+0x47/0x2f0 Guard the array access in __rlookup_amd_iommu(). With=
    the fix applied on 6.18.22, the gVNIC at 00:08.0 is skipped cleanly and th=
    e VM boots.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53283" target=3D= "_blank" rel=3D"noopener">CVE-2026-53283</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amd/display: Wrap DCN32 phantom-plane allocation in DC_RUN_WITH_PREEMPTION= _ENABLED [Why] dcn32_validate_bandwidth() wraps dcn32_internal_validate_bw(=
    ) with DC_FP_START()/DC_FP_END(). In x86 non-RT, DC_FP_START takes fpregs_l= ock(), which disables local softirqs. The DML1 path through dcn32_enable_ph= antom_plane() calls kvzalloc() to allocate ~335 KiB for dc_plane_state. Thi=
    s triggers the vmalloc path, which calls BUG_ON(in_interrupt()) because it'=
    s invoked within the FPU-enabled (softirq disabled) region, leading to a ke= rnel crash. [How] Wrap the dc_state_create_phantom_plane() call with the DC= _RUN_WITH_PREEMPTION_ENABLED() macro to allow preemption during this memory=
    allocation. (cherry picked from commit 885ccbef7b94a8b38f69c4211c679021aa2= 7ad11)</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53285" target=3D= "_blank" rel=3D"noopener">CVE-2026-53285</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: idp=
    f: fix double free and use-after-free in aux device error paths When auxili= ary_device_add() fails in idpf_plug_vport_aux_dev() or idpf_plug_core_aux_d= ev(), the err_aux_dev_add label calls auxiliary_device_uninit() and falls t= hrough to err_aux_dev_init. The uninit call will trigger put_device(), whic=
    h invokes the release callback (idpf_vport_adev_release / idpf_core_adev_re= lease) that frees iadev. The fall-through then reads adev-&gt;id from the f= reed iadev for ida_free() and double-frees iadev with kfree(). Free the IDA=
    slot and clear the back-pointer before uninit, while adev is still valid, = then return immediately. Commit 65637c3a1811 ("idpf: fix UAF in RDMA core a=
    ux dev deinitialization") fixed the same use-after-free in the matching unp= lug path in this file but missed both probe error paths.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53286" target=3D= "_blank" rel=3D"noopener">CVE-2026-53286</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: aud= it: fix incorrect inheritable capability in CAPSET records __audit_log_caps= et() records the effective capability set into the inheritable field due to=
    a copy-paste error. Every CAPSET audit record therefore reports cap_pi (pr= ocess inheritable) with the value of cap_effective instead of cap_inheritab= le. This silently corrupts audit data used for compliance and forensic anal= ysis: an attacker who modifies inheritable capabilities to prepare for a pr= ivilege-escalating exec would have the change masked in the audit trail. Th=
    e bug has been present since the original introduction of CAPSET audit reco= rds in 2008.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53287" target=3D= "_blank" rel=3D"noopener">CVE-2026-53287</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: arm= 64: Reserve an extra page for early kernel mapping The final part of [data,=
    end) segment may overflow into the next page of init_pg_end[1] which is th=
    e gap page before early_init_stack[2]: [1] crash_arm64_v9.0.1&gt; vtop ffff= ffed00601000 VIRTUAL PHYSICAL ffffffed00601000 83401000 PAGE DIRECTORY: fff= fffecffd62000 PGD: ffffffecffd62da0 =3D&gt; 10000000833fb003 PMD: ffffff800= 33fb018 =3D&gt; 10000000833fe003 PTE: ffffff80033fe008 =3D&gt; 68000083401f=
    03 PAGE: 83401000 PTE PHYSICAL FLAGS 68000083401f03 83401000 (VALID|SHARED|= AF|NG|PXN|UXN) PAGE PHYSICAL MAPPING INDEX CNT FLAGS fffffffec00d0040 83401= 000 0 0 1 4000 reserved [2] ffffffed002c8000 (r) __pi__data ffffffed0054e00=
    0 (d) __pi___bss_start ffffffed005f5000 (b) __pi_init_pg_dir ffffffed005fe0=
    00 (b) __pi_init_pg_end ffffffed005ff000 (B) early_init_stack ffffffed00608= 000 (b) __pi__end For 4K pages, the early kernel mapping may use 2MB block = entries but the kernel segments are only 64KB aligned. Segment boundaries t= hat fall within a 2MB block therefore require a PTE table so that different=
    attributes can be applied on either side of the boundary. KERNEL_SEGMENT_C= OUNT still correctly counts the five permanent kernel VMAs registered by de= clare_kernel_vmas(). However, since commit 5973a62efa34 ("arm64: map [_text=
    , _stext) virtual address range non-executable+read-only"), the early mappe=
    r also maps [_text, _stext) separately from [_stext, _etext). This adds one=
    more early-only split and can require one more page-table page than the ex= isting EARLY_SEGMENT_EXTRA_PAGES allowance reserves. Increase the 4K-page e= arly mapping allowance by one page to cover that additional split. [catalin= .marinas@arm.com: rewrote part of the commit log] [catalin.marinas@arm.com:=
    expanded the code comment]</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53288" target=3D= "_blank" rel=3D"noopener">CVE-2026-53288</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ice=
    : fix NULL pointer dereference in ice_reset_all_vfs() ice_reset_all_vfs() i= gnores the return value of ice_vf_rebuild_vsi(). When the VSI rebuild fails=
    (e.g. during NVM firmware update via nvmupdate64e), ice_vsi_rebuild() tear=
    s down the VSI on its error path, leaving txq_map and rxq_map as NULL. The = subsequent unconditional call to ice_vf_post_vsi_rebuild() leads to a NULL = pointer dereference in ice_ena_vf_q_mappings() when it accesses vsi-&gt;txq= _map[0]. The single-VF reset path in ice_reset_vf() already handles this co= rrectly by checking the return value of ice_vf_reconfig_vsi() and skipping = ice_vf_post_vsi_rebuild() on failure. Apply the same pattern to ice_reset_a= ll_vfs(): check the return value of ice_vf_rebuild_vsi() and skip ice_vf_po= st_vsi_rebuild() and ice_eswitch_attach_vf() on failure. The VF is left saf= ely disabled (ICE_VF_STATE_INIT not set, VFGEN_RSTAT not set to VFACTIVE) a=
    nd can be recovered via a VFLR triggered by a PCI reset of the VF (sysfs re= set or driver rebind). Note that this patch does not prevent the VF VSI reb= uild from failing during NVM update - the underlying cause is firmware bein=
    g in a transitional state while the EMP reset is processed, which can cause=
    Admin Queue commands (ice_add_vsi, ice_cfg_vsi_lan) to fail. This patch on=
    ly prevents the subsequent NULL pointer dereference that crashes the kernel=
    when the rebuild does fail. crash&gt; bt PID: 50795 TASK: ff34c9ee708dc680=
    CPU: 1 COMMAND: "kworker/u512:5" #0 [ff72159bcfe5bb50] machine_kexec at ff= ffffffaa8850ee #1 [ff72159bcfe5bba8] __crash_kexec at ffffffffaaa15fba #2 [= ff72159bcfe5bc68] crash_kexec at ffffffffaaa16540 #3 [ff72159bcfe5bc70] oop= s_end at ffffffffaa837eda #4 [ff72159bcfe5bc90] page_fault_oops at ffffffff= aa893997 #5 [ff72159bcfe5bce8] exc_page_fault at ffffffffab528595 #6 [ff721= 59bcfe5bd10] asm_exc_page_fault at ffffffffab600bb2 [exception RIP: ice_ena= _vf_q_mappings+0x79] RIP: ffffffffc0a85b29 RSP: ff72159bcfe5bdc8 RFLAGS: 00= 010206 RAX: 00000000000f0000 RBX: ff34c9efc9c00000 RCX: 0000000000000000 RD=
    X: 0000000000000000 RSI: 0000000000000010 RDI: ff34c9efc9c00000 RBP: ff34c9= efc27d4828 R8: 0000000000000093 R9: 0000000000000040 R10: ff34c9efc27d4828 = R11: 0000000000000040 R12: 0000000000100000 R13: 0000000000000010 R14: R15:=
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ff72159bcfe5bdf8] ice_sri= ov_post_vsi_rebuild at ffffffffc0a85e2e [ice] #8 [ff72159bcfe5be08] ice_res= et_all_vfs at ffffffffc0a920b4 [ice] #9 [ff72159bcfe5be48] ice_service_task=
    at ffffffffc0a31519 [ice] #10 [ff72159bcfe5be88] process_one_work at fffff= fffaa93dca4 #11 [ff72159bcfe5bec8] worker_thread at ffffffffaa93e9de #12 [f= f72159bcfe5bf18] kthread at ffffffffaa946663 #13 [ff72159bcfe5bf50] ret_fro= m_fork at ffffffffaa8086b9 The panic occurs attempting to dereference the N= ULL pointer in RDX at ice_sriov.c:294, which loads vsi-&gt;txq_map (offset = 0x4b8 in ice_vsi). The faulting VSI is an allocated slab object but not ful=
    ly initialized after a failed ice_vsi_rebuild(): crash&gt; struct ice_vsi 0= xff34c9efc27d4828 netdev =3D 0x0, rx_rings =3D 0x0, tx_rings =3D 0x0, q_vec= tors =3D 0x0, txq_map =3D 0x0, rxq_map =3D 0x0, alloc_txq =3D 0x10, num_txq=
    =3D 0x10, alloc_rxq =3D 0x10, num_rxq =3D 0x10, The nvmupdate64e process w=
    as performing NVM firmware update: crash&gt; bt 0xff34c9edd1a30000 PID: 498=
    58 TASK: ff34c9edd1a30000 CPU: 1 COMMAND: "nvmupdate64e" #0 [ff72159bcd6176= 18] __schedule at ffffffffab5333f8 #4 [ff72159bcd617750] ice_sq_send_cmd at=
    ffffffffc0a35347 [ice] #5 [ff72159bcd6177a8] ice_sq_send_cmd_retry at ffff= ffffc0a35b47 [ice] #6 [ff72159bcd617810] ice_aq_send_cmd at ffffffffc0a3801=
    8 [ice] #7 [ff72159bcd617848] ice_aq_read_nvm at ffffffffc0a40254 [ice] #8 = ---truncated---</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53289" target=3D= "_blank" rel=3D"noopener">CVE-2026-53289</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: ALS=
    A: hda/conexant: Fix missing error check for jack detection In cx_probe(), = the return value of snd_hda_jack_detect_enable_callback() is ignored. This = function returns a pointer, and if it fails (e.g., due to memory allocation=
    failure), it returns an error pointer which must be checked using IS_ERR()=
    . If the registration fails, the driver continues to probe, but the jack de= tection callback will not be registered. This can lead to a kernel crash la= ter when the driver attempts to handle jack events or accesses the uninitia= lized structure. Check the return value using IS_ERR() and propagate the er= ror via PTR_ERR() to the probe caller.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53291" target=3D= "_blank" rel=3D"noopener">CVE-2026-53291</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : phonet: do not BUG_ON() in pn_socket_autobind() on failed bind syzbot rep= orted a kernel BUG triggered from pn_socket_sendmsg() via pn_socket_autobin= d(): kernel BUG at net/phonet/socket.c:213! RIP: 0010:pn_socket_autobind ne= t/phonet/socket.c:213 [inline] RIP: 0010:pn_socket_sendmsg+0x240/0x250 net/= phonet/socket.c:421 Call Trace: sock_sendmsg_nosec+0x112/0x150 net/socket.c= :797 __sock_sendmsg net/socket.c:812 [inline] __sys_sendto+0x402/0x590 net/= socket.c:2280 ... pn_socket_autobind() calls pn_socket_bind() with port 0 a= nd, on -EINVAL, assumes the socket was already bound and asserts that the p= ort is non-zero: err =3D pn_socket_bind(sock, ..., sizeof(struct sockaddr_p= n)); if (err !=3D -EINVAL) return err; BUG_ON(!pn_port(pn_sk(sock-&gt;sk)-&= gt;sobject)); return 0; /* socket was already bound */ However pn_socket_bi= nd() also returns -EINVAL when sk-&gt;sk_state is not TCP_CLOSE, even when = the socket has never been bound and pn_port() is still 0. In that case the = BUG_ON() fires and panics the kernel from a user-triggerable path. Treat th=
    e "bind returned -EINVAL but pn_port() is still 0" case as a regular error = and propagate -EINVAL to the caller instead of crashing. Existing callers a= lready translate a non-zero return from pn_socket_autobind() into -ENOBUFS/= -EAGAIN, so returning -EINVAL here only changes behaviour from panic to a n= ormal errno.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53292" target=3D= "_blank" rel=3D"noopener">CVE-2026-53292</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amdgpu: fix AMDGPU_INFO_READ_MMR_REG There were multiple issues in that co= de. First of all the order between the reset semaphore and the mm_lock was = wrong (e.g. copy_to_user) was called while holding the lock. Then we alloca= ted memory while holding the reset semaphore which is also a pretty big bug=
    and can deadlock. Then we used down_read_trylock() instead of waiting for = the reset to finish. (cherry picked from commit 361b6e6b303d4b691f6c5974d3e= aab67ca6dd90e)</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53293" target=3D= "_blank" rel=3D"noopener">CVE-2026-53293</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mai= lbox: mailbox-test: don't free the reused channel The RX channel can be ali= ased to the TX channel if it has a different MMIO. This special case needs =
    to be handled when freeing the channels otherwise a double-free occurs.</td=

    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53294" target=3D= "_blank" rel=3D"noopener">CVE-2026-53294</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mai= lbox: add sanity check for channel array Fail gracefully if there is no cha= nnel array attached to the mailbox controller. Otherwise the later derefere= nce will cause an OOPS which might not be seen because mailbox controllers = might instantiate very early. Remove the comment explaining the obvious whi=
    le here.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53295" target=3D= "_blank" rel=3D"noopener">CVE-2026-53295</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: mai= lbox: mailbox-test: free channels on probe error On probe error, free the p= reviously obtained channels. This not only prevents a leak, but also UAF sc= enarios because the client structure will be removed nonetheless because it=
    was allocated with devm.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53296" target=3D= "_blank" rel=3D"noopener">CVE-2026-53296</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : mana: Guard mana_remove against double invocation If PM resume fails (e.g=
    ., mana_attach() returns an error), mana_probe() calls mana_remove(), which=
    tears down the device and sets gd-&gt;gdma_context =3D NULL and gd-&gt;dri= ver_data =3D NULL. However, a failed resume callback does not automatically=
    unbind the driver. When the device is eventually unbound, mana_remove() is=
    invoked a second time. Without a NULL check, it dereferences gc-&gt;dev wi=
    th gc =3D=3D NULL, causing a kernel panic. Add an early return if gdma_cont= ext or driver_data is NULL so the second invocation is harmless. Move the d=
    ev =3D gc-&gt;dev assignment after the guard so it cannot dereference NULL.= </td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53297" target=3D= "_blank" rel=3D"noopener">CVE-2026-53297</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : airoha: Move ndesc initialization at end of airoha_qdma_init_rx_queue() I=
    f queue entry or DMA descriptor list allocation fails in airoha_qdma_init_r= x_queue routine, airoha_qdma_cleanup() will trigger a NULL pointer derefere= nce running netif_napi_del() for RX queue NAPIs since netif_napi_add() has = never been executed to this particular RX NAPI. The issue is due to the ear=
    ly ndesc initialization in airoha_qdma_init_rx_queue() since airoha_qdma_cl= eanup() relies on ndesc value to check if the queue is properly initialized=
    . Fix the issue moving ndesc initialization at end of airoha_qdma_init_tx r= outine. Move page_pool allocation after descriptor list allocation in order=
    to avoid memory leaks if desc allocation fails.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53298" target=3D= "_blank" rel=3D"noopener">CVE-2026-53298</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : airoha: Move ndesc initialization at end of airoha_qdma_init_tx() If queu=
    e entry list allocation fails in airoha_qdma_init_tx_queue routine, airoha_= qdma_cleanup_tx_queue() will trigger a NULL pointer dereference accessing t=
    he queue entry array. The issue is due to the early ndesc initialization in=
    airoha_qdma_init_tx_queue(). Fix the issue moving ndesc initialization at = end of airoha_qdma_init_tx routine.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53299" target=3D= "_blank" rel=3D"noopener">CVE-2026-53299</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: res= et: amlogic: t7: Fix null reset ops Fix missing reset ops causing kernel nu=
    ll pointer dereference. This SOC's reset is currently not used yet.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53301" target=3D= "_blank" rel=3D"noopener">CVE-2026-53301</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: cry= pto: eip93 - fix hmac setkey algo selection eip93_hmac_setkey() allocates a=
    temporary ahash transform for computing HMAC ipad/opad key material. The a= llocation uses the driver-specific cra_driver_name (e.g. "sha256-eip93") bu=
    t passes CRYPTO_ALG_ASYNC as the mask, which excludes async algorithms. Sin=
    ce the EIP93 hash algorithms are the only ones registered under those drive=
    r names and they are inherently async, the lookup is self-contradictory and=
    always fails with -ENOENT. When called from the AEAD setkey path, this fai= lure leaves the SA record partially initialized with zeroed digest fields. =
    A subsequent crypto operation then dereferences a NULL pointer in the reque=
    st context, resulting in a kernel panic: ``` pc : eip93_aead_handle_result+= 0xc8c/0x1240 [crypto_hw_eip93] lr : eip93_aead_handle_result+0xbec/0x1240 [= crypto_hw_eip93] sp : ffffffc082feb820 x29: ffffffc082feb820 x28: ffffff801= 1043980 x27: 0000000000000000 x26: 0000000000000000 x25: ffffffc078da0bc8 x= 24: 0000000091043980 x23: ffffff8004d59e50 x22: ffffff8004d59410 x21: fffff= f8004d593c0 x20: ffffff8004d593c0 x19: ffffff8004d4f300 x18: 00000000000000=
    00 x17: 0000000000000000 x16: 0000000000000000 x15: 0000007fda7aa498 x14: 0= 000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000= 000000 x10: fffffffff8127a80 x9 : 0000000000000000 x8 : ffffff8004d4f380 x7=
    : 0000000000000000 x6 : 000000000000003f x5 : 0000000000000040 x4 : 000000= 0000000008 x3 : 0000000000000009 x2 : 0000000000000008 x1 : 000000002800000=
    3 x0 : ffffff8004d388c0 Code: 910142b6 f94012e0 f9002aa0 f90006d3 (f9400740=
    ) ``` The reported symbol eip93_aead_handle_result+0xc8c is a resolution ar= tifact from static functions being merged under the nearest exported symbol=
    . Decoding the faulting sequence: ``` 910142b6 ADD X22, X21, #0x50 f94012e0=
    LDR X0, [X23, #0x20] f9002aa0 STR X0, [X21, #0x50] f90006d3 STR X19, [X22,=
    #0x8] f9400740 LDR X0, [X26, #0x8] ``` The faulting LDR at [X26, #0x8] is = loading ctx-&gt;flags (offset 8 in eip93_hash_ctx), where ctx has been reso= lved to NULL from a partially initialized or unreachable transform context = following the failed setkey. Fix this by dropping the CRYPTO_ALG_ASYNC mask=
    from the crypto_alloc_ahash() call. The code already handles async complet= ion correctly via crypto_wait_req(), so there is no requirement to restrict=
    the lookup to synchronous algorithms. Note that hashing a single 64-byte b= lock through the hardware is likely slower than doing it in software due to=
    the DMA round-trip overhead, but offloading it may still spare CPU cycles =
    on the slower embedded cores where this IP is found. [Detailed investigatio=
    n report of this bug]</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53302" target=3D= "_blank" rel=3D"noopener">CVE-2026-53302</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: f2f=
    s: protect extension_list reading with sb_lock in f2fs_sbi_show() In f2fs_s= bi_show(), the extension_list, extension_count and hot_ext_count are read w= ithout holding sbi-&gt;sb_lock. If a concurrent sysfs store modifies the ex= tension list via f2fs_update_extension_list(), the show path may read incon= sistent count and array contents, potentially leading to out-of-bounds acce=
    ss or displaying stale data. Fix this by holding sb_lock around the entire = extension list read and format operation.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53303" target=3D= "_blank" rel=3D"noopener">CVE-2026-53303</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: scs=
    i: sg: Resolve soft lockup issue when opening /dev/sgX The parameter def_re= served_size defines the default buffer size reserved for each Sg_fd and sho= uld be restricted to a range between 0 and 1,048,576 (see https://tldp.org/= HOWTO/SCSI-Generic-HOWTO/proc.html). Although the function sg_proc_write_dr= essz enforces this limit, it is possible to bypass it by directly modifying=
    the module parameter as shown below, which then causes a soft lockup: echo=
    -1 &gt; /sys/module/sg/parameters/def_reserved_size exec 4&lt;&gt; /dev/sg=
    0 watchdog: BUG: soft lockup - CPU#5 stuck for 26 seconds! [bash:537] Modul=
    es loaded: CPU: 5 UID: 0 PID: 537 Command: bash, kernel version 6.19.0-rc3+=
    #134, PREEMPT disabled Hardware: QEMU Standard PC (i440FX + PIIX, 1996), B= IOS version 1.16.1-2.fc37 dated 04/01/2014 ... Call Trace: sg_build_reserve= +0x5c/0xa0 sg_add_sfp+0x168/0x270 sg_open+0x16e/0x340 chrdev_open+0xbe/0x23=
    0 do_dentry_open+0x175/0x480 vfs_open+0x34/0xf0 do_open+0x265/0x3d0 path_op= enat+0x110/0x290 do_filp_open+0xc3/0x170 do_sys_openat2+0x71/0xe0 __x64_sys= _openat+0x6d/0xa0 do_syscall_64+0x62/0x310 entry_SYSCALL_64_after_hwframe+0= x76/0x7e The fix is to use module_param_cb to validate and reject invalid v= alues assigned to def_reserved_size.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53304" target=3D= "_blank" rel=3D"noopener">CVE-2026-53304</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: usb=
    : typec: ps883x: Fix Oops at unbind When trying to unbind a device in order=
    to bind to it vfio-platform as: echo bc0000.geniqup &gt; /sys/bus/platform= /devices/bc0000.geniqup/driver/unbind I get the following Oops: [ 436.47863=
    9] Unable to handle kernel NULL pointer dereference at virtual address 0000= 000000000020 [ 436.487762] Mem abort info: [ 436.490716] ESR =3D 0x00000000= 96000004 [ 436.494595] EC =3D 0x25: DABT (current EL), IL =3D 32 bits [ 436= .500071] SET =3D 0, FnV =3D 0 [ 436.503250] EA =3D 0, S1PTW =3D 0 [ 436.506= 505] FSC =3D 0x04: level 0 translation fault [ 436.511533] Data abort info:=
    [ 436.514558] ISV =3D 0, ISS =3D 0x00000004, ISS2 =3D 0x00000000 [ 436.520= 215] CM =3D 0, WnR =3D 0, TnD =3D 0, TagAccess =3D 0 [ 436.525436] GCS =3D =
    0, Overlay =3D 0, DirtyBit =3D 0, Xs =3D 0 [ 436.530918] user pgtable: 4k p= ages, 48-bit VAs, pgdp=3D00000008861a9000 [ 436.537554] [0000000000000020] = pgd=3D0000000000000000, p4d=3D0000000000000000 [ 436.544548] Internal error=
    : Oops: 0000000096000004 [#1] SMP [ 436.550374] Modules linked in: [ 436.55= 3542] CPU: 2 UID: 0 PID: 671 Comm: bash Tainted: G W 7.0.0-rc3-g56fcdd0911a= 5-dirty #2 PREEMPT [ 436.564440] Tainted: [W]=3DWARN [ 436.567515] Hardware=
    name: LENOVO 91B6CTO1WW/3796, BIOS O6NKT3BA 05/02/2025 [ 436.574675] pstat=
    e: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=3D--) [ 436.581841] =
    pc : ps883x_retimer_remove+0x14/0x94 [ 436.586605] lr : i2c_device_remove+0= x28/0x84 [ 436.591017] sp : ffff8000847137c0 That's because the ps883x_reti= mer_remove() retrieves the driver data from i2c_get_clientdata() which was = never set at probe. So, add i2c_set_clientdata() at the end of the probe.</=

    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53305" target=3D= "_blank" rel=3D"noopener">CVE-2026-53305</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: tty=
    : hvc_iucv: fix off-by-one in number of supported devices MAX_HVC_IUCV_LINE=
    S =3D=3D HVC_ALLOC_TTY_ADAPTERS =3D=3D 8. This is the number of entries in:=
    static struct hvc_iucv_private *hvc_iucv_table[MAX_HVC_IUCV_LINES]; Someti= mes hvc_iucv_table[] is limited by: (a) if (num &gt; hvc_iucv_devices) // f=
    or error detection or (b) for (i =3D 0; i &lt; hvc_iucv_devices; i++) // in=
    2 places (so these 2 don't agree; second one appears to be correct to me.)=
    hvc_iucv_devices can be 0..8. This is a counter. (c) if (hvc_iucv_devices = &gt; MAX_HVC_IUCV_LINES) If hvc_iucv_devices =3D=3D 8, (a) allows the code =
    to access hvc_iucv_table[8]. Oops.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53306" target=3D= "_blank" rel=3D"noopener">CVE-2026-53306</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: pin= ctrl: pinconf-generic: Fully validate 'pinmux' property The pinconf_generic= _parse_dt_pinmux() assumes that the 'pinmux' property is not empty when pre= sent. This might be not true. With that, the allocator will give a special = value in return and not NULL which lead to the crash when trying to access = that (invalid) memory. Fix that by fully validating 'pinmux' value, includi=
    ng its length.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53307" target=3D= "_blank" rel=3D"noopener">CVE-2026-53307</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: pow= er: supply: max77705: Free allocated workqueue and fix removal order Use de=
    vm interface for allocating workqueue to fix two bugs at the same time: 1. = Driver leaks the memory on remove(), because the workqueue is not destroyed=
    . 2. Driver allocates workqueue and then registers interrupt handlers with = devm interface. This means that probe error paths will not use a reversed o= rder, but first destroy the workqueue and then, via devm release handlers, = free the interrupt. The interrupt handler schedules work on this exact work= queue, thus if interrupt is hit in this short time window - after destroyin=
    g workqueue, but before devm() frees the interrupt - the schedulled work wi=
    ll lead to use of freed memory. Change is not equivalent in the workqueue i= tself: use non-legacy API which does not set (__WQ_LEGACY | WQ_MEM_RECLAIM)=
    . The workqueue is used to update power supply (power_supply_changed()) sta= tus, thus there is no point to run it for memory reclaim. Note that dev_nam= e() is not directly used in second argument to prevent possible unlikely pa= rsing any "%" character in device name as format.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53308" target=3D= "_blank" rel=3D"noopener">CVE-2026-53308</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: soc= /tegra: cbb: Fix cross-fabric target timeout lookup When a fabric receives =
    an error interrupt, the error may have occurred on a different fabric. The = target timeout lookup was using the wrong base address (cbb-&gt;regs) with = offsets from a different fabric's target map, causing a kernel page fault. = Unable to handle kernel paging request at virtual address ffff80000954cc00 =
    pc : tegra234_cbb_get_tmo_slv+0xc/0x28 Call trace: tegra234_cbb_get_tmo_slv= +0xc/0x28 print_err_notifier+0x6c0/0x7d0 tegra234_cbb_isr+0xe4/0x1b4 Add te= gra234_cbb_get_fabric() to look up the correct fabric device using fab_id, = and use its base address for accessing target timeout registers.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53310" target=3D= "_blank" rel=3D"noopener">CVE-2026-53310</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: fus=
    e: fix uninit-value in fuse_dentry_revalidate() fuse_dentry_revalidate() ma=
    y be called with a dentry that didn't had -&gt;d_time initialised. The issu=
    e was found with KMSAN, where lookup_open() calls __d_alloc(), followed by = d_revalidate(), as shown below: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D BUG: KMSAN: uninit-value in fuse= _dentry_revalidate+0x150/0x13d0 fs/fuse/dir.c:394 fuse_dentry_revalidate+0x= 150/0x13d0 fs/fuse/dir.c:394 d_revalidate fs/namei.c:1030 [inline] lookup_o= pen fs/namei.c:4405 [inline] open_last_lookups fs/namei.c:4583 [inline] pat= h_openat+0x1614/0x64c0 fs/namei.c:4827 do_file_open+0x2aa/0x680 fs/namei.c:= 4859 [...] Uninit was created at: slab_post_alloc_hook mm/slub.c:4466 [inli= ne] slab_alloc_node mm/slub.c:4788 [inline] kmem_cache_alloc_lru_noprof+0x3= 82/0x1280 mm/slub.c:4807 __d_alloc+0x55/0xa00 fs/dcache.c:1740 d_alloc_para= llel+0x99/0x2740 fs/dcache.c:2604 lookup_open fs/namei.c:4398 [inline] open= _last_lookups fs/namei.c:4583 [inline] path_openat+0x135f/0x64c0 fs/namei.c= :4827 do_file_open+0x2aa/0x680 fs/namei.c:4859 [...] =3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53311" target=3D= "_blank" rel=3D"noopener">CVE-2026-53311</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: iom= mu/riscv: Remove overflows on the invalidation path Since RISC-V supports a=
    sign extended page table it should support a gather-&gt;end of ULONG_MAX, = but if this happens it will infinite loop because of the overflow. Also avo=
    id overflow computing the length by moving the +1 to the other side of the = &lt;</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53312" target=3D= "_blank" rel=3D"noopener">CVE-2026-53312</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amd/display: Avoid NULL dereference in dc_dmub_srv error paths In dc_dmub_= srv_log_diagnostic_data() and dc_dmub_srv_enable_dpia_trace(). Both functio=
    ns check: if (!dc_dmub_srv || !dc_dmub_srv-&gt;dmub) and then call DC_LOG_E= RROR() inside that block. DC_LOG_ERROR() uses dc_dmub_srv-&gt;ctx internall=
    y. So if dc_dmub_srv is NULL, the logging itself can dereference a NULL poi= nter and cause a crash. Fix this by splitting the checks. First check if dc= _dmub_srv is NULL and return immediately. Then check dc_dmub_srv-&gt;dmub a=
    nd log the error only when dc_dmub_srv is valid. Fixes the below: ../displa= y/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_data() error: we previous=
    ly assumed 'dc_dmub_srv' could be null (see line 961) ../display/dc/dc_dmub= _srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: we previously assumed 'd= c_dmub_srv' could be null (see line 1166)</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53313" target=3D= "_blank" rel=3D"noopener">CVE-2026-53313</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: pad= ata: Put CPU offline callback in ONLINE section to allow failure syzbot rep= orted the following warning: DEAD callback error for CPU1 WARNING: kernel/c= pu.c:1463 at _cpu_down+0x759/0x1020 kernel/cpu.c:1463, CPU#0: syz.0.1960/14= 614 at commit 4ae12d8bd9a8 ("Merge tag 'kbuild-fixes-7.0-2' of git://git.ke= rnel.org/pub/scm/linux/kernel/git/kbuild/linux") which tglx traced to padat= a_cpu_dead() given it's the only sub-CPUHP_TEARDOWN_CPU callback that retur=
    ns an error. Failure isn't allowed in hotplug states before CPUHP_TEARDOWN_= CPU so move the CPU offline callback to the ONLINE section where failure is=
    possible.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53314" target=3D= "_blank" rel=3D"noopener">CVE-2026-53314</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amd/ras: Fix NULL deref in ras_core_get_utc_second_timestamp() ras_core_ge= t_utc_second_timestamp() retrieves the current UTC timestamp (in seconds si= nce the Unix epoch) through a platform-specific RAS system callback and is = used for timestamping RAS error events. The function checks ras_core in the=
    conditional statement before calling the sys_fn callback. However, when th=
    e condition fails, the function prints an error message using ras_core-&gt;= dev. If ras_core is NULL, this can lead to a potential NULL pointer derefer= ence when accessing ras_core-&gt;dev. Add an early NULL check for ras_core =
    at the beginning of the function and return 0 when the pointer is not valid=
    . This prevents the dereference and makes the control flow clearer.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53315" target=3D= "_blank" rel=3D"noopener">CVE-2026-53315</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: drm= /amd/ras: Fix NULL deref in ras_core_ras_interrupt_detected() Fixes a NULL = pointer dereference when ras_core is NULL and ras_core-&gt;dev is accessed =
    in the error path. Reported by: Dan Carpenter &lt;dan.carpenter@linaro.org&= gt;</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53316" target=3D= "_blank" rel=3D"noopener">CVE-2026-53316</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: mt7921: Place upper limit on station AID Any station configured wi=
    th an AID over 20 causes a firmware crash. This situation occurred in our t= esting using an AP interface on 7922 hardware, with a modified hostapd, sou= rced from Mediatek's OpenWRT feeds. In stock hostapd, station AIDs begin co= unting at 1, and this configuration is prevented with an upper limit on ass= ociated stations. However, the modified hostapd began allocation at 65, whi=
    ch caused the firmware to crash. This fix does not allow these AIDs to work=
    , but will prevent the firmware crash. This crash was only seen on IFTYPE_A=
    P interfaces, and the fix does not appear to have an effect on IFTYPE_STATI=
    ON behavior.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53317" target=3D= "_blank" rel=3D"noopener">CVE-2026-53317</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: wif=
    i: mt76: mt7925: prevent NULL pointer dereference in mt7925_tx_check_aggr()=
    Move the NULL check for 'sta' before dereferencing it to prevent a possibl=
    e crash.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53318" target=3D= "_blank" rel=3D"noopener">CVE-2026-53318</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: blk= -wbt: remove WARN_ON_ONCE from wbt_init_enable_default() wbt_init_enable_de= fault() uses WARN_ON_ONCE to check for failures from wbt_alloc() and wbt_in= it(). However, both are expected failure paths: - wbt_alloc() can return NU=
    LL under memory pressure (-ENOMEM) - wbt_init() can fail with -EBUSY if wbt=
    is already registered syzbot triggers this by injecting memory allocation = failures during MTD partition creation via ioctl(BLKPG), causing a spurious=
    warning. wbt_init_enable_default() is a best-effort initialization called = from blk_register_queue() with a void return type. Failure simply means the=
    disk operates without writeback throttling, which is harmless. Replace WAR= N_ON_ONCE with plain if-checks, consistent with how wbt_set_lat() in the sa=
    me file already handles these failures. Add a pr_warn() for the wbt_init() = failure to retain diagnostic information without triggering a full stack tr= ace.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53319" target=3D= "_blank" rel=3D"noopener">CVE-2026-53319</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: nil= fs2: reject zero bd_oblocknr in nilfs_ioctl_mark_blocks_dirty() nilfs_ioctl= _mark_blocks_dirty() uses bd_oblocknr to detect dead blocks by comparing it=
    with the current block number bd_blocknr. If they differ, the block is con= sidered dead and skipped. However, bd_oblocknr should never be 0 since bloc=
    k 0 typically stores the primary superblock and is never a valid GC target = block. A corrupted ioctl request with bd_oblocknr set to 0 causes the compa= rison to incorrectly match when the lookup returns -ENOENT and sets bd_bloc= knr to 0, bypassing the dead block check and calling nilfs_bmap_mark() on a=
    non-existent block. This causes nilfs_btree_do_lookup() to return -ENOENT,=
    triggering the WARN_ON(ret =3D=3D -ENOENT). Fix this by rejecting ioctl re= quests with bd_oblocknr set to 0 at the beginning of each iteration. [ryusu= ke: slightly modified the commit message and comments for accuracy]</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53320" target=3D= "_blank" rel=3D"noopener">CVE-2026-53320</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: io_= uring/napi: cap busy_poll_to 10 msec Currently there's no cap on the maximu=
    m amount of time that napi is allowed to poll if no events are found, which=
    can lead to kernel complaints on a task being stuck as there's no conditio= nal rescheduling done within that loop. Just cap it to 10 msec in total, th= at's already way above any kind of sane value that will reap any benefits, = yet low enough that it's nowhere near being able to trigger preemption comp= laints.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53321" target=3D= "_blank" rel=3D"noopener">CVE-2026-53321</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : dsa: remove redundant netdev_lock_ops() from conduit ethtool ops DSA repl= aces the conduit (master) device's ethtool_ops with its own wrappers that a= ggregate stats from both the conduit and DSA switch ports. Taking the lock = again inside the DSA wrappers causes a deadlock. Stumbled upon this when bo= oting qemu with fbnic and CONFIG_NET_DSA_LOOP=3Dy (which looks like some ki=
    nd of testing device that auto-populates the ports of eth0). `ethtool -i` i=
    s enough to deadlock. This means we have basically zero coverage for DSA st= uff with real ops locked devs. Remove the redundant netdev_lock_ops()/netde= v_unlock_ops() calls from the DSA conduit ethtool wrappers.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53323" target=3D= "_blank" rel=3D"noopener">CVE-2026-53323</a></td>
    </tr>

    <td class=3D"vendor-product">Linux--Linux</td>
    <td>In the Linux kernel, the following vulnerability has been resolved: net=
    : mana: Use pci_name() for debugfs directory naming Use pci_name(pdev) for = the per-device debugfs directory instead of hardcoded "0" for PFs and pci_s= lot_name(pdev-&gt;slot) for VFs. The previous approach had two issues: 1. p= ci_slot_name() dereferences pdev-&gt;slot, which can be NULL for VFs in env= ironments like generic VFIO passthrough or nested KVM, causing a NULL point=
    er dereference. 2. Multiple PFs would all use "0", and VFs across different=
    PCI domains or buses could share the same slot name, leading to -EEXIST er= rors from debugfs_create_dir(). pci_name(pdev) returns the unique BDF addre= ss, is always valid, and is unique across the system.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53324" target=3D= "_blank" rel=3D"noopener">CVE-2026-53324</a></td>
    </tr>

    <td class=3D"vendor-product">LY Corporation--Central Dogma</td>
    <td>A vulnerability has been identified in centraldogma-server-mirror-git v= ersions prior to 0.84.0, where the Git mirror SSH client does not verify re= mote host keys for git+ssh:// connections, allowing an on-path attacker to = perform man-in-the-middle attacks and compromise mirrored repositories.</td=

    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11745" target=3D= "_blank" rel=3D"noopener">CVE-2026-11745</a></td>
    </tr>

    <td class=3D"vendor-product">LY Corporation--Central Dogma</td>
    <td>A vulnerability has been identified in centraldogma-server versions pri=
    or to 0.84.0, where enabling ZooKeeper replication without setting replicat= ion.secret causes the server to silently fall back to a hard-coded, publicl=
    y known secret. This default credential authenticates the embedded ZooKeepe=
    r ensemble, allowing an attacker with network access to read the full repli= cation log or join the quorum and execute arbitrary replicated commands acr= oss the cluster.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11746" target=3D= "_blank" rel=3D"noopener">CVE-2026-11746</a></td>
    </tr>

    <td class=3D"vendor-product">LY Corporation--Central Dogma</td>
    <td>A vulnerability has been identified in centraldogma-server-auth-shiro v= ersions prior to 0.84.0, where the SearchFirstActiveDirectoryRealm substitu= tes the login username into an LDAP search filter without neutralizing LDAP=
    filter metacharacters, allowing an unauthenticated attacker to manipulate = the filter to cause authentication confusion and enumerate the directory st= ructure.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11748" target=3D= "_blank" rel=3D"noopener">CVE-2026-11748</a></td>
    </tr>

    <td class=3D"vendor-product">Mailerup--Mailerup</td>
    <td>Open redirect vulnerability (CWE-601) in the _safe_redirect function of=
    the click-tracking endpoint (/c/&lt;token&gt;/) in Mailerup &lt;1.0.0=C2= =A0on all platforms allows remote unauthenticated attackers to redirect vic= tims to arbitrary external sites and conduct phishing attacks via a crafted=
    u=C2=A0query parameter, because the URL scheme is validated (blocking java= script: and data:) but the destination host is not restricted to an allowli= st, and a signing.BadSignature exception is silently caught so a valid sign=
    ed token is not required.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13163" target=3D= "_blank" rel=3D"noopener">CVE-2026-13163</a></td>
    </tr>

    <td class=3D"vendor-product">Mailerup--Mailerup</td>
    <td>Missing Authentication for Critical Function (CWE-306) in the RegisterV= iew (apps/accounts/views.py), exposed at POST /api/auth/register/, in Maile= rUp &lt;1.0.1 allows a remote, unauthenticated attacker to self-register a = working account on instances where registration is intended to be restricte=
    d, because the endpoint applies the AllowAny permission with no email verif= ication, CAPTCHA, or administrator approval. Any account created this way c=
    an read all email stored by the instance, resulting in full disclosure of s= tored messages to an arbitrary unauthenticated attacker</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13164" target=3D= "_blank" rel=3D"noopener">CVE-2026-13164</a></td>
    </tr>

    <td class=3D"vendor-product">mastodon--mastodon</td>
    <td>Mastodon is a free, open-source social network server based on Activity= Pub. Prior to 4.5.10, 4.4.17, and 4.3.23, the list of disallowed IP address=
    ranges was lacking an IP address range that can be used to reach local IP = addresses. An attacker can use an IP address in the affected range to make = Mastodon perform HTTP requests against loopback interfaces, potentially all= owing access to otherwise private resources and services. This vulnerabilit=
    y is fixed in 4.5.10, 4.4.17, and 4.3.23.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46348" target=3D= "_blank" rel=3D"noopener">CVE-2026-46348</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, MessagePackReader.ReadDateTime() can allocate stack memory base=
    d on an attacker-controlled MessagePack extension length. In the slow path = for timestamp extension parsing, the computed tokenSize includes the extens= ion body length from the wire and is used in a stackalloc operation before = the extension length is validated as one of the valid timestamp sizes. A ve=
    ry small payload can claim a large timestamp extension body and cause a sta=
    ck allocation large enough to trigger an uncatchable StackOverflowException=
    , terminating the host process. This vulnerability is fixed in 2.5.301 and = 3.1.7.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48502" target=3D= "_blank" rel=3D"noopener">CVE-2026-48502</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, the parameterless MessagePackInputFormatter() constructor uses = default serializer options, which resolve to MessagePackSerializerOptions.S= tandard with MessagePackSecurity.TrustedData. The formatter is designed for=
    ASP.NET Core MVC request bodies, which commonly cross an HTTP trust bounda= ry. This insecure default can expose applications to denial-of-service atta= cks that MessagePackSecurity.UntrustedData is intended to mitigate, such as=
    hash-collision attacks against dictionary-like model properties. This vuln= erability is fixed in 2.5.301 and 3.1.7.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48509" target=3D= "_blank" rel=3D"noopener">CVE-2026-48509</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, when MessagePack-CSharp decompresses Lz4Block or Lz4BlockArray = payloads, it reads declared uncompressed lengths from the wire and allocate=
    s output buffers based on those lengths before validating that the compress=
    ed data is valid or that the declared expansion is reasonable. A small payl= oad can claim a very large uncompressed length and force a large allocation=
    before LZ4 decoding begins. This vulnerability is fixed in 2.5.301 and 3.1= .7.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48510" target=3D= "_blank" rel=3D"noopener">CVE-2026-48510</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, ExpandoObjectFormatter.Deserialize populates System.Dynamic.Exp= andoObject by calling IDictionary&lt;string, object&gt;.Add for each map en= try. ExpandoObject internally maintains member names in array-like structur= es, so inserting many distinct keys can require repeated linear scans and a= rray copies. For large attacker-controlled maps, this produces quadratic CP=
    U and allocation behavior. The issue is especially surprising because Expan= doObjectResolver.Options is configured with MessagePackSecurity.UntrustedDa= ta, but collision-resistant dictionary comparers cannot protect ExpandoObje=
    ct insertion internals. This vulnerability is fixed in 2.5.301 and 3.1.7.</=

    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48511" target=3D= "_blank" rel=3D"noopener">CVE-2026-48511</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, MessagePack-CSharp's JSON conversion helpers contain multiple r= ecursion paths that do not consistently enforce a depth limit. These paths = are in the JSON conversion component rather than normal typed MessagePack d= eserialization. MessagePackSerializer.ConvertFromJson recursively processes=
    nested JSON arrays and objects in FromJsonCore() without consulting Messag= ePackSecurity.MaximumObjectGraphDepth. TinyJsonReader.ReadNextToken() recur= sively consumes comma and colon separator characters, allowing even malform=
    ed JSON with long separator runs to consume one stack frame per character. = MessagePackSerializer.ConvertToJson applies depth checks to arrays and maps=
    , but the typeless extension branch for ext-100 recursively calls ToJsonCor= e() without applying MessagePackSecurity.DepthStep(ref reader). Each path c=
    an allow attacker-controlled input to exhaust the process stack and trigger=
    an uncatchable StackOverflowException instead of failing with a catchable = parse or serialization exception. This vulnerability is fixed in 2.5.301 an=
    d 3.1.7.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48512" target=3D= "_blank" rel=3D"noopener">CVE-2026-48512</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, runtime-generated union deserializers emitted by DynamicUnionRe= solver do not call MessagePackSecurity.DepthStep(ref reader) and do not dec= rement reader.Depth around recursive deserialization and skip paths. This m= eans union deserialization does not consistently participate in the maximum=
    object graph depth enforcement that protects other recursive formatter pat= hs. For unknown union keys, the emitted deserializer calls reader.Skip() on=
    attacker-controlled data without an enclosing depth step. This vulnerabili=
    ty is fixed in 2.5.301 and 3.1.7.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48513" target=3D= "_blank" rel=3D"noopener">CVE-2026-48513</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, UnsafeBlitFormatterBase&lt;T&gt;.Deserialize reads an attacker-= controlled byteLength from an extension payload and allocates an array base=
    d on that value before validating it against the extension header length or=
    remaining payload bytes. The outer extension header is bounded by availabl=
    e input, but that bound is not used to constrain the inner byteLength befor=
    e allocation. A very small payload can therefore request a very large T[] a= llocation. This vulnerability is fixed in 2.5.301 and 3.1.7.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48514" target=3D= "_blank" rel=3D"noopener">CVE-2026-48514</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, MessagePack-CSharp's multi-dimensional array formatters read di= mension lengths directly from the payload and allocate T[,], T[,,], or T[,,=
    ,] before validating that the dimension product matches the encoded element=
    count. The formatter reads a guarded element array header, but allocation =
    of the target multi-dimensional array happens before the dimensions are che= cked against that element count. A small payload can therefore declare larg=
    e dimensions, provide an empty or tiny inner array, and cause a large heap = allocation before element data is validated. This vulnerability is fixed in=
    2.5.301 and 3.1.7.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48515" target=3D= "_blank" rel=3D"noopener">CVE-2026-48515</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, InterfaceLookupFormatter&lt;TKey,TElement&gt; constructs an int= ernal Dictionary&lt;TKey, IGrouping&lt;TKey,TElement&gt;&gt; with the defau=
    lt equality comparer instead of the security-aware comparer supplied by opt= ions.Security.GetEqualityComparer&lt;TKey&gt;(). This formatter omission al= lows hash-collision CPU denial of service against ILookup&lt;TKey,TElement&= gt; even when the application has opted into the untrusted-data security po= sture This vulnerability is fixed in 2.5.301 and 3.1.7.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48516" target=3D= "_blank" rel=3D"noopener">CVE-2026-48516</a></td>
    </tr>

    <td class=3D"vendor-product">MessagePack-CSharp--MessagePack-CSharp</td> <td>MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.301=
    and 3.1.7, MessagePack-CSharp's typeless deserialization includes MessageP= ackSerializerOptions.ThrowIfDeserializingTypeIsDisallowed(Type) as a safety=
    check for dangerous types. The default implementation checks the outer typ=
    e name, but it does not recursively inspect array element types or generic = type arguments. As a result, a type that would be blocked directly can be w= rapped inside an array or constructed generic type and pass the outer type = check. The formatter machinery can then materialize formatters for the inne=
    r blocked type. This vulnerability is fixed in 2.5.301 and 3.1.7.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48517" target=3D= "_blank" rel=3D"noopener">CVE-2026-48517</a></td>
    </tr>

    <td class=3D"vendor-product">Mintplex-Labs--anything-llm</td>
    <td>AnythingLLM is an application that turns pieces of content into context=
    that any LLM can use as references during chatting. From 1.11.1 until 1.14= .1, userId/workspaceId scoping to the parsed-files read/delete paths was ad= ded. However, the POST /api/workspace/:slug/embed-parsed-file/:fileId flow = still deletes the target file by primary key only, with no ownership check,=
    inside two finally{} blocks that run even when the ownership-checked read = fails. As a result a manager or admin (multi-user mode) can delete any othe=
    r user's parsed file in any workspace - including workspaces they are not a=
    member of - by enumerating integer fileIds. The server even returns "File = not found" while still deleting the file. This vulnerability is fixed in 1.= 14.1.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55611" target=3D= "_blank" rel=3D"noopener">CVE-2026-55611</a></td>
    </tr>

    <td class=3D"vendor-product">misp--misp</td>
    <td>Multiple MISP core controllers and model capture paths accepted client-= controlled request fields such as primary keys (id) and ownership/scope for= eign keys (event_id, org_id, user_id, sharing_group_id, galaxy_cluster_uuid=
    , organisation_uuid, and related nested object identifiers) without consist= ently stripping, pinning, or revalidating them against the server-authorize=
    d object. In affected paths, an authenticated user with access to one autho= rized object could submit crafted REST or form payloads that caused MISP to=
    save data against a different object than the one checked by the authoriza= tion logic. Depending on the endpoint, this could allow object overwrite, o= bject re-parenting, ownership transfer, unauthorized sharing-group scoping,=
    event/object injection, proposal retargeting, or stored attacker-controlle=
    d content appearing in another user's context. The fixes harden affected cr= eate/edit/import flows by stripping client-supplied primary keys on create-= only saves, re-pinning route- or database-authorized identifiers before sav=
    e operations, validating effective sharing-group scope, and adding field wh= itelists where ownership fields must never be editable. The initial broad f=
    ix also added a central CRUDComponent::edit()=C2=A0primary-key re-pin so pa= yload-supplied IDs cannot redirect saves away from the already-authorized r= ow. GitHub's patch for 7acf8220c=C2=A0describes this central issue as CRUDC= omponent::edit()=C2=A0copying supplied fields, including a payload primary = key, onto the loaded record, allowing CakePHP save()=C2=A0to update an arbi= trary row unless the loaded ID is re-pinned.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56422" target=3D= "_blank" rel=3D"noopener">CVE-2026-56422</a></td>
    </tr>

    <td class=3D"vendor-product">misp--misp</td>
    <td>MISP Core contained broken access-control checks in the bulk deletion f= lows for Event Reports=C2=A0and Sharing Groups. The affected deleteSelectio= n=C2=A0handlers authorized deletion using broad role-level permissions inst= ead of validating authorization for each selected object. For Event Reports=
    , EventReportsController::deleteSelection=C2=A0relied on the global perm_ad= d=C2=A0capability rather than a per-report ownership/authorization check. A=
    s a result, a contributor-level user could submit report IDs or UUIDs for r= eports belonging to other organisations and hard-delete them instance-wide.=
    The fix changed the callback to call EventReport::fetchIfAuthorized($user,=
    $itemId, 'delete')=C2=A0for each selected report before deletion. For Shar= ing Groups, SharingGroupsController::deleteSelection=C2=A0relied on the glo= bal perm_sharing_group=C2=A0capability rather than verifying ownership of e= ach selected sharing group. This allowed a sharing-group-capable user to ha= rd-delete sharing groups owned by other organisations, bypassing the per-ob= ject ownership gate used by the single-object delete action. The fix change=
    d the callback to call SharingGroup::checkIfOwner($user, $itemId)=C2=A0for = each selected sharing group. An authenticated attacker with the relevant br= oad role permission could abuse the affected bulk deletion endpoints to del= ete objects outside their organisation's authorization scope, causing loss =
    of event-report content or sharing-group configuration across the instance.= </td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56423" target=3D= "_blank" rel=3D"noopener">CVE-2026-56423</a></td>
    </tr>

    <td class=3D"vendor-product">misp--misp</td>
    <td>MISP core contained multiple broken access-control flaws where authoriz= ation checks were performed against the wrong entity, or where ownership/ed= itability checks were missing on write paths. In affected subsystems, a low= er-privileged authenticated user with the relevant feature permission could=
    cause the application to authorize one object but mutate another, or could=
    modify objects that were merely visible rather than editable by the user's=
    organization. The affected paths included: * Event Reports tag removal: th=
    e route-authorized report could differ from the report ID used for tag deta= chment, enabling cross-organization tag removal from another event report *=
    Collection Elements bulk deletion: bulk deletion authorized against a coll= ection whose ID matched the collection-element row ID, rather than the elem= ent's actual parent collection, enabling deletion of elements from collecti= ons the user did not own. * Analyst Data capture/update: nested analyst dat=
    a updates could overwrite an existing record without applying the normal ca= nEditAnalystData=C2=A0ownership check, enabling cross-organization overwrit=
    e of analyst data records. * Template Elements editing: editing authorized = against a template whose ID matched the template-element ID, rather than th=
    e element's actual parent template, enabling unauthorized edits to another = organization's template elements. * Decaying Model editing and mappings: wr= ite paths loaded models using view-scope access but did not verify edit own= ership, enabling users to edit or remap visible models owned by another org= anization.=C2=A0 Successful exploitation could allow an authenticated user = with subsystem-specific permissions to perform unauthorized cross-organizat= ion modifications or deletions of MISP data, resulting in integrity loss, u= nauthorized tampering with shared intelligence, and disruption of analyst w= orkflows.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56424" target=3D= "_blank" rel=3D"noopener">CVE-2026-56424</a></td>
    </tr>

    <td class=3D"vendor-product">misp--misp</td>
    <td>The Azure Active Directory (AAD) authentication implementation containe=
    d multiple weaknesses in its OAuth 2.0 authorization flow that could allow = attackers to bypass important security guarantees provided by the protocol.=
    The application used the PHP session identifier (session_id()) as the OAut=
    h state parameter. Because session identifiers are long-lived authenticatio=
    n credentials, exposing them in OAuth redirect URLs could leak valid sessio=
    n tokens through browser history, HTTP Referer headers, reverse proxies, ac= cess logs, or third-party infrastructure involved in the authentication flo=
    w. If obtained by an attacker, the leaked session identifier could potentia= lly be used for session hijacking. Additionally, the implementation did not=
    regenerate the session identifier after successful authentication, leaving=
    authenticated sessions susceptible to session fixation attacks where an at= tacker forces a victim to use a known session identifier before login and l= ater reuses that identifier after authentication. The OAuth state value was=
    also not implemented as a dedicated, single-use nonce. This weakened CSRF = protections and increased the risk of replay attacks against the OAuth call= back process. The authentication flow further failed to enforce HTTPS for t=
    he configured OAuth redirect URI. If a non-HTTPS redirect URI was used, OAu=
    th authorization codes and access tokens could traverse the network in plai= ntext, exposing sensitive credentials to network attackers. Finally, OAuth = error responses containing attacker-controlled GET parameters were logged v= erbatim. An attacker could inject control characters or crafted log content=
    , leading to log forging, log injection, or corruption of audit records. Th=
    e fix introduces: * A dedicated cryptographically random OAuth state value.=
    * Single-use state validation and invalidation. * Constant-time state comp= arison using hash_equals(). * Session identifier rotation after successful = authentication. * Enforcement of HTTPS-only redirect URIs. * Sanitized and = length-limited logging of OAuth error parameters. AAD Authentication Plugin=
    (OAuth 2.0 / Azure Active Directory integration)</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56425" target=3D= "_blank" rel=3D"noopener">CVE-2026-56425</a></td>
    </tr>

    <td class=3D"vendor-product">misp--misp</td>
    <td>MISP allowed a site administrator to configure an arbitrary filesystem = path for the NDJSON error log used by JsonLogTool. Because log entries can = include attacker-controlled content, an authenticated attacker with site ad= ministrator privileges could direct log output to a PHP file in a web-acces= sible directory and inject PHP code through logged data. Accessing the resu= lting file could lead to remote code execution with the privileges of the w=
    eb server process. The fix restricts log destinations to existing directori=
    es beneath APP/tmp/logs or /var/log, requires absolute paths, rejects strea=
    m wrappers and traversal-related input, and limits filenames to .log or .nd= json extensions while disallowing executable extension segments.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56446" target=3D= "_blank" rel=3D"noopener">CVE-2026-56446</a></td>
    </tr>

    <td class=3D"vendor-product">misp--misp</td>
    <td>MISP allowed an authenticated site administrator to set the Kafka_rdkaf= ka_config setting to an arbitrary filesystem path. MISP subsequently parsed=
    the referenced INI file and passed its options to rdkafka. A crafted attac= ker-controlled configuration file could use rdkafka options such as plugin.= library.paths to load an external library, resulting in arbitrary code exec= ution with the privileges of the MISP process. An attacker could leverage a=
    MISP-writable location, such as an uploaded file or administrative image, =
    to host the malicious configuration file. The issue is fixed by restricting=
    the setting to absolute .ini files located only in approved configuration = directories outside the webroot and MISP upload targets.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-56447" target=3D= "_blank" rel=3D"noopener">CVE-2026-56447</a></td>
    </tr>

    <td class=3D"vendor-product">MosaicML--Composer</td>
    <td>MosaicML Composer Deserialization of Untrusted Data Remote Code Executi=
    on Vulnerability. This vulnerability allows remote attackers to execute arb= itrary code on affected installations of MosaicML Composer. User interactio=
    n is required to exploit this vulnerability in that the target must visit a=
    malicious page or open a malicious file. The specific flaw exists within t=
    he parsing of checkpoints. The issue results from the lack of proper valida= tion of user-supplied data, which can result in deserialization of untruste=
    d data. An attacker can leverage this vulnerability to execute code in the = context of the current process. Was ZDI-CAN-27990.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10043" target=3D= "_blank" rel=3D"noopener">CVE-2026-10043</a></td>
    </tr>

    <td class=3D"vendor-product">motioneye-project--motioneye</td>
    <td>motionEye (mEye) is an online interface for a piece of software called = "motion," which is a video surveillance program with motion detection. Vers= ions prior to 0.44.0 contain an absolute path traversal vulnerability in mu= ltiple media file handlers that allows an attacker to read arbitrary files = from the filesystem. The affected handlers accept a user-controlled filenam=
    e parameter and construct filesystem paths using `os.path.join()`. When an = absolute path is supplied, Python discards the configured media directory a=
    nd returns the attacker-supplied path directly. The application then bypass=
    es Tornado's built-in path validation by overriding the relevant safety che= cks. As a result, an attacker can access files outside of the configured ca= mera media directory, subject to the permissions of the motionEye process. = Version 0.44.0 fixes the issue.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55488" target=3D= "_blank" rel=3D"noopener">CVE-2026-55488</a></td>
    </tr>

    <td class=3D"vendor-product">MSI--NBFoundation Service</td>
    <td>Insecure Permissions vulnerability in MSI NBFoundation Service v.2.0.25= 06.1201 allows a remote attacker to obtain sensitive information via the MS= IAPService.exe component</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-37452" target=3D= "_blank" rel=3D"noopener">CVE-2026-37452</a></td>
    </tr>

    <td class=3D"vendor-product">MSI--NBFoundation Service</td>
    <td>Insecure Permissions vulnerability in MSI NBFoundation Service v.2.0.25= 06.1201 allows a remote attacker to obtain sensitive information via the MS= I_SERVICE_2 pipe</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-37453" target=3D= "_blank" rel=3D"noopener">CVE-2026-37453</a></td>
    </tr>

    <td class=3D"vendor-product">MSI--NBFoundation Service</td>
    <td>Insecure Permissions vulnerability in MSI NBFoundation Service v.2.0.25= 06.1201 allows a remote attacker to obtain sensitive information via the 3D= ES-ECB encryption</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-37454" target=3D= "_blank" rel=3D"noopener">CVE-2026-37454</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.43, = 2.22.1, and 2.20.7, an authenticated user with permission to create or modi=
    fy workflows could achieve global prototype pollution via an unvalidated pa= gination parameter in the HTTP Request node. Combined with other techniques=
    this could lead to RCE on the instance. This vulnerability is fixed in 1.1= 23.43, 2.22.1, and 2.20.7.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44789" target=3D= "_blank" rel=3D"noopener">CVE-2026-44789</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.43, = 2.22.1, and 2.20.7, an authenticated user with permission to create or modi=
    fy workflows could inject CLI flags on the Git node's Push operation allowi=
    ng an attacker to read arbitrary files from the n8n server potentially lead= ing to full compromise. This vulnerability is fixed in 1.123.43, 2.22.1, an=
    d 2.20.7.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44790" target=3D= "_blank" rel=3D"noopener">CVE-2026-44790</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.43, = 2.22.1, and 2.20.7, an authenticated user with permission to create or modi=
    fy workflows could bypass the patch for CVE-2026-42232 in the XML node. Whe=
    n combined with other nodes, this could lead to RCE on the n8n host. This v= ulnerability is fixed in 1.123.43, 2.22.1, and 2.20.7.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44791" target=3D= "_blank" rel=3D"noopener">CVE-2026-44791</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.43, = 2.22.1, and 2.20.7, an attacker with write access to the git repository con= nected to an n8n Source Control configuration could commit a malicious Data=
    Table JSON file containing a crafted column name. When an administrator pe= rformed a Source Control Pull, n8n imported the file and could lead to SQL = injection on the internal PostgreSQL instance. Exploitation requires the n8=
    n instance uses PostgreSQL as its database backend, the Source Control feat= ure is enabled and connected to a repository the attacker can write to, and=
    an administrator triggers a Source Control Pull. This vulnerability is fix=
    ed in 1.123.43, 2.22.1, and 2.20.7.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44792" target=3D= "_blank" rel=3D"noopener">CVE-2026-44792</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.43, = 2.22.1, and 2.20.7, the OAuth1 and OAuth2 credential reconnect endpoints au= thorized access using credential:read rather than credential:update. An aut= henticated user with read-only access to a shared credential could initiate=
    an OAuth reconnect flow and overwrite the stored token material for that c= redential with tokens bound to an external account they control. Workflows = relying on the affected credential would subsequently execute under the att= acker's OAuth identity, enabling data exfiltration to attacker-controlled e= xternal services and persistent takeover of shared integrations. This vulne= rability is fixed in 1.123.43, 2.22.1, and 2.20.7.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45732" target=3D= "_blank" rel=3D"noopener">CVE-2026-45732</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.48, = 2.21.8, and 2.22.4, an authenticated user with permission to create or modi=
    fy workflows containing a Python Code Node could escape the sandbox and ach= ieve arbitrary code execution on the task runner container. This vulnerabil= ity is fixed in 1.123.48, 2.21.8, and 2.22.4.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49444" target=3D= "_blank" rel=3D"noopener">CVE-2026-49444</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.48, = 2.21.8, and 2.22.4, an authenticated user with permission to create or modi=
    fy workflows could supply a local filesystem path as the source repository =
    in the Git node's Clone operation, or as the target repository in the Push = operation, bypassing the N8N_RESTRICT_FILE_ACCESS_TO file sandbox. This all= owed the contents of any local git repository accessible to the n8n process=
    to be cloned into an allowed path and read, circumventing the access restr= ictions that correctly blocked direct file reads to the same paths. This vu= lnerability is fixed in 1.123.48, 2.21.8, and 2.22.4.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49465" target=3D= "_blank" rel=3D"noopener">CVE-2026-49465</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.55, = 2.25.7, and 2.26.2, an authenticated user with workflow edit access could c= onfigure a Respond to Webhook node to serve binary content with an attacker= -controlled Content-Type. The binary response path bypassed the central Con= tent-Security-Policy sandbox header, allowing a public webhook to execute J= avaScript in the n8n origin when visited by an authenticated user, with acc= ess to that user's session. This vulnerability is fixed in 1.123.55, 2.25.7=
    , and 2.26.2.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54301" target=3D= "_blank" rel=3D"noopener">CVE-2026-54301</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.55, = 2.25.7, and 2.26.2, an authenticated user with workflow edit access could i= nject arbitrary JavaScript into the Chat Trigger's generated page by settin=
    g a malicious webhookId. When a logged-in user visited the chat URL, the in= jected code executed in the n8n origin with that user's session privileges.=
    This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54302" target=3D= "_blank" rel=3D"noopener">CVE-2026-54302</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 2.24.0, an=
    endpoint in the Meta and Microsoft Teams trigger nodes reflects a query pa= rameter into the HTTP response without sanitization or Content-Security-Pol= icy headers, enabling reflected XSS in the n8n origin when a logged-in user=
    visits a crafted URL. This vulnerability is fixed in 2.24.0.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54303" target=3D= "_blank" rel=3D"noopener">CVE-2026-54303</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.55, = 2.25.7, and 2.26.1, an authenticated user with permission to create or modi=
    fy workflows and access to a SecurityScorecard credential with limited allo= wed domains could configure the SecurityScorecard node's report download op= eration to target an attacker-controlled URL. The node attached the Securit= yScorecard API token to the outbound request, causing the credential to be = sent to the attacker-controlled host bypassing credential configured limita= tions and exfiltrating. This vulnerability is fixed in 1.123.55, 2.25.7, an=
    d 2.26.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54304" target=3D= "_blank" rel=3D"noopener">CVE-2026-54304</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.55, = 2.25.7, and 2.26.2, three EE endpoints used by the Dynamic Credentials feat= ure accepted any authenticated n8n session without performing per-resource = ownership or scope checks on the target workflow or credential. An authenti= cated user with no project membership or credential sharing relationship co= uld enumerate credential identifiers, names, and types referenced by any pr= ivate workflow in the instance, initiate an OAuth authorization flow agains=
    t another user's credential to overwrite its stored tokens with tokens boun=
    d to an account they control, or revoke another user's stored credential to= kens entirely. Workflows relying on a hijacked credential would subsequentl=
    y execute under the attacker's OAuth identity, enabling data exfiltration t=
    o attacker-controlled external services and persistent takeover of integrat= ions. Token revocation would break affected workflows. This vulnerability i=
    s fixed in 1.123.55, 2.25.7, and 2.26.2.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54305" target=3D= "_blank" rel=3D"noopener">CVE-2026-54305</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 2.25.7 and=
    2.26.2, a prototype pollution vulnerability allowed a crafted public webho=
    ok payload to inject attacker-controlled fields into workflow data during i= nternal object copying. These fields could be surfaced and consumed as norm=
    al values by downstream built-in nodes. Where a workflow combines a public = webhook with action nodes that consume the resulting fields, an attacker co= uld cause the workflow to act as a confused deputy - targeting unintended r= ecords or issuing outbound requests using the workflow owner's configured c= redentials. This vulnerability is fixed in 2.25.7 and 2.26.2.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54306" target=3D= "_blank" rel=3D"noopener">CVE-2026-54306</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 1.123.55, = 2.25.7, and 2.26.2, a member-level user with editor access to a shared work= flow could reference credentials they do not own via specific public API en= dpoints. Credential ownership checks were only enforced partially leading t=
    o cross-user credential access. This issue affects instances where workflow=
    sharing is enabled and at least one workflow has been shared with a member= -level user as an Editor. This vulnerability is fixed in 1.123.55, 2.25.7, = and 2.26.2.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54307" target=3D= "_blank" rel=3D"noopener">CVE-2026-54307</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 2.25.7 and=
    2.26.2, the MicrosoftAgent365Trigger and StripeTrigger node did not valida=
    te that inbound requests. As a result, an unauthenticated attacker who know=
    s the webhook URL could submit a forged payload and cause the workflow to e= xecute with attacker-controlled data. This vulnerability is fixed in 2.25.7=
    and 2.26.2.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54308" target=3D= "_blank" rel=3D"noopener">CVE-2026-54308</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 2.25.7 and=
    2.26.2, when @n8n/mcp-browser is run in HTTP transport mode, the MCP endpo= int accepts session initialization and tool invocation requests without any=
    authentication. Any network-reachable client, or any website visited by th=
    e user, can establish an MCP session and invoke browser-control tools. Wher=
    e the n8n AI Browser Bridge extension is installed and a browser connection=
    is active, an unauthenticated caller can access browser-control capabiliti=
    es including navigation, JavaScript evaluation, and cookie and storage acce=
    ss against the user's real browser profile. This issue only affects instanc=
    es where @n8n/mcp-browser is run with the HTTP transport (--transport http)=
    . This vulnerability is fixed in 2.25.7 and 2.26.2.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54309" target=3D= "_blank" rel=3D"noopener">CVE-2026-54309</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 2.25.7 and=
    2.26.2, an authenticated user with permission to create or modify workflow=
    s could supply a crafted parameters to the TimescaleDB and/or legacy Postgr=
    es v1 node's allowing arbitrary SQL to be injected and executed against the=
    connected database within the privileges of the configured database accoun=
    t. This vulnerability is fixed in 2.25.7 and 2.26.2.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54310" target=3D= "_blank" rel=3D"noopener">CVE-2026-54310</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 2.25.7 and=
    2.26.2, an authenticated user with permission to create or modify workflow=
    s could pollute the sandbox used by the Merge node's SQL Query mode. Becaus=
    e the sandbox context was cached and reused across all workflow executions =
    on the instance, prototype mutations introduced by one user's workflow pers= ist into subsequent Merge SQL executions belonging to other users or projec= ts. This allowed a low-privileged attacker to intercept workflow data proce= ssed by other users on the same instance. This issue only affects multi-use=
    r n8n instances where more than one user has permission to create and execu=
    te workflows containing the Merge node in SQL Query mode. This vulnerabilit=
    y is fixed in 2.25.7 and 2.26.2.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54311" target=3D= "_blank" rel=3D"noopener">CVE-2026-54311</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 2.24.0, an=
    authenticated user with permission to create or modify workflows could ach= ieve global prototype pollution via the Microsoft SQL node by supplying a c= rafted value as the table parameter. This pollutes Object.prototype process= -wide for the lifetime of the n8n server process, causing application-wide = validation failures and rendering the n8n instance completely non-functiona=
    l until restarted. This vulnerability is fixed in 2.24.0.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54312" target=3D= "_blank" rel=3D"noopener">CVE-2026-54312</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 2.24.0, an=
    authenticated user with workflow edit access could supply a malicious filt=
    er value in the MongoDB node's Find And Replace operation. The value was no=
    t validated before being passed to MongoDB as a query filter, allowing unin= tended documents to be matched and overwritten with attacker-controlled con= tent. This vulnerability is fixed in 2.24.0.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54313" target=3D= "_blank" rel=3D"noopener">CVE-2026-54313</a></td>
    </tr>

    <td class=3D"vendor-product">n8n-io--n8n</td>
    <td>n8n is an open source workflow automation platform. Prior to 2.24.0, th=
    e Compression node's Decompress operation expanded attacker-controlled arch= ives into memory without enforcing limits on decompressed output size. An u= nauthenticated attacker could send a small compressed archive to a public w= ebhook workflow using this node, causing the n8n process to terminate due t=
    o memory exhaustion and disrupting all workflows in the same instance. This=
    vulnerability is fixed in 2.24.0.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54314" target=3D= "_blank" rel=3D"noopener">CVE-2026-54314</a></td>
    </tr>

    <td class=3D"vendor-product">NEC Corporation--ExpressUpdate Agent for Windo= ws</td>
    <td>An access control deficiency vulnerability exists in ExpressUpdate Agen=
    t for Windows. If a malicious user gains access to the product, arbitrary c= ode could be executed with SYSTEM privileges.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8797" target=3D"= _blank" rel=3D"noopener">CVE-2026-8797</a></td>
    </tr>

    <td class=3D"vendor-product">nestjs--nest</td>
    <td>Nest is a framework for building scalable Node.js server-side applicati= ons. Prior to 11.1.24, an authentication bypass vulnerability exists in @ne= stjs/platform-fastify. When middleware is registered through NestJS's Middl= ewareConsumer.forRoutes() API on the Fastify adapter, an unauthenticated cl= ient can bypass the Nest middleware registered for that route by simply app= ending a trailing slash (/) to the request URL. This bypass works on the de= fault Fastify adapter configuration. This vulnerability is fixed in 11.1.24= .</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54281" target=3D= "_blank" rel=3D"noopener">CVE-2026-54281</a></td>
    </tr>

    <td class=3D"vendor-product">NLnet Labs--NSD</td>
    <td>If NSD is configured as secondary for a zone, the primary of that zone = can crash NSD with an AXFR containing a DNS message with a special crafted = SVCB RR with an rdata size of 65512, that let's an (uint16_t) variable that=
    is used to allocate space needed for the RR wrap (because total size &gt; = 65535), causing a heap overflow. The attacker can perform a controlled (RCE=
    class) head write of up to 65509 bytes</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12244" target=3D= "_blank" rel=3D"noopener">CVE-2026-12244</a></td>
    </tr>

    <td class=3D"vendor-product">NLnet Labs--NSD</td>
    <td>NSD from version 4.13.0 has a heap use-after-free bug in logging errors=
    on TLS connections, causing a crash of the server process, which can be tr= iggered trivially by sending a DNS query over a DoT connection, and closing=
    the connection without reading the response.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12245" target=3D= "_blank" rel=3D"noopener">CVE-2026-12245</a></td>
    </tr>

    <td class=3D"vendor-product">NLnet Labs--NSD</td>
    <td>NSD version 4.14.0 introduced a bug where a specially crafted APL RR, w= ith an adflength larger than permitted for the address family will overwrit=
    e the stack when the zone is written to disk, with a maximum of 111 attacke=
    r controlled bytes.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12246" target=3D= "_blank" rel=3D"noopener">CVE-2026-12246</a></td>
    </tr>

    <td class=3D"vendor-product">NLnet Labs--NSD</td>
    <td>When a provide-xfr is given with a tls-auth-name, a secondary requestin=
    g a transfer should provide a client certificate with that name. However, n=
    o client certificate is needed when the request comes in over TLS over the = regular tls-port (and not the tls-auth-port) or over over TCP over the regu= lar port, when the other conditions of the provide-xfr rule match.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12490" target=3D= "_blank" rel=3D"noopener">CVE-2026-12490</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, the upload-by-URL path did not enforce NC_ATTACHMENT_FIELD_SIZE aga= inst either the remote file's advertised Content-Length or the decoded leng=
    th of a data: URI, allowing an authenticated user to bypass the configured = per-file size limit. This vulnerability is fixed in 2026.04.1.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46553" target=3D= "_blank" rel=3D"noopener">CVE-2026-46553</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.4, deleted API tokens continued to authenticate requests until their c= ache entry expired, because the auth cache was not invalidated by token val=
    ue at deletion time. The API token deletion path removed the database row b=
    ut did not evict the token-value keyed entry from the auth cache. The auth = middleware therefore continued to accept the deleted token until the cache = entry aged out, leaving a deletion-to-revocation window of up to three days=
    . This vulnerability is fixed in 2026.04.4.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46554" target=3D= "_blank" rel=3D"noopener">CVE-2026-46554</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, the public shared-view relation endpoints accepted a caller-supplie=
    d column ID without verifying that the column was visible in the shared vie=
    w, so anyone holding a share UUID could read links from any LTAR column on = the view's table - including columns the view owner had hidden. publicMmLis=
    t, publicHmList, and relDataList already ensured that the requested column = belonged to the view's model, but did not check the view-column entry's sho=
    w flag. This vulnerability is fixed in 2026.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47279" target=3D= "_blank" rel=3D"noopener">CVE-2026-47279</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, the password-reset page rendered the URL token directly into a Java= Script string literal in a server-rendered EJS template. EJS &lt;%=3D %&gt;=
    HTML-entity-encodes a fixed set of characters but does not escape single q= uotes or backslashes, so a crafted token could break out of the JS string c= ontext and execute attacker-controlled script in the NocoDB origin. Trigger= ing required only that a victim follow a malicious password-reset link. Thi=
    s vulnerability is fixed in 2026.04.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47376" target=3D= "_blank" rel=3D"noopener">CVE-2026-47376</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, the client-side hashRedirect plugin called window.location.replace(=
    ) on a path extracted from the URL hash fragment after only checking hashPa= th.startsWith('/'). Protocol-relative URLs (//attacker.com/) also satisfy t= hat check, so a crafted link silently redirected visitors to an attacker-co= ntrolled origin. This vulnerability is fixed in 2026.04.1.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47377" target=3D= "_blank" rel=3D"noopener">CVE-2026-47377</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, Public shared-view endpoints exposed values from columns that the v= iew owner had hidden, via three independent paths: groupBy returned raw val= ues for any column named in the request, filter and sort arrays operated on=
    hidden columns enabling boolean-blind extraction, and the related-data lis=
    t accepted arbitrary link-column IDs from other tables in the same base. Th=
    is vulnerability is fixed in 2026.04.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47378" target=3D= "_blank" rel=3D"noopener">CVE-2026-47378</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, the shared-view password check fell back to strict-equality (=3D=3D= =3D) comparison for legacy plaintext passwords, leaking the password's leng=
    th and per-character prefix through response timing. This vulnerability is = fixed in 2026.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47379" target=3D= "_blank" rel=3D"noopener">CVE-2026-47379</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.04.1, sign-in response timing differed between known and unknown email ad= dresses because the unknown-user branch returned without performing a passw= ord hash comparison. This vulnerability is fixed in 2026.04.1.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47380" target=3D= "_blank" rel=3D"noopener">CVE-2026-47380</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, a user in one workspace could exercise another workspace's integrat= ion through the testConnection endpoint by supplying its ID, because the in= tegration was fetched in a bypass scope and the caller's permission check m= atched any base in any workspace. This vulnerability is fixed in 2026.05.1.= </td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47381" target=3D= "_blank" rel=3D"noopener">CVE-2026-47381</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, the connection-test endpoint opened a raw TCP socket to the user-su= pplied database host without resolving and range-checking the destination, =
    so private and link-local addresses (including IPv4-mapped IPv6 forms and l= ocalhost) reached the driver. This vulnerability is fixed in 2026.05.1.</td=

    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47382" target=3D= "_blank" rel=3D"noopener">CVE-2026-47382</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, an authenticated commenter could store HTML in row comments that ex= ecuted as script when other users hovered over the comment in the expanded = form view. The comment write paths persisted the raw comment body with no s= erver-side sanitisation; the expanded-form sidebar then rendered the stored=
    body and fed its data-tooltip attribute to Tippy with allowHTML: true. Eve=
    n when the editor stripped script tags at write time, attribute-level paylo= ads re-entered the DOM as live HTML on hover. This vulnerability is fixed i=
    n 2026.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47383" target=3D= "_blank" rel=3D"noopener">CVE-2026-47383</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, an authenticated user with column-create permission can inject SQL = into the bulk groupBy endpoint by setting a column's title to a SQL fragmen=
    t. The bulk groupBy path in group-by.ts builds three database-specific knex= .raw() aggregations that interpolate the request's column_name directly int=
    o the SQL string. Column lookup in data-table.service.ts matches on both th=
    e sanitized column_name field and the free-text title, so a title containin=
    g a SQL fragment bypasses the public endpoint's existing column allowlist a=
    nd reaches the query builder unescaped. This vulnerability is fixed in 2026= .05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47384" target=3D= "_blank" rel=3D"noopener">CVE-2026-47384</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, an authenticated user with base-create permission can attach a SQLi=
    te source pointing at an arbitrary file on the NocoDB host, including NocoD= B's own internal databases. The SQLite client and the base/integration crea=
    te services accepted a caller-supplied filename and passed it to fs.exists = and fs.open('w') without restricting the location. A user could point a sou= rce at noco.db, at a tenant database under nc_minimal_dbs/, or at any writa= ble path the NocoDB process can reach, and then read or overwrite its conte= nts through the regular table APIs.This vulnerability is fixed in 2026.05.1= .</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47385" target=3D= "_blank" rel=3D"noopener">CVE-2026-47385</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, two concurrent token-exchange requests using the same OAuth authori= zation code could each mint a distinct valid (access_token, refresh_token) = pair, breaking the single-use guarantee that PKCE relies on. This vulnerabi= lity is fixed in 2026.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47386" target=3D= "_blank" rel=3D"noopener">CVE-2026-47386</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, the shared form-view submit handler (packages/nc-gui/composables/us= eSharedFormViewStore.ts) in NocoDB writes the form's redirect_url to window= .location.href after a same-host check that does not validate the URL schem=
    e. A user with editor role (or above) on any base can plant a javascript: U=
    RL in the form's redirect_url; when an authenticated viewer opens the share= -link and submits the form, the payload executes in the NocoDB origin and c=
    an read the session token from localStorage["nocodb-gui-v2"]. This vulnerab= ility is fixed in 2026.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47387" target=3D= "_blank" rel=3D"noopener">CVE-2026-47387</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, a low-privilege MCP token holder with knowledge of an attachment pa=
    th could read any file in shared storage, including attachments belonging t=
    o other bases and workspaces, because the MCP readAttachment tool did not v= erify the file's ownership. This vulnerability is fixed in 2026.05.1.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47388" target=3D= "_blank" rel=3D"noopener">CVE-2026-47388</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, revokeAllOAuthTokensByUser in the users service is an empty stub be= ing called from passwordChange, passwordForgot, and passwordReset. OAuth ac= cess and refresh tokens were not revoked when the user changed, reset, or r= ecovered their password, leaving an attacker-issued OAuth grant valid after=
    the user believed they had locked the attacker out. This vulnerability is = fixed in 2026.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53926" target=3D= "_blank" rel=3D"noopener">CVE-2026-53926</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, the spreadsheet-fetch endpoint (axiosRequestMake) accepted URLs who=
    se path contained a permitted extension anywhere in the string, and applied=
    a hand-rolled regex blocklist that omitted 127.0.0.0/8 and 169.254.0.0/16,=
    allowing the cloud-metadata endpoint to be reached with a crafted URL This=
    vulnerability is fixed in 2026.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53927" target=3D= "_blank" rel=3D"noopener">CVE-2026-53927</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, a stolen refresh token survived a password-forgot flow and could be=
    used to mint fresh JWTs even after the user reset their password. password= Change and passwordReset deleted the user's refresh tokens, but passwordFor= got only rotated token_version and revoked OAuth tokens - it did not call U= serRefreshToken.deleteAllUserToken(user.id). An attacker holding a captured=
    refresh cookie could still exchange it for a new access token after the vi= ctim triggered the recovery flow. This vulnerability is fixed in 2026.05.1.= </td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53928" target=3D= "_blank" rel=3D"noopener">CVE-2026-53928</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, with NC_SECURE_ATTACHMENTS=3Dtrue, an authenticated uploader could = deliver .html or .svg attachments that the browser rendered inline from the=
    NocoDB origin instead of forcing a download. The signed attachment handler=
    stored response-header overrides under PascalCase keys (ResponseContentDis= position, ResponseContentType) while the controller that served the file re=
    ad them under lowercase-hyphen names (response-content-disposition). The mi= smatch dropped the Content-Disposition: attachment header, leaving Express =
    to auto-render .html, .svg, and similar inline. This vulnerability is fixed=
    in 2026.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53929" target=3D= "_blank" rel=3D"noopener">CVE-2026-53929</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, the base-migration endpoint accepted a caller-supplied URL that the=
    migration worker dereferenced without enforcing protocol or destination, a= llowing scheme abuse (file:, ftp:, etc.) and probing of internal HTTP desti= nations. This vulnerability is fixed in 2026.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53930" target=3D= "_blank" rel=3D"noopener">CVE-2026-53930</a></td>
    </tr>

    <td class=3D"vendor-product">nocodb--nocodb</td>
    <td>NocoDB is software for building databases as spreadsheets. Prior to 202= 6.05.1, the spreadsheet-import endpoint axiosRequestMake could be used as a=
    generic HTTP proxy. Before the fix it was reachable unauthenticated, and i=
    ts URL-extension allowlist was a regex tested against the full URL string, =
    so URLs whose query string ended in .csv satisfies the gate even though the=
    underlying request is for another file. This vulnerability is fixed in 202= 6.05.1.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53931" target=3D= "_blank" rel=3D"noopener">CVE-2026-53931</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A flaw in Node.js proxy tunnel error handling could expose proxy creden= tials in `ERR_PROXY_TUNNEL` error messages. When proxy credentials are embe= dded in the proxy URL, they may be exposed through error handling paths and=
    captured by logs, diagnostics, or other error consumers. This vulnerabilit=
    y affects all supported release lines: **Node.js 22**, **Node.js 24**, and = **Node.js 26**.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48615" target=3D= "_blank" rel=3D"noopener">CVE-2026-48615</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A flaw in Node.js TLS hostname handling can cause Node.js unicode dot s= eparator handling can lead to tls wildcard-depth authentication bypass due =
    to resolver and verifier hostname normalization mismat. This can lead to co= nfidentiality impact or bypass of the intended security boundary under affe= cted configurations. This vulnerability affects all supported release lines=
    : **Node.js 22**, **Node.js 24**, and **Node.js 26**.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48618" target=3D= "_blank" rel=3D"noopener">CVE-2026-48618</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A flaw in Node.js HTTP/2 client allows a server to send an unlimited nu= mber of ORIGIN frames, which could lead to an Out of Memory error on the cl= ient. This vulnerability affects all supported release lines: **Node.js 22*=
    *, **Node.js 24**, and **Node.js 26**.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48619" target=3D= "_blank" rel=3D"noopener">CVE-2026-48619</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A inconsistency in Node.js hostname matching can cause a trust-policy b= ypass in multi-context mTLS setups. This vulnerability affects all supporte=
    d release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48928" target=3D= "_blank" rel=3D"noopener">CVE-2026-48928</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A flaw in Node.js TLS hostname handling can cause Embedded-nul hostname=
    s can lead to silent authority rebinding due to c-string truncation in reso= lver bindings. This vulnerability affects all supported release lines: **No= de.js 22**, **Node.js 24**, and **Node.js 26**.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48930" target=3D= "_blank" rel=3D"noopener">CVE-2026-48930</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A flaw in Node.js HTTP Agent can cause a client to accept as valid a re= sponse that is send before the client has sent the request. This vulnerabil= ity affects all supported release lines: **Node.js 22**, **Node.js 24**, an=
    d **Node.js 26**.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48931" target=3D= "_blank" rel=3D"noopener">CVE-2026-48931</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A flaw in Node.js WebCrypto implementation can crash the process if the=
    input of `subtle.encrypt()` is a multiple of 2GiB. This vulnerability affe= cts all supported release lines: **Node.js 22**, **Node.js 24**, and **Node= .js 26**.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48933" target=3D= "_blank" rel=3D"noopener">CVE-2026-48933</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A flaw in Node.js TLS host verification can cause an attacker to bypass=
    certification validation. This vulnerability affects all supported release=
    lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48934" target=3D= "_blank" rel=3D"noopener">CVE-2026-48934</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A flaw in Node.js Permission API can cause a file metadata to be modifi=
    ed even on a path that was set as read-only with e.g. `--allow-fs-read`. Th=
    is vulnerability affects all supported release lines: **Node.js 22**, **Nod= e.js 24**, and **Node.js 26**.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48935" target=3D= "_blank" rel=3D"noopener">CVE-2026-48935</a></td>
    </tr>

    <td class=3D"vendor-product">nodejs--node</td>
    <td>A flaw in Node.js Permission API can cause a local server to be started=
    (via a Unix domain socket), even without the `--allow-net` permission. Thi=
    s vulnerability affects one supported release line: **Node.js 26**.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48936" target=3D= "_blank" rel=3D"noopener">CVE-2026-48936</a></td>
    </tr>

    <td class=3D"vendor-product">notepad-plus-plus--notepad-plus-plus</td> <td>Notepad++ is a free and open-source source code editor. From 8.9.4 unti=
    l 8.9.6, Notepad++ contains a local privilege escalation vulnerability in t=
    he installer. During installation, the installer invokes powershell.exe wit= hout using an absolute path after setting the working directory to the inst= allation contextMenu directory. If an attacker can pre-place a malicious po= wershell.exe in a user-writable custom installation directory, and a privil= eged user later runs the installer and selects that directory, the attacker= -controlled executable is launched with the elevated privileges of the inst= aller. This vulnerability is fixed in 8.9.6.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46710" target=3D= "_blank" rel=3D"noopener">CVE-2026-46710</a></td>
    </tr>

    <td class=3D"vendor-product">notepad-plus-plus--notepad-plus-plus</td> <td>Notepad++ is a free and open-source source code editor. Prior to 8.9.6.=
    4, NppCommands.cpp checks the HMAC of the on-disk shortcuts.xml at the mome=
    nt a user command fires (Time-of-Check). However, the command payload is ta= ken from the in-memory _userCommands vector, which is populated at applicat= ion startup and never re-synchronized with the on-disk file (Time-of-Use). = Swapping shortcuts.xml between startup and command execution causes the HMA=
    C check to validate a clean file while a malicious command runs. An attacke=
    r with write access to shortcuts.xml places a malicious version on disk bef= ore launch, then immediately restores the legitimate file. The HMAC check a=
    t execution time validates the restored legitimate file (check passes), whi=
    le the malicious payload executes from memory. This vulnerability is fixed =
    in 8.9.6.4.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-52885" target=3D= "_blank" rel=3D"noopener">CVE-2026-52885</a></td>
    </tr>

    <td class=3D"vendor-product">Ollama AI--Ollama</td>
    <td>Unauthenticated remote information disclosure vulnerability in Ollama's=
    model quantization engine allows an attacker to read and exfiltrate the se= rver's heap memory, potentially leading to sensitive data exposure, further=
    compromise, and stealthy persistence.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-5757" target=3D"= _blank" rel=3D"noopener">CVE-2026-5757</a></td>
    </tr>

    <td class=3D"vendor-product">open-webui--open-webui</td>
    <td>Open WebUI is a self-hosted artificial intelligence platform designed t=
    o operate entirely offline. Prior to 0.9.6, the chat message listener allow=
    s non-same-origin input:prompt and action:submit messages, so an external s= ite can set prompt text and trigger submitPrompt() in an authenticated vict=
    im session. I validated this with a cross-origin attacker page that auto-po= sted messages and caused unauthorized POST /api/v1/chats/new and POST /api/= chat/completions requests containing attacker-controlled prompts. This enab= les cross-site forced actions and model/tool execution under victim privile= ges without consent. This vulnerability is fixed in 0.9.6.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54007" target=3D= "_blank" rel=3D"noopener">CVE-2026-54007</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the sqlo_place_dt_set component of openlink virtuoso-openso= urce v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafte=
    d SQL statements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61018" target=3D= "_blank" rel=3D"noopener">CVE-2025-61018</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the sqlo_key_part_best component of openlink virtuoso-opens= ource v7.2.11 allows attackers to cause a Denial of Service (DoS) via craft=
    ed SQL statements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61019" target=3D= "_blank" rel=3D"noopener">CVE-2025-61019</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the sqlo_strip_in_join component of openlink virtuoso-opens= ource v7.2.11 allows attackers to cause a Denial of Service (DoS) via craft=
    ed SQL statements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61020" target=3D= "_blank" rel=3D"noopener">CVE-2025-61020</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the sqlo_natural_join_cond component of openlink virtuoso-o= pensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via c= rafted SQL statements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61021" target=3D= "_blank" rel=3D"noopener">CVE-2025-61021</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the sqlo_tb_col_preds component of openlink virtuoso-openso= urce v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafte=
    d SQL statements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61022" target=3D= "_blank" rel=3D"noopener">CVE-2025-61022</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the st_compare component of openlink virtuoso-opensource v7= .2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL s= tatements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61023" target=3D= "_blank" rel=3D"noopener">CVE-2025-61023</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the sqlo_try_in_loop component of openlink virtuoso-opensou= rce v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted=
    SQL statements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61024" target=3D= "_blank" rel=3D"noopener">CVE-2025-61024</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the sslr_qst_get component of openlink virtuoso-opensource = v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL=
    statements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61025" target=3D= "_blank" rel=3D"noopener">CVE-2025-61025</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the t_set_push component of openlink virtuoso-opensource v7= .2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL s= tatements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61027" target=3D= "_blank" rel=3D"noopener">CVE-2025-61027</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the time_t_to_dt component of openlink virtuoso-opensource = v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL=
    statements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61028" target=3D= "_blank" rel=3D"noopener">CVE-2025-61028</a></td>
    </tr>

    <td class=3D"vendor-product">openlink virtuoso-opensource--openlink virtuos= o-opensource v7.2.11</td>
    <td>An issue in the sqlo_untry component of openlink virtuoso-opensource v7= .2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL s= tatements.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-61029" target=3D= "_blank" rel=3D"noopener">CVE-2025-61029</a></td>
    </tr>

    <td class=3D"vendor-product">OpenStack--Swift</td>
    <td>In OpenStack Swift before 2.37.2, proxy-server does not strip internal = update headers (X-Container-Host, X-Container-Device, X-Delete-At-Host, X-D= elete-At-Device) from client requests before forwarding them to object-serv= ers. An authenticated user with write access can inject these headers to re= direct container update requests to an attacker-controlled server, enabling=
    server-side request forgery. The SSRF requests expose internal cluster met= adata including storage policy indexes, partition mappings, device names, a=
    nd when at rest encryption is enabled, cipher text and initialization vecto=
    rs for the container-level encryption key. The attacker can also cause "gho=
    st listings" in arbitrary containers via the shard-range redirect mechanism= .</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50221" target=3D= "_blank" rel=3D"noopener">CVE-2026-50221</a></td>
    </tr>

    <td class=3D"vendor-product">OpenText--Access Manager</td>
    <td>An unauthorized user can modify configuration through API calls that af= fects the OpenText Access Manager.=C2=A0This issue affects Access Manager b= efore 5.1.3.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11877" target=3D= "_blank" rel=3D"noopener">CVE-2026-11877</a></td>
    </tr>

    <td class=3D"vendor-product">OpenText--Access Manager</td>
    <td>Improper neutralization of input during web page generation ('cross-sit=
    e scripting') vulnerability in OpenText Access Manager allows Cross-Site Sc= ripting (XSS). This issue affects Access Manager: from 5.1 through 5.1.2.</=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11878" target=3D= "_blank" rel=3D"noopener">CVE-2026-11878</a></td>
    </tr>

    <td class=3D"vendor-product">outline--outline</td>
    <td>Outline is a service that allows for collaborative documentation. Prior=
    to 1.8.0, the AuthenticationHelper.canAccess function uses ctx.originalUrl=
    to verify if an API key or OAuth token has the required scopes for a reque= st. It extracts the resource by splitting the URL by / and taking the last = segment. However, it fails to strip the URL fragment (#). Because Koa's rou= ter uses ctx.path (which strips the fragment) for routing, an attacker can = append a fragment containing a permitted path (e.g., #foo/api/documents.inf=
    o) to a restricted endpoint (e.g., /api/documents.create). The router will = route the request to the restricted endpoint, but canAccess will evaluate t=
    he permitted path in the fragment, bypassing the API key scope restrictions=
    and allowing privilege escalation. This vulnerability is fixed in 1.8.0.</=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54573" target=3D= "_blank" rel=3D"noopener">CVE-2026-54573</a></td>
    </tr>

    <td class=3D"vendor-product">PaperCut--Print Deploy</td>
    <td>An insecure process execution vulnerability exists in the pc-printer-up= dater.exe component of the PaperCut Print Deploy Client for Windows. The ap= plication, which typically operates with high-level system privileges, atte= mpts to perform an internal validation check by invoking a secondary system=
    utility using an unqualified file reference. Because the application does = not specify an absolute path to this utility, it relies on the operating sy= stem's default search order to locate the executable. Under specific condit= ions, a local attacker with the ability to modify directories within the sy= stem's search path could plant a malicious binary that mimics the expected = utility. This could result in the malicious code being executed with SYSTEM=
    privileges, leading to a full compromise of the affected host.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6645" target=3D"= _blank" rel=3D"noopener">CVE-2026-6645</a></td>
    </tr>

    <td class=3D"vendor-product">Payara--Payara Server</td>
    <td>A critical vulnerability in Admin GUI in Payara Server Full 4.x, 5.x, 6= .x, 7.x, 7.2026.x, 6.2025.x, 6.2024.x on All platforms that allows the atta= cker to leak the admin gfresttoken to an attacker-controlled host that can = result in a full unauthenticated takeover of Payara admin domain. A Server-= Side Request Forgery (SSRF) vulnerability in the DownloadServlet of the Adm=
    in GUI in Payara Server allows a remote attacker to exfiltrate the administ= rator's REST session token (gfresttoken) to an attacker-controlled host via=
    a crafted request URL. Combined with the absence of CSRF protection on Dow= nloadServlet, an unauthenticated attacker can trick a logged-in administrat=
    or into triggering the token leak, then replay the stolen token to gain ful=
    l administrative access to the Payara domain, leading to arbitrary code exe= cution via WAR deployment. The vulnerability exists in the=C2=A0DownloadSer= vlet=C2=A0and associated=C2=A0ContentSource=C2=A0implementations (LogViewer= ContentSource,=C2=A0LogFilesContentSource,=C2=A0LBConfigContentSource,=C2= =A0ClientStubsContentSource) within the=C2=A0admingui:console-common=C2=A0m= odule.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12986" target=3D= "_blank" rel=3D"noopener">CVE-2026-12986</a></td>
    </tr>

    <td class=3D"vendor-product">PayloadCMS--PayloadCMS</td>
    <td>An Improper Authorization vulnerability exists in PayloadCMS version 3.= 84.1 due to insufficient access control on the account unlock operation.</t=

    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11779" target=3D= "_blank" rel=3D"noopener">CVE-2026-11779</a></td>
    </tr>

    <td class=3D"vendor-product">Pegasystems--Pega Infinity</td>
    <td>Pega Platform versions 8.3.0 through Infinity 25.1.2 are affected by an=
    authorization weakness that may allow authenticated users to access certai=
    n additional data via crafted URLs.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-62180" target=3D= "_blank" rel=3D"noopener">CVE-2025-62180</a></td>
    </tr>

    <td class=3D"vendor-product">Pentestify--Pentestify</td>
    <td>Server-Side Request Forgery (SSRF) (CWE-918) in the PDF generation endp= oint GET /api/reports/{id}/pdf (backend/main.py) in ccyl13 Pentestify 1.0.0=
    and lower allows remote attackers to make the server issue requests to arb= itrary internal or external URLs, including cloud metadata services, and re= turn the rendered content in the resulting PDF via a crafted Host header, b= ecause the target URL is built from request.base_url without validation.</t=

    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13150" target=3D= "_blank" rel=3D"noopener">CVE-2026-13150</a></td>
    </tr>

    <td class=3D"vendor-product">PHPOffice--PhpSpreadsheet</td>
    <td>PhpSpreadsheet is a pure PHP library for reading and writing spreadshee=
    t files. Prior to 1.30.5, CVE-2026-34084 was patched by the helper File::pr= ohibitWrappers. The helper calls parse_url($filename, PHP_URL_SCHEME) and t= hen checks is_string($scheme) &amp;&amp; strlen($scheme) &gt; 1 to reject s= tream wrappers such as phar://, php://, data:// or expect://. The check is = not equivalent to "does the path contain a wrapper". When the input has the=
    form phar:///path/file.phar/inner with three or more slashes after the sch= eme, parse_url returns boolean false instead of returning the scheme string=
    . The is_string($scheme) branch is therefore skipped, the helper returns wi= thout throwing, and the caller proceeds. PHP's stream layer, however, still=
    treats phar:///... as a valid phar wrapper and opens the underlying phar f= ile. The result is that IOFactory::load($attackerPath) walks past the patch=
    and still touches the phar wrapper. On PHP 7.x, simply reaching the phar w= rapper via is_file is enough for PHP to automatically deserialize the phar = metadata, which in turn invokes the magic methods __wakeup and __destruct o=
    f an attacker controlled object and gives full RCE. On PHP 8.x, automatic m= etadata deserialization for plain file ops was removed, so the chain at the=
    PhpSpreadsheet layer reduces to a phar wrapper file read primitive, and RC=
    E only resurfaces if the downstream consumer ever calls Phar::getMetadata. = This vulnerability is fixed in 1.30.5.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45034" target=3D= "_blank" rel=3D"noopener">CVE-2026-45034</a></td>
    </tr>

    <td class=3D"vendor-product">Pivotal-- Pivotal CRM</td>
    <td>An issue in Pivotal CRM v.6.6.04.08 allows a remote attacker to execute=
    arbitrary code via the Pivotal.Core.Common.dll and Pivotal.Engine.Client.S= ervices.Conversion.dll components.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-39253" target=3D= "_blank" rel=3D"noopener">CVE-2026-39253</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.33.4 and 11.0.7, a malicious cod= eload.github.com server can serve whatever tarball it wants and pnpm will i= nstall it regardless of the lockfile. The lockfile does not store the hash =
    of the dependencies from https://codeload.github.com. This means that if th=
    is server was compromised or a person's machine configuration was compromis= ed, pnpm would download and install these dependencies. This vulnerability =
    is fixed in 10.33.4 and 11.0.7.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48995" target=3D= "_blank" rel=3D"noopener">CVE-2026-48995</a></td>
    </tr>

    <td class=3D"vendor-product">pnpm--pnpm</td>
    <td>pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm can send u= ser-level unscoped npm authentication credentials to a registry chosen by a=
    repository-local .npmrc file. In the reproduced case, the user's npm confi=
    g contains a default registry and an unscoped _authToken. The repository do=
    es not provide a token-bearing auth line. It only sets registry=3D to a dif= ferent registry URL. During normal pnpm metadata/install workflows, pnpm bi= nds the user-origin unscoped credential to the repository-selected registry=
    and sends it as an Authorization header. This vulnerability is fixed in 10= .34.0 and 11.4.0.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50017" target=3D= "_blank" rel=3D"noopener">CVE-2026-50017</a></td>
    </tr>

    <td class=3D"vendor-product">presire--qSnapper</td>
    <td>Lack of authentication when using the "snapshot diff" functions in qSna= pper before version 1.3.3 allowed a local attacker to see otherwise read pr= otected information.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41047" target=3D= "_blank" rel=3D"noopener">CVE-2026-41047</a></td>
    </tr>

    <td class=3D"vendor-product">presire--qSnapper</td>
    <td>Incorrect caching of authentication between different polkit methods in=
    qSnapper before version 1.3.3 allowed a local attacker to use functions li=
    ke "restore from snapshot" even if only allowed to do "delete snapshot".</t=

    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41048" target=3D= "_blank" rel=3D"noopener">CVE-2026-41048</a></td>
    </tr>

    <td class=3D"vendor-product">presire--qSnapper</td>
    <td>Incorrect caching of authentication between different users of the=C2=
    =A0 qSnapper dbus service before version 1.3.3 allowed any local attacker t=
    o use dbus functions after a privileged users has authenticated for them.</=

    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-41049" target=3D= "_blank" rel=3D"noopener">CVE-2026-41049</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--pretix</td>
    <td>Malicious HTML content could be injected into the email address of an o= rder, which pretix showed without sanitization on the confirmation page for=
    individual tickets in that order.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13225" target=3D= "_blank" rel=3D"noopener">CVE-2026-13225</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--pretix</td>
    <td>Malicious HTML content contained in the layout specification of a PDF t= icket or badge layout was executed when the PDF editor is opened in the bro= wser. This could allow one backend user to inject JavaScript into the brows=
    er context of another backend user. Due to requirements of the PDF renderin=
    g and editing libraries used, this is one of the few pages in our backend t= hat do not have a strong Content-Security-Policy that would render this cap= ability useless for most scenarios.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57532" target=3D= "_blank" rel=3D"noopener">CVE-2026-57532</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--pretix</td>
    <td>Malicious HTML content could be injected into the page pretix shows whe=
    n redirection to an untrusted page occurs. Since this page has a Content-Se= curity-Policy, this can mainly be used for phishing purposes.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57533" target=3D= "_blank" rel=3D"noopener">CVE-2026-57533</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--pretix</td>
    <td>Content injected to PDF rendering contexts could, in many places, inclu=
    de HTML content including &lt;img&gt; tags. If the src attribute of these i= mages pointed to an URL, the PDF rendering engine would download the image = from that place and display it, thereby leaking information about the rende= ring server and possibly creating an SSRF vector in the local network.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57535" target=3D= "_blank" rel=3D"noopener">CVE-2026-57535</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--pretix-computop</td>
    <td>Our payment integration with Computop-based payment methods did not pro= perly validate payment status responses. An attacker could use a successful=
    payment status response from one payment and supply it to the system for a=
    different payment, gaining access to multiple valid tickets with only one = payment.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13223" target=3D= "_blank" rel=3D"noopener">CVE-2026-13223</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--pretix-digital</td>
    <td>Malicious HTML content could be injected into the content rendered by t=
    he pretix-digital plugin.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13314" target=3D= "_blank" rel=3D"noopener">CVE-2026-13314</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--pretix-mollie</td>
    <td>Our payment integration with Mollie did not properly validate payment s= tatus responses. An attacker could use a successful payment status response=
    from one payment and supply it to the system for a different payment, gain= ing access to multiple valid tickets with only one payment.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57536" target=3D= "_blank" rel=3D"noopener">CVE-2026-57536</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--pretix-oppwa</td>
    <td>Our payment integration with Oppwa-based payment methods did not proper=
    ly validate payment status responses. An attacker could use a successful pa= yment status response from one payment and supply it to the system for a di= fferent payment, gaining access to multiple valid tickets with only one pay= ment.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13222" target=3D= "_blank" rel=3D"noopener">CVE-2026-13222</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--pretix-pages</td>
    <td>Malicious HTML content could be injected into the content of a page in = the pretix-pages plugin.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57534" target=3D= "_blank" rel=3D"noopener">CVE-2026-57534</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--Venueless</td>
    <td>Untrusted user data was passed verbatim to Excel exports for administra= tors. This allowed formula injection which can be used to compromise the en= vironment of the user loading the file or other data in the file.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12862" target=3D= "_blank" rel=3D"noopener">CVE-2026-12862</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--Venueless</td>
    <td>An unvalidated redirect was contained in Venueless' social login functi= onality and could be exploited for phishing using trusted domains.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12863" target=3D= "_blank" rel=3D"noopener">CVE-2026-12863</a></td>
    </tr>

    <td class=3D"vendor-product">pretix--Venueless</td>
    <td>Permissions where checked incorrectly during room creation, allowing at= tackers to create rooms of types they shouldn't be allowed to create.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13350" target=3D= "_blank" rel=3D"noopener">CVE-2026-13350</a></td>
    </tr>

    <td class=3D"vendor-product">py-pdf--pypdf</td>
    <td>pypdf is a free and open-source pure-python PDF library. Prior to 6.12.=
    2, an attacker who uses this vulnerability can craft a PDF which leads to l= ong runtimes. This requires accessing a stream which uses the /FlateDecode = filter with a PNG predictor. This vulnerability is fixed in 6.12.2.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49460" target=3D= "_blank" rel=3D"noopener">CVE-2026-49460</a></td>
    </tr>

    <td class=3D"vendor-product">py-pdf--pypdf</td>
    <td>pypdf is a free and open-source pure-python PDF library. Prior to 6.12.=
    2, an attacker who uses this vulnerability can craft a PDF which leads to l= arge memory usage. This requires extracting the text of a page which contai=
    ns a form XObject with self-references. This vulnerability is fixed in 6.12= .2.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49461" target=3D= "_blank" rel=3D"noopener">CVE-2026-49461</a></td>
    </tr>

    <td class=3D"vendor-product">py-pdf--pypdf</td>
    <td>pypdf is a free and open-source pure-python PDF library. Prior to 6.13.=
    0, an attacker who uses this vulnerability can craft a PDF which leads to a=
    n infinite loop. This requires extracting the text in layout mode. This vul= nerability is fixed in 6.13.0.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54530" target=3D= "_blank" rel=3D"noopener">CVE-2026-54530</a></td>
    </tr>

    <td class=3D"vendor-product">py-pdf--pypdf</td>
    <td>pypdf is a free and open-source pure-python PDF library. Prior to 6.13.=
    0, an attacker who uses this vulnerability can craft a PDF which leads to a=
    n infinite loop. This requires merging a file with outlines into a writer. = This vulnerability is fixed in 6.13.0.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54531" target=3D= "_blank" rel=3D"noopener">CVE-2026-54531</a></td>
    </tr>

    <td class=3D"vendor-product">py-pdf--pypdf</td>
    <td>pypdf is a free and open-source pure-python PDF library. Prior to 6.13.=
    1, an attacker who uses this vulnerability can craft a PDF which leads to a=
    n infinite loop. This requires merging a file with threads/articles into a = writer. This vulnerability is fixed in 6.13.1.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54651" target=3D= "_blank" rel=3D"noopener">CVE-2026-54651</a></td>
    </tr>

    <td class=3D"vendor-product">Python Software Foundation--CPython</td>
    <td>When using the "configparser" module to write configuration files conta= ining multi-line text values with carriage return characters (\r) the resul= ting file could be injected with unexpected keys and values if the attacker=
    controls the written value.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-0864" target=3D"= _blank" rel=3D"noopener">CVE-2026-0864</a></td>
    </tr>

    <td class=3D"vendor-product">Python Software Foundation--CPython</td> <td>tarfile.extractall() with the 'data' or 'tar' filter could be bypassed =
    by a crafted archive where a hardlink references a symlink stored at a deep=
    er name than the hardlink itself.=C2=A0 The extraction fallback validated t=
    he symlink at it's archived location but recreated it at the hardlink's sha= llower path, letting a relative target the filter judged contained escape t=
    he destination directory.=C2=A0 This allowed a malicious tar archive to cre= ate a symlink pointing outside the destination, enabling out-of-destination=
    file reads or writes. This was an incomplete fix of CVE-2025-4330.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11940" target=3D= "_blank" rel=3D"noopener">CVE-2026-11940</a></td>
    </tr>

    <td class=3D"vendor-product">Python Software Foundation--CPython</td>
    <td>When using the "tarfile" module with a file opened in "streaming mode" = (mode=3D"r|") the tarfile module did not properly handle EOF, making archiv=
    e parsing take exponentially longer.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11972" target=3D= "_blank" rel=3D"noopener">CVE-2026-11972</a></td>
    </tr>

    <td class=3D"vendor-product">QOS.CH Sarl--Logback-core</td>
    <td>ACE vulnerability in conditional configuration file processing by QOS.C=
    H logback-core up to and including version 1.5.35 in Java applications, all= ows an attacker to execute arbitrary code circumventing existing protection=
    s against CVE-2025-11226 by=C2=A0compromising an existing logback configura= tion file or by injecting an environment variable before program execution.=
    A successful attack requires the presence of Janino library to be present =
    on the user's class path. In addition, the attacker must=C2=A0 have write a= ccess to a configuration file. Alternatively, the attacker could inject a m= alicious environment variable pointing to a malicious configuration file. I=
    n both cases, the attack requires existing privilege.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13006" target=3D= "_blank" rel=3D"noopener">CVE-2026-13006</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup viewclient Cross-Site Scripting Authentication By= pass Vulnerability. This vulnerability allows remote attackers to bypass au= thentication on affected installations of Quest NetVault Backup. User inter= action is required to exploit this vulnerability in that the target must vi= sit a malicious page or open a malicious file. The specific flaw exists wit= hin the viewclient webpage. The issue results from the lack of proper valid= ation of user-supplied data, which can lead to the injection of an arbitrar=
    y script. An attacker can leverage this in conjunction with other vulnerabi= lities to execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-2820= 2.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7569" target=3D"= _blank" rel=3D"noopener">CVE-2026-7569</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup NVBUDashboard SQL Injection Remote Code Execution=
    Vulnerability. This vulnerability allows remote attackers to execute arbit= rary code on affected installations of Quest NetVault Backup. Although auth= entication is required to exploit this vulnerability, the existing authenti= cation mechanism can be bypassed. The specific flaw exists within the proce= ssing of NVBUDashboard JSON-RPC messages. The issue results from the lack o=
    f proper validation of a user-supplied string before using it to construct = SQL queries. An attacker can leverage this vulnerability to execute code in=
    the context of NETWORK SERVICE. Was ZDI-CAN-27809.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7570" target=3D"= _blank" rel=3D"noopener">CVE-2026-7570</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup addclient3 Cross-Site Scripting Authentication By= pass Vulnerability. This vulnerability allows remote attackers to bypass au= thentication on affected installations of Quest NetVault Backup. User inter= action is required to exploit this vulnerability in that the target must vi= sit a malicious page or open a malicious file. The specific flaw exists wit= hin the addclient3 webpage. The issue results from the lack of proper valid= ation of user-supplied data, which can lead to the injection of an arbitrar=
    y script. An attacker can leverage this in conjunction with other vulnerabi= lities to execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-2766= 6.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9780" target=3D"= _blank" rel=3D"noopener">CVE-2026-9780</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup NVBURASDevice SQL Injection Remote Code Execution=
    Vulnerability. This vulnerability allows remote attackers to execute arbit= rary code on affected installations of Quest NetVault Backup. Although auth= entication is required to exploit this vulnerability, the existing authenti= cation mechanism can be bypassed. The specific flaw exists within the proce= ssing of NVBURASDevice JSON-RPC messages. The issue results from the lack o=
    f proper validation of a user-supplied string before using it to construct = SQL queries. An attacker can leverage this vulnerability to execute code in=
    the context of NETWORK SERVICE. Was ZDI-CAN-27648.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9781" target=3D"= _blank" rel=3D"noopener">CVE-2026-9781</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup NVBUDeviceDrive SQL Injection Remote Code Executi=
    on Vulnerability. This vulnerability allows remote attackers to execute arb= itrary code on affected installations of Quest NetVault Backup. Although au= thentication is required to exploit this vulnerability, the existing authen= tication mechanism can be bypassed. The specific flaw exists within the pro= cessing of NVBUDeviceDrive JSON-RPC messages. The issue results from the la=
    ck of proper validation of a user-supplied string before using it to constr= uct SQL queries. An attacker can leverage this vulnerability to execute cod=
    e in the context of NETWORK SERVICE. Was ZDI-CAN-27633.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9782" target=3D"= _blank" rel=3D"noopener">CVE-2026-9782</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup NVBURemovableMedia SQL Injection Remote Code Exec= ution Vulnerability. This vulnerability allows remote attackers to execute = arbitrary code on affected installations of Quest NetVault Backup. Although=
    authentication is required to exploit this vulnerability, the existing aut= hentication mechanism can be bypassed. The specific flaw exists within the = processing of NVBURemovableMedia JSON-RPC messages. The issue results from = the lack of proper validation of a user-supplied string before using it to = construct SQL queries. An attacker can leverage this vulnerability to execu=
    te code in the context of NETWORK SERVICE. Was ZDI-CAN-27632.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9783" target=3D"= _blank" rel=3D"noopener">CVE-2026-9783</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup NVBULibraryPort SQL Injection Remote Code Executi=
    on Vulnerability. This vulnerability allows remote attackers to execute arb= itrary code on affected installations of Quest NetVault Backup. Although au= thentication is required to exploit this vulnerability, the existing authen= tication mechanism can be bypassed. The specific flaw exists within the pro= cessing of NVBULibraryPort JSON-RPC messages. The issue results from the la=
    ck of proper validation of a user-supplied string before using it to constr= uct SQL queries. An attacker can leverage this vulnerability to execute cod=
    e in the context of NETWORK SERVICE. Was ZDI-CAN-27631.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9784" target=3D"= _blank" rel=3D"noopener">CVE-2026-9784</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup NVBULibrarySlot SQL Injection Remote Code Executi=
    on Vulnerability. This vulnerability allows remote attackers to execute arb= itrary code on affected installations of Quest NetVault Backup. Although au= thentication is required to exploit this vulnerability, the existing authen= tication mechanism can be bypassed. The specific flaw exists within the pro= cessing of NVBULibrarySlot JSON-RPC messages. The issue results from the la=
    ck of proper validation of a user-supplied string before using it to constr= uct SQL queries. An attacker can leverage this vulnerability to execute cod=
    e in the context of NETWORK SERVICE. Was ZDI-CAN-27630.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9785" target=3D"= _blank" rel=3D"noopener">CVE-2026-9785</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup NVBUDashboard SQL Injection Remote Code Execution=
    Vulnerability. This vulnerability allows remote attackers to execute arbit= rary code on affected installations of Quest NetVault Backup. Although auth= entication is required to exploit this vulnerability, the existing authenti= cation mechanism can be bypassed. The specific flaw exists within the proce= ssing of NVBUDashboard JSON-RPC messages. The issue results from the lack o=
    f proper validation of a user-supplied string before using it to construct = SQL queries. An attacker can leverage this vulnerability to execute code in=
    the context of NETWORK SERVICE. Was ZDI-CAN-27626.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9786" target=3D"= _blank" rel=3D"noopener">CVE-2026-9786</a></td>
    </tr>

    <td class=3D"vendor-product">Quest--NetVault Backup</td>
    <td>Quest NetVault Backup NVBULogDaemon Command Injection Remote Code Execu= tion Vulnerability. This vulnerability allows remote attackers to execute a= rbitrary code on affected installations of Quest NetVault Backup. Although = authentication is required to exploit this vulnerability, the existing auth= entication mechanism can be bypassed. The specific flaw exists within the p= rocessing of NVBULogDaemon JSON-RPC messages. The issue results from the la=
    ck of proper validation of a user-supplied string before using it to execut=
    e a system call. An attacker can leverage this vulnerability to execute cod=
    e in the context of SYSTEM. Was ZDI-CAN-27625.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9787" target=3D"= _blank" rel=3D"noopener">CVE-2026-9787</a></td>
    </tr>

    <td class=3D"vendor-product">Redox--Relibc</td>
    <td>An issue in the pthread_rwlockattr_setpshared() function of relibc comm=
    it 61f42d allows attackers to cause a Denial of Service (DoS) via a crafted=
    input.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-38637" target=3D= "_blank" rel=3D"noopener">CVE-2026-38637</a></td>
    </tr>

    <td class=3D"vendor-product">Redox--Relibc</td>
    <td>An issue in the parse_month function (/time/strptime.rs) of relibc comm=
    it ab6a2e allows attackers to cause a Denial of Service (DoS) via parsing a=
    crafted input.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-38639" target=3D= "_blank" rel=3D"noopener">CVE-2026-38639</a></td>
    </tr>

    <td class=3D"vendor-product">Redox--Relibc</td>
    <td>A reachable unwrap in the __assert_fail function (/assert/mod.rs) of re= libc commit 61f42d allows attackers to cause a Denial of Service (DoS) via =
    a crafted string.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-38640" target=3D= "_blank" rel=3D"noopener">CVE-2026-38640</a></td>
    </tr>

    <td class=3D"vendor-product">Redox--Relibc</td>
    <td>An issue in the DSO::mmap_and_copy function of relibc commit 61f42d all= ows attackers to cause a Denial of Service (DoS) via loading a crafted shar=
    ed library.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-38641" target=3D= "_blank" rel=3D"noopener">CVE-2026-38641</a></td>
    </tr>

    <td class=3D"vendor-product">Reolink--Home Hub</td>
    <td>A vulnerability exists in the netclient and factory services of Reolink=
    Home Hub (versions prior to v3.3.0.456_26031911) due to the possibility of=
    brute-force cracking the credentials. This issue could allow attackers on = the same local network to intercept traffic between the Hub and associated = cameras and compromise the credentials of connected cameras.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57473" target=3D= "_blank" rel=3D"noopener">CVE-2026-57473</a></td>
    </tr>

    <td class=3D"vendor-product">Revive Adserver--Revive Adserver</td>
    <td>A missing validation of user input when saving delivery limitations in = Revive Adserver 6.0.6 and earlier could allow a low-privileged user to use = the logical parameter to inject malicious PHP code into the compiledlimitat= ions field on the database and have it executed during banner delivery. Inp=
    ut sanitisation has been improved to ensure that the parameter is properly = validated.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-34916" target=3D= "_blank" rel=3D"noopener">CVE-2026-34916</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A missing access control check when linking banners or campaigns to a z= one through the zone-include.php script of Revive Adserver 6.0.6 and earlie=
    r, or via its API allows a low-privileged user could link their zones to ba= nners or campaigns owned by other managers on the same instance, resulting =
    in inconsistent ownership relationships. Ownership validation has been adde=
    d to ensure that banners and campaigns can only be linked to zones managed =
    by the same account.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-34912" target=3D= "_blank" rel=3D"noopener">CVE-2026-34912</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A missing access control check when linking trackers to campaigns throu=
    gh the campaign-trackers.php script of Revive Adserver 6.0.6 and earlier co= uld allow a low-privileged user to link their trackers to campaigns owned b=
    y other managers on the same instance, resulting in inconsistent ownership = relationships. Ownership validation has been added to ensure that campaigns=
    can only be linked to trackers owned by the same advertiser.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-34913" target=3D= "_blank" rel=3D"noopener">CVE-2026-34913</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A missing sanitisation of user input in the zone-include.php script of = Revive Adserver 6.0.6 and earlier. A low-privileged user could exploit the = clientid parameter to perform blind SQL injection attacks. Input sanitisati=
    on has been improved to ensure that all parameters processed by the script = are properly validated.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-34914" target=3D= "_blank" rel=3D"noopener">CVE-2026-34914</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A missing sanitisation of user input in the zone-include.php script of = Revive Adserver 6.0.6 and earlier could allow a low-privileged user to expl= oit the clientid parameter to perform blind SQL injection attacks. Input sa= nitisation has been improved to ensure that all parameters processed by the=
    script are properly validated.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-34915" target=3D= "_blank" rel=3D"noopener">CVE-2026-34915</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>Low-privileged session IDs generated for the web admin console could be=
    reused in the XML RPC API, whose authentication is normally restricted to = admin users. An attacker could leverage this to gain unauthorised access an=
    d exploit API level vulnerabilities. The session context (web/API) is now r= ecorded along with other session data, preventing session IDs from being us=
    ed interchangeably.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-34917" target=3D= "_blank" rel=3D"noopener">CVE-2026-34917</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>Low-privileged users could use their Full Name as a vector for a stored=
    XSS attack. The name is included in system generated emails, whose content=
    is stored in the details field of the userlog table. An admin user viewing=
    the email content through userlog-details.php would have any malicious Jav= aScript payload executed due to missing output sanitisation. Proper escapin=
    g has been added to the userlog details output.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44956" target=3D= "_blank" rel=3D"noopener">CVE-2026-44956</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A missing access control check when invoking various modify methods in = the XML RPC API of Revive Adserver 6.0.6 and earlier. The API allowed entit= ies to be reassigned to different parent entities, leading to inconsistent = ownership relationships. This issue was exploitable only in combination wit=
    h CVE-2026-34917 or with third-party API extensions that expose API functio= nality to low-privileged users. Access control checks have been added to va= lidate access to parent entities in the API modify methods.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44957" target=3D= "_blank" rel=3D"noopener">CVE-2026-44957</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>An access control bypass allows an advertiser-level user to activate or=
    deactivate a banner in Revive Adserver 6.0.6 and earlier, even when such p= ermissions were not granted. The banner-edit.php script allowed the banner = status to be overwritten solely based on banner edit permissions. The statu=
    s field has been removed from the hidden form fields in the banner edit scr= een.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44958" target=3D= "_blank" rel=3D"noopener">CVE-2026-44958</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A missing validation of user input exists when saving delivery limitati= ons in Revive Adserver 6.0.6 and earlier. A low-privileged user could add a=
    n unexpected component parameter and inject malicious PHP code into the com= piledlimitations field, which would then be executed during banner delivery=
    . Input sanitisation has been improved to ensure that unexpected parameters=
    are filtered out.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44959" target=3D= "_blank" rel=3D"noopener">CVE-2026-44959</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A stored XSS can be exploited by leveraging the usernames as an attack = vector. When an admin user viewed the audit log details for affected entrie=
    s, any malicious JavaScript payload embedded in the username would be execu= ted due to missing output sanitisation. Proper escaping has been added to t=
    he audit log details output.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44960" target=3D= "_blank" rel=3D"noopener">CVE-2026-44960</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>The XML-RPC API addUser method has a validation bypass introduced in th=
    e fix for CVE-2025-55129. As a result, API users could create usernames tha=
    t enabled impersonation or stored XSS attacks. Proper validation has been a= dded where it was missing.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44961" target=3D= "_blank" rel=3D"noopener">CVE-2026-44961</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A bypass for CVE-2026-34913 exists with proper ownership validation tha=
    t had not been applied to the reverse operation of linking campaigns and tr= ackers through the `tracker-campaigns.php` script in Revive Adserver 6.0.7 = and earlier. As a result, a low-privileged user could link their trackers t=
    o campaigns owned by other managers on the same instance, leading to incons= istent ownership relationships.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50739" target=3D= "_blank" rel=3D"noopener">CVE-2026-50739</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A missing sanitisation vulnerability of user input in the zone-include.= php script exists in Revive Adserver 6.0.7 and earlier. A low-privileged us=
    er could exploit the refresh parameter of the iFrame invocation tag to perf= orm reflected XSS attacks.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50740" target=3D= "_blank" rel=3D"noopener">CVE-2026-50740</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>Bypass to the fix for CVE-2026-34916. Variants of such vectors have bee=
    n also reported by phucrio and offsetmd. The fix can be bypassed either by = sending a disallowed but otherwise valid plugin identifier as `type`, or us= ing the `ox.setChannelTargeting` XML-RPC API method.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50741" target=3D= "_blank" rel=3D"noopener">CVE-2026-50741</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A stored XSS vulnerabilities exists in the `maintenance-acl-check.php` = and `maintenance-banners-check.php` tools of Revive Adserver 6.0.7. The iss=
    ue was caused by entity names being displayed without proper escaping when = inconsistencies were detected. Whether the XSS payload is executed when an = administrator uses the affected maintenance tools is not entirely under the=
    attacker's control.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50742" target=3D= "_blank" rel=3D"noopener">CVE-2026-50742</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A bypass to the admin-only restriction of the XML-RPC API in Revive Ads= erver 6.0.7. The API response for the ox.login method returned a session ID=
    cookie in the HTTP headers, and although the method correctly returned an = error, the associated session was not invalidated. As a result, the leaked = session ID could be used to perform subsequent API calls without restrictio= ns.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50744" target=3D= "_blank" rel=3D"noopener">CVE-2026-50744</a></td>
    </tr>

    <td class=3D"vendor-product">Revive--Adserver</td>
    <td>A missing sanitisation vulnerability exists with user input in the stat= s-video.php script. The way URLs to this script were constructed did not fo= llow best practices, and the output of the Smarty custom helper function ur=
    l was neither properly encoded nor sanitised, allowing user-supplied input =
    to be reflected without escaping.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-50745" target=3D= "_blank" rel=3D"noopener">CVE-2026-50745</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and = 7.10.11, Rocket.Chat's SAML integration does not verify the signature on in= bound LogoutRequest messages. An unauthenticated remote attacker who knows =
    a target user's SAML NameID - which major identity providers (Okta, Google = Workspace, Microsoft Entra ID, JumpCloud) expose as the user's email addres=
    s - can craft a valid-looking unsigned LogoutRequest and submit it to the S=
    P logout endpoint. The server processes it as legitimate, immediately destr= oying the victim's session. Because the attack requires no authentication a=
    nd no interaction from the victim, it can be repeated in a loop against ind= ividual users or scripted across many accounts, effectively rendering the R= ocket.Chat instance unusable for SAML-authenticated users. This vulnerabili=
    ty is fixed in 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.1= 1.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45677" target=3D= "_blank" rel=3D"noopener">CVE-2026-45677</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and = 7.10.12, Rocket.Chat allows users deactivated through users.deactivateIdle =
    to keep using already-issued login tokens. A user that an administrator has=
    marked inactive for idleness can still access authenticated REST endpoints=
    with the old token. This vulnerability is fixed in 8.5.0, 8.4.2, 8.3.4, 8.= 2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45757" target=3D= "_blank" rel=3D"noopener">CVE-2026-45757</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and = 7.10.11, Rocket.Chat's SAML service provider implementation silently skips = both SAML Response and Assertion signature validation when the configured I=
    dP certificate field is empty. The verifySignatures routine performs an ear=
    ly return when serviceProviderOptions.cert is falsy, which is the default s= tate of the setting. Because provider registration only gates on the SAML "= enabled" toggle and not on the presence of a certificate, an administrator = who enables SAML without pasting an IdP certificate obtains a fully wired, = publicly reachable SAML login endpoint that accepts unsigned or attacker-su= pplied assertions. This is a default-configuration authentication-bypass cl= ass: the fail-open branch is reached with no misconfiguration beyond leavin=
    g a field at its shipped default. This vulnerability is fixed in 8.5.0, 8.4= .1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-46423" target=3D= "_blank" rel=3D"noopener">CVE-2026-46423</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and = 7.10.12, Rocket.Chat does not revoke OAuth bearer or refresh tokens when a = user is deactivated. A deactivated user can continue using an existing OAut=
    h access token, and can also mint a fresh access token from an existing ref= resh token. This vulnerability is fixed in 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.=
    5, 8.0.6, 7.13.8, and 7.10.12.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-49277" target=3D= "_blank" rel=3D"noopener">CVE-2026-49277</a></td>
    </tr>

    <td class=3D"vendor-product">RocketChat--Rocket.Chat</td>
    <td>Rocket.Chat is an open-source, secure, fully customizable communication=
    s platform. Prior to 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13,=
    in apps/meteor/app/apple/server/loginHandler.ts, handleIdentityToken parse=
    s a JWT issued by Apple during the OAuth flow. The try block checks for an = email parameter. If the JWT does not contain an email address, the applicat= ion falls back to accepting an arbitrary email value supplied directly in t=
    he request. Attackers are able to forge Apple JWTs that do not contain an e= mail address and leverage this vulnerability to carry out account takeover = attacks. This vulnerability is fixed in 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, = 8.0.7, and 7.10.13.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55666" target=3D= "_blank" rel=3D"noopener">CVE-2026-55666</a></td>
    </tr>

    <td class=3D"vendor-product">rtk-ai--rtk</td>
    <td>rtk filters and compresses command outputs before they reach your LLM c= ontext. Prior to 0.32.0, RTK (Rust Token Killer) improperly trusts project-= local configuration files. RTK automatically loads .rtk/filters.toml from t=
    he working directory with highest priority and without user notification. A=
    n attacker can place a malicious filter file in a repository to apply regex= -based modifications (e.g., strip_lines_matching) to shell command output b= efore it is shown to the LLM, without any indication that the output has be=
    en modified. This allows attackers to selectively suppress or alter command=
    output (including file contents, diffs, and security scan results) without=
    detection, potentially concealing malicious code during AI-assisted develo= pment or review. This vulnerability is fixed in 0.32.0.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-45792" target=3D= "_blank" rel=3D"noopener">CVE-2026-45792</a></td>
    </tr>

    <td class=3D"vendor-product">ruby--net-imap</td>
    <td>Net::IMAP implements Internet Message Access Protocol (IMAP) client fun= ctionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands a= ccept a "raw data" argument that is sent verbatim after validation to preve=
    nt command injection. However, if a server does not support non-synchronizi=
    ng literals, it may still be possible to inject arbitrary IMAP commands ins= ide non-synchronizing literals. A server without support for non-synchroniz= ing literals may interpret the "+}\r\n" as the end of a malformed command l= ine and respond with a tagged BAD. In that case, the contents of the litera=
    l will be interpreted as one or more new pipelined commands, allowing a CRL=
    F command injection attack to succeed. This affects criteria for #search an=
    d #uid_search; search_keys for #sort, #thread, #uid_sort, and #uid_thread; = and attr for #fetch and #uid_fetch. This vulnerability is fixed in 0.6.5 an=
    d 0.5.15.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47240" target=3D= "_blank" rel=3D"noopener">CVE-2026-47240</a></td>
    </tr>

    <td class=3D"vendor-product">ruby--net-imap</td>
    <td>Net::IMAP implements Internet Message Access Protocol (IMAP) client fun= ctionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands a= ccept a raw string argument which is only validated to prevent CRLF injecti=
    on and then sent verbatim. If this string is derived from user-controlled i= nput, an attacker can force the next command to be absorbed as a continuati=
    on of the first command. This will cause the first command to eventually fa= il, but also prevents it from returning until another command is sent (from=
    another thread). That other command will not return until the connection i=
    s closed. This vulnerability is fixed in 0.6.5 and 0.5.15.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47241" target=3D= "_blank" rel=3D"noopener">CVE-2026-47241</a></td>
    </tr>

    <td class=3D"vendor-product">ruby--net-imap</td>
    <td>Net::IMAP implements Internet Message Access Protocol (IMAP) client fun= ctionality in Ruby. Prior to 0.6.5 and 0.5.15, when Net::IMAP#id is called = with a hash argument, although the ID field value strings are correctly quo= ted (escaping quoted specials), they were not validated to prohibit CRLF se= quences. While Net::IMAP#enable does process its arguments for aliases, it = does not validate them as valid atoms (or as a list of valid atoms). The #t= o_s value is sent verbatim. Arguments to either command could be used by an=
    attacker to inject arbitrary IMAP commands. This vulnerability is fixed in=
    0.6.5 and 0.5.15.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47242" target=3D= "_blank" rel=3D"noopener">CVE-2026-47242</a></td>
    </tr>

    <td class=3D"vendor-product">ruby-concurrency--concurrent-ruby</td> <td>concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7,=
    Concurrent::AtomicReference#update can enter a permanent busy retry loop w= hen the current value is Float::NAN. The issue is caused by the interaction=
    between AtomicReference#update, which retries until compare_and_set(old_va= lue, new_value) succeeds; Numeric compare_and_set, which checks old =3D=3D = old_value before attempting the underlying atomic swap.; and Ruby NaN seman= tics, where Float::NAN =3D=3D Float::NAN is always false. As a result, once=
    an AtomicReference contains Float::NAN, calling #update repeatedly evaluat=
    es the caller's block and never returns. In services that store externally = derived numeric values in an AtomicReference, this can cause CPU exhaustion=
    or permanent request/job hangs. This vulnerability is fixed in 1.3.7.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54904" target=3D= "_blank" rel=3D"noopener">CVE-2026-54904</a></td>
    </tr>

    <td class=3D"vendor-product">ruby-concurrency--concurrent-ruby</td> <td>concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7,=
    Concurrent::ReentrantReadWriteLock can incorrectly grant a write lock afte=
    r one thread acquires the read lock 32,768 times. The lock stores a thread'=
    s local read and write hold counts in one integer. The low 15 bits are used=
    for the read hold count, and bit 15 is used as WRITE_LOCK_HELD. After 32,7=
    68 reentrant read acquisitions, the local read count crosses into the write= -lock bit. try_write_lock then treats the thread as already holding a write=
    lock and returns true without setting the global RUNNING_WRITER bit. This = breaks the core mutual-exclusion guarantee: the caller is told it has a wri=
    te lock, but other threads can still hold or acquire read locks at the same=
    time. This vulnerability is fixed in 1.3.7.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54905" target=3D= "_blank" rel=3D"noopener">CVE-2026-54905</a></td>
    </tr>

    <td class=3D"vendor-product">ruby-concurrency--concurrent-ruby</td> <td>concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7,=
    Concurrent::ReadWriteLock#release_write_lock does not verify that the call= ing thread acquired the write lock. Any thread with access to the lock obje=
    ct can release an active write lock held by another thread. A second writer=
    can then enter its critical section while the first writer is still runnin=
    g. Concurrent::ReadWriteLock#release_read_lock also decrements the shared c= ounter even when no read lock is held. Calling it on a fresh lock changes t=
    he counter from 0 to -1, after which normal read acquisition raises Concurr= ent::ResourceLimitError. This is a synchronization correctness issue in the=
    public Concurrent::ReadWriteLock API. This vulnerability is fixed in 1.3.7= .</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54906" target=3D= "_blank" rel=3D"noopener">CVE-2026-54906</a></td>
    </tr>

    <td class=3D"vendor-product">SafeLine--SafeLine SL6/SL6+</td>
    <td>The SafeLine SL6 and SL6+ devices integrated into elevator emergency in= tercom systems are vulnerable to an authentication bypass. This vulnerabili=
    ty allows attackers to bypass authentication requirements and access the de= vice's configuration service via the Bluetooth Low Energy (BLE) interface. = Consequently, an attacker within wireless range can gain unauthorized admin= istrative access to the device configuration.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-4994" target=3D"= _blank" rel=3D"noopener">CVE-2025-4994</a></td>
    </tr>

    <td class=3D"vendor-product">Safetica--Endpoint Client</td>
    <td>Kernel driver ProcessMonitorDriver.sys in Safetica's endpoint client x6=
    4 , versions 10.5.75.0 and 11.11.4.0, allows unprivileged user to abuse IOC=
    TL path and terminate protected system processes.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-0828" target=3D"= _blank" rel=3D"noopener">CVE-2026-0828</a></td>
    </tr>

    <td class=3D"vendor-product">Schneider Electric--EasyLogic T150 (formerly S= aitel DR) Remote Terminal Unit &amp; Controller</td>
    <td>CWE-522 Insufficiently Protected Credentials vulnerability that could c= ause unauthorized access and exposure of sensitive information when unauthe= nticated attacker accesses credentials stored within firmware or system fil= es. With this credential an attacker could subsequently compromise the devi=
    ce if they have physical access to the device.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9650" target=3D"= _blank" rel=3D"noopener">CVE-2026-9650</a></td>
    </tr>

    <td class=3D"vendor-product">Schneider Electric--EasyLogic T150 (formerly S= aitel DR) Remote Terminal Unit &amp; Controller</td>
    <td>CWE-732 Incorrect Permission Assignment for Critical Resource vulnerabi= lity that could cause unauthorized disclosure of password hashes and potent= ial account compromise when an attacker with privileged local access reads = improperly protected system files.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9651" target=3D"= _blank" rel=3D"noopener">CVE-2026-9651</a></td>
    </tr>

    <td class=3D"vendor-product">Schneider Electric--PowerLogic P7</td>
    <td>CWE-476 NULL Pointer Dereference vulnerability exists that could cause =
    a denial-of-service condition, rendering the device's HMI and configuration=
    functionality unavailable when malformed requests are received over expose=
    d network interfaces.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9716" target=3D"= _blank" rel=3D"noopener">CVE-2026-9716</a></td>
    </tr>

    <td class=3D"vendor-product">Schneider Electric--PowerLogic P7</td>
    <td>CWE-78 Neutralization of Special Elements used in an OS Command ('OS Co= mmand Injection') vulnerability exists that could allow unauthorized execut= ion of commands with elevated privileges, impacting system integrity, confi= dentiality, and availability when a privileged authenticated user interacts=
    with a vulnerable network-exposed service.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9717" target=3D"= _blank" rel=3D"noopener">CVE-2026-9717</a></td>
    </tr>

    <td class=3D"vendor-product">Schneider Electric--PowerLogic P7</td>
    <td>CWE-617 Reachable Assertion vulnerability exists that could allow an au= thenticated attacker to trigger a denial-of-service condition, impacting sy= stem availability when a specially crafted request is sent to a vulnerable = network-exposed service.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9718" target=3D"= _blank" rel=3D"noopener">CVE-2026-9718</a></td>
    </tr>

    <td class=3D"vendor-product">seaweedfs--seaweedfs</td>
    <td>SeaweedFS is a distributed storage system for object storage (S3), file=
    systems, and Iceberg tables. Prior to 4.30, the S3 API gateway and the Ice= berg REST catalog gateway construct their routers with mux.NewRouter().Skip= Clean(true). With path cleaning disabled, a .. segment inside the URL survi= ves routing, so a request such as `GET /bucket-A/../evil-bucket/key`, is ma= tched as bucket=3Dbucket-A, object=3D../evil-bucket/key. The captured objec=
    t key is then joined into a filer path with util.JoinPath (S3) / path.Join = (Iceberg), which collapse the .. server-side, so the actual read or write l= ands in evil-bucket. This vulnerability is fixed in 4.30.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54917" target=3D= "_blank" rel=3D"noopener">CVE-2026-54917</a></td>
    </tr>

    <td class=3D"vendor-product">Significant-Gravitas--AutoGPT</td>
    <td>AutoGPT is a workflow automation platform for creating, deploying, and = managing continuous artificial intelligence agents. Prior to 0.6.32, there =
    is a DoS vulnerability in AITextSummarizerBlock. Malicious users can amplif=
    y their input. For example, if a malicious user inputs 10K of content, the = server will consume 50G of memory, eventually causing memory resources to b=
    e exhausted, resulting in DoS. This vulnerability is fixed in 0.6.32.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-32394" target=3D= "_blank" rel=3D"noopener">CVE-2025-32394</a></td>
    </tr>

    <td class=3D"vendor-product">Significant-Gravitas--AutoGPT</td>
    <td>AutoGPT is a workflow automation platform for creating, deploying, and = managing continuous artificial intelligence agents. Prior to 0.6.32, there =
    is a DoS vulnerability in ExtractTextInformationBlock. Malicious users can = amplify their input. For example, if a malicious user inputs 10K of content=
    , the server will consume 50G of memory, eventually causing memory resource=
    s to be exhausted, resulting in DoS. This vulnerability is fixed in 0.6.32.= </td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-32423" target=3D= "_blank" rel=3D"noopener">CVE-2025-32423</a></td>
    </tr>

    <td class=3D"vendor-product">silabs.com--Simplicity SDK</td>
    <td>SYMCRYPTO is the SiXG301's host side hardware engine accessed by PSA cr= ypto library that accelerates symmetric cryptographic operations (AES encry= ption/decryption and hashing). DPA Countermeasures on SYMCRYPTO can be weak= ened (reduced entropy) by forcing certain seed values if an attacker gains = code execution capability on the impacted device. * Therefore, the keys loa= ded on SYMCRYPTO may be more vulnerable to extraction through DPA attacks t= han intended</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-4930" target=3D"= _blank" rel=3D"noopener">CVE-2026-4930</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, malformed global ZCL messages can trig= ger out-of-bounds reads in framework parsing logic and terminate the proces=
    s. These messages must come from a device that has already joined the netwo= rk, and no information leakage back to the sender was observed.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-4526" target=3D"= _blank" rel=3D"noopener">CVE-2026-4526</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, malformed Color Control messages can l= ead to asserts that terminate the process. These messages must come from a = device that has already joined the network. Only devices supporting the Col=
    or Control cluster may be impacted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47145" target=3D= "_blank" rel=3D"noopener">CVE-2026-47145</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, malformed Color Control messages can l= ead to asserts that terminate the process. These messages must come from a = device that has already joined the network. Only devices supporting the Col=
    or Control cluster may be impacted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47146" target=3D= "_blank" rel=3D"noopener">CVE-2026-47146</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, malformed OTA requests can drive the O=
    TA server parser into out-of-bounds reads. A limited amount of data from RA=
    M is read back to the requester. The size and location of this data is limi= ted. These requests must come from a device that has already joined the net= work. Only devices supporting the OTA Server cluster may be impacted.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47147" target=3D= "_blank" rel=3D"noopener">CVE-2026-47147</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, malformed GetGroupMembership commands = can trigger repeated reads past the end of the message payload and terminat=
    e the process. These messages must come from a device that has already join=
    ed the network, and no information leakage back to the sender was observed.=
    Only devices supporting the Groups cluster may be impacted.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47148" target=3D= "_blank" rel=3D"noopener">CVE-2026-47148</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, malformed or out-of-range Door Lock us=
    er identifiers can trigger out-of-bounds table reads and terminate the proc= ess. These messages must come from a device that has already joined the net= work, and no information leakage back to the sender was observed. Only devi= ces supporting the Door Lock cluster may be impacted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47149" target=3D= "_blank" rel=3D"noopener">CVE-2026-47149</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, malformed IAS Zone enrollment messages=
    can trigger an out-of-bounds state-table write and terminate the process. = The size and location of this write is limited. These messages must come fr=
    om a device that has already joined the network. Only devices supporting th=
    e IAS Zone cluster may be impacted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47150" target=3D= "_blank" rel=3D"noopener">CVE-2026-47150</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, malformed ClearWeekdaySchedule message=
    s can trigger out-of-bounds writes into Door Lock schedule state. The size = and location of this data is limited. These messages must come from a devic=
    e that has already joined the network. Only devices supporting the Door Loc=
    k cluster may be impacted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47151" target=3D= "_blank" rel=3D"noopener">CVE-2026-47151</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, a malformed Level Control Move command=
    can terminate the process through a divide-by-zero fault. This command mus=
    t come from a device that has already joined the network. Only devices supp= orting the Level Control cluster may be impacted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47152" target=3D= "_blank" rel=3D"noopener">CVE-2026-47152</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, a malformed Level Control Step command=
    can terminate the process through a divide-by-zero fault. This command mus=
    t come from a device that has already joined the network. Only devices supp= orting the Level Control cluster may be impacted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47153" target=3D= "_blank" rel=3D"noopener">CVE-2026-47153</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--EmberZNet</td>
    <td>In EmberZNet v9.0.2 and earlier, a malformed GetProfileResponse message=
    can trigger out-of-bounds reads while iterating interval entries and termi= nate the process. These messages must come from a device that has already j= oined the network, and no information leakage back to the sender was observ= ed. Only devices supporting the Simple Metering cluster may be impacted.</t=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-47154" target=3D= "_blank" rel=3D"noopener">CVE-2026-47154</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--SiSDK</td>
    <td>Incorrect use of the PUF key for user key generation in EFR32xG27 resul=
    ts in predictable keys</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-2815" target=3D"= _blank" rel=3D"noopener">CVE-2026-2815</a></td>
    </tr>

    <td class=3D"vendor-product">Silicon Labs--SiSDK</td>
    <td>Improper bounds validation in EmberZNet SDK versions 9.0.2 and earlier = may result in crashes or dynamic memory leakage.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6432" target=3D"= _blank" rel=3D"noopener">CVE-2026-6432</a></td>
    </tr>

    <td class=3D"vendor-product">siyuan-note--siyuan</td>
    <td>SiYuan is an open-source personal knowledge management system. Prior to=
    3.7.0, SiYuan Note's kernel HTTP server unconditionally trusts all chrome-= extension:// origins, granting RoleAdministrator access to every installed = browser extension without any authentication. Combined with the default emp=
    ty AccessAuthCode on desktop installs, any Chrome/Chromium extension -- inc= luding a compromised legitimate extension via supply chain attack -- can ma=
    ke fully authenticated admin API calls to the SiYuan kernel at 127.0.0.1:68= 06, enabling data exfiltration, stored XSS injection, and configuration tam= pering. This vulnerability is fixed in 3.7.0.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54069" target=3D= "_blank" rel=3D"noopener">CVE-2026-54069</a></td>
    </tr>

    <td class=3D"vendor-product">siyuan-note--siyuan</td>
    <td>SiYuan is an open-source personal knowledge management system. Prior to=
    3.7.0, Lute's HTML sanitizer does not remove &lt;iframe&gt; elements. Comb= ined with the SiYuan Electron client's permissive security configuration, a=
    n attacker can include a malicious &lt;iframe&gt; in a Bazaar package READM=
    E that executes arbitrary commands on the victim's machine when the package=
    details are viewed. No package installation is required. This vulnerabilit=
    y is fixed in 3.7.0.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54759" target=3D= "_blank" rel=3D"noopener">CVE-2026-54759</a></td>
    </tr>

    <td class=3D"vendor-product">sparklemotion--nokogiri</td>
    <td>Nokogiri is an open source XML and HTML library for the Ruby programmin=
    g language. Prior to 1.19.4, Nokogiri::XML::NodeSet#[] (and its alias #slic=
    e) checked the requested index against the node set's bounds using a 32-bit= -truncated copy of the index. A large negative index could pass the check a=
    nd then be used at full width, reading outside the node set's storage. On C= Ruby this is an out-of-bounds read that typically crashes the process; on J= Ruby it is not memory-unsafe but returns an incorrect node. This vulnerabil= ity is fixed in 1.19.4.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57235" target=3D= "_blank" rel=3D"noopener">CVE-2026-57235</a></td>
    </tr>

    <td class=3D"vendor-product">sparklemotion--nokogiri</td>
    <td>Nokogiri is an open source XML and HTML library for the Ruby programmin=
    g language. Prior to 1.19.4, calling Document#encoding=3D with an invalid e= ncoding (e.g., a non-string, or a string containing a null byte) raises an = exception, but only after freeing the document's current encoding string wi= thout replacing it. The document is left referencing freed memory, so the n= ext call to Document#encoding reads invalid memory, which can cause a segfa= ult or leak freed bytes into a Ruby String. Affects the CRuby (libxml2) imp= lementation only; JRuby is not affected. This vulnerability is fixed in 1.1= 9.4.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57236" target=3D= "_blank" rel=3D"noopener">CVE-2026-57236</a></td>
    </tr>

    <td class=3D"vendor-product">sparklemotion--nokogiri</td>
    <td>Nokogiri is an open source XML and HTML library for the Ruby programmin=
    g language. Prior to 1.19.4, Nokogiri contains a bug when calling certain m= ethods on allocated-but-uninitialized native wrapper classes that inherit f= rom Nokogiri::XML::Node. This caused a NULL pointer dereference that could = crash the process. This vulnerability is fixed in 1.19.4.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57434" target=3D= "_blank" rel=3D"noopener">CVE-2026-57434</a></td>
    </tr>

    <td class=3D"vendor-product">sparklemotion--nokogiri</td>
    <td>Nokogiri is an open source XML and HTML library for the Ruby programmin=
    g language. Prior to 1.19.4, Nokogiri's CRuby native extension could leave =
    a Ruby wrapper pointing to freed memory when replacing the value of an XML = attribute. If Ruby code had already accessed an attribute child node, Nokog= iri::XML::Attr#value=3D could free the underlying native child node while t=
    he wrapper remained reachable through the document node cache. A later use =
    of the freed child node or a Ruby GC mark could dereference an invalid poin= ter, causing an invalid read and a possible segfault. This vulnerability is=
    fixed in 1.19.4.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57435" target=3D= "_blank" rel=3D"noopener">CVE-2026-57435</a></td>
    </tr>

    <td class=3D"vendor-product">sparklemotion--nokogiri</td>
    <td>Nokogiri is an open source XML and HTML library for the Ruby programmin=
    g language. Prior to 1.19.4, Nokogiri::XML::Document#root=3D validated only=
    that the new root was a Nokogiri::XML::Node, allowing a DTD node to be set=
    as the document root. The result is a heap use-after-free during garbage c= ollection or finalization, leading to an invalid memory read or potentially=
    a segfault. This vulnerability is fixed in 1.19.4.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57436" target=3D= "_blank" rel=3D"noopener">CVE-2026-57436</a></td>
    </tr>

    <td class=3D"vendor-product">sparklemotion--nokogiri</td>
    <td>Nokogiri is an open source XML and HTML library for the Ruby programmin=
    g language. Prior to 1.19.4, Nokogiri::XML::XPathContext did not keep its s= ource document alive for garbage collection. If an XPathContext outlived it=
    s document and the document was collected, evaluating an XPath expression c= ould read invalid memory and potentially segfault. This is only reachable w= hen application code constructs an XPathContext directly and lets the docum= ent become unreachable while continuing to use the context. The normal Docu= ment#xpath, #css, and related search methods are not affected, and it is no=
    t triggerable by malicious document input. This vulnerability is fixed in 1= .19.4.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57437" target=3D= "_blank" rel=3D"noopener">CVE-2026-57437</a></td>
    </tr>

    <td class=3D"vendor-product">sparklemotion--nokogiri</td>
    <td>Nokogiri is an open source XML and HTML library for the Ruby programmin=
    g language. Prior to 1.19.4, XInclude substitution performed by Nokogiri::X= ML::Node#do_xinclude replaced each &lt;xi:include&gt; in place, freeing the=
    include node along with its children (such as &lt;xi:fallback&gt; and its = descendants) and any namespaces declared on them. If an application had alr= eady exposed one of those nodes or namespaces to Ruby, the corresponding Ru=
    by object was left pointing at freed memory. Using the object could result =
    in invalid reads or writes to memory. This vulnerability is fixed in 1.19.4= .</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57438" target=3D= "_blank" rel=3D"noopener">CVE-2026-57438</a></td>
    </tr>

    <td class=3D"vendor-product">Technitium --Technitium DNS Server v.14.3</td> <td>An issue in Technitium DNS Server v.14.3 and before allows a remote att= acker to cause a denial of service via the DnsServerApp.exe, DnsServerApp.d= ll, TechnitiumLibrary.Net/Dns/DnsClient.cs components</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-36478" target=3D= "_blank" rel=3D"noopener">CVE-2026-36478</a></td>
    </tr>

    <td class=3D"vendor-product">Tenda--N300 F3</td>
    <td>Cleartext storage and exposure of WPA2 credentials, and missing authent= ication on the rr/wr memory read/write commands, in the unauthenticated UAR=
    T debug console of the Tenda N300 F3 (V603) allow a physically proximate at= tacker to obtain stored WPA2 credentials in cleartext and to read or write = arbitrary memory via the serial console.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-38571" target=3D= "_blank" rel=3D"noopener">CVE-2026-38571</a></td>
    </tr>

    <td class=3D"vendor-product">Thinkst Applied Research--Canarytokens</td>
    <td>An HTML injection vulnerability exists in the Google Chat webhook notif= ication=C2=A0 sent by Thinkst Applied Research Canarytokens, enabling Inter= face Manipulation in Google Chat. An attacker can insert limited HTML conte=
    nt including links. This issue affects Canarytokens: from Docker tag sha-4a= ef1db90 before sha-8ab4dccd, from Git commit 4aef1db90 before 8ab4dccd.</td=

    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12888" target=3D= "_blank" rel=3D"noopener">CVE-2026-12888</a></td>
    </tr>

    <td class=3D"vendor-product">Thinkst Applied Research--Canarytokens</td> <td>Stored Cross-Site Scripting in the exposed AWS API key store of=C2=A0Th= inkst Applied Research Canarytokens. Anonymous exploitation requires knowle= dge of a random identifier. This issue affects Canarytokens: from Docker ta=
    g sha-4116b92cb before sha-f5aa5c4e, from Git commit 4116b92cb before f5aa5= c4e.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-13140" target=3D= "_blank" rel=3D"noopener">CVE-2026-13140</a></td>
    </tr>

    <td class=3D"vendor-product">ToolJet--ToolJet</td>
    <td>ToolJet is the open-source foundation am AI-native platform for buildin=
    g and deploying internal tools, workflows and AI agents. Prior to 3.20.178-= lts, any authenticated user with builder role (free tier) can overwrite a g= lobally-shared marketplace plugin with arbitrary JavaScript that executes s= erver-side with full Node.js access (require, process). The malicious code = runs whenever any user on the instance triggers a query using that plugin -=
    achieving both RCE and supply-chain compromise of the entire ToolJet deplo= yment. This vulnerability is fixed in 3.20.178-lts.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55413" target=3D= "_blank" rel=3D"noopener">CVE-2026-55413</a></td>
    </tr>

    <td class=3D"vendor-product">Totolink--EX1200L</td>
    <td>Totolink=C2=A0EX1200L router is vulnerable to Buffer Overflow in the lo= gin functionality in=C2=A0cgi-bin/cstecgi.cgi endpoint.=C2=A0This vulnerabi= lity could be exploited to cause the program to crash and to execute code r= emotely. This allows the attacker to perform actions as root including read= ing and editing data, as well as bricking the router. Because vendor contac=
    t attempts were unsuccessful, the vulnerability has only been confirmed in = version 9.3.5u.6146_B20201023 but may also affect other versions.</td> <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-44089" target=3D= "_blank" rel=3D"noopener">CVE-2026-44089</a></td>
    </tr>

    <td class=3D"vendor-product">TP-Link Systems Inc.--Archer MR200 v07</td>
    <td>A command injection vulnerability has been identified in the DHCP optio=
    n processing logic in multiple TP-Link router models, due to insufficient v= alidation of externally supplied DHCP option data.=C2=A0An adjacent attacke=
    r may exploit this vulnerability by supplying crafted DHCP responses, poten= tially resulting in unauthorized command execution during device initializa= tion or provisioning workflows. This typically occurs when the device is in=
    a factory-default or unconfigured state. Successful exploitation may allow=
    an adjacent, unauthenticated attacker to execute arbitrary commands with e= levated privileges, potentially leading to full compromise of the affected = device and unauthorized administrative control.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11834" target=3D= "_blank" rel=3D"noopener">CVE-2026-11834</a></td>
    </tr>

    <td class=3D"vendor-product">TP-Link Systems Inc.--Tapo C200 v3</td>
    <td>A denial-of-service (DoS) vulnerability has been identified in Tapo C20=
    0 v3 in the network packet handling logic due to improper handling of IPv4 = fragmented packets.=C2=A0 An unauthenticated adjacent attacker can send cra= fted packets to cause excessive resource consumption, leading to instabilit=
    y of the device.Successful exploitation can remotely trigger a temporary de= nial-of-service condition,=C2=A0causing the camera to become unresponsive a=
    nd resulting in intermittent loss of video monitoring and recording.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12760" target=3D= "_blank" rel=3D"noopener">CVE-2026-12760</a></td>
    </tr>

    <td class=3D"vendor-product">traefik--traefik</td>
    <td>Traefik is an HTTP reverse proxy and load balancer. Prior to 2.11.48, 3= .6.19, and 3.7.3, there is a high severity vulnerability in Traefik's Strip= Prefix middleware that allows an unauthenticated attacker to bypass route-l= evel authentication and authorization. When a public router matches on a Pa= thPrefix rule and applies the StripPrefix middleware, a request path contai= ning .. or its percent-encoded form %2e%2e can match the public route at ro= uting time and then, after the prefix is stripped and the path is normalize=
    d, resolve to a path served by a separate, authenticated router. As a resul=
    t, an attacker can reach protected backend paths - such as admin or interna=
    l configuration endpoints - without satisfying the authentication middlewar=
    e attached to the protected router. This vulnerability is fixed in 2.11.48,=
    3.6.19, and 3.7.3.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48020" target=3D= "_blank" rel=3D"noopener">CVE-2026-48020</a></td>
    </tr>

    <td class=3D"vendor-product">traefik--traefik</td>
    <td>Traefik is an HTTP reverse proxy and load balancer. From 3.7.0 until 3.= 7.3, there is a high severity vulnerability in Traefik's domain-fronting pr= otection (SNICheck) that allows an unauthenticated client to bypass mutual = TLS enforced through wildcard router TLSOptions. When a router uses a wildc= ard host rule such as Host(*.example.com) with stricter TLS options (for ex= ample RequireAndVerifyClientCert), SNICheck resolves the TLS options for th=
    e HTTP Host header using exact map lookups only and never applies wildcard = matching. If another permissive SNI is served on the same entrypoint, an at= tacker can complete the TLS handshake under the permissive options and then=
    send an HTTP Host header targeting the wildcard-protected backend, reachin=
    g it without presenting a client certificate. This affects the regular HTTP=
    S / HTTP-2 path and does not require HTTP/3. This vulnerability is fixed in=
    3.7.3.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-48491" target=3D= "_blank" rel=3D"noopener">CVE-2026-48491</a></td>
    </tr>

    <td class=3D"vendor-product">traefik--traefik</td>
    <td>Traefik is an HTTP reverse proxy and load balancer. Prior to 3.7.3, the=
    re is a critical vulnerability in Traefik's HTTP/3 (QUIC) TLS configuration=
    selection that allows unauthenticated clients to bypass router-specific mT=
    LS enforcement. When HTTP/3 is enabled on an entrypoint, the TLS handshake = selects the applicable TLS configuration through an exact, case-sensitive l= ookup on the SNI value, which fails to match wildcard host patterns (e.g., = *.example.com) or case variants of the configured hostname. Because the han= dshake falls back to the default TLS configuration - which may not require = client certificates - a client can complete the QUIC handshake without pres= enting a certificate, while the subsequent HTTP routing layer still dispatc= hes the request to a backend protected by a router-specific mTLS policy. Th=
    e issue affects deployments where HTTP/3 is enabled, a router uses a wildca=
    rd Host rule or case-insensitive hostname matching, a router-specific TLSOp= tions enforces client certificate authentication, and UDP access to the ent= rypoint is reachable by an attacker. This vulnerability is fixed in 3.7.3.<=

    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53622" target=3D= "_blank" rel=3D"noopener">CVE-2026-53622</a></td>
    </tr>

    <td class=3D"vendor-product">traefik--traefik</td>
    <td>Traefik is an HTTP reverse proxy and load balancer. Prior to 3.6.21 and=
    3.7.5, there is a high severity vulnerability in Traefik's Kubernetes Gate= way provider affecting the crossProviderNamespaces allowlist. For HTTPRoute=
    rules that declare multiple (WRR) backendRefs, Traefik evaluates the allow= list against the target backendRef.namespace instead of the route's own nam= espace. As a result, an HTTPRoute created in a namespace that is not allow-= listed can reference a cross-provider TraefikService such as api@internal, = dashboard@internal or rest@internal by pointing backendRef.namespace at an = allow-listed namespace covered by a Gateway API ReferenceGrant, exposing in= ternal Traefik services on the data plane. Exploitation requires the abilit=
    y to create an accepted HTTPRoute and a matching ReferenceGrant from an all= ow-listed namespace; it does not require any change to Traefik static confi= guration, RBAC, or the deployment itself. This vulnerability is fixed in 3.= 6.21 and 3.7.5.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54761" target=3D= "_blank" rel=3D"noopener">CVE-2026-54761</a></td>
    </tr>

    <td class=3D"vendor-product">traefik--traefik</td>
    <td>Traefik is an HTTP reverse proxy and load balancer. From 3.7.0-ea.1 unt=
    il 3.7.5, there is a medium severity vulnerability in Traefik's Kubernetes = Ingress NGINX provider that causes affected routes to fail open. When an In= gress explicitly enables BasicAuth or DigestAuth through the supported ngin= x.ingress.kubernetes.io/auth-type and auth-secret annotations, but the refe= renced auth Secret cannot be resolved or parsed, Traefik logs the resolutio=
    n error, skips installing the authentication middleware, and still emits a = router to the backend service. A route that operators intended to protect i=
    s therefore published to the data plane without its authentication control,=
    allowing unauthenticated access to the backend. The trigger is an invalid =
    or unresolved auth dependency - a missing, malformed, unreadable, or policy= -denied Secret - rather than an intentionally unprotected route. This vulne= rability is fixed in 3.7.5.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54762" target=3D= "_blank" rel=3D"noopener">CVE-2026-54762</a></td>
    </tr>

    <td class=3D"vendor-product">Trellix--Trellix Network Security NX, EX, FX, = AX, and CMS</td>
    <td>A Code Injection vulnerability existed in Trellix Network Security CM a=
    nd NX. A locally authenticated admin user can execute arbitrary code using = the web interface and Alert artifact details.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-7958" target=3D"= _blank" rel=3D"noopener">CVE-2025-7958</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--AI Share &amp; Summarize</td>
    <td>The AI Share &amp; Summarize WordPress plugin before 2.0.4 does not san= itise and escape some of its shortcode attributes before outputting them in=
    a page, allowing users with the Contributor role and above to perform Stor=
    ed Cross-Site Scripting attacks.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10531" target=3D= "_blank" rel=3D"noopener">CVE-2026-10531</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Cornerstone</td>
    <td>The Cornerstone WordPress plugin before 7.8.9 does not enforce capabili=
    ty checks on one of its REST API routes, allowing any authenticated user to=
    disclose the metadata of any other user, including roles, session token pr= eviews and stored billing/shipping fields. This affects the premium co Corn= erstone page builder distributed bundled with the X , not the unrelated fre=
    e `cornerstone` Cornerstone WordPress plugin before 7.8.9 (v0.8.x) on the .= org repository.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9709" target=3D"= _blank" rel=3D"noopener">CVE-2026-9709</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Cornerstone</td>
    <td>The Cornerstone WordPress plugin before 7.8.8 does not enforce capabili=
    ty checks on one of its CSS-preview request handlers, and exposes the nonce=
    needed to call it to every logged-in user on any wp-admin page, allowing a=
    ny authenticated user to evaluate dynamic content tokens against arbitrary = users and disclose their sensitive metadata including raw password hashes. = This affects the premium co Cornerstone page builder distributed bundled wi=
    th the X , not the unrelated free `cornerstone` Cornerstone WordPress plugi=
    n before 7.8.8 (v0.8.x) on the .org repository.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9710" target=3D"= _blank" rel=3D"noopener">CVE-2026-9710</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Email Address Encoder</td>
    <td>The Email Address Encoder WordPress plugin before 1.0.25, email-encoder= -premium WordPress plugin before 0.3.12 does not properly handle email repl= acement, which could allow unauthenticated users to perform Stored XSS atta= cks</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-5305" target=3D"= _blank" rel=3D"noopener">CVE-2026-5305</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Frontend File Manager Plugin</td>
    <td>The Frontend File Manager Plugin WordPress plugin through 23.6 does not=
    sanitise nor escape a filename submitted to the frontend file-rename endpo= int before storing it as post meta and rendering it back on the admin File = Manager listing, leading to a Stored Cross-Site Scripting vulnerability exp= loitable by users with Subscriber-level access and above against an adminis= trator viewing the file management interface.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8378" target=3D"= _blank" rel=3D"noopener">CVE-2026-8378</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Frontend File Manager Plugin</td>
    <td>The Frontend File Manager Plugin WordPress plugin through 23.6 does not=
    properly enforce its nonce check on the file download handler, allowing un= authenticated attackers to download files uploaded by any user through the = Frontend File Manager Plugin WordPress plugin through 23.6 by iterating ide= ntifiers.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8379" target=3D"= _blank" rel=3D"noopener">CVE-2026-8379</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Frontend File Manager Plugin</td>
    <td>The Frontend File Manager Plugin WordPress plugin through 23.6 does not=
    properly verify ownership of every targeted post before permanent deletion=
    , allowing authenticated users with author-level access and above to perman= ently delete arbitrary posts and pages. When the Frontend File Manager Plug=
    in WordPress plugin through 23.6's "Allow guest uploads" setting is enabled=
    by an administrator, the same deletion primitive becomes reachable by unau= thenticated users.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8380" target=3D"= _blank" rel=3D"noopener">CVE-2026-8380</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Infility Global</td>
    <td>The Infility Global Infility Global WordPress plugin before 2.15.20 for=
    WordPress does not sanitize or validate the orderby and order parameters i=
    n the import_list(), url_detail(), and file_detail() admin page callbacks b= efore using them in SQL queries, allowing authenticated attackers with Edit= or-level access or higher to perform time-based blind SQL injection and ext= ract sensitive data from the database. The ImportData module must be enable=
    d via the Infility Global WordPress plugin before 2.15.20's module toggle p= age.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7842" target=3D"= _blank" rel=3D"noopener">CVE-2026-7842</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Infility Global</td>
    <td>The Infility Global WordPress plugin before 2.15.19 does not properly s= anitize and escape some parameters before using them in SQL statements, lea= ding to a SQL Injection vulnerability exploitable by authenticated users wi=
    th Subscriber-level access and above.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8163" target=3D"= _blank" rel=3D"noopener">CVE-2026-8163</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--InPost PL</td>
    <td>The InPost PL WordPress plugin before 1.9.1 does not verify that the re= quest originates from the legitimate buyer before allowing the WooCommerce = order parcel-locker destination to be updated, allowing unauthenticated att= ackers to silently redirect the shipping destination of any pending or proc= essing order on the site.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9702" target=3D"= _blank" rel=3D"noopener">CVE-2026-9702</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Masteriyo LMS</td>
    <td>The Masteriyo LMS WordPress plugin before 2.2.1 does not perform author= ization checks in a course-progress REST API controller, allowing unauthent= icated users to read and permanently delete any user's course-progress reco= rds.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10824" target=3D= "_blank" rel=3D"noopener">CVE-2026-10824</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Motors</td>
    <td>The Motors WordPress plugin before 1.4.110 does not have proper authori= sation and CSRF checks on one of its AJAX actions, allowing unauthenticated=
    attackers to modify arbitrary post metadata, such as the gallery, featured=
    image and, on WooCommerce sites, product prices.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7859" target=3D"= _blank" rel=3D"noopener">CVE-2026-7859</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Paid Membership Plugin, Ecommerce, Us=
    er Registration Form, Login Form, User Profile &amp; Restrict Content</td> <td>The Paid Membership Plugin, Ecommerce, User Registration Form, Login Fo= rm, User Profile &amp; Restrict Content WordPress plugin before 4.16.17 doe=
    s not verify that the user performing a subscription action owns the target=
    ed subscription, allowing any authenticated user (Subscriber+) to cancel ot= her users' active subscriptions via an Insecure Direct Object Reference.</t=

    <td>2026-06-27</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10820" target=3D= "_blank" rel=3D"noopener">CVE-2026-10820</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Pie Register</td>
    <td>The Pie Register WordPress plugin before 3.8.4.10 does not use sufficie= ntly random values when generating its account verification tokens, allowin=
    g unauthenticated attackers to predict a valid token and activate an accoun=
    t without access to the associated email inbox.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10530" target=3D= "_blank" rel=3D"noopener">CVE-2026-10530</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Post Duplicator</td>
    <td>The Post Duplicator WordPress plugin before 3.0.15 does not safely hand=
    le custom meta-data during post duplication, storing attacker-supplied seri= alized values without the WordPress meta API's double-serialization protect= ion, allowing users with Contributor-level access and above to inject a PHP=
    Object.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10749" target=3D= "_blank" rel=3D"noopener">CVE-2026-10749</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Printcart Web to Print Product Design=
    er for WooCommerce</td>
    <td>The Printcart Web to Print Product Designer for WooCommerce WordPress p= lugin through 2.4.8 is vulnerable to path traversal which makes it possible=
    for the attacker to retrieve the directory listing for arbitrary directori=
    es on the server.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-10268" target=3D= "_blank" rel=3D"noopener">CVE-2025-10268</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--SALESmanago &amp; Leadoo</td>
    <td>The SALESmanago &amp; Leadoo WordPress plugin before 3.11.3 does not pr= operly sanitise and escape a parameter passed to one of its AJAX actions be= fore using it in a SQL statement, and fails to enforce authorisation on tha=
    t action, allowing authenticated users with minimal permissions, such as su= bscribers, to perform SQL injection attacks.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10835" target=3D= "_blank" rel=3D"noopener">CVE-2026-10835</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Shariff for WordPress</td>
    <td>The Shariff for WordPress Shariff for WordPress plugin through 1.0.11 d= oes not sanitize or escape the shariff_infourl setting before outputting it=
    in the frontend HTML via the generateshariff() function, which could allow=
    high privilege users such as admin to perform Stored Cross-Site Scripting = attacks even when the unfiltered_html capability is disallowed (for example=
    in multisite setup).</td>
    <td>2026-06-27</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9677" target=3D"= _blank" rel=3D"noopener">CVE-2026-9677</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Simple Basic Contact Form</td>
    <td>The Simple Basic Contact Form WordPress plugin through 20250114 does no=
    t escape user-supplied input before reflecting it into the contact form out= put on validation errors, leading to a Reflected Cross-Site Scripting vulne= rability that unauthenticated attackers can exploit against site visitors v=
    ia a crafted link or cross-site form submission.</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8172" target=3D"= _blank" rel=3D"noopener">CVE-2026-8172</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Site Kit by Google</td>
    <td>The Site Kit by Google WordPress plugin before 1.176.0 does not properl=
    y restrict a REST API write endpoint to administrators, allowing lower-priv= ileged users who have been granted dashboard sharing access (such as Editor=
    s) to modify a site-wide Site Kit by Google WordPress plugin before 1.176.0=
    setting that should only be modifiable by administrators.</td> <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10753" target=3D= "_blank" rel=3D"noopener">CVE-2026-10753</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--smart-post-show-pro</td>
    <td>Multiple Shapedsmart-post-show-pro WordPress plugin before 4.0.2, Real = Testimonials Pro WordPress plugin before 3.2.5, Product Slider for WooComme= rce Pro WordPress plugin before 3.5.3 Pro smart-post-show-pro WordPress plu= gin before 4.0.2, Real Testimonials Pro WordPress plugin before 3.2.5, Prod= uct Slider for WooCommerce Pro WordPress plugin before 3.5.3 were distribut=
    ed with malicious code through the vendor's compromised update server, allo= wing unauthenticated attackers to deploy a second-stage payload that exfilt= rates credentials and other sensitive data and grants full control of affec= ted sites.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10735" target=3D= "_blank" rel=3D"noopener">CVE-2026-10735</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Transbank Webpay</td>
    <td>The Transbank Webpay WordPress plugin before 1.14.0 does not sanitize a=
    nd escape logs to be displayed, allowing unauthenticated users to perform S= tored XSS attacks against logged in administrator</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6858" target=3D"= _blank" rel=3D"noopener">CVE-2026-6858</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--ultimate-woocommerce-auction-pro</td> <td>The ultimate-woocommerce-auction-pro WordPress plugin through 2.4.5 doe=
    s not sanitise and escape a parameter before outputting it back in the page=
    , leading to a Reflected Cross-Site Scripting which could be used against h= igh privilege users such as admin</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-4110" target=3D"= _blank" rel=3D"noopener">CVE-2026-4110</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--ultimate-woocommerce-auction-pro</td> <td>The ultimate-woocommerce-auction-pro WordPress plugin through 2.4.5 doe=
    s not sanitise and escape a parameter before outputting it back in the page=
    , leading to a Reflected Cross-Site Scripting which could be used against h= igh privilege users such as admin</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-4259" target=3D"= _blank" rel=3D"noopener">CVE-2026-4259</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--Vitepos</td>
    <td>The Vitepos WordPress plugin before 3.4.2 does not properly restrict th=
    e roles that can be assigned when creating new users via one of its REST AP=
    I endpoints, allowing authenticated users with a custom Vitepos WordPress p= lugin before 3.4.2 role to escalate privileges to administrator.</td> <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8157" target=3D"= _blank" rel=3D"noopener">CVE-2026-8157</a></td>
    </tr>

    <td class=3D"vendor-product">Unknown--YMC Filter</td>
    <td>The YMC Filter WordPress plugin before 3.11.3 does not properly authori=
    ze access to one of its REST API endpoints and does not validate a user-sup= plied query parameter, allowing unauthenticated attackers to retrieve the t= itles and content of private, draft, and other non-public posts.</td> <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10823" target=3D= "_blank" rel=3D"noopener">CVE-2026-10823</a></td>
    </tr>

    <td class=3D"vendor-product">Unraid--Unraid</td>
    <td>Unraid Web Server FileUpload Command Injection Remote Code Execution Vu= lnerability. This vulnerability allows remote attackers to execute arbitrar=
    y code on affected installations of Unraid. Authentication is required to e= xploit this vulnerability. The specific flaw exists within FileUpload.php. = The issue results from the lack of proper validation of a user-supplied str= ing before using it to execute a system call. An attacker can leverage this=
    vulnerability to execute code in the context of the www-data user. Was ZDI= -CAN-30116.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9772" target=3D"= _blank" rel=3D"noopener">CVE-2026-9772</a></td>
    </tr>

    <td class=3D"vendor-product">Unraid--Unraid</td>
    <td>Unraid Web Server ToggleState Command Injection Remote Code Execution V= ulnerability. This vulnerability allows remote attackers to execute arbitra=
    ry code on affected installations of Unraid. Authentication is required to = exploit this vulnerability. The specific flaw exists within ToggleState.php=
    . The issue results from the lack of proper validation of a user-supplied s= tring before using it to execute a system call. An attacker can leverage th=
    is vulnerability to execute code in the context of the www-data user. Was Z= DI-CAN-30134.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-9773" target=3D"= _blank" rel=3D"noopener">CVE-2026-9773</a></td>
    </tr>

    <td class=3D"vendor-product">upKeeper Solutions--upKeeper Instant Privilege=
    Access</td>
    <td>Improper output neutralization for logs vulnerability in upKeeper Solut= ions upKeeper Instant Privilege Access on Windows allows Log Injection-Tamp= ering-Forging. This issue affects upKeeper Instant Privilege Access: throug=
    h 1.6.1.</td>
    <td>2026-06-24</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10745" target=3D= "_blank" rel=3D"noopener">CVE-2026-10745</a></td>
    </tr>

    <td class=3D"vendor-product">vim--vim</td>
    <td>Vim is an open source, command line text editor. Prior to 9.2.0653, the=
    tree_count_words() function in src/spellfile.c fills in the word-count fie= lds of a spell-file word trie by walking it iteratively with a depth counte=
    r. The counter is bounded only by the trie structure itself; it is never ch= ecked against the size of the fixed MAXWLEN-element stack arrays it indexes=
    (arridx[], curi[], wordcount[]). A crafted .spl/.sug file pair, loaded whe=
    n the user invokes spell suggestion, can drive the descent arbitrarily deep=
    , so the function writes past the end of those arrays. This is a stack out-= of-bounds write that corrupts the call frame and crashes the editor. This v= ulnerability is fixed in 9.2.0653.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55693" target=3D= "_blank" rel=3D"noopener">CVE-2026-55693</a></td>
    </tr>

    <td class=3D"vendor-product">vim--vim</td>
    <td>Vim is an open source, command line text editor. Prior to 9.2.0663, a V= imscript code injection vulnerability exists in s:NetrwLocalRmFile() in the=
    netrw plugin (runtime/pack/dist/opt/netrw/autoload/netrw.vim) when deletin=
    g a local file from the browser. A filename derived from the buffer's direc= tory listing is interpolated into an Ex command line passed to :execute wit=
    h only the backslash character escaped, allowing a crafted filename contain= ing a bar (|) to terminate the intended command and execute arbitrary Vimsc= ript, including shell commands via :call system() and :!. This vulnerabilit=
    y is fixed in 9.2.0663.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55895" target=3D= "_blank" rel=3D"noopener">CVE-2026-55895</a></td>
    </tr>

    <td class=3D"vendor-product">vim--vim</td>
    <td>Vim is an open source, command line text editor. From 9.2.0320 until 9.= 2.0679, a crafted undo or swap file can store a virtual-text property whose=
    offset and length point outside the line's property data. When Vim restore=
    s or displays such a line it converts the offset into a pointer and reads t=
    he virtual text without bounds checking, causing an out-of-bounds read that=
    can crash Vim or disclose adjacent heap memory. This vulnerability is fixe=
    d in 9.2.0679.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57454" target=3D= "_blank" rel=3D"noopener">CVE-2026-57454</a></td>
    </tr>

    <td class=3D"vendor-product">vim--vim</td>
    <td>Vim is an open source, command line text editor. Prior to 9.2.0698, the=
    single-byte branch of spell_soundfold_sofo() in src/spell.c translates a w= ord through a spell file's SOFO (sound-folding) byte map into a caller-owne=
    d result buffer. Its copy loop advances the output index ri with no upper b= ound and terminates only on the input NUL, writing one byte per input byte = into the MAXWLEN-element stack buffer the caller provides. A word longer th=
    an MAXWLEN, passed to soundfold() (or reached via sound-based spell suggest= ion) while a SOFO-based spell language is active, therefore writes past the=
    end of that buffer. This is a stack out-of-bounds write that corrupts the = call frame and crashes the editor. This vulnerability is fixed in 9.2.0698.= </td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57455" target=3D= "_blank" rel=3D"noopener">CVE-2026-57455</a></td>
    </tr>

    <td class=3D"vendor-product">vim--vim</td>
    <td>Vim is an open source, command line text editor. Prior to 9.2.0699, Vim=
    's Python omni-completion (runtime/autoload/python3complete.vim and the leg= acy pythoncomplete.vim) executes reconstructed function and class definitio=
    ns from the current buffer with exec() as part of populating the completion=
    dictionary. When reconstructing that source, each scope's docstring is ins= erted verbatim between triple quotes with no escaping, so a hostile buffer = can break out of the triple-quoted literal and execute attacker-controlled = Python during omni-completion. This vulnerability is fixed in 9.2.0699.</td=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-57456" target=3D= "_blank" rel=3D"noopener">CVE-2026-57456</a></td>
    </tr>

    <td class=3D"vendor-product">vitejs--launch-editor</td>
    <td>launch-editor allows users to open files with line numbers in editor fr=
    om Node.js. Prior to 2.14.1, the launch-editor NPM package accesses arbitra=
    ry paths including Windows UNC paths. When a UNC path is opened, Windows au= tomatically attempts NTLM authentication to the remote host, causing the us= er's NTLMv2 password hash to be leaked to an attacker-controlled SMB server=
    . This can result in credential compromise through offline hash cracking. T= his vulnerability is fixed in 2.14.1.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53632" target=3D= "_blank" rel=3D"noopener">CVE-2026-53632</a></td>
    </tr>

    <td class=3D"vendor-product">vitejs--vite</td>
    <td>Vite is a frontend tooling framework for JavaScript. Prior to 8.0.16, 7= .3.5, and 6.4.3, the contents of files that are specified by server.fs.deny=
    can be returned to the browser on Windows. Vite's dev server denies direct=
    access to sensitive files through server.fs.deny, including entries such a=
    s .env, .env.*, and *.{crt,pem}. However, on Windows, the deny logic does n=
    ot correctly normalize NTFS ADS path forms before access checks are applied=
    . Because of this, requests such as /.env::$DATA?raw are treated as allowed=
    paths, while Windows resolves them to the original file's default data str= eam. Similar to that, Windows allows accessing a file using a different nam=
    e with the 8.3 short name compatibility feature. Vite did not reject access= ing files via them. This vulnerability is fixed in 8.0.16, 7.3.5, and 6.4.3= .</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53571" target=3D= "_blank" rel=3D"noopener">CVE-2026-53571</a></td>
    </tr>

    <td class=3D"vendor-product">vllm-project--vllm</td>
    <td>vLLM is an inference and serving engine for large language models (LLMs=
    ). From 0.5.5 until 0.23.1rc0, integer truncation of tensor dimensions in v= LLM's GGUF dequantize kernels (csrc/quantization/gguf/gguf_kernel.cu) cause=
    s partial tensor processing. The output tensor is allocated at full size vi=
    a torch::empty (uninitialized memory), but the dequantize CUDA kernel proce= sses only a truncated number of elements. The unfilled portion of the outpu=
    t tensor retains whatever was previously in GPU memory. In multi-tenant inf= erence deployments, this residual GPU memory may contain tensor data from o= ther users' inference requests, constituting information disclosure. This v= ulnerability is fixed in 0.23.1rc0.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-53923" target=3D= "_blank" rel=3D"noopener">CVE-2026-53923</a></td>
    </tr>

    <td class=3D"vendor-product">vllm-project--vllm</td>
    <td>vLLM is an inference and serving engine for large language models (LLMs=
    ). Prior to 0.23.1rc0, ll temperature validation gates use comparison opera= tors (&lt;, &gt;), which silently evaluate to False for NaN and for positiv=
    e Infinity in Python's IEEE 754 float semantics. Both values pass every gua=
    rd and propagate to GPU sampling kernels, where they produce undefined beha= vior or CUDA errors that can crash the inference worker. This vulnerability=
    is fixed in 0.23.1rc0.</td>
    <td>2026-06-22</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-54235" target=3D= "_blank" rel=3D"noopener">CVE-2026-54235</a></td>
    </tr>

    <td class=3D"vendor-product">Wolfram Research Inc.--Cloud</td>
    <td>The default JVM can access files and directories under `/tmp/` includin=
    g the `$TemporaryDirectory` of other users on the same cloud instance (`/tm= p/UserTemporaryFiles/`). The `-init` file for the the JVM initialization ex= ists in the vulnerable directory during the startup of the JVM. An attacker=
    with access to the shared `/tmp/` space can preemptively create or replace=
    `.jar` files or directories (via the `-init` file) that the victim JVM wil=
    l resolve first in its classpath. By strategically placing a malicious vers= ion of a commonly used library (e.g., `commons-io`) in a location that is i= ncluded in the classpath before the legitimate version, an attacker can cau=
    se the JVM to load the malicious class during startup, thereby executing th=
    e attacker's code.</td>
    <td>2026-06-26</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2025-11919" target=3D= "_blank" rel=3D"noopener">CVE-2025-11919</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>wolfSSL's AVX2-optimized ML-KEM implementation (mlkem_cmp_avx2) compare=
    s only 1536 of the 1568 ciphertext bytes during the Fujisaki-Okamoto re-enc= ryption check in ML-KEM-1024 decapsulation. Ciphertexts that differ from th=
    e expected re-encryption solely in bytes 1536-1567 bypass implicit rejectio=
    n and are accepted as valid, breaking IND-CCA2 security. An attacker able t=
    o submit chosen ciphertexts to a decapsulation oracle that uses a static ML= -KEM-1024 key, and to observe whether the genuine shared secret or the impl= icit-rejection secret was produced, can use this as a plaintext-checking or= acle to recover the private key. A proof of concept recovered a full ML-KEM= -1024 private key with approximately 98% success using roughly 350 chosen c= iphertexts. The flaw is a deterministic logic error and does not rely on ti= ming measurements.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10097" target=3D= "_blank" rel=3D"noopener">CVE-2026-10097</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>OCSP CertID serial-number length-confusion in wolfSSL_OCSP_resp_find_st= atus allows a same-issuer SingleResponse whose serial is a prefix of the ta= rget serial to be reported as the revocation status of a different certific= ate. The lookup compared serial-number bytes without first requiring the tw=
    o serial numbers to be of equal length, so a SingleResponse for one certifi= cate (same issuer) whose serial is a prefix of the target's serial would ma= tch, returning the wrong certificate's status. The fix requires the serial = lengths to be equal before comparing the serial bytes.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10098" target=3D= "_blank" rel=3D"noopener">CVE-2026-10098</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>The X25519 x86_64 assembly implementation fails to clear the most signi= ficant bit during the final modular reduction, so the computed result may n=
    ot be fully reduced modulo the field prime 2^255 - 19. This can leave the f= ield element in a non-canonical form, producing an incorrect result from th=
    e scalar multiplication and potentially a wrong shared secret. The final ca= rry-propagation chains in the x64 and AVX2 reduction routines could overflo=
    w into the top bit, and the high limb was not masked afterward, so the 255-= bit field element was left non-canonical.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10512" target=3D= "_blank" rel=3D"noopener">CVE-2026-10512</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Certificates with wildcard DNS SANs (e.g. *.example.com) bypassed CA na= me-constraint checks. A certificate with a wildcard DNS SAN that should be = rejected by the issuing CA's permitted/excluded DNS name constraints could =
    be accepted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-10592" target=3D= "_blank" rel=3D"noopener">CVE-2026-10592</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>X.509 trust-chain bypass in the OpenSSL compatibility certificate verif= ier (wolfSSL_X509_verify_cert()). This affects only builds with --enable-op= ensslextra (OPENSSL_EXTRA) and whose application validates certificates by = calling X509_verify_cert() with caller-supplied untrusted intermediate cert= ificates; for those users it is critical, otherwise the library is unaffect= ed. In particular, native wolfSSL TLS/DTLS usage is not impacted. wolfSSL's=
    X509_verify_cert() temporarily loads each caller-supplied untrusted interm= ediate into the certificate manager but failed to drop them before the trus= ted-store check, so an untrusted intermediate could anchor the path itself.=
    An attacker can present a chain that never reaches a configured trust anch=
    or and have it accepted, resulting in acceptance of an attacker-controlled = certificate. This is certificate verification independent of TLS (e.g. S/MI= ME/CMS, code/firmware signing, JWT/JWS x5c), is not specific to any key typ=
    e or algorithm, and a single untrusted intermediate suffices. The default w= olfSSL TLS handshake (WOLFSSL_VERIFY_PEER) is not affected; only TLS applic= ations doing manual or deferred peer verification through this API are, whi=
    ch also requires --enable-sessioncerts.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11310" target=3D= "_blank" rel=3D"noopener">CVE-2026-11310</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Missing SNI/ALPN binding on stateful (session-ID) resumption, which pre= viously skipped the binding check performed for ticket-based resumption. A = cached session could be resumed under a different SNI/ALPN than originally = negotiated and, where client-authentication policy differs across virtual h= osts, carry the cached peer-authentication state into a context it was not = established for. Resumption now verifies the SNI/ALPN binding for all paths=
    and declines (falling back to a full handshake) on mismatch.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11703" target=3D= "_blank" rel=3D"noopener">CVE-2026-11703</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>X.509 trust-chain bypass (path-depth exhaustion) in the OpenSSL compati= bility certificate verifier (wolfSSL_X509_verify_cert()). This affects only=
    builds with --enable-opensslextra whose application calls X509_verify_cert=
    () with caller-supplied untrusted intermediates; for those users it is crit= ical, otherwise the library is unaffected. Native wolfSSL TLS/DTLS usage is=
    not impacted. X509_verify_cert() returned success based only on the last v= erified link rather than on reaching a trust anchor: when the supplied chai=
    n is deeper than the verifier's maximum path depth (default 100), path buil= ding runs out of depth while still walking untrusted intermediates and the = chain is accepted even though it never reaches a configured trust anchor, a= llowing acceptance of an attacker-controlled certificate. The default TLS h= andshake (WOLFSSL_VERIFY_PEER) is not affected; only applications doing man= ual or deferred verification through this API are.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11999" target=3D= "_blank" rel=3D"noopener">CVE-2026-11999</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Out-of-bounds heap read during SM2/SM3 certificate signature verificati= on. When parsing a certificate with an SM3wSM2 signature, the Subject Key I= dentifier computation reads the trailing 65 bytes of the public key without=
    checking that the key is at least that long. A public key shorter than 65 = bytes results in an out-of-bounds heap read, leading to a potential crash (= denial of service); there is no out-of-bounds write. Note this only affects=
    builds with SM2 support (--enable-sm2 or --enable-all).</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-12340" target=3D= "_blank" rel=3D"noopener">CVE-2026-12340</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Out-of-bounds write in the Renesas TSIP TLS 1.3 transcript buffer. In t= sip_StoreMessage() the capacity check guarding the fixed message bag (MSGBA= G_SIZE) sets an error code but fails to return, so execution falls through =
    to an XMEMCPY that writes past the end of the buffer once the accumulated T=
    LS 1.3 handshake transcript exceeds MSGBAG_SIZE (8 KB), corrupting adjacent=
    heap state and potentially causing a remote denial of service crash. The b=
    ag is sized to hold a normal handshake, so this is reached only by an unusu= ally large but valid certificate chain, or by a malicious or man-in-the-mid= dle server sending an oversized handshake message to a client that does not=
    strictly verify the chain. This only affects builds using the Renesas TSIP=
    TLS port (WOLFSSL_RENESAS_TSIP_TLS) as a TLS 1.3 client on Renesas MCUs wi=
    th TSIP hardware enabled, and is rated High within those builds. All other = configurations are unaffected.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55958" target=3D= "_blank" rel=3D"noopener">CVE-2026-55958</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Un-negotiated Raw Public Key (RFC 7250) accepted in place of an X.509 c= ertificate, bypassing chain validation. A raw public key has no chain, so P= arseCertRelative() accepts it without performing any trust verification; it=
    must therefore only be accepted when RPK was actually negotiated for that = peer. The check now defaults the expected type to X.509 (per RFC 7250/8446)=
    when no type was negotiated, comparing against the received server certifi= cate type on the client and the selected client certificate type on the ser= ver, and rejects any mismatch, including an un-negotiated raw public key, w= ith UNSUPPORTED_CERTIFICATE. Only affects builds with Raw Public Key suppor=
    t (HAVE_RPK) enabled - disabled by default in a standalone build, but inclu= ded in --enable-all.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55960" target=3D= "_blank" rel=3D"noopener">CVE-2026-55960</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>wolfSSL_PKCS7_verify() returning success for a degenerate (certs-only) = PKCS#7 object that contains no signer. Such an object has empty signerInfos=
    , so the underlying signed-data verification succeeds without authenticatin=
    g any content. The compatibility-layer verify path now rejects the object w= hen no signer signature has actually been verified, so a PKCS#7 carrying no=
    valid signature is no longer reported as verified. This is enforced regard= less of the PKCS7_NOVERIFY flag, which only suppresses signer certificate c= hain validation and was never intended to waive the requirement that a sign= ature exist. Only affects OpenSSL compatibility builds that call the PKCS7_= verify() compatibility API on potentially degenerate PKCS#7 bundles.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55961" target=3D= "_blank" rel=3D"noopener">CVE-2026-55961</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>TLS 1.3 post-handshake authentication (PHA) issue where a server could = accept a client's Finished message without the client having sent a Certifi= cate and CertificateVerify. The post-handshake-auth exemption that allows a=
    n empty/absent peer certificate was only intended for the initial handshake=
    , but it was also being applied while a post-handshake CertificateRequest w=
    as still outstanding. The check is now scoped to the initial handshake only=
    : on the server, once a post-handshake CertificateRequest has been sent (ce= rtReqCtx is set), a peer certificate and a valid CertificateVerify are requ= ired again before the Finished is accepted, with empty-certificate handling=
    following the configured verify mode (FAIL_IF_NO_PEER_CERT) just as during=
    first-handshake client authentication. Only affects TLS 1.3 servers built = with post-handshake authentication support (WOLFSSL_POST_HANDSHAKE_AUTH / -= -enable-postauth, included in --enable-all) that enable WOLFSSL_VERIFY_POST= _HANDSHAKE and request a client certificate after the handshake via wolfSSL= _request_certificate(). Clients, and servers that do not use post-handshake=
    authentication, are unaffected.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55962" target=3D= "_blank" rel=3D"noopener">CVE-2026-55962</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Chain intermediate CA:TRUE without keyCertSign accepted as a signing CA=
    . Intermediate CA certificates are required to have the keyCertSign key usa=
    ge when a Key Usage extension is present, but chain-supplied temporary CAs = (WOLFSSL_TEMP_CA) added while building a certificate path were previously e= xempted from this check, so an intermediate asserting CA:TRUE but lacking k= eyCertSign was accepted as a signing CA. The check now applies to chain-sup= plied temporary CAs as well; only operator-loaded root certificates (WOLFSS= L_USER_CA) and self-signed roots remain exempt. Per RFC 5280 an absent Key = Usage extension implies all usages, so the requirement is enforced only whe=
    n the extension is actually present (extKeyUsageSet). Affects the OpenSSL-c= ompatibility certificate-path-building path (X509_verify_cert / X509_STORE,=
    OPENSSL_EXTRA/OPENSSL_ALL), where untrusted chain intermediates are added =
    as temporary CAs; native (non-OpenSSL-compat) certificate verification does=
    not create temporary CAs and is unaffected. Within those builds, the check=
    applies unless ALLOW_INVALID_CERTSIGN is defined.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55964" target=3D= "_blank" rel=3D"noopener">CVE-2026-55964</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>AES-GCM encryption/decryption with extremely large cumulative single me= ssage sizes (&gt;64 GiB) were not properly rejected by the streaming APIs, = allowing counter wrap, keystream reuse, and consequent plaintext recovery.<=

    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-55967" target=3D= "_blank" rel=3D"noopener">CVE-2026-55967</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Partial-chain certificate verification may accept chains that terminate=
    at a peer-supplied, untrusted intermediate certificate rather than a trust=
    ed anchor. An attacker could present a chain that ends at an intermediate t= hey control and have it accepted as valid. This affects the OpenSSL compati= bility certificate-path-building path (wolfSSL_X509_verify_cert / X509_STOR=
    E, OPENSSL_EXTRA) when the X509_V_FLAG_PARTIAL_CHAIN verify flag is enabled= .</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6091" target=3D"= _blank" rel=3D"noopener">CVE-2026-6091</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>When HAVE_ENCRYPT_THEN_MAC is configured, the implementation could fall=
    back to MAC-then-Encrypt rather than enforcing Encrypt-then-MAC.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6092" target=3D"= _blank" rel=3D"noopener">CVE-2026-6092</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Heap buffer overread in wc_PKCS7_DecodeEnvelopedData when parsing craft=
    ed PKCS7 EnvelopedData. This could theoretically be triggered by attacker-s= upplied data delivered via S/MIME or CMS.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6094" target=3D"= _blank" rel=3D"noopener">CVE-2026-6094</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Bleichenbacher padding oracle in PKCS#7 KTRI decryption. When decryptin=
    g PKCS#7 EnvelopedData using RSA PKCS#1 v1.5 key transport, wolfSSL returne=
    d distinguishable error codes depending on whether RSA padding validation f= ailed versus whether the decrypted content was malformed. An attacker able =
    to submit crafted EnvelopedData messages and observe error responses could = use this as a padding oracle to incrementally recover the encrypted Content=
    Encryption Key (CEK). The fix generates a deterministic pseudo-random fake=
    CEK on padding failure (via HMAC-SHA256) and proceeds with decryption iden= tically, using constant-time operations throughout, so that all failure pat=
    hs produce the same error regardless of padding validity.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6291" target=3D"= _blank" rel=3D"noopener">CVE-2026-6291</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Out-of-bounds write in SetSuitesHashSigAlgo when processing an oversize=
    d signature algorithms list, allowing a write past the bounds of the destin= ation buffer.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6325" target=3D"= _blank" rel=3D"noopener">CVE-2026-6325</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>PKCS#12 MAC verification uses an attacker-controlled comparison length,=
    weakening the integrity check on the MAC and allowing a mismatched MAC to =
    be accepted. The PKCS#12 verify path compared the locally computed HMAC aga= inst the MAC parsed from the PKCS#12 structure using a length taken directl=
    y from the attacker-supplied input, without first verifying that it equals = the length of the digest actually produced by the configured algorithm. A t= runcated or zero-length stored MAC could therefore be accepted, defeating t=
    he integrity protection of the MAC.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6329" target=3D"= _blank" rel=3D"noopener">CVE-2026-6329</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>The ML-KEM ARM64 NEON ciphertext comparison only compares half of the i= nput, breaking the Fujisaki-Okamoto transform's implicit rejection and weak= ening IND-CCA2 security on that code path. The constant-time comparison eff= ectively ignored part of the re-encrypted ciphertext, so a decapsulating pa= rty could fail to detect a manipulated ciphertext and proceed without the s= tandard's required implicit rejection.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6330" target=3D"= _blank" rel=3D"noopener">CVE-2026-6330</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>HMAC zero-length tag forgery in EVP_DigestVerifyFinal, where a zero-len= gth tag could be accepted as valid during HMAC verification. In the OpenSSL= -compatibility HMAC verify path the supplied signature length was only chec= ked as not exceeding the MAC length, so a zero-length or otherwise truncate=
    d tag could pass verification. The fix requires the supplied tag length to = exactly equal the MAC length and rejects a zero-length MAC, so a forged sho=
    rt or empty tag is no longer accepted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6331" target=3D"= _blank" rel=3D"noopener">CVE-2026-6331</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Certificate policy and RFC 8446 compliance concerns regarding the conti= nued acceptance of SHA-1/MD5 in certificate processing.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6412" target=3D"= _blank" rel=3D"noopener">CVE-2026-6412</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>A CRL critical extension bypass exists in ParseCRL_Extensions where cri= tical extensions are not properly enforced, allowing a crafted CRL with an = unhandled critical extension to be accepted. This only affects builds with = CRL support enabled and where a crafted CRL had a trusted signature when pa= rsed.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6450" target=3D"= _blank" rel=3D"noopener">CVE-2026-6450</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Integer underflow in wc_PKCS7_DecryptOri when handling crafted Other Re= cipient Info, leading to incorrect length handling during decryption.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6678" target=3D"= _blank" rel=3D"noopener">CVE-2026-6678</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>A heap buffer overflow could occur in the DTLS 1.3 ACK serialization pa=
    th before the connecting peer is authenticated. The buffer overflow was due=
    to an integer truncation when computing the length of the ACK record-numbe=
    r list, causing an undersized buffer to be allocated and then overrun. This=
    affects builds using DTLS 1.3 and wolfSSL version 5.9.0 and earlier. A fix=
    was added to the 5.9.1 release.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6679" target=3D"= _blank" rel=3D"noopener">CVE-2026-6679</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>The PKCS#7 decode path ignores the caller-supplied output buffer size (= outputSz), allowing decoded content to be written past the bounds of the pr= ovided buffer. This affects wolfSSL 5.9.0 and earlier and was fixed in the = 5.9.1 release.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6681" target=3D"= _blank" rel=3D"noopener">CVE-2026-6681</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>X.509 name constraint bypass via the Subject Common Name when treated a=
    s a DNS-type name. A certificate whose Subject CN violates an issuing CA's = DNS name constraints could be accepted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-6731" target=3D"= _blank" rel=3D"noopener">CVE-2026-6731</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>PKCS7_verify signer confusion allows forged signatures, where the signe=
    r associated with a signature is not correctly bound, permitting a forged s= ignature to be accepted.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7511" target=3D"= _blank" rel=3D"noopener">CVE-2026-7511</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>Use-after-free in PQC hybrid key-share handling. This is an incomplete-= fix follow-up to CVE-2026-5460 (released in 5.9.1): a malicious TLS 1.3 ser= ver sending a truncated PQC hybrid KeyShare can still trigger the error cle= anup path to operate on freed memory.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7531" target=3D"= _blank" rel=3D"noopener">CVE-2026-7531</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>iPAddress name constraints bypass when WOLFSSL_IP_ALT_NAME is not defin= ed. IP address name constraints are not enforced in that configuration, all= owing a certificate to bypass an issuing CA's IP address constraints.</td> <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-7532" target=3D"= _blank" rel=3D"noopener">CVE-2026-7532</a></td>
    </tr>

    <td class=3D"vendor-product">wolfSSL--wolfSSL</td>
    <td>wc_Blake2bHmacFinal and wc_Blake2sHmacFinal discard the message when th=
    e key length exceeds the block size, producing a MAC that is independent of=
    the input. When the supplied key is longer than the BLAKE2 block size the = key-hashing branch reinitialized the running hash state, discarding the acc= umulated message data, so the resulting MAC depended only on the key and no=
    t on the message being authenticated. This bug is specific to the HMAC-BLAK=
    E2 APIs that were added in wolfSSL version 5.9.0.</td>
    <td>2026-06-25</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-8720" target=3D"= _blank" rel=3D"noopener">CVE-2026-8720</a></td>
    </tr>

    <td class=3D"vendor-product">Yokogawa Electric Corporation--FAST/TOOLS</td> <td>Overview: A vulnerability has been found in FAST/TOOLS and CI Server. T=
    he web server may return a response containing the CI Server setting inform= ation. This information could be exploited by an attacker for other attacks=
    . The affected products and versions are as follows: FAST/TOOLS (Packages: = RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB) R9.01 to R10.04 CI Server=C2=A0(All = packages)=C2=A0R1.01 to R1.04</td>
    <td>2026-06-23</td>
    <td>not yet calculated</td>
    <td><a href=3D"https://www.cve.org/CVERecord?id=3DCVE-2026-11833" target=3D= "_blank" rel=3D"noopener">CVE-2026-11833</a></td>
    </tr>
    </tbody>
    </table>
    <p><a href=3D"#top">Back to top</a></p>
    </div>
    </div>
    </div>
    <style>body {
    font-size: 1em; font-family: Arial, Verdana, sans-serif; font-weight: norma=
    l; font-style: normal; color: #333333;
    }
    </style>
    =20


    <div id=3D"mail_footer">
    <p style=3D"text-align: center;"><span style=3D"font-size: 10.0pt; colo=
    r: #757575;">Having trouble viewing this message?=C2=A0</span><a href=3D"ht= tps://content.govdelivery.com/accounts/USDHSCISA/bulletins/41e3aa5" target= =3D"_blank" rel=3D"noopener">View it as a webpage</a>.=C2=A0<a href=3D"http= s://content.govdelivery.com/accounts/USDHS/bulletins/292141e" target=3D"_bl= ank" rel=3D"noopener"></a><span style=3D"font-size: 10.0pt; color: #757575;= "></span></p>
    <p style=3D"text-align: center;"><span style=3D"font-size: 10.0pt; color: #= 757575;">You are subscribed to updates from the </span><a href=3D"https://w= ww.cisa.gov"><span style=3D"font-size: 10.0pt;">Cybersecurity and Infrastru= cture Security Agency</span></a><span style=3D"font-size: 10.0pt; color: #7= 57575;"> (CISA)<br></span><a href=3D"https://public.govdelivery.com/account= s/USDHSCISA/subscriber/edit?preferences=3Dtrue#tab1" target=3D"_blank" rel= =3D"noopener"><span style=3D"font-size: 10.0pt; color: #00568c;">Manage Sub= scriptions</span></a>=C2=A0=C2=A0<span style=3D"font-size: 10.0pt; color: #= 757575;">|=C2=A0=C2=A0</span><a href=3D"https://www.cisa.gov/privacy-policy=
    " target=3D"_blank" rel=3D"noopener"><span style=3D"font-size: 10.0pt; colo=
    r: #00568c;">Privacy Policy</span></a><span style=3D"font-size: 10.0pt; col= or: #757575;">=C2=A0=C2=A0|=C2=A0 <a href=3D"https://subscriberhelp.granicu= s.com/s/article/Subscriber-Help-Center" target=3D"_blank" rel=3D"noopener">= Help</a><a href=3D"https://insights.govdelivery.com/Communications/Subscrib= er_Help_Center" target=3D"_blank" rel=3D"noopener"></a></span><span style= =3D"font-size: 10.0pt; color: #757575;"></span></p>
    <p style=3D"text-align: center;"><span style=3D"font-size: 10.0pt; color: #= 757575;">Connect with CISA: <br></span><a href=3D"https://www.facebook.com/= CISA" target=3D"_blank" rel=3D"noopener"><span style=3D"font-size: 10.0pt; = color: #00568c;">Facebook</span></a><span style=3D"font-size: 10.0pt; color=
    : #757575;">=C2=A0 |=C2=A0 </span><a href=3D"https://twitter.com/CISAgov" t= arget=3D"_blank" rel=3D"noopener"><span style=3D"font-size: 10.0pt; color: = #00568c;">Twitter</span></a><span style=3D"font-size: 10.0pt; color: #75757= 5;">=C2=A0 |=C2=A0 </span><a href=3D"https://Instagram.com/cisagov" target= =3D"_blank" rel=3D"noopener"><span style=3D"font-size: 10.0pt; color: #0056= 8c;">Instagram</span></a><span style=3D"font-size: 10.0pt; color: #757575;"= >=C2=A0 |=C2=A0 </span><a href=3D"https://www.linkedin.com/company/cybersec= urity-and-infrastructure-security-agency" target=3D"_blank" rel=3D"noopener= "><span style=3D"font-size: 10.0pt; color: #00568c;">LinkedIn</span></a><sp=
    an style=3D"font-size: 10.0pt; color: #757575;">=C2=A0 |=C2=A0=C2=A0 </span= ><a href=3D"https://www.youtube.com/channel/UCxyq9roe-npgzrVwbpoAy0A" targe= t=3D"_self"><span style=3D"font-size: 10.0pt; color: #00568c;">YouTube</spa= n></a><span style=3D"font-size: 10.0pt; color: #757575;"></span></p>

    </div>
    <div id=3D"tagline">
    <hr>
    <table style=3D"width: 100%;" border=3D"0" cellspacing=3D"0" cellpadding=3D=

    <tbody>

    <td style=3D"color: #757575; font-size: 10px; font-family: Arial;" width=3D= "89%">This email was sent to cisa@toolazy.synchro.net using GovDelivery Com= munications Cloud, on behalf of: Cybersecurity and Infrastructure Security = Agency =C2=B7 707 17th St, Suite 4000 =C2=B7 Denver, CO 80202</td>
    <td align=3D"right" width=3D"11%"><a href=3D"https://subscriberhelp.granicu= s.com/" target=3D"_blank" rel=3D"noopener"><img src=3D"https://content.govd= elivery.com/images/govd-logo-dark.png" border=3D"0" alt=3D"GovDelivery logo=
    " width=3D"115"></a></td>
    </tr>
    </tbody>
    </table>
    <style type=3D"text/css">body .abe-column-block { min-height: 5px; } table.= gd_combo_table img {margin-left:10px; margin-right:10px;} table.gd_combo_ta= ble div.govd_image_display img, table.gd_combo_table td.gd_combo_image_cell=
    img {margin-left:0px; margin-right:0px;}</style>

    </div>
    </td>
    </tr>
    </table>

    <img alt=3D"" src=3D"https://links-2.govdelivery.com/CI0/0101019f14a64bd7-8= f3f9c96-82da-4c15-b01d-649c21ae471b-000000/N4EAobGNWKvtORwxo-IHJaGBqcxbACAH= zbeL0yL7Gu0=3D452" style=3D"display: none; width: 1px; height: 1px;">
    </body>
    </html>

    --===============4830605103477052940==--

    --===============4218377396049682665==--