# Secrets Management

Secrets management is the protection and lifecycle management of credentials such as certificates, keys, passwords, and tokens used by nonhuman users, applications, and IT resources.

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

## Still tracking company passwords in spreadsheets? You're flying blind.

DevFeed: [Still tracking company passwords in spreadsheets? You're flying blind.](<https://devfeed.tech/articles/still-tracking-company-passwords-in-spreadsheets-you-re-flying-blind-146324.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/still-tracking-company-passwords-in-spreadsheets-youre-flying-blind/>)

Author: Sponsored by NordPass Business

Published: 2026-11-20T15:00:10Z

Content type: article

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [passwords](<https://devfeed.tech/topics/passwords.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [company](<https://devfeed.tech/tags/company.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [it](<https://devfeed.tech/tags/it.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [management](<https://devfeed.tech/tags/management.md>), [nord-security](<https://devfeed.tech/tags/nord-security.md>), [nordpass](<https://devfeed.tech/tags/nordpass.md>), [password-management](<https://devfeed.tech/tags/password-management.md>), [passwords](<https://devfeed.tech/tags/passwords.md>), [risks](<https://devfeed.tech/tags/risks.md>), [security](<https://devfeed.tech/tags/security.md>), [security-risks](<https://devfeed.tech/tags/security-risks.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [simplify](<https://devfeed.tech/tags/simplify.md>), [spreadsheets](<https://devfeed.tech/tags/spreadsheets.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [stored](<https://devfeed.tech/tags/stored.md>), [support](<https://devfeed.tech/tags/support.md>), [systems](<https://devfeed.tech/tags/systems.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [tracking](<https://devfeed.tech/tags/tracking.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [visibility](<https://devfeed.tech/tags/visibility.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Manually maintained password spreadsheets miss credentials employees create, change, or share outside the reporting process, leaving admins unable to reliably assess ownership, access, strength, reuse, age, or breach exposure. The source says convenience drives workarounds such as browser storage, shared documents, chat, and personal vaults. NordPass is presented as a centralized vault with XChaCha20 encryption and zero-knowledge architecture; its Data Breach Scanner and Password Health identify weak, reused, old, and exposed passwords, while password requirements, secure sharing, the Sharing Hub, and activity logs help admins manage access and review changes. A managed vault does not ensure adoption or provide a complete inventory: teams still need clear expectations, shared-login ownership and access-removal rules, and separate handling for secrets such as API keys, recovery codes, and certificates.

### Source excerpt

Tracking company passwords in spreadsheets can leave IT administrators unaware of weak, reused, or compromised credentials stored and shared outside approved systems. NordPass explains how centralized password management can improve credential visibility, identify security risks, and simplify secure password sharing. [...]

## CVE-2026-133648 - Flowintel Disables TLS Certificate Verification for MISP and Mail Connections

DevFeed: [CVE-2026-133648 - Flowintel Disables TLS Certificate Verification for MISP and Mail Connections](<https://devfeed.tech/articles/cve-2026-133648-flowintel-disables-tls-certificate-verification-for-misp-and-mail-connections-145915.md>)

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

Author: cvefeed.io

Published: 2026-11-20T10:23:53Z

Content type: news

Language: en

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

Topics: [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [email](<https://devfeed.tech/topics/email.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-133648](<https://devfeed.tech/tags/cve-2026-133648.md>), [flowintel](<https://devfeed.tech/tags/flowintel.md>), [mail](<https://devfeed.tech/tags/mail.md>), [misp](<https://devfeed.tech/tags/misp.md>), [published](<https://devfeed.tech/tags/published.md>), [tls](<https://devfeed.tech/tags/tls.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

Flowintel versions before 4.1.0 disabled TLS certificate verification for MISP HTTPS API calls and used unverified SSL contexts for IMAP TLS and SMTP STARTTLS connections. An unauthenticated attacker with a network position between Flowintel and a configured MISP or mail server could impersonate that server, capture API keys or mail credentials, read exchanged threat intelligence, or modify data returned to Flowintel. The described attack requires no user interaction.

### Source excerpt

CVE ID :CVE-2026-133648 Published : Nov. 20, 2026, 10:23 a.m. | 38 minutes ago Description :Flowintel disabled TLS certificate verification for all MISP API connections and used unverified SSL contexts for IMAP and SMTP STARTTLS mail connections. This allowed an on-path (man-in-the-middle) attacker positioned between Flowintel and its MISP or mail servers to impersonate the remote server and intercept sensitive data. Affected connections include: - All MISP HTTPS API calls (event retrieval, attribute search, event creation, connectivity checks, and API validation) - SMTP STARTTLS connections used for sending email notifications - IMAP TLS connections used for fetching mail archives and testing connectivity An attacker who can observe or intercept network traffic between Flowintel and the MISP or mail server could: - Capture MISP API keys and mail credentials (SMTP/IMAP passwords) - Read all threat intelligence data exchanged (events, attributes, objects, reports) - Inject or modify threat intelligence data returned to Flowintel The vulnerability required no authentication on the part of the attacker and no user interaction; it was exploitable by any party with a network position between Flowintel and its configured MISP or mail endpoints. Affected versions: Flowintel prior to 4.1.0. Severity: 9.9 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## AI incidents of 2026: Rogue agents, stolen keys, and other familiar stories

DevFeed: [AI incidents of 2026: Rogue agents, stolen keys, and other familiar stories](<https://devfeed.tech/articles/ai-incidents-of-2026-rogue-agents-stolen-keys-and-other-familiar-stories-143870.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/ai-incidents-root-causes-patterns>)

Author: Oscar Sanchez Jr.

Published: 2026-11-19T16:04:00Z

Content type: news

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [keys](<https://devfeed.tech/tags/keys.md>), [news](<https://devfeed.tech/tags/news.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [security-incidents](<https://devfeed.tech/tags/security-incidents.md>)

### AI overview

A review of 50 publicly reported AI-related security incidents through November 19, 2026 found that familiar weaknesses dominated: exposed secrets, excessive permissions, weak isolation and compromised vendors. AI agents sometimes accelerated attacks or acted beyond intended boundaries, but only three incidents involved a reported previously unknown vulnerability. Of 44 incidents with a stated cause, 35 had multiple failure points; six reports gave no specific cause and 17 lacked at least one detail. The review recommends limiting agents' access, protecting credentials, enforcing boundaries and requiring approval for irreversible actions. Its counts are based on disclosed cases, categories can overlap, and the sample is not a complete picture of incidents that year.

### Source excerpt

We reviewed 50 AI-related security incidents from 2026. Most came down to exposed secrets, over-scoped access, weak isolation and compromised vendors. Category: News

## CVE-2026-55508 - Wavelog has unauthenticated SQL injection in the OQRS callsign log search

DevFeed: [CVE-2026-55508 - Wavelog has unauthenticated SQL injection in the OQRS callsign log search](<https://devfeed.tech/articles/cve-2026-55508-wavelog-has-unauthenticated-sql-injection-in-the-oqrs-callsign-log-search-141201.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-18T20:44:30Z

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>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-55508](<https://devfeed.tech/tags/cve-2026-55508.md>), [database](<https://devfeed.tech/tags/database.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [logging](<https://devfeed.tech/tags/logging.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [parameter](<https://devfeed.tech/tags/parameter.md>), [password](<https://devfeed.tech/tags/password.md>), [password-reset](<https://devfeed.tech/tags/password-reset.md>), [post](<https://devfeed.tech/tags/post.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-injection](<https://devfeed.tech/tags/sql-injection.md>), [wavelog](<https://devfeed.tech/tags/wavelog.md>)

### AI overview

Before Wavelog 2.5, the unauthenticated POST /oqrs/search_log endpoint passes its callsign parameter into a raw SQL clause without parameter binding. A remote attacker can exploit this with UNION-based SQL injection to read application records, including credentials and password reset tokens; the tokens may enable account takeover, including of administrator accounts. The issue is fixed in version 2.5.

### Source excerpt

CVE ID :CVE-2026-55508 Published : Nov. 18, 2026, 8:44 p.m. | 37 minutes ago Description :Wavelog is web-based amateur radio logging software. Prior to 2.5, the callsign parameter accepted by POST /oqrs/search_log in application/controllers/Oqrs.php search_log() reaches application/models/Oqrs_model.php search_log(), where it is concatenated directly into a raw SQL WHERE clause without parameter binding. An unauthenticated remote attacker can use UNION-based SQL injection to read arbitrary application database records, including account data, password hashes, API keys, station credentials, reset tokens, QSO data, and station metadata. Disclosure of password reset tokens can be combined with the forgot_password workflow to take over accounts, including administrator accounts. This issue is fixed in version 2.5. Severity: 9.4 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## How to use .cursorignore to keep secrets out of Cursor

DevFeed: [How to use .cursorignore to keep secrets out of Cursor](<https://devfeed.tech/articles/how-to-use-cursorignore-to-keep-secrets-out-of-cursor-141134.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/19/how-to-use-cursorignore-to-keep-secrets-out-of-cursor/>)

Author: Ritesh Patel

Published: 2026-11-18T20:32:39.731906Z

Content type: tutorial

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [cursor](<https://devfeed.tech/topics/cursor.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [developer](<https://devfeed.tech/tags/developer.md>), [filter](<https://devfeed.tech/tags/filter.md>), [git](<https://devfeed.tech/tags/git.md>), [gitignore](<https://devfeed.tech/tags/gitignore.md>), [global](<https://devfeed.tech/tags/global.md>), [governance](<https://devfeed.tech/tags/governance.md>), [ignore](<https://devfeed.tech/tags/ignore.md>), [indexing](<https://devfeed.tech/tags/indexing.md>), [protection](<https://devfeed.tech/tags/protection.md>), [secret](<https://devfeed.tech/tags/secret.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [secrets-management](<https://devfeed.tech/tags/secrets-management.md>), [security](<https://devfeed.tech/tags/security.md>), [tab](<https://devfeed.tech/tags/tab.md>)

### AI overview

A root-level `.cursorignore` uses `.gitignore`-style patterns to keep matched files from Cursor Agent and Tab and from @ mention references, but Cursor's documentation says this is not complete protection: terminal and MCP tools may still read ignored files. Defaults cover `.env*` and `.gitignore` matches, but not example names such as `*.key`, `*.pem`, `credentials.json`, or `secrets.json`; add patterns for those. A global ignore list applies across projects, and Hierarchical Cursor Ignore can search parent directories for ignore files. Negation cannot restore a file beneath an excluded directory unless the nested directory is re-included first. Test with a dummy file in Cursor itself, since `git check-ignore` checks only `.gitignore`; record the Cursor version because the cited reference does not specify an app version. Claude Code uses a separate `permissions.deny` format, so rules must be written and tested for each tool.

### Source excerpt

Use a .cursorignore file to keep secret files away from Cursor's Agent and Tab. The Cursor docs say this blocks access but is not complete protection.

## gt 2.0.0: a quarter of the tokens for AI agents, and flags like gh

DevFeed: [gt 2.0.0: a quarter of the tokens for AI agents, and flags like gh](<https://devfeed.tech/articles/gt-2-0-0-a-quarter-of-the-tokens-for-ai-agents-and-flags-like-gh-142884.md>)

Original publisher: [Read original article](<https://blog.gitea.com/release-of-gitea-cli-2.0.0/>)

Author: bircni

Published: 2026-11-18T20:30:00Z

Content type: release

Language: en

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

Topics: [Gitea](<https://devfeed.tech/topics/gitea.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>)

Tags: [2-0-0](<https://devfeed.tech/tags/2-0-0.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [costs](<https://devfeed.tech/tags/costs.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [gitea](<https://devfeed.tech/tags/gitea.md>), [json](<https://devfeed.tech/tags/json.md>), [log](<https://devfeed.tech/tags/log.md>), [release](<https://devfeed.tech/tags/release.md>), [settings](<https://devfeed.tech/tags/settings.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

gitea-cli 2.0.0 reduces output consumed by AI agents: failed-run logs show only failed steps, omit per-line timestamps by default, and piped lists use shorter commit IDs and omit redundant URLs. `--json` and `--csv` now require explicit fields; `--jq .` requests all JSON fields. Absent values are consistently `null`, empty lists are `[]`, and fields that need extra requests are fetched only when requested. The major release also aligns pull-request flags and team reviewer syntax with `gh`, so scripts using renamed flags must be updated; the same CLI and JSON stability promise now applies to 2.x. Scoped `GITEA_TOKEN` credentials can run commands that do not require user identity, including repository reads with `read:repository`. Settings remain readable across versions, though tokens moved to the new keyring entry format cannot be found by 1.x afterward. Gitea 28+ remains supported. `go install` no longer installs 2.x; use another listed distribution method.

### Source excerpt

We are releasing **gitea-cli 2.0.0**. Just over two weeks after [1.0.0](/release-of-gitea-cli-1.0.0/), this major release makes `gt` much cheaper to use from AI coding agents: the log of a failed run now costs about a quarter of the tokens it did. It also brings the last breaking changes we wanted before settling down. `gt`'s flags and JSON output now follow `gh`, settings and stored credentials stay readable across versions, and `gt` works with narrowly scoped CI access tokens. On top of that come many bug fixes from a review against a real Gitea 28.4.

## CVE-2026-130782 - Incus before 7.6.0 Improper Authorization Exposes Default Project Resources

DevFeed: [CVE-2026-130782 - Incus before 7.6.0 Improper Authorization Exposes Default Project Resources](<https://devfeed.tech/articles/cve-2026-130782-incus-before-7-6-0-improper-authorization-exposes-default-project-resources-141176.md>)

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

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-18T19:17:54Z

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>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [admin](<https://devfeed.tech/tags/admin.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [backups](<https://devfeed.tech/tags/backups.md>), [bucket](<https://devfeed.tech/tags/bucket.md>), [clients](<https://devfeed.tech/tags/clients.md>), [contents](<https://devfeed.tech/tags/contents.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [custom](<https://devfeed.tech/tags/custom.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-130782](<https://devfeed.tech/tags/cve-2026-130782.md>), [export](<https://devfeed.tech/tags/export.md>), [full](<https://devfeed.tech/tags/full.md>), [images](<https://devfeed.tech/tags/images.md>), [incus](<https://devfeed.tech/tags/incus.md>), [keys](<https://devfeed.tech/tags/keys.md>), [linuxcontainers](<https://devfeed.tech/tags/linuxcontainers.md>), [lxc](<https://devfeed.tech/tags/lxc.md>), [network](<https://devfeed.tech/tags/network.md>), [peer](<https://devfeed.tech/tags/peer.md>), [project](<https://devfeed.tech/tags/project.md>), [resources](<https://devfeed.tech/tags/resources.md>)

### AI overview

Incus versions before 7.6.0 have an improper authorization flaw: restricted and view-only clients may access default project resources by requesting that project directly. If they know resource names, they can read profiles, images, network-zone peer keys, and stored credentials. They may also export custom volume or bucket backups, potentially exposing their full contents or S3 admin keys. The supplied text rates the vulnerability 8.3 (high) but gives no specific remediation steps.

### Source excerpt

CVE ID :CVE-2026-130782 Published : Nov. 18, 2026, 7:17 p.m. | 1 hour, 36 minutes ago Description :Incus before 7.6.0 contains an improper authorization vulnerability that allows restricted and view-only clients to read default project resources by requesting the default project directly. Attackers knowing resource names can read profiles, images, network zone peer keys and stored credentials, and export custom volume or bucket backups to obtain full contents or S3 admin keys. Severity: 8.3 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Attackers hijack Microsoft's agent-framework package to steal Azure and CI credentials

DevFeed: [Attackers hijack Microsoft's agent-framework package to steal Azure and CI credentials](<https://devfeed.tech/articles/attackers-hijack-microsoft-s-agent-framework-package-to-steal-azure-and-ci-credentials-140730.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4250167/attackers-hijack-microsofts-agent-framework-package-to-steal-azure-and-ci-credentials-2.html>)

Author: Gyana Swain

Published: 2026-11-18T12:03:34Z

Content type: news

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Azure DevOps](<https://devfeed.tech/topics/azure-devops.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [endor labs](<https://devfeed.tech/topics/endor-labs.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [.env](<https://devfeed.tech/topics/dotenv.md>), [pip](<https://devfeed.tech/topics/pip.md>)

Tags: [agent-framework](<https://devfeed.tech/tags/agent-framework.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-devops](<https://devfeed.tech/tags/azure-devops.md>), [build-systems](<https://devfeed.tech/tags/build-systems.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code-security](<https://devfeed.tech/tags/code-security.md>), [code-security-development-tools-security-software-development](<https://devfeed.tech/tags/code-security-development-tools-security-software-development.md>), [credential-stealer](<https://devfeed.tech/tags/credential-stealer.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [development-tools](<https://devfeed.tech/tags/development-tools.md>), [devops](<https://devfeed.tech/tags/devops.md>), [hijack](<https://devfeed.tech/tags/hijack.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [malware](<https://devfeed.tech/tags/malware.md>), [managed-identity](<https://devfeed.tech/tags/managed-identity.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [openai](<https://devfeed.tech/tags/openai.md>), [package](<https://devfeed.tech/tags/package.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>)

### AI overview

Two malicious PyPI releases of Microsoft's Agent Framework (1.26.1 and 1.26.2) were available for less than an hour on November 17. Their payload ran at Python startup, even without importing the package, while installing the genuine framework so applications continued to work. It collected secrets from environment variables, credential files and running processes, and requested Azure identity tokens; stolen data was sent to an attacker-controlled webhook. The attack particularly targeted CI runners and Azure workloads, according to Endor Labs, and images, caches or lockfiles created during the exposure window may still contain a malicious release. Removing the package cannot retract data already sent. The cited researchers advise checking environments and build artifacts for both versions and their payload files, treating reachable secrets as compromised and rotating them, reviewing Azure activity logs, pinning a verified release with hash checking, and blocking outbound traffic to webhook.site from build infrastructure. Microsoft had not publicly confirmed how the attacker gained publishing access.

### Source excerpt

Attackers briefly hijacked Microsoft's official Agent Framework package on PyPI and used it to distribute credential-stealing malware capable of harvesting cloud tokens, developer secrets and CI/CD credentials from developer workstations and automated build systems, according to multiple security researchers. Two malicious versions of the package, 1.26.1 and 1.26.2, appeared on PyPI on November 17 and stayed live for less than an hour. "The package is a credential stealer: it harvests environment secrets, cloud and package-manager credentials, and Azure managed identity tokens, then exfiltrates them to an attacker-controlled webhook," OX Security, one of several security firms that flagged the releases, said in a blog post. The payload ran automatically every time Python started, even if no code imported the package, OX said. The malicious versions also installed the genuine framework code, so applications kept working, and the compromise was easy to miss. The package has 192,534 monthly downloads, according to the firm. Other security firms, including Aikido Security, Endor Labs, and SafeDep, published similar analyses of the attack. Microsoft has not said publicly how the attacker got access to publish the package. The company did not immediately respond to a request for comment. How the stealer worked The stealer collected environment variables with names containing words such as TOKEN, SECRET, PASSWORD, KEY, AZURE, AWS, GITHUB, and OPENAI, OX said. It also read up to 60 credential files. These included Azure CLI settings, Git and Docker credentials, npm and pip configuration, Hugging Face tokens, Azure DevOps build agent credentials and application .env files. It pulled secrets from up to 300 other running processes as well. The stealer also asked for new tokens. Inside Azure DevOps pipelines, it requested an identity token that can be exchanged for Azure access, OX said in the blog post. It also requested managed identity tokens for Azure services, including Re

## CVE-2026-130740 - Grav 2.0.0 before 2.2.18 Information Disclosure of Password Hashes and Reset Tokens

DevFeed: [CVE-2026-130740 - Grav 2.0.0 before 2.2.18 Information Disclosure of Password Hashes and Reset Tokens](<https://devfeed.tech/articles/cve-2026-130740-grav-2-0-0-before-2-2-18-information-disclosure-of-password-hashes-and-reset-tokens-140427.md>)

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

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-18T11:34:02Z

Content type: news

Language: en

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

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [2-0-0](<https://devfeed.tech/tags/2-0-0.md>), [2026](<https://devfeed.tech/tags/2026.md>), [2fa](<https://devfeed.tech/tags/2fa.md>), [account](<https://devfeed.tech/tags/account.md>), [admin](<https://devfeed.tech/tags/admin.md>), [api](<https://devfeed.tech/tags/api.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve-2026-130740](<https://devfeed.tech/tags/cve-2026-130740.md>), [directory](<https://devfeed.tech/tags/directory.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [flex](<https://devfeed.tech/tags/flex.md>), [form](<https://devfeed.tech/tags/form.md>), [getgrav](<https://devfeed.tech/tags/getgrav.md>), [grav](<https://devfeed.tech/tags/grav.md>), [information](<https://devfeed.tech/tags/information.md>), [password](<https://devfeed.tech/tags/password.md>), [publishers](<https://devfeed.tech/tags/publishers.md>), [reset](<https://devfeed.tech/tags/reset.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [users](<https://devfeed.tech/tags/users.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Grav versions 2.0.0 through before 2.2.18 expose password hashes, two-factor authentication secrets, and reset tokens because account serialization is unfiltered. The excerpt says publishers and read-only user managers can access this data by embedding a Flex form for the user-accounts directory in a page or querying the Flex API with admin.users.read; exposed credentials may enable super-admin account takeover. The vulnerability is rated 8.7 (High).

### Source excerpt

CVE ID :CVE-2026-130740 Published : Nov. 18, 2026, 11:34 a.m. | 14 minutes ago Description :Grav from 2.0.0 before 2.2.18 contains an information disclosure vulnerability that allows publishers and read-only user managers to read password hashes, 2FA secrets and reset tokens through unfiltered account serialization. Attackers can embed a Flex form for the user-accounts directory in a page or query the Flex API with admin.users.read to obtain super admin credentials and take over the account. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Cloud keys leaked in Docker Hub images are stolen within seconds

DevFeed: [Cloud keys leaked in Docker Hub images are stolen within seconds](<https://devfeed.tech/articles/cloud-keys-leaked-in-docker-hub-images-are-stolen-within-seconds-138535.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/cloud-keys-leaked-in-docker-hub-images-are-stolen-within-seconds/>)

Author: Bill Toulas

Published: 2026-11-17T21:27:17Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [token jacking](<https://devfeed.tech/topics/token-jacking.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [anthropic-api](<https://devfeed.tech/tags/anthropic-api.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [automated](<https://devfeed.tech/tags/automated.md>), [aws](<https://devfeed.tech/tags/aws.md>), [business-email-compromise](<https://devfeed.tech/tags/business-email-compromise.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [honeypot](<https://devfeed.tech/tags/honeypot.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [key](<https://devfeed.tech/tags/key.md>), [keys](<https://devfeed.tech/tags/keys.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [public](<https://devfeed.tech/tags/public.md>), [published](<https://devfeed.tech/tags/published.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

In a four-month experiment, researchers published 300 honeypot images across eight public container registries and found exposed credentials could be exploited within seconds. On Docker Hub, the fastest planted AWS key use came 7.86 seconds after publication; the median first call was 51.19 seconds, and all 100 AWS keys were used within 15 minutes. The keys received more than 140,000 API calls from 5,000 unique IP addresses, while exposed OpenAI and Anthropic keys were used to exhaust test-account balances. Monitoring rarely detected containers being run, suggesting scanners usually extracted secrets by inspecting image layers or querying registry APIs. The researchers recommend scanning images for secrets before publication and restricting or rate-limiting access to Docker Hub's feed of recently updated images. In an August check, they found no changes to platform defenses.

### Source excerpt

Credentials and access secrets exposed in public Docker Hub images are being extracted and exploited by attackers within as little as eight seconds of publication. [...]

## Recent Android Remote Key Provisioning Attacks | Guardsquare

DevFeed: [Recent Android Remote Key Provisioning Attacks | Guardsquare](<https://devfeed.tech/articles/recent-android-remote-key-provisioning-attacks-guardsquare-139530.md>)

Original publisher: [Read original article](<https://www.guardsquare.com/blog/android-remote-key-provisioning-attacks>)

Author: Sergio Castell - Security Researcher

Published: 2026-11-17T14:14:41Z

Content type: article

Language: en

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

Topics: [Android Security](<https://devfeed.tech/topics/android-security.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [private key](<https://devfeed.tech/topics/private-key.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Android](<https://devfeed.tech/topics/android.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [App attestation](<https://devfeed.tech/topics/app-attestation.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [api-security](<https://devfeed.tech/tags/api-security.md>), [app-attestation](<https://devfeed.tech/tags/app-attestation.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [automated](<https://devfeed.tech/tags/automated.md>), [backend](<https://devfeed.tech/tags/backend.md>), [bootloader](<https://devfeed.tech/tags/bootloader.md>), [certificate-revocation](<https://devfeed.tech/tags/certificate-revocation.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [crl](<https://devfeed.tech/tags/crl.md>), [dexguard](<https://devfeed.tech/tags/dexguard.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>), [remote](<https://devfeed.tech/tags/remote.md>), [technical](<https://devfeed.tech/tags/technical.md>), [threat-monitoring](<https://devfeed.tech/tags/threat-monitoring.md>)

### AI overview

The excerpt describes two ways attackers can obtain Android Remote Key Provisioning keyboxes through weaknesses in Qualcomm and MediaTek device security. On vulnerable Qualcomm devices, root software can supply a custom attestation public key to KeyMint and use the device as an oracle to request Google-signed certificates; a firmware update can fix the flaw. MediaTek examples involve modifying the TEE to extract attestation keys or provisioning credentials, with the latter potentially enabling certificate requests without the original device. Short-lived certificates and revocation lists do not prevent repeated keybox generation. The excerpt recommends server-side monitoring for keys reused across devices, unusually high certificate issuance counts, and mismatches between attestation and account or transaction behavior, with rate limits or step-up checks in response. It also suggests supplementing Key Attestation with dynamic app attestation.

### Source excerpt

In a previous article, we described how advanced users and attackers are abusing leaked keyboxes and relaying attestation requests to remote devices in order to bypass the Key Attestation API. We also covered how Remote Key Provisioning (RKP) replaces factory-provisioned attestation credentials with regularly renewed certificates.

## MicroVMs, Egress MITM, and sealed tokens: Sandboxing untrusted code at scale

DevFeed: [MicroVMs, Egress MITM, and sealed tokens: Sandboxing untrusted code at scale](<https://devfeed.tech/articles/microvms-egress-mitm-and-sealed-tokens-sandboxing-untrusted-code-at-scale-140598.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/microvms-egress-mitm-and-sealed-tokens-sandboxing-untrusted-code-at-scale>)

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

Content type: article

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [AI Sandbox](<https://devfeed.tech/topics/ai-sandbox.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [agent-fleet](<https://devfeed.tech/tags/agent-fleet.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [ci](<https://devfeed.tech/tags/ci.md>), [controls](<https://devfeed.tech/tags/controls.md>), [egress](<https://devfeed.tech/tags/egress.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [instant](<https://devfeed.tech/tags/instant.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [mitm](<https://devfeed.tech/tags/mitm.md>), [network](<https://devfeed.tech/tags/network.md>), [results](<https://devfeed.tech/tags/results.md>), [sandboxing](<https://devfeed.tech/tags/sandboxing.md>), [scale](<https://devfeed.tech/tags/scale.md>), [sealed](<https://devfeed.tech/tags/sealed.md>), [startup](<https://devfeed.tech/tags/startup.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

The described CI sandbox runs each job in a hardware-isolated microVM and enforces outbound network policy outside the guest. A gVisor-based layer blocks cloud metadata, private ranges, and loopback, and tears down the VM on the first forbidden connection. The supervisor terminates application traffic and can add credentials in flight; SDKs that need a token receive an ephemeral-key-sealed token that is usable only when sent to an authorized host. The article reports that indexed toolchains are exposed through a lazy virtual filesystem, allowing environments with gigabytes of tools to start in under a second. Jobs are configured declaratively, can be invoked from the CLI, a pre-commit hook, an agent call, or a GitHub webhook, and run in separate microVMs with lockfile checks. Each run yields a signed attestation linking environment, result, and commit for merge-gate verification without rerunning the suite. These are the authors' reported design and performance claims.

### Source excerpt

Chainguard explains the engineering behind secure CI for AI agents, from microVM isolation and network controls to instant startup and signed results.

## After the harvest: Find and secure developer secrets without slowing developers down

DevFeed: [After the harvest: Find and secure developer secrets without slowing developers down](<https://devfeed.tech/articles/after-the-harvest-find-and-secure-developer-secrets-without-slowing-developers-down-138315.md>)

Original publisher: [Read original article](<https://1password.com/blog/secure-developer-secrets>)

Author: info@1password.com (Baksheesh Singh Ghuman)

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

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [after](<https://devfeed.tech/tags/after.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [ai-services](<https://devfeed.tech/tags/ai-services.md>), [can](<https://devfeed.tech/tags/can.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-assistants](<https://devfeed.tech/tags/coding-assistants.md>), [commands](<https://devfeed.tech/tags/commands.md>), [commits](<https://devfeed.tech/tags/commits.md>), [copy](<https://devfeed.tech/tags/copy.md>), [created](<https://devfeed.tech/tags/created.md>), [credential-harvesting](<https://devfeed.tech/tags/credential-harvesting.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developers](<https://devfeed.tech/tags/developers.md>), [devices](<https://devfeed.tech/tags/devices.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [unified-access](<https://devfeed.tech/tags/unified-access.md>)

### AI overview

Developer Watchtower finds plaintext credentials, including SSH keys and .env files, on local devices. Its alerts let developers import .env secrets into 1Password Environments, while admins can review a Local disk exposure report showing affected users and devices without seeing secret values. Environments stores and supplies app variables on demand, avoiding a standing plaintext .env file. Developers can import or add variables, use the CLI and SDKs, connect service accounts for automation, and use supported AI coding workflows through 1Password's MCP Server. Teams and Business customers can share environments with groups, with organization-wide availability controlled by admins. The article recommends enabling Watchtower, reviewing the report, treating found credentials as potentially exposed, revoking or rotating them, and storing replacements in Environments. It says Developer Watchtower is available at no extra cost to existing 1Password users.

### Source excerpt

In our first post on credential harvesting, we looked at what happens after an attacker gets inside an environment. The credentials they find can determine how fast and how far they move into other systems. AI is compressing that timeline, and developer machines are where many of those credentials sit. Finding exposed credentials is only half of the job. The harder part is fixing them without disrupting the way developers work. In this post we'll cover how 1Password Developer Watchtower and 1Password Environments help teams find, replace, and manage developer secrets. The riskiest copy of a secret is usually the one on disk For many developers, the fastest place to put a secret is a local .env file. It is familiar, supported by the tools they already use, and usually stored in plaintext. Even when teams provide dedicated secrets tooling, it can feel slow and disconnected from the workflow, so the familiar path wins. That habit feeds secret sprawl, and the numbers are moving the wrong way. GitGuardian's 2026 State of Secrets Sprawl report found 28.65 million new secrets in public GitHub commits in 2025, up 34% from the previous year. Leaked secrets for AI services grew 81% in a single year. For security teams, the bigger problem is visibility. A plaintext credential on a laptop is harder to monitor, rotate, revoke, or trace to the systems that depend on it. And now that AI coding assistants can access project files and run terminal commands, those credentials may be readable by more than the developer who created them. Secure developer secrets with 1Password That is the gap 1Password is closing with 1Password Environments and Developer Watchtower. They help teams find improperly stored developer credentials, secure them where employees already trust, and let developers keep using them without slowing down work. Developer Watchtower finds plaintext developer credentials on local devices, including .env files, and guides users to import them into 1Password Developer cr

## CVE-2026-76823 - OpenCTI: Elasticsearch credentials disclosed to connector tokens through logsWorkerConfig

DevFeed: [CVE-2026-76823 - OpenCTI: Elasticsearch credentials disclosed to connector tokens through logsWorkerConfig](<https://devfeed.tech/articles/cve-2026-76823-opencti-elasticsearch-credentials-disclosed-to-connector-tokens-through-logsworkerconfig-136285.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-16T21:17:31Z

Content type: news

Language: en

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

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [audit](<https://devfeed.tech/tags/audit.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [bearer-token](<https://devfeed.tech/tags/bearer-token.md>), [capability](<https://devfeed.tech/tags/capability.md>), [citeum](<https://devfeed.tech/tags/citeum.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-76823](<https://devfeed.tech/tags/cve-2026-76823.md>), [delete](<https://devfeed.tech/tags/delete.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [history](<https://devfeed.tech/tags/history.md>), [impact](<https://devfeed.tech/tags/impact.md>), [index](<https://devfeed.tech/tags/index.md>), [opencti](<https://devfeed.tech/tags/opencti.md>), [opencti-platform](<https://devfeed.tech/tags/opencti-platform.md>), [published](<https://devfeed.tech/tags/published.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Before OpenCTI 7.260706.0, the logsWorkerConfig GraphQL query uses the broad CONNECTORAPI capability and exposes Elasticsearch connection details, including credentials, to anyone holding a connector API bearer token. If those credentials are valid and Elasticsearch is reachable, a caller may read, modify, or delete OpenCTI indices and audit history outside application-layer controls; impact depends on credential privileges and network reachability. The issue is fixed in version 7.260706.0.

### Source excerpt

CVE ID :CVE-2026-76823 Published : Nov. 16, 2026, 9:17 p.m. | 1 hour, 37 minutes ago Description :OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260706.0, the logsWorkerConfig GraphQL query is authorized with the broad CONNECTORAPI capability and returns Elasticsearch connection details including elasticsearch_username, elasticsearch_password, elasticsearch_api_key, the URL, index, proxy, and TLS-verification setting. A holder of any connector API bearer token can retrieve this credential material. If the returned credentials are valid and Elasticsearch is reachable, the caller can directly read, modify, or delete OpenCTI indices and audit history outside application-layer role, marking, organization, and audit controls, with the practical impact bounded by the credentials' privileges and network reachability. This issue is fixed in version 7.260706.0. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## AMD Unveils Versal TR Devices With 229,000 DMIPS and Backside Attack Protection

DevFeed: [AMD Unveils Versal TR Devices With 229,000 DMIPS and Backside Attack Protection](<https://devfeed.tech/articles/amd-unveils-versal-tr-devices-with-229-000-dmips-and-backside-attack-protection-136076.md>)

Original publisher: [Read original article](<https://www.storagereview.com/news/amd-unveils-versal-tr-devices-with-229000-dmips-and-backside-attack-protection>)

Author: Harold Fritts

Published: 2026-11-16T15:43:01Z

Content type: news

Language: en

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

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Protection](<https://devfeed.tech/topics/protection.md>), [Embedded Systems](<https://devfeed.tech/topics/embedded-systems.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>)

Tags: [3d](<https://devfeed.tech/tags/3d.md>), [acceleration](<https://devfeed.tech/tags/acceleration.md>), [aging](<https://devfeed.tech/tags/aging.md>), [ai](<https://devfeed.tech/tags/ai.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [amd](<https://devfeed.tech/tags/amd.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [arm](<https://devfeed.tech/tags/arm.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [availability](<https://devfeed.tech/tags/availability.md>), [boot](<https://devfeed.tech/tags/boot.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [compute](<https://devfeed.tech/tags/compute.md>), [edge](<https://devfeed.tech/tags/edge.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [int8](<https://devfeed.tech/tags/int8.md>), [portfolio](<https://devfeed.tech/tags/portfolio.md>), [protection](<https://devfeed.tech/tags/protection.md>)

### AI overview

AMD's Versal TR devices pair Versal AI Edge Series Gen 2 compute with added physical and cryptographic protections. A sensor-based die bonded over the compute die is intended to shield the silicon backside, detect tampering, and prevent boot if it is removed or compromised; expanded glitch detection covers simultaneous glitches across two voltage rails. The devices add hardware acceleration for ML-DSA and SLH-DSA, hybrid boot signatures, and ASU key-vault improvements alongside a memory element aging sensor. AMD lists portfolio maxima of 229,000 DMIPS, 369 INT8 TOPS, and 543,000 LUTs, without assigning them to specific SKUs. Select equivalent Gen 2 devices can be used for development and transitioned to corresponding TR devices without rerunning synthesis or place and route. First samples are expected in the second half of 2027, with production in the first half of 2028. The first-of-its-kind protection claim is attributed to AMD's internal analysis; the referenced footnote was not supplied.

### Source excerpt

AMD has announced Versal tamper-resistant (TR) devices that combine physical attack protection with the heterogeneous compute architecture of the AMD Versal AI Edge Series Gen 2. The portfolio delivers up to 229,000 DMIPS of scalar compute, 369 INT8 TOPS, and 543,000 LUTs, according to AMD. The first devices are expected to sample in the second The post AMD Unveils Versal TR Devices With 229,000 DMIPS and Backside Attack Protection appeared first on StorageReview.com.

## CVE-2026-129877 - DeepAudit 2.0.0-beta.1 through 3.8.0 Information Disclosure via /api/v1/config/defaults

DevFeed: [CVE-2026-129877 - DeepAudit 2.0.0-beta.1 through 3.8.0 Information Disclosure via /api/v1/config/defaults](<https://devfeed.tech/articles/cve-2026-129877-deepaudit-2-0-0-beta-1-through-3-8-0-information-disclosure-via-api-v1-config-defaults-135473.md>)

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

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-16T15:17:26Z

Content type: news

Language: en

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

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [token jacking](<https://devfeed.tech/topics/token-jacking.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [cve-2026-129877](<https://devfeed.tech/tags/cve-2026-129877.md>), [deepaudit](<https://devfeed.tech/tags/deepaudit.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [github](<https://devfeed.tech/tags/github.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [lintsinghua](<https://devfeed.tech/tags/lintsinghua.md>), [llm](<https://devfeed.tech/tags/llm.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [server](<https://devfeed.tech/tags/server.md>)

### AI overview

DeepAudit versions 2.0.0-beta.1 through 3.8.0 are reported vulnerable to unauthenticated information disclosure through GET /api/v1/config/defaults. The endpoint can expose the operator's LLM provider API keys and GitHub or GitLab tokens, which attackers could use to abuse those services and access repositories. The excerpt gives a severity rating of 8.7 but does not provide remediation steps.

### Source excerpt

CVE ID :CVE-2026-129877 Published : Nov. 16, 2026, 3:17 p.m. | 23 minutes ago Description :DeepAudit 2.0.0-beta.1 through 3.8.0 contains an information disclosure vulnerability that allows unauthenticated attackers to retrieve server secrets through the /api/v1/config/defaults endpoint. Attackers can send a GET request to obtain the operator's LLM provider API keys and GitHub or GitLab tokens, then abuse those services and accessible repositories. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Managing Secrets in Dockerized Applications: From GitHub Actions to Production

DevFeed: [Managing Secrets in Dockerized Applications: From GitHub Actions to Production](<https://devfeed.tech/articles/managing-secrets-in-dockerized-applications-from-github-actions-to-production-136240.md>)

Original publisher: [Read original article](<https://blog.devops.dev/managing-secrets-with-docker-from-github-actions-to-the-production-server-99a5bc0cd53c?source=rss----33f8b2d9a328---4>)

Author: Vahid Faraji

Published: 2026-11-16T13:26:01Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [secret rotation](<https://devfeed.tech/topics/secret-rotation.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [asp-net](<https://devfeed.tech/tags/asp-net.md>), [asp-net-core](<https://devfeed.tech/tags/asp-net-core.md>), [aspdotnetcore](<https://devfeed.tech/tags/aspdotnetcore.md>), [aws-secrets-manager](<https://devfeed.tech/tags/aws-secrets-manager.md>), [azure](<https://devfeed.tech/tags/azure.md>), [bind](<https://devfeed.tech/tags/bind.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-image](<https://devfeed.tech/tags/docker-image.md>), [files](<https://devfeed.tech/tags/files.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [hashicorp-vault](<https://devfeed.tech/tags/hashicorp-vault.md>), [information](<https://devfeed.tech/tags/information.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [manage](<https://devfeed.tech/tags/manage.md>), [management-secrets](<https://devfeed.tech/tags/management-secrets.md>), [production](<https://devfeed.tech/tags/production.md>), [secrets](<https://devfeed.tech/tags/secrets.md>)

### AI overview

The author keeps production secrets outside Docker images and the deployment workflow by storing each value in a protected file on the VPS, mounting only needed files into containers as read-only, and adding those mounts to GitHub Actions' `docker run` command. In ASP.NET Core, `Program.cs` reads the files at startup into existing `IConfiguration` keys, preserving the application's configuration interface; development uses .NET User Secrets. The approach fits the project's existing multi-container VPS setup and needs only limited workflow and application changes. Its limits include the need to manage file permissions, backups and recovery, access controls, and rotation; because values are read at startup, changed secrets require a container restart. Successful CI or container creation alone does not confirm the application is healthy in production.

### Source excerpt

In one of my projects developed with ASP.NET Core, I was using Docker to run the services and GitHub Actions to manage the CI/CD process. The deployment process was automated: with every push to the main branch, tests were executed first, then a new Docker image was built and transferred to the VPS, and finally the previous container was replaced with the new version. While reviewing this process, I decided to make the management of sensitive production information independent of the build and deployment lifecycle as well. It wasn't just about securing secrets; I wanted each part of the infrastructure to have a clearly defined responsibility. Source code would be stored in Git, the Docker image would be responsible for running the application, GitHub Actions would manage the deployment process, and sensitive information such as API keys, database connection strings, and client secrets would remain in the production environment. My goal was to ensure that each deployment changed only the application version, not the way its sensitive information was managed. I had several options to achieve this, from environment variables and GitHub Actions Secrets to dedicated secret management services such as Azure Key Vault, HashiCorp Vault, and AWS Secrets Manager. However, considering the project's existing architecture, which ran on a VPS with multiple Docker containers, I preferred a simpler and more manageable approach. In the end, I chose protected files on the VPS and read-only Docker bind mounts and implemented this structure with a few limited changes to Program.cs and the GitHub Actions workflow. In the following sections, I'll share my experience with this change, the technical decisions I made, and the lessons I learned during implementation. Step 1: Moving Secrets to the VPS The first thing I did was decide where to store sensitive information on the server. I didn't want to create separate, scattered paths for every secret. I preferred a clear structure that could

## Tighter Access Controls for Management Keys

DevFeed: [Tighter Access Controls for Management Keys](<https://devfeed.tech/articles/tighter-access-controls-for-management-keys-140687.md>)

Original publisher: [Read original article](<https://openrouter.ai/blog/announcements/scoped-management-keys/>)

Author: Sasha Blumenfeld

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

Content type: release

Language: en

Sources: [OpenRouter](<https://devfeed.tech/sources/openrouter.md>)

Topics: [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [CRUD](<https://devfeed.tech/topics/crud.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [audit](<https://devfeed.tech/tags/audit.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [budget](<https://devfeed.tech/tags/budget.md>), [cost](<https://devfeed.tech/tags/cost.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [delete](<https://devfeed.tech/tags/delete.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [error](<https://devfeed.tech/tags/error.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [keys](<https://devfeed.tech/tags/keys.md>), [management](<https://devfeed.tech/tags/management.md>), [workspace](<https://devfeed.tech/tags/workspace.md>)

### AI overview

Management keys can now be restricted by scope (one workspace or the organization) and access level (read-only or read/write). Workspace-scoped keys cannot access other workspaces; within their own workspace they can manage API keys, members, guardrails, provider keys, observability destinations, and presets, and read budgets, activity, and analytics. Budget changes, credits, organization settings, workspace creation or deletion, organization membership, and private endpoints still require an organization key. Read-only keys can use permitted read routes, including analytics, while create, update, and delete requests fail. Scope and access level are fixed at creation; changing them requires creating a replacement key and deleting the old one. Workspace Admins can create keys for their workspace, while Organization Admins can create workspace keys or organization-wide keys.

### Source excerpt

Make a management key read-only, limit it to one workspace, or both, so each key can only do the job it was created for.

## Your SSL certificates can now last 200 days at most: The real risk isn't renewal

DevFeed: [Your SSL certificates can now last 200 days at most: The real risk isn't renewal](<https://devfeed.tech/articles/your-ssl-certificates-can-now-last-200-days-at-most-the-real-risk-isn-t-renewal-133712.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/ssl-certificate-lifespan-200-days-renewal/>)

Author: SitePoint Sponsors

Published: 2026-11-14T06:07:40Z

Content type: article

Language: en

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

Topics: [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>)

Tags: [automated](<https://devfeed.tech/tags/automated.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [expire](<https://devfeed.tech/tags/expire.md>), [fail](<https://devfeed.tech/tags/fail.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [risk](<https://devfeed.tech/tags/risk.md>), [security](<https://devfeed.tech/tags/security.md>), [ssl](<https://devfeed.tech/tags/ssl.md>), [ssl-certificates](<https://devfeed.tech/tags/ssl-certificates.md>)

### AI overview

Certificate lifetimes are capped at 200 days now, fall to 100 days in March 2027, then 47 days in 2029. The shorter schedule chiefly affects manually renewed certificates; managed hosting and CDN setups that already renew automatically may see little change. Automation can fail quietly when credentials or validation break, a renewed certificate is not activated, timers are too long, or certificates sit on systems the automation does not cover. An expired certificate can block visitors and break checkouts, logins, and integrations. The excerpt recommends inventorying certificates and owners, replacing fixed renewal timers with lifetime-based timing, and checking certificates externally as visitors receive them. It proposes warning at about one quarter of certificate life remaining and escalating at one tenth, rather than using fixed 30-day and seven-day alerts. Site24x7 is presented as one cloud monitoring option that reads installed certificates and tracks expiry details.

### Source excerpt

SSL certificates now last 200 days at most, dropping to 47 by 2029. See why automated renewals still fail quietly and how to monitor certificates before they expire. Continue reading Your SSL certificates can now last 200 days at most: The real risk isn't renewal on SitePoint.

## Google Drafts Stricter Key-Management Rules for Web Certificates, Requiring Audits for All Subordinate CA Key Generation

DevFeed: [Google Drafts Stricter Key-Management Rules for Web Certificates, Requiring Audits for All Subordinate CA Key Generation](<https://devfeed.tech/articles/google-drafts-stricter-key-management-rules-for-web-certificates-requiring-audits-for-all-subordinate-ca-key-generation-134010.md>)

Original publisher: [Read original article](<https://joho-todai.com/en/google-web-certificate-key-management-stricter-rules/>)

Author: Toru Misaki

Published: 2026-11-14T01:54:44Z

Content type: news

Language: en

Sources: [Joho no Todai](<https://devfeed.tech/sources/joho-no-todai.md>)

Topics: [private key](<https://devfeed.tech/topics/private-key.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [public key](<https://devfeed.tech/topics/public-key.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [audits](<https://devfeed.tech/tags/audits.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backups](<https://devfeed.tech/tags/backups.md>), [ca](<https://devfeed.tech/tags/ca.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [forms](<https://devfeed.tech/tags/forms.md>), [generation](<https://devfeed.tech/tags/generation.md>), [google](<https://devfeed.tech/tags/google.md>), [key](<https://devfeed.tech/tags/key.md>), [key-management](<https://devfeed.tech/tags/key-management.md>), [keys](<https://devfeed.tech/tags/keys.md>), [management](<https://devfeed.tech/tags/management.md>), [private](<https://devfeed.tech/tags/private.md>), [private-key](<https://devfeed.tech/tags/private-key.md>), [protection](<https://devfeed.tech/tags/protection.md>), [required](<https://devfeed.tech/tags/required.md>), [revision](<https://devfeed.tech/tags/revision.md>), [rules](<https://devfeed.tech/tags/rules.md>), [website](<https://devfeed.tech/tags/website.md>)

### AI overview

The proposed CA/Browser Forum revision would tighten how browser-trusted certificate authorities generate, protect, track, and transfer private keys. Outside validated cryptographic modules, keys could be protected only by encryption with a key-encryption key kept inside the module or by secret sharing; all covered CA key generation would require documented procedures and an auditor's presence or a full video recording. Records would link the generated public key to later certificates through hash comparisons and quality checks, addressing the eMudhra incident in which a different key went undetected for about 18 months. If transfer between devices cannot meet the rules, the CA must generate a new key at the destination. Phase one is scheduled for March 15, 2027, and phase two for September 15, 2027, subject to adoption; missing evidence of compliant protection could require subordinate certificate revocation. Published Japanese CA policies vary, but they cannot establish actual compliance effort because internal controls may differ.

### Source excerpt

A proposed revision to the common standards governing issuers of browser-trusted website certificates would uniformly require approved forms of private-key protection, audited key generation, transfer procedures, and key inventories. A CA that cannot demonstrate the existence and protection of its keys could be required to revoke certificates.

## Hackers compromise 4,800 GitHub accounts to steal cloud credentials

DevFeed: [Hackers compromise 4,800 GitHub accounts to steal cloud credentials](<https://devfeed.tech/articles/hackers-compromise-4-800-github-accounts-to-steal-cloud-credentials-130986.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/hackers-compromise-4-800-github-accounts-to-steal-cloud-credentials/>)

Author: Bill Toulas

Published: 2026-11-12T22:25:30Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [self-hosted runner](<https://devfeed.tech/topics/self-hosted-runner.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [docker](<https://devfeed.tech/tags/docker.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [google-cloud-platform](<https://devfeed.tech/tags/google-cloud-platform.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [wfx-loot](<https://devfeed.tech/tags/wfx-loot.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

The wfx-loot campaign used credentials from 4,837 compromised GitHub accounts to probe 61,764 repositories for write access; researchers confirmed secret theft from at least 1,835 targets. The attackers disguised pull requests as dependency audit notes, then injected a credential-stealing script through GitHub Actions workflows or npm install hooks. It sought GitHub and cloud tokens, developer and infrastructure secrets, and AI-service credentials, and could exchange GitHub OIDC tokens for temporary AWS, Azure, and Google Cloud sessions. Collected data was sent to attacker-controlled servers; changes and logs were then removed in under a minute. Automated publishing also placed malicious releases in Packagist and a Go module. Aikido advises checking for the wfx-docs branch, probe pull requests, and workflow-run gaps; where execution is confirmed, rotate all secrets and cloud roles available to affected workflows.

### Source excerpt

A new campaign dubbed 'wfx-loot' has unfolded on GitHub where threat actors used 4,837 compromised accounts to probe 61,764 repositories, open pull requests, and push secrets-stealing malware. [...]

## eMudhra revokes 8 more CAs it previously declared unaffected by key compromise

DevFeed: [eMudhra revokes 8 more CAs it previously declared unaffected by key compromise](<https://devfeed.tech/articles/emudhra-revokes-8-more-cas-it-previously-declared-unaffected-by-key-compromise-130552.md>)

Original publisher: [Read original article](<https://blog.adafruit.com/2026/11/12/emudhra-revokes-8-more-cas-it-previously-declared-unaffected-by-key-compromise/>)

Author: Anne Barela

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

Content type: news

Language: en

Sources: [Adafruit Industries](<https://devfeed.tech/sources/adafruit-industries-makers-hackers-artists-designers-and-engineers.md>)

Topics: [private key](<https://devfeed.tech/topics/private-key.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [audits](<https://devfeed.tech/tags/audits.md>), [certificate-authorities](<https://devfeed.tech/tags/certificate-authorities.md>), [certificate-authority](<https://devfeed.tech/tags/certificate-authority.md>), [code](<https://devfeed.tech/tags/code.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [emudhra](<https://devfeed.tech/tags/emudhra.md>), [history](<https://devfeed.tech/tags/history.md>), [hsm](<https://devfeed.tech/tags/hsm.md>), [private-key](<https://devfeed.tech/tags/private-key.md>), [python](<https://devfeed.tech/tags/python.md>), [security](<https://devfeed.tech/tags/security.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

eMudhra revoked eight additional intermediate CAs that it had previously said were unaffected by its October key compromise. The issue traces to an April 30, 2025 key ceremony: a Python script used to transfer keys between Utimaco and Crypto4A HSMs read private keys into the ceremony computer's memory. Unlike eight ECDSA keys previously affected by a bug that truncated their values, the eight RSA keys were not shortened; eMudhra says it cannot demonstrate they were handled under its own rules. Six were for TLS and two for code signing, covering 195 certificates. The excerpt says eMudhra is leaving the publicly trusted TLS business.

### Source excerpt

The Hacker News reports that eMudhra has revoked 8 more intermediate certificate authorities, the same ones it had called unaffected by its October key compromise. An intermediate CA has its own private key, used to sign the certificates the company issues. Both problems trace back to a key ceremony on April 30, 2025, where 16 [...]

## Apify rotates API tokens, prompts 2FA resets after breach

DevFeed: [Apify rotates API tokens, prompts 2FA resets after breach](<https://devfeed.tech/articles/apify-rotates-api-tokens-prompts-2fa-resets-after-breach-130429.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/apify-rotates-api-tokens-prompts-2fa-resets-after-breach/>)

Author: Bill Toulas

Published: 2026-11-12T14:36:47Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [secret rotation](<https://devfeed.tech/topics/secret-rotation.md>), [Security](<https://devfeed.tech/topics/security.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [2fa](<https://devfeed.tech/tags/2fa.md>), [accenture](<https://devfeed.tech/tags/accenture.md>), [account](<https://devfeed.tech/tags/account.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-boom](<https://devfeed.tech/tags/ai-boom.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [api](<https://devfeed.tech/tags/api.md>), [apify](<https://devfeed.tech/tags/apify.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automation](<https://devfeed.tech/tags/automation.md>), [breach](<https://devfeed.tech/tags/breach.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [security-breach](<https://devfeed.tech/tags/security-breach.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [systems](<https://devfeed.tech/tags/systems.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [third-party](<https://devfeed.tech/tags/third-party.md>), [token](<https://devfeed.tech/tags/token.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [two-factor-authentication](<https://devfeed.tech/tags/two-factor-authentication.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Apify says an unauthorized third party accessed parts of its internal systems on November 9-10, 2026; it detected the incident the next day, cut off access and began investigating. Its response included rotating internal credentials and customer API tokens, resetting active sessions, and revoking some external OAuth connections, including GitHub. Apify said affected users would be emailed when reconnection is safe. Customer notices said there was no indication that platform-stored account data was affected, but advised some users to reset 2FA because codes may have been exposed; the company said passwords remained safe. The excerpt does not establish the investigation's final findings or the full scope of exposure.

### Source excerpt

Apify has rotated critical internal secrets and revoked some third-party OAuth connections after detecting unauthorized access to its internal systems. [...]

## CVE-2026-127046 - MISP Modules Website Exposes External Tool API Keys in /external\_tools/list Response

DevFeed: [CVE-2026-127046 - MISP Modules Website Exposes External Tool API Keys in /external\_tools/list Response](<https://devfeed.tech/articles/cve-2026-127046-misp-modules-website-exposes-external-tool-api-keys-in-external-tools-list-response-130309.md>)

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

Author: cvefeed.io

Published: 2026-11-12T12:18:23Z

Content type: news

Language: en

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

Topics: [API keys](<https://devfeed.tech/topics/api-keys.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-127046](<https://devfeed.tech/tags/cve-2026-127046.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [enrichment](<https://devfeed.tech/tags/enrichment.md>), [external-services](<https://devfeed.tech/tags/external-services.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [json](<https://devfeed.tech/tags/json.md>), [memory](<https://devfeed.tech/tags/memory.md>), [misp](<https://devfeed.tech/tags/misp.md>), [misp-modules](<https://devfeed.tech/tags/misp-modules.md>), [network](<https://devfeed.tech/tags/network.md>), [network-traffic](<https://devfeed.tech/tags/network-traffic.md>), [patch](<https://devfeed.tech/tags/patch.md>), [website](<https://devfeed.tech/tags/website.md>)

### AI overview

The MISP Modules website exposed stored external-tool API keys through the unauthenticated `/external_tools/list` response. The edit form also placed credentials in the page DOM, client-side state, and save traffic because each save required the key to be sent again. A network-reachable client could retrieve keys used to authenticate with external analysis or enrichment services, potentially impersonating the MISP instance or accessing those services. The described impact is limited to confidentiality of the keys; the source indicates no integrity or availability impact on the website.

### Source excerpt

CVE ID :CVE-2026-127046 Published : Nov. 12, 2026, 12:18 p.m. | 1 hour, 9 minutes ago Description :The MISP Modules website component contains an information disclosure vulnerability in the external tools management interface. The /external_tools/list endpoint returned stored API keys (the api_key field) in its JSON response via the ExternalTools model serializer. Additionally, the browser-based edit form pre-populated the API key input field with the stored credential value, exposing it in the DOM. The /external_tools/list endpoint is accessible without authentication (the regression tests verify the response for both authenticated and unauthenticated clients), meaning any network-reachable client could retrieve the API keys for all configured external tools. These keys are used by the server to authenticate submissions to external analysis or enrichment services, so their disclosure allows an attacker to impersonate the MISP instance or directly access those external services. The vulnerability also affected the edit workflow: the change_config endpoint previously required the API key to be present and non-empty on every save, forcing the key to round-trip through the client. The browser JavaScript stored the key in a reactive state object and updated the in-memory tool list with the credential value, further increasing the window of exposure in client-side memory and network traffic. Affected component: the website sub-application of MISP Modules, specifically the external_tools module (serializer in models.py, list endpoint, and the external_tools_index.html template). The impact is limited to confidentiality of the stored API keys; no integrity or availability impact on the MISP Modules website itself is indicated by the patch. Severity: 9.2 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

[Next page](<https://devfeed.tech/topics/secrets-management.md?cursor=WyIyMDI2LTExLTEyVDEyOjE4OjIzKzAwOjAwIiwgIjYwNjJjNWQ3LTI3MGMtNGE3ZC1iMDA4LWQyMWM3MGMzNDhhMCJd>)