Tiếp theoHướng dẫn tiếp theo
How to Prompt AI for Better Code
Ứng dụng
HƯỚNG DẪN ứng dụng
Trung tâm lời nhắc công khai có thể giúp các nhóm khám phá và điều chỉnh các ví dụ lời nhắc nhưng quy trình công việc SDK có thể tải nhiều hơn văn bản hướng dẫn hiển thị.
Nghe hướng dẫn nàyAI thuật lại · ~3 min
LangSmith public prompt pulls can deserialize manifests containing model or prompt configuration; a 2026 security advisory documents risks including request redirection and exposure of prompt contents or credentials. Treat public manifests as untrusted executable configuration until reviewed, pinned, and tested.
Public prompt collections are useful for finding task structures and examples, but a prompt pulled through an SDK may include a serialized manifest with model configuration or LangChain objects. LangSmith’s documentation describes its public hub as community-created and warns that entries are user-generated, unverified, and not reviewed or endorsed. That statement applies to this hub; it should not be generalized to every prompt marketplace. More importantly, copying visible text and pulling a public manifest into an application are different trust decisions. The LangSmith SDK maintainers published GitHub advisory GHSA-3644-q5cj-c5c7 for public prompt pulls that deserialize untrusted manifests without an explicit trust-boundary warning. The advisory explains that a manifest may configure model endpoints, headers, or other constructor arguments, and may deserialize prompt or runnable objects. In affected workflows, a malicious public manifest could redirect requests to an attacker-controlled base URL or proxy and expose prompt contents, retrieved context, credentials, or other request data. The vulnerability applies when an application pulls a public owner/name prompt, the source is untrusted or compromised, and the application uses the manifest without independent review. It is not a claim that simply viewing a prompt in the web hub causes this impact. The advisory lists patched versions: Python langsmith 0.8.0 and later, JavaScript/TypeScript langsmith 0.6.0 and later, langchain 0.3.30 and later, and langchain-classic 1.0.7 and later. Patched SDKs block public owner/name pulls by default; callers must explicitly opt in with dangerously_pull_public_prompt or dangerouslyPullPublicPrompt. Do not treat that opt-in as a trust check. Review the manifest and source, pin an approved commit rather than relying on a moving latest reference, avoid include_model and secrets_from_env for untrusted sources, and keep credentials scoped. Apply code review, version control, testing, and audit practices as you would for executable configuration. Same-organization prompts also need access controls and review if credentials or accounts could be compromised.
A developer pulls a public LangSmith prompt by owner/name and reviews its manifest, model settings, and pinned commit before considering it for an application.
A security reviewer rejects an untrusted manifest that configures an attacker-controlled model base URL or proxy that could redirect LLM traffic.
A team checks SDK versions against the LangSmith advisory and upgrades Python langsmith to 0.8.0 or later or JS/TS langsmith to 0.6.0 or later.
A prompt library process records the source commit, review evidence, and approved changes, then uses controlled credentials and regression tests before deployment.
Prompt libraries may become more tightly integrated with application code and model configuration, which makes source provenance and change review increasingly important. SDK defaults and advisory guidance can change, so teams should track current maintained documentation and patch notices. A pinned commit, reviewed manifest, controlled credentials, and regression checks provide clearer control than a popularity score or a mutable “latest” reference. Public prompts should remain untrusted until a reviewer approves the exact version and use. Internal prompt libraries also need access control and change history to reduce risks from compromised accounts.
Bản tin miễn phí
Ba câu chuyện AI đã được xác minh vào mỗi buổi sáng các ngày trong tuần, được viết bằng tiếng Anh đơn giản. Miễn phí mãi mãi, không có quảng cáo.
Một email mỗi ngày trong tuần. Hủy đăng ký trong một cú nhấp chuột. Chúng tôi không bao giờ bán hoặc chia sẻ địa chỉ của bạn.
Tự kiểm tra
Phản hồi tức thì về mọi câu trả lời và chứng chỉ có thể chia sẻ với ID có thể xác minh sau khi bạn vượt qua khóa học.
Hỗ trợ giáo dục AI miễn phí. AI Understanding là tổ chức phi lợi nhuận 501(c)(3) — không bao giờ có quảng cáo, không có tường phí. Hãy quyên góp
Public prompt hubs can help teams discover and adapt prompt examples, but SDK workflows may load more than visible instruction text. LangSmith public prompt pulls can deserialize manifests containing model or prompt configuration; a 2026 security advisory documents risks including request redirection and exposure of prompt contents or credentials. Treat public manifests as untrusted executable configuration until reviewed, pinned, and tested.
The current docs give this warning specifically for the public hub.
The advisory says public manifests are deserialized and may configure runtime objects.
The advisory describes request redirection and possible disclosure when vulnerable applications pull untrusted manifests.
The advisory lists langsmith Python versions before 0.8.0 as affected and 0.8.0 as patched.
The advisory lists langsmith npm versions before 0.6.0 as affected and 0.6.0 as patched.
Tiếp tục học hỏi
Đã chọn thêm hướng dẫn cho chủ đề này
Tiếp theoHướng dẫn tiếp theo
How to Prompt AI for Better Code
Ứng dụng