# REST API

REST API is an application programming interface that follows the REST architectural style for communication and information exchange between computer systems.

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

## Best API Catalogs and Registries for AI Agents

DevFeed: [Best API Catalogs and Registries for AI Agents](<https://devfeed.tech/articles/best-api-catalogs-and-registries-for-ai-agents-146946.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/best-api-catalogs-registries-agents>)

Author: Swytchcode Team

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

Content type: comparison

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>), [Postman](<https://devfeed.tech/topics/postman.md>), [Swagger](<https://devfeed.tech/topics/swagger.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [api-catalog](<https://devfeed.tech/tags/api-catalog.md>), [api-governance](<https://devfeed.tech/tags/api-governance.md>), [api-management](<https://devfeed.tech/tags/api-management.md>), [api-testing](<https://devfeed.tech/tags/api-testing.md>), [apps](<https://devfeed.tech/tags/apps.md>), [arcade](<https://devfeed.tech/tags/arcade.md>), [backstage](<https://devfeed.tech/tags/backstage.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [postman](<https://devfeed.tech/tags/postman.md>), [registries](<https://devfeed.tech/tags/registries.md>), [schema](<https://devfeed.tech/tags/schema.md>)

### AI overview

The comparison centers on whether an API catalog checks schemas against live providers when an agent calls a method. Backstage stores manually maintained YAML entities; Postman's Catalog surfaces governance and validation but describes no live endpoint polling; Stoplight lints specs during design; Composio, Arcade, Pipedream, and Zapier MCP offer broad agent tool catalogs, but their cited docs do not describe call-time schema drift checks. Swagger Catalog is presented as aiming to validate in real time, though its implementation could not be verified from public pages and it was still rolling out at the time checked. The excerpt says Swytchcode validates each execution against the real API and records audit results, while cautioning that semantic discovery can select the wrong provider unless scoped. It also says Swytchcode lacks hosted end-user SaaS connection screens, making Composio or Arcade faster for that use case. Catalog size, authorization, design-time governance, and call-time freshness address different needs.

### Source excerpt

We rank Backstage, Postman, Stoplight, SwaggerHub and the agent-native catalogs on one question: does the schema stay current at call time?

## Best Tools for Multi-Tenant API Credentials

DevFeed: [Best Tools for Multi-Tenant API Credentials](<https://devfeed.tech/articles/best-tools-for-multi-tenant-api-credentials-146954.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/best-multi-tenant-credential-tools>)

Author: Swytchcode Team

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

Content type: comparison

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [best](<https://devfeed.tech/tags/best.md>), [call](<https://devfeed.tech/tags/call.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [customer](<https://devfeed.tech/tags/customer.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [multi-tenant](<https://devfeed.tech/tags/multi-tenant.md>), [risk](<https://devfeed.tech/tags/risk.md>), [tenant](<https://devfeed.tech/tags/tenant.md>), [token](<https://devfeed.tech/tags/token.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

The key risk in multi-tenant agents is a valid API call using the wrong customer's token. Nango, WorkOS Pipes, and Auth0 Token Vault enforce tenant boundaries through storage or tenant context; Composio and Arcade require each call to identify the acting user, so isolation depends on the calling code or identity-provider check. Paragon/ActionKit ties pricing to connected users, while Arcade charges per auth event and tool call. Swytchcode selects credentials per tenant at execution time, runs on customer-controlled infrastructure, and adds policy checks, safe retries, validation, and audit records, but does not host an end-user OAuth connection screen. The excerpt frames Swytchcode as an execution layer that can complement a separate connection product.

### Source excerpt

The real risk in multi-tenant agents is a correct-looking call that runs against the wrong customer's token. Here's who actually stops that.

## CVE-2026-63189 - Dialoqbase: Unauthenticated path traversal in GET /api/v1/view/\* leads to arbitrary file read and full application takeover

DevFeed: [CVE-2026-63189 - Dialoqbase: Unauthenticated path traversal in GET /api/v1/view/\* leads to arbitrary file read and full application takeover](<https://devfeed.tech/articles/cve-2026-63189-dialoqbase-unauthenticated-path-traversal-in-get-api-v1-view-leads-to-arbitrary-file-read-and-full-application-takeover-140830.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-18T16:18:16Z

Content type: news

Language: en

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

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [file](<https://devfeed.tech/topics/file.md>), [API](<https://devfeed.tech/topics/api.md>), [.env](<https://devfeed.tech/topics/dotenv.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [bots](<https://devfeed.tech/tags/bots.md>), [chatbots](<https://devfeed.tech/tags/chatbots.md>), [conversations](<https://devfeed.tech/tags/conversations.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-63189](<https://devfeed.tech/tags/cve-2026-63189.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [dialoqbase](<https://devfeed.tech/tags/dialoqbase.md>), [directory](<https://devfeed.tech/tags/directory.md>), [file](<https://devfeed.tech/tags/file.md>), [full](<https://devfeed.tech/tags/full.md>), [n4ze3m](<https://devfeed.tech/tags/n4ze3m.md>), [path-traversal](<https://devfeed.tech/tags/path-traversal.md>), [published](<https://devfeed.tech/tags/published.md>), [traversal](<https://devfeed.tech/tags/traversal.md>), [v1](<https://devfeed.tech/tags/v1.md>), [view](<https://devfeed.tech/tags/view.md>)

### AI overview

Before Dialoqbase 1.11.5, an unauthenticated GET /api/v1/view/* request can use path traversal to read server files outside the uploads directory. If environment files expose DB_SECRET_KEY, an attacker can forge administrator JWTs and take over bots, conversations, integrations, and stored third-party credentials. The issue is fixed in version 1.11.5.

### Source excerpt

CVE ID :CVE-2026-63189 Published : Nov. 18, 2026, 4:18 p.m. | 15 minutes ago Description :Dialoqbase is an application for creating chatbots. Prior to 1.11.5, the unauthenticated GET /api/v1/view/* route in server/src/routes/api/v1/view/root.ts resolves its attacker-controlled wildcard path without normalization or containment, allowing traversal outside the intended uploads directory and arbitrary server file reads. Reading environment files can disclose DB_SECRET_KEY, the application's JWT signing key, which permits forged administrator tokens and takeover of bots, conversations, integrations, and stored third-party credentials. This issue is fixed in version 1.11.5. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Securing REST APIs with JWT authorizers in Amazon API Gateway

DevFeed: [Securing REST APIs with JWT authorizers in Amazon API Gateway](<https://devfeed.tech/articles/securing-rest-apis-with-jwt-authorizers-in-amazon-api-gateway-139433.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/securing-rest-apis-with-jwt-authorizers-in-amazon-api-gateway/>)

Author: Giedrius Praspaliauskas

Published: 2026-11-17T18:39:16Z

Content type: tutorial

Language: en

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

Topics: [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [authorizer](<https://devfeed.tech/tags/authorizer.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [scopes](<https://devfeed.tech/tags/scopes.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Amazon API Gateway REST API JWT authorizers validate OIDC tokens in the request path without a Lambda invocation. Configure trusted issuers, audiences, signing algorithms and optional claim rules; API Gateway checks signatures, expiry, not-before time and method scopes, then passes validated claims to the integration. The walkthrough applies separate `orders:read` and `orders:write` scopes to GET and POST methods and adds a Cognito user pool as a second issuer. Missing, malformed, expired or untrusted tokens receive 401; valid tokens failing scope or claim checks receive 403. Lambda authorizers remain useful for custom logic, token introspection or non-JWT credentials. Limits include 1-10 issuers, cached signing keys, no revocation checks, and public issuer URLs. Scope checks use `scope` or `scp`; the article notes Entra ID client-credentials permissions in `roles` require a dedicated audience per caller or a Lambda authorizer for role checks.

### Source excerpt

Amazon API Gateway REST APIs now support JWT authorizers, which validate tokens from any OIDC-compatible identity provider in API Gateway itself, with no Lambda authorizer required. Learn how JWT authorizers work, then build a REST API that accepts machine-to-machine tokens with per-method scopes and adds an Amazon Cognito user pool as a second issuer.

## Apache Polaris Catalog Federation: Iceberg REST, Hive, and Hadoop

DevFeed: [Apache Polaris Catalog Federation: Iceberg REST, Hive, and Hadoop](<https://devfeed.tech/articles/apache-polaris-catalog-federation-iceberg-rest-hive-and-hadoop-138580.md>)

Original publisher: [Read original article](<https://www.dremio.com/blog/apache-polaris-catalog-federation-iceberg-rest-hive-and-hadoop/>)

Author: Alex Merced

Published: 2026-11-17T15:23:33Z

Content type: tutorial

Language: en

Sources: [Dremio](<https://devfeed.tech/sources/dremio.md>)

Topics: [Hadoop](<https://devfeed.tech/topics/hadoop.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-polaris](<https://devfeed.tech/tags/apache-polaris.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [configure](<https://devfeed.tech/tags/configure.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [dremio-blog-open-data-insights](<https://devfeed.tech/tags/dremio-blog-open-data-insights.md>), [hadoop](<https://devfeed.tech/tags/hadoop.md>), [hive](<https://devfeed.tech/tags/hive.md>), [iceberg](<https://devfeed.tech/tags/iceberg.md>), [rest](<https://devfeed.tech/tags/rest.md>)

### AI overview

Apache Polaris 1.9.0 federation provides a unified REST and governance layer over Iceberg REST, Hive metastore, and Hadoop catalogs while leaving remote metadata authoritative. Federation is disabled by default and must be enabled and configured; Polaris forwards metadata calls and enforces RBAC. Subcatalog-level controls require explicitly enabled synthetic Polaris entities and validation. Connection requirements differ: Iceberg REST authentication depends on the endpoint, Hive uses configured client properties, and Hadoop uses the Polaris process identity for object-store access and has layout and namespace-property limits. The guide recommends using only documented connection properties, keeping secrets out of them, checking credential vending, cache TTL and invalidation behavior, and testing RBAC, remote outages, metadata changes, and rollback before staged production rollout. Cached results may remain available during outages or stale until expiry; exact error behavior for Hive and Hadoop depends on client versions. The guidance is specific to Polaris 1.9.0 and says to verify behavior against version-specific documentation.

### Source excerpt

Configure Apache Polaris catalog federation for Iceberg REST, Hive, and Hadoop catalogs with authentication, credential vending, RBAC, and safe rollout tests. The post Apache Polaris Catalog Federation: Iceberg REST, Hive, and Hadoop appeared first on Dremio.

## Serving Scikit-LLM Pipelines as REST APIs with FastAPI

DevFeed: [Serving Scikit-LLM Pipelines as REST APIs with FastAPI](<https://devfeed.tech/articles/serving-scikit-llm-pipelines-as-rest-apis-with-fastapi-135526.md>)

Original publisher: [Read original article](<https://machinelearningmastery.com/serving-scikit-llm-pipelines-as-rest-apis-with-fastapi/>)

Author: Iván Palomares Carrascosa

Published: 2026-11-16T11:00:00Z

Content type: tutorial

Language: en

Sources: [MachineLearningMastery.com](<https://devfeed.tech/sources/machinelearningmastery-com.md>)

Topics: [FastAPI](<https://devfeed.tech/topics/fastapi.md>), [text-classification](<https://devfeed.tech/topics/text-classification.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Ollama](<https://devfeed.tech/topics/ollama.md>), [scikit-learn](<https://devfeed.tech/topics/scikit-learn.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [classification](<https://devfeed.tech/tags/classification.md>), [fastapi](<https://devfeed.tech/tags/fastapi.md>), [language-models](<https://devfeed.tech/tags/language-models.md>), [llm](<https://devfeed.tech/tags/llm.md>), [local](<https://devfeed.tech/tags/local.md>), [ollama](<https://devfeed.tech/tags/ollama.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [rest-apis](<https://devfeed.tech/tags/rest-apis.md>), [serve](<https://devfeed.tech/tags/serve.md>), [serving](<https://devfeed.tech/tags/serving.md>), [text](<https://devfeed.tech/tags/text.md>), [text-classification](<https://devfeed.tech/tags/text-classification.md>), [zero-shot](<https://devfeed.tech/tags/zero-shot.md>)

### AI overview

The excerpt describes serving a Scikit-LLM zero-shot text classifier locally through FastAPI and Ollama. It configures a local Ollama model, builds a classifier with scikit-learn's fit/predict pattern, serializes it to a joblib file, then loads it in an asynchronous FastAPI app with a /predict endpoint that can accept multiple texts. The app is run with uvicorn and tested through FastAPI's interactive docs at /docs. The label set supplied during fit defines the only categories the classifier can return; the LLM's weights are not updated, so inputs are mapped into that closed set. The excerpt presents this as a simple one-stage pipeline and notes that Scikit-LLM can support larger pipelines with preprocessing.

### Source excerpt

In this article, you will learn how to serve a Scikit-LLM zero-shot text classification pipeline, powered by a local Ollama model, as a REST API...

## AI made integrations the vendor's problem

DevFeed: [AI made integrations the vendor's problem](<https://devfeed.tech/articles/ai-made-integrations-the-vendor-s-problem-135988.md>)

Original publisher: [Read original article](<https://blog.n8n.io/ai-made-integrations-the-vendors-problem/>)

Author: Andrew Green

Published: 2026-11-16T10:17:32Z

Content type: article

Language: en

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

Topics: [API Economy](<https://devfeed.tech/topics/api-economy.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [n8n](<https://devfeed.tech/topics/n8n.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-sdk](<https://devfeed.tech/tags/agent-sdk.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent-development](<https://devfeed.tech/tags/ai-agent-development.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [audit](<https://devfeed.tech/tags/audit.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bash](<https://devfeed.tech/tags/bash.md>), [behavioral-analysis](<https://devfeed.tech/tags/behavioral-analysis.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-agent-sdk](<https://devfeed.tech/tags/claude-agent-sdk.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-code-hooks](<https://devfeed.tech/tags/claude-code-hooks.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>)

### AI overview

The excerpt argues that agent integrations have shifted some work from API consumers to providers, while leaving application developers responsible for choosing and composing integration methods. MCP standardizes access to tools, resources, and prompts, but providers must maintain servers and handle discovery, transport security, and protocol changes; skills can supply workflow guidance beyond schemas. Other discussed paths include updated APIs and security standards, deterministic hooks for policy checks and auditing, and SDK-defined tools and subagents, which place tool selection and composition in application code. The author expects providers to support a mix of MCP, APIs, hooks, and SDKs, with simpler APIs remaining useful for some calls.

### Source excerpt

In the second iteration of the AI Agent Development Tools report, I replaced the integrability axis with enterprise-readiness. I wanted this to signify the departure from 2020-style IPaaS. With MCP getting traction to the point where every vendor offers an MCP server, I said the integration burden now

## Kotlin Multiplatform Networking with Native Android and iOS ViewModels

DevFeed: [Kotlin Multiplatform Networking with Native Android and iOS ViewModels](<https://devfeed.tech/articles/kotlin-multiplatform-networking-with-native-android-and-ios-viewmodels-134271.md>)

Original publisher: [Read original article](<https://proandroiddev.com/kmp-networking-native-viewmodels-cf6fb357b012?source=rss----c72404660798---4>)

Author: Ravi Rawal

Published: 2026-11-14T14:49:33Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Ktor](<https://devfeed.tech/topics/ktor.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [coroutine-testing](<https://devfeed.tech/topics/coroutine-testing.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [cancellation](<https://devfeed.tech/tags/cancellation.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [coroutine](<https://devfeed.tech/tags/coroutine.md>), [domain](<https://devfeed.tech/tags/domain.md>), [error](<https://devfeed.tech/tags/error.md>), [http](<https://devfeed.tech/tags/http.md>), [http-client](<https://devfeed.tech/tags/http-client.md>), [ios](<https://devfeed.tech/tags/ios.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [native](<https://devfeed.tech/tags/native.md>), [networking](<https://devfeed.tech/tags/networking.md>), [published](<https://devfeed.tech/tags/published.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>)

### AI overview

The article recommends sharing Ktor networking, serialization, repositories, domain models, and meaningful use cases in Kotlin Multiplatform while Android and iOS retain native ViewModels and presentation state. Callers own coroutine or task lifecycles: Android can launch through `viewModelScope`; iOS can bridge Kotlin suspend functions to Swift `async`/`await` with KMP-NativeCoroutines or SKIE and cancel its Swift `Task`. Ktor requests are suspending and need no automatic dispatcher switch when they are main-safe; truly blocking or CPU-heavy work should use an appropriate injected dispatcher. Preserve cancellation, reuse the HTTP client, and keep DTO-to-domain and domain-to-UI mapping at their respective boundaries. The article notes that Swift interop adds generated types and conversions, and shared unit tests do not verify platform HTTP engines or the Kotlin-to-Swift bridge.

### Source excerpt

Share Ktor networking, repositories, and use cases while Android and iOS keep control of their native ViewModels, UI state, threading, and cancellation. Kotlin Multiplatform allows us to share networking and business logic between Android and iOS. When an API call is made from the shared Kotlin module to the native app there are a number of things we need to make a decision on. Who creates the coroutine? Who handles where the work is executed? Will the ViewModel be the same for Android and iOS? How do we get the use cases from the shared module onto each platform? The decisions here are more important than the actual HTTP client. A good KMP architecture will not have all the layers shared between both platforms. We can leave the repositories and use cases in Kotlin, have Android use its Jetpack ViewModels and iOS use SwiftUI with its native Swift ViewModels. Both platforms will call the same business functions but each will have control over their own presentation lifecycle. It's important to make sure the work that needs to be consistent is shared. Let's look at how we can create this architecture using a simple example of fetching articles from a REST API. 1. Decide what belongs in shared code Lets start with two native applications and one shared KMP module. The Android and iOS applications will not need or have identical ViewModels. But they should access to the same business operation. The shared module can own: HTTP client configuration and API requests. DTOs and serialization. Repository implementations and data-to-domain mapping. Use cases that represent application operations. Shared validation, business rules, and error classification. Android can use using Jetpack ViewModel, viewModelScope, and StateFlow. iOS may use SwiftUI, ObservableObject, @Published, and Swift concurrency. This is one of the architecture options described in the Kotlin Multiplatform ViewModel documentation: sharing the repository and data layers while keeping platform-specific ViewMo

## CVE-2026-95613 - Zenitel Connect pREST API adopts arbitrary PostgreSQL role from unvalidated JWT sub claim

DevFeed: [CVE-2026-95613 - Zenitel Connect pREST API adopts arbitrary PostgreSQL role from unvalidated JWT sub claim](<https://devfeed.tech/articles/cve-2026-95613-zenitel-connect-prest-api-adopts-arbitrary-postgresql-role-from-unvalidated-jwt-sub-claim-132487.md>)

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

Author: CVEFEED.io

Published: 2026-11-13T16:19:38Z

Content type: news

Language: en

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

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [ca](<https://devfeed.tech/tags/ca.md>), [connect](<https://devfeed.tech/tags/connect.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-95613](<https://devfeed.tech/tags/cve-2026-95613.md>), [data-volume](<https://devfeed.tech/tags/data-volume.md>), [database](<https://devfeed.tech/tags/database.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [filesystem](<https://devfeed.tech/tags/filesystem.md>), [firmware](<https://devfeed.tech/tags/firmware.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [password](<https://devfeed.tech/tags/password.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [private-key](<https://devfeed.tech/tags/private-key.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>)

### AI overview

In Zenitel Connect firmware before 1.11.0, the pREST API sets the PostgreSQL session role from an unvalidated JWT `sub` claim while connected as the `postgres` superuser. The API signs and verifies tokens using a platform CA private key stored on a data volume shared between containers. A local attacker who can read that key can forge a JWT with `sub=postgres` and use the API to perform database operations as the superuser, including reading the master encryption key and password hashes. The excerpt reports no affected products in its product table, so it does not identify specific product versions beyond the firmware range in the description.

### Source excerpt

CVE ID :CVE-2026-95613 Published : Nov. 13, 2026, 4:19 p.m. | 1 hour ago Description :The pREST database REST API in Zenitel Connect firmware before 1.11.0 signs and verifies JWTs with the platform CA private key, which is stored on a data volume shared between containers, and sets the PostgreSQL session role from the unvalidated sub claim of each request while connected to the database as the "postgres" superuser, which allows local attackers who can read the platform CA private key from the container filesystem to execute database operations as the PostgreSQL superuser, including reading the master encryption key and password hashes, via a forged JWT with sub=postgres sent to the pREST API. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Manage AI Scan for repositories using the REST API

DevFeed: [Manage AI Scan for repositories using the REST API](<https://devfeed.tech/articles/manage-ai-scan-for-repositories-using-the-rest-api-133231.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-13-manage-ai-scan-for-repositories-using-the-rest-api>)

Author: Allison

Published: 2026-11-13T12:22:41Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [code-scanning](<https://devfeed.tech/tags/code-scanning.md>), [github](<https://devfeed.tech/tags/github.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [preview](<https://devfeed.tech/tags/preview.md>), [public](<https://devfeed.tech/tags/public.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>)

### AI overview

The REST API public preview adds a `repository_scan` setting to GitHub's AI Scan enablement endpoints for organizations and repositories. Use `GET` or `PATCH /orgs/{org}/code-scanning/ai-scan` or `GET` or `PATCH /repos/{owner}/{repo}/code-scanning/ai-scan`, setting the property to `enabled` or `disabled`; it can be updated alongside `pr_scan`. Organization settings constrain repositories: disabling prevents them from enabling AI Scan, while enabling lets repositories inherit the setting or opt out. Enterprise policy must allow AI Scan; a blocked enablement returns `422`, and if either setting in a combined request is blocked, neither changes. Enabling repository scans does not start one: users with write access run scans on demand, consuming Code Security AI credits. Organization owners and security managers manage organization settings; repository administrators can opt out individual repositories. Availability covers public organization-owned repositories and private or internal repositories with GitHub Code Security or Advanced Security. GitHub Enterprise Server is unsupported.

### Source excerpt

You can now turn GitHub code scanning's AI Scan for repositories on or off with the REST API at the organization and repository levels. This public preview adds a repository_scan... The post Manage AI Scan for repositories using the REST API appeared first on The GitHub Blog.

## Hacked Nixie Clock Waits for the Bus

DevFeed: [Hacked Nixie Clock Waits for the Bus](<https://devfeed.tech/articles/hacked-nixie-clock-waits-for-the-bus-131561.md>)

Original publisher: [Read original article](<https://hackaday.com/2026/11/13/hacked-nixie-clock-waits-for-the-bus/>)

Author: Tom Nardi

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

Content type: news

Language: en

Sources: [Hackaday](<https://devfeed.tech/sources/hackaday.md>)

Topics: [io interface](<https://devfeed.tech/topics/io-interface.md>), [Python](<https://devfeed.tech/topics/python.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [board](<https://devfeed.tech/tags/board.md>), [bus](<https://devfeed.tech/tags/bus.md>), [classic-hacks](<https://devfeed.tech/tags/classic-hacks.md>), [clock](<https://devfeed.tech/tags/clock.md>), [clock-hacks](<https://devfeed.tech/tags/clock-hacks.md>), [communication](<https://devfeed.tech/tags/communication.md>), [converter](<https://devfeed.tech/tags/converter.md>), [display](<https://devfeed.tech/tags/display.md>), [firmware](<https://devfeed.tech/tags/firmware.md>), [hacked](<https://devfeed.tech/tags/hacked.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [i2c](<https://devfeed.tech/tags/i2c.md>), [microcontroller](<https://devfeed.tech/tags/microcontroller.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [nixie-tube](<https://devfeed.tech/tags/nixie-tube.md>), [nixie-tube-clock](<https://devfeed.tech/tags/nixie-tube-clock.md>), [pcb](<https://devfeed.tech/tags/pcb.md>), [pi](<https://devfeed.tech/tags/pi.md>), [public-transit](<https://devfeed.tech/tags/public-transit.md>), [python](<https://devfeed.tech/tags/python.md>), [raspberry-pi](<https://devfeed.tech/tags/raspberry-pi.md>), [script](<https://devfeed.tech/tags/script.md>), [serial](<https://devfeed.tech/tags/serial.md>), [st-link](<https://devfeed.tech/tags/st-link.md>), [stm8](<https://devfeed.tech/tags/stm8.md>)

### AI overview

Justin Scott repurposed a two-digit Nixie clock to show minutes until the next bus at his local stop. He used a ST-LINK V2 programmer and traced the STM8 microcontroller pins to modify the board firmware, then connected spare I/O pins over serial to a Raspberry Pi Zero through a level converter. A Python script on the Pi queries the bus API and sends the countdown to the clock; blinking decimal points indicate background activity.

### Source excerpt

Nixie clocks have become popular enough that these days there's no shortage of turn-key options that let you experience that warm glow with a minimum of fuss. Many still come ...read more

## Home Assistant-compatible ESP32 4-channel PWM fan controller is designed for server racks and NAS systems

DevFeed: [Home Assistant-compatible ESP32 4-channel PWM fan controller is designed for server racks and NAS systems](<https://devfeed.tech/articles/home-assistant-compatible-esp32-4-channel-pwm-fan-controller-is-designed-for-server-racks-and-nas-systems-131324.md>)

Original publisher: [Read original article](<https://www.cnx-software.com/2026/11/13/home-assistant-compatible-esp32-4-channel-pwm-fan-controller-is-designed-for-server-racks-and-nas-systems/>)

Author: Debashis Das

Published: 2026-11-13T03:16:49Z

Content type: news

Language: en

Sources: [CNX Software - Embedded Systems News](<https://devfeed.tech/sources/cnx-software-embedded-systems-news.md>)

Topics: [ESP32](<https://devfeed.tech/topics/esp32.md>), [Home Assistant](<https://devfeed.tech/topics/home-assistant.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [esp32](<https://devfeed.tech/tags/esp32.md>), [esphome](<https://devfeed.tech/tags/esphome.md>), [espressif](<https://devfeed.tech/tags/espressif.md>), [fan](<https://devfeed.tech/tags/fan.md>), [fan-control](<https://devfeed.tech/tags/fan-control.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [home-assistant](<https://devfeed.tech/tags/home-assistant.md>), [nas](<https://devfeed.tech/tags/nas.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [pwm](<https://devfeed.tech/tags/pwm.md>), [server](<https://devfeed.tech/tags/server.md>)

### AI overview

CoolMaker Lab's open-source ESP32 controller independently manages up to four 4-pin PWM fans, with speed control, RPM monitoring, and switches that can cut fan power for zero-RPM operation. It connects to Home Assistant through ESPHome and also offers a web interface, HTTP REST API, Bluetooth proxy, and OTA updates. With v2.0 hardware and firmware, up to four DS18B20 sensors can drive local temperature-based control; the stated defaults turn fans off at 30°C or below and ramp them to the configured maximum by 50°C, with adjustable limits. Optional LD2402G radar enables presence-based automation. The article contrasts it with the ANAVI Fume Extractor, which switches a fan based on air quality, and the ARCTIC controller, which has 10 PWM connectors but is described as relying on motherboard USB and SATA power and lacking wireless and Home Assistant support. The excerpt gives a $28 price excluding shipping and says documentation and design files are available in Chinese and English.

### Source excerpt

Designed by CoolMaker Lab in China, the ESP32 4-channel PWM fan controller is an open-source, Home Assistant-compatible board for managing cooling in server racks, NAS systems, network cabinets, and other DIY enclosures. It can independently control up to four 4-pin PWM fans, supporting PWM-based speed adjustment, tachometer-based RPM monitoring, and individual fan power switching. The controller supports up to four external DS18B20 temperature sensors for automatic fan speed adjustment, along with a web interface, an HTTP REST API, and Bluetooth proxy functionality. The latest v2.0 hardware and firmware also support optional LD2402G 24GHz mmWave radar for presence-based automation. ESP32 4-channel PWM fan controller specifications: MCU - ESP32-WROOM-32-N4 module with 4MB flash, 2.4GHz Wi-Fi, and Bluetooth LE (BLE proxy) Fan control 4x independent 4-pin PWM fan connectors with 1-100% PWM speed adjustment 4x tachometer inputs for RPM monitoring TPS22810DBVR-based individual fan power switch with load switches for complete shutdown (zero-RPM operation) Automatic [...] The post Home Assistant-compatible ESP32 4-channel PWM fan controller is designed for server racks and NAS systems appeared first on CNX Software - Embedded Systems News.

## Build a serverless recipe-sharing API with Go and Amazon Aurora DSQL

DevFeed: [Build a serverless recipe-sharing API with Go and Amazon Aurora DSQL](<https://devfeed.tech/articles/build-a-serverless-recipe-sharing-api-with-go-and-amazon-aurora-dsql-131173.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-a-serverless-recipe-sharing-api-with-go-and-amazon-aurora-dsql/>)

Author: Steve Brown

Published: 2026-11-12T16:14:20Z

Content type: tutorial

Language: en

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

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>)

Tags: [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [go](<https://devfeed.tech/tags/go.md>), [iam](<https://devfeed.tech/tags/iam.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [keys](<https://devfeed.tech/tags/keys.md>), [optimistic-concurrency](<https://devfeed.tech/tags/optimistic-concurrency.md>), [recipe](<https://devfeed.tech/tags/recipe.md>), [referential-integrity](<https://devfeed.tech/tags/referential-integrity.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [retries](<https://devfeed.tech/tags/retries.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [token](<https://devfeed.tech/tags/token.md>), [uuid](<https://devfeed.tech/tags/uuid.md>)

### AI overview

The article demonstrates a Go recipe-sharing REST API that runs locally as a Gin HTTP server or on AWS Lambda behind API Gateway, using the same handlers and an Amazon Aurora DSQL store. It describes UUID text primary keys to spread writes across storage partitions; short-lived IAM tokens, TLS, and a pgx connection pool managed by the Go connector; and separate DDL operations because DDL and DML cannot share a transaction. The sample checks chef and recipe references in handlers, though the database can enforce them with foreign keys instead. Aurora DSQL optimistic concurrency conflicts can be retried by the connector's occretry package with exponential backoff, so transaction logic should be idempotent. Deployment uses a script and CloudFormation for Lambda, API Gateway, IAM, and logs; its IP allowlist is not authentication, and the article recommends adding an authorization method for production. The text also notes connection recycling before the 60-minute server limit and low pool sizing for single-request Lambda invocations.

### Source excerpt

Build a fully serverless recipe-sharing REST API in Go on Amazon Aurora DSQL, AWS Lambda, and Amazon API Gateway. Learn UUID primary keys for even write distribution, short-lived IAM token authentication, application-layer referential integrity, and automatic optimistic-concurrency retries, with a one-command CloudFormation deployment.

## How to get a Google Gemini API key--and use the Gemini API

DevFeed: [How to get a Google Gemini API key--and use the Gemini API](<https://devfeed.tech/articles/how-to-get-a-google-gemini-api-key-and-use-the-gemini-api-129823.md>)

Original publisher: [Read original article](<https://zapier.com/blog/gemini-api>)

Author: Miguel Rebelo

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

Content type: tutorial

Language: en

Sources: [Zapier](<https://devfeed.tech/sources/zapier.md>)

Topics: [generative-ai-tools](<https://devfeed.tech/topics/generative-ai-tools.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [API Monetization](<https://devfeed.tech/topics/api-monetization.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-studio](<https://devfeed.tech/tags/ai-studio.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [gemini-4](<https://devfeed.tech/tags/gemini-4.md>), [gemini-4-carbon](<https://devfeed.tech/tags/gemini-4-carbon.md>), [gemini-api](<https://devfeed.tech/tags/gemini-api.md>), [google](<https://devfeed.tech/tags/google.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [images](<https://devfeed.tech/tags/images.md>), [multimodality](<https://devfeed.tech/tags/multimodality.md>), [openai](<https://devfeed.tech/tags/openai.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

The guide explains how to obtain a Gemini API key in Google AI Studio and make a REST request, using Postman as its example. Create a key from the key icon, associate it with a project, and store it securely. In Postman, send a POST request with the API URL, the x-goog-api-key and Content-Type: application/json headers, and a JSON body containing a model and prompt. The guide also shows how to add system instructions and nest generation settings such as max_output_tokens under generation_config. It contrasts AI Studio's simpler setup with the broader model and settings access through Google Cloud's Gemini platform. Pricing includes a limited free tier, pay-as-you-go usage, and an enterprise option; the free tier has lower limits and may time out or return 503 errors during high demand, while its requests and outputs may be used for model training. The text notes that API rate limits are not clearly displayed and recommends checking the Rate Limits tab. This is an excerpted guide, so it does not establish current model availability or provide a complete API reference.

### Source excerpt

OpenAI and Anthropic models can read text and look at images just fine, but video is a big no-no. If you're building a tool or a product that absolutely needs that type of media, you'd have to engineer a long workaround, decomposing it into multiple images and then feeding them as an input. A big techie flex if you manage to do it, but is it worth the time? Google has the answer if you want to go faster. Its latest models, led by Gemini 4 Carbon, focus on multimodality, being capable of consumin

## One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration

DevFeed: [One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration](<https://devfeed.tech/articles/one-identity-unveils-active-roles-8-6-with-enhanced-security-and-administration-127824.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4247172/one-identity-unveils-active-roles-8-6-with-enhanced-security-and-administration-2.html>)

Author: CIO

Published: 2026-11-11T04:44:23Z

Content type: release

Language: en

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

Topics: [active directory](<https://devfeed.tech/topics/active-directory.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [saml](<https://devfeed.tech/topics/saml.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Entra ID](<https://devfeed.tech/topics/entra-id.md>), [microsoft 365](<https://devfeed.tech/topics/microsoft-365.md>), [PowerShell](<https://devfeed.tech/topics/powershell.md>)

Tags: [active-directory](<https://devfeed.tech/tags/active-directory.md>), [administration](<https://devfeed.tech/tags/administration.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [api](<https://devfeed.tech/tags/api.md>), [api-access](<https://devfeed.tech/tags/api-access.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [console](<https://devfeed.tech/tags/console.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [entra-id](<https://devfeed.tech/tags/entra-id.md>), [flexible](<https://devfeed.tech/tags/flexible.md>), [identity](<https://devfeed.tech/tags/identity.md>), [integration](<https://devfeed.tech/tags/integration.md>), [interface](<https://devfeed.tech/tags/interface.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [management](<https://devfeed.tech/tags/management.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-365](<https://devfeed.tech/tags/microsoft-365.md>), [powershell](<https://devfeed.tech/tags/powershell.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [roles](<https://devfeed.tech/tags/roles.md>), [security](<https://devfeed.tech/tags/security.md>), [storytype-press-release](<https://devfeed.tech/tags/storytype-press-release.md>)

### AI overview

Active Roles 8.6 combines a fix for an RSTS configuration security issue with cumulative features, enhancements and resolved issues from the intervening releases after 8.2.1 SP6, superseding versions 8.3, 8.4 and 8.5. The cumulative release line adds the Active Roles REST API and Redistributable Secure Token Server capabilities for API access and SAML 2.0 federated authentication. The excerpt characterizes the change as an administration and integration upgrade, not a visual redesign. It describes a configurable thick-client UI modeled on Microsoft Active Directory, one console for Active Directory, Microsoft Entra ID and Microsoft 365, and support for PowerShell and VBScript. PeerSpot figures and rankings are also reported, based on 92 reviews.

### Source excerpt

Active Roles 8.6: Cumulative security, feature and administration upgrades One Identity has introduced Active Roles 8.6, strengthening secure and streamlined Active Directory administration with cumulative platform improvements, expanded API capabilities and greater authentication flexibility. Active Roles 8.6, updated July 27, 2026, focuses on security and cumulative platform improvements. It fixes an RSTS configuration security issue and supersedes versions 8.3, 8.4 and 8.5. Compared with Active Roles 8.2.1 SP6, One Identity says 8.6 incorporates the features, enhancements and resolved issues delivered across that intervening release line. See the Active Roles 8.6 Release Notes. The recent improvements are therefore best described as an administrator and integration experience upgrade, rather than a new visual redesign. The cumulative release line adds capabilities including the Active Roles REST API, as well as Redistributable Secure Token Server capabilities supporting API access and SAML 2.0 federated authentication. Active Roles 8.6: Familiar Administration Meets Greater Flexibility and Consolidation Those upgrades complement one of Active Roles' most recognizable usability strengths: a flexible, configurable UI that can be tailored to individual users and personas. Its thick-client interface is designed to resemble the familiar Microsoft Active Directory experience, helping reduce the learning curve for experienced AD administrators. The broader experience centers on consolidation, with a single console spanning Active Directory, Microsoft Entra ID and Microsoft 365 helping administrators avoid constantly switching between separate management environments. Together with PowerShell and VBScript support, the product keeps familiar tools and interaction patterns at the center of the administrator experience. This combination of configurable views, familiar administration and centralized control supports Active Roles' position among top Active Directory managemen

## Laravel Rest Api 3.0: Typed Fields, Metrics, and OpenAPI Docs

DevFeed: [Laravel Rest Api 3.0: Typed Fields, Metrics, and OpenAPI Docs](<https://devfeed.tech/articles/laravel-rest-api-3-0-typed-fields-metrics-and-openapi-docs-126628.md>)

Original publisher: [Read original article](<https://laravel-news.com/laravel-rest-api-3>)

Author: Eric L. Barnes

Published: 2026-11-10T13:33:18Z

Content type: release

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>), [Laravel](<https://devfeed.tech/topics/laravel.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Eloquent ORM](<https://devfeed.tech/topics/eloquent.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [algolia](<https://devfeed.tech/tags/algolia.md>), [api](<https://devfeed.tech/tags/api.md>), [count](<https://devfeed.tech/tags/count.md>), [counts](<https://devfeed.tech/tags/counts.md>), [docs](<https://devfeed.tech/tags/docs.md>), [eloquent](<https://devfeed.tech/tags/eloquent.md>), [fields](<https://devfeed.tech/tags/fields.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [laravel-packages](<https://devfeed.tech/tags/laravel-packages.md>), [metric](<https://devfeed.tech/tags/metric.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [package](<https://devfeed.tech/tags/package.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [scramble](<https://devfeed.tech/tags/scramble.md>)

### AI overview

Laravel Rest Api 3.0 rebuilds Eloquent-to-REST resources around typed fields: one field declaration governs type-compatible filters, write validation, response values and API documentation. It replaces built-in docs with Scramble's OpenAPI output and tests request examples against the generated document. Resource metrics gain dedicated endpoints for values, trends, partitions, progress and tables, with date ranges, time zones, prior-period comparisons, caching, and access limited to rows the user may see. Actions and writes can require confirmation: the API returns 428 with a message and signed token, then runs the same request when resubmitted with that token. Other changes include per-resource and per-row policy checks, tenant scoping, transactional nested writes, version conflict responses, and queued action batches. Version 3.0 requires PHP 8.3+ and Laravel 13.30+; Laravel 12 users should remain on 2.x. The excerpt notes breaking changes and refers to an upgrade guide.

### Source excerpt

Laravel Rest Api 3.0 rebuilds the package around typed fields, adds metric endpoints and write confirmations, and documents your API with Scramble. The post Laravel Rest Api 3.0: Typed Fields, Metrics, and OpenAPI Docs appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## TwinLight: A Multi-Timescale Physical-Layer-Aware T-API-Compliant Optical Domain Controller Digital Twin

DevFeed: [TwinLight: A Multi-Timescale Physical-Layer-Aware T-API-Compliant Optical Domain Controller Digital Twin](<https://devfeed.tech/articles/twinlight-a-multi-timescale-physical-layer-aware-t-api-compliant-optical-domain-controller-digital-twin-124032.md>)

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

Author: Carlos Natalino, Piotr Lechowicz, Renato Ambrosone, Enrico Miotto, Vittorio Curri, Paolo Monti

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

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [communications](<https://devfeed.tech/topics/communications.md>), [API](<https://devfeed.tech/topics/api.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [controller](<https://devfeed.tech/tags/controller.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [digital-twin](<https://devfeed.tech/tags/digital-twin.md>), [engine](<https://devfeed.tech/tags/engine.md>), [network](<https://devfeed.tech/tags/network.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [optical](<https://devfeed.tech/tags/optical.md>), [physics-optics](<https://devfeed.tech/tags/physics-optics.md>), [rest](<https://devfeed.tech/tags/rest.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

TwinLight is an open-source optical-network digital twin designed to act as an optical domain controller. Its T-API REST and telemetry streaming interfaces expose a physical-layer engine that combines a GNPy steady-state baseline with four analytical transients. The excerpt does not specify what those transients model or report performance results.

### Source excerpt

arXiv:2611.09359v1 Announce Type: cross Abstract: We demonstrate TwinLight, an open-source optical-network digital twin acting as an optical domain controller. Its T-API REST and telemetry streaming interfaces expose a physical-layer engine that combines a GNPy steady-state baseline with four analytical transients.

## Copilot code review: API management and review overview updates

DevFeed: [Copilot code review: API management and review overview updates](<https://devfeed.tech/articles/copilot-code-review-api-management-and-review-overview-updates-121900.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-06-copilot-code-review-api-management-and-review-overview-updates>)

Author: Allison

Published: 2026-11-07T00:27:19Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [GitHub API](<https://devfeed.tech/topics/github-api.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [comment](<https://devfeed.tech/tags/comment.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [copilot-code](<https://devfeed.tech/tags/copilot-code.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [github](<https://devfeed.tech/tags/github.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [github-copilot-code-review](<https://devfeed.tech/tags/github-copilot-code-review.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [manage](<https://devfeed.tech/tags/manage.md>), [more](<https://devfeed.tech/tags/more.md>), [overview](<https://devfeed.tech/tags/overview.md>), [policy](<https://devfeed.tech/tags/policy.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [review](<https://devfeed.tech/tags/review.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

GitHub Copilot code review settings can now be managed through REST and GraphQL APIs from enterprise to repository level, with permissions and token support varying by endpoint. Enterprise and organization settings endpoints do not support GitHub Apps or fine-grained personal access tokens; repository settings endpoints do, requiring Administration read or write permission, while classic tokens need repository administrator access. API responses expose review attribution, available effort levels, and reported skills, MCP servers, or custom instructions. Review overviews consolidate unreviewed files and move effort details into a compact footer. Other updates include three-model balanced reviews, one automatic retry for failed or timed-out reviews, fallback to another eligible model, and AI-credit reporting for agent sessions. The excerpt says these updates are available on Copilot Pro, Pro+, Max, Business, and Enterprise plans.

### Source excerpt

You can now manage GitHub Copilot code review settings through the REST and GraphQL APIs, from enterprise policy down to individual repositories. Copilot's review overview comment is now more compact,... The post Copilot code review: API management and review overview updates appeared first on The GitHub Blog.

## CVE-2026-86044 - JupyterLab Desktop: One-Click Jupyter Server Token Leak leading to Remote Code Execution

DevFeed: [CVE-2026-86044 - JupyterLab Desktop: One-Click Jupyter Server Token Leak leading to Remote Code Execution](<https://devfeed.tech/articles/cve-2026-86044-jupyterlab-desktop-one-click-jupyter-server-token-leak-leading-to-remote-code-execution-121681.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-06T21:17:12Z

Content type: news

Language: en

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

Topics: [jupyterlab](<https://devfeed.tech/topics/jupyterlab.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [execution](<https://devfeed.tech/topics/execution.md>), [jupyter](<https://devfeed.tech/topics/jupyter.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-86044](<https://devfeed.tech/tags/cve-2026-86044.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [execution](<https://devfeed.tech/tags/execution.md>), [jupyter](<https://devfeed.tech/tags/jupyter.md>), [jupyterlab](<https://devfeed.tech/tags/jupyterlab.md>), [leak](<https://devfeed.tech/tags/leak.md>), [link](<https://devfeed.tech/tags/link.md>), [local](<https://devfeed.tech/tags/local.md>), [managed](<https://devfeed.tech/tags/managed.md>), [mathjax](<https://devfeed.tech/tags/mathjax.md>), [notebook](<https://devfeed.tech/tags/notebook.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [server](<https://devfeed.tech/tags/server.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

Before JupyterLab Desktop 4.6.2-1, the renderer could access getServerInfo without checking that the page still had the local Jupyter server origin. In a local managed session with JupyterLab earlier than 4.4.8, a crafted MathJax link in an untrusted notebook can send the renderer to an attacker-controlled site; if the victim clicks it, that site can retrieve the server URL and token through the preload bridge. The attacker can then use the Jupyter REST API to create and trust a notebook that runs code as the victim. Environments using JupyterLab 4.4.8 or later are unaffected because corrected link handling breaks the chain's first step. JupyterLab Desktop fixes the vulnerability in 4.6.2-1.

### Source excerpt

CVE ID :CVE-2026-86044 Published : Nov. 6, 2026, 9:17 p.m. | 53 minutes ago Description :JupyterLab Desktop is the cross-platform desktop application for JupyterLab. Prior to 4.6.2-1, JupyterLab Desktop exposed getServerInfo to the renderer without confirming that the current page still had the local Jupyter server origin. In a local managed session using JupyterLab before 4.4.8, an attacker can place a crafted MathJax link in an untrusted notebook. If a victim opens the notebook and clicks the link, the existing renderer navigates to an attacker-controlled site while retaining access to the preload bridge. The site can call getServerInfo to obtain the local server URL and authentication token, then use the Jupyter REST API to create and trust a notebook that executes arbitrary code as the victim. Users whose environment already uses JupyterLab 4.4.8 or later are unaffected because the corrected link handling breaks the first step of the chain. This vulnerability is fixed in 4.6.2-1. Severity: 9.6 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-58273 - Rucio: Authorisation Bypass on REST API endpoint for signing URLs

DevFeed: [CVE-2026-58273 - Rucio: Authorisation Bypass on REST API endpoint for signing URLs](<https://devfeed.tech/articles/cve-2026-58273-rucio-authorisation-bypass-on-rest-api-endpoint-for-signing-urls-119651.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-05T22:18:49Z

Content type: news

Language: en

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

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-58273](<https://devfeed.tech/tags/cve-2026-58273.md>), [data](<https://devfeed.tech/tags/data.md>), [delete](<https://devfeed.tech/tags/delete.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [framework](<https://devfeed.tech/tags/framework.md>), [gcs](<https://devfeed.tech/tags/gcs.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [signing](<https://devfeed.tech/tags/signing.md>), [urls](<https://devfeed.tech/tags/urls.md>)

### AI overview

Rucio's `/credentials/signurl` endpoint checks the account supplied in `X-Rucio-Account` instead of the authenticated issuer, allowing any authenticated low-privilege user to claim `root` and pass the root-only permission check. The endpoint can then issue presigned read, write, or delete URLs for attacker-selected objects using stored S3, GCS, or Swift credentials; in multi-VO deployments, `X-Rucio-VO` can select another tenant. The described impact includes data disclosure, modification, deletion, and cross-tenant access on cloud-backed RSEs. The issue is listed as fixed in 35.9.0, 38.6.0, and 41.0.0rc1.

### Source excerpt

CVE ID :CVE-2026-58273 Published : Nov. 5, 2026, 10:18 p.m. | 1 hour, 4 minutes ago Description :Rucio is a scientific data management framework. From 1.16.1 until 35.9.0, 38.6.0, and 41.0.0rc1, the /credentials/signurl endpoint reads X-Rucio-Account instead of the account stored in request.environ['issuer'] by token authentication. Any authenticated low-privilege user can supply root as the header value and pass the root-only get_signed_url permission check. The server then returns a presigned read, write, or delete URL for an attacker-selected object using stored S3, GCS, or Swift credentials, and X-Rucio-VO can select another tenant in multi-VO deployments. This permits data disclosure, modification, deletion, and cross-tenant access on cloud-backed RSEs. This issue is fixed in versions 35.9.0, 38.6.0, and 41.0.0rc1. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## A Practical Introduction to the Twitch Helix API

DevFeed: [A Practical Introduction to the Twitch Helix API](<https://devfeed.tech/articles/a-practical-introduction-to-the-twitch-helix-api-121371.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/a-practical-introduction-to-the-twitch-helix-api/>)

Author: SitePoint Team

Published: 2026-11-05T20:17:12Z

Content type: article

Language: en

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

Topics: [Twitch](<https://devfeed.tech/topics/twitch.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [2022](<https://devfeed.tech/tags/2022.md>), [about](<https://devfeed.tech/tags/about.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [account](<https://devfeed.tech/tags/account.md>), [act](<https://devfeed.tech/tags/act.md>), [actions](<https://devfeed.tech/tags/actions.md>), [alert](<https://devfeed.tech/tags/alert.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [array](<https://devfeed.tech/tags/array.md>), [article](<https://devfeed.tech/tags/article.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [avatar](<https://devfeed.tech/tags/avatar.md>), [practical](<https://devfeed.tech/tags/practical.md>), [social-media](<https://devfeed.tech/tags/social-media.md>), [twitch](<https://devfeed.tech/tags/twitch.md>)

### AI overview

Twitch Helix is Twitch's current REST API for public data and scoped user actions; the retired Kraken API is obsolete. Read-only tools can usually use an app access token from the client credentials flow, while actions on a person's behalf--such as messaging or moderation--require a user token with appropriate scopes. Every request also needs a Client ID, and the app secret must stay server-side. Helix provides user, stream, category, clip and chat-related endpoints; EventSub delivers live events, while Helix handles lookups and message sending. The excerpt highlights practical safeguards: heed rate-limit headers and cache stable data, store user IDs because logins can change, handle missing users as empty results, and batch up to 100 logins per users request.

### Source excerpt

null Continue reading A Practical Introduction to the Twitch Helix API on SitePoint.

## CVE-2026-69134 - SuiteCRM: SQL Injection via REST API securexss() Bypass in Relationship Management

DevFeed: [CVE-2026-69134 - SuiteCRM: SQL Injection via REST API securexss() Bypass in Relationship Management](<https://devfeed.tech/articles/cve-2026-69134-suitecrm-sql-injection-via-rest-api-securexss-bypass-in-relationship-management-119524.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-05T19:17:24Z

Content type: news

Language: en

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

Topics: [SQL](<https://devfeed.tech/topics/sql.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [alter](<https://devfeed.tech/tags/alter.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [crm](<https://devfeed.tech/tags/crm.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customer-relationship-management](<https://devfeed.tech/tags/customer-relationship-management.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-69134](<https://devfeed.tech/tags/cve-2026-69134.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [management](<https://devfeed.tech/tags/management.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-injection](<https://devfeed.tech/tags/sql-injection.md>)

### AI overview

In SuiteCRM versions before 7.15.2 and 8.10.2, the REST v4 JSON handler uses the pre-filter RAW_REQUEST value in relationship writes, whose helpers interpolate supplied fields into SQL INSERT and UPDATE statements. An authenticated user can exploit this path through relationship fields to read or alter database data; file writes may also be possible if the database account has elevated privileges. The issue is fixed in versions 7.15.2 and 8.10.2.

### Source excerpt

CVE ID :CVE-2026-69134 Published : Nov. 5, 2026, 7:17 p.m. | 1 hour, 51 minutes ago Description :SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, the REST v4 JSON handler reads the pre-filter RAW_REQUEST value and relationship write helpers interpolate supplied field values into INSERT and UPDATE statements. The affected flow begins at $GLOBALS['RAW_REQUEST'] and uses set_relationship, SugarRelationship::addRow(), SugarRelationship::updateRow(), and contact_role to carry attacker-controlled data or authorization state into the security-sensitive operation. An authenticated user can inject SQL through relationship fields to read or alter database data and may reach file-write consequences when the database account has elevated privileges. This issue is fixed in versions 7.15.2 and 8.10.2. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-93389 - LiteSpeed Cache \<= 7.9.1 - Unauthenticated Sensitive Information Disclosure (WooCommerce Store API Cart/Checkout PII + Cart-Token) via Public REST Caching

DevFeed: [CVE-2026-93389 - LiteSpeed Cache \<= 7.9.1 - Unauthenticated Sensitive Information Disclosure (WooCommerce Store API Cart/Checkout PII + Cart-Token) via Public REST Caching](<https://devfeed.tech/articles/cve-2026-93389-litespeed-cache-7-9-1-unauthenticated-sensitive-information-disclosure-woocommerce-store-api-cart-checkout-pii-cart-token-via-public-rest-caching-118154.md>)

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

Author: CVEFEED.io; wordfence.com

Published: 2026-11-05T05:18:40Z

Content type: news

Language: en

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

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [pii](<https://devfeed.tech/topics/pii.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [billing](<https://devfeed.tech/tags/billing.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-93389](<https://devfeed.tech/tags/cve-2026-93389.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [information](<https://devfeed.tech/tags/information.md>), [litespeed-cache](<https://devfeed.tech/tags/litespeed-cache.md>), [litespeedtech](<https://devfeed.tech/tags/litespeedtech.md>), [pii](<https://devfeed.tech/tags/pii.md>), [public](<https://devfeed.tech/tags/public.md>), [rest](<https://devfeed.tech/tags/rest.md>), [store](<https://devfeed.tech/tags/store.md>), [token](<https://devfeed.tech/tags/token.md>), [woocommerce](<https://devfeed.tech/tags/woocommerce.md>)

### AI overview

LiteSpeed Cache versions up to and including 7.9.1 can expose WooCommerce customer data when the shipped default `cache-rest=1` setting is enabled. The excerpt says Store API cart and checkout GET responses are cached publicly without varying by Cart-Token or WooCommerce session, so a later unauthenticated client may receive a shopper's personalized response. Disclosed data may include billing and shipping details, cart contents and totals, a live Cart-Token JWT and nonce, and checkout `order_key`; the source says the token and nonce can enable cart or checkout session hijacking. The excerpt gives a CVSS severity of 8.2 (HIGH) but provides no remediation steps.

### Source excerpt

CVE ID :CVE-2026-93389 Published : Nov. 5, 2026, 5:18 a.m. | 2 hours, 9 minutes ago Description :The LiteSpeed Cache plugin for WordPress is vulnerable to unauthenticated disclosure of sensitive WooCommerce customer data in all versions up to, and including, 7.9.1 With Cache REST enabled (the shipped default cache-rest=1), LiteSpeed stores WooCommerce Store API GET responses (/wc/store/v1/cart and /wc/store/v1/checkout) as PUBLIC cache objects and does not vary the cache on the Cart-Token or WooCommerce session. A shopper's personalized cart/checkout response is therefore served to any later, cookie-less and token-less client as an LSCache HIT. This makes it possible for unauthenticated attackers to read another shopper's billing and shipping details (name, company, street address, email, phone), cart contents and totals, and the shopper's live Cart-Token session JWT and nonce (enabling cart/checkout-session hijack), plus order_key on the checkout endpoint. Severity: 8.2 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## HubSpot to ClickHouse: Sync Methods, Setup & API Limits Guide

DevFeed: [HubSpot to ClickHouse: Sync Methods, Setup & API Limits Guide](<https://devfeed.tech/articles/hubspot-to-clickhouse-sync-methods-setup-api-limits-guide-118921.md>)

Original publisher: [Read original article](<https://estuary.dev/blog/hubspot-to-clickhouse>)

Author: Seán Whelan

Published: 2026-11-04T22:42:36Z

Content type: article

Language: en

Sources: [Estuary](<https://devfeed.tech/sources/estuary.md>)

Topics: [hubspot](<https://devfeed.tech/topics/hubspot.md>), [clickhouse](<https://devfeed.tech/topics/clickhouse.md>), [elt](<https://devfeed.tech/topics/elt.md>), [API](<https://devfeed.tech/topics/api.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [compare](<https://devfeed.tech/tags/compare.md>), [dedupe](<https://devfeed.tech/tags/dedupe.md>), [elt](<https://devfeed.tech/tags/elt.md>), [guide](<https://devfeed.tech/tags/guide.md>), [hubspot](<https://devfeed.tech/tags/hubspot.md>), [limits](<https://devfeed.tech/tags/limits.md>), [managed](<https://devfeed.tech/tags/managed.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [setup](<https://devfeed.tech/tags/setup.md>), [sync](<https://devfeed.tech/tags/sync.md>)

### AI overview

HubSpot can feed ClickHouse through CSV for one-off analysis, custom API code, open-source ELT, or a managed connector. Ongoing syncs must account for HubSpot API quotas, delayed search indexing, and incremental searches that omit archived or deleted records; calculated properties also need separate refreshes. In ClickHouse, use ReplacingMergeTree keyed by record ID and query with FINAL to deduplicate versions. The text describes Estuary polling recent-change and delayed search endpoints, retrying 429s, and refreshing calculated properties daily, but its HubSpot connector does not remove archived or merged records; those require reconciliation. Its associations omit labels and type IDs. Setup also depends on read scopes, a suitable ClickHouse version and grants, network access, sync scheduling, and batch sizes that avoid excessive parts. Rebuild history depends on collection storage retention, and property typing can trade convenience for precision.

### Source excerpt

Sync HubSpot to ClickHouse with a managed tool, open-source ELT or the HubSpot API. Compare 4 methods, plan for rate limits and dedupe with FINAL.

[Next page](<https://devfeed.tech/topics/rest-api.md?cursor=WyIyMDI2LTExLTA0VDIyOjQyOjM2KzAwOjAwIiwgIjA4MWM2Y2E5LTdlNzUtNDMzOC1hNzBmLWFlODVhNjk2YmEwNyJd>)