# Cross-origin resource sharing (CORS)

Cross-origin resource sharing (CORS) is an HTTP-based protocol that lets servers declare whether responses can be shared with other origins.

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

## What Chrome Extensions Can and Cannot Do with Manifest V3

DevFeed: [What Chrome Extensions Can and Cannot Do with Manifest V3](<https://devfeed.tech/articles/what-chrome-extensions-can-and-cannot-do-with-manifest-v3-142013.md>)

Original publisher: [Read original article](<https://jsdev.space/chrome-extension-manifest/>)

Author: Anton Liberant

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

Content type: article

Language: en

Sources: [JavaScript Development](<https://devfeed.tech/sources/javascript-development.md>)

Topics: [Chrome extension](<https://devfeed.tech/topics/chrome-extension.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [certificates](<https://devfeed.tech/tags/certificates.md>), [chrome-extensions](<https://devfeed.tech/tags/chrome-extensions.md>), [http](<https://devfeed.tech/tags/http.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [manifest-v3](<https://devfeed.tech/tags/manifest-v3.md>), [websites](<https://devfeed.tech/tags/websites.md>)

### AI overview

Manifest V3 can support a useful browser monitor: `webRequest` observes main-frame status codes, server redirects, and approximate time to first response byte, while `webNavigation` helps identify client redirects and single-page app route changes. Coverage is incomplete: cached or prerendered pages, site service workers, and browser event ordering can leave gaps, so missing data should not be presented as a fresh HTTP result. Chrome 144's certificate-data option may require an experimental flag; reliable expiry checks may need a backend, with hostname and network protections and explicit user initiation. RDAP can provide registration expiry over HTTPS where supported, but coverage and disclosed dates vary; cache results and use a Public Suffix List library to find registered domains. MV3 workers can stop after inactivity, so persist state, register listeners at startup, and use alarms; alarms do not run while the device sleeps. Availability checks should be bounded and cookie-free, distinguish HTTP errors from network failures, filter noisy errors, and limit retries. Broad host permissions enable arbitrary-site monitoring; optional host permissions suit user-selected sites.

### Source excerpt

Learn how Chrome extensions can inspect HTTP responses, track redirects, check SSL certificates, and monitor websites under Manifest V3 limitations.

## HTTP Methods: GET, POST, PUT, PATCH and DELETE Explained

DevFeed: [HTTP Methods: GET, POST, PUT, PATCH and DELETE Explained](<https://devfeed.tech/articles/http-methods-get-post-put-patch-and-delete-explained-131779.md>)

Original publisher: [Read original article](<https://markodenic.com/http-methods/>)

Author: Marko

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

Content type: article

Language: en

Sources: [Marko Denic Blog](<https://devfeed.tech/sources/marko-denic-blog.md>)

Topics: [HTTP](<https://devfeed.tech/topics/http.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [CRUD](<https://devfeed.tech/topics/crud.md>), [fetch](<https://devfeed.tech/topics/fetch.md>)

Tags: [cors](<https://devfeed.tech/tags/cors.md>), [delete](<https://devfeed.tech/tags/delete.md>), [examples](<https://devfeed.tech/tags/examples.md>), [fetch](<https://devfeed.tech/tags/fetch.md>), [http](<https://devfeed.tech/tags/http.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [patch](<https://devfeed.tech/tags/patch.md>), [post](<https://devfeed.tech/tags/post.md>), [safe](<https://devfeed.tech/tags/safe.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [vs](<https://devfeed.tech/tags/vs.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

HTTP methods express the intended operation and affect whether requests can be safely repeated and whether browsers preflight cross-origin calls. GET reads data; POST creates a resource or triggers an action and may create duplicates when retried. PUT replaces the full resource, so omitted fields are removed; PATCH changes only specified fields, though repeatability depends on the patch operation. DELETE and PUT are idempotent in intended server state, even when repeated responses differ. HEAD returns GET headers without a body, and OPTIONS asks what the server allows. For cross-origin calls, browsers skip preflight only for simple GET, HEAD, or POST requests with allowed content types and no custom headers; PUT, PATCH, DELETE, and JSON POST require OPTIONS approval with suitable CORS headers. The text also notes that fetch() does not reject on HTTP error statuses, so callers should check response.ok, and recommends uppercase PATCH.

### Source excerpt

What each HTTP request method does, which ones are safe and idempotent, PUT vs PATCH vs POST, fetch() examples, and when CORS sends a preflight.

## Port Your Spring Code With Fewer Edits, and Libraries That Bring Their Own Server

DevFeed: [Port Your Spring Code With Fewer Edits, and Libraries That Bring Their Own Server](<https://devfeed.tech/articles/port-your-spring-code-with-fewer-edits-and-libraries-that-bring-their-own-server-128961.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/cn1libs-with-a-server-side/>)

Author: Shai Almog

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

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [backend frameworks](<https://devfeed.tech/topics/backend-frameworks.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Library](<https://devfeed.tech/topics/library.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [backend](<https://devfeed.tech/tags/backend.md>), [bigdecimal](<https://devfeed.tech/tags/bigdecimal.md>), [boot](<https://devfeed.tech/tags/boot.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [build](<https://devfeed.tech/tags/build.md>), [classes](<https://devfeed.tech/tags/classes.md>), [client](<https://devfeed.tech/tags/client.md>), [code](<https://devfeed.tech/tags/code.md>), [codename](<https://devfeed.tech/tags/codename.md>), [column](<https://devfeed.tech/tags/column.md>), [controllers](<https://devfeed.tech/tags/controllers.md>), [http](<https://devfeed.tech/tags/http.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [json](<https://devfeed.tech/tags/json.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [logging](<https://devfeed.tech/tags/logging.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [server](<https://devfeed.tech/tags/server.md>), [spring](<https://devfeed.tech/tags/spring.md>)

### AI overview

The Codename One backend adds Spring-style conveniences intended to let existing service code port with import changes: it now checks `consumes`/`produces`, handles CORS preflights, supports `ResponseStatusException`, and provides placeholder logging with per-thread MDC. Build-time JSON codecs support typed reads and writes without runtime reflection. The excerpt also lists added JDK, ORM, and security features, including HTTP/2 enforcement and an XML parser that refuses `DOCTYPE`. Libraries can now bundle server code: Maven cn1libs include a `backend.zip`, while Gradle publishes a `<library>-backend` artifact. A server dependency wires marked library controllers, beans, entities, repositories, and migrations at build time; unmarked jars are ignored, and same-named server classes take precedence.

### Source excerpt

A cn1lib can now ship its server half too: controllers, beans, entities and migrations that wire themselves in. Plus structured logging, typed JSON and HTTP/2 in the backend.

## How to Export HTML to DOCX with Images That Work on Mobile

DevFeed: [How to Export HTML to DOCX with Images That Work on Mobile](<https://devfeed.tech/articles/how-to-export-html-to-docx-with-images-that-work-on-mobile-119682.md>)

Original publisher: [Read original article](<https://jsdev.space/howto/html-to-docx/>)

Author: anton liberant

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

Content type: article

Language: en

Sources: [JavaScript Development](<https://devfeed.tech/sources/javascript-development.md>)

Topics: [HTML](<https://devfeed.tech/topics/html.md>), [Image](<https://devfeed.tech/topics/image.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [Markdown](<https://devfeed.tech/topics/markdown.md>)

Tags: [docx](<https://devfeed.tech/tags/docx.md>), [export](<https://devfeed.tech/tags/export.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [html](<https://devfeed.tech/tags/html.md>), [images](<https://devfeed.tech/tags/images.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [mobile](<https://devfeed.tech/tags/mobile.md>)

### AI overview

Mobile image loss often comes from the file's internal format: HTML renamed as .doc and DOCX packages relying on altChunk depend on viewers importing HTML, which desktop Word may do but mobile viewers may not. The article recommends generating native OOXML with the JavaScript docx library: parse HTML, map supported elements such as headings, paragraphs and tables to Word structures, and embed fetched or decoded image bytes in the DOCX. Remote image fetching requires CORS permission; the examples support PNG, JPEG, GIF and BMP. The converter is a foundation rather than a full HTML renderer, and does not cover features such as merged table cells without extra logic. It also recommends preserving image proportions, recording image failures, and testing in target mobile viewers. Large exports may use substantial memory, so server-side generation may be more reliable.

### Source excerpt

Learn why HTML-based Word exports lose images on mobile and how to generate compatible DOCX files with embedded images using JavaScript.

## 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...

## bREACHYing the Perimeter: How One HTTP Request can Hijack your AI Robot

DevFeed: [bREACHYing the Perimeter: How One HTTP Request can Hijack your AI Robot](<https://devfeed.tech/articles/breachying-the-perimeter-how-one-http-request-can-hijack-your-ai-robot-116289.md>)

Original publisher: [Read original article](<https://jfrog.com/blog/reachy-http-request-hijacks-ai-robot/>)

Author: drewt@jfrog.com

Published: 2026-11-03T14:15:25Z

Content type: article

Language: en

Sources: [From the Frog's mouth - JFrog Blog](<https://devfeed.tech/sources/from-the-frog-s-mouth-jfrog-blog.md>)

Topics: [reachy](<https://devfeed.tech/topics/reachy.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [smartdevices](<https://devfeed.tech/topics/smartdevices.md>), [huggingface\_hub](<https://devfeed.tech/topics/huggingface-hub.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-ml](<https://devfeed.tech/tags/ai-ml.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [cases](<https://devfeed.tech/tags/cases.md>), [cve-2026-96455](<https://devfeed.tech/tags/cve-2026-96455.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [extend](<https://devfeed.tech/tags/extend.md>), [fastapicve](<https://devfeed.tech/tags/fastapicve.md>), [hidden](<https://devfeed.tech/tags/hidden.md>), [hijack](<https://devfeed.tech/tags/hijack.md>), [http](<https://devfeed.tech/tags/http.md>), [iot-security](<https://devfeed.tech/tags/iot-security.md>), [literally](<https://devfeed.tech/tags/literally.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malicious-packages](<https://devfeed.tech/tags/malicious-packages.md>), [models](<https://devfeed.tech/tags/models.md>), [one](<https://devfeed.tech/tags/one.md>), [open-source-robots](<https://devfeed.tech/tags/open-source-robots.md>), [packages](<https://devfeed.tech/tags/packages.md>), [pollen-robotics](<https://devfeed.tech/tags/pollen-robotics.md>), [reachy-mini](<https://devfeed.tech/tags/reachy-mini.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [request](<https://devfeed.tech/tags/request.md>), [rise](<https://devfeed.tech/tags/rise.md>), [risks](<https://devfeed.tech/tags/risks.md>), [robot](<https://devfeed.tech/tags/robot.md>), [robotics](<https://devfeed.tech/tags/robotics.md>), [security](<https://devfeed.tech/tags/security.md>), [security-research](<https://devfeed.tech/tags/security-research.md>), [supply-chain-attack](<https://devfeed.tech/tags/supply-chain-attack.md>)

### AI overview

JFrog Security Research reports five CVEs in the Reachy Mini daemon and demonstrates network and browser-triggered attack chains that can install and execute malicious Python packages, escalate to persistent root, and control the robot. The daemon reportedly listens on all interfaces at port 8000 without authentication; wildcard CORS enables cross-origin requests, and a localhost-only setting does not restrict the server bind. A separate Bluetooth chain combines unauthenticated sound-file upload, shared PIN state, and path traversal to run an uploaded script as root. The article recommends updating to a fixed version (v1.11.0 or later), or temporarily firewalling port 8000, avoiding untrusted apps and browsing on a shared network, and tightening sudoers. It also calls for endpoint authentication, restricted CORS, rejecting local package installs, and network segmentation for fleets.

### Source excerpt

Software supply chain attacks are on the rise, and naturally taking the headlines. But with the rise of localized models and common software embedded into smart "things", risks may even be hidden in plain sight - or, in some cases, quite literally watching you. Vulnerabilities and malicious packages may extend risks to the unlikeliest of ...

## CVE-2026-62863 - MoLing: unauthenticated SSE and wildcard CORS expose tool sessions

DevFeed: [CVE-2026-62863 - MoLing: unauthenticated SSE and wildcard CORS expose tool sessions](<https://devfeed.tech/articles/cve-2026-62863-moling-unauthenticated-sse-and-wildcard-cors-expose-tool-sessions-109391.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-10-30T21:17:14Z

Content type: news

Language: en

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

Topics: [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [Server-sent events (SSE)](<https://devfeed.tech/topics/server-sent-events-sse.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [commands](<https://devfeed.tech/tags/commands.md>), [cors](<https://devfeed.tech/tags/cors.md>), [cve-2026-62863](<https://devfeed.tech/tags/cve-2026-62863.md>), [files](<https://devfeed.tech/tags/files.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [sse](<https://devfeed.tech/tags/sse.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Before MoLing 0.5.0, running the MCP server in SSE mode with `-l` leaves `/sse` and `/message` unauthenticated, while `mcp-go` allows any origin. A malicious page visited by someone using the server can open a cross-origin `EventSource`, read the `sessionId` from the `/sse` endpoint event, then send unauthorized tool calls to `/message`. Depending on configured tools, calls may read or write local files, execute commands, or take other actions. Loopback binding alone does not prevent this browser-mediated attack. The issue is stated to be fixed in version 0.5.0.

### Source excerpt

CVE ID :CVE-2026-62863 Published : Oct. 30, 2026, 9:17 p.m. | 37 minutes ago Description :MoLing is a computer-use and browser-use based MCP server. Prior to 0.5.0, when MoLing runs in SSE mode using `-l`, its `/sse` and `/message` HTTP endpoints do not authenticate requests and the `mcp-go` dependency sets `Access-Control-Allow-Origin: *`. A malicious web page can open a cross-origin `EventSource` to `/sse`, including a loopback listener, and read the `endpoint` event to obtain `sessionId`. After a victim running SSE mode visits that page, the attacker can use the disclosed `sessionId` against `/message` to send unauthorized MCP tool calls. Depending on the configured tools, those calls can read or write local files, execute commands or perform other actions. Binding only to loopback does not prevent this browser-mediated attack. This issue is fixed in version 0.5.0. Severity: 9.6 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## How to fix Webflow API CORS errors with a Webflow Cloud proxy route

DevFeed: [How to fix Webflow API CORS errors with a Webflow Cloud proxy route](<https://devfeed.tech/articles/how-to-fix-webflow-api-cors-errors-with-a-webflow-cloud-proxy-route-109583.md>)

Original publisher: [Read original article](<https://www.webflow.com/blog/fix-webflow-api-cors-errors>)

Author: Ismail Ajagbe

Published: 2026-10-30T00:00:00Z

Content type: tutorial

Language: en

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

Topics: [webflow](<https://devfeed.tech/topics/webflow.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [API](<https://devfeed.tech/topics/api.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [hosting](<https://devfeed.tech/topics/hosting.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [cors](<https://devfeed.tech/tags/cors.md>), [errors](<https://devfeed.tech/tags/errors.md>), [guides](<https://devfeed.tech/tags/guides.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [route](<https://devfeed.tech/tags/route.md>), [webflow](<https://devfeed.tech/tags/webflow.md>)

### AI overview

A Webflow Cloud Next.js Route Handler can fix browser CORS failures while keeping the Webflow API token out of public page code. The guide moves the request server-side, stores a replacement read-only token and fixed published-items URL in secret/runtime environment variables, and optionally allows specific calling origins. It recommends removing the exposed script and revoking its token, then serving only intended public content because an origin allowlist is not authentication and command-line clients can bypass it. The app must include Webflow Cloud's mount path in browser requests; the guide uses NEXT_PUBLIC_BASE_PATH for app code and a path in Webflow page scripts. It also notes that proxy requests count toward Webflow Cloud's allowance, while the upstream call does not; using api-cdn.webflow.com can serve published items from cache for up to 300 seconds.

### Source excerpt

Explore how to move your Webflow API token out of page code and into a Webflow Cloud proxy route.

## CVE-2026-61542 - Gearboy advisory / Gearsystem body: Unauthenticated network exposure of MCP HTTP tools

DevFeed: [CVE-2026-61542 - Gearboy advisory / Gearsystem body: Unauthenticated network exposure of MCP HTTP tools](<https://devfeed.tech/articles/cve-2026-61542-gearboy-advisory-gearsystem-body-unauthenticated-network-exposure-of-mcp-http-tools-105497.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-10-28T20:18:27Z

Content type: news

Language: en

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

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

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [bind](<https://devfeed.tech/tags/bind.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve-2026-61542](<https://devfeed.tech/tags/cve-2026-61542.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [files](<https://devfeed.tech/tags/files.md>), [http](<https://devfeed.tech/tags/http.md>), [localhost](<https://devfeed.tech/tags/localhost.md>), [loopback](<https://devfeed.tech/tags/loopback.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [media](<https://devfeed.tech/tags/media.md>), [network](<https://devfeed.tech/tags/network.md>), [optional](<https://devfeed.tech/tags/optional.md>), [patch](<https://devfeed.tech/tags/patch.md>), [peer](<https://devfeed.tech/tags/peer.md>), [port](<https://devfeed.tech/tags/port.md>)

### AI overview

The optional `--mcp-http` mode exposes MCP tools to reachable network peers: the described Gearsystem transport binds to `INADDR_ANY` (normally port 7777) and dispatches POSTs to `/mcp` without authorization or `Host`/`Origin` checks. A peer can initialize a session and invoke emulator and debugging operations; the advisory bounds the reported impact to the emulator process, debugging state, and local files accepted as media, with no host code execution demonstrated. A loopback-bind control blocked network access. Gearboy 3.8.7 contains a patch.

### Source excerpt

CVE ID :CVE-2026-61542 Published : Oct. 28, 2026, 8:18 p.m. | 59 minutes ago Description :Gearboy is a Game Boy, Game Boy Color, and Super Game Boy emulator and debugger with an embedded MCP server. Gearsystem, the affected component, has an optional `--mcp-http` mode that accepts unauthenticated MCP requests from any reachable network peer despite localhost-only documentation and logging. In the described `platforms/shared/desktop/mcp/mcp_transport.h` transport, the socket binds `INADDR_ANY`, normally on port 7777, and POST requests to `/mcp` reach dispatch without `Authorization`, `Host`, or `Origin` checks. Responses and OPTIONS advertise `Access-Control-Allow-Origin: *`. A peer can initialize an MCP session and invoke exposed emulator/debugging operations; even a garbage bearer token does not block dispatch, while a loopback-bind negative control prevents network access. The reported impact is bounded to the emulator process, debugging state, and local files accepted as media, rather than demonstrated host code execution. Gearboy 3.8.7 contains a patch. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-59179 - OpenHop: Path Traversal in Flow ID File Operations

DevFeed: [CVE-2026-59179 - OpenHop: Path Traversal in Flow ID File Operations](<https://devfeed.tech/articles/cve-2026-59179-openhop-path-traversal-in-flow-id-file-operations-104698.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-10-28T14:17:04Z

Content type: news

Language: en

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

Topics: [Authorization](<https://devfeed.tech/topics/authorization.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [CRUD](<https://devfeed.tech/topics/crud.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [api](<https://devfeed.tech/tags/api.md>), [browser](<https://devfeed.tech/tags/browser.md>), [can](<https://devfeed.tech/tags/can.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cors](<https://devfeed.tech/tags/cors.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-59179](<https://devfeed.tech/tags/cve-2026-59179.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [data](<https://devfeed.tech/tags/data.md>), [delete](<https://devfeed.tech/tags/delete.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [details](<https://devfeed.tech/tags/details.md>), [directory](<https://devfeed.tech/tags/directory.md>), [file](<https://devfeed.tech/tags/file.md>), [flow](<https://devfeed.tech/tags/flow.md>), [id](<https://devfeed.tech/tags/id.md>), [operations](<https://devfeed.tech/tags/operations.md>), [path-traversal](<https://devfeed.tech/tags/path-traversal.md>), [traversal](<https://devfeed.tech/tags/traversal.md>)

### AI overview

Before OpenHop 0.3.7, unauthenticated `GET /api/flows/:id` and `DELETE /api/flows/:id` requests pass decoded flow IDs to file-path construction without an allow-list. Path normalization can reach `.yaml` files outside the configured flow directory, allowing accessible files to be read as YAML-parsed JSON or permanently deleted. The description says permissive CORS can expose loopback-bound instances to malicious webpages, while Docker defaults to `HOST=0.0.0.0` and allows direct unauthenticated network access. The issue is fixed in repository release 0.3.7; the supplied text does not identify affected product versions.

### Source excerpt

CVE ID :CVE-2026-59179 Published : Oct. 28, 2026, 2:17 p.m. | 2 hours, 30 minutes ago Description :OpenHop is a tool for creating interactive data-flow diagrams. Prior to 0.3.7, `@openhop/server` passes unauthenticated flow route parameters from `GET /api/flows/:id` and `DELETE /api/flows/:id` in `packages/server/src/routes.ts` to `FlowStore.filePath()` in `packages/server/src/store.ts` without an identifier allow-list. The router applies `decodeURIComponent` to the id, and `path.join()` then normalizes traversal outside the configured flow directory after appending the .yaml extension. An attacker can read accessible YAML files as YAML-parsed JSON or permanently delete accessible .yaml files outside that directory, exposing configuration or secrets and disrupting dependent services. In `packages/server/src/index.ts`, CORS `origin: true` permits any browser origin, enabling a malicious webpage to target a loopback-bound instance. Docker deployments default to `HOST=0.0.0.0` and permit direct unauthenticated network access. This issue is fixed in repository release 0.3.7. Severity: 8.3 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## When POST Becomes GET: Investigating HTTP Method Interchangeability and Its Security Implications

DevFeed: [When POST Becomes GET: Investigating HTTP Method Interchangeability and Its Security Implications](<https://devfeed.tech/articles/when-post-becomes-get-investigating-http-method-interchangeability-and-its-security-implications-103383.md>)

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

Author: Matteo Golinelli, Seif Errahmane Hannachi, Bruno Crispo

Published: 2026-10-28T04: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>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [Cache](<https://devfeed.tech/topics/cache.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [also](<https://devfeed.tech/tags/also.md>), [applications](<https://devfeed.tech/tags/applications.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [automated](<https://devfeed.tech/tags/automated.md>), [avoid](<https://devfeed.tech/tags/avoid.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [body](<https://devfeed.tech/tags/body.md>), [browser](<https://devfeed.tech/tags/browser.md>), [but](<https://devfeed.tech/tags/but.md>), [cache](<https://devfeed.tech/tags/cache.md>), [can](<https://devfeed.tech/tags/can.md>), [cases](<https://devfeed.tech/tags/cases.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [csrf](<https://devfeed.tech/tags/csrf.md>), [csrf-token](<https://devfeed.tech/tags/csrf-token.md>), [http](<https://devfeed.tech/tags/http.md>), [post](<https://devfeed.tech/tags/post.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

MIDE detects HTTP method interchangeability by replaying browser-captured POST requests as GET requests with body parameters moved into the query string, then comparing responses against both the original POST and a no-query GET baseline. In an unauthenticated scan of the Tranco top 10k, it found high-confidence cases on 407 sites: 4.1% of all tested sites and 14.9% of those with replayed POSTs. Targeted checks found cases where invalid CSRF tokens were rejected on POST but accepted on equivalent GET requests; the study also observed Web Cache Deception conditions and cacheable GET responses. The findings show that method-scoped defenses may have gaps, though the experiment was unauthenticated and covers only the tested sites and captured requests.

### Source excerpt

arXiv:2610.37474v1 Announce Type: new Abstract: HTTP method semantics are a common boundary between safe retrieval and state-changing operations; however, deployed web applications do not always enforce this boundary consistently. In this paper, we study HTTP method interchangeability, a behavior where a POST request can be rewritten as a GET request to the same endpoint, with POST body parameters moved into the query string, while preserving an equivalent observed response. We present Method Interchange Detection Engine (MIDE), an automated pipeline that crawls web applications in a browser, records POST requests generated by page loads and user-interface interactions, converts supported POST bodies into GET candidates, and compares replayed responses with the original POST response. To avoid counting generic or parameter-independent responses as interchangeable, MIDE also sends a no-query GET baseline. We treat as high-confidence evidence of interchangeability only the cases where the converted GET matches the POST, while the baseline does not. We perform a large-scale unauthenticated experiment on the Tranco top 10k. We find high-confidence interchangeable requests on 407 of 10,000 tested sites (4.1%), 407 of 3,200 sites with captured POSTs (12.7%), and 407 of 2,734 sites with replayed POSTs (14.9%). A targeted Cross-Site Request Forgery (CSRF) token-replay check finds cases where invalid tokens are rejected for POST but accepted for the equivalent GET. We also observe Web Cache Deception (WCD) conditions and cacheable GET responses for interchangeable request instances. These results demonstrate that method interchangeability is observable in real web applications and can expose method-scoped defense gaps.

## CVE-2026-58497 - Uni-CLI: Legacy HTTP MCP transport accepted browser-originated localhost requests

DevFeed: [CVE-2026-58497 - Uni-CLI: Legacy HTTP MCP transport accepted browser-originated localhost requests](<https://devfeed.tech/articles/cve-2026-58497-uni-cli-legacy-http-mcp-transport-accepted-browser-originated-localhost-requests-98331.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-10-23T15:17:34Z

Content type: news

Language: en

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

Topics: [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>), [HTTP](<https://devfeed.tech/topics/http.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cors](<https://devfeed.tech/tags/cors.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-58497](<https://devfeed.tech/tags/cve-2026-58497.md>), [http](<https://devfeed.tech/tags/http.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [localhost](<https://devfeed.tech/tags/localhost.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [transport](<https://devfeed.tech/tags/transport.md>)

### AI overview

Before Uni-CLI 0.225.2, its legacy JSON-RPC-over-HTTP MCP transport accepted requests on loopback without checking browser Origin headers. A malicious webpage could send a simple POST to the local `/mcp` endpoint and, if the user had started the local MCP HTTP transport, invoke tools through the server. The Streamable HTTP transport already checked this browser-to-localhost boundary; the legacy stateless path did not. The issue is patched in 0.225.2 and does not change Uni-CLI's local-code-execution trust model.

### Source excerpt

CVE ID :CVE-2026-58497 Published : Oct. 23, 2026, 3:17 p.m. | 4 hours, 25 minutes ago Description :Uni-CLI gives people and agents one command interface for websites, browsers, desktop applications, local tools, and MCP. Prior to version 0.225.2, Uni-CLI exposed the legacy JSON-RPC-over-HTTP MCP transport on loopback without validating browser Origin headers before routing requests. A malicious web page could send a CORS simple POST request, such as text/plain, to the local /mcp endpoint and deliver a JSON-RPC body to the dispatcher. If the user had started the local MCP HTTP transport, that page could drive tools/call requests against the user's local Uni-CLI server. The Streamable HTTP transport already enforced this browser-to-localhost boundary. The legacy stateless HTTP path did not, so the two HTTP transports had drifted. This issue is about the browser-to-localhost boundary; it does not change Uni-CLI's local-code-execution trust model. This issue has been patched in version 0.225.2. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CORS Error Fix: Diagnose Console Errors and Configure Headers

DevFeed: [CORS Error Fix: Diagnose Console Errors and Configure Headers](<https://devfeed.tech/articles/cors-error-fix-diagnose-console-errors-and-configure-headers-93002.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/cors-error-fix-troubleshooting-playbook/>)

Author: SitePoint Team

Published: 2026-10-21T15:42:54Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

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

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [added](<https://devfeed.tech/tags/added.md>), [apply](<https://devfeed.tech/tags/apply.md>), [browser](<https://devfeed.tech/tags/browser.md>), [configure](<https://devfeed.tech/tags/configure.md>), [console](<https://devfeed.tech/tags/console.md>), [cors](<https://devfeed.tech/tags/cors.md>), [development](<https://devfeed.tech/tags/development.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [error](<https://devfeed.tech/tags/error.md>), [errors](<https://devfeed.tech/tags/errors.md>), [express](<https://devfeed.tech/tags/express.md>), [headers](<https://devfeed.tech/tags/headers.md>), [messages](<https://devfeed.tech/tags/messages.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [programming](<https://devfeed.tech/tags/programming.md>), [reading](<https://devfeed.tech/tags/reading.md>), [responses](<https://devfeed.tech/tags/responses.md>), [server](<https://devfeed.tech/tags/server.md>), [using](<https://devfeed.tech/tags/using.md>), [web](<https://devfeed.tech/tags/web.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

CORS errors can arise because the server omits required headers, mishandles an OPTIONS preflight, redirects the preflight, or combines wildcard origins with credentialed requests. The excerpt recommends reading the browser console message, reproducing preflight with curl, and matching the response to the cause. During development, a Vite proxy makes API calls appear same-origin, but it does not replace production CORS configuration. For production, it gives examples for Express, Next.js and Nginx that use explicit origin allowlists, handle OPTIONS, and return appropriate headers; Express middleware handles preflights at app level, while Next.js examples define an OPTIONS handler or middleware. It cautions against reflecting unvalidated origins, using `*` with credentials, Nginx header inheritance pitfalls, and setting CORS headers in both the application and proxy. Verify headers on both preflight and actual responses.

### Source excerpt

Diagnose browser CORS errors from console messages and preflight responses, then apply secure fixes using development proxies or server-side headers in Express, Next.js, and Nginx. Continue reading CORS Error Fix: Diagnose Console Errors and Configure Headers on SitePoint.

## Express React Refresh Token Setup: Diagnosing Missing Cookies and 401s

DevFeed: [Express React Refresh Token Setup: Diagnosing Missing Cookies and 401s](<https://devfeed.tech/articles/express-react-refresh-token-setup-diagnosing-missing-cookies-and-401s-84084.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/express-react-refresh-token-cookie-diagnosis/>)

Author: SitePoint Team

Published: 2026-10-09T15:45:24Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Express](<https://devfeed.tech/topics/express.md>), [React](<https://devfeed.tech/topics/react.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [async](<https://devfeed.tech/tags/async.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [axios](<https://devfeed.tech/tags/axios.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [cors](<https://devfeed.tech/tags/cors.md>), [express](<https://devfeed.tech/tags/express.md>), [http](<https://devfeed.tech/tags/http.md>), [implement](<https://devfeed.tech/tags/implement.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [programming](<https://devfeed.tech/tags/programming.md>), [react](<https://devfeed.tech/tags/react.md>), [retry](<https://devfeed.tech/tags/retry.md>), [rotation](<https://devfeed.tech/tags/rotation.md>), [token](<https://devfeed.tech/tags/token.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

This tutorial explains how to diagnose missing HTTP-only refresh cookies in an Express 5 and React application. It covers credentialed requests, CORS and cookie settings, token rotation, and a single-flight retry guard for concurrent 401 responses. It also describes production hardening, including refresh-token reuse detection.

### Source excerpt

Fix missing HTTP-only refresh cookies in Express 5 and React, configure CORS and cookie options, and implement silent token rotation with single-flight retry on 401s. Continue reading Express React Refresh Token Setup: Diagnosing Missing Cookies and 401s on SitePoint.

## Secure Cookies with SameSite: Lax, Strict, and Cross-Site Rules

DevFeed: [Secure Cookies with SameSite: Lax, Strict, and Cross-Site Rules](<https://devfeed.tech/articles/secure-cookies-with-samesite-lax-strict-and-cross-site-rules-77565.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/secure-cookies-samesite-reference/>)

Author: SitePoint Team

Published: 2026-10-08T22:00:57Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Application Security](<https://devfeed.tech/topics/application-security.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [XSS](<https://devfeed.tech/topics/xss.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [applications](<https://devfeed.tech/tags/applications.md>), [article](<https://devfeed.tech/tags/article.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [axios](<https://devfeed.tech/tags/axios.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [copy](<https://devfeed.tech/tags/copy.md>), [django](<https://devfeed.tech/tags/django.md>), [express](<https://devfeed.tech/tags/express.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [none](<https://devfeed.tech/tags/none.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [programming](<https://devfeed.tech/tags/programming.md>), [rules](<https://devfeed.tech/tags/rules.md>), [web](<https://devfeed.tech/tags/web.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

A technical reference explains how SameSite cookie settings interact with Secure and HttpOnly flags, browser behavior, and cross-site requests. It provides recommendations and implementation examples for Express, Next.js, and Django, plus a checklist for debugging cookie issues.

### Source excerpt

A technical reference on configuring SameSite cookie attributes (Strict, Lax, None) alongside Secure and HttpOnly flags, with implementation patterns for Express, Next.js, and Django. Continue reading Secure Cookies with SameSite: Lax, Strict, and Cross-Site Rules on SitePoint.

## Ship a React SPA with AuthKit to production

DevFeed: [Ship a React SPA with AuthKit to production](<https://devfeed.tech/articles/ship-a-react-spa-with-authkit-to-production-77383.md>)

Original publisher: [Read original article](<https://workos.com/blog/react-spa-authkit-production>)

Author: WorkOS

Published: 2026-10-08T00:00:00Z

Content type: tutorial

Language: en

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

Topics: [React](<https://devfeed.tech/topics/react.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [password reset](<https://devfeed.tech/topics/password-reset.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cors](<https://devfeed.tech/tags/cors.md>), [csrf](<https://devfeed.tech/tags/csrf.md>), [custom-domain](<https://devfeed.tech/tags/custom-domain.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [development](<https://devfeed.tech/tags/development.md>), [react](<https://devfeed.tech/tags/react.md>), [vite](<https://devfeed.tech/tags/vite.md>)

### AI overview

A hands-on guide to taking a Vite and React single-page app from local development to production with WorkOS AuthKit. It covers sign-in setup, refresh-token storage in httpOnly cookies, custom authentication domains, preview deployments, and server-side verification of access tokens in a Node API.

### Source excerpt

Take a Vite and React app from localhost to production with httpOnly cookie refresh, a custom Authentication API domain, preview deployments, and a Node API that verifies every request.

## Testing an iframe's postMessage Handler

DevFeed: [Testing an iframe's postMessage Handler](<https://devfeed.tech/articles/testing-an-iframe-s-postmessage-handler-66720.md>)

Original publisher: [Read original article](<https://blog.master.dev/testing-an-iframes-postmessage-handler/>)

Author: Keshav Malik

Published: 2026-10-07T15:23:18Z

Content type: tutorial

Language: en

Sources: [Master.dev Blog RSS Feed](<https://devfeed.tech/sources/master-dev-blog-rss-feed.md>)

Topics: [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [XSS](<https://devfeed.tech/topics/xss.md>), [Single-page application (SPA)](<https://devfeed.tech/topics/spa.md>)

Tags: [blog-post](<https://devfeed.tech/tags/blog-post.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cross-site-scripting](<https://devfeed.tech/tags/cross-site-scripting.md>), [iframe](<https://devfeed.tech/tags/iframe.md>), [iframes](<https://devfeed.tech/tags/iframes.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [postmessage](<https://devfeed.tech/tags/postmessage.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>)

### AI overview

A tutorial demonstrates how to secure an iframe widget's postMessage handler. It checks the sender's exact origin and window, validates the message shape and height, clamps resize values, and uses a specific target origin when sending messages. The article also explains how wildcard target origins and missing rate limits can create security and reliability risks.

### Source excerpt

There are some real complexities using iframes and the postMessage API for communication between a widget and its parent. Security vulnerabilities like cross-origin scripting risks being one.

## How to add Webflow autocomplete based on an external database

DevFeed: [How to add Webflow autocomplete based on an external database](<https://devfeed.tech/articles/how-to-add-webflow-autocomplete-based-on-an-external-database-59990.md>)

Original publisher: [Read original article](<https://webflowmarketingmain.com/blog/webflow-autocomplete-external-database>)

Author: Ismail Ajagbe

Published: 2026-09-25T00:00:00Z

Content type: tutorial

Language: en

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

Topics: [webflow](<https://devfeed.tech/topics/webflow.md>), [autocomplete](<https://devfeed.tech/topics/autocomplete.md>), [Database](<https://devfeed.tech/topics/database.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [API](<https://devfeed.tech/topics/api.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [autocomplete](<https://devfeed.tech/tags/autocomplete.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [database](<https://devfeed.tech/tags/database.md>), [guides](<https://devfeed.tech/tags/guides.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [http](<https://devfeed.tech/tags/http.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [webflow](<https://devfeed.tech/tags/webflow.md>)

### AI overview

A tutorial for building a Webflow lookup field that provides autocomplete suggestions from an external database. It uses a Next.js Route Handler on Webflow Cloud, a same-origin fetch from the page, and an environment variable to keep the database token out of client-side code.

### Source excerpt

Learn how to build a Webflow lookup field that pulls suggestions from your external database through a Route Handler on Webflow Cloud.

## Adding custom domains to AWS Lambda MicroVMs with Application Load Balancer

DevFeed: [Adding custom domains to AWS Lambda MicroVMs with Application Load Balancer](<https://devfeed.tech/articles/adding-custom-domains-to-aws-lambda-microvms-with-application-load-balancer-58218.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/adding-custom-domains-to-aws-lambda-microvms-with-application-load-balancer/>)

Author: Frank Scarfo

Published: 2026-09-22T16:48:32Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [nginx](<https://devfeed.tech/topics/nginx.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Machine Learning](<https://devfeed.tech/topics/amazon-machine-learning.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cors](<https://devfeed.tech/tags/cors.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [development](<https://devfeed.tech/tags/development.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [networking](<https://devfeed.tech/tags/networking.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial presents a reusable networking pattern for exposing AWS Lambda MicroVMs through custom domains while supporting browser CORS without changing the MicroVM application. It uses an Application Load Balancer for TLS termination, host-header rewriting, CORS handling, and private forwarding over AWS PrivateLink, with deployment through the AWS CDK.

### Source excerpt

Many teams want to expose their AWS Lambda MicroVMs under a custom domain they own, and satisfy CORS for browser clients, without changing the application. This post shows how, using an Application Load Balancer that rewrites the Host header and forwards over AWS PrivateLink, deployed with the AWS CDK.

## Introducing Worker Previews: isolated preview environments for every change your agent makes

DevFeed: [Introducing Worker Previews: isolated preview environments for every change your agent makes](<https://devfeed.tech/articles/introducing-worker-previews-isolated-preview-environments-for-every-change-your-agent-makes-57828.md>)

Original publisher: [Read original article](<https://blog.cloudflare.com/worker-previews/>)

Author: Nanda Syahrasyad

Published: 2026-09-22T13:00:00Z

Content type: release

Language: en

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

Topics: [Deployment](<https://devfeed.tech/topics/deployment.md>), [staging](<https://devfeed.tech/topics/staging.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [observability](<https://devfeed.tech/topics/observability.md>), [test](<https://devfeed.tech/topics/test.md>), [Git](<https://devfeed.tech/topics/git.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [API](<https://devfeed.tech/topics/api.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [branch](<https://devfeed.tech/tags/branch.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cors](<https://devfeed.tech/tags/cors.md>), [database](<https://devfeed.tech/tags/database.md>), [developers](<https://devfeed.tech/tags/developers.md>), [environments](<https://devfeed.tech/tags/environments.md>), [git](<https://devfeed.tech/tags/git.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [observability](<https://devfeed.tech/tags/observability.md>), [preview](<https://devfeed.tech/tags/preview.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [production](<https://devfeed.tech/tags/production.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [test](<https://devfeed.tech/tags/test.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

Cloudflare introduces Worker Previews, giving every Git branch an isolated, production-like environment with its own code, configuration, URL, observability, and state. The release is designed to let developers and agents test changes, inspect behavior, and verify fixes before production deployment.

### Source excerpt

Worker Previews gives every branch its own URL, configuration, state, and observability, so you and your agents can test changes in parallel without affecting production.

## A Nix store is three functions

DevFeed: [A Nix store is three functions](<https://devfeed.tech/articles/a-nix-store-is-three-functions-54772.md>)

Original publisher: [Read original article](<https://fzakaria.com/2026/09/11/a-nix-store-is-three-functions>)

Published: 2026-09-12T03:00:00Z

Content type: article

Language: en

Sources: [Farid Zakaria's Blog](<https://devfeed.tech/sources/farid-zakaria-s-blog.md>)

Topics: [Nix](<https://devfeed.tech/topics/nix.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [GitHub Pages](<https://devfeed.tech/topics/github-pages.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Git](<https://devfeed.tech/topics/git.md>)

Tags: [cors](<https://devfeed.tech/tags/cors.md>), [git](<https://devfeed.tech/tags/git.md>), [github-pages](<https://devfeed.tech/tags/github-pages.md>), [http](<https://devfeed.tech/tags/http.md>), [nix](<https://devfeed.tech/tags/nix.md>)

### AI overview

The article explains that a Nix binary cache can be implemented with three functions and that the underlying storage medium, protocol, and domain can vary. It discusses using GitHub Pages and other static file servers as Nix stores, with signatures and content-addressed archives providing transport independence.

### Source excerpt

While building trynix I needed somewhere to host a store-path that did not exist on cache.nixos.org.1 I wanted to demonstrate that non-Nixpkgs store paths could be booted just as easily. I was also waiting for @domenkozar to enable CORS on cache.nixos.org so I could use it. ↩

## Fetch Metadata request headers

DevFeed: [Fetch Metadata request headers](<https://devfeed.tech/articles/fetch-metadata-request-headers-89172.md>)

Original publisher: [Read original article](<https://specification.website/spec/security/fetch-metadata/>)

Author: Joost de Valk

Published: 2026-09-10T00:00:00Z

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

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

Tags: [application-security](<https://devfeed.tech/tags/application-security.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cors](<https://devfeed.tech/tags/cors.md>), [csrf](<https://devfeed.tech/tags/csrf.md>), [headers](<https://devfeed.tech/tags/headers.md>), [recommended](<https://devfeed.tech/tags/recommended.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Fetch Metadata headers let servers identify the context of browser requests and reject unwanted cross-site requests. The tutorial recommends applying a resource isolation policy in middleware, allowing ordinary inbound links, retaining existing CSRF and authentication checks, and varying cacheable responses on the request headers used by the policy.

### Source excerpt

Read Sec-Fetch-Site, Sec-Fetch-Mode and Sec-Fetch-Dest to reject unwanted cross-site browser requests before a handler runs. Keep ordinary inbound links working and retain other CSRF defences.

## How We Migrated a Production Cluster from Ingress NGINX to Gateway API

DevFeed: [How We Migrated a Production Cluster from Ingress NGINX to Gateway API](<https://devfeed.tech/articles/how-we-migrated-a-production-cluster-from-ingress-nginx-to-gateway-api-51165.md>)

Original publisher: [Read original article](<https://www.fairwinds.com/blog/migrated-production-cluster-from-ingress-nginx-to-gateway-api>)

Author: Husne Ozmen

Published: 2026-07-01T17:08:57Z

Content type: tutorial

Language: en

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

Topics: [ingress-nginx](<https://devfeed.tech/topics/ingress-nginx.md>), [gateway](<https://devfeed.tech/topics/gateway.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Network](<https://devfeed.tech/topics/network.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [Firewall](<https://devfeed.tech/topics/firewall.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>)

Tags: [cors](<https://devfeed.tech/tags/cors.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [how-to-kube](<https://devfeed.tech/tags/how-to-kube.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [ingress](<https://devfeed.tech/tags/ingress.md>), [ingress-nginx](<https://devfeed.tech/tags/ingress-nginx.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [migration](<https://devfeed.tech/tags/migration.md>), [production](<https://devfeed.tech/tags/production.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>)

### AI overview

A practical account of migrating a production Kubernetes cluster from ingress-nginx to Gateway API under real traffic. It explains Gateway API's resource ownership and typed validation, discusses weighted routing, and describes selecting kgateway based on requirements including CORS, WAF support, and ExternalName replacement.

### Source excerpt

Back in January, we published a post about the retirement of ingress-nginx and laid out what that means for teams still running it. We also gave a CNCF CloudNative Live talk a couple of years ago that walked through the case for Gateway API.

## Reporting API (Reporting-Endpoints)

DevFeed: [Reporting API (Reporting-Endpoints)](<https://devfeed.tech/articles/reporting-api-reporting-endpoints-89179.md>)

Original publisher: [Read original article](<https://specification.website/spec/security/reporting-endpoints/>)

Author: Joost de Valk

Published: 2026-06-16T00:00:00Z

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

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

Tags: [api](<https://devfeed.tech/tags/api.md>), [browser](<https://devfeed.tech/tags/browser.md>), [csp](<https://devfeed.tech/tags/csp.md>), [header](<https://devfeed.tech/tags/header.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [recommended](<https://devfeed.tech/tags/recommended.md>), [reports](<https://devfeed.tech/tags/reports.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The Reporting API uses the Reporting-Endpoints response header to direct browser-generated JSON reports to named endpoints. These reports can surface CSP, cross-origin isolation, and Permissions-Policy problems, as well as API deprecations, browser interventions, and crashes. The tutorial explains how to configure endpoints, collect reports, test report-only policies, and avoid common setup mistakes.

### Source excerpt

A response header that names HTTP endpoints to which the browser POSTs structured violation reports -- CSP and COOP breaches, permissions-policy violations, deprecations, interventions, and crashes -- so you learn what is breaking in the field.

[Next page](<https://devfeed.tech/topics/cors.md?cursor=WyIyMDI2LTA2LTE2VDAwOjAwOjAwKzAwOjAwIiwgImNlNjVhMjg4LTZkMjQtNGU0Zi1iYmQ2LTYxMDQwNDBiMmIyZSJd>)