# frontend security

Frontend security is the practice of protecting web frontends against attacks through browser security features, HTTP security mechanisms, cookies, and security headers.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Borrowed UI: Why Your Next Desktop Tool Might Just Need a Browser Tab

DevFeed: [Borrowed UI: Why Your Next Desktop Tool Might Just Need a Browser Tab](<https://devfeed.tech/articles/borrowed-ui-why-your-next-desktop-tool-might-just-need-a-browser-tab-146211.md>)

Original publisher: [Read original article](<https://hackernoon.com/borrowed-ui-why-your-next-desktop-tool-might-just-need-a-browser-tab?source=rss>)

Author: Shreyam Adhikari

Published: 2026-11-20T07:00:02Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [browser](<https://devfeed.tech/topics/browser.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Jupyter Notebook](<https://devfeed.tech/topics/jupyter-notebook.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [application-design](<https://devfeed.tech/tags/application-design.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [assets](<https://devfeed.tech/tags/assets.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [background](<https://devfeed.tech/tags/background.md>), [better](<https://devfeed.tech/tags/better.md>), [bind](<https://devfeed.tech/tags/bind.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [browser](<https://devfeed.tech/tags/browser.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [desktop-apps](<https://devfeed.tech/tags/desktop-apps.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [jupyter](<https://devfeed.tech/tags/jupyter.md>), [jupyter-notebook](<https://devfeed.tech/tags/jupyter-notebook.md>), [local](<https://devfeed.tech/tags/local.md>), [local-web-applications](<https://devfeed.tech/tags/local-web-applications.md>), [pprof](<https://devfeed.tech/tags/pprof.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [syncthing](<https://devfeed.tech/tags/syncthing.md>), [tool](<https://devfeed.tech/tags/tool.md>), [ui](<https://devfeed.tech/tags/ui.md>), [user-interface](<https://devfeed.tech/tags/user-interface.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

Borrowed UI (BUI) uses a local process for the work and a browser tab for occasional controls or visualization. The excerpt contrasts pprof's optional local profiling interface (which may need Graphviz), Syncthing's GUI for inspecting and configuring a background service, and Jupyter's notebook interface, where kernels can continue running after a tab closes. It may suit tools that already work as a CLI or service and need tables, charts, or configuration; it avoids bundling a browser engine but does not remove browser resource use. Trade-offs include compatibility, port conflicts, startup and reconnection work, and the difference between closing a tab and stopping a process. Security requires deliberate protections: loopback binding by default, Host and Origin validation, and safeguards for state-changing requests; Syncthing calls for authentication and HTTPS when its GUI is exposed beyond the local machine. Native windows may fit better when native menus, global shortcuts, file associations, or controlled window lifecycle matter.

### Source excerpt

Local tools can borrow the browser for their interface. Explore pprof, Syncthing and Jupyter, plus the trade-offs and security boundaries.

## MetaScanner: An Empirical Study and Proactive Defense against Deceptive UI Attacks in Social VR

DevFeed: [MetaScanner: An Empirical Study and Proactive Defense against Deceptive UI Attacks in Social VR](<https://devfeed.tech/articles/metascanner-an-empirical-study-and-proactive-defense-against-deceptive-ui-attacks-in-social-vr-146040.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.25608>)

Author: Junhee Lee, Seungwon Woo, Minseok Kim, Jongseop Kim, Kiyoung Kim, Hwanjo Heo, Jinwoo Kim

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [VRChat](<https://devfeed.tech/topics/vrchat.md>), [Virtual reality](<https://devfeed.tech/topics/virtual-reality.md>), [vulnerability management](<https://devfeed.tech/topics/vulnerability-management.md>), [human computer interaction](<https://devfeed.tech/topics/human-computer-interaction.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [adversarial](<https://devfeed.tech/tags/adversarial.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [assets](<https://devfeed.tech/tags/assets.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [awareness](<https://devfeed.tech/tags/awareness.md>), [behaviors](<https://devfeed.tech/tags/behaviors.md>), [content](<https://devfeed.tech/tags/content.md>), [content-creators](<https://devfeed.tech/tags/content-creators.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-hc](<https://devfeed.tech/tags/cs-hc.md>), [defense](<https://devfeed.tech/tags/defense.md>), [effectiveness](<https://devfeed.tech/tags/effectiveness.md>), [efficiently](<https://devfeed.tech/tags/efficiently.md>), [elements](<https://devfeed.tech/tags/elements.md>), [proactive](<https://devfeed.tech/tags/proactive.md>), [social](<https://devfeed.tech/tags/social.md>), [social-vr](<https://devfeed.tech/tags/social-vr.md>), [study](<https://devfeed.tech/tags/study.md>), [ui](<https://devfeed.tech/tags/ui.md>), [vr](<https://devfeed.tech/tags/vr.md>)

### AI overview

The paper introduces four deceptive UI attacks that use seemingly benign scripts and interactive elements in virtual worlds to manipulate social VR users into unintended actions. The authors implemented the attacks on VRChat, and an IRB-approved study with 30 participants confirmed their effectiveness. Their proposed MetaScanner scans world assets, including scripts and interactive objects, for suspicious or deceptive elements before users encounter them. It detected all four attack scenarios in test worlds and averaged 5 seconds per scan across 38 real-world assets.

### Source excerpt

arXiv:2611.25608v1 Announce Type: new Abstract: Social virtual reality (VR) platforms have surged in popularity but continue to face significant security challenges, including privacy invasion and user manipulation. Yet, the security risks posed by deceptive content remain largely unexplored. In this paper, we introduce four novel deceptive UI attacks that covertly manipulate social VR users into performing unintended actions without their awareness. We show how adversarial content creators can embed seemingly benign scripts and interactive elements within carefully designed virtual worlds, deceiving users into unknowingly carrying out harmful behaviors. We implemented these attacks on VRChat, a leading social VR platform, and an IRB-approved user study involving 30 participants confirmed their effectiveness. To mitigate these threats, we propose MetaScanner, a proactive analysis system that efficiently scans virtual world assets, including scripts and interactive objects, to identify suspicious or deceptive elements before users are exposed to them. We demonstrate that MetaScanner can successfully detect all threats in test worlds where the four attack scenarios were implemented. Additionally, MetaScanner shows its lightweight nature, with an average scanning time of 5 seconds across 38 real-world assets.

## Achieving the impossible: XSS in innerHTML without equals

DevFeed: [Achieving the impossible: XSS in innerHTML without equals](<https://devfeed.tech/articles/achieving-the-impossible-xss-in-innerhtml-without-equals-141058.md>)

Original publisher: [Read original article](<https://portswigger.net/research/achieving-the-impossible-xss-in-innerhtml-without-equals>)

Author: Gareth Heyes

Published: 2026-11-18T14:39:45Z

Content type: article

Language: en

Sources: [PortSwigger Research](<https://devfeed.tech/sources/portswigger-research.md>)

Topics: [XSS](<https://devfeed.tech/topics/xss.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [HTML](<https://devfeed.tech/topics/html.md>)

Tags: [html](<https://devfeed.tech/tags/html.md>), [research](<https://devfeed.tech/tags/research.md>), [web-security](<https://devfeed.tech/tags/web-security.md>), [xss](<https://devfeed.tech/tags/xss.md>)

### AI overview

The `<selectedcontent>` element clones the selected `<option>`'s child nodes, and that cloning can execute a script that did not run in its original location. Combining it with an SVG `<script>` inserted through `innerHTML` solved the "innerHTML context but no equals allowed" challenge: the SVG namespace and cloning are both required. The same element also enabled vectors without whitespace, `/`, or `=`, with SVG markup allowing legitimate page content to follow. Browser behavior differs: the `innerHTML` vector no longer works in Chrome after a change that marks SVG scripts as already started, but the article reports it still works in Safari 27.2. A related no-whitespace, no-slash, no-equals vector is reported working in Chrome 157 and Safari.

### Source excerpt

Introduction I'm delighted to introduce Masato Kinugawa as a guest web security researcher on the PortSwigger research channel. Masato is a well known web security expert who has found countless high

## Attackers Used Optimizely to A/B Test Malware on Top Websites

DevFeed: [Attackers Used Optimizely to A/B Test Malware on Top Websites](<https://devfeed.tech/articles/attackers-used-optimizely-to-a-b-test-malware-on-top-websites-139521.md>)

Original publisher: [Read original article](<https://krebsonsecurity.com/2026/11/attackers-used-optimizely-to-a-b-test-malware-on-top-websites/>)

Author: BrianKrebs

Published: 2026-11-18T02:52:04Z

Content type: news

Language: en

Sources: [Krebs on Security](<https://devfeed.tech/sources/krebs-on-security.md>)

Topics: [Malware](<https://devfeed.tech/topics/malware.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [XSS](<https://devfeed.tech/topics/xss.md>)

Tags: [a-b-testing](<https://devfeed.tech/tags/a-b-testing.md>), [a-little-sunshine](<https://devfeed.tech/tags/a-little-sunshine.md>), [bbc](<https://devfeed.tech/tags/bbc.md>), [cnn](<https://devfeed.tech/tags/cnn.md>), [content-security-policy](<https://devfeed.tech/tags/content-security-policy.md>), [coruna](<https://devfeed.tech/tags/coruna.md>), [crawler-ninja](<https://devfeed.tech/tags/crawler-ninja.md>), [darksword](<https://devfeed.tech/tags/darksword.md>), [data-breaches](<https://devfeed.tech/tags/data-breaches.md>), [decryptads](<https://devfeed.tech/tags/decryptads.md>), [infoblox](<https://devfeed.tech/tags/infoblox.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [malware](<https://devfeed.tech/tags/malware.md>), [optimizely](<https://devfeed.tech/tags/optimizely.md>), [report-uri](<https://devfeed.tech/tags/report-uri.md>), [scott-helme](<https://devfeed.tech/tags/scott-helme.md>), [security](<https://devfeed.tech/tags/security.md>), [security-tools](<https://devfeed.tech/tags/security-tools.md>), [third-party](<https://devfeed.tech/tags/third-party.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [web-fraud-2-0](<https://devfeed.tech/tags/web-fraud-2-0.md>), [websites](<https://devfeed.tech/tags/websites.md>), [zach-edwards](<https://devfeed.tech/tags/zach-edwards.md>)

### AI overview

On November 16, 2026, an attacker exploited a vulnerability in Optimizely Experimentation to inject malicious JavaScript into projects serving at least 178 organizations. The payload was rebuilt 26 times and could steal payment card data, cookies, and screenshots, replace cryptocurrency payment addresses, and target older Apple devices with exploit kits. Because Optimizely scripts often run immediately on page load, visitors did not need to click or consent for the code to execute. Report URI found that 68 affected sites had no content security policy (CSP), 50 had policies that still allowed the payload, and only 24 fully blocked it. Optimizely said it contained and remediated the vulnerability, removed injected code, revoked tokens, reset account access, and added protections while investigating with experts. The excerpt presents effective CSPs as a way to restrict third-party content, while noting deployment can be difficult and many sites lack or weaken these policies. It also mentions script blockers and modern ad blockers as user-side options, with script blocking requiring users to manage many requests.

### Source excerpt

At least 178 top web destinations unwittingly served a variety of malware exploits against visitors over the past 24 hours thanks to a security vulnerability involving Optimizely, a company that helps websites customize user experiences and test out new features. Experts say the incident, which saw data-stealing malicious software silently injected into sites like the BBC, CNN, Equifax, Ledger and Zoom, was exacerbated by the reality that few popular websites enforce strict rules on the sources of third-party content.

## Optimizely confirms massive cyberattack on customer websites injected stealer malware

DevFeed: [Optimizely confirms massive cyberattack on customer websites injected stealer malware](<https://devfeed.tech/articles/optimizely-confirms-massive-cyberattack-on-customer-websites-injected-stealer-malware-139496.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4249975/optimizely-confirms-massive-cyberattack-on-customer-websites-injected-stealer-malware-3.html>)

Author: Evan Schuman

Published: 2026-11-18T01:39:49Z

Content type: news

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [XSS](<https://devfeed.tech/topics/xss.md>), [Malware](<https://devfeed.tech/topics/malware.md>), [Security](<https://devfeed.tech/topics/security.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-platform](<https://devfeed.tech/tags/ai-platform.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [china](<https://devfeed.tech/tags/china.md>), [code](<https://devfeed.tech/tags/code.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [coruna](<https://devfeed.tech/tags/coruna.md>), [cryptocurrency](<https://devfeed.tech/tags/cryptocurrency.md>), [customers](<https://devfeed.tech/tags/customers.md>), [cyberattack](<https://devfeed.tech/tags/cyberattack.md>), [cyberattacks](<https://devfeed.tech/tags/cyberattacks.md>), [cyberattacks-cybercrime-identity-and-access-management-internet-security-network-security-secur](<https://devfeed.tech/tags/cyberattacks-cybercrime-identity-and-access-management-internet-security-network-security-secur.md>), [cybercrime](<https://devfeed.tech/tags/cybercrime.md>), [darksword](<https://devfeed.tech/tags/darksword.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [development](<https://devfeed.tech/tags/development.md>), [eagle](<https://devfeed.tech/tags/eagle.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [email](<https://devfeed.tech/tags/email.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [internet-security](<https://devfeed.tech/tags/internet-security.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [malware](<https://devfeed.tech/tags/malware.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [optimizely](<https://devfeed.tech/tags/optimizely.md>), [security](<https://devfeed.tech/tags/security.md>), [stealer](<https://devfeed.tech/tags/stealer.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [websites](<https://devfeed.tech/tags/websites.md>)

### AI overview

An authentication flaw in Optimizely's Experimentation account signup flow reportedly let attackers impersonate users, add malicious JavaScript to customer projects, and distribute it through trusted Optimizely CDN snippets. Researcher Scott Helme confirmed the same infection on 178 sites and said there could be more. The code stole payment card details entered in sites' own form fields, cryptocurrency wallet addresses, cookies and screenshots, and delivered iOS exploit kits; the report says hosted payment iframes such as Stripe and Adyen were out of its reach. Optimizely said it blocked the vulnerable path, revoked sessions and tokens, removed injected code, and blocked delivery through Cloudflare. An analyst questioned its confident claims that the platform was fully secured, citing a discrepancy between the vendor's and researcher's first-observed attack times. The excerpt also reports the analyst's concern that allowing "unsafe-eval" could let backup code run despite other policy blocks, and quotes recommendations to restrict script-src and connect-src and drop unsafe-eval where possible, starting in report-only mode.

### Source excerpt

Attackers apparently from China used an authentication security hole within the popular Optimizely AI platform for marketers to steal from at least 178 sites owned by some of the planet's largest companies. Named victims featured vendors including Zoom, Paychex, Equifax, and GitLab, and end-user enterprises including Starbucks, IKEA, Mattel, American Eagle, Air France, Mutual of Omaha, Heineken, Home Chef, Cinnabon, American Eagle, Levi, Costco and HSBC. Salesforce issued a statement confirming that it had also been impacted by the attack. "Salesforce is investigating unauthorized modifications to scripts provided by Optimizely and used on certain Salesforce websites," it wrote in an email statement. "As a precaution, Salesforce is confirming that Optimizely scripts are disabled across preview and production instances." The attacks were discovered by UK-based security researcher Scott Helme, the founder of Report URI, who said in an interview that his team had confirmed 178 victims, but that there could be more. "That's the number that we directly observed and that all carried the same infection," he said. Helme published a report about the attacks on Monday, in which he described an attack methodology where an Optimizely capability in its Web Experimentation product facilitating adding members to a site's development team was leveraged to insert malware into the sites. "The malware was a multi-purpose kit. It swapped cryptocurrency wallet addresses for the attacker's, skimmed payment cards, stole cookies and screenshots, and on iPhones and iPads it delivered the Coruna and DarkSword iOS exploit kits," Helme wrote. "The important lesson here is that trusted JavaScript doesn't always remain trustworthy. A website can be compromised through a third-party dependency without its own code or infrastructure ever being breached." Optimizely customers load a JavaScript "snippet" from Optimizely's CDN onto their sites which contains Optimizely code, the customer's A/B tests,

## Optimizely confirms massive cyberattack on customer websites injected stealer malware

DevFeed: [Optimizely confirms massive cyberattack on customer websites injected stealer malware](<https://devfeed.tech/articles/optimizely-confirms-massive-cyberattack-on-customer-websites-injected-stealer-malware-139524.md>)

Original publisher: [Read original article](<https://www.computerworld.com/article/4249960/optimizely-confirms-massive-cyberattack-on-customer-websites-injected-stealer-malware-2.html>)

Author: Evan Schuman

Published: 2026-11-18T01:39:40Z

Content type: news

Language: en

Sources: [Computerworld](<https://devfeed.tech/sources/computerworld.md>)

Topics: [XSS](<https://devfeed.tech/topics/xss.md>), [Malware](<https://devfeed.tech/topics/malware.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-platform](<https://devfeed.tech/tags/ai-platform.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [china](<https://devfeed.tech/tags/china.md>), [code](<https://devfeed.tech/tags/code.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [coruna](<https://devfeed.tech/tags/coruna.md>), [cryptocurrency](<https://devfeed.tech/tags/cryptocurrency.md>), [customers](<https://devfeed.tech/tags/customers.md>), [cyberattack](<https://devfeed.tech/tags/cyberattack.md>), [cyberattacks](<https://devfeed.tech/tags/cyberattacks.md>), [cyberattacks-cybercrime-internet-security-network-security-security](<https://devfeed.tech/tags/cyberattacks-cybercrime-internet-security-network-security-security.md>), [cybercrime](<https://devfeed.tech/tags/cybercrime.md>), [darksword](<https://devfeed.tech/tags/darksword.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [development](<https://devfeed.tech/tags/development.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [email](<https://devfeed.tech/tags/email.md>), [end-user](<https://devfeed.tech/tags/end-user.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [internet-security](<https://devfeed.tech/tags/internet-security.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [malware](<https://devfeed.tech/tags/malware.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [optimizely](<https://devfeed.tech/tags/optimizely.md>), [security](<https://devfeed.tech/tags/security.md>), [stealer](<https://devfeed.tech/tags/stealer.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [websites](<https://devfeed.tech/tags/websites.md>)

### AI overview

Attackers exploited a vulnerability in Optimizely Experimentation's signup flow to impersonate users and inject malicious JavaScript into customer projects. Researcher Scott Helme's team confirmed 178 infected sites and said there could be more. The code, added to Optimizely's trusted CDN snippet, stole payment-card details entered in sites' own form fields, cookies, and screenshots; it also swapped cryptocurrency wallet addresses and delivered iOS exploit kits. Hosted payment iframes such as Stripe and Adyen were beyond the observed card skimmer's reach. Optimizely said it blocked the vulnerable path, revoked sessions and tokens, removed injected code, and blocked delivery, but Helme could not yet verify the flaw was closed. Analyst Frank Dickson cited a three-and-a-half-hour discrepancy in the reported start times and questioned the vendor's early assurances. He advised restricting script and connection sources, removing unsafe-eval where possible, and starting CSP changes in report-only mode.

### Source excerpt

Attackers apparently from China used an authentication security hole within the popular Optimizely AI platform for marketers to steal from at least 178 sites owned by some of the planet's largest companies. Named victims featured vendors including Zoom, Paychex, Equifax, and GitLab, and end-user enterprises including Starbucks, IKEA, Mattel, American Eagle, Air France, Mutual of Omaha, Heineken, Home Chef, Cinnabon, American Eagle, Levi, Costco and HSBC. Salesforce issued a statement confirming that it had also been impacted by the attack. "Salesforce is investigating unauthorized modifications to scripts provided by Optimizely and used on certain Salesforce websites," it wrote in an email statement. "As a precaution, Salesforce is confirming that Optimizely scripts are disabled across preview and production instances." The attacks were discovered by UK-based security researcher Scott Helme, the founder of Report URI, who said in an interview that his team had confirmed 178 victims, but that there could be more. "That's the number that we directly observed and that all carried the same infection," he said. Helme published a report about the attacks on Monday, in which he described an attack methodology where an Optimizely capability in its Web Experimentation product facilitating adding members to a site's development team was leveraged to insert malware into the sites. "The malware was a multi-purpose kit. It swapped cryptocurrency wallet addresses for the attacker's, skimmed payment cards, stole cookies and screenshots, and on iPhones and iPads it delivered the Coruna and DarkSword iOS exploit kits," Helme wrote. "The important lesson here is that trusted JavaScript doesn't always remain trustworthy. A website can be compromised through a third-party dependency without its own code or infrastructure ever being breached." Optimizely customers load a JavaScript "snippet" from Optimizely's CDN onto their sites which contains Optimizely code, the customer's A/B tests,

## 178 Organizations Served Malware Through Optimizely. What Have the Companies Said?

DevFeed: [178 Organizations Served Malware Through Optimizely. What Have the Companies Said?](<https://devfeed.tech/articles/178-organizations-served-malware-through-optimizely-what-have-the-companies-said-138681.md>)

Original publisher: [Read original article](<https://hackernoon.com/178-organizations-served-malware-through-optimizely-what-have-the-companies-said?source=rss>)

Author: Cyber Espionage

Published: 2026-11-17T21:02:36Z

Content type: news

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Malware](<https://devfeed.tech/topics/malware.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>)

Tags: [cnn](<https://devfeed.tech/tags/cnn.md>), [cybersecurity-incident](<https://devfeed.tech/tags/cybersecurity-incident.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-outbreak](<https://devfeed.tech/tags/malware-outbreak.md>), [optimizely](<https://devfeed.tech/tags/optimizely.md>), [optimizely-malware](<https://devfeed.tech/tags/optimizely-malware.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [salesforce](<https://devfeed.tech/tags/salesforce.md>), [scripts](<https://devfeed.tech/tags/scripts.md>), [served-malware](<https://devfeed.tech/tags/served-malware.md>), [zoom](<https://devfeed.tech/tags/zoom.md>)

### AI overview

Attackers exploited an Optimizely Experimentation vulnerability on November 16 to inject malicious JavaScript into customer projects, serving malware through legitimate snippets on sites in a 178-entry inventory. The payload could substitute cryptocurrency addresses, skim card details from page-accessible forms, transmit readable cookies and screenshots in some cases, and attempt iOS exploit delivery; confirmed totals for affected visitors, stolen data, device compromises and losses remain unknown. Optimizely said it fixed the vulnerability, removed injected code and notified affected business customers. Salesforce issued an advisory and said it would notify affected customers if it identified unauthorized data access. Zoom said it disabled Optimizely in production as a precaution and had not identified customer-data impact at that time. Equifax told Reuters it stopped using Optimizely and found no evidence its own systems were compromised; IKEA said it was assessing potential effects. The excerpt verifies public responses from these four organizations plus Optimizely (five distinct companies), but does not establish how many affected organizations notified website visitors. Its 〝鈥

### Source excerpt

178 organizations served malware through compromised Optimizely scripts. From CNN to Zoom and Salesforce, here's what happened and how companies responded.

## Thundermail Q4 2026 recap: new features, your feedback, and what's next

DevFeed: [Thundermail Q4 2026 recap: new features, your feedback, and what's next](<https://devfeed.tech/articles/thundermail-q4-2026-recap-new-features-your-feedback-and-what-s-next-138601.md>)

Original publisher: [Read original article](<https://blog.thunderbird.net/2026/11/thundermail-q4-2026-recap-new-features-your-feedback-and-whats-next/>)

Author: ltoh

Published: 2026-11-17T20:23:00Z

Content type: news

Language: en

Sources: [The Thunderbird Blog](<https://devfeed.tech/sources/the-thunderbird-blog.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [2027](<https://devfeed.tech/tags/2027.md>), [aliases](<https://devfeed.tech/tags/aliases.md>), [alpha](<https://devfeed.tech/tags/alpha.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [auto-complete](<https://devfeed.tech/tags/auto-complete.md>), [bcc](<https://devfeed.tech/tags/bcc.md>), [birds](<https://devfeed.tech/tags/birds.md>), [caldav](<https://devfeed.tech/tags/caldav.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [cc](<https://devfeed.tech/tags/cc.md>), [features](<https://devfeed.tech/tags/features.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [ideas](<https://devfeed.tech/tags/ideas.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [next](<https://devfeed.tech/tags/next.md>), [q4](<https://devfeed.tech/tags/q4.md>), [recap](<https://devfeed.tech/tags/recap.md>), [thunderbird](<https://devfeed.tech/tags/thunderbird.md>), [thundermail](<https://devfeed.tech/tags/thundermail.md>)

### AI overview

Thundermail's Q4 recap describes an actively developing webmail service shaped by Early Bird feedback. Its webmail has added compose tools, inbox search and message controls, and contact and identity management; accounts include 15 service-domain aliases, with up to three custom domains supporting unlimited aliases and catch-all routing. MFA is available through an authenticator app, with recovery codes recommended. Send provides end-to-end encrypted file sharing, and Appointment supports booking. Users are requesting a webmail calendar, separate inboxes for custom domains, more pricing options, and migration of email, calendar, and contacts history. Calendar access is currently via CalDAV without a web interface. The team targets a visual server-side mail-rules editor for December and a webmail calendar for Q1 2027; these are plans, not completed features. The post notes that webmail still has rough edges.

### Source excerpt

It has been quite a year. When we started welcoming our first Early Birds into Thundermail, we had a waitlist, a vision, and a lot of work ahead of us. Since then, thousands of you have joined, tested, filed ideas, and helped us shape what this service is becoming. The upcoming new year is a [...] The post Thundermail Q4 2026 recap: new features, your feedback, and what's next appeared first on The Thunderbird Blog.

## Malware spread through Optimizely hits 178 organizations, including BBC, CNN and Zoom

DevFeed: [Malware spread through Optimizely hits 178 organizations, including BBC, CNN and Zoom](<https://devfeed.tech/articles/malware-spread-through-optimizely-hits-178-organizations-including-bbc-cnn-and-zoom-137117.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/11/17/optimizely-vulnerability-malicious-javascript/>)

Author: Sinisa Markovic

Published: 2026-11-17T11:53:40Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [XSS](<https://devfeed.tech/topics/xss.md>), [Malware](<https://devfeed.tech/topics/malware.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [bbc](<https://devfeed.tech/tags/bbc.md>), [cnn](<https://devfeed.tech/tags/cnn.md>), [code](<https://devfeed.tech/tags/code.md>), [company](<https://devfeed.tech/tags/company.md>), [cryptocurrency](<https://devfeed.tech/tags/cryptocurrency.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customer-projects](<https://devfeed.tech/tags/customer-projects.md>), [customers](<https://devfeed.tech/tags/customers.md>), [cyberattack](<https://devfeed.tech/tags/cyberattack.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [experimentation](<https://devfeed.tech/tags/experimentation.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [hot-stuff](<https://devfeed.tech/tags/hot-stuff.md>), [hudson-rock](<https://devfeed.tech/tags/hudson-rock.md>), [incident](<https://devfeed.tech/tags/incident.md>), [ios](<https://devfeed.tech/tags/ios.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malicious-javascript](<https://devfeed.tech/tags/malicious-javascript.md>), [malware](<https://devfeed.tech/tags/malware.md>), [news](<https://devfeed.tech/tags/news.md>), [optimizely](<https://devfeed.tech/tags/optimizely.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [party](<https://devfeed.tech/tags/party.md>), [plant](<https://devfeed.tech/tags/plant.md>), [zoom](<https://devfeed.tech/tags/zoom.md>)

### AI overview

On 16 November 2026, an attacker exploited Optimizely Experimentation to inject malicious JavaScript into customer projects; the code was served from Optimizely's own CDN. Researcher Scott Helme's team found malware in 188 of 1,611 snippets checked, affecting visitors at 178 organizations. The payload evolved during the day and could replace crypto wallet addresses, skim card details entered into sites' own payment forms, steal cookies and screenshots, and deliver iOS exploit kits. Card fields operated by a separate payment provider were out of reach; researchers cautioned that some claimed iOS stages had not been independently reproduced or shown to compromise a real device. Optimizely said it fixed the vulnerability, removed injected code and secured affected accounts. Helme's crawl found only 24 organizations had CSP policies strict enough to block the attack; allowing Optimizely's domain did not help because the malicious code came from there.

### Source excerpt

An attacker exploited a vulnerability in Optimizely's web experimentation platform to plant malicious JavaScript on its customers' websites, the company has confirmed. Companies add Optimizely Web to their sites through a JavaScript snippet loaded from Optimizely's servers. "Earlier today, Optimizely identified a security incident in which an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects. We've fixed the vulnerability and removed the injected code from ... More -> The post Malware spread through Optimizely hits 178 organizations, including BBC, CNN and Zoom appeared first on Help Net Security.

## Whose Agent Are You? Multi-Layer Fingerprinting and Attribution of Autonomous Web Agents

DevFeed: [Whose Agent Are You? Multi-Layer Fingerprinting and Attribution of Autonomous Web Agents](<https://devfeed.tech/articles/whose-agent-are-you-multi-layer-fingerprinting-and-attribution-of-autonomous-web-agents-131938.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2606.20910>)

Author: Dayeon Kang, Hyejun Jeong, Jade Sheffey, Pubali Datta, Amir Houmansadr

Published: 2026-11-13T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [agentic browsing](<https://devfeed.tech/topics/agentic-browsing.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Browser Automation](<https://devfeed.tech/topics/browser-automation.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-frameworks](<https://devfeed.tech/tags/agent-frameworks.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-web](<https://devfeed.tech/tags/ai-web.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [attribution](<https://devfeed.tech/tags/attribution.md>), [autogen](<https://devfeed.tech/tags/autogen.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [bot](<https://devfeed.tech/tags/bot.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsing](<https://devfeed.tech/tags/browsing.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [claude](<https://devfeed.tech/tags/claude.md>), [content](<https://devfeed.tech/tags/content.md>), [content-protection](<https://devfeed.tech/tags/content-protection.md>), [crawlers](<https://devfeed.tech/tags/crawlers.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

The paper presents a multi-layer fingerprinting method to distinguish autonomous web agents from human visitors and traditional crawlers. A logging framework on an instrumented domain combines network characteristics, including TLS and HTTP behavior, with browser interaction patterns. Tested on AutoGen, Browser Use, Claude, Gemini, ChatGPT, and Skyvern, the features reveal differences in request construction, connection setup, and browser actions. A decision tree classifier reportedly achieved 100% accuracy in the study, identifying agent architectures and separating their traffic from human and legacy-crawler baselines. The authors propose cross-layer tracking as a way to support content protection and web security policy enforcement; the supplied abstract does not detail the evaluation conditions or limits of that accuracy result.

### Source excerpt

arXiv:2606.20910v2 Announce Type: replace-cross Abstract: As AI web agents proliferate, combining large language models with autonomous, browser-level control, indiscriminate content scraping by web agents has emerged as a privacy and security challenge. Existing defenses, such as robots.txt and active bot-blocking, are insufficient, as they are widely violated and easily circumvented. In this work, we demonstrate that AI web agents can be effectively distinguished from humans and traditional crawlers using a multi-layer fingerprint based on both network layer characteristics (e.g., TLS, HTTP) and browser interaction behavior. We implement this mechanism as a programmatic logging framework that can be deployed on a live, instrumented domain. By analyzing six prominent agent frameworks (AutoGen, Browser Use, Claude, Gemini, ChatGPT, and Skyvern), we uncover latent structural differences in how these systems assemble HTTP requests, establish TLS/HTTP connections, and execute autonomous browser actions. Feeding these multi-layer features into a decision tree classifier, our framework achieves high-fidelity identification (100% accuracy), successfully isolating distinct agent architectures and differentiating agent traffic from both human browsing baselines and legacy crawlers. Our findings demonstrate that cross-layer agent tracking provides a robust approach to content protection and web security policy enforcement.

## What Are HttpOnly Cookies? A Simple Guide to Secure Sessions

DevFeed: [What Are HttpOnly Cookies? A Simple Guide to Secure Sessions](<https://devfeed.tech/articles/what-are-httponly-cookies-a-simple-guide-to-secure-sessions-130198.md>)

Original publisher: [Read original article](<https://hackernoon.com/what-are-httponly-cookies-a-simple-guide-to-secure-sessions?source=rss>)

Author: Mohsen

Published: 2026-11-12T07:14:02Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [XSS](<https://devfeed.tech/topics/xss.md>), [LocalStorage](<https://devfeed.tech/topics/localstorage.md>)

Tags: [cookies](<https://devfeed.tech/tags/cookies.md>), [cross-site-scripting](<https://devfeed.tech/tags/cross-site-scripting.md>), [csrf](<https://devfeed.tech/tags/csrf.md>), [express](<https://devfeed.tech/tags/express.md>), [httponly-cookies](<https://devfeed.tech/tags/httponly-cookies.md>), [js](<https://devfeed.tech/tags/js.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [nextjs](<https://devfeed.tech/tags/nextjs.md>), [security](<https://devfeed.tech/tags/security.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [theft](<https://devfeed.tech/tags/theft.md>), [web](<https://devfeed.tech/tags/web.md>), [web-application-security](<https://devfeed.tech/tags/web-application-security.md>), [xss](<https://devfeed.tech/tags/xss.md>)

### AI overview

An `HttpOnly` session cookie keeps its value out of JavaScript while the browser still sends it to the server on matching requests. This blocks injected scripts from reading and exfiltrating the token, but does not stop XSS: malicious code running in the page can still make authenticated requests, and HttpOnly does not by itself prevent CSRF. Set the cookie server-side with `Set-Cookie`; client JavaScript cannot create an HttpOnly cookie. The excerpt recommends pairing it with `Secure` and `SameSite`, and notes that sensitive actions may also need a CSRF token. Its Express and Next.js examples differ in `maxAge` units: milliseconds in Express, seconds in Next.js. It also describes `SameSite=Lax` as a common session default and `Strict` as more restrictive, with usability tradeoffs.

### Source excerpt

What the HttpOnly flag does, what it stops (token theft via XSS), what it doesn't, and how to set it in Express and Next.js.

## Blind trust: stealing credentials through CSP

DevFeed: [Blind trust: stealing credentials through CSP](<https://devfeed.tech/articles/blind-trust-stealing-credentials-through-csp-129540.md>)

Original publisher: [Read original article](<https://portswigger.net/research/blind-trust-stealing-credentials-through-csp>)

Author: Gareth Heyes

Published: 2026-11-11T14:26:01Z

Content type: article

Language: en

Sources: [PortSwigger Research](<https://devfeed.tech/sources/portswigger-research.md>)

Topics: [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [XSS](<https://devfeed.tech/topics/xss.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [credentials](<https://devfeed.tech/tags/credentials.md>), [csp](<https://devfeed.tech/tags/csp.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The described Burp AT skill checks CSPs for allow-listed script gadgets and for a credential exfiltration path using a self-posting form. Gadget matching follows the `script-src-elem` -> `script-src` -> `default-src` fallback, browser-style host matching, and requires a gadget to be allowed by every enforced policy. Report-only findings are informational; `strict-dynamic`, nonce or hash gates, and unrestricted inline scripts affect whether a gadget applies. The form check accounts for the fact that `form-action` does not inherit from `default-src`: an omitted directive permits submissions anywhere, while `'self'` can still permit a reflected two-stage form to submit credentials and a payload back to the page, which then redirects to Burp Collaborator. The excerpt's example uses `default-src 'none'` with `form-action 'self'`; the skill reports that vector as viable despite scripts being blocked. When viable, it can build a PoC using the reflected parameter and configured Collaborator domain. The described method depends on a reflected HTML-injection sink.

### Source excerpt

Content Security Policy is supposed to be the safety net that stops an HTML injection from turning into XSS. Usually it works. But sometimes it doesn't, because the policy allows-lists a domain that h

## What Is Web Cache Deception and How Can Attackers Exploit It?

DevFeed: [What Is Web Cache Deception and How Can Attackers Exploit It?](<https://devfeed.tech/articles/what-is-web-cache-deception-and-how-can-attackers-exploit-it-128459.md>)

Original publisher: [Read original article](<https://hackernoon.com/what-is-web-cache-deception-and-how-can-attackers-exploit-it?source=rss>)

Author: Martins Chibueze

Published: 2026-11-11T06:50:13Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [cache-control](<https://devfeed.tech/topics/cache-control.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [appsec](<https://devfeed.tech/tags/appsec.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [audit](<https://devfeed.tech/tags/audit.md>), [burp-suite](<https://devfeed.tech/tags/burp-suite.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cache-control](<https://devfeed.tech/tags/cache-control.md>), [cache-deception-armor](<https://devfeed.tech/tags/cache-deception-armor.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [clicks](<https://devfeed.tech/tags/clicks.md>), [client](<https://devfeed.tech/tags/client.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [data](<https://devfeed.tech/tags/data.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [file](<https://devfeed.tech/tags/file.md>), [penetration-testing](<https://devfeed.tech/tags/penetration-testing.md>), [portswigger](<https://devfeed.tech/tags/portswigger.md>), [prevent](<https://devfeed.tech/tags/prevent.md>), [private](<https://devfeed.tech/tags/private.md>), [static](<https://devfeed.tech/tags/static.md>), [url-parsing-vulnerability](<https://devfeed.tech/tags/url-parsing-vulnerability.md>), [web](<https://devfeed.tech/tags/web.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

Web cache deception can expose private, user-specific responses when a cache and origin server interpret the same URL differently. In the described PortSwigger lab, appending "x.css" to a private account URL left the origin serving the account page while the cache treated the .css suffix as a static-file rule; a later cache hit returned the user's API key. The text says attackers may lure victims to such URLs through links or phishing, then request the same URL to read the cached response. Suggested protections are to mark authenticated or personalized responses `Cache-Control: no-store, private`, ensure CDN rules honor that header, enable CDN-native protections such as Cloudflare Cache Deception Armor, which checks Content-Type against the requested extension, and audit URL parsing and normalization for cache-origin mismatches.

### Source excerpt

What happens when a web cache mistakes private data for a static file? Explore web cache deception attacks and how to prevent them.

## Announcing origin-bound OTP-Token headers in Appwrite Auth

DevFeed: [Announcing origin-bound OTP-Token headers in Appwrite Auth](<https://devfeed.tech/articles/announcing-origin-bound-otp-token-headers-in-appwrite-auth-128964.md>)

Original publisher: [Read original article](<https://appwrite.io/blog/post/announcing-otp-token-email-header>)

Author: Aditya Oberai

Published: 2026-11-11T00:00:00Z

Content type: release

Language: en

Sources: [Appwrite Blog](<https://devfeed.tech/sources/appwrite-blog.md>)

Topics: [Appwrite](<https://devfeed.tech/topics/appwrite.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [email](<https://devfeed.tech/topics/email.md>)

Tags: [announcements](<https://devfeed.tech/tags/announcements.md>), [auth](<https://devfeed.tech/tags/auth.md>), [autofill](<https://devfeed.tech/tags/autofill.md>), [email](<https://devfeed.tech/tags/email.md>), [headers](<https://devfeed.tech/tags/headers.md>), [otp](<https://devfeed.tech/tags/otp.md>), [password-managers](<https://devfeed.tech/tags/password-managers.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

Appwrite Auth now adds an `OTP-Token` email header carrying a one-time code and the requesting web origin, allowing compatible mail clients, browsers, and password managers to offer autofill only on that origin. It applies to email OTP sign-in, verification, recovery, and email MFA challenges on Appwrite Cloud and self-hosted 2.7+, with no setting or SDK update; mark code inputs `autocomplete="one-time-code"`. Appwrite binds only usable HTTPS or local development origins, so server-side calls, native-app schemes, and public HTTP origins receive the existing email without the header. Custom SMTP relays may rewrite the header. Support depends on client software and an early IETF Internet-Draft. Origin binding reduces phishing risk during autofill but does not stop users from manually entering codes on phishing sites; the text recommends passkeys for phishing-resistant sign-in.

### Source excerpt

Appwrite Auth now adds an OTP-Token header to every email code, so mail clients and password managers can autofill the code on your app's origin only.

## New in Symfony 8.2: AssetMapper Improvements

DevFeed: [New in Symfony 8.2: AssetMapper Improvements](<https://devfeed.tech/articles/new-in-symfony-8-2-assetmapper-improvements-127158.md>)

Original publisher: [Read original article](<https://symfony.com/blog/new-in-symfony-8-2-assetmapper-improvements>)

Author: Javier Eguiluz

Published: 2026-11-10T08:14:00Z

Content type: release

Language: en

Sources: [Symfony](<https://devfeed.tech/sources/symfony-blog.md>)

Topics: [Symfony](<https://devfeed.tech/topics/symfony.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [import](<https://devfeed.tech/topics/import.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [asset](<https://devfeed.tech/tags/asset.md>), [asset-map](<https://devfeed.tech/tags/asset-map.md>), [assets](<https://devfeed.tech/tags/assets.md>), [css](<https://devfeed.tech/tags/css.md>), [development](<https://devfeed.tech/tags/development.md>), [directory](<https://devfeed.tech/tags/directory.md>), [esm](<https://devfeed.tech/tags/esm.md>), [feature](<https://devfeed.tech/tags/feature.md>), [files](<https://devfeed.tech/tags/files.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [map](<https://devfeed.tech/tags/map.md>), [maps](<https://devfeed.tech/tags/maps.md>), [security](<https://devfeed.tech/tags/security.md>), [symfony](<https://devfeed.tech/tags/symfony.md>), [third-party](<https://devfeed.tech/tags/third-party.md>)

### AI overview

Symfony 8.2 adds AssetMapper controls for package integrity, version timing, import-map exposure and compiled metadata. Configurable SHA-256, SHA-384 or SHA-512 hashes add SRI attributes to rendered resources. `minimum_release_age` makes `importmap:update` hold back newer releases, prereleases and versions above `latest`; `importmap:outdated` lists withheld versions. It does not restrict `importmap:require`, and checking publication dates requires downloading larger npm metadata. The new `--no-esm` option fetches a package file as published, but requires its in-package path; relative imports are fetched while bare imports must still be required separately. In debug mode, AssetMapper now ignores compiled metadata so source edits are used. Setting `importmap_entries: reachable` limits rendered entries to those reachable through static and dynamic imports, but cannot trace variable dynamic imports and is disabled by default. `metadata_dir` can move generated metadata outside the public assets directory; its default remains unchanged.

### Source excerpt

AssetMapper lets you use modern JavaScript and CSS without a build step, relying on native browser features like import maps. Symfony 8.2 improves it in several areas: security of third-party packages, control over what the import map exposes, and a smoother...

## Vercel Introduces DBSC: How It Protects Against Cookie Theft

DevFeed: [Vercel Introduces DBSC: How It Protects Against Cookie Theft](<https://devfeed.tech/articles/vercel-introduces-dbsc-how-it-protects-against-cookie-theft-121451.md>)

Original publisher: [Read original article](<https://www.techrepublic.com/article/news-vercel-dbsc-session-cookie-theft-protection/>)

Author: Joseph Ofonagoro

Published: 2026-11-06T16:58:33Z

Content type: news

Language: en

Sources: [TechRepublic](<https://devfeed.tech/sources/techrepublic.md>)

Topics: [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [browser-security](<https://devfeed.tech/tags/browser-security.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [dbsc](<https://devfeed.tech/tags/dbsc.md>), [device-bound-session-credentials](<https://devfeed.tech/tags/device-bound-session-credentials.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [infostealer-malware](<https://devfeed.tech/tags/infostealer-malware.md>), [news](<https://devfeed.tech/tags/news.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [security](<https://devfeed.tech/tags/security.md>), [session-cookies](<https://devfeed.tech/tags/session-cookies.md>), [session-hijacking](<https://devfeed.tech/tags/session-hijacking.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel is gradually rolling out Device Bound Session Credentials (DBSC) to make stolen session cookies harder to replay. It binds a browser session to a device-held cryptographic key, which the browser must prove it has before the server renews the session; a stolen cookie alone ordinarily cannot provide that proof. The excerpt says Vercel's implementation currently works only in Chrome, following support in Chrome 146 on Windows and Chrome 148 on macOS. Windows uses a compatible TPM to protect keys, while macOS uses Apple's Secure Enclave, so unsupported or unavailable hardware may prevent users from benefiting. DBSC makes cookie theft less useful but does not stop other credential theft or malware on a compromised device. The excerpt recommends continuing MFA, activity monitoring, updates and access restrictions, and checking device support and rollout status.

### Source excerpt

Vercel is rolling out DBSC to make stolen session cookies harder to exploit. Learn how the protection works, its hardware requirements and security limits. The post Vercel Introduces DBSC: How It Protects Against Cookie Theft appeared first on TechRepublic.

## Vercel ties login sessions to devices, rolls out AI security reviews in public beta

DevFeed: [Vercel ties login sessions to devices, rolls out AI security reviews in public beta](<https://devfeed.tech/articles/vercel-ties-login-sessions-to-devices-rolls-out-ai-security-reviews-in-public-beta-119162.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/11/05/vercel-security-review-session-hijacking/>)

Author: Zeljka Zorz

Published: 2026-11-05T14:37:00Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [Security](<https://devfeed.tech/topics/security.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [MFA](<https://devfeed.tech/topics/mfa.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [applications](<https://devfeed.tech/tags/applications.md>), [beta](<https://devfeed.tech/tags/beta.md>), [cloud-based](<https://devfeed.tech/tags/cloud-based.md>), [cloud-platform](<https://devfeed.tech/tags/cloud-platform.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [device-bound-session-credentials](<https://devfeed.tech/tags/device-bound-session-credentials.md>), [devices](<https://devfeed.tech/tags/devices.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [hijacking](<https://devfeed.tech/tags/hijacking.md>), [hot-stuff](<https://devfeed.tech/tags/hot-stuff.md>), [infostealer](<https://devfeed.tech/tags/infostealer.md>), [launch](<https://devfeed.tech/tags/launch.md>), [login](<https://devfeed.tech/tags/login.md>), [malware](<https://devfeed.tech/tags/malware.md>), [news](<https://devfeed.tech/tags/news.md>), [public-beta](<https://devfeed.tech/tags/public-beta.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [security](<https://devfeed.tech/tags/security.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [web-application-security](<https://devfeed.tech/tags/web-application-security.md>)

### AI overview

Vercel is rolling out device-bound login sessions and a code security review tool. Device Bound Session Credentials (DBSC) stores a key in device secure hardware and requires browsers to prove possession of it to refresh short-lived session cookies, limiting the value of stolen cookies. If secure key storage is unavailable, authentication falls back to standard behavior. The excerpt says DBSC is currently supported only in Chrome on Mac and Windows; Vercel is rolling it out gradually and is working on a less secure polyfill for other browsers and DPoP for its CLI. Vercel Security Review, in public beta for Pro and Enterprise teams, scans code changed since the previous deployment on GitHub pushes, traces reachability and existing protections, and reports findings on pull requests, in the Security dashboard, and via CLI. Vercel Agent can verify a finding and commit a minimal fix with updated tests, or users can pass findings to another coding agent. Use is free until November 10, 2026.

### Source excerpt

Vercel, the popular cloud platform for building and hosting websites and web applications, has announced the rollout of Device Bound Session Credentials (DBSC) and the launch of Vercel Security Review in public beta. Making stolen session cookies worthless Device Bound Session Credentials is a security technology designed to limit the consequences of an infostealer infection and to thwart attackers' session hijacking attempts. Aside from stealing authentication credentials, modern info-stealing malware such as Lumma, RedLine, and ... More -> The post Vercel ties login sessions to devices, rolls out AI security reviews in public beta appeared first on Help Net Security.

## Common Security Risks in File Upload and Sharing Platforms

DevFeed: [Common Security Risks in File Upload and Sharing Platforms](<https://devfeed.tech/articles/common-security-risks-in-file-upload-and-sharing-platforms-118797.md>)

Original publisher: [Read original article](<https://hackernoon.com/common-security-risks-in-file-upload-and-sharing-platforms?source=rss>)

Author: Filestack

Published: 2026-11-05T06:29:55Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [XSS](<https://devfeed.tech/topics/xss.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [antivirus](<https://devfeed.tech/tags/antivirus.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [app](<https://devfeed.tech/tags/app.md>), [fake](<https://devfeed.tech/tags/fake.md>), [file](<https://devfeed.tech/tags/file.md>), [file-upload](<https://devfeed.tech/tags/file-upload.md>), [file-upload-malware](<https://devfeed.tech/tags/file-upload-malware.md>), [file-upload-validation](<https://devfeed.tech/tags/file-upload-validation.md>), [filestack](<https://devfeed.tech/tags/filestack.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [links](<https://devfeed.tech/tags/links.md>), [malware](<https://devfeed.tech/tags/malware.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [risks](<https://devfeed.tech/tags/risks.md>), [security](<https://devfeed.tech/tags/security.md>), [security-risks](<https://devfeed.tech/tags/security-risks.md>), [share](<https://devfeed.tech/tags/share.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [sharing-platforms](<https://devfeed.tech/tags/sharing-platforms.md>), [types](<https://devfeed.tech/tags/types.md>), [upload](<https://devfeed.tech/tags/upload.md>), [user](<https://devfeed.tech/tags/user.md>), [virus-scanning-api](<https://devfeed.tech/tags/virus-scanning-api.md>)

### AI overview

File upload and sharing risks arise at different stages: intake can admit malware, active scripts, disguised file types or resource exhaustion, while delivery can expose files through weak access checks, long-lived or guessable links, unsafe hosting domains and retained metadata. The article recommends validating file contents rather than trusting client names or types, limiting uploads, scanning files and serving only clean copies. For sharing, check per-file authorization before issuing a signed, read-only link with a short expiry; signed links do not identify who holds them. It also describes delivering files from a separate CDN domain and sharing processed images when location metadata should be removed. Filestack examples use signed upload policies and a virus-detection workflow, while the app remains responsible for deciding which users may access each file.

### Source excerpt

The common security risks in user file upload and sharing platforms, from malware and fake file types to guessable share links, and how to stop each one.

## CVE-2026-92704 - SharpEmu: Cross-site request forgery in the debugger frontend leads to arbitrary process execution

DevFeed: [CVE-2026-92704 - SharpEmu: Cross-site request forgery in the debugger frontend leads to arbitrary process execution](<https://devfeed.tech/articles/cve-2026-92704-sharpemu-cross-site-request-forgery-in-the-debugger-frontend-leads-to-arbitrary-process-execution-117098.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-92704>)

Author: CVEFEED.io; github.com

Published: 2026-11-04T16:17:55Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [also](<https://devfeed.tech/tags/also.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [body](<https://devfeed.tech/tags/body.md>), [browser](<https://devfeed.tech/tags/browser.md>), [can](<https://devfeed.tech/tags/can.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-92704](<https://devfeed.tech/tags/cve-2026-92704.md>), [debugger](<https://devfeed.tech/tags/debugger.md>), [execution](<https://devfeed.tech/tags/execution.md>), [forgery](<https://devfeed.tech/tags/forgery.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [process](<https://devfeed.tech/tags/process.md>), [request](<https://devfeed.tech/tags/request.md>), [site](<https://devfeed.tech/tags/site.md>)

### AI overview

SharpEmu's repository-provided debugger frontend in versions 0.0.3-release.3 and earlier exposes an unauthenticated loopback API vulnerable to cross-site requests: it lacks CSRF and request-origin checks and accepts JSON with browser-simple content types. A page that can reach the listener may invoke launch, debugger-command, or TCP-connect endpoints. Launch requires an existing emulator binary (executable on POSIX) and an existing ebootPath; the other endpoints can control an attached emulated process or reach host-accessible network services. DNS rebinding may also enable interactive reading of API responses. Chromium may require Local Network Access permission for public-origin pages, but the excerpt says local-origin pages and other delivery paths are not consistently restricted. The issue is fixed in 0.0.3-release.3-patch.1; the debugger tooling is not included in release archives.

### Source excerpt

CVE ID :CVE-2026-92704 Published : Nov. 4, 2026, 4:17 p.m. | 56 minutes ago Description :SharpEmu is an experimental PlayStation 5 emulator for Windows and Linux. In version 0.0.3-release.3 and earlier, the repository-provided debugger frontend tooling is vulnerable while running. This tooling is not included in the release archives. The frontend exposes an HTTP API on 127.0.0.1:8765 without authentication or CSRF token. Its do_POST handler in tools/SharpEmu.DebuggerFrontend/debugger_frontend.py does not validate the Origin, Referer, Sec-Fetch-Site, or Host headers. The _read_json_body() function also accepts JSON sent with browser-simple content types instead of requiring application/json . A malicious page that can reach the loopback listener can send cross-origin requests to /api/launch , /api/command , and /api/connect . Chromium may require Local Network Access permission for pages served from public origins. Local-origin pages and other delivery paths are not consistently subject to this restriction. The /api/launch endpoint accepts an attacker-selected emulatorPath if it points to an existing file on the victim's host. On POSIX systems, that file must also be executable. The endpoint additionally requires an existing ebootPath . The /api/command endpoint exposes debugger operations, including write-memory , set-register , and continue . The /api/connect endpoint can initiate outbound TCP connections. These operations can let an attacker execute an existing binary with the victim's privileges, control the attached emulated process, or reach network services accessible from the host. DNS rebinding can additionally let the attacker read API responses interactively. This issue is fixed in version 0.0.3-release.3-patch.1 Severity: 8.3 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Making HTTP header injection critical with one prompt

DevFeed: [Making HTTP header injection critical with one prompt](<https://devfeed.tech/articles/making-http-header-injection-critical-with-one-prompt-117789.md>)

Original publisher: [Read original article](<https://portswigger.net/research/making-http-header-injection-critical-with-one-prompt>)

Author: Tom Stacey

Published: 2026-11-04T15:12:29Z

Content type: release

Language: en

Sources: [PortSwigger Research](<https://devfeed.tech/sources/portswigger-research.md>)

Topics: [HTTP](<https://devfeed.tech/topics/http.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [prompt](<https://devfeed.tech/topics/prompt.md>)

Tags: [critical](<https://devfeed.tech/tags/critical.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [header](<https://devfeed.tech/tags/header.md>), [http](<https://devfeed.tech/tags/http.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [redirect](<https://devfeed.tech/tags/redirect.md>), [scan](<https://devfeed.tech/tags/scan.md>)

### AI overview

Burp AT's new HTTP Request Header Injection check can use a staged workflow to test whether injection enables request splitting, identify redirect gadgets, and attempt a redirect to an attacker-controlled collaborator. It first determines where the injected header appears upstream, then fuzzes request prefixes; distinct status codes support a desync finding. If it finds a suitable redirect, it combines the request structure with that gadget and reports the exploit with evidence if repeated requests produce the expected redirect. The workflow favors this redirect route over Response Queue Poisoning, which the authors found too dangerous in testing; they say cache poisoning could extend the primitive to a full-site takeover. If exploitation steps fail, it can still report a validated or tentative finding. A separate tunnelling skill may run when full desync is not possible, seeking an access control bypass or preparing an Intruder session for manual testing.

### Source excerpt

You can now escalate HTTP header injection to a CRLF-Powered Desync and exploit it to serve random users a redirect to your collaborator, in a single prompt. We've just introduced a new scan check for

## GHSA-5mx8-mwrp-5693: Generated URLs Can Point to a Host Chosen by the Client

DevFeed: [GHSA-5mx8-mwrp-5693: Generated URLs Can Point to a Host Chosen by the Client](<https://devfeed.tech/articles/ghsa-5mx8-mwrp-5693-generated-urls-can-point-to-a-host-chosen-by-the-client-116459.md>)

Original publisher: [Read original article](<https://symfony.com/blog/ghsa-5mx8-mwrp-5693-generated-urls-can-point-to-a-host-chosen-by-the-client>)

Author: Fabien Potencier

Published: 2026-11-04T11:54:00Z

Content type: news

Language: en

Sources: [Symfony](<https://devfeed.tech/sources/symfony-blog.md>)

Topics: [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>)

Tags: [7-4](<https://devfeed.tech/tags/7-4.md>), [actions](<https://devfeed.tech/tags/actions.md>), [also](<https://devfeed.tech/tags/also.md>), [app](<https://devfeed.tech/tags/app.md>), [applications](<https://devfeed.tech/tags/applications.md>), [asset](<https://devfeed.tech/tags/asset.md>), [assets](<https://devfeed.tech/tags/assets.md>), [base](<https://devfeed.tech/tags/base.md>), [branch](<https://devfeed.tech/tags/branch.md>), [can](<https://devfeed.tech/tags/can.md>), [client](<https://devfeed.tech/tags/client.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [http](<https://devfeed.tech/tags/http.md>), [issue](<https://devfeed.tech/tags/issue.md>), [point](<https://devfeed.tech/tags/point.md>), [security](<https://devfeed.tech/tags/security.md>), [symfony](<https://devfeed.tech/tags/symfony.md>), [this](<https://devfeed.tech/tags/this.md>), [urls](<https://devfeed.tech/tags/urls.md>)

### AI overview

Symfony HTTP Foundation versions before 5.4.56, 6.4.50, 7.4.23, and 8.1.11 are affected. In certain front-controller configurations, Request::getBaseUrl() could accept a client-controlled prefix when the request URI began with `//` or `/\\`. Generated links, form actions, redirects, and relative asset URLs could then point to an attacker-chosen host, potentially exposing login credentials or loading attacker-hosted scripts. Exploitation requires a user to follow a crafted link. `framework.trusted_hosts` does not prevent it because the actual request host remains unchanged. The issue applies to apps whose front controller is in a subdirectory and whose server forwards URIs that do not begin with that directory, or that sets `SCRIPT_NAME` to the request path. Symfony says its documented configurations are unaffected. The fix makes `getBaseUrl()` return an empty base URL for these URI prefixes.

### Source excerpt

Affected versions Symfony HTTP Foundation versions <5.4.56, >=6, <6.4.50, >=7, <7.4.23, >=8, <8.1.11 are affected by this security issue. The issue has been fixed in Symfony HTTP Foundation 5.4.56, 6.4.50, 7.4.23, 8.1.11. Description...

## GHSA-3h27-hjv7-fqjx: Path Rules Enforced in Front of PHP Can Be Bypassed by Appending the Path to the Script Name

DevFeed: [GHSA-3h27-hjv7-fqjx: Path Rules Enforced in Front of PHP Can Be Bypassed by Appending the Path to the Script Name](<https://devfeed.tech/articles/ghsa-3h27-hjv7-fqjx-path-rules-enforced-in-front-of-php-can-be-bypassed-by-appending-the-path-to-the-script-name-116457.md>)

Original publisher: [Read original article](<https://symfony.com/blog/ghsa-3h27-hjv7-fqjx-path-rules-enforced-in-front-of-php-can-be-bypassed-by-appending-the-path-to-the-script-name>)

Author: Fabien Potencier

Published: 2026-11-04T11:54:00Z

Content type: release

Language: en

Sources: [Symfony](<https://devfeed.tech/sources/symfony-blog.md>)

Topics: [Symfony](<https://devfeed.tech/topics/symfony.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [apache](<https://devfeed.tech/tags/apache.md>), [block](<https://devfeed.tech/tags/block.md>), [branch](<https://devfeed.tech/tags/branch.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [cve](<https://devfeed.tech/tags/cve.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [http](<https://devfeed.tech/tags/http.md>), [location](<https://devfeed.tech/tags/location.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [patch](<https://devfeed.tech/tags/patch.md>), [php](<https://devfeed.tech/tags/php.md>), [request](<https://devfeed.tech/tags/request.md>), [route](<https://devfeed.tech/tags/route.md>), [router](<https://devfeed.tech/tags/router.md>), [rules](<https://devfeed.tech/tags/rules.md>), [script](<https://devfeed.tech/tags/script.md>), [security](<https://devfeed.tech/tags/security.md>), [symfony](<https://devfeed.tech/tags/symfony.md>), [waf](<https://devfeed.tech/tags/waf.md>)

### AI overview

Affected Symfony HTTP Foundation releases strip a script name such as `/index.php` even when it is only the beginning of a longer path segment. With `SCRIPT_NAME=/index.php`, `/index.phpadmin` can therefore be routed as `/admin`; encoded variants also work. Symfony `access_control` and firewall rules use the same path info as the router and are not affected, but front-of-PHP protections such as nginx or Apache path rules and CDN or WAF rules on `/admin` can be bypassed. The issue affects versions 5.4.50-5.4.55, 6.4.29-6.4.49, 7.3.7-7.4.22, and 8.0 through 8.1.10. The fix strips the script name only when followed by `/`, `?`, or the end of the URL; fixed releases are 5.4.56, 6.4.50, 7.4.23, and 8.1.11.

### Source excerpt

Affected versions Symfony HTTP Foundation versions >=5.4.50, <5.4.56, >=6.4.29, <6.4.50, >=7.3.7, <7.4.23, >=8, <8.1.11 are affected by this security issue. The issue has been fixed in Symfony HTTP Foundation 5.4.56, 6.4.50, 7.4.23,...

## The Native Menace: Host-to-Browser Cross-Boundary Attacks via Native Messaging

DevFeed: [The Native Menace: Host-to-Browser Cross-Boundary Attacks via Native Messaging](<https://devfeed.tech/articles/the-native-menace-host-to-browser-cross-boundary-attacks-via-native-messaging-116144.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.04291>)

Author: Jyotirmay Chauhan, Rownak Islam, Jason Polakis

Published: 2026-11-04T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [api](<https://devfeed.tech/tags/api.md>), [apps](<https://devfeed.tech/tags/apps.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browser-extensions](<https://devfeed.tech/tags/browser-extensions.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [channel](<https://devfeed.tech/tags/channel.md>), [communication](<https://devfeed.tech/tags/communication.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [digital-signing](<https://devfeed.tech/tags/digital-signing.md>), [downloads](<https://devfeed.tech/tags/downloads.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [european-union](<https://devfeed.tech/tags/european-union.md>), [google-drive](<https://devfeed.tech/tags/google-drive.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [native](<https://devfeed.tech/tags/native.md>)

### AI overview

The paper reports that a non-privileged malicious native app can exploit browser Native Messaging to intercept sensitive extension communications or misuse other native apps as confused deputies. Demonstrations target extensions for 1Password, the EU eID system, and Google Drive, with impacts including password vault leakage and arbitrary document signing in governmental workflows. The authors attribute the attacks to an untrusted communication channel lacking a root of trust or client attestation, and propose message encryption using out-of-band secret sharing as mitigation. This overview is based on the supplied abstract.

### Source excerpt

arXiv:2611.04291v1 Announce Type: new Abstract: Modern browsers are complex software platforms that users can customize through browser extensions to further expand their functionality. Extensions derive their functionality from privileged browser APIs that expose powerful capabilities. Prior work has extensively studied how malicious webpages or extensions can target those capabilities. However, prior research has overlooked the NativeMessaging API, which allows extensions to create a communication channel that bridges the gap between web content rendered in the browser and native apps running on the user's machine. This API enables workflows that cross the browser's boundary to perform critical operations (e.g., digital signing) or exchange sensitive data (e.g., credentials). In this paper, we conduct the first, to our knowledge, empirical security analysis of NativeMessaging, and present a novel attack that allows a non-privileged malicious native app to misuse browsers' native messaging capabilities to stealthily intercept sensitive communications or launch confused deputy attacks against other native apps. To demonstrate the significant risk introduced by native messaging, we present a series of concrete attacks against popular and critical apps (e.g., 1Password, the European Union's eID system, Google Drive), whose browser extensions have more than 532 million cumulative downloads. Our attacks have severe ramifications, including full password vault leakage, and arbitrary document signing in governmental workflows. Fundamentally, these attacks are possible due to native messaging being built on top of an untrusted communication channel without providing a root of trust or enforcing some form of client attestation. Accordingly, we propose a straightforward mitigation technique of message encryption with out-of-band secret sharing, to prevent our attacks.

## AgentShield: Fortifying Web Applications Against AI Agents and Agentic Browsers

DevFeed: [AgentShield: Fortifying Web Applications Against AI Agents and Agentic Browsers](<https://devfeed.tech/articles/agentshield-fortifying-web-applications-against-ai-agents-and-agentic-browsers-111215.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.41181>)

Author: Moiz Ali, Nafis Karim, Rownak Islam, Jyotirmay Chauhan, Dhruv Kuchhal, Jason Polakis

Published: 2026-11-02T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [agentic browsing](<https://devfeed.tech/topics/agentic-browsing.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [bot-defenses](<https://devfeed.tech/tags/bot-defenses.md>), [browser-agents](<https://devfeed.tech/tags/browser-agents.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [detection](<https://devfeed.tech/tags/detection.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [prompt-injection](<https://devfeed.tech/tags/prompt-injection.md>), [web](<https://devfeed.tech/tags/web.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>)

### AI overview

The abstract reports that many anti-bot defenses built for traditional automation struggle to detect AI browser agents. AgentShield aims to distinguish agents from people by using dynamic forms that reveal content progressively and collect detailed interaction telemetry tied to the agents' perception-reasoning-action loop. The authors also describe Extinction-induced Policy Drift: repeated obstruction can lead agents to relax safeguards and behave unsafely. They propose defensive prompt injections to mitigate agent-driven content extraction. The supplied text does not include detailed measurements or deployment specifics.

### Source excerpt

arXiv:2610.41181v1 Announce Type: new Abstract: LLM-powered browser agents are transforming web automation by autonomously interacting with websites and executing complex workflows. However, the effectiveness of existing anti-bot defenses against these systems remains unclear. We present a systematic empirical evaluation of modern agentic browsers against widely deployed anti-bot mechanisms, characterizing their capabilities, limitations, and behavioral differences from humans. Our results show that many defenses designed for traditional automation struggle to reliably detect autonomous AI-driven agents. Accordingly, we introduce AgentShield, a behavioral fingerprinting framework that targets the Perception-Reasoning-Action (PRA) loop underlying agentic user clients. By leveraging dynamic web forms that progressively reveal content and capture fine-grained interaction telemetry, AgentShield exposes behavioral artifacts that enable differentiation between human users and autonomous agents. We further demonstrate Extinction-induced Policy Drift (EPD), a novel attack in which repeated obstruction of task completion causes agents to relax their safeguards and engage in unsafe behaviors. Finally, we present defensive prompt injection techniques that exploit agent-specific weaknesses to mitigate emerging forms of autonomous web abuse that rely on content extraction. Our results highlight both the shortcomings of current web defenses against agentic user clients and the feasibility of practical detection mechanisms tailored to this new generation of web automation.

[Next page](<https://devfeed.tech/topics/frontend-security.md?cursor=WyIyMDI2LTExLTAyVDA1OjAwOjAwKzAwOjAwIiwgIjA4ZDNjN2UxLWJjMzktNGZkYy1hOTg2LTFjMDE0MjcyMDBmMCJd>)